Improve CodeScanning top 10 report to use better severities #79
+90
−45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes changes to improve the handling and comparison of alert severities in the
CodeScanning
feature. The most important changes include modifying the severity level handling in thesummaryTop10
method and refactoring the severity comparison logic inAlertMetrics
.Enhancements to
CodeScanning
class:Weakness
to the attributes list in theCodeScanning
class to include CWE information in the output.cweFromTags
method to extract CWE information from alert tags, improving the clarity and detail of the alert summaries.summaryTop10
method to include CWE information and improve the formatting of file paths in the output.Improvements to
AlertMetrics
utility:getAlertSeverity
function to centralize and simplify the logic for determining the severity of different types of alerts.compareAlertSeverity
function to use the newgetAlertSeverity
function, improving code readability and maintainability.Before:
After: