The latest articles on DEV Community by Chris Morris (@chris_morris). https://dev.to/chris_morris https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4004554%2F7e888014-decb-4ea7-a10b-eeb7edff7ab6.jpg https://dev.to/chris_morris en Chris Morris Sat, 27 Jun 2026 22:57:10 +0000 https://dev.to/chris_morris/almost-half-the-wordpress-plugin-directory-has-not-been-updated-in-two-years-26i8 https://dev.to/chris_morris/almost-half-the-wordpress-plugin-directory-has-not-been-updated-in-two-years-26i8 <p>I indexed the WordPress.org plugin directory and measured how well it is maintained. The headline: of the 57,383 plugins in the index, 45.6 percent have not shipped an update in 24 or more months. Data is as of June 2026.</p> <p>Here is the full staleness picture, measured against plugins that report an update date:</p> <ul> <li>65 percent: no update in 6+ months</li> <li>56 percent: no update in 12+ months</li> <li>45.6 percent: no update in 24+ months</li> <li>41.2 percent: no update in 36+ months</li> </ul> <p>"Not updated in two years" is the common line for calling a plugin abandoned, and WordPress.org uses a similar signal when it warns you on a plugin page. So nearly half the directory carries that flag.</p> <h2> The interesting part is who goes stale </h2> <p>Abandonment is not evenly spread. It tracks inversely with install count:</p> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>Active installs</th> <th>Abandoned (no update in 24+ months)</th> </tr> </thead> <tbody> <tr> <td>1K to 10K</td> <td>23.9 percent</td> </tr> <tr> <td>10K to 100K</td> <td>10.1 percent</td> </tr> <tr> <td>100K to 1M</td> <td>2 percent</td> </tr> <tr> <td>1M+</td> <td>0 percent</td> </tr> </tbody> </table></div> <p>The very large plugins are maintained. The risk and the opportunity sit in the middle. 192 plugins with 10,000 or more active installs have not been updated in over two years. Each one is a real user base running code nobody is shipping fixes for.</p> <h2> Why a builder should care </h2> <p>A plugin with 30,000 installs and no maintainer is not a dead end. It is a ready-made market. The users already exist, the search demand already exists, and the incumbent has stopped competing. The work is not inventing a category. It is shipping a maintained, modern version of something people already rely on.</p> <p>That is a very different starting point from a cold launch. You are not asking whether anyone wants the thing. You are looking at the install count and reading the recent one-star reviews to find out exactly what to fix.</p> <h2> How to use this </h2> <p>If you are looking for a side project or a small product to build, abandoned mid-size plugins are a practical place to start. Pick a niche you understand, find a plugin in it with a stuck user base, read its support forum, and confirm the gap before you write any code.</p> <p>The full report, with the named lists of the most-installed abandoned plugins, the most-installed low-rated plugins, and the largest plugins with the weakest support, is here:</p> <p><a href="https://wpgoldmine.io/research/state-of-wordpress-plugin-opportunities-2026" rel="noopener noreferrer">The State of WordPress Plugin Opportunities 2026</a></p> <p>The numbers above are measured from live WordPress.org data and the method is stated on the report.</p> wordpress webdev opensource data