@types/bcryptjs
1
Versions
—
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
types
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Package correctly targets bcryptjs; Levenshtein match to bcrypt is a false positive for this stub. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Stub/deprecated @types package; minimal payload and no docs are expected for this pattern. | ai | |
| phantom-deps | phantom-dep:bcryptjs | AI (phantom-deps): Stub package; bcryptjs is the peer it redirects to, not a direct import. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 1 / 0 |
v3.0.0
1 finding
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.