@pnpm/fetching.binary-fetcher
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-peer-dep:@pnpm/worker | AI (dependencies): Internal pnpm monorepo peer dependency; stable across versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are pnpm-internal monorepo packages at matching version (1100.0.0), consistent with namespace reorganization from @pnpm/fetcher-base to @pnpm/fetching.fetcher-base etc. SLSA provenance confirms CI/CD build integrity. | ai | |
| dependencies | unvetted-dep:@pnpm/fetching.fetcher-base | AI (dependencies): Internal pnpm monorepo package following the same naming/versioning convention; published by the same pnpmuser account with strong track record. | ai | |
| dependencies | unvetted-dep:@pnpm/fetching.types | AI (dependencies): Internal pnpm monorepo package following the same naming/versioning convention; published by the same pnpmuser account with strong track record. | ai | |
| dependencies | unvetted-dep:@pnpm/store.index | AI (dependencies): Internal pnpm monorepo package following the same naming/versioning convention; published by the same pnpmuser account with strong track record. | ai | |
| provenance | no-provenance | AI (provenance): pnpm is a well-established, trusted package manager project; lack of Sigstore provenance is not a meaningful risk signal for this publisher. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1101.0.8 | 9 / 5 | |
| 1101.0.7 | 9 / 5 | |
| 1101.0.6 | 9 / 5 | |
| 1101.0.5 | 9 / 5 | |
| 1101.0.4 | 9 / 5 | |
| 1101.0.3 | 9 / 5 | |
| 1101.0.2 | 9 / 5 | |
| 1101.0.1 | 9 / 5 | |
| 1101.0.0 | 9 / 5 | |
| 1100.0.2 | 9 / 5 | |
| 1100.0.1 | 9 / 5 | |
| 1100.0.0 | 9 / 5 | |
| 1005.0.4 | 8 / 5 | |
| 1005.0.3 | 8 / 5 | |
| 1005.0.2 | 8 / 5 | |
| 1005.0.1 | 7 / 3 | |
| 1005.0.0 | 7 / 3 | |
| 1004.0.0 | 7 / 3 | |
| 1003.0.1 | 7 / 3 | |
| 1003.0.0 | 7 / 3 | |
| 1002.0.3 | 7 / 3 | |
| 1002.0.2 | 7 / 3 | |
| 1002.0.1 | 7 / 3 |
v1101.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1101.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1101.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1101.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1101.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1101.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1101.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1101.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1101.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1005.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1005.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1005.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1005.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1005.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1004.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1003.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1003.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.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.