Merged
Conversation
alex
reviewed
Mar 17, 2023
Contributor
Author
|
Another option is to use the github advisories to receive vulnerabilities reports, if you rather I can update the doc to mention it instead of emailing. But it need to be enabled and it is in beta yet. |
alex
approved these changes
Mar 20, 2023
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.
Changes
Closes #221
It needs yet a security email to gather possible vulnerabilities reports.
I've proposed this vulnerability disclosure timeline but let me know if you are more confortable with a different one.
PS: the Security Advisory is a github tool to Vulnerabilities Disclosures (I've seen you've already familiar with it).
Besides that feel free to edit or suggest any changes to this document, it is supposed to reflect the amount of effort the team can offer to handle vulnerabilities.