hypercore-storage
Storage engine for Hypercore
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:bare-fs | AI (phantom-deps): bare-fs is used via package.json imports map for Bare runtime; not a direct import but legitimately declared. | ai | |
| phantom-deps | phantom-dep:bare-path | AI (phantom-deps): bare-path is used via package.json imports map for Bare runtime; same pattern as bare-fs. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 12 / 7 | |
| 2.9.0 | 13 / 5 | |
| 2.0.4 | 13 / 5 | |
| 2.0.0 | 13 / 5 | |
| 1.18.0 | 13 / 5 |
v3.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.