http-terminator
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
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 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 4 / 20 | |
| 3.1.0 | 4 / 20 | |
| 3.0.4 | 4 / 17 | |
| 3.0.3 | 4 / 16 | |
| 3.0.2 | 4 / 17 | |
| 3.0.1 | 4 / 17 | |
| 3.0.0 | 3 / 17 |
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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.
v3.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.