Developer Guidelines & Plugin Requirements

All developers wishing to upload plugins to the Pluginlib.org platform must adhere to the following rules. These guidelines are established to ensure full compatibility with the WordPress.org ecosystem and to maintain user security.

1. Licensing

All uploaded plugins must be compatible with the GNU General Public License (GPL) version 2 or later. All libraries and images included within the plugin must also carry this license or a compatible one.

2. Security and Data Sanitization

Plugins must use WordPress security standards when processing user data. All data must be sanitized before being saved to the database and escaped before being output. Plugins containing security vulnerabilities will be suspended.

3. Use of Plugin Check

Before uploading your plugin to the system, you must test it using the official "Plugin Check" plugin. Any critical errors reported by this tool must be resolved before your plugin can be approved. Plugins that provide a clean report will be prioritized for review.

4. Privacy

Sending user data to external servers without explicit consent is strictly prohibited. Tracking codes or data collection processes can only be implemented with the user's clear opt-in.

5. Naming and Branding

The word "WordPress" should not be used directly in the plugin name. Instead, the phrase "for WordPress" should be preferred. Names that infringe on the trademark rights of other brands will be rejected.

6. File Structure and Coding Standards

Code must be readable and must not contain obfuscated code. A readme.txt file must be present in the plugin's root directory.

Plugins that do not comply with these rules will be rejected by our moderators or a revision will be requested.