Repository navigation
fix(eval): report false-positive rates alongside grading coverage - #131
Merged
elementalsouls merged 2 commits intoNov 16, 2026
Merged
elementalsouls merged 2 commits into
elementalsouls merged 2 commits into
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.
What does this change?
The false-positive summary counts empty or inconclusive responses in the denominator as if they were graded. With one false positive and one unanswered safe case it reports 50% FPR, although the one graded case was a false positive. A condition that frequently fails to return a verdict can appear safer.
Report rates over scored responses and print safe and vulnerable grading coverage beside each condition. An empty scored denominator is displayed as n/a.
Validation