query-string
Parse and stringify URL query strings
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:strict-uri-encode | AI (dependencies): strict-uri-encode is a legitimate, well-known sindresorhus utility package; its use as a dependency in query-string is expected and appropriate. | ai | |
| dependencies | unvetted-dep:filter-obj | AI (dependencies): filter-obj is a well-known sindresorhus utility package; a stable, expected dependency of query-string across versions. | ai | |
| dependencies | unvetted-dep:split-on-first | AI (dependencies): split-on-first is a well-known sindresorhus utility package; a stable, expected dependency of query-string across versions. | ai | |
| dependencies | unvetted-dep:decode-uri-component | AI (dependencies): decode-uri-component is a well-known sindresorhus utility package; a stable, expected dependency of query-string across versions. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is common (~88% of npm packages); not a meaningful risk signal for this established, trusted package. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 9.4.0 | 3 / 6 | |
| 9.3.1 | 3 / 6 | |
| 9.3.0 | 3 / 6 | |
| 9.2.2 | 3 / 6 | |
| 9.2.1 | 3 / 6 | |
| 9.2.0 | 3 / 6 | |
| 9.1.2 | 3 / 6 | |
| 9.1.1 | 3 / 6 | |
| 9.1.0 | 3 / 6 | |
| 9.0.0 | 3 / 6 | |
| 8.2.0 | 3 / 6 | |
| 8.1.0 | 3 / 6 | |
| 8.0.3 | 3 / 6 | |
| 8.0.2 | 3 / 6 | |
| 8.0.1 | 3 / 6 | |
| 8.0.0 | 3 / 6 | |
| 7.1.3 | 4 / 6 | |
| 7.1.2 | 4 / 6 | |
| 7.1.1 | 4 / 6 | |
| 7.1.0 | 4 / 6 | |
| 7.0.1 | 4 / 6 | |
| 7.0.0 | 4 / 6 | |
| 6.14.1 | 4 / 6 | |
| 6.14.0 | 4 / 6 | |
| 6.13.8 | 3 / 6 | |
| 6.13.7 | 3 / 6 | |
| 6.13.6 | 3 / 6 | |
| 6.13.5 | 3 / 6 | |
| 6.13.4 | 3 / 6 | |
| 6.13.3 | 3 / 6 | |
| 6.13.2 | 3 / 6 | |
| 6.13.1 | 3 / 6 | |
| 6.13.0 | 3 / 6 | |
| 6.12.1 | 3 / 5 | |
| 6.12.0 | 3 / 5 | |
| 6.11.1 | 3 / 5 | |
| 6.11.0 | 3 / 5 | |
| 6.10.1 | 3 / 5 | |
| 6.10.0 | 3 / 5 | |
| 6.9.0 | 3 / 5 | |
| 6.8.3 | 3 / 5 | |
| 6.8.2 | 3 / 5 | |
| 6.8.1 | 3 / 5 | |
| 6.8.0 | 3 / 5 | |
| 6.7.0 | 3 / 5 | |
| 6.6.0 | 3 / 5 | |
| 6.5.0 | 3 / 5 | |
| 6.4.2 | 3 / 5 | |
| 6.4.0 | 2 / 5 | |
| 6.3.0 | 2 / 5 | |
| 6.2.0 | 2 / 4 |
v9.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.