@pnpm/crypto.hash
Generate hashes
3
Versions
MIT
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
pnpmuserzkochan
Keywords
pnpmpnpm11cryptohash
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pnpm/fs.graceful-fs | AI (dependencies): Internal pnpm monorepo package following the same versioning scheme; routine refactoring of graceful-fs handling within the pnpm namespace. | ai | |
| provenance | no-provenance | AI (provenance): pnpm monorepo packages from zkochan consistently lack Sigstore provenance; this is a stable pattern for this publisher and not a risk indicator. | ai | |
| dependencies | unvetted-dep:@pnpm/graceful-fs | AI (dependencies): @pnpm/graceful-fs is an internal pnpm monorepo package published by the same maintainer (zkochan); stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@pnpm/crypto.polyfill | AI (dependencies): @pnpm/crypto.polyfill is an internal pnpm monorepo package published by the same maintainer (zkochan); stable false positive for this package. | ai |
v1100.0.1
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.0
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1000.2.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.