url-http
Get input as normalized WHATWG URL
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:re2 | AI (phantom-deps): re2 is a declared runtime dep used conditionally/optionally; phantom-dep heuristic fires but it's a legitimate optional native binding. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.3.7 | 3 / 12 | |
| 1.3.6 | 3 / 13 | |
| 1.3.5 | 3 / 13 | |
| 1.3.4 | 3 / 13 | |
| 1.3.3 | 3 / 13 | |
| 1.3.2 | 3 / 14 | |
| 1.3.1 | 3 / 14 |
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.