amp-toolbox-optimizer
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): AMP Optimizer bundles AMP runtime/transformer assets; large file counts are expected for this package's nature and consistent with its history. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth reflects bundled AMP runtime artifacts, a known characteristic of AMP tooling packages, not injected payloads. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads from a fixed local subdirectory (__dirname/transformers/). This is a standard plugin-loading pattern within the package's own files, not arbitrary module loading. | ai | |
| dependencies | unvetted-dep:amp-toolbox-core | AI (dependencies): amp-toolbox-core is a first-party sibling package from the same ampproject/amp-toolbox monorepo and publisher; not a third-party risk. | ai | |
| dependencies | unvetted-dep:amp-toolbox-runtime-version | AI (dependencies): amp-toolbox-runtime-version is a first-party sibling package from the same ampproject/amp-toolbox monorepo and publisher; not a third-party risk. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.5.3 | 5 / 0 | |
| 0.5.2 | 5 / 0 | |
| 0.5.1 | 6 / 0 | |
| 0.5.0 | 5 / 0 | |
| 0.4.8 | 5 / 0 | |
| 0.4.7 | 5 / 0 | |
| 0.4.6 | 5 / 0 | |
| 0.4.5 | 5 / 0 | |
| 0.4.4 | 5 / 0 | |
| 0.4.3 | 5 / 0 | |
| 0.4.1 | 5 / 8 | |
| 0.4.0 | 4 / 9 | |
| 0.3.1 | 3 / 8 | |
| 0.3.0 | 3 / 8 | |
| 0.1.0 | 3 / 8 |
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.