chore(deps): move the fast-uri floor to 3.1.6 for four more advisories - #9
Conversation
`Security Audit` is red on `main`, and on every open PR with it: four advisories landed in the same parser after the last bump — GHSA-5jgf-p345-68v8, GHSA-f65p-4m7j-42xc, GHSA-fph4-wmhf-6fwf and GHSA-jqff-g426-hqxp, all ReDoS or parsing confusion in fast-uri below 3.1.6. The existing entry's floor moves rather than a second one being added: two overlapping ranges for one package is how a floor stops applying without anybody noticing. Same path as before — `@commitlint/cli` > `ajv`, dev tooling only — and 3.1.6 published 2026-08-23, well past `minimumReleaseAge`. Claude-Session: https://claude.ai/code/session_01GGixjxi5AQ2cNK62bBymfF
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 4 remain after this review. 📝 WalkthroughWalkthroughThe workspace raises the transitive ChangesDependency security update
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized dependency-floor and lockfile update addresses the reported fast-uri advisories, with the supplied audit and validation checks passing. No actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
🟢 Approval recommended
The override and lockfile changes consistently remove fast-uri@3.1.5 and enforce 3.1.6 without introducing functional code changes.
Pull request overview
This PR updates the pnpm override “floor” for fast-uri to ensure transitive dev-tooling consumers (via @commitlint/cli → ajv) cannot resolve vulnerable versions affected by newly published advisories.
Changes:
- Raise the
fast-urioverride range from<3.1.5to<3.1.6, pinning resolutions to3.1.6. - Regenerate/update
pnpm-lock.yamlto reflectfast-uri@3.1.6in both package entries andajv’s resolved dependency snapshot.
File summaries
| File | Description |
|---|---|
| pnpm-workspace.yaml | Moves the fast-uri override floor to <3.1.6 and updates the advisory context comment. |
| pnpm-lock.yaml | Updates the lockfile override and resolved dependency graph to use fast-uri@3.1.6. |
Review details
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
- Files reviewed: 1/2 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Security Auditis red onmainhere — and therefore on #8 and anything else open — with four advisories published into the same parser since the last bump:fast-uribelow 3.1.6.Same path this override already existed for:
@commitlint/cli→ajv, dev tooling only.The existing entry's floor moves rather than a second entry being added — two overlapping ranges for one package is how a floor stops applying without anybody noticing (in the sibling repo I tried the second-entry form first and pnpm resolved the older pin, still vulnerable).
3.1.6published 2026-08-23, so it clearsminimumReleaseAge: 10080comfortably.pnpm audit --audit-level=high→ No known vulnerabilities found;node scripts/validate.mjsgreen.Merging this unblocks #8.
https://claude.ai/code/session_01GGixjxi5AQ2cNK62bBymfF
Summary by CodeRabbit