keccak
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:node-gyp-build | AI (dependencies): node-gyp-build is a well-known, widely-used tool for loading prebuilt native binaries; no risk for this package. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is used in the native C++ binding via binding.gyp, not imported in JS. This is the standard usage pattern for nan in native Node.js addons. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build || exit 0 is the standard prebuilt binary loader pattern for native addons; stable and expected for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .napi.node binaries for darwin/linux/win32 are the documented distribution mechanism for this native crypto addon under cryptocoinjs. | ai |
v3.0.2
3 findingsScript: node-gyp-build || exit 0
Package contains compiled binaries that could be backdoors: • prebuilds/linux-x64/node.napi.glibc.node • prebuilds/linux-x64/node.napi.musl.node • prebuilds/darwin-x64/node.napi.node • prebuilds/win32-x64/node.napi.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
3 findingsScript: node-gyp-build || exit 0
Package contains compiled binaries that could be backdoors: • prebuilds/linux-x64/node.napi.glibc.node • prebuilds/linux-x64/node.napi.musl.node • prebuilds/darwin-x64/node.napi.node • prebuilds/win32-x64/node.napi.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
3 findingsScript: node-gyp-build || exit 0
Package contains compiled binaries that could be backdoors: • prebuilds/darwin-x64/node.napi.node • prebuilds/linux-x64/node.napi.node • prebuilds/win32-x64/node.napi.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
2 findingsScript: npm run rebuild || echo "Keccak bindings compilation fail. Pure JS implementation will be used."
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.