@ampproject/toolbox-core
Commonly used functionality for amp-toolbox
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer changes reflect normal team rotation within the official AMP Project org; publisher account and repo URL remain consistent with the ampproject GitHub org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of prior maintainers is consistent with team rotation in the AMP Project; no signs of hostile takeover given stable publisher account and repo. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; absence is expected for this era of publishing and not a risk indicator for this established package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from amp-toolbox to ampproject-admin reflects a legitimate AMP Project org account consolidation; ampproject-admin has a strong track record (109 approved, 0 rejected) and is the canonical AMP Project admin account. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 2.10.1 | 2 / 0 | |
| 2.10.0 | 2 / 0 | |
| 2.9.0 | 2 / 0 | |
| 2.8.0 | 2 / 0 | |
| 2.7.4 | 2 / 0 | |
| 2.7.2 | 2 / 0 | |
| 2.7.1 | 2 / 0 | |
| 2.6.1 | 2 / 0 | |
| 2.6.0 | 2 / 0 | |
| 2.5.4 | 2 / 0 | |
| 2.5.1 | 2 / 0 | |
| 2.5.0 | 2 / 0 | |
| 2.3.0 | 1 / 0 | |
| 2.2.0 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 1.1.1 | 1 / 0 | |
| 1.1.0 | 1 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 |
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
2 findingsThis version was published by a different npm account than previous versions on 2024-06-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-12-02. This could indicate a legitimate maintainer transition or an account compromise.
v2.6.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-10-01. This could indicate a legitimate maintainer transition or an account compromise.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.