Fix open Dependabot/Aikido dependency alerts

[yosriady]

Summary

Clears every open Dependabot alert (37) plus the Aikido fast-uri finding for this repo.

Root workspace (pnpm-workspace.yaml overrides): brace-expansion → ^5.0.8, js-yaml 3.x → ≥3.15.0, @babel/core → ≥7.29.6 <8 (capped to avoid the freshly-released 8.x major).

.deepsec scanning workspace (scanner tooling, not shipped): deepsec bumped to ^2.2.9 and overrides added for fast-uri (≥3.1.4, CVE-2026-16221 — the Aikido finding), hono ≥4.12.27, @hono/node-server ≥2.0.5, undici ≥7.28.0 <8, tar ≥7.5.21 (incl. critical CVE-2026-59873), qs ≥6.15.2, body-parser ≥2.3.0, brace-expansion ≥5.0.8.

Notes: undici is capped <8 to stay on the requested major; @hono/node-server takes the 1.x→2.x major the advisory requires — it's internal to the deepsec scanner only.

Verification

• ✅ pnpm test 34/34 (integration suite is env-gated as designed)
• ✅ pnpm build (CJS + ESM) and pnpm lint clean
• ✅ Lockfiles grep-verified: js-yaml 3.15.0, brace-expansion 5.0.8/5.0.9, @babel/core 7.29.7, fast-uri 3.1.5, hono 4.12.34, undici 7.29.0, tar 7.5.22, qs 6.15.3, body-parser 2.3.0, @hono/node-server 2.0.12
• ✅ All resolved versions ≥7 days old (minimumReleaseAge respected)

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	deepsec@​2.2.9

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @protobufjs/float is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: .deepsec/pnpm-lock.yaml → npm/deepsec@2.2.9 → npm/@protobufjs/float@1.0.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@protobufjs/float@1.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm highlight.js is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: .deepsec/pnpm-lock.yaml → npm/deepsec@2.2.9 → npm/highlight.js@10.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/highlight.js@10.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm typebox is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: .deepsec/pnpm-lock.yaml → npm/deepsec@2.2.9 → npm/typebox@1.1.38 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typebox@1.1.38. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 222a33b812

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Raise the scanner workspace's Node requirement

When .deepsec is installed with Node 22.14 (the version used throughout this repository's workflows), this upgrade pulls @earendil-works/pi-coding-agent@0.81.1 and related packages, all of which declare node >=22.19.0 in the new lockfile. An engine-strict installation therefore fails, while a non-strict installation leaves the documented scanner commands running on an unsupported runtime; declare/document Node >=22.19 for this workspace or retain a compatible Deepsec version.

Useful? React with 👍 / 👎.

[yosriady]

Fixed in c936a21: .deepsec/package.json now declares engines.node: >=22.19.0, so engine-strict installs fail fast on older runtimes instead of leaving the scanner on an unsupported Node.

[chatgpt-codex-connector]

Cap security overrides at their patched majors

When this lockfile is next regenerated, these open-ended overrides can force future incompatible majors such as Hono 5, @hono/node-server 3, tar 8, or qs 7 even when their consumers request the current majors, because pnpm overrides replace the consumers' version ranges. The frozen lockfile masks this for now, but a routine dependency update can therefore break the scanner; add upper bounds as already done for fast-uri and undici.

Useful? React with 👍 / 👎.

[yosriady]

Fixed in c936a21: every override is now capped at its patched major (hono <5, @hono/node-server <3, tar <8, qs <7, body-parser <3, brace-expansion <6), and the overrides are duplicated into .deepsec/pnpm-workspace.yaml so both pnpm 9 (package.json#pnpm) and pnpm >=10 (workspace file) apply them on a future regeneration. Also force zod >=4.4.0 <5 there (@vercel/sandbox pinned the flagged 3.24.4 exactly); deepsec 2.2.9 CLI verified booting after the change.