Add security policy#335
Merged
Merged
Conversation
Avoids duplicating version support info that is already maintained in the wiki, reducing maintenance burden.
Contributor
Author
|
Should we mark 1.x as EOL in the version table because it requires PHP 5.6? (EOL'd 7 years, 4 months ago) |
This file contains hidden or 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
2 participants
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.
Summary
Add a security policy to document supported versions and the vulnerability reporting process.
Major Changes
.github/SECURITY.mdwithsupported version tablereference to version table in wiki and vulnerability reporting instructionsMinor Changes
None.
Backwards Compatibility Notes
No breaking changes. This is a documentation-only addition.
Work Remaining
None.
Test Plan
N/A - documentation only.