If you have been paying attention to the repo lately, you know things are moving at a breakneck pace. The WordPress Plugins Team just released their latest stats, and the numbers are staggering: we have gone from a comfortable 150 submissions per week in 2024 to over 500 per week in 2026. That is not just growth; it is an explosion that threatens to create a massive bottleneck if we do not scale our human infrastructure.
I have seen this happen before with major API updates. Everyone rushes to build the “next big thing,” and suddenly, the gatekeepers are overwhelmed. Consequently, the team is calling for a fresh wave of contributors to help maintain the quality and security of the ecosystem. If you are a developer who cares about the codebase of the internet, this is your signal.
The 500-Plugin Problem: Why We Need the WordPress Plugins Team
In 2025, the team managed to double the number of plugins they handled with the same small group of volunteers. However, as we hit March 2026, the pace has quadrupled. We are now seeing as many plugins in two days as we used to see in an entire week. This isn’t just a “numbers” problem; it’s a security and stability concern for every site owner using the directory.
As I noted when discussing why the team name change matters, these volunteers are the first line of defense against malformed code and security vulnerabilities. When the queue gets backed up, developers get frustrated, and sometimes “hacks” start appearing in the wild because people can’t wait for the official review.
What Does a Plugin Reviewer Actually Do?
Being part of the WordPress Plugins Team isn’t just about clicking “Approve.” It is a technical deep dive into thousands of lines of varied logic. Specifically, you will be looking for things like improper data sanitization, missing nonces, or race conditions in transients. For instance, a reviewer might catch a snippet like this that puts a site at risk:
<?php
/**
* THE WRONG WAY: Direct input in a query.
* Reviewers catch this every single day.
*/
function bbioon_save_settings_bad() {
if ( isset( $_POST['plugin_option'] ) ) {
update_option( 'my_plugin_data', $_POST['plugin_option'] ); // NO SANITIZATION!
}
}
/**
* THE RIGHT WAY: Sanitized and validated.
*/
function bbioon_save_settings_good() {
// 1. Check permissions
if ( ! current_user_can( 'manage_options' ) ) return;
// 2. Verify nonce
check_admin_referer( 'bbioon_settings_action', 'bbioon_nonce' );
if ( isset( $_POST['plugin_option'] ) ) {
// 3. Sanitize the input based on expected type
$clean_data = sanitize_text_field( $_POST['plugin_option'] );
update_option( 'my_plugin_data', $clean_data );
}
}
Reviewers follow the Detailed Plugin Guidelines to ensure every submission meets the community standards. It’s a two-month training period, but once you are through, you are essentially a guardian of the directory.
Sponsorship: Stability Beyond Code
We need to talk about the organizations making this possible. Names like Awesome Motive, SiteGround, and Hostinger are already sponsoring thousands of reviews. If your organization relies on WordPress to generate revenue, sponsoring a volunteer is one of the most direct ways to ensure the platform remains a trustworthy source of functionality.
Without these sponsors, the WordPress Plugins Team would likely collapse under the weight of 500+ weekly tickets. If you can’t commit 10 hours a week to code review, consider if your company can “Five for the Future” by funding someone who can.
Look, if this WordPress Plugins Team stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Takeaway: The 2026 Timeline
The deadline for the first round of applications is 27 March 2026. If you miss that, there is a second window in June. The ecosystem is growing faster than ever, and we need technical minds to keep it from becoming the Wild West. Check out the Featured Plugins Experiment to see where the directory is heading, and if you have the skills, get involved.
“},excerpt:{raw:
