Skip to content

fix: resolve JS-YAML DoS vulnerability#95

Merged
guy-shahine merged 2 commits into
mainfrom
fix/js-yaml-vulnerability
Jul 21, 2026
Merged

fix: resolve JS-YAML DoS vulnerability#95
guy-shahine merged 2 commits into
mainfrom
fix/js-yaml-vulnerability

Conversation

@guy-shahine

Copy link
Copy Markdown
Member

Summary

Update js-yaml from 3.15.0 to 5.2.0 to address Dependabot alert #86.

Resolves quadratic-complexity DoS vulnerability in merge key handling via repeated aliases.

Test plan

- Update js-yaml from 3.15.0 to 5.2.0 (addresses Dependabot alert #86)
- Resolves quadratic-complexity DoS in merge key handling via repeated aliases

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 46 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e07b0c6a-c323-4faa-8e9a-8a7a27356a39

📥 Commits

Reviewing files that changed from the base of the PR and between 64034c5 and 3aaf727.

⛔ 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/js-yaml-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

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

@guy-shahine
guy-shahine merged commit e08cfe0 into main Jul 21, 2026
9 checks passed
@guy-shahine
guy-shahine deleted the fix/js-yaml-vulnerability branch July 21, 2026 21:57
@akadenia-bot

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.6.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

4 participants