fix: resolve js-yaml DoS vulnerability (Dependabot #67)

[sriramveeraghanta]

Summary

Resolves the one open Dependabot alert on the repository:

• [changes from master to self-hosted #67] js-yaml — Quadratic-complexity DoS in merge key handling via repeated aliases
  • Advisory: GHSA-h67p-54hq-rp68 (CVE-2026-53550), moderate severity
  • Vulnerable range: < 3.15.0; patched in 3.15.0
  • js-yaml is a transitive dev dependency pulled in by gray-matter@4.0.3 (used by VitePress for frontmatter parsing).

Change

Added a scoped pnpm override in pnpm-workspace.yaml that bumps only the vulnerable range:

overrides:
  js-yaml@<3.15.0: 3.15.0

gray-matter@4.0.3 accepts js-yaml@^3.13.1, so 3.15.0 is fully compatible. The lockfile now resolves js-yaml to 3.15.0 everywhere; the vulnerable 3.14.2 is gone.

Verification

• pnpm install — lockfile regenerated, js-yaml resolved to 3.15.0
• pnpm build — succeeds
• pnpm check:format — passes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jul 15, 2026 8:35pm

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 36 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: 42d9bc25-f670-4d6c-8bee-e0d3ea51cd5b

📥 Commits

Reviewing files that changed from the base of the PR and between 400af96 and 7363424.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• pnpm-workspace.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/js-yaml-dos-vulnerability

---

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