chore(deps): Bump qs from 6.15.2 to 6.16.0 in /agent-governance-python/agent-os/extensions/mcp-server

[dependabot]

Bumps qs from 6.15.2 to 6.16.0.

Changelog

Sourced from qs's changelog.

6.16.0

• [New] stringify: add a depth option to bound recursion depth (default Infinity)
• [Fix] stringify: serialize Date values when a filter is provided
• [Fix] parse: enforce arrayLimit on comma groups under []= when throwOnLimitExceeded is set
• [Fix] parse: flatten a collection appended to an overflowed array (#571)
• [Fix] utils: isBuffer: do not invoke a non-callable constructor.isBuffer
• [Fix] stringify: do not let allowEmptyArrays skip cycle detection (or drop own keys) on an empty array with own properties
• [Fix] stringify: encode dots in a top-level key with a primitive value when encodeDotInKeys is set (#562)
• [Docs] threat model: clarify stringify deep-nesting DoS is caller-bounded
• [Docs] clarify arrayLimit is a representation threshold, not an element-count cap
• [Tests] parse: remove a test that pinned []= comma groups escaping arrayLimit
• [Tests] stringify: pin current encodeDotInKeys separator-dot behavior
• [Dev Deps] update @ljharb/eslint-config, eslint
• [Dev Deps] update eslint, evalmd

6.15.3

• [Fix] parse: enforce throwOnLimitExceeded for cumulative array growth via combine/merge
• [Fix] utils: respect encoding of surrogate pairs across chunks (#559)
• [Robustness] parse: throw the arrayLimit error before splitting oversized comma values
• [Robustness] utils.merge / utils.assign: avoid invoking __proto__ setter when copying own properties
• [Robustness] utils: enforce arrayLimit consistently across merge's array paths
• [Perf] utils: make compact O(n) via a side-channel visited-set instead of Array.indexOf
• [Deps] update side-channel
• [Dev Deps] update eslint, mock-property, tape
• [Tests] parse: characterize current lenient handling of unbalanced bracket keys (#558)

Commits

• bb9379e v6.16.0
• 62fd254 [Fix] stringify: serialize Date values when a filter is provided
• 8859c37 [Fix] parse: enforce arrayLimit on comma groups under []= when `throwOn...
• 8079adc [Tests] parse: remove a test that pinned []= comma groups escaping `array...
• d56f48c [Fix] parse: flatten a collection appended to an overflowed array
• e83d321 [Fix] utils: isBuffer: do not invoke a non-callable constructor.isBuffer
• 7e87a07 [Dev Deps] update @ljharb/eslint-config, eslint
• 9a76af2 [Dev Deps] update eslint, evalmd
• 3a890d4 [Dev Deps] update eslint, evalmd
• b433a9b [Fix] stringify: do not let allowEmptyArrays skip cycle detection (or dro...
• 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.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[github-actions]

PR Review Summary

Check	Status	Details
🔍 Code Review	⚠️ Missing	No current-run comment
🛡️ Security Scan	⚠️ Missing	No current-run comment
🔄 Breaking Changes	⚠️ Missing	No current-run comment
📝 Docs Sync	⚠️ Missing	No current-run comment
🧪 Test Coverage	⚠️ Missing	No current-run comment

Verdict: ⚠️ AI review incomplete; ready for human review

AI review comments are untrusted advisory output. The summary reports workflow-generated completion status only, not model-authored pass/fail claims.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/hasown	2.0.4	Unknown	Unknown
npm/qs	6.16.0	🟢 5.4	Details Check Score Reason Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Packaging ⚠️ -1 packaging workflow not detected Security-Policy 🟢 10 security policy file detected Code-Review ⚠️ 2 Found 7/30 approved changesets -- score normalized to 2 Binary-Artifacts 🟢 10 no binaries found in the repo Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Maintained 🟢 10 18 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10 Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 CII-Best-Practices 🟢 5 badge detected: Passing Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0
npm/side-channel	1.1.1	🟢 4.4	Details Check Score Reason Maintained 🟢 5 5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Packaging ⚠️ -1 packaging workflow not detected Binary-Artifacts 🟢 10 no binaries found in the repo Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 SAST ⚠️ 0 no SAST tool detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md Security-Policy 🟢 10 security policy file detected

Scanned Files

• agent-governance-python/agent-os/extensions/mcp-server/package-lock.json

[github-actions]

📦 Dependency diff (SBOM)

Comparing main → dependabot/npm_and_yarn/agent-governance-python/agent-os/extensions/mcp-server/qs-6.16.0.

✅ No dependency changes detected.

[Imran Siddique (imran-siddique)]

Posting a shared root cause here rather than a review of the bump, because this PR is red for reasons
that have nothing to do with qs, and the same is true across the whole Dependabot queue right now.

test (agent-os, 3.11/3.12/3.13) is a repo-wide break that started on 2026-09-02. It is not a
test failure. Collection never completes:

anyio/_core/_typedattr.py:10: in <module>
    from typing_extensions import sentinel
E   ImportError: cannot import name 'sentinel' from 'typing_extensions'.
    Did you mean: 'Sentinel'?

Anything importing fastapi.testclient hits it, because FastAPI imports anyio.abc.

Cause: a silent dependency downgrade, not an upstream bug. anyio 4.15.0 was published
2026-09-02 21:46 UTC and declares typing_extensions>=4.16.0, because lowercase sentinel only
exists from 4.16.0. But agent-governance-python/requirements/ci-test.txt line 20 hash-pins:

typing-extensions==4.15.0 \
    --hash=sha256:f0fa19c6845758ab08074a0cfa8b7aecb71c999ca73d62883bc25cc018c4e548

pip reports the conflict as a warning and exits 0, so the install "succeeds" with an anyio that
cannot import. The CI log carries the warning right above the failure:

ERROR: pip's dependency resolver does not currently take into account all the packages
that are installed. ... dependency conflicts.

Reproduced locally in a clean venv, byte-identical to CI:

typing_extensions 4.16.0 + anyio 4.15.0 -> from anyio.abc import ObjectReceiveStream -> OK
typing_extensions 4.15.0 + anyio 4.15.0 -> ImportError: cannot import name 'sentinel'

4.15.0 has Sentinel but not sentinel; 4.16.0 has both.

Fix: bump that one pin in ci-test.txt to typing-extensions==4.16.0 with its hashes. The
comment above it says it is there as a pytest-asyncio transitive for Python <3.13, and 4.16.0
satisfies that equally.

The second red check, Validate PR title, is also not this PR's fault and affects 39 of the 42 open
Dependabot PRs. The gate enforces subjectPattern: ^(?![A-Z]).+$ and Dependabot capitalises
Bump, so every PR it opens fails on arrival, which in turn keeps auto-merge red. #3710 is the
five-line fix and has been waiting three weeks on a missing DCO sign-off; I have commented there with
the numbers.

ci-complete is the aggregator reporting the two above, not a third problem.

So nothing here needs the bump author's attention. Two one-line fixes elsewhere clear the entire
Dependabot backlog.

[Imran Siddique (imran-siddique)]

MohammadHaroonAbuomar liamcrumm this is not about the qs bump, it is the repo-wide CI break I
diagnosed above and it needs one line from a maintainer.

anyio 4.15.0 shipped 2026-09-02 requiring typing_extensions>=4.16.0, but
agent-governance-python/requirements/ci-test.txt:20 hash-pins typing-extensions==4.15.0. pip
reports the conflict and exits 0, so every test module importing fastapi.testclient fails at
collection and test (agent-os, 3.11/3.12/3.13) is red across the board. Reproduced in a clean venv.

Bumping that pin to 4.16.0 with its hashes fixes every affected PR at once.