Repository navigation
docs: add a security policy - #5157
Merged
Merged
Conversation
Point reporters to GitHub's private vulnerability reporting and list the versions that get security fixes.
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
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.
Motivation
The repo has no security policy. Private vulnerability reporting is already on, so this adds a
SECURITY.mdthat points reporters to it and lists the versions that get security fixes: the 6.x line onmainand the latest 5.x release.Related issue
None.
Screenshots / Videos
Rendered
SECURITY.md:Test plan
SECURITY.mdin this PR's Files view with the rich diff and check the table and the link.