Plugin profile · observed daily since 02 Aug 2026
Health Check & Troubleshooting
Active installs200,000+ rounded
Current authorWordPress.org
Owner changesNone while we have been watching
Last release2 years ago 25 Jul 2024
Support0 / 1 resolved, last 2 months
Releases on record26
Rating3.6 /5 · 181
Added to directory09 Jun 2018
Requires WP4.4
Requires PHP5.6
Version lag0.5 behind
Tested up toWP 6.6.7 WordPress is now on 7.1
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by WordPress.org throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| Clorith | 26 | 20 Feb 2018 | 25 Jul 2024 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Very widely adopted: 200,000+ active installs. In the top tier of the directory by install count.
545 downloads a day over the last 7 days, falling 15% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
08 Aug 2026peak 954/day06 Sep 2026
Install band fell to 200,000+ on 04 Sep 2026, from 300,000+. Both figures are rounded to one significant digit, so the size of the change is not knowable from them.
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep | 05 Sep | 06 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 503 | 661 | 863 | 928 | 587 | 650 | 378 | 606 | 954 | 0 | 721 | 657 | 499 |
| Active installs | 300,000+ | 300,000+ | 300,000+ | 300,000+ | 300,000+ | 300,000+ | 300,000+ | 300,000+ | 300,000+ | 300,000+ | 300,000+ | 200,000+ | 200,000+ | 200,000+ |
| Support threads | 4 | 3 | 3 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
Unchanged throughout: ratings total (181) · version (1.7.1) · threads resolved (0)
36 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory8 years ago 09 Jun 2018
Requires WP4.4
Requires PHP5.6
Version lag0.5 behind
Is anyone still maintaining this?
- No release in 774 days (2.1 years). The last was 25 Jul 2024.
- Declares compatibility only up to WordPress 6.6.7, while 7.1 is current. The author has not confirmed it runs on the last 5 releases.
- 0 of 1 support threads answered in the last two months.
- The same account maintains 20 other plugins, 15 of which were updated in the last 90 days. the account is active.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 02 Aug 20261 month agoInstall band moved to 300,000+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 20261 month agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 16 Jan 20268 months agoDormancy threshold crossed540 days since the last release (2024-07-25). Dormancy is a maintenance observation, not a judgement about the owner.
- 25 Jul 20242 years agoVersion 1.7.1 released
- 19 Dec 20232.5 years agoVersion 1.7.0 releasedfrom the release logCommitted by Clorith.
- 31 Mar 20233 years agoVersion 1.6.0 releasedfrom the release logCommitted by Clorith.
- 01 Nov 20223.5 years agoVersion 1.5.1 releasedfrom the release logCommitted by Clorith.
- 10 Sep 20223.5 years agoVersion 1.5.0 releasedfrom the release logCommitted by Clorith.
- 24 May 20224 years agoVersion 1.4.5 releasedfrom the release logCommitted by Clorith.
- 09 Apr 20206 years agoVersion 1.4.4 releasedfrom the release logCommitted by Clorith.
- 31 Mar 20206 years agoVersion 1.4.3 releasedfrom the release logCommitted by Clorith.
- 18 Dec 20196.5 years agoVersion 1.4.2 releasedfrom the release logCommitted by Clorith.
- 28 Sep 20196.5 years agoVersion 1.4.1 releasedfrom the release logCommitted by Clorith.
- 16 Aug 20197 years agoVersion 1.4.0 releasedfrom the release logCommitted by Clorith.
- 09 May 20197 years agoVersion 1.3.2 releasedfrom the release logCommitted by Clorith.
- 06 May 20197 years agoVersion 1.3.0 releasedfrom the release logCommitted by Clorith.
- 09 Jun 20188 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
- 20 Feb 20188.5 years ago13 earlier releasesfrom the release logBetween 20 Feb 2018 and 06 May 2019. Listed individually in the public release log rather than here.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by WordPress.org for all 36 days we have observed it.
- It was last released 2 years ago (25 Jul 2024).
- Its author declares it tested up to WordPress 6.6.7; WordPress is now on 7.1.
- WordPress.org reports 200,000+ active installs.
- It carries 181 ratings, averaging 3.6 out of 5.
- 0 of 1 support threads in the last two months are marked resolved.
What can’t be known
- Whether the quiet is neglect or a finished plugin. That is the author’s intent, which no dataset records, and a stable plugin can need no changes for years.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
This plugin has not been updated in a long time. These carry the same tags and describe themselves in the same terms, so they are a starting point for a replacement, not a recommendation. Check them yourself.
Mozzy Assistance
Monitor, back up and safely maintain WordPress with health checks, protected updates and rollback through Mozzy.
10+ installsupdated 02 Sep 2026
far fewer installs
Compare side by side Flow Store Check for WooCommerce
WooCommerce store health check and diagnostics for catalog, inventory, checkout, orders, payments, shipping, email, and system configuration.
fewer than 10 installsupdated 30 Aug 2026
Compare side by side Plugin Health Check
Adds checks to the Site Health screen to test installed plugins and themes.
20+ installsupdated 06 Aug 2019
far fewer installs · no release in over 18 months
Compare side by side Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about Health Check & Troubleshooting: a person reads every submission, and corrections get a reply within 5 business days.