Summary
Togoder Security scanned the npm package qs@6.16.0 on Oct 4, 2026. An AI review of 7 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/qs.js | safe | No malicious patterns detected; this is the standard bundled 'qs' query string library. |
| eslint.config.mjs | safe | Cleared by Jev triage; no further analysis needed |
| lib/formats.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/index.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/parse.js | safe | No malicious patterns detected; this is a legitimate query string parser with standard prototype-pollution and array-limit safeguards. |
| lib/stringify.js | safe | No malicious patterns detected; the file is a standard query-string serialization implementation with no network, filesystem, process, or dynamic code execution activity. |
| lib/utils.js | safe | This is a legitimate utility module from the qs library handling query string parsing/encoding with no malicious patterns such as network requests, credential harvesting, process spawning, or dynamic code execution. |
Affected version ranges
None of the 3 scanned versions of qs are flagged high or critical. The latest scanned version, 6.16.0, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 6.16.0 | No issues | 1 | 6.16.0 | |
| 6.14.0 | Needs review | 1 | 6.14.0 | Prototype pollution |
| 6.13.0 | Not scanned | 1 | 6.13.0 | |
| 6.11.0 | No issues | 1 | 6.11.0 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of qs
Frequently asked questions
Is qs safe to use?
Our AI source review of qs@6.16.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does qs contain malware?
No malware was identified in qs@6.16.0 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was qs checked?
Togoder Security downloaded the published npm package and had an AI model read its 7 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan qs together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in qs@6.16.0, cost nothing.