hypercore-crypto
The crypto primitives used in hypercore, extracted into a separate module
Supply chain provenance
Status for the latest visible version.
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
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 |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.7.0 | 3 / 4 | |
| 3.6.1 | 3 / 2 | |
| 3.6.0 | 3 / 2 | |
| 3.5.0 | 3 / 2 | |
| 3.4.2 | 3 / 2 | |
| 3.4.1 | 3 / 2 | |
| 3.4.0 | 3 / 2 | |
| 3.3.1 | 3 / 2 | |
| 3.3.0 | 3 / 2 | |
| 3.2.1 | 3 / 2 | |
| 3.2.0 | 3 / 2 |
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.