fix(security): patch vulnerable transitive deps via pnpm overrides

[ayoub3bidi]

Contribution workflow

• Base branch is develop: This PR targets develop, not main.
• Guidelines and docs: I have read CONTRIBUTING.md and the docs relevant to my change.
• This template: I kept the PR template structure and filled in the sections below.

Description

Patch 7 open code-scanning security vulnerabilities in transitive devDependencies by adding pnpm overrides to force patched versions. All affected packages are dev-only (eslint, vitest, wrangler toolchain) and do not ship to the production client bundle.

Type of Change

• 🔧 Chore (maintenance, dependencies, etc.)

Related Issues

Closes code-scanning alerts #1–#8 (7 open, 1 already fixed).

Changes Made

• Added pnpm overrides in package.json for 5 vulnerable transitive dependencies
• Regenerated pnpm-lock.yaml with patched versions

Override Details

Package	Vulnerable	Fixed	CVE	Severity
minimatch	3.1.2	3.1.5	CVE-2026-26996, CVE-2026-27904	High
minimatch	9.0.5	9.0.9	CVE-2026-26996, CVE-2026-27904	High
semver	7.7.2	7.8.5	CVE-2026-3672	High
flatted	3.3.3	3.4.3	CVE-2026-32141	High
ajv	6.12.6	6.15.0	CVE-2025-69873	Medium

Testing

• All existing tests pass (pnpm test:run) — 1907 tests, 165 files
• ESLint passes (pnpm lint)
• Prettier formatting applied (pnpm format:check)
• Production build succeeds (pnpm build)

Breaking Changes

• None

Checklist

• I have completed the Contribution workflow checklist at the top of this template
• My code follows the project's style guidelines
• I have performed a self-review of my code
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes

Additional Notes

• All overrides are scoped to major version selectors (@3, @9, @6, @7) so they only affect the vulnerable major lines
• The dompurify alert (Redesign algorithms dropdown #5) was already fixed in a prior commit — no action needed
• Once parent packages (eslint, vitest, etc.) update their dependency ranges, these overrides can be removed

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 8 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 Plus

Run ID: 9bce389a-3a4c-401c-a9e2-269ff1e253a7

📥 Commits

Reviewing files that changed from the base of the PR and between 9fd279c and bf00d10.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/security-dependency-vulns

---

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.}

[github-actions]

Preview for Bayan Flow Staging ready!

Name	Link
🔨 Latest commit	bf00d10
🔍 Latest deploy log	https://github.com/ayoub3bidi/bayan-flow/actions/runs/30164158132
😎 Deploy Preview	https://pr-212-bayan-flow-staging.ayoub3bidi.workers.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

Preview alias pr-212 on the staging worker. Updates automatically with new commits.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[ayoub3bidi]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.