http-terminator
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
gajus
Keywords
kubernetesprometheus
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:delay | AI (phantom-deps): delay is explicitly declared as a runtime dependency in package.json; the phantom-dep finding is a false positive likely due to indirect usage patterns in the codebase. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread provenance adoption; publisher gajus has a strong track record. Absence of provenance is not a risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 4 / 20 |
v3.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.