Plugin profile · observed daily since 02 Aug 2026
WP Autoload
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 invisnet 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 |
|---|---|---|---|
| invisnet | 14 | 25 Nov 2011 | 22 Sep 2012 |
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: 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.
0 downloads a day over the last 7 days, falling 100% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
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 | 16 Aug | 17 Aug | 18 Aug | 19 Aug | 20 Aug | 21 Aug | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Unchanged throughout: ratings total (0) · active installs (0+) · version (2.5.1) · support threads (0) · threads resolved (0)
28 days of observation, most recent 14 shown.
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 5,089 days (13.9 years). The last was 22 Sep 2012.
- Declares compatibility only up to WordPress 3.4.2, while 7.1 is current. The author has not confirmed it runs on the last 37 releases.
- The same account maintains 9 other plugins, and none has been updated in over a year, the most recent on 01 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 202627 days 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.
- 16 Mar 201412 years agoDormancy threshold crossed540 days since the last release (2012-09-22). Dormancy is a maintenance observation, not a judgement about the owner.
- 22 Sep 201213 years agoVersion 2.5.1 released
- 10 Sep 201213 years agoVersion 2.5.0 releasedfrom the release logCommitted by invisnet.
- 28 Feb 201214 years agoVersion 2.1.2 releasedfrom the release logCommitted by invisnet.
- 28 Feb 201214 years agoVersion 2.1.3 releasedfrom the release logCommitted by invisnet.
- 25 Feb 201214 years agoVersion 2.1.0 releasedfrom the release logCommitted by invisnet.
- 25 Feb 201214 years agoVersion 2.1.1 releasedfrom the release logCommitted by invisnet.
- 11 Jan 201214 years agoVersion 2.0.0 releasedfrom the release logCommitted by invisnet.
- 30 Nov 201114 years agoVersion 1.1.1 releasedfrom the release logCommitted by invisnet.
- 28 Nov 201114 years agoVersion 1.0.1 releasedfrom the release logCommitted by invisnet.
- 28 Nov 201114 years agoVersion 1.0.2 releasedfrom the release logCommitted by invisnet.
- 28 Nov 201114 years agoVersion 1.0.3 releasedfrom the release logCommitted by invisnet.
- 28 Nov 201114 years agoVersion 1.0.4 releasedfrom the release logCommitted by invisnet.
- 28 Nov 201114 years agoVersion 1.1.0 releasedfrom the release logCommitted by invisnet.
- 25 Nov 201114 years ago1 earlier releasesfrom the release logBetween 25 Nov 2011 and 25 Nov 2011. Listed individually in the public release log rather than here.
- 24 Nov 201114 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 invisnet for all 28 days we have observed it.
- It was last released 13 years ago (22 Sep 2012).
- Its author declares it tested up to WordPress 3.4.2; WordPress is now on 7.1.
- 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
- 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.
Code Embed provides a very easy and efficient way to embed code (JavaScript, CSS and HTML) in your posts and pages.
A lightweight plugin that automatically minifies, compresses, and caches HTML, CSS, and JavaScript on demand to improve your website’s load speed.
The growing library of 300+ ready-to-use templates that work with all WordPress themes including Astra, Hello, OceanWP, GeneratePress and more
Extend Elementor with 68+ widgets, 114 prebuilt demos, Mega Menu Builder, Theme Builder, and advanced interactive effects.
Access 100+ Gutenberg templates and ready-to-use starter sites for WordPress. All designs work with the Neve theme. One-click import, fully responsive …
WP Custom CSS JS plugin allows you to add any HTML, CSS, Javascript, jQuery or Tracking Pixel easily on your wordpress site right from your dashboard.
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 Autoload: a person reads every submission, and corrections get a reply within 5 business days.