Full observed history · 4 daily observations
Aggregator
Events
Everything the registry has recorded for this plugin, newest first.
The plugin stopped returning data from the plugin API for three consecutive daily passes. WordPress.org does not publish a reason when a plugin is closed; none is asserted here. The last known-good snapshot is frozen below as the archival record.
A new release arrived 2,435 days after the previous one (2019-12-04). A break in dormancy is a maintenance observation, not a judgement about the release or the owner.
Daily 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.
540 days since the last release (2019-12-04). Dormancy is a maintenance observation, not a judgement about the owner.
Ownership series
Each distinct value the author_profile field has held across our own daily observations, with the window it was seen in. This is the series that cannot be reconstructed after the fact. The WordPress.org API publishes only the current value.
| Account | Display name | First seen | Last seen | Days |
|---|---|---|---|---|
| edwardbock | EdwardBock | 02 Aug 2026 | 05 Aug 2026 | 4 |
Release series
Every release this registry holds, from both of its sources. Rows marked release log were read from the plugin’s public SVN history after the fact rather than watched in the directory, which is why a version can appear here that the crawler never saw live. “First observed” is when the daily crawl first met the version, and can trail the release date: by up to a day normally, or longer if the plugin was absent from the directory when the version shipped.
| Version | Released | First observed | Source |
|---|---|---|---|
| 2.2.0 | 04 Aug 2026 | 05 Aug 2026 | observed |
| 2.1.2 | 04 Dec 2019 | 02 Aug 2026 | observed |
| 2.1.1 | 31 Jul 2019 | — | release log |
| 2.1 | 04 Jul 2017 | — | release log |
| 2.0.4 | 29 Jun 2017 | — | release log |
| 2.0.3 | 31 May 2017 | — | release log |
| 2.0.2 | 24 Apr 2017 | — | release log |
| 2.0.1 | 20 Apr 2017 | — | release log |
| 2.0 | 19 Apr 2017 | — | release log |
| 1.1.4 | 16 Mar 2017 | — | release log |
| 1.1.3 | 13 Jul 2016 | — | release log |
| 1.1.2 | 19 Oct 2015 | — | release log |
| 1.1.1 | 19 Oct 2015 | — | release log |
| 1.1 | 19 Oct 2015 | — | release log |
| 1.0.8 | 28 Sep 2015 | — | release log |
| 1.0.7 | 11 Aug 2015 | — | release log |
| 1.0.6 | 21 Jul 2015 | — | release log |
| 1.0.5 | 17 Jul 2015 | — | release log |
| 1.0.4 | 17 Jul 2015 | — | release log |
| 1.0.3 | 16 Jul 2015 | — | release log |
| 1.0.2 | 29 Jun 2015 | — | release log |
| 1.0.1 | 15 Jun 2015 | — | release log |
| 1.0 | 05 Jun 2015 | — | release log |
“Released” is the author’s own date (the API’s last_updated for observed rows, the SVN tag date for recovered ones) and is stated in UTC, as every date here is. WordPress.org renders the same timestamp in your local time zone, so the two sites can disagree by a calendar day without disagreeing about the moment.
Install-band series
The WordPress.org API rounds active_installs to the first significant digit and stops at 10,000,000. Only band transitions are recorded here. A difference between two rounded figures is not a measurement, and this registry does not report one.
| Band | First seen | Last seen |
|---|---|---|
| 10+ | 02 Aug 2026 | 05 Aug 2026 |
One band across the whole observed window, no transition to report.