The WordPress Plugins Team released its latest update for the week ending May 10, 2026, revealing a steady but stretched moderation pipeline. Despite reviewing 583 plugin submissions, only 357 were approved, reflecting an approval rate just under 50%. Meanwhile, the queue of plugins awaiting review continues to expand, signaling ongoing challenges in balancing quality control with community demand.
Key Takeaways
- The Plugins Team reviewed 583 new plugins last week, approving 357 and rejecting 196.
- The plugin review queue stands at 4,832, with over 4,100 plugins pending longer than a week.
- Approximately 3,887 plugins are waiting on author responses, highlighting common revision delays.
- Help Scout handled over 2,000 conversations, with Mondays being the busiest support day.
- Review backlog growth signals persistent resource constraints for the Plugins Team.
Current Plugin Review Activity and Queue Backlog
In the week from May 4 to May 10, 2026, the Plugins Team processed 583 new plugin submissions. Of these, 357 were approved, while 196 were rejected, and 72 were closed without approval. This approval rate of approximately 48% is consistent with recent trends, reflecting the team’s commitment to maintaining standards while addressing the volume of submissions.
The backlog remains a critical concern. The total queue includes 4,832 plugins in various states of review. Notably, 4,126 plugins have been in the queue longer than seven days, underscoring delays in processing. Within the queue, 229 are new submissions not yet processed, while 4,603 are pending, awaiting some form of action.
A significant bottleneck is the 3,887 plugins pending author responses to reviewer feedback. This stage often extends review times, as authors must update their code, address security or compatibility issues, and resubmit. Meanwhile, 603 plugins are awaiting reviewer action, though 113 of these have not yet triggered email notifications to authors, indicating possible process inefficiencies.
Support and Communication Metrics
The team’s support infrastructure via Help Scout remains active, managing 2,006 concurrent conversations. Of these, 1,120 are new, with 1,785 distinct customers engaged. The team averages 250 conversations daily, with Mondays being the busiest, receiving 1,170 messages and sending 3,666 replies. The volume highlights both the demand for assistance and the workload on support staff, who also create significant email correspondence (971 emails during the period).
Challenges and Implications for the Plugin Ecosystem
The continuing growth in the review queue presents strategic challenges for the WordPress plugin ecosystem. As more developers submit plugins, the moderation process struggles to keep pace, risking longer wait times for approval and potential frustration for authors and users alike.
In practice, this backlog can delay plugin availability, affecting site operators who seek new or updated functionality. Agencies and developers must plan for these delays, potentially adjusting project timelines or seeking alternative plugins with quicker approval histories.
The high number of plugins pending author action suggests opportunities for improving communication clarity and streamlining revision guidance. Faster turnaround from authors could alleviate some backlog pressures, but this depends on clear, timely feedback from reviewers and sufficient developer resources.
Historical Context and Trends
The WordPress plugin repository has grown exponentially over the past decade, becoming a critical pillar of the CMS’s extensibility. However, this growth has stretched the moderation teams’ capacity, a trend that has accelerated with the rise of complex block-based plugins and increased security scrutiny.
Past efforts to automate parts of the review process have helped but cannot fully replace human judgment, especially regarding security and compatibility. The current statistics reflect a system still heavily reliant on manual review, which naturally limits throughput.
For context, our previous plugin team coverage tracks the same metrics week-over-week, showing incremental improvements but persistent challenges in managing review times and queue sizes.
What This Means for WordPress Users
We recommend plugin developers be proactive in responding to reviewer feedback promptly to minimize delays. For agencies and freelancers, factoring potential plugin approval wait times into project plans is prudent, especially for clients who depend on specific features or custom plugins.
Site owners should monitor plugin updates closely, as delays in approval can impact the availability of important security patches or new features. Considering well-maintained, established plugins might reduce risks associated with slower approval cycles for newer plugins.
This situation also signals a need for ongoing investment in the plugin review infrastructure. Whether through improved tools, additional reviewers, or clearer process guidelines, the community must address these bottlenecks to sustain a healthy plugin ecosystem as WordPress continues to grow.
Frequently Asked Questions
Why is the plugin approval rate around 48%?
The approval rate reflects the team’s quality standards, rejecting plugins that do not meet security, compatibility, or coding guidelines. About half of submissions require revisions or do not comply and thus are rejected to protect users.
What causes the large backlog in the plugin review queue?
The backlog results from high submission volume combined with manual review processes and delays when authors take time to respond to requested changes. Limited reviewer capacity also contributes.
How can developers speed up the review process?
Developers can accelerate reviews by responding quickly and thoroughly to feedback, ensuring their plugins adhere to guidelines before submission, and proactively testing for common issues.
What impact does the plugin review backlog have on WordPress site owners?
Site owners may experience delays in accessing new or updated plugins, which can affect security and functionality. Planning with awareness of possible delays is advisable.
