Add SECURITY.md to document security policy #754
Merged
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
This commit adds a SECURITY.md file to the repository to document the security policy. I recently enabled the private security advisories feature on the repository (which is a relatively new "beta" feature in github). Since we now have a place to privately raise potential security issues (besides email) it is good to have a documented policy on how security vulnerabilities should be reported and our support policy for version we will fix (which is just the latest release). As the project matures we can adjust this policy as needed (likely to support more than one version at a time).
IvanIsCoding
approved these changes
Nov 30, 2022
Pull Request Test Coverage Report for Build 3593219435
💛 - Coveralls |
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.
This commit adds a SECURITY.md file to the repository to document the security policy. I recently enabled the private security advisories feature on the repository (which is a relatively new "beta" feature in github). Since we now have a place to privately raise potential security issues (besides email) it is good to have a documented policy on how security vulnerabilities should be reported and our support policy for version we will fix (which is just the latest release). As the project matures we can adjust this policy as needed (likely to support more than one version at a time).