Plugin profile · observed daily since 02 Aug 2026

AIM Style Vault

Active installs10+ rounded
Current authorAIMScott
Owner changesNone while we have been watching
Last release13 years ago 01 Jun 2013
Support no recent threads
Releases on record1
Rating5.0 /5 · 1
Added to directory01 Jun 2013
Requires WP3.0
Requires PHPfalse
Version lag3.6 behind
Tested up toWP 3.5.2 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 AIMScott throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.

Full observed history, including every field transition

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.

3 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 11/day15 Sep 2026
5.0
out of 5
1 rating
51100%
400%
300%
200%
100%

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.

Field02 Sep03 Sep04 Sep05 Sep06 Sep07 Sep08 Sep09 Sep10 Sep11 Sep12 Sep13 Sep14 Sep15 Sep
Downloads that day000000110000110

Unchanged throughout: ratings total (1) · active installs (10+) · version (1.0.0) · support threads (0) · threads resolved (0)

45 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 directory13 years ago 01 Jun 2013
Requires WP3.0
Requires PHPfalse
Version lag3.6 behind

Is anyone still maintaining this?

  • No release in 4,854 days (13.3 years). The last was 01 Jun 2013.
  • Declares compatibility only up to WordPress 3.5.2, while 7.1 is current. The author has not confirmed it runs on the last 36 releases.
  • AIMScott 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.

  1. 02 Aug 20261 month ago
    First 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.
  2. 23 Nov 201411 years ago
    Dormancy threshold crossed540 days since the last release (2013-06-01). Dormancy is a maintenance observation, not a judgement about the owner.
  3. 01 Jun 201313 years ago
    Version 1.0.0 released
  4. 01 Jun 201313 years ago
    Added 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 AIMScott for all 45 days we have observed it.
  • It was last released 13 years ago (01 Jun 2013).
  • Its author declares it tested up to WordPress 3.5.2; WordPress is now on 7.1.
  • WordPress.org reports 10+ active installs.
  • It carries 1 rating, averaging 5.0 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.

Custom CSS Pro

Professional real-time CSS editor for those who want to code CSS.

7,000+ installs5.0★ (15)updated 23 Aug 2026
customcss
Custom Body Class

A plain simple plugin which allows you to add a custom CSS class the HTML body tag.

10,000+ installs5.0★ (21)updated 27 Jul 2025
customcss
Classic Editor

Enables the previous "classic" editor and the old-style Edit Post screen with TinyMCE, Meta Boxes, etc. Supports all plugins that extend this screen.

8,000,000+ installs4.9★ (1,247)updated 28 May 2026
editor
Simple CSS

Add CSS to your website through an admin editor, the Customizer or a metabox for page/post specific CSS.

80,000+ installs4.9★ (60)updated 15 Sep 2025
css
Live CSS Preview

Live front-end and Customizer CSS editing powered by native WordPress Additional CSS storage.

300+ installs5.0★ (2)updated 06 Apr 2026
csseditor
Classic Widgets

Enables the previous "classic" widgets settings screens in Appearance - Widgets and the Customizer. Disables the block editor from managing widgets.

2,000,000+ installs4.9★ (272)updated 08 Dec 2025
editor

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 AIM Style Vault: a person reads every submission, and corrections get a reply within 5 business days.

The record is never silently edited, and your email is never published.