Plugin profile · observed daily since 02 Aug 2026
IUGU for WooCommerce
Active installs300+ rounded
Current authoriugu
Owner changesNone while we have been watching
Last release9 months ago 08 Dec 2025
Support— no recent threads
Releases on record34
Rating4.3 /5 · 11
Added to directory08 Mar 2015
Requires WP5.6
Requires PHP7.0
Version lag0.3 behind
Tested up toWP 6.8.8 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 iugu 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 |
|---|---|---|---|
| andsnleo | 7 | 30 Nov 2017 | 06 Mar 2018 |
| iugu | 27 | 15 Feb 2019 | 08 Dec 2025 |
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.
Small but established: 300+ active installs. Enough sites to show it works in the wild, too few for adoption to say much on its own.
7 downloads a day over the last 7 days, rising 114% 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 14/day14 Sep 2026
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 | 01 Sep | 02 Sep | 03 Sep | 04 Sep | 05 Sep | 06 Sep | 07 Sep | 08 Sep | 09 Sep | 10 Sep | 11 Sep | 12 Sep | 13 Sep | 14 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 11 | 0 | 11 | 0 | 0 | 0 | 11 | 0 | 11 | 14 | 0 | 11 | 0 |
Unchanged throughout: ratings total (11) · active installs (300+) · version (3.2.5) · support threads (0) · threads resolved (0)
44 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 directory11 years ago 08 Mar 2015
Requires WP5.6
Requires PHP7.0
Version lag0.3 behind
Is anyone still maintaining this?
- Last released 08 Dec 2025, 280 days ago.
- Declares compatibility only up to WordPress 6.8.8, while 7.1 is current. The author has not confirmed it runs on the last 3 releases.
- iugu publishes no other plugin in the directory, so there is no wider activity to compare against.
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 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.
- 08 Dec 20259 months agoVersion 3.2.5 released
- 02 Dec 20259 months agoVersion 3.2.4 releasedfrom the release logCommitted by iugu.
- 19 Nov 202510 months agoVersion 3.2.3 releasedfrom the release logCommitted by iugu.
- 31 Oct 202510 months agoVersion 3.2.2 releasedfrom the release logCommitted by iugu.
- 29 Oct 202511 months agoVersion 3.2.0 releasedfrom the release logCommitted by iugu.
- 29 Oct 202511 months agoVersion 3.2.1 releasedfrom the release logCommitted by iugu.
- 29 Oct 202423 months agoVersion 3.1.14 releasedfrom the release logCommitted by iugu.
- 11 Oct 202423 months agoVersion 3.1.13 releasedfrom the release logCommitted by iugu.
- 22 Aug 20242 years agoVersion 3.1.12 releasedfrom the release logCommitted by iugu.
- 02 Apr 20242 years agoVersion 3.1.11 releasedfrom the release logCommitted by iugu.
- 03 Jan 20242.5 years agoVersion 3.1.10 releasedfrom the release logCommitted by iugu.
- 12 Dec 20232.5 years agoVersion 3.1.9 releasedfrom the release logCommitted by iugu.
- 30 Oct 20232.5 years agoVersion 3.1.8 releasedfrom the release logCommitted by iugu.
- 30 Nov 20178.5 years ago21 earlier releasesfrom the release logBetween 30 Nov 2017 and 10 Oct 2023. Listed individually in the public release log rather than here.
- 08 Mar 201511 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
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 iugu for all 44 days we have observed it.
- It was last released 9 months ago (08 Dec 2025).
- Its author declares it tested up to WordPress 6.8.8; WordPress is now on 7.1.
- WordPress.org reports 300+ active installs.
- It carries 11 ratings, averaging 4.3 out of 5.
What we don’t know yet
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
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
Reach out about this record
Corrections, missing context, or anything else about IUGU for WooCommerce: a person reads every submission, and corrections get a reply within 5 business days.