Add security policy #3344
Merged
Add security policy #3344
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>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #3344 +/- ##
=======================================
Coverage 98.38% 98.38%
=======================================
Files 77 77
Lines 24951 24951
=======================================
Hits 24548 24548
Misses 403 403 |
|
I've enabled the private security report feature on the seaborn repo and think I'd prefer that to be the only official route. I don't actually check my "public" email address all that often as it catches a lot of spam. |
Signed-off-by: Pedro Kaj Kjellerup Nacht <pnacht@google.com>
|
Updated. |
|
Thanks @pnacht |
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 #3343.
As described in the issue, this PR adds a security policy for seaborn.
The policy currently uses an email I found in the pyproject.toml file. It also suggests using GitHub's private reporting feature (must be enabled in the project settings). Let me know if you'd rather use just one means of reporting and/or change the email.
The policy also contains a 90-day remediation timeline, which I adopted because it's pretty common. But let me know if you'd rather change that (or anything else!).