Explain CVE remediation for vendored dependencies#3228
Merged
Conversation
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
wiedenmeier
reviewed
Apr 10, 2026
wiedenmeier
reviewed
Apr 10, 2026
wiedenmeier
approved these changes
Apr 10, 2026
Member
wiedenmeier
left a comment
wiedenmeier
left a comment
There was a problem hiding this comment.
Looks good, just a few little nits
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
matthewhelmke
approved these changes
Apr 13, 2026
Collaborator
matthewhelmke
left a comment
matthewhelmke
left a comment
There was a problem hiding this comment.
That's very clear, thank you!
LGTM
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
3 participants
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.
[ ] Check if this is a typo or other quick fix and ignore the rest :)
Type of change
Update to library CVE remediations page
What should this PR do?
Clarify how CVE remediations work for Python packages when a CVE exists in a dependency of vendored code
Why are we making this change?
To prevent confusion if customers see +cgr.N versions of a package but no advisory in the VEX feed. Thread here.
What are the acceptance criteria?
Content should clearly explain how this works