Repository navigation
Standardise the security policy and move it to .github - #165
Merged
Merged
Conversation
Every VIP-maintained plugin now carries the same policy, routing reports to HackerOne and pointing reporters to the bounty eligibility rules first, so this replaces the plugin-specific wording. The file moves to .github/, which GitHub reads just as it does the root and which is already excluded from release archives and WordPress.org. The SECURITY.md exclusion in .distignore is no longer needed. The README and CONTRIBUTING links follow it; the README uses GitHub's security policy URL, which resolves wherever the file lives.
GaryJones
force-pushed
the
GaryJones/security-policy
branch
from
October 9, 2026 07:24
c17808e to
2f353f1
Compare
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
1 participant
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.
Automattic handles vulnerability reports through its HackerOne programme. This repo already had a root
SECURITY.md, but its wording was its own, and the VIP plugins now share a single policy so researchers get the same guidance whichever repo they land on.This replaces the file with the shared wording (report through HackerOne rather than public issues or pull requests, and read the bounty eligibility guidelines first) and moves it to
.github/SECURITY.md. GitHub reads it there just as it does from the root, and that folder is already excluded from release archives and WordPress.org, so theSECURITY.mdline in.distignoreis no longer needed.The README and CONTRIBUTING links follow the file. The README links to GitHub's
/security/policyURL, which resolves wherever the file lives and works onmainbefore this reaches a release.