blake2
1
Versions
—
License
Yes
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
ludiosvrza
Keywords
cryptohashhashingblake2blake2bblake2bpblake2sblake2sp
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): node-gyp rebuild is the standard build step for this native BLAKE2 binding; stable across versions. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): NAN is used via binding.gyp/native addon build, not directly imported in JS; false positive for native addons. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 1 / 2 |
v5.0.1
2 findings
HIGH
Package has 'install' script
install-scripts
Script: node-gyp rebuild
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.