support/crate-report-form: Split security checkbox into malicious-code and vulnerability
#12043
+216
−61
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
Turbo87
added
C-enhancement ✨
|
Looks great on my side! |
|
Screenshots LGTM. Is it worth calling out "soundness" issues in the same category as vulnerabilities? |
|
Looks like a great improvement, thanks. |
|
Good idea!! |
cuviper
approved these changes
Oct 6, 2025
LawnGnome
approved these changes
Oct 6, 2025
|
thanks for the reviews everyone! :)
I'm not sure. I wouldn't want the contact form to become too verbose, I think. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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 better reflects our security policy, which treats these cases slightly different. With this PR, malicious code reports are also sent to [email protected] to improve response times. Clicking the vulnerability checkbox now shows an additional help text suggesting to the user to first contact the crate author, file a RustSec report and read our security policy.
/cc @rust-lang/security @rust-lang/wg-secure-code
Malicious Code
Vulnerability