Plugin profile · observed daily since 02 Aug 2026
Js Css Include Manager
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 gqevu6bsiz 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 |
|---|---|---|---|
| gqevu6bsiz | 14 | 26 Mar 2013 | 24 Sep 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: 30+ 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 | 25 Aug | 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Unchanged throughout: ratings total (2) · active installs (30+) · version (1.4.4) · support threads (0) · threads resolved (0)
37 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 4,002 days (11.0 years). The last was 24 Sep 2015.
- Declares compatibility only up to WordPress 4.3.34, while 7.1 is current. The author has not confirmed it runs on the last 28 releases.
- The same account maintains 12 other plugins, 1 of which was updated in the last 90 days. the account is active.
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 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.
- 17 Mar 20179.5 years agoDormancy threshold crossed540 days since the last release (2015-09-24). Dormancy is a maintenance observation, not a judgement about the owner.
- 24 Sep 201510 years agoVersion 1.4.4 released
- 13 May 201511 years agoVersion 1.4.3 releasedfrom the release logCommitted by gqevu6bsiz.
- 16 Feb 201511 years agoVersion 1.4.2 releasedfrom the release logCommitted by gqevu6bsiz.
- 26 Dec 201411 years agoVersion 1.4.1 releasedfrom the release logCommitted by gqevu6bsiz.
- 12 Sep 201411 years agoVersion 1.4 releasedfrom the release logCommitted by gqevu6bsiz.
- 29 Dec 201312 years agoVersion 1.3.3.1 releasedfrom the release logCommitted by gqevu6bsiz.
- 16 Dec 201312 years agoVersion 1.3.3 releasedfrom the release logCommitted by gqevu6bsiz.
- 08 Aug 201313 years agoVersion 1.3.2 releasedfrom the release logCommitted by gqevu6bsiz.
- 18 Jul 201313 years agoVersion 1.3.1.1 releasedfrom the release logCommitted by gqevu6bsiz.
- 14 Jul 201313 years agoVersion 1.3.1 releasedfrom the release logCommitted by gqevu6bsiz.
- 13 Jul 201313 years agoVersion 1.3 releasedfrom the release logCommitted by gqevu6bsiz.
- 11 May 201313 years agoVersion 1.2 releasedfrom the release logCommitted by gqevu6bsiz.
- 11 May 201313 years agoVersion 1.2.1 releasedfrom the release logCommitted by gqevu6bsiz.
- 26 Mar 201313 years ago1 earlier releasesfrom the release logBetween 26 Mar 2013 and 26 Mar 2013. Listed individually in the public release log rather than here.
- 21 Oct 201213 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 gqevu6bsiz for all 37 days we have observed it.
- It was last released 10 years ago (24 Sep 2015).
- Its author declares it tested up to WordPress 4.3.34; WordPress is now on 7.1.
- WordPress.org reports 30+ active installs.
- It carries 2 ratings, 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.
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.
A great way to insert and manage custom code (CSS, JS, meta tags, etc.) into website before </head>, after <body> or before </body>.
The ultimate snippet manager for WordPress. Create and manage custom HTML, CSS, or JS code snippets and control where and when they are displayed.
Create custom "Shortcodes" easily for HTML, JavaScript, CSS code snippets and use the shortcodes within posts, pages & widgets
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 Js Css Include Manager: a person reads every submission, and corrections get a reply within 5 business days.