@pnpm/hooks.types
Types for hooks
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-dep:@pnpm/lockfile.types | AI (dependencies): Internal pnpm monorepo package; publisher has strong track record and SLSA provenance attestation covers the release pipeline. | ai | |
| dependencies | unvetted-dep:@pnpm/store.cafs-types | AI (dependencies): Internal pnpm monorepo package; publisher has strong track record and SLSA provenance attestation covers the release pipeline. | ai | |
| dependencies | unvetted-dep:@pnpm/fetching.fetcher-base | AI (dependencies): Internal pnpm monorepo package; publisher has strong track record and SLSA provenance attestation covers the release pipeline. | ai | |
| dependencies | unvetted-dep:@pnpm/resolving.resolver-base | AI (dependencies): Internal pnpm monorepo package; publisher has strong track record and SLSA provenance attestation covers the release pipeline. | ai | |
| provenance | no-provenance | AI (provenance): Established pnpm monorepo package; lack of provenance is consistent with all other @pnpm/* packages and not a risk signal here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1100.0.9 | 5 / 2 | |
| 1100.0.8 | 5 / 2 | |
| 1100.0.7 | 5 / 2 | |
| 1100.0.6 | 5 / 2 | |
| 1100.0.5 | 5 / 2 | |
| 1100.0.4 | 5 / 2 | |
| 1100.0.3 | 5 / 2 | |
| 1100.0.2 | 5 / 2 | |
| 1100.0.1 | 5 / 2 | |
| 1100.0.0 | 5 / 2 | |
| 1001.0.20 | 2 / 1 | |
| 1001.0.19 | 2 / 1 | |
| 1001.0.18 | 2 / 1 | |
| 1001.0.17 | 2 / 1 | |
| 1001.0.16 | 2 / 1 | |
| 1001.0.15 | 2 / 1 | |
| 1001.0.14 | 2 / 1 | |
| 1001.0.13 | 2 / 1 |
v1100.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.3
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.
v1001.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1001.0.18
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.17
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.16
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.15
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.14
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.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.