@pnpm/cli-utils
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): zkochan is the canonical pnpm maintainer; the switch from pnpmuser (CI bot) to zkochan is a legitimate maintainer transition for the pnpm monorepo, not a compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): This is a sub-package of the pnpm monorepo with 379 versions; dormancy reflects the sub-package's update cadence, not project abandonment. Publisher zkochan has a strong track record. | ai | |
| provenance | no-provenance | AI (provenance): pnpm monorepo packages are published without Sigstore provenance; this is consistent across all @pnpm/* packages and not a security concern for this well-established project. | ai | |
| phantom-deps | phantom-dep:load-json-file | AI (phantom-deps): load-json-file is a declared runtime dependency in package.json; phantom-dep flag is a false positive for this package. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1001.3.12 | 14 / 4 | |
| 1001.3.11 | 14 / 4 | |
| 1001.3.10 | 14 / 4 | |
| 1001.3.9 | 14 / 4 | |
| 1001.3.8 | 14 / 4 | |
| 1001.3.7 | 14 / 4 | |
| 1001.3.6 | 14 / 4 | |
| 1001.3.5 | 14 / 4 | |
| 1001.3.4 | 14 / 4 | |
| 1001.3.3 | 14 / 4 | |
| 1001.3.2 | 14 / 4 | |
| 1001.3.1 | 14 / 4 | |
| 1001.3.0 | 14 / 4 | |
| 1001.2.19 | 14 / 4 | |
| 1001.2.18 | 14 / 4 | |
| 1001.2.17 | 14 / 4 | |
| 1001.2.16 | 14 / 4 | |
| 1001.2.15 | 14 / 4 | |
| 1001.2.14 | 14 / 4 | |
| 1001.2.13 | 14 / 4 | |
| 1001.2.12 | 14 / 4 | |
| 1001.2.11 | 14 / 4 | |
| 1001.2.10 | 14 / 4 | |
| 1001.2.9 | 14 / 4 | |
| 1001.2.8 | 14 / 4 | |
| 1001.2.7 | 14 / 4 | |
| 1001.2.6 | 14 / 4 | |
| 1001.2.5 | 14 / 4 | |
| 1001.2.4 | 14 / 4 | |
| 1001.2.3 | 14 / 4 | |
| 1001.2.2 | 14 / 4 | |
| 1001.2.1 | 14 / 4 | |
| 1001.2.0 | 14 / 4 | |
| 1001.1.2 | 14 / 4 | |
| 1001.1.1 | 14 / 4 | |
| 1001.1.0 | 14 / 4 | |
| 1001.0.3 | 14 / 4 | |
| 1001.0.2 | 14 / 4 | |
| 1001.0.1 | 14 / 4 | |
| 1001.0.0 | 14 / 4 |
v1001.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1001.3.6
2 findingsThis version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.13
2 findingsThis version was published by a different npm account than previous versions on 2025-12-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1001.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1001.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.4
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 2025-09-29. This could indicate a legitimate maintainer transition or an account compromise.
v1001.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.1.0
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 2025-08-07. This could indicate a legitimate maintainer transition or an account compromise.
v1001.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.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.