Add SECURITY.md#883
Merged
Merged
Conversation
58 tasks
Member
Author
|
This is failing for the reasons described in #885 I expect that those are unrelated to the changes in this PR though, so this is ready for review. |
gforsyth
approved these changes
May 29, 2026
Contributor
|
Admin merging as failures are unrelated |
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
2 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.
Description
Contributes to rapidsai/build-planning#281
SECURITY.mddescribing how to report security vulnerabilitiesNotes for Reviewers
Why not just set this org-wide?
An org-wide default is set at https://github.com/rapidsai/.github/blob/main/SECURITY.md, but adding an actual file in each repo offers a few benefits:
This can be admin-merged
I'll stop CI intentionally after
pre-commitruns, to save CI time and resources.