You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Severity table on the Essentials screen is becoming very hard to read with so much data repeated at a row level.
One idea is to add a separate column for each System - Score combination and/or creating System subsections.
Using https://public.vulnerablecode.io/vulnerabilities/VCID-29te-f3et-aaac as an example:
There are many pairs of numeric and text scores from the same origin (URL). Since the text score is effectively an alias in these cases it would be better to see the cvss.31 and generic_textual values in separate columns on a single row for that origin. This is an extremely common pattern
With the increase in cvss versions and other systems it might also makes sense to have separate sections for cvss vs. epss especially because these scores are not comparable.
For this particular VCID there are also 15 instances (14 duplicates) for the epss Score
The text was updated successfully, but these errors were encountered:
The Severity table on the Essentials screen is becoming very hard to read with so much data repeated at a row level.
One idea is to add a separate column for each System - Score combination and/or creating System subsections.
Using https://public.vulnerablecode.io/vulnerabilities/VCID-29te-f3et-aaac as an example:
For this particular VCID there are also 15 instances (14 duplicates) for the epss Score
The text was updated successfully, but these errors were encountered: