Add security policy #3722
Closed
Add security policy #3722
Conversation
This file contains 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
Signed-off-by: Pedro Kaj Kjellerup Nacht <pnacht@google.com>
|
We will create the |
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.
Fixes #3721.
This PR adds a security policy to the project. As described in more detail in the linked issue, this eases the responsible reporting of vulnerabilities before they're publicized to the wider public.
The policy currently allows reporting either via email (currently a placeholder) or using GitHub's private reporting feature (which needs to be enabled in the project settings). Let me know which email (or website) to use or whether you'd rather just use GitHub's feature.
The policy also mentions a 90-day remediation timeline. This is pretty standard, but let me know if you'd rather change this or anything else!