Full observed history · 86 daily observations
SardexPay for WooCommerce
Events
Everything the registry has recorded for this plugin, newest first.
The plugin resumed returning data from the plugin API after a recorded closure. WordPress.org does not publish reasons for closures or reinstatements; none is asserted here.
“sardexnet” → “SardexPay”. The wordpress.org account is unchanged, so this is the same owner relabelling themselves, not a transfer. Recorded as a fact; it carries no score weight.
A new release arrived 905 days after the previous one (2024-04-03). A break in dormancy is a maintenance observation, not a judgement about the release or the owner.
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.
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 (2024-04-03). Dormancy is a maintenance observation, not a judgement about the owner.
Reported by the plugin API as the date this plugin was added.
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 |
|---|---|---|---|---|
| sardexnet | SardexPay | 02 Aug 2026 | 31 Oct 2026 | 86 |
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 |
|---|---|---|---|
| 3.0.0 | 25 Sep 2026 | 30 Sep 2026 | observed |
| 2.2.2 | 03 Apr 2024 | 02 Aug 2026 | observed |
| 2.2.1 | 03 Apr 2024 | — | release log |
| 2.2.0 | 23 Feb 2022 | — | release log |
| 2.1.1 | 19 Jul 2021 | — | release log |
| 2.1.0 | 15 Jul 2021 | — | release log |
| 2.0.3 | 10 Mar 2021 | — | release log |
| 2.0.2 | 14 Jan 2021 | — | release log |
| 2.0.1 | 14 Jan 2021 | — | release log |
| 2.0.0 | 04 Jan 2021 | — | release log |
| 1.0.4 | 26 Aug 2020 | — | release log |
| 1.0.3 | 25 Aug 2020 | — | release log |
| 1.0.2 | 13 Aug 2020 | — | release log |
| 1.0.1 | 12 Aug 2020 | — | 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 |
|---|---|---|
| 30+ | 04 Oct 2026 | 31 Oct 2026 |
| 20+ | 01 Oct 2026 | 03 Oct 2026 |
| 30+ | 02 Aug 2026 | 30 Sep 2026 |