Add Security Policy #187
Merged
Add Security Policy #187
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: Gabriela Gutierrez <gabigutierrez@google.com>
|
Thanks! |
|
No problem! Don't forget to enable the private reporting:
|
|
On Mon, Aug 28, 2023 at 07:12:41AM -0700, Gabriela Gutierrez wrote:
No problem! Don't forget to enable the private reporting:
1. Open the repo's settings
2. Click on Code security & analysis
3. Click "Enable" for "Private vulnerability reporting"
Done thanks
|
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 #174
Hi there! If you like to consider this change, here's a Security Policy suggestion.
Please not that the link for reporting vulnerabilities uses the private vulnerability reporting GitHub feature. You would need to enable the feature in the repo for the reports to start working. If you prefer an email for reporting, I can update the PR. If you decide to use the private vulnerability reporting, you can enable it following the instructions here.
I've tried to keep the timelines of confirming a vulnerability report and fixing a vulnerability as open as possible. Let me know what you think and if this seems reasonable for maintainance.