tstokes8040

This plugin creates a security.txt file in the WordPress installation root.
You can edit/add to this file within the WordPress SecurityTXT settings page.
The purpose of the security.txt file is to allow users to properly disclose security vulnerabilities or bugs to you.
The <a href="https://securitytxt.org/" rel="nofollow ugc">security.txt</a> file is currently a draft “standard”. This file is similar to the robots.txt file but for security. Large companies have already started to adopt this standard including Google, Facebook, GitHub, just to name a few.
We welcome development to make this plugin even better! Create your <a href="https://github.com/tstokes8040/security-txt" rel="nofollow ugc">pull request</a> or <a href="https://github.com/tstokes8040/security-txt" rel="nofollow ugc">submit a bug here</a>.

security-txt

A plugin for serving 'security.txt' in WordPress 6.1.1+.

securitytext.org

The purpose of this project is to create a set-it-and-forget-it plugin that can be installed without much effort to get a WordPress site compliant with the current <a href="https://securitytxt.org/" rel="nofollow ugc"><code>security.txt</code></a> spec. It is therefore highly opinionated but built for configuration. It will automatically configure itself but you are encouraged to visit the plugin settings page after activating it.
<a href="https://github.com/securitytxt" rel="nofollow ugc"><code>security.txt</code></a> is a <a href="https://tools.ietf.org/html/draft-foudil-securitytxt-00" rel="nofollow ugc">draft</a> “standard” which allows websites to define security policies. This “standard” sets clear guidelines for security researchers on how to report security issues, and allows bug bounty programs to define a scope. Security.txt is the equivalent of <code>robots.txt</code>, but for security issues.
There is a help page built into the plugin if you need help configuring it. For developers, there is <a href="https://austinheap.github.io/wordpress-security-txt/" rel="nofollow ugc">documentation for <code>wordpress-security-txt</code> online</a>, the source of which is in the <a href="https://github.com/austinheap/wordpress-security-txt/tree/master/docs" rel="nofollow ugc"><code>docs/</code></a> directory. The most logical place to start are the <a href="https://austinheap.github.io/wordpress-security-txt/packages/WordPress.Security.Txt.html" rel="nofollow ugc">docs for the <code>WordPress_Security_Txt</code> class</a>.
<h3>Translations</h3>
The <code>security.txt</code> for WordPress plugin includes translations for the following 17 languages:
<ul>
<li>Arabic (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-ar_AR.po" rel="nofollow ugc">PO file</a>)</li>
<li>Bengali (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-bn_BN.po" rel="nofollow ugc">PO file</a>)</li>
<li>Catalan (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-ca_ES.po" rel="nofollow ugc">PO file</a>)</li>
<li>Chinese (Simplified) (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-zh_CN.po" rel="nofollow ugc">PO file</a>)</li>
<li>Chinese (Traditional) (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-zh_TW.po" rel="nofollow ugc">PO file</a>)</li>
<li>English (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-en_EN.po" rel="nofollow ugc">PO file</a>)</li>
<li>English (AU) (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-en_AU.po" rel="nofollow ugc">PO file</a>)</li>
<li>English (US) (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-en_US.po" rel="nofollow ugc">PO file</a>)</li>
<li>French (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-fr_FR.po" rel="nofollow ugc">PO file</a>)</li>
<li>German (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-de_DE.po" rel="nofollow ugc">PO file</a>)</li>
<li>Hindi (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-hi_IN.po" rel="nofollow ugc">PO file</a>)</li>
<li>Italian (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-it_IT.po" rel="nofollow ugc">PO file</a>)</li>
<li>Portuguese (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-pt_PT.po" rel="nofollow ugc">PO file</a>)</li>
<li>Portuguese (BR) (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-pt_BR.po" rel="nofollow ugc">PO file</a>)</li>
<li>Romanian (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-ro_RO.po" rel="nofollow ugc">PO file</a>)</li>
<li>Russian (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-ru_RU.po" rel="nofollow ugc">PO file</a>)</li>
<li>Spanish (<a href="https://github.com/austinheap/wordpress-security-txt-translations/blob/master/wordpress-security-txt-es_ES.po" rel="nofollow ugc">PO file</a>)</li>
</ul>
If you would like to contribute a new languge or you spotted in error in one of the translation files, please feel free to contribute directly to the <a href="https://poeditor.com/join/project/utTvBn327C" rel="nofollow ugc">public <code>wordpress-security-txt</code> POEditor project</a>. Once accepted additions/modifications are automagically built by POEditor to PO/MO files and published to the <a href="https://github.com/austinheap/wordpress-security-txt-translations" rel="nofollow ugc">wordpress-security-txt-translation</a> repository.
The translations repository is included in builds submitted to the WordPress plugin directory. Users with the <a href="https://github.com/afragen/github-updater" rel="nofollow ugc">GitHub Updater Plugin</a> don’t have to wait for builds to the WordPress plugin directory — they can get updated translations as soon as they’re published to the repository by POEditor.
<h3>Anonymous Statistics (Opt-in)</h3>
This plugin has an option — that is disabled by default and can only be enabled by explicilty opt-ing in on the <code>security.txt</code> Settings page — to collect anonymous statistics to help better understand how this plugin is used and how people are implementing their <code>security.txt</code> documents. The goal of collecting this data is to aid in research and design of the <a href="https://tools.ietf.org/html/draft-foudil-securitytxt-00" rel="nofollow ugc">specification</a>, the <a href="https://github.com/austinheap/php-security-txt" rel="nofollow ugc">PHP library</a>, the <a href="https://github.com/austinheap/wordpress-security-txt" rel="nofollow ugc">plugin</a> itself, and to help us create a better experience for all users.
For example, one function of anonymous statistics is to send your <code>security.txt</code> document to our servers. This allows us to track what percent of users are implementing the specification according to the draft RFC, and how it might differ from the explicit definitions submitted to the <a href="https://www.ietf.org/" rel="nofollow ugc">Internet Engineering Task Force (IETF)</a>.
We respect your privacy and are happy to clarify on any aspect of the statistics collection and analysis. More importantly, you can <a href="https://github.com/austinheap/wordpress-security-txt/tree/master/trunk" rel="nofollow ugc">verify this in the code for yourself on GitHub</a>.
We do not track any personally-identifiable information and we are committed to protecting your privacy. With regards to performance, the tracking is implemented in such a way so as to not impact of your WordPress site at all.
<h3>Badges</h3>
All the badges!
<a href="https://github.com/austinheap/wordpress-security-txt/releases" rel="nofollow ugc"></a> 
<a href="https://packagist.org/packages/austinheap/wordpress-security-txt" rel="nofollow ugc"></a> 
<a href="https://travis-ci.org/austinheap/wordpress-security-txt" rel="nofollow ugc"></a> 
<a href="https://gemnasium.com/github.com/austinheap/wordpress-security-txt" rel="nofollow ugc"></a> 
<a href="https://scrutinizer-ci.com/g/austinheap/wordpress-security-txt/?branch=master" rel="nofollow ugc"></a> 
<a href="https://styleci.io/repos/111479243" rel="nofollow ugc"></a> 
<a href="https://codeclimate.com/github/austinheap/wordpress-security-txt/maintainability" rel="nofollow ugc"></a> 
<a href="https://codeclimate.com/github/austinheap/wordpress-security-txt/test_coverage" rel="nofollow ugc"></a> 
<a href="https://insight.sensiolabs.com/projects/5d9ed5a0-dbd0-45be-a92c-6d827483e742" rel="nofollow ugc"></a>

wp-security-txt

Do exactly what it says.
Clean code / clean UI... what else?

Great plugin. Thanks for it.

Excellent

A plugin for serving 'security.txt' in WordPress 4.9+, based on configuration settings.

security-txt vs wp-security-txt