Add a security policy #269
Closed
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 <[email protected]>
|
Hey, let me know if this is something you're interested in. Otherwise, feel free to close! |
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 #268.
As described in the issue, this PR adds a security policy for the project to let people know how to responsibly report any vulnerabilities they might find.
Currently the policy suggests either an email or using GH's private reporting feature. I couldn't find an appropriate email, so I've left a placeholder for now.
The policy also has a 90-day timeline to remediate any vulnerabilities, which is pretty common.
If you want to make any changes (to the email/website or just use the private report or change the timeline, for example), let me know and I'll happily change the PR.