Add security policy #1484
Merged
Add security policy #1484
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>
BillyDonahue
approved these changes
Apr 26, 2023
|
Please let me know if there's anything else I can do on this. If the other maintainers aren't interested, feel free to close! |
Closed
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 #1483.
This PR adds a security policy for JsonCpp.
After reading the conversation in #838, I wrote the policy to suggest the use of GitHub's private reporting feature (must be enabled in the project settings). Let me know if you'd rather use an email or external website (or both!).
The policy also suggests a 90-day remediation schedule, simply because it's pretty standard practice. If you'd rather change that (or anything else!), let me know.