← Home

@alloy-js/typescript

npm Repository Homepage
24
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

bterlson

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; stable for this package going forward. ai
bogus-package bogus-package AI (bogus-package): Part of the @alloy-js monorepo ecosystem by Microsoft's Brian Terlson; missing metadata fields are typical for scoped monorepo packages, not spam indicators. ai
npm-metadata no-description AI (npm-metadata): Scoped monorepo package; missing description is a cosmetic issue, not a security signal for this established package. ai
dependencies unvetted-dep:@alloy-js/core AI (dependencies): @alloy-js/core is a sibling package in the same monorepo, pinned to the same minor version. This is expected and not a risk. ai

Versions (showing 24 of 24)

Version Deps Published
0.24.0 3 / 8
0.23.0 3 / 7
0.22.0 3 / 7
0.21.0 3 / 7
0.20.0 3 / 7
0.19.0 3 / 7
0.18.0 3 / 7
0.17.0 3 / 7
0.16.0 3 / 7
0.15.0 3 / 7
0.14.0 3 / 7
0.13.0 3 / 7
0.12.0 3 / 7
0.11.0 3 / 7
0.10.0 3 / 9
0.9.0 3 / 9
0.8.0 3 / 9
0.7.0 3 / 9
0.6.0 3 / 9
0.5.0 3 / 9
0.4.0 3 / 9
0.3.0 3 / 9
0.2.0 3 / 9
0.1.0 3 / 9

v0.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.