chore(deps): resolve npm security advisories (consolidated)

[kzamanbd]

What

Single consolidated lockfile update that resolves the open Dependabot npm_and_yarn security PRs, instead of merging ~19 of them one-by-one (each rebases package-lock.json → serial conflicts).

Advisories: 49 → 28. Critical cleared; high 16 → 5.

Changes

• @wordpress/scripts 30 → 32.5.1 (dev). Clears the shell-quote critical plus a batch of build-tool highs (ws, serialize-javascript, @babel/core, minimatch, …).
• react-router-dom → ^7.18.1 (prod). Patches the shipped react-router advisory (Dependabot chore(deps): bump react-router and react-router-dom #98).
• overrides: @babel/runtime ^7.26.10 (fixes the copy pulled in via @emotion/styled that actually ships in dist/), serialize-javascript ^7.0.7.
• src/routing/index.tsx: type navigation as ReturnType<typeof useNavigation> — react-router 7.18 narrowed useNavigation()'s public return type (dropped matches/historyAction).

What ships in dist/

Production-only audit: 8 → 3 moderate, all with no upstream fix yet — @wordpress/components, @wedevs/plugin-ui (github dep, fix belongs in that repo), uuid (fix is a breaking major that would break CJS consumers).

The residual 28

Almost entirely dev/test tooling that never reaches users: lighthouse → @sentry/node → @opentelemetry/* (pulled by @wordpress/scripts' e2e utils), webpack-dev-server, markdownlint. No safe fix exists (npm only offers a bogus @wordpress/scripts downgrade), and forcing overrides there risks breaking the build for tooling with zero shipped exposure.

Verification

• npm run typecheck ✅
• npm run build ✅ (webpack 5.105.2, only pre-existing asset-size perf warnings)

Note

Once merged to develop, Dependabot re-evaluates and auto-closes the superseded npm_and_yarn PRs whose advisories are now resolved in the lockfile.

[coderabbitai]

Warning

Review limit reached

@kzamanbd, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 12 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 317a25ca-5eff-4bcc-8db0-9090c317a993

📥 Commits

Reviewing files that changed from the base of the PR and between 60273ad and bb48c85.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• package.json
• src/routing/index.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/deps-security-audit

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}