@peerbit/crypto
9
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
marcus.pousette
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 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.1.4 | 13 / 2 | |
| 3.1.3 | 12 / 4 | |
| 3.1.2 | 13 / 4 | |
| 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.4
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.