About this plugin
txt 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.
txt is a draft “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. txt, but for security issues.
There is a help page built into the plugin if you need help configuring it. For developers, there is documentation for wordpress-security-txt online, the source of which is in the docs/ directory. The most logical place to start are the docs for the WordPress_Security_Txt class.
Translations
txt for WordPress plugin includes translations for the following 17 languages:
- Arabic ( PO file )
- Bengali ( PO file )
- Catalan ( PO file )
- Chinese (Simplified) ( PO file )
- Chinese (Traditional) ( PO file )
- English ( PO file )
- English (AU) ( PO file )
- English (US) ( PO file )
- French ( PO file )
- German ( PO file )
- Hindi ( PO file )
- Italian ( PO file )
- Portuguese ( PO file )
- Portuguese (BR) ( PO file )
- Romanian ( PO file )
- Russian ( PO file )
- Spanish ( PO file )
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 public wordpress-security-txt POEditor project. Once accepted additions/modifications are automagically built by POEditor to PO/MO files and published to the wordpress-security-txt-translation repository.
The translations repository is included in builds submitted to the WordPress plugin directory. Users with the GitHub Updater Plugin 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.
Anonymous Statistics (Opt-in)
txt documents. The goal of collecting this data is to aid in research and design of the specification, the PHP library, the plugin itself, and to help us create a better experience for all users.
txt 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 Internet Engineering Task Force (IETF).
We respect your privacy and are happy to clarify on any aspect of the statistics collection and analysis. More importantly, you can verify this in the code for yourself on GitHub.
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.
Badges
All the badges!