deps: bump fast-uri from 3.1.0 to 3.1.2

[dependabot]

Bumps fast-uri from 3.1.0 to 3.1.2.

Release notes

Sourced from fast-uri's releases.

v3.1.2

⚠️ Security Release

• Fix for GHSA-v39h-62p7-jpjc

What's Changed

• Handle malformed fragment decoding as a parse error by @​mcollina in fastify/fast-uri#171

Full Changelog: fastify/fast-uri@v3.1.1...v3.1.2

v3.1.1

⚠️ Security Release

• Fix for GHSA-q3j6-qgpj-74h6

What's Changed

• build(deps-dev): bump tsd from 0.32.0 to 0.33.0 by @​dependabot[bot] in fastify/fast-uri#148
• build(deps): bump actions/checkout from 4 to 5 by @​dependabot[bot] in fastify/fast-uri#149
• chore(.npmrc): ignore scripts by @​Fdawgs in fastify/fast-uri#150
• build(deps-dev): remove @​fastify/pre-commit by @​Fdawgs in fastify/fast-uri#151
• build(deps): bump actions/setup-node from 4 to 5 by @​dependabot[bot] in fastify/fast-uri#152
• ci(ci): add concurrency config by @​Fdawgs in fastify/fast-uri#153
• build(deps): bump actions/setup-node from 5 to 6 by @​dependabot[bot] in fastify/fast-uri#154
• build(deps): bump actions/checkout from 5 to 6 by @​dependabot[bot] in fastify/fast-uri#156
• chore(license): standardise license notice by @​Fdawgs in fastify/fast-uri#159
• style: remove trailing whitespace by @​Fdawgs in fastify/fast-uri#161
• ci: remove unused github files by @​Tony133 in fastify/fast-uri#162
• chore: update readme by @​Tony133 in fastify/fast-uri#164
• build(deps): bump fastify/workflows/.github/workflows/plugins-ci-package-manager.yml from 5 to 6 by @​dependabot[bot] in fastify/fast-uri#165
• build(deps): bump fastify/workflows/.github/workflows/plugins-ci.yml from 5 to 6 by @​dependabot[bot] in fastify/fast-uri#166
• build(deps-dev): bump neostandard from 0.12.2 to 0.13.0 by @​dependabot[bot] in fastify/fast-uri#167
• ci: add lock-threads workflow by @​Fdawgs in fastify/fast-uri#169

New Contributors

• @​Tony133 made their first contribution in fastify/fast-uri#162

Full Changelog: fastify/fast-uri@v3.1.0...v3.1.1

Commits

• 919dd8e Bumped v3.1.2
• c65ba57 fixup: linting
• 6c86c17 Merge commit from fork
• a95158a Handle malformed fragment decoding without throwing (#171)
• cea547c Bumped v3.1.1
• 876ce79 Merge commit from fork
• dcdf690 ci: add lock-threads workflow (#169)
• c860e65 build(deps-dev): bump neostandard from 0.12.2 to 0.13.0 (#167)
• 9b4c6dc build(deps): bump fastify/workflows/.github/workflows/plugins-ci.yml (#166)
• 85d09a9 build(deps): bump fastify/workflows/.github/workflows/plugins-ci-package-mana...
• 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.

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[robotlearning123]

Backlog-loop verification: checks/tests green except pre-existing base failures (delta: Head (3352908) = origin/main (ce7da5b) + exactly 1 commit (git rev-list --count origin/main ^origin/dependabot/npm_and_yarn/fast-uri-3.1.2 = 0), and the only changed file is package-lock.json — so base-vs-head is an exact baseline comparison.
CODE GATES (meaured, identical both sides): npm ci exit 0 / npm test 57 pass 0 fail / e2e 9 pass 0 fail / lint 0 errors 1 warning / typecheck exit 0 / build exit 0 — base identical. No gate is worse at head.
FAILING CHECK claude-review: FAILURE at head; also FAILURE for every dependabot PR on the same base ref (29/29 dependabot PRs FAILURE; #70 same annotation 2026-05-23, different diff), and repo-wide 49/52 PRs that ran it are red (47 FAILURE + 2 FAILURE,FAILURE) vs only 3 SUCCESS (#22/#24/#25, human author). Base is not green on this gate either — it is a repo-baseline condition, not a PR regression.
SECURITY DELTA (the real change): fast-uri 3.1.0 (base lock) -> 3.1.2 (head lock). Open high-severity fast-uri alerts: 7/7 apply to base version 3.1.0; 5/7 apply to head version 3.1.2 => merge closes 2 (#86 GHSA-v39h-62p7-jpjc, #87 GHSA-q3j6-qgpj-74h6) and leaves 5 open (#93,#92 need >=3.1.6, #81 >=3.1.5, #73 >=3.1.4, #72 >=3.1.3). Min version closing all 7 = 3.1.6 (3.1.8 exists in 3.x, latest is 4.2.1). npm audit totals UNCHANGED: base {low:1,moderate:8,high:10,total:19} -> head identical; npm audit still lists fast-uri high "3.0.0 - 3.1.5" at head.
Incidental: head lock also repairs a stale root version (base lock 0.1.0 vs base package.json 0.2.0 -> head 0.2.0).). Independent review: REQUEST_CHANGES.
GROK REVIEW OF PR #65 (agent-next/agent-ready, head dependabot/npm_and_yarn/fast-uri-3.1.2 @ 3352908, base main) — grok 1.0.41, ran headless, exit 0, VERDICT: REQUEST_CHANGES

RAW REVIEWER OUTPUT (verbatim, findings section):
"VERDICT: REQUEST_CHANGES

1. package-lock.json:2318 — The indirect pin moves fast-uri from 3.1.0 to 3.1.2 (integrity matches the registry tarball), which is what the PR body claims for GHSA-q3j6-qgpj-74h6 and GHSA-v39h-62p7-jpjc. That pin is still vulnerable. GHSA-fph4-wmhf-6fwf (CVE-2026-75899, high) affects >=3.1.2 <3.1.6 and is an incomplete fix of the 3.1.2 authority-delimiter change, so this bump introduces it. 3.1.2 is also inside later ranges, including GHSA-v2hh-gcrm-f6hx (<=3.1.3) and GHSA-hrr3-gc8f-f4qj (>=3.0.0 <3.1.8). Both ajv copies still allow fast-uri ^3.0.1 (package-lock.json:875, package-lock.json:1375), and 3.1.8 satisfies that range. npm audit --package-lock-only on a lockfile resolved to 3.1.8 reports no fast-uri advisory; the same audit on this PR's tree reports fast-uri high. Retarget the single hoisted entry at package-lock.json:2318 to 3.1.8. The root 0.1.0 -> 0.2.0 lock metadata and the peer flag edits are what current npm rewrites alongside the bump, and no repo source imports fast-uri, so those are not separate defects."

PRIMARY VERIFICATION BY EXECUTION (each claim re-run by me; writer=devin/deepseek, reviewer=grok, verifier=this worker):

• Diff size/scope CONFIRMED: git diff --stat origin/main HEAD = package-lock.json | 19 ++++++------------- (6 insertions, 13 deletions), 1 file. git diff origin/main...HEAD and two-dot diff are identical, i.e. main's lockfile is byte-identical to the fork point (ce7da5b) except these 19 lines — no staleness regression other than the bump. Single commit 3352908 by dependabot[bot] (2026-05-09) contains the whole change.
• fast-uri entry CONFIRMED at package-lock.json:2318 = "version": "3.1.2"; integrity sha512-rVjf7ArG3LTk+FS6Yw81V1DLuZl1bRbNrev6Tmd/9RaroeeRRJhAt7jg/6YFxbvAQXUCavSoZhPPj6oOx+5KjQ== matches npm view fast-uri@3.1.2 dist.integrity exactly (no tampered tarball).
• Line citations CONFIRMED: package-lock.json:875 and :1375 both read "fast-uri": "^3.0.1" (the two ajv copies).
• "no repo source imports fast-uri" CONFIRMED: grep -rn "fast-uri" --include='*.ts' --include='*.js' --include='*.json' --include='*.mjs' . (excluding node_modules/package-lock.json) returns zero hits.
• AUDIT POWER DEMONSTRATION CONFIRMED (the negative result is not void): on this PR's lockfile, npm audit --package-lock-only (npm 10.9.4 / node v22.22.0) reports fast-uri: high | range 3.0.0 - 3.1.5, totals {low:1, moderate:8, high:10, total:19}; with fast-uri rewritten to 3.1.8 (integrity sha512-GZMtZUTNRpOVIECoXwLNZS5xUGE+mVNbTB8h/7Rwh2TFWcBQiPzTgyZi05BF9UMZKkLJv8XBRJTlU7zg8+ZfMg==) the fast-uri entry disappears and totals drop to {low:1, moderate:8, high:9, total:18}. Same check, both outcomes — the reviewer's remediation target is verified, not asserted.
• GHSA-fph4-wmhf-6fwf CONFIRMED REAL and CONFIRMED to newly apply: gh api /advisories/GHSA-fph4-wmhf-6fwf = CVE-2026-75899, severity high, "fast-uri vulnerable to server-side request forgery via repeated hostname percent-decoding", fast-uri range >= 3.1.2, < 3.1.6 -> patched 3.1.6. 3.1.0 is outside that range, 3.1.2 is inside it, so merging opens a new high alert (inference from the published range; the alert itself appears only post-merge).
• GHSA-v2hh-gcrm-f6hx range CONFIRMED: repo alert docs: carry forward #71 with complete baseline hook arguments #73 >= 3.0.0, <= 3.1.3, first patched 3.1.4.
• CORRECTION to the reviewer: grok's third advisory, GHSA-hrr3-gc8f-f4qj (>=3.0.0 <3.1.8), is NOT FOUND — gh api /advisories/GHSA-hrr3-gc8f-f4qj returns HTTP 404 and gh api "/advisories?ghsa_id=GHSA-hrr3-gc8f-f4qj" returns 0. No such repo alert exists either. Striking this one item; the finding stands on the verified items above. (Label: unverified / not found - gap.)
• ALERT CLOSURE CHECK (per repo notes): main (fast-uri 3.1.0) has 7 open fast-uri dependabot alerts — CODEOWNERS assigns all rules to @anthropics/agent-ready-maintainers — review gate is inert #87 (<=3.1.0, patched 3.1.1), dependabot watches only the root lockfile; 5 other package-lock.json files unmonitored #86 (<=3.1.1, patched 3.1.2), docs: align vision with v2 readiness checks #72 (<3.1.3, patched 3.1.3), docs: carry forward #71 with complete baseline hook arguments #73 (<=3.1.3, patched 3.1.4), docker-compose.yml invokes nonexistent 'scan' command; docker compose up exits 1 #81 (<3.1.5, patched 3.1.5), fix(fs): make expected ENOENT probes silent control flow #92 and fix(docker): run as non-root, prune dev deps, add .dockerignore #93 (<3.1.6, patched 3.1.6). Merging 3.1.2 closes only dependabot watches only the root lockfile; 5 other package-lock.json files unmonitored #86 and CODEOWNERS assigns all rules to @anthropics/agent-ready-maintainers — review gate is inert #87; docs: align vision with v2 readiness checks #72/docs: carry forward #71 with complete baseline hook arguments #73/docker-compose.yml invokes nonexistent 'scan' command; docker compose up exits 1 #81/fix(fs): make expected ENOENT probes silent control flow #92/fix(docker): run as non-root, prune dev deps, add .dockerignore #93 stay open and require up to 3.1.6. Latest fast-uri is 4.2.1; the 3.1.x line ends at 3.1.8 and ajv's ^3.0.1 permits it, so 3.1.8 is the correct in-range target. Repo-wide 72 open alerts total.
• RUNTIME vs DEV USAGE CHECK (per repo notes; corrects the note's premise): fast-uri is NOT dev-only. packages/mcp/package.json:35 lists "@modelcontextprotocol/sdk": "^1.11.0" under "dependencies", and the lock shows that SDK requiring ajv ^8.17.1 + ajv-formats ^3.0.1 (dev: false), both requiring fast-uri ^3.0.1. It reaches the shipped MCP scanner at runtime, which raises rather than lowers the severity.
• SCOPE CREEK, judged not a defect by the reviewer, confirmed as dependabot-generated: the same commit rewrites the lockfile root version 0.1.0 -> 0.2.0 (fork point's package.json already said 0.2.0 while its lock said 0.1.0, so this reduces drift) and toggles "peer": true on 8 packages (7 removals: express, zod, acorn, eslint, typescript, @eslint/eslintrc-era entries, etc.; 1 addition: hono). No package versions change besides fast-uri, so the installed tree is unaffected; worth naming in the PR but not a merge blocker.
• CI/merge state: gh pr view 65 --json statusCheckRollup shows 8 green checks (Check Repository, Lint & Format, Validate PR, Type Check, Scan Agent Readiness, Test 20.x, Test 22.x, Build) and claude-review FAILURE; mergeStateStatus = BLOCKED. The failure is the known actor-policy baseline, not code: check-run annotation reads "Action failed with error: Workflow initiated by non-human actor: dependabot (type: Bot). Add bot to allowed_bots list or use '*' to allow all bots." (.github:185, exit code 1). Changing allowed_bots is a repo-settings action outside this loop's scope — needs_owner for the merge gate.

RECOMMENDED ACTION (evidence-backed, not executed — this loop is review-only for a foreign head): do not merge PR #65 as-is; retarget the single hoisted entry at package-lock.json:2318 to fast-uri 3.1.8 (in-range for ajv ^3.0.1), which by execution removes fast-uri from npm audit and closes all 7 alerts including the one 3.1.2 would newly open; the claude-review actor-policy failure needs an owner decision before the PR can go green.

DEVIATIONS (logged, conservative option taken):

1. The task's "(head PR-head)" is an unsubstituted placeholder; the real head is dependabot/npm_and_yarn/fast-uri-3.1.2 (confirmed via gh pr view 65 --json headRefName,headRefOid = 3352908...). I pinned the review to that exact SHA rather than guessing; no other branch exists for this PR.
2. The prescribed worktree path /tmp/loop-wt-agent-next_agent-ready-pr65 did not exist (only other runs' worktrees were present, untouched). I ran git fetch origin --prune in /home/robot/workspace/agent-next/agent-ready and created the worktree fresh via git worktree add --detach <path> 3352908a... as the safety contract requires.
3. I added two clauses to the reviewer prompt: pin the concrete head SHA (placeholder) and "READ-ONLY review: do not modify, commit, or push anything" (grok ran with --always-approve inside a worktree of a shared repo). Review substance unchanged.
4. Grok ran once, exit 0, well inside the 540s bound — no retry and no reviewer-lane-unavailable fallback was needed.
5. No PR comment was posted: the STEPS 1-4 do not include one and the head is foreign (review-only). All mutation stayed inside my own /tmp worktree; the main tree is clean (git status --porcelain empty), HEAD still 8373df4, no loop/* branches created, no PR approved or merged.
6. Cleanup done and verified: git -C /home/robot/workspace/agent-next/agent-ready worktree remove /tmp/loop-wt-agent-next_agent-ready-pr65 --force succeeded, git worktree list shows only the repo's three pre-existing worktrees, my /tmp/pr65-audit scratch and captured logs are deleted; the two other /tmp loop-wt-* directories belong to other runs and were left alone.