← Home

range-parser

Range header field string parser

12
Versions
MIT
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

ulisesgasconblakeembreytjholowaychukdougwilsonjonathanongjongleberry

Keywords

rangeparserhttp

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): tjholowaychuk → dougwilson is a well-documented legitimate transfer of jshttp packages circa 2016; dougwilson is a core Express/jshttp maintainer with a long established track record. ai
maintainer-change maintainer-added AI (maintainer-change): dougwilson, jonathanong, jongleberry are all known jshttp/Express ecosystem maintainers; this reflects the legitimate 2016 org transfer, not a compromise. ai
source-diff source-size-tripled AI (source-diff): Size increase from ~920B to ~2KB is consistent with legitimate feature additions/validation improvements; no obfuscation or encoded payload indicators present. ai

Versions (showing 12 of 12)

Version Deps Published
1.3.0 0 / 10
1.2.1 0 / 10
1.2.0 0 / 6
1.1.0 0 / 6
1.0.3 0 / 2
1.0.2 0 / 3
1.0.1 0 / 3
1.0.0 0 / 2
0.0.4 0 / 2
0.0.3 0 / 2
0.0.2 0 / 2
0.0.1 0 / 2

v1.3.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: dougwilson → blakeembrey (on 2026-06-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-06-25. This could indicate a legitimate maintainer transition or an account compromise.