@pnpm/node.resolver
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 creator/maintainer; transition from pnpmuser (CI account) to zkochan is a legitimate and expected change for this pnpm monorepo package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Part of the pnpm monorepo; dormancy reflects no changes needed in this sub-package, not abandonment or takeover. Publisher identity (zkochan) is well-established. | ai | |
| provenance | no-provenance | AI (provenance): pnpm packages are published without Sigstore provenance consistently; publisher has strong track record with 56 approved packages. | ai | |
| phantom-deps | phantom-dep:@pnpm/types | AI (phantom-deps): @pnpm/types is a same-org type-only dependency; phantom detection is a false positive for TypeScript type packages in monorepos. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1001.0.25 | 9 / 3 | |
| 1001.0.24 | 9 / 3 | |
| 1001.0.23 | 9 / 3 | |
| 1001.0.22 | 9 / 3 | |
| 1001.0.21 | 9 / 3 | |
| 1001.0.20 | 9 / 3 | |
| 1001.0.19 | 9 / 3 | |
| 1001.0.18 | 9 / 3 | |
| 1001.0.17 | 9 / 3 | |
| 1001.0.16 | 9 / 3 | |
| 1001.0.15 | 9 / 3 | |
| 1001.0.14 | 9 / 3 | |
| 1001.0.13 | 9 / 3 | |
| 1001.0.12 | 9 / 3 | |
| 1001.0.11 | 9 / 3 | |
| 1001.0.10 | 9 / 3 | |
| 1001.0.9 | 9 / 3 | |
| 1001.0.8 | 9 / 3 | |
| 1001.0.7 | 9 / 3 | |
| 1001.0.6 | 9 / 3 | |
| 1001.0.5 | 9 / 3 | |
| 1001.0.4 | 9 / 3 | |
| 1001.0.3 | 9 / 3 | |
| 1001.0.2 | 9 / 3 | |
| 1001.0.1 | 9 / 3 | |
| 1001.0.0 | 9 / 3 |
v1001.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1001.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.20
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.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.10
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.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.7
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.0.6
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.0.5
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-10-21. This could indicate a legitimate maintainer transition or an account compromise.
v1001.0.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-10-14. This could indicate a legitimate maintainer transition or an account compromise.
v1001.0.3
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.