@peerbit/crypto
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has clean track record; no content changes vs prior approved version; dormancy consistent with slow-moving crypto library. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): elliptic is a widely-used, legitimate crypto library; its use here is expected for a crypto utility package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established crypto utility in a large monorepo; sparse README/keywords are a style choice, not spam. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): @peerbit/crypto is a scoped crypto utility in the peerbit ecosystem; Levenshtein proximity to bcrypt is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:@peerbit/cache | AI (phantom-deps): @peerbit/cache is listed as a runtime dep and is same-org; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 13 / 4 | |
| 3.1.0 | 13 / 4 | |
| 3.0.1 | 13 / 4 | |
| 3.0.0 | 13 / 4 | |
| 2.4.1 | 13 / 4 | |
| 2.4.0 | 13 / 4 |
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.