Update vulnerability severity color scheme for improved visual hierarchy #848
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.
The vulnerability display used inconsistent colors that didn't provide clear visual distinction between severity levels (critical and high were both red variants, medium was yellow, low was green).
Changes
Updated color mappings in
secator/output_types/vulnerability.py:This creates a clearer gradient from red (critical) through orange tones (high/medium) to cyan (low), making severity levels immediately distinguishable in terminal output and reports.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.