hyperblobs
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): holepunchto org publishes via GitHub Actions CI/CD with SLSA attestation; this is the expected publisher going forward. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): andrewosh removal aligns with org-level CI/CD publishing transition; no malicious indicators. | ai | |
| 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 library; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:bare-events | AI (phantom-deps): bare-events is used via package.json imports map for Bare runtime; not a direct import by design. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.12.1 | 8 / 5 | |
| 2.12.0 | 8 / 5 | |
| 2.11.1 | 8 / 5 | |
| 2.11.0 | 8 / 5 | |
| 2.10.0 | 8 / 5 | |
| 2.9.1 | 8 / 5 | |
| 2.9.0 | 8 / 5 |
v2.12.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-05. 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.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.