Repository navigation
Add security issue reporting guidelines - #57
Conversation
Added a section for reporting security issues and provided a link to the WordPress HackerOne program.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
|
saarnilauri
left a comment
saarnilauri
left a comment
There was a problem hiding this comment.
Thanks @jeffpaul Before we add this, a clarifying question: does the plugin exists as component in the HackerOne?
saarnilauri
left a comment
saarnilauri
left a comment
There was a problem hiding this comment.
Even we are not sure that the plugin exists as component in the HackerOne, we can merge this as the component part in the H1 report is not a blocker.
So I am merging this, as I have done so for the sibling plugins.
This pull request adds a new section to the
SECURITY.mdfile to provide clear instructions for reporting security issues. The update ensures contributors know how to responsibly disclose vulnerabilities.Security documentation:
SECURITY.md, including a link to the WordPress HackerOne program for responsible disclosure.