Merged
Conversation
To draw attention to the enabled "private vulnerability reporting" feature. Because unlike the SECURITY.md file which is prominently shown in a few places in the GitHub UI, the "private vulnerability reporting" feature can be difficult to find in case users are not aware that it exists.
Owner
|
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
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.
Resolves #199
To draw attention to the enabled "private vulnerability reporting" feature. Because unlike the SECURITY.md file which is prominently shown in a few places in the GitHub UI, the "private vulnerability reporting" feature can be difficult to find in case users are not aware that it exists.
Here are a few places where this SECURITY.md is shown:
Feel free to adjust the policy file as you like though, for example:
(maybe that is only needed if you get a lot of bogus reports)