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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with holepunchto org's CI/CD practices. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance attestation present; strongest supply chain integrity signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): lejeunerenard is a known contributor in the holepunchto ecosystem; addition is consistent with legitimate team growth for this active project. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Hypercore is a long-established package from its original maintainer mafintosh; dormancy followed by resumed development is consistent with the holepunchto ecosystem's release cadence. | ai | |
| dependencies | unvetted-dep:hypercore-storage | AI (dependencies): hypercore-storage is a first-party storage backend for hypercore, maintained by the same Holepunch organization. | ai | |
| dependencies | unvetted-dep:b4a | AI (dependencies): b4a is a well-known Buffer/Uint8Array compatibility library from the Holepunch ecosystem, stable and widely used across many P2P packages. | ai | |
| dependencies | unvetted-dep:streamx | AI (dependencies): streamx is a well-established streams implementation from the Holepunch/mafintosh ecosystem, used across many legitimate packages. | ai | |
| provenance | no-provenance | AI (provenance): hypercore is a long-established Holepunch ecosystem package; lack of provenance is consistent across all versions and is not a risk signal here. | ai | |
| phantom-deps | phantom-dep:bare-events | AI (phantom-deps): bare-events is intentionally declared in package.json imports for Bare runtime compatibility — a documented Holepunch ecosystem pattern, not a phantom dependency in the traditional sense. | ai |
Versions (showing 47 of 147)
| Version | Deps | Published |
|---|---|---|
| 11.0.46 | 20 / 10 | |
| 11.0.45 | 20 / 10 | |
| 11.0.44 | 20 / 10 | |
| 11.0.43 | 20 / 10 | |
| 11.0.42 | 20 / 10 | |
| 11.0.41 | 20 / 10 | |
| 11.0.40 | 20 / 10 | |
| 11.0.39 | 20 / 10 | |
| 11.0.38 | 20 / 10 | |
| 11.0.37 | 20 / 10 | |
| 11.0.36 | 20 / 10 | |
| 11.0.35 | 20 / 10 | |
| 11.0.34 | 20 / 10 | |
| 11.0.33 | 20 / 10 | |
| 11.0.32 | 20 / 10 | |
| 11.0.31 | 20 / 10 | |
| 11.0.30 | 20 / 10 | |
| 11.0.29 | 20 / 10 | |
| 11.0.28 | 20 / 10 | |
| 11.0.27 | 20 / 10 | |
| 11.0.26 | 20 / 10 | |
| 11.0.25 | 20 / 10 | |
| 11.0.24 | 20 / 10 | |
| 11.0.23 | 20 / 10 | |
| 11.0.22 | 20 / 10 | |
| 11.0.21 | 20 / 10 | |
| 11.0.20 | 20 / 10 | |
| 11.0.19 | 20 / 10 | |
| 11.0.18 | 22 / 12 | |
| 11.0.17 | 22 / 12 | |
| 11.0.16 | 22 / 12 | |
| 11.0.15 | 22 / 12 | |
| 11.0.14 | 22 / 12 | |
| 11.0.13 | 22 / 12 | |
| 11.0.12 | 22 / 12 | |
| 11.0.11 | 22 / 12 | |
| 11.0.10 | 22 / 12 | |
| 11.0.9 | 22 / 12 | |
| 11.0.8 | 22 / 12 | |
| 11.0.7 | 22 / 12 | |
| 11.0.6 | 22 / 12 | |
| 11.0.5 | 22 / 12 | |
| 11.0.4 | 22 / 12 | |
| 11.0.3 | 22 / 12 | |
| 11.0.2 | 22 / 12 | |
| 11.0.1 | 22 / 12 | |
| 11.0.0 | 22 / 12 |
v11.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.