@alloy-js/typescript
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.23.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.