@pnpm/resolve-dependencies
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@pnpm/constants | AI (phantom-deps): Monorepo internal dep; same-org scope, expected pattern. | ai | |
| phantom-deps | phantom-dep:@pnpm/pick-fetcher | AI (phantom-deps): Monorepo internal dep; same-org scope, expected pattern. | ai | |
| phantom-deps | phantom-dep:@pnpm/workspace.spec-parser | AI (phantom-deps): Monorepo internal dep; same-org scope, expected pattern. | ai | |
| phantom-deps | phantom-dep:safe-promise-defer | AI (phantom-deps): Config-referenced dep; stable pattern in this package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1008.8.2 | 41 / 6 | |
| 1008.8.1 | 40 / 5 | |
| 1008.8.0 | 40 / 5 | |
| 1008.7.7 | 40 / 5 | |
| 1008.7.6 | 40 / 5 | |
| 1008.7.5 | 40 / 5 | |
| 1008.7.3 | 40 / 5 | |
| 1008.7.2 | 40 / 5 | |
| 1008.7.1 | 40 / 5 | |
| 1008.7.0 | 40 / 5 | |
| 1008.6.2 | 40 / 5 | |
| 1008.6.1 | 40 / 5 | |
| 1008.6.0 | 40 / 5 | |
| 1008.5.3 | 40 / 5 | |
| 1008.5.2 | 40 / 5 | |
| 1008.5.1 | 40 / 5 | |
| 1008.5.0 | 40 / 5 | |
| 1008.4.0 | 40 / 5 | |
| 1008.3.1 | 40 / 5 | |
| 1008.3.0 | 40 / 5 | |
| 1008.2.4 | 40 / 5 | |
| 1008.2.3 | 40 / 5 | |
| 1008.2.1 | 40 / 5 | |
| 1008.2.0 | 40 / 5 | |
| 1008.1.1 | 39 / 5 | |
| 1008.1.0 | 39 / 5 | |
| 1008.0.2 | 39 / 5 | |
| 1008.0.1 | 38 / 5 | |
| 1008.0.0 | 38 / 5 |
v1008.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1008.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1008.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1008.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1008.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.