Classify packages as internal vs external#5
Merged
Merged
Conversation
4 tasks
Adds a --internal <PATTERN> option that classifies packages by name so the report groups results into "Internal — fixable at source" and "External — must wait or override". Lets you triage who-fixes-what during a CVE sweep. Patterns without wildcards act as prefixes (e.g. UiPath matches UiPath and UiPath.Foo); patterns with * or ? are globs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
--internal <PATTERN>so the report groups results into "Internal — fixable at source (open a PR upstream)" and "External — must wait or override". Useful for triaging who-fixes-what during a CVE sweep..separator (soAcmematchesAcmeandAcme.Foo); a pattern containing*or?is treated as a glob over the full package name. All matching is case-insensitive.--internalcomposes with--vulnerable(severity columns) and CPM-aware reporting.Example
Test plan
--internal Autofacon the solution), glob match (--internal Newt*on the solution), and no-match (--internal Acme.*against Baz, falls entirely into External).snitch <solution>with and without--internaland confirm the grouped output renders the way you want.🤖 Generated with Claude Code