bcrypto
JS crypto library
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:bufio | AI (dependencies): bufio is a bcoin-org package published by the same author (chjj) as bcrypto; it is a trusted sibling dependency within the same ecosystem. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is used by node-gyp for native addon compatibility; it is referenced in build config files as expected for a native C++ addon package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is a core utility in a cryptography library; no malicious payload hiding, just standard encoding operations. | ai | |
| typosquat | typosquat.levenshtein:bcryptjs | AI (typosquat): bcrypto is a distinct, well-established crypto library in the bcoin-org ecosystem, not a typosquat of bcryptjs. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): bcrypto is a distinct, well-established crypto library in the bcoin-org ecosystem, not a typosquat of bcrypt. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is expected and legitimate in a cryptography library handling PEM/encoding formats; not indicative of malicious payloads. | ai | |
| install-scripts | install-script:install | AI (install-scripts): bcrypto is a native crypto addon; node-gyp rebuild is the standard and expected install script for building C bindings. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 3 / 2 | |
| 4.2.9 | 4 / 1 | |
| 4.2.8 | 4 / 1 | |
| 4.1.0 | 4 / 1 | |
| 4.0.1 | 4 / 1 | |
| 4.0.0 | 4 / 1 |
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.