create-hash
create hashes for browserify
2
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
cwmmadcousensdominictarrindutnyjprichardson
Keywords
crypto
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in test.js is used to decode hash test vectors for algorithm verification — standard practice in crypto test suites, not a malicious payload. | ai | |
| dependencies | unvetted-dep:ripemd160 | AI (dependencies): ripemd160 is a standard crypto-browserify ecosystem dependency, expected for this hashing library. | ai | |
| dependencies | unvetted-dep:cipher-base | AI (dependencies): cipher-base is a standard crypto-browserify ecosystem dependency, expected for this hashing library. | ai |
v1.1.3
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.