Skip to content
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

Set minimum reporting level of vuln scans to high. #342

Merged
merged 1 commit into from
Jan 16, 2025

Conversation

GROwen
Copy link
Contributor

@GROwen GROwen commented Jan 16, 2025

Motivation

During the weekly CVE scan review our priorities are constrained by time constraints. This means we focus on CVEs of high or greater.

As such we should only report on CVEs that we will action.

@GROwen GROwen added the NEEDS REVIEW Good for newcomers label Jan 16, 2025
@GROwen GROwen requested a review from nicksantamaria January 16, 2025 00:06
@GROwen GROwen self-assigned this Jan 16, 2025
@GROwen GROwen merged commit b3dacf8 into 6.x Jan 16, 2025
12 checks passed
@GROwen GROwen deleted the build/tune-scan-reporting-levels branch January 16, 2025 00:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NEEDS REVIEW Good for newcomers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants