Report vulnerabilities upstream first#2692
Merged
djc merged 2 commits intorustsec:mainfrom Apr 8, 2026
Merged
Conversation
amousset
reviewed
Mar 4, 2026
amousset
approved these changes
Mar 4, 2026
LawnGnome
approved these changes
Mar 11, 2026
djc
approved these changes
Mar 12, 2026
Member
fintelia
force-pushed
the
upstream-first
branch
from
e773780 to
6cb3f0b
Compare
Contributor
Author
|
Fixed the merge conflict |
Member
|
Thanks! |
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
4 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.
This clarifies the guidance that vulnerabilities should be reported to upstream crates rather than directly to the RustSec advisory-db.
More context: #2662 (comment)