-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove cve field from Findings #9908
Conversation
Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.
Note 🔴 Risk threshold exceeded. Adding a reviewer if one is configured in notification list: @mtesauro @grendel513 Tip Get answers to your security questions. Add a comment in this PR starting with @DryRunSecurity. For example...
Powered by DryRun Security |
I will not fix Ruff Linter here as this is already covered here: #9903 |
DryRun Security SummaryThe pull request primarily focuses on refactoring the handling of vulnerability IDs (CVEs) in the application's data models, including the removal of the automatic setting of the Expand for full summarySummary: The code changes in this pull request are primarily focused on refactoring the handling of vulnerability IDs (CVEs) in the application's data models. The key changes include the removal of the automatic setting of the From an application security perspective, the removal of the automatic Additionally, the removal of the Files Changed:
Code AnalysisWe ran
Riskiness🔴 Risk threshold exceeded. We've notified @mtesauro, @grendel513. |
5d6c19c
to
4688037
Compare
@Maffooch, can you guide me here? |
|
@manuel-sommer I am a little nervous for this change to be processed at the moment. I am closing for now, and we can revisit in the future |
@Maffooch 👍 |
This PR removes cve field as all cves were migrated to unsaved_vulnerability_ids. See #9791 (review)