farmhash
Node-API implementation of FarmHash, Google's family of very fast hash functions
3
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
lovell
Keywords
farmhashhashcityhashmurmurhashfingerprint
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): Standard native addon install pattern (prebuild-install || node-gyp rebuild); stable for this package. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is used via binding.gyp at build time, not via JS import. | ai | |
| phantom-deps | phantom-dep:prebuild-install | AI (phantom-deps): prebuild-install is invoked from install script, not imported in JS. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt platform-specific .node binaries are the standard distribution mechanism for this native addon. SLSA provenance attestation confirms they were built from the official source repo. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used solely to load the correct platform-specific .node binary — a standard and expected pattern for cross-platform native addons. | ai | |
| dependencies | unvetted-dep:detect-libc | AI (dependencies): detect-libc is a well-known utility for detecting glibc vs musl on Linux, legitimately used by native addon packages to select the correct binary. | ai |
v5.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.
v4.0.1
2 findings
HIGH
Package has 'install' script
install-scripts
Script: prebuild-install || 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.