hyperdrive
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:streamx | AI (dependencies): streamx is a core Holepunch/mafintosh streaming library; stable dependency in this ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Established Holepunch package; provenance not used by this publisher across their ecosystem. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 13.3.2 | 12 / 14 | |
| 13.3.1 | 12 / 14 | |
| 13.3.0 | 12 / 13 | |
| 13.2.1 | 12 / 13 | |
| 13.2.0 | 12 / 13 | |
| 13.1.3 | 12 / 13 | |
| 13.1.2 | 12 / 13 | |
| 13.1.1 | 12 / 13 | |
| 13.1.0 | 12 / 13 | |
| 13.0.2 | 12 / 12 | |
| 13.0.1 | 12 / 11 | |
| 13.0.0 | 12 / 11 |
v13.3.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.
v13.3.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.
v13.2.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.
v13.2.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.
v13.1.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.
v13.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.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.
v13.1.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.
v13.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.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.