qs

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

Same major only

1 release in betweenevery note read

Other targets from 6.2.6Newest 6.x, Latest6.17.1 Clears its 2 advisories6.16.0

0
changes to make: 0
advisories fixed: 1
new: 2
fixes

Security

4 advisories still affect 6.3.0

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

6.3.0
17 Oct 20161 new · 2 fixes
- new
  Add support for RFC 1738 (#174, #173)
- fixed
  Ensure utils.merge handles merging two arrays
- fixed
  Avoid using a sparse array

5 other lines we could not sort, mostly version bumps

stringify: Add serializeDate option to customize Date serialization
6.3.0
Only constructors should be capitalized
6.3.0
Capitalized var names are for constructors only
6.3.0
formats: cache String#replace
6.3.0
Update browserify, eslint, @ljharb/eslint-config; add safe-publish-latest
6.3.0

4 internal lines (docs, tests, tooling) left out.

Upgrade to 6.3.0

npm install qs@6.3.0

What 6.3.0 needs

Reading 6.3.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 6.3.0. 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 6.3.0.