Repository navigation
fix: adjudicate AI vulnerability claims and eligible inputs - #19
8000Merged
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.
Scope
Adjudicate the existing AI-vulnerability catalogue rather than promote disputed, wrong-product, placeholder or unresolved rows. Preserve optional fix versions, ecosystem/version boundaries and meaningful reference/severity behavior. Count eligible package inputs independently of emitted findings.
Six reviewed paths only: scanner, CLI, their behavior regressions, changelog and existing audit note. Earlier local secrets workflow/allowlist are excluded and preserved. No version bump, package/release/tag, source acquisition or runner activation.
Evidence