The purpose of this project is to create set-it-and-forget-it plugin that can be installed without much effort to get WordPress site compliant with the current security txt spec.
The most logical place to start are the docs for WordPress Security Txt class..
The security txt for WordPress plugin includes translations for the following 17 languages.
If you would like to contribute new languge or you spotted in one of the translation files, please feel free to contribute to the public wordpress-security-txt POEditor project.
Once accepted additions modifications are built by POEditor to PO MO files and published to the wordpress-security-txt-translation repository..
The repository is included in builds submitted to WordPress plugin directory.
Users with GitHub Updater Plugin don't have to wait for builds to WordPress plugin directory — they can get updated translations as soon as they're published to the repository by POEditor..
This plugin has option — that is disabled by default and can be enabled by explicilty opt-ing in on the security txt Settings page — to collect anonymous statistics to help better understand how this plugin is used and how people implementing their security txt documents.
The goal of collecting this data is to aid in research and design of the specification, PHP, the plugin itself, and to help us create better experience for all users..
This allows us to track what percent of users implementing the specification according to RFC, and how it might differ from the explicit definitions submitted to Internet Engineering Task Force ..
Read more
Related items:
