@pnpm/registry.pkg-metadata-filter
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pnpm/registry.types | AI (dependencies): @pnpm/registry.types is an internal pnpm monorepo package published by the same trusted publisher; unvetted status is expected and benign for this package. | ai | |
| provenance | no-provenance | AI (provenance): pnpm packages are published by a long-established trusted publisher; lack of Sigstore provenance is acceptable given the track record and canonical repo URL. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1000.1.6 | 2 / 3 | |
| 1000.1.5 | 2 / 3 | |
| 1000.1.4 | 2 / 3 | |
| 1000.1.3 | 2 / 3 | |
| 1000.1.2 | 2 / 3 | |
| 1000.1.1 | 2 / 3 | |
| 1000.1.0 | 2 / 3 | |
| 1000.0.0 | 2 / 3 |
v1000.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.1.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.
v1000.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.