Skip to content

fix: upgrade dependencies, patch cryptography CVE-2024-12345, and add…#414

Open
nikhildhamdhere15 wants to merge 1 commit into
sreerevanth:mainfrom
nikhildhamdhere15:feature/dependency-upgrade-cve-333
Open

fix: upgrade dependencies, patch cryptography CVE-2024-12345, and add…#414
nikhildhamdhere15 wants to merge 1 commit into
sreerevanth:mainfrom
nikhildhamdhere15:feature/dependency-upgrade-cve-333

Conversation

@nikhildhamdhere15

Copy link
Copy Markdown

This PR addresses the dependency maintenance and security requirements outlined in #333.

Changes Made:

  1. Dependency Upgrades (pyproject.toml): - Upgraded cryptography to >=43.0.1 to patch the medium-severity vulnerability (CVE-2024-12345).
    • Bumped backend core packages (fastapi, uvicorn, pydantic, redis, celery, httpx, rich) to their designated safe minor/patch versions.
  2. CI Automated Safety Check (.github/workflows/test-on-pr.yml):
    • Added an automated pip-audit step to the PR test pipeline to catch and block any high-severity security vulnerabilities moving forward.
  3. Documentation (CONTRIBUTING.md):
    • Appended a new section detailing the dependency management workflow and vulnerability auditing instructions for future contributors.

Closes #333

@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@nikhildhamdhere15, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 10 minutes and 52 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9b0f311c-d8ed-43ba-93f3-d6b4ec4a1cd7

📥 Commits

Reviewing files that changed from the base of the PR and between 19bbbeb and b6f08ae.

📒 Files selected for processing (3)
  • .github/workflows/test-on-pr.yml
  • CONTRIBUTING.md
  • pyproject.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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 and usage tips.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[DEPENDENCY] Upgrade packages and remediate cryptography CVE

2 participants