Plugin profile · observed daily since 02 Aug 2026 · CLOSED
Committee history
Archival record
This plugin no longer returns data from the WordPress.org plugin API. The figures below are the last known-good observation, frozen on 14 Aug 2026. WordPress.org does not publish a reason when a plugin is closed, and none is inferred here.
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 justinvansteijn throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
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 early-stage: fewer than 10 active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
2 downloads a day averaged over 7 days. WordPress.org reports a running download total; the gap between two days is that day’s downloads. Unlike the install figure it is exact and has no ceiling, so it shows movement the rounded band cannot. Too few days so far to say whether it is rising or falling.
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 | 02 Aug | 03 Aug | 04 Aug | 05 Aug | 06 Aug | 07 Aug | 08 Aug | 09 Aug | 10 Aug | 11 Aug | 12 Aug | 13 Aug | 14 Aug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | — | — | — | — | — | 0 | 0 | 0 | 11 | 0 | 0 | 0 |
Unchanged throughout: ratings total (0) · active installs (0+) · version (1.0.0) · support threads (0) · threads resolved (0)
13 days of observation.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Is anyone still maintaining this?
- No release in 2,863 days (7.8 years). The last was 03 Nov 2018.
- Does not declare which WordPress version it has been tested against. A field the author sets themselves, so it is left blank rather than reported wrong.
- justinvansteijn 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.
- 15 Aug 202621 days agoRemoved from the WordPress.org directoryThe 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.
- 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.
- 26 Apr 20206 years agoDormancy threshold crossed540 days since the last release (2018-11-03). Dormancy is a maintenance observation, not a judgement about the owner.
- 03 Nov 20187.5 years agoVersion 1.0.0 released
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
- The plugin stopped returning data from the WordPress.org API on 14 Aug 2026.
- It has been held by justinvansteijn for all 13 days we have observed it.
- It was last released 7.5 years ago (03 Nov 2018).
- Its author declares it tested up to WordPress 4.7.35, which is current.
- WordPress.org reports fewer than 10 active installs.
What we don’t know yet
- Nobody has rated it. The first rating that arrives shows up here.
- 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.
What can’t be known
- Why it was closed. WordPress.org publishes no reason when a plugin is removed, and does not publish one later.
- 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
Reach out about this record
Corrections, missing context, or anything else about Committee history: a person reads every submission, and corrections get a reply within 5 business days.