hypercore-crypto
The crypto primitives used in hypercore, extracted into a separate module
2
Versions
MIT
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
mafintoshandrewosh
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): Trusted long-standing publisher with strong track record; script changes are benign dev tooling additions only. | ai | |
| dependencies | unvetted-dep:b4a | AI (dependencies): b4a is a standard Holepunch/Hypercore ecosystem utility package; expected dependency for this package across all versions. | ai | |
| dependencies | unvetted-dep:compact-encoding | AI (dependencies): compact-encoding is a standard Holepunch/Hypercore ecosystem encoding package; expected dependency for this package across all versions. | ai | |
| dependencies | unvetted-dep:sodium-universal | AI (dependencies): sodium-universal is the canonical libsodium binding used throughout the Hypercore ecosystem; expected and appropriate for a crypto primitives package. | ai |
v3.7.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
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.