Display EPSS Score And Percentile In Vulnerability Page #832
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added the raw EPSS score and percentile numbers to the vulnerability details page, similar to the CVSS Exploit Score and other metrics Signed-off-by: Aravind Parappil <[email protected]>
Ran npm run prettier-fix Signed-off-by: Aravind Parappil <[email protected]>
Signed-off-by: Aravind Parappil <[email protected]>
This was referenced Apr 25, 2024
|
Note: This is the same PR as #789 that got accidentally closed while I was trying to fix conflicts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Adds the raw EPSS score and percentile numbers to the vulnerability details page, similar to the CVSS Exploit Score and other metrics.
Addressed Issue
Fixes #544
Additional Details
Initially thought of converting both the numbers into percentage by multiplying by 100 for readability (Would have to use .toFixed(2) to avoid JS floating point multiplication precision issue). But kept them as the raw number itself since that's how the EPSS data by FIRST is reported.
Checklist