Add Security Policy #160
Merged
Add Security Policy #160
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
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 #159
Here's a Security Policy suggestion!
The link for reporting vulnerabilities uses GitHub's Security Advisories report vulnerability feature, which is in beta. You would need to enable the feature in the repo for it to work.
How to enable Security Avisory
Another option is to report through an email, let me know if that works better. I've tried to keep the timelines for confirming vulnerability reports and fixing vulnerabilities as open as possible. Let me know what do you think and if this seems reasonable.