Add SECURITY.md file - #2766
Merged
Merged
Conversation
The other day, Rodrigo and me noticed that WPCS does not have a published security policy (via a `SECURITY.md` file). This commit intends to add such a file, which should help inform security researchers how to disclose any findings they may have. The file is placed in the `.github` directory. This will allow for it to be recognized correctly by GitHub, while not cluttering up the project root directory. Ref: https://docs.github.com/en/code-security/how-tos/report-and-fix-vulnerabilities/configure-vulnerability-reporting/add-security-policy
Member
Author
|
@dd32 As you seem to have an opinion about policy files in this repo, want to check through the text of this one before it is added ? |
dingo-d
requested changes
Jul 17, 2026
dingo-d
left a comment
dingo-d
left a comment
Member
There was a problem hiding this comment.
One small fix that affected the rendering
Co-authored-by: Denis Žoljom <dingo-d@users.noreply.github.com>
dingo-d
approved these changes
Jul 17, 2026
GaryJones
approved these changes
Jul 20, 2026
lesterchan
pushed a commit
to lesterchan/WordPress-Coding-Standards
that referenced
this pull request
Aug 9, 2026
* Add `SECURITY.md` file The other day, Rodrigo and me noticed that WPCS does not have a published security policy (via a `SECURITY.md` file). This commit intends to add such a file, which should help inform security researchers how to disclose any findings they may have. The file is placed in the `.github` directory. This will allow for it to be recognized correctly by GitHub, while not cluttering up the project root directory. Ref: https://docs.github.com/en/code-security/how-tos/report-and-fix-vulnerabilities/configure-vulnerability-reporting/add-security-policy --------- Co-authored-by: jrfnl <jrfnl@users.noreply.github.com> Co-authored-by: Denis Žoljom <dingo-d@users.noreply.github.com>
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
3 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.
Description
The other day, Rodrigo and me noticed that WPCS does not have a published security policy (via a
SECURITY.mdfile).This commit intends to add such a file, which should help inform security researchers how to disclose any findings they may have.
The file is placed in the
.githubdirectory. This will allow for it to be recognized correctly by GitHub, while not cluttering up the project root directory.Ref: https://docs.github.com/en/code-security/how-tos/report-and-fix-vulnerabilities/configure-vulnerability-reporting/add-security-policy
Suggested changelog entry
N/A
Notes
I have checked the following pages to confirm that WPCS is not covered under HackerOne:
The text is in part inspired by a similar policy for the Requests library, which I previously wrote (so there are no copyright issues).