@node-rs/bcrypt-darwin
Rust bcrypt binding
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
broooooklyn
Keywords
bcryptauthpasswordauthenticationencryptioncryptoN-APInapi-rsnode-rs
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): This package IS a platform-specific native binary distribution (.node file) for the napi-rs bcrypt binding. The binary is the intended artifact, not a backdoor. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary sub-packages legitimately have no deps and minimal READMEs; this is a standard napi-rs distribution pattern. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 0 / 0 |
v0.5.0
2 findings
HIGH
Bundled binary files (1)
npm-metadata
Package contains compiled binaries that could be backdoors: • bcrypt.darwin.node
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.