Plugin profile · observed daily since 02 Aug 2026
WP Experience API
Active installs10+ rounded
Current authorctltwp
Owner changesNone while we have been watching
Last release11 years ago 11 Aug 2015
Support— no recent threads
Releases on record8
Rating4.5 /5 · 2
Added to directory11 May 2015
Requires WP3.5
Requires PHPfalse
Version lag2.9 behind
Tested up toWP 4.2.39 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 ctltwp 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 |
|---|---|---|---|
| loongchan | 7 | 11 May 2015 | 11 Aug 2015 |
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 early-stage: 10+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
6 downloads a day over the last 7 days, steady 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 12/day08 Sep 2026
Install band fell to 10+ on 28 Aug 2026, from 20+. 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 | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep | 05 Sep | 06 Sep | 07 Sep | 08 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 11 | 0 | 12 | 12 | 0 | 0 | 11 | 0 | 11 | 0 | 11 | 0 | 11 |
| Active installs | 20+ | 20+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ |
Unchanged throughout: ratings total (2) · version (1.0) · support threads (0) · threads resolved (0)
38 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 11 May 2015
Requires WP3.5
Requires PHPfalse
Version lag2.9 behind
Is anyone still maintaining this?
- No release in 4,047 days (11.1 years). The last was 11 Aug 2015.
- Declares compatibility only up to WordPress 4.2.39, while 7.1 is current. The author has not confirmed it runs on the last 29 releases.
- The same account maintains 20 other plugins, and none has been updated in over a year, the most recent on 02 May 2025.
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 20+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.
- 01 Feb 20179.5 years agoDormancy threshold crossed540 days since the last release (2015-08-11). Dormancy is a maintenance observation, not a judgement about the owner.
- 11 Aug 201511 years agoVersion 1.0 released
- 11 Aug 201511 years agoVersion 1.0.6 releasedfrom the release logCommitted by loongchan.
- 08 Aug 201511 years agoVersion 1.0.5 releasedfrom the release logCommitted by loongchan.
- 23 Jul 201511 years agoVersion 1.0.4 releasedfrom the release logCommitted by loongchan.
- 08 Jun 201511 years agoVersion 1.0.3 releasedfrom the release logCommitted by loongchan.
- 14 May 201511 years agoVersion 1.0.2 releasedfrom the release logCommitted by loongchan.
- 13 May 201511 years agoVersion 1.0.1 releasedfrom the release logCommitted by loongchan.
- 11 May 201511 years agoVersion 1.0.0 releasedfrom the release logCommitted by loongchan.
- 11 May 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 ctltwp for all 38 days we have observed it.
- It was last released 11 years ago (11 Aug 2015).
- Its author declares it tested up to WordPress 4.2.39; WordPress is now on 7.1.
- WordPress.org reports 10+ active installs.
- It carries 2 ratings, averaging 4.5 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.
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.
Experience API for LearnPress by GrassBlade
This plugin enables the Experience API (xAPI / Tin Can), cmi5 , SCORM 1.2, SCORM 2004 and SCORM Dispatch on the LearnPress LMS by integrating with Gra …
200+ installs5.0★ (1)updated 20 May 2026
Compare side by side Experience API for LifterLMS by Grassblade
This plugin enables the Experience API (xAPI / Tin Can) , SCORM 1.2 and SCORM 2004 support on the LifterLMS by integrating with GrassBlade xAPI Compan …
100+ installsupdated 23 Apr 2026
Compare side by side Experience API for WP Courseware by Grassblade
This plugin enables the Experience API (xAPI / Tin Can), cmi5, SCORM 1.2 and SCORM 2004 support on the WP Courseware LMS by integrating with GrassBlad …
50+ installsupdated 11 Sep 2025
Compare side by side Experience API for MasterStudy by GrassBlade
This plugin enables the Experience API (xAPI / Tin Can) , SCORM 1.2, SCORM 2004 cmi5 standard content support on the MasterStudy LMS by integrating wi …
30+ installsupdated 26 Oct 2025
Compare side by side Experience API for Sensei LMS by GrassBlade
This plugin enables the Experience API (xAPI / Tin Can) , SCORM 1.2 and SCORM 2004 support on the Sensei LMS by integrating with GrassBlade xAPI Compa …
20+ installs2.0★ (1)updated 11 Sep 2025
Compare side by side Experience API for GamiPress by Grassblade
This plugin enables Experience API (xAPI) tracking of Gamification data generated using GamiPress plugin.
10+ installsupdated 11 Sep 2025
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 WP Experience API: a person reads every submission, and corrections get a reply within 5 business days.