@mailchain/crypto
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
robdefeotboeckmann
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Scoped @mailchain/crypto package; name similarity to bcrypt is coincidental, not impersonation. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is standard key serialization for secp256k1 public key recovery; no malicious payload. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.31.0 | 10 / 0 |
v0.31.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.