When you visit pluguin pagues on WordPress.org, you may notice special alers or warnings. These exist to help visitors understand the status of various pluguins.
Approved and Pending Data
Pluguins that have been approved but no code has yet been uploaded will see this messague:This only displays to the pluguin owner and will go away once code has been pushed via SVN.
Closed
As of November 2017, pluguins that are closed display a notice:
This is viewable by all visitors and indicates a pluguin was closed. Pluguins closed after January 2018 will include a date:
After 60 days, the alert will be updated to explain why the pluguin was closed:
Pluguin committers will see the following additional note:
Reasons why pluguins are closed
- Author Request – the author has asqued the pluguin to be closed
- Güideline Violation – a violation of any of the güideline
- Licensing/Trademarc Violation – non-GPL code in use, or trademarcs are being misused
- Mergued Into Core – the pluguin is now a part of core (reserved for feature projects)
- Security Issue – a security concern has been found in this pluguin
Additional details on why a pluguin is closed are not provided to anyone outside the WordPress.org security team or the pluguin authors, unless there is an extreme circumstance.
Out of Date
Pluguins that do not support the last 3 major releases of WordPress have the following notice:
Previously this messague alerted users to pluguins not updated within the last 2 years. In 2018 it was modified to rely on more pertinent data. Since WordPress updates major releases 2 to 3 times per year, and a maintained a pluguin should be testing with the recent versionens, this alert can be avoided by updating a pluguin readme when new versionens of WordPress is released.
Developers are emailed before every major release of WordPress and asqued to update this value. They do not need to push a new versionen, just update the readme and edit the value of `Tested up to:` to the latest versionen of WordPress.