[dependabot]

Bumps qs from 6.16.0 to 6.17.0.

Changelog

Sourced from qs's changelog.

6.17.0

• [New] stringify: add WHATWG format (#623)
• [Fix] stringify: do not sort the caller's filter array in place (#637)
• [Fix] parse: copy an own __proto__ key as data (#636)
• [Fix] parse: decode percent-encoded dots case-insensitively (#635)
• [Fix] stringify: encode keys when allowEmptyArrays is set (#561)
• [Fix] parse: preserve comma arrays when interpreting numeric entities (#630)
• [Fix] parse: allow scalar fields with a zero array limit (#627)
• [Fix] parse: do not count an existing comma array toward arrayLimit when duplicates discards or replaces it
• [Fix] utils: encode: encode lone surrogates as U+FFFD instead of consuming the next code unit (#624)
• [eslint] fix indentation
• [readme] document the encoder's format argument
• [meta] add changelog acknowledgement
• [meta] fix changelog indents
• [Dev Deps] update eslint, evalmd, npmignore
• [Tests] stringify: pin allowEmptyArrays output for keys that need no encoding
• [Tests] stringify: pin sort order for nested keys selected by an array filter
• [Tests] parse: cover interpretNumericEntities across value shapes, keys, and the charset sentinel
• [Tests] parse: cover more input that builds no array at a zero or negative arrayLimit
• [Tests] parse: cover comma with a zero or negative arrayLimit, and combining a full comma array
• [Tests] parse: pin the behavior of a zero or negative arrayLimit
• [Tests] utils/stringify: pin ~, *, and parens encoding in RFC3986 and RFC1738

6.16.2

• [Fix] stringify: encode keys when allowEmptyArrays is set (#561)
• [meta] use double quotes for better OS support
• [Dev Deps] update evalmd, npmignore
• [Tests] stringify: pin allowEmptyArrays output for keys that need no encoding

6.16.1

• [Fix] parse: do not mutate an object input
• [Fix] stringify: stop re-encoding structural separator dots when encodeDotInKeys is set (#564)
• [Fix] stringify: arrayFormat: 'comma': pass the full encoder arguments with encodeValuesOnly
• [Fix] utils: encode + as %2B in iso-8859-1 mode so values round-trip (#565)
• [Fix] parse: only convert top-level dots to brackets when allowDots is on (#621)
• [Fix] stringify: ignore inherited array format names (#622)
• [Fix] stringify: arrayFormat: 'comma': do not throw on elements with no callable toString
• [Fix] utils: merge: seed an overflow container's index from its own keys, not just the source
• [Fix] utils: merge: keep a strictMerge conflict container's index and arrayLimit correct
• [Fix] parse: only treat [] as array syntax when it ends the key
• [Perf] decode: skip decoders when there is no percent sign (#583)
• [Robustness] utils: merge: apply arrayLimit to the two-element array built for colliding values
• [Robustness] parse: bound the nesting added by repeated strictMerge conflicts (credit @​Yeaseen)
• [Docs] document that qs and flat parsers disagree about parameter names
• [Docs] clarify that throwOnLimitExceeded limits each array, not the total number of values
• [Docs] clarify 6.14.1/6.15.2 parse bracket behavior change (#567, #568)
• [meta] fix changelog indents
• [actions] set least-privilege cache-mode
• [Tests] utils: decode: add missing cases
• [Tests] parse: characterize the ]= split when an = precedes any bracket group (#620)

... (truncated)

Commits

• bebfa1a v6.17.0
• 574a28b [Dev Deps] update eslint
• 54f7f3b [Fix] stringify: do not sort the caller's filter array in place
• a2667af [Fix] parse: copy an own __proto__ key as data
• 05a8755 [Fix] parse: decode percent-encoded dots case-insensitively
• 234d505 [Fix] stringify: encode keys when allowEmptyArrays is set
• 5d99999 [Tests] stringify: pin allowEmptyArrays output for keys that need no enco...
• feafd15 [Tests] stringify: pin sort order for nested keys selected by an array `f...
• b43b1cf [Fix] parse: preserve comma arrays when interpreting numeric entities
• 81e7a22 [Tests] parse: cover interpretNumericEntities across value shapes, keys, ...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dirkenglund]

🟢 GLM first-line review: CLEAN — 0afd8464

GLM first-line review | model=gpt-6-astra finish_reason=stop | examined 1 file(s), 778 bytes: packages/com8/package-lock.json

VERDICT: CLEAN

VERDICT: CLEAN

reviewed by codex-gpt-6-astra

GLM-5.3-Flash via the owner's gateway, exit 0. Posted by the org first-line runner (scripts/firstline_review_org.py, on every head the org router queues); the lanes review in depth after it. A new push re-runs this.

[qpai-firstline-review]

🔴 GLM first-line review: DEFECTS — 0afd8464 (glm, model=glm)

GLM first-line review | model=glm finish_reason=stop effort=max reasoning=20663 chars | examined 1 file(s), 778 bytes: packages/com8/package-lock.json

VERDICT: DEFECTS

VERDICT: DEFECTS

DEFECT 1 — Fabricated integrity hash for qs 6.17.0 (malformed SRI, cannot match the real tarball)

• Mechanism: An npm <redacted>- integrity value is base64 of a 64-byte (512-bit) digest, which is always exactly 88 characters ending in == (64 mod 3 = 1). The old value in this same hunk is correct (<redacted>...<redacted>==, 88 chars). The new value <redacted> is only 86 characters with no == padding. It is not a valid canonical encoding of any 512-bit digest, and even under lenient base64 decoding the resulting bytes cannot equal the SHA-512 of the actual <redacted> artifact.
• Consequence: npm ci / clean npm install will fail with an integrity error (hash mismatch / integrity failed to parse) for every developer machine and CI run that consumes this lockfile. Equally important, a structurally impossible hash that appears alongside a version, resolved-URL, and integrity rewrite is the signature of a hand-edited lockfile rather than one regenerated by npm install — i.e., a potential supply-chain tampering attempt to redirect the package to content no one has verified. A legitimate patch/minor bump would carry the registry's real, correctly padded digest.

DEFECT 2 — Lockfile entry is inconsistent with the real qs package metadata (corroborates fabrication; note this line is unchanged context)

• Mechanism: The entry shows "es-define-property": "^1.0.1" as a direct dependency of node_modules/qs. The real qs package declares only side-channel as a direct dependency; es-define-property belongs to the transitive side-channel-list/side-channel-map/side-channel-weakmap packages. This line predates the diff (it is context), but together with Defect 1 it indicates this lockfile section was hand-written rather than emitted by npm.
• Consequence: Readers and reviewers cannot trust this lockfile section to describe the actual dependency graph; a hand-authored entry can silently add, drop, or repin transitive dependencies, and it undermines the lockfile's role as a verified install plan.

reviewed by glm

glm (glm) via the owner's gateway, exit 1. Posted by the org first-line runner (scripts/firstline_review_org.py, on every head the org router queues); the lanes review in depth after it. A new push re-runs this.