hyperbee
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:b4a | AI (dependencies): b4a is a standard holepunchto buffer utility; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:streamx | AI (dependencies): streamx is a core holepunchto streaming primitive; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established holepunchto ecosystem package; provenance not used by this publisher across their catalog. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.27.3 | 12 / 9 | |
| 2.27.2 | 12 / 9 | |
| 2.27.1 | 12 / 9 | |
| 2.27.0 | 12 / 9 | |
| 2.26.5 | 12 / 6 | |
| 2.26.4 | 12 / 6 | |
| 2.26.3 | 12 / 6 | |
| 2.26.2 | 12 / 6 | |
| 2.26.1 | 12 / 6 | |
| 2.26.0 | 12 / 6 | |
| 2.25.0 | 12 / 6 | |
| 2.24.3 | 11 / 6 |
v2.27.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.
v2.27.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.
v2.27.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.
v2.26.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.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.
v2.25.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.
v2.24.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.