Welcome to the official blog for the Plugins Team.
The team acts as gate-keepers and fresh eyes on newly submitted plugins, as well as reviewing any reported security or guideline violations.
Quick Links
The team acts as gate-keepers and fresh eyes on newly submitted plugins, as well as reviewing any reported security or guideline violations.
Quick Links
TL;DR: Three new reviewers have completed their onboarding and are now actively reviewing plugins. Thanks to them, and to the whole team, the review queue went from a mid-April peak of roughly 1,050 plugins back to nearly zero, even as submissions hit new records. And we have great news: the application form is open again for a second round. Apply here before 26 June 2026.
Back in March we published Contribute to the Plugins Team!, where we explained that you were submitting plugins faster than ever, and that we needed more hands on deck to keep up.
You answered. We received a wonderful response from the community, selected a first group of candidates, and started their training. Today we want to introduce the people who completed that process, show you what their contribution has already achieved, and let you know that the form is open again for anyone who wants to join the next round.
After roughly two months of onboarding and mentoring, three new members have joined the team and are already reviewing plugins and replying to authors every week. Please join us in welcoming:
Their work has been essential to the stability of the review queue. Beyond the reviews themselves, having more reviewers sharing the load means other members can devote more time to projects that improve the directory for everyone, such as Plugin Check and our internal scanner tooling. A healthy queue is not just about clearing a backlog, it is what makes the rest of the teamโs work possible.
You can find them, and the rest of us, on the team page.
The best way to thank our new contributors is to show what changed. Here is how the review queue evolved through the first half of 2026, alongside the number of new plugins you submitted each week.


The story in numbers:
In other words: the team absorbed a rising tide of submissions and cleared a huge backlog at the same time. This was achieved thanks to the efforts of both existing and new team members. You are still increasing the number of plugins you submit, and besides plugin reviews we also have many more emails to manage regarding all kind of queries about the directory, its use and guidelines.
Weโve continued to lean on automated tooling to make reviews faster, and AI-assisted checks did help us handle this volume. But we want to be clear about something: these tools support reviewers; they donโt replace them.
Judgement calls, conversations with authors, security context, manage of guideline violations and the many edge cases that donโt fit a pattern all still depend on experienced humans. This is a combination of tooling and committed people working together.
The team is in better shape, but submissions keep increasing, we have new challenges ahead and want to be future-proof. As we announced in March, weโre opening a second round of applications. If youโd like to help keep the plugin directory healthy, secure, and reliable for the millions of sites that depend on it, weโd love to hear from you.
There are still two ways to contribute:
The deadline to apply for this round is 26 June 2026.
If you already submitted it back in March, you donโt need to do it again, we have your submission and it will be taken into account.
I want to apply to join the Plugins Team ยป
To Marcel, Shiva, and Shameem: thank you for the time, care, and energy youโve already put in. To the reviewers who mentored them, the rest of the team and to the sponsors who help volunteers to devote their time and cover costs such as the intensive use of AI: thank you. And to everyone who submits and maintain plugins making the plugins directory a trusted place for extending WordPressโs functionality.
ะัะพัั-ะฟะพัั ะพั +make.wordpress.org/meta: Plugin Directory screenshots gallery update
X-comment from +make.wordpress.org/docs: Comment on WordPress Documentation Team Closes 200+ Issues โ and Needs Your Help
X-post from +make.wordpress.org/meta: Plugin Directory MCP Server
TL;DR: We are looking for contributors and/or organizations that are willing to contribute to the Plugins Team. Apply here.
In recent years, the Plugins Team has gone through several phases, and we have been able to meet the challenges you have set for us. In 2025, we were excited to manage twice as many plugins as in 2024 with approximately the same number of volunteers. This was possible thanks to improved processes and tools, as well as the higher quality of the plugins you submitted. Thank you very much for that.
Itโs 2026, andโฆ letโs be clear: youโre absolutely crushing it with plugins.

In previous years, we typically received 100โ150 new pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. submissions per week. In 2025, that number started at over 200 per week and rose to more than 300 by the end of the year. In 2026, the pace is accelerating even further, exceeding 500 weekly submissions by March.
To keep up with this rapid growth, we need more hands on deck.
There are two ways to contribute to the team.
Our team is looking for new members who are able to join the team for reviewing plugins.
Your tasks would look like this:
Our current team members will guide and train you on how to perform these tasks. The training period takes about two months.
There are three essential requirements for successfully joining the team and contributing:ย
This three requirements and expectations are further explained in the form, you can check it out and submit your application now.
We know that it is not easy to reach the level of commitment that this team requires, which is why we know that sponsors are essential for the stability of this team.
We would like to thank all of the sponsors who support the volunteers on this team. Here are some of the achievements made in 2025 thanks to the support of the following sponsors:
The WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Plugins Team plays a vital role in maintaining the health, security, and reliability of the plugins directory, which serves millions of WordPress sites worldwide. By sponsoring volunteers on this team, you help ensure that contributors can dedicate time to reviewing plugins, maintaining quality standards, enforcing guidelines, and improving security across the ecosystem. This helps ensure that the plugins in the directory remain a trustworthy and reliable source of functionality that meets the essential standards expected within the WordPress environment.
You can sponsor the team by contributing the time of people from your organization or by supporting volunteers who are (or could be) on the team. If you donโt know anyone who you could sponsor, we will help you find them.
Our timeline:
Feel free to ask questions or share any feedback in the comments or email plugins at wordpress.org.
Thanks to @davidperez , @nilambar and @lukecarbis for their feedback for creating this process.
If there is one thing worth highlighting this year, it is how AI has impacted the WordPress pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. ecosystem. This impact is evident both in the number of submissions sent for review to be published in the directory, and in how the team is implementing AI-based analysis processes to help deliver improved workflows with a certain level of automation.
The WordPress โPlugin Review Teamโ proposed a name change to the โPlugins Teamโ to better reflect the broader scope of its responsibilities, which went beyond reviewing new plugin submissions. At that time, the team was also working on improving tools such as the Internal Scanner and the Plugin Check Plugin, incorporating automated and AI-assisted checks, and collaborating closely with the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team to resolve open tickets and enhance features of the plugin directory. The change aimed to align the teamโs name with its expanded role in improving the overall quality, reliability, and security of plugins in the ecosystem.
The number of submissions sent for review has doubled compared to last year. While last year we had an average of 150 weekly submissions, in the final weeks of this year the 300 mark has been surpassed, with volumes stabilising at around 330 submissions per week.

This situation continues to challenge the team to keep the queue for a first review under one week, even with this doubled volume of submissions.
To meet this goal, we have focused on improving the teamโs two main tools: Internal Scanner and the Plugin Check Plugin.
In 2025, the WordPress Plugins Team reviewed 12,713 plugins, representing a 40.6% increase compared to 2024. This confirms a continued and substantial growth of the plugin ecosystem, with significantly more submissions entering the review process.
During the year author responsiveness improved slightly compared to 2024, sadly 38.7% of the plugins we reviewed received no reply from their authors, which remains a relatively high proportion. Although this percentage decreased by over 10% in respect to 2024, it continues to be a major factor that prevents volunteers from making better use of their time.
Despite this, plugin approvals increased in absolute and relative terms. Out of the 7,882 plugins that followed the review process, a total of 5,415 plugins were approved, up 66.2% from the previous year with 3,259 approvals. Overall, 69.5% of reviewed plugins were approved (63.4% in 2024), showing a clear improvement in approval rates. Highlighting once again that active developer engagement strongly correlates with successful approval.
The review process in 2025 was also more intensive and thorough. The total number of reviews carried out grew by 52.2%, exceeding 58,000, as each plugin normally requires more than one review before itโs ready for approval.
The number of issues identified during reviews increased by 15.1%, reaching 59,137 issues. This rise reflects deeper scrutiny rather than a decline in quality. In fact, the average number of issues per plugin decreased, indicating that submissions were generally better prepared. This improvement is even clearer for approved plugins, which required significantly fewer issues to be resolved on average than in previous years.
In summary, 2025 was a year of scale, stronger review practices, and gradual quality improvement, but also one of growing operational demands:
Overall, we have a more mature and quality-focused review process, supported by automation and better-prepared submissions, while also highlighting the need to further address responsiveness and review capacity as the ecosystem continues to expand.
The internal scanner is the in-house tool that the team uses to review plugins. It searches for hundreds of possible issues that the reviewers either confirm or dismiss when creating a report. As part of the improvements to this central tool for our day-to-day plugin reviews, we have worked on reducing review time, particularly for highly repetitive and time-consuming processes such as:
During this year, we added more than 80 new features and checks to our internal tools, as well as incorporating over 100 improvements and behavioral changes. Our focus was on expanding automated checks, enhancing AI-assisted reviews, minimizing false positives, and significantly improving performance and scalability (e.g. bulk scans, caching, and parallel execution). We also created new tools to help streamline communication with authors who contact us via the support inbox.
Since the launch of this plugin, we have continuously improved it by adding new checks and refining existing ones.
In 2025, the main advancements include:
The plugin has evolved from a basic validator into a security-focused tool with improved code quality checks, better CLI support, and stronger validation against WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ plugin directory requirements.
Since October, and in collaboration with the Meta team, we have implemented PCP to run automatic scans on every new plugin version update.
This new strategy aligns with the teamโs objective of establishing proactive measures to improve the overall security of the WordPress plugin ecosystem.
At present, an internal report is generated, but our next goal is for authors to receive a report outlining the main detected issues, enabling them to actively improve the security of their plugins. We expect to see this enhancement rolled out in the coming weeks.We continue to recommend that authors follow best practices such as the WordPress Coding Standards and set up automated workflowsโsuch as GitHub Actionsโto have their plugins reviewed by Plugin Check as part of their development process.
In conclusion, it has been a year in which we have experienced significant growth in the number of plugins submitted, while the team has remained the same size. The queue has stayed stable thanks to improvements in the tools, which have allowed us to be far more productive.
In addition, authors now have an essential tool to validate their developments before they are submitted to the directory. PCP will help us improve the plugin ecosystem by checking updates in the WordPress plugin directory.
It has also been a year of AI supporting the development of WordPress plugins. Many community members have become involved in plugin development for the first time. This increases the diversity of the plugin directory and shows that AI has lowered the barriers to entry without compromising plugin quality (since the โbarrierโ for plugin approval has not been lowered).
One of the key challenges for 2026 will be identifying how AI can support the community in improving plugins and strengthening their security, while ensuring this progress delivers genuine, positive impact. At the same time, the team is seeing an unprecedented increase in plugin submissions for review, with record numbers arriving each week. Our challenge will be to scale our team and processes to handle this growth effectively, while maintaining the standards and practices that have always guided our contribution.
This post was written by @davidperez and reviewed by @frantorres
X-comment from +make.wordpress.org/project: Comment on Proposal: 2026 Major Release Schedule
As an important part of the internet, the WordPress community, actively thinks about the security of the ecosystem. Community members, developers, specialized companies, and independent researchers all play a role in maintaining the security of the environment.
In the Plugins Team, weโre passionate not only with improving the tools we already work with, but also with making them public so the community can use them when developing and building plugins.
Thatโs why the Plugins Team, Performance Team, and MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team launched the Plugin Check plugin, a tool that runs checks on your pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. and generates a report so developers can apply proper security measures and improve the plugin overall.
On September 17th of 2024, we introduced automatic detection of issues for new plugins that fail to meet the minimum required checks. This feature provides developers with guidance on how to resolve these issues before the Plugins Team conducts a manual review.
This has helped improve the quality of plugin submissions before they even reach a human reviewer. Thanks to AI support during manual reviews using our Internal Scanner, plus the teamโs effort to complete more reviews, the queue hasnโt grown despite receiving more than double the number of plugins compared to last year.
We are now running Plugin Check for ALL plugins updates, new and already approved.
Since Monday, October 27th, thanks to the Meta team, weโve implemented automatic detection on wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ for issues related to security, compatibility and compliance.
Right now, this information is available internally for the team, who will evaluate it and send reports to authors as needed. During this phase, we will observe how PCPs behave during updates and we will improve as we see fit.
Once weโve evaluated the performance of PCP with plugin updates, the goal is to deliver via email a security report to authors right after they update their plugin. Our aim is to promote and maintain good development practices across the entire WordPress ecosystem.
To wrap up: this week marks a small but meaningful step forward in improving the security of plugins hosted on wordpress.org. We look forward to the community taking this opportunity to double-check their plugins when sending an update โ or even before.
This post was written by David Perez and reviewed by Francisco Torres.
After WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what theyโve learned throughout the year and share the joy. Learn more. US, we have prepared some insights about our team and we wanted to share it with the community.
These are the insights from the Plugins Team:
In summary, although the number of submitted plugins is increasing, the teamโs effort remains steady, thanks in part to AI automation in certain areas. Our goal is to continue improving by implementing AI in more checks, as well as introducing proactive scanning of the current Plugins Directory.
All this data was prepared on the 31th of August.
Written by @davidperez, reviewed by @frantorres