hyperbee2
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Holepunch org package published via CI with SLSA provenance; maintainer removal consistent with org housekeeping. | ai | |
| dependencies | unvetted-dep:b4a | AI (dependencies): b4a is a standard mafintosh/Holepunch ecosystem utility; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:streamx | AI (dependencies): streamx is a core mafintosh streaming library; stable false positive 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 JS import by design. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 2.10.2 | 9 / 5 | |
| 2.10.1 | 9 / 5 | |
| 2.10.0 | 9 / 5 | |
| 2.9.5 | 9 / 5 | |
| 2.9.4 | 9 / 5 | |
| 2.9.3 | 9 / 5 | |
| 2.9.2 | 9 / 5 | |
| 2.9.1 | 9 / 5 | |
| 2.9.0 | 9 / 5 | |
| 2.8.0 | 9 / 5 | |
| 2.7.1 | 9 / 5 | |
| 2.7.0 | 9 / 5 | |
| 2.6.1 | 8 / 5 | |
| 2.6.0 | 8 / 5 | |
| 2.5.0 | 8 / 5 | |
| 2.4.4 | 8 / 5 | |
| 2.4.3 | 8 / 5 | |
| 2.4.2 | 8 / 5 | |
| 2.4.1 | 8 / 5 | |
| 2.3.0 | 7 / 5 | |
| 2.2.0 | 7 / 5 | |
| 2.1.1 | 7 / 5 | |
| 2.1.0 | 7 / 5 | |
| 2.0.4 | 7 / 5 | |
| 2.0.3 | 7 / 5 | |
| 2.0.1 | 7 / 5 | |
| 2.0.0 | 7 / 5 | |
| 1.2.0 | 7 / 4 | |
| 1.1.2 | 7 / 4 |
v2.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.1
1 findingPublished 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.