Plugin Dependencies
by scribu · Uncategorized
Also makes 17 other plugins · 27.6K+ installs across the portfolio →
Plugin dependency management
48 health vs 56 average across 16,376 Uncategorized plugins
High removal-risk signals
63/100Maintenance and integrity signals that tend to precede a WordPress.org removal. Not an official status, a heads-up to act.
- Long abandoned. No update in 11+ years — the top precursor to removal once a vulnerability is found.
- Compatibility drift. Tested only up to WordPress 4.0.38, well behind 6.8.
Directory ranking optimization
How it's scored →How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.
Under-optimized
Biggest win: Update recency
To rank higher: Last updated 4309 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.
Get the full rank-higher report →Daily downloads
Since 2022-10-05 · 1,427 days · wp.org + Plugin Pulse archive
30-day downloads
Rolling 30-day volume · peaks are release surges
58
now · peak 80
Directory rank vs rivals
wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you
Update activity
How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.
Release cadence
No release in a yearHow often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.
0
releases in the last 12 months
11.7y ago
latest release · v1.3
3
tagged releases on record
Recent releases
What its installed base runs
via wordpress.orgShare of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.
Estimated active installs
The public count shows “100+”. Our estimate pins where the real number sits.
Modeled within the band wp.org reports; tightens as we track daily.
Install history · since 2015-04-23 · 1,395 observations
Estimated value
What this plugin might earn a year, and what it might sell for. Modeled from public signals; we don't see anyone's books.
Est. annual revenue
Est. acquisition value
No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price. A small install base leaves thin data to model from.
Details
Recent reviews
All reviews on wp.org ↗- ★★★★★ Gahapati9.9y ago
This plugin — with its companion Known Plugin Dependencies — offers basic, and that is to say: robust — plugin dependency information and handling. This core functionality is missing from WP Core, unfortunately. I’ve seen plugin developers role out all kinds of dependency notification mechanisms on their own, which would not be needed, if this — or something very similar to this — were to become part of WP Core. Of course, there is the TGM Plugin Activation library out there, which may look like the real deal. But then, for a simple dependency notification in a simple plugin, this would seem way too complex and unnecessary. So, where can I vote for this? P.S.: Would one of the devs care to update the compatibility info in the read-me file?
Read on wp.org ↗ - ★★★★★ moneer9910.6y ago
This plugin should be WordPress core functionality. Thanks
Read on wp.org ↗ - ★★★★★ Adrian Mörchen11.3y ago
Should be WordPress core functionality.
Read on wp.org ↗ - ★★★★★ blpraveen11.6y ago
Exactly what I was looking at this should be present in wordpress by default not as plugin/extension. Thanks
Read on wp.org ↗ - ★★★★★ antongorodezkiy12.0y ago
Useful, thanks
Read on wp.org ↗ - ★★★★★ webkod3r12.2y ago
Wow… just that I’m looking for.
Read on wp.org ↗ - ★★★★★ Jason Judge13.2y ago
This needs to be a core function of WP. It is especially useful when developing large projects, and the custom code is split into a handful of plugins to handle distinct functionality. Being able to handle dependencies like this avoids many white screens and scratching of heads.
Read on wp.org ↗
Behavioral tests
via WP HiveAutomated install-time checks, tested on PHP 7.2.16 · WP 5.3
Growth timeline
Install-tier crossings we have observed, and how long each tier took to outgrow
- 2026-08-31 200+ → 100+ down after 1132 days in tier
- 2023-07-26 300+ → 200+ down after 1 days in tier
- 2023-07-25 200+ → 300+ up after 3 days in tier
- 2023-07-22 300+ → 200+ down after 3 days in tier
- 2023-07-19 200+ → 300+ up after 2 days in tier
- 2023-07-17 300+ → 200+ down
Competes with
The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).
-
Stock Dependencies for WooCommerce 100+ installs · 4.2★ · 1 shared tag B - K Known Plugin Dependencies 10+ installs · 4.0★ · 1 shared tag D
Embed this report card
Drop a live Pulse card for Plugin Dependencies into a readme, a review or a deck. It updates itself.
<iframe src="https://plugins.wpmayor.com/embed/plugin-dependencies" width="480" height="300" style="border:0" loading="lazy" title="Plugin Dependencies — Plugin Pulse"></iframe> Plugin Dependencies: 100+ active installs, 5.0★ (7 reviews). Plugin Pulse (WP Mayor), as of 2026-08-31. https://plugins.wpmayor.com/plugin/plugin-dependencies