Show ml_score in the frontend findings list#149
Merged
Conversation
This file contains hidden or 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
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.
Linked issue
Closes #36
What this PR does
successfully surfaced the ranker's ML score next to severity badges in the Findings view, added sample data for visual testing, persisted the ML score in the SQLite database backend, and added a sorting toggle.
Type of change
ML tier (if applicable)
Stack affected
Changes
Backend
Added the ml_score column to the findings table in the database and handled automatic migrations. Updated scan tasks to insert the score and endpoints to retrieve it.
Frontend
Mapped ml_score from backend findings to frontend findings. Added mock scores to sample data to make visual testing instant.
New dependencies
NA
Database / schema changes
NA
Testing
How did you test this?
Backend tests were successfully run and passed.
Frontend production build compiled and completed successfully.
Checklist
console.erroror unhandled Python exceptions introducedrequirements.txt/package.jsonupdated if new dependencies added.pkl,.pt, etc.) are gitignored, not committedAnything reviewers should focus on
NA
Screenshots (if UI changed)
NA