@pnpm/list
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @pnpm package with 7+ years history; levenshtein match to 'jest' is purely coincidental. | ai | |
| phantom-deps | phantom-dep:@pnpm/crypto.polyfill | AI (phantom-deps): @pnpm/crypto.polyfill is listed as a runtime dependency in package.json; same org scope, stable false positive. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1000.3.5 | 11 / 3 | |
| 1000.3.4 | 11 / 3 | |
| 1000.3.3 | 11 / 3 | |
| 1000.3.2 | 11 / 3 | |
| 1000.3.1 | 11 / 3 | |
| 1000.3.0 | 11 / 3 | |
| 1000.2.7 | 10 / 4 | |
| 1000.2.6 | 10 / 4 | |
| 1000.2.5 | 10 / 4 | |
| 1000.2.4 | 10 / 4 | |
| 1000.2.3 | 10 / 4 | |
| 1000.2.2 | 10 / 4 | |
| 1000.2.1 | 10 / 4 | |
| 1000.2.0 | 10 / 4 | |
| 1000.1.5 | 10 / 4 | |
| 1000.1.4 | 10 / 4 | |
| 1000.1.3 | 10 / 4 | |
| 1000.1.2 | 10 / 4 | |
| 1000.1.1 | 10 / 4 | |
| 1000.1.0 | 10 / 4 | |
| 1000.0.22 | 10 / 4 | |
| 1000.0.21 | 10 / 4 | |
| 1000.0.20 | 10 / 4 | |
| 1000.0.19 | 10 / 4 | |
| 1000.0.18 | 10 / 4 | |
| 1000.0.17 | 10 / 4 |
v1000.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.2.0
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.