BAD CODE: 26 open Dependabot alerts on main, including a critical in node-tar

[flyingrobots]

Observation

gh api repos/flyingrobots/think/dependabot/alerts reports 26 open alerts on the default branch:

Severity	Count
critical	1
high	9
medium	16

Affected packages: fast-uri, hono, ip-address, tar, undici.

The critical and highs:

critical  tar          node-tar: Decompression/parse DoS via unlimited input
high      tar          node-tar: Negative tar entry size causes infinite loop in archive replace
high      fast-uri     host confusion via backslash authority introducer
high      fast-uri     host confusion via failed IDN canonicalization
high      fast-uri     host confusion via literal backslash authority delimiter
high      ip-address   Address4 decodes leading-zero octets as decimal while resolvers decode as octal (SSRF / trust-boundary bypass)

npm audit additionally reports a fixable advisory against @modelcontextprotocol/sdk, which is a direct dependency rather than transitive.

Why this matters here specifically

node-tar is not incidental to this repository. The git-cas fixture path extracts archives with tar — test/acceptance/repair-v17-mind.test.js and test/acceptance/readme-smoke-mind-fixture.test.js both restore a tarball and unpack it, and scripts/build-smoke-mind-fixture.mjs produces them. A decompression DoS in the library used to unpack fixture archives is squarely on a path this project exercises in CI.

ip-address SSRF-class bypasses matter because Think performs upstream reachability checks and pushes to a configured remote URL.

Every alert reports a fix as available, so this is upgrade work, not mitigation work.

Why it went unnoticed

Nothing in the repository surfaces this. Pushes print a Dependabot banner to stderr, which is easy to scroll past, and npm run lint and npm test are both silent about advisories. docs/method/backlog/bad-code/CORE_audit-no-dependency-freshness-cadence.md already records the absence of a freshness cadence; this issue is the concrete evidence of what that gap costs.

Suggested direction

• Resolve the critical and high alerts first; all have fixes published.
• Decide whether npm audit belongs in CI as a gate or a report. Given the repo's existing preference for ratchets over prose, an advisory-count ratchet would fit the established pattern and would not block on newly-disclosed advisories the way a hard gate does.
• Reconcile with BAD CODE: exact-pinned @git-stunts dependencies stop upstream fixes reaching Think #37: raising these versions interacts with the exact pins on @git-stunts/*, and with the pending plumbing/git-warp propagation.

References

• docs/method/backlog/bad-code/CORE_audit-no-dependency-freshness-cadence.md
• BAD CODE: exact-pinned @git-stunts dependencies stop upstream fixes reaching Think #37 — dependency pinning policy
• Existing Dependabot PR: chore(deps): bump fast-uri from 3.1.0 to 3.1.2 in the npm_and_yarn group across 1 directory #12 (fast-uri bump), open since before this audit

[coderabbitai]

🔗 Related PRs

#5 - [codex] Refresh CONTRIBUTING for METHOD [closed]
#15 - Runtime Truth ratchet and Think-on-Echo model seam [closed]
#24 - Add Think feature proposal docs [merged]
#30 - Agent-first README, MCP install tooling, and capture/test isolation fixes [open]
#31 - Capture followthrough policy and test-harness isolation [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!