qs

6.17.1 · 28 Oct 2026BSD-3-Clause214.6M / weekRepository npm Atom feed

Same major only

3 releases in betweenevery note read

Other targets from 5.0.0Clears its 4 advisories6.16.0 Latest6.17.1

0
changes to make: 0
advisories fixed: 0
new: 1
fix

Security

4 advisories still affect 5.2.1

qs: Denial of Service via Attacker Controlled isBuffermoderate · GHSA-4mjr-xmp4-gh2g
qs's arrayLimit bypass in its bracket notation allows DoS via memory exhaustionmoderate · GHSA-6rw7-vpxm-498p
Prototype Pollution Protection Bypass in qshigh · GHSA-gqgv-6jq5-jjj9
qs vulnerable to Prototype Pollutionhigh · GHSA-hrpp-h998-j3pp

Upgrading to 6.16.0 clears them.

Release by release

5.2.1
20 Jul 20161 fix
- fixed
  Ensure key=x&key&key=y results in 3, not 2, values
5.1.0 – 5.2.02 releases, nothing new or fixed in the notes

3 other lines we could not sort, mostly version bumps

#64 Add option to sort object keys in the query string
5.2.0
#117 make URI encoding stringified results optional
5.1.0
#106 Add flag skipNulls to optionally skip null values in stringify
5.1.0

Upgrade to 5.2.1

npm install qs@5.2.1

What 5.2.1 needs

Reading 5.2.1's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 5.2.1. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
4 advisories still affect 5.2.1.