@terrazzo/token-tools
Various utilities for token types
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from drewpowers to GitHub Actions CI/CD is a documented, legitimate migration backed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD migration; SLSA attestation and unchanged content confirm no takeover. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 3 / 0 | |
| 2.1.0 | 3 / 0 | |
| 2.0.3 | 3 / 0 | |
| 2.0.2 | 3 / 0 | |
| 2.0.1 | 3 / 0 | |
| 2.0.0 | 3 / 0 | |
| 0.10.5 | 3 / 1 |
v2.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-16. 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.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.