Plugin profile · observed daily since 02 Aug 2026
CodeMirror for CodeEditor
Active installs40+ rounded
Current authorredcocker
Owner changesNone while we have been watching
Last release14 years ago 28 Mar 2012
Support— no recent threads
Releases on record12
Rating— no ratings yet
Added to directory01 Oct 2011
Requires WP2.8
Requires PHPfalse
Version lag3.8 behind
Tested up toWP 3.3.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 redcocker 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 |
|---|---|---|---|
| redcocker | 12 | 01 Oct 2011 | 28 Mar 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: 40+ 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.
08 Aug 2026peak 11/day28 Aug 2026
No ratings on record, so there is no sentiment to report.
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 | 15 Aug | 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Unchanged throughout: ratings total (0) · active installs (40+) · version (0.5.6.1) · support threads (0) · threads resolved (0)
27 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 directory14 years ago 01 Oct 2011
Requires WP2.8
Requires PHPfalse
Version lag3.8 behind
Is anyone still maintaining this?
- No release in 5,267 days (14.4 years). The last was 28 Mar 2012.
- Declares compatibility only up to WordPress 3.3.2, while 7.1 is current. The author has not confirmed it runs on the last 38 releases.
- The same account maintains 7 other plugins, and none has been updated in over a year, the most recent on 08 Nov 2013.
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.
- 19 Sep 201312 years agoDormancy threshold crossed540 days since the last release (2012-03-28). Dormancy is a maintenance observation, not a judgement about the owner.
- 28 Mar 201214 years agoVersion 0.5.6.1 released
- 01 Mar 201214 years agoVersion 0.5.6 releasedfrom the release logCommitted by redcocker.
- 04 Feb 201214 years agoVersion 0.5.5 releasedfrom the release logCommitted by redcocker.
- 18 Jan 201214 years agoVersion 0.5.3 releasedfrom the release logCommitted by redcocker.
- 12 Jan 201214 years agoVersion 0.5 releasedfrom the release logCommitted by redcocker.
- 23 Nov 201114 years agoVersion 0.4.5 releasedfrom the release logCommitted by redcocker.
- 30 Oct 201114 years agoVersion 0.4 releasedfrom the release logCommitted by redcocker.
- 26 Oct 201114 years agoVersion 0.3.6 releasedfrom the release logCommitted by redcocker.
- 14 Oct 201114 years agoVersion 0.3.5 releasedfrom the release logCommitted by redcocker.
- 09 Oct 201114 years agoVersion 0.3 releasedfrom the release logCommitted by redcocker.
- 03 Oct 201114 years agoVersion 0.2 releasedfrom the release logCommitted by redcocker.
- 01 Oct 201114 years agoVersion 0.1 releasedfrom the release logCommitted by redcocker.
- 01 Oct 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 redcocker for all 27 days we have observed it.
- It was last released 14 years ago (28 Mar 2012).
- Its author declares it tested up to WordPress 3.3.2; WordPress is now on 7.1.
- WordPress.org reports 40+ 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 Block Pro – Beautiful Syntax Highlighting
Code highlighting powered by the VS Code engine. Performance focused. No bloat.
10,000+ installs4.8★ (50)updated 15 Aug 2026
Compare side by side WP SyntaxHighlighter
This plugin is code syntax highlighter based on SyntaxHighlighter ver. 3.0.83 and 2.1.382.
300+ installs5.0★ (1)updated 29 Feb 2012
no release in over 18 months
Compare side by side SyntaxHighlighter Evolved
Easily post syntax-highlighted code to your site without having to modify the code at all. As seen on WordPress.com.
20,000+ installs4.3★ (86)updated 03 Mar 2025
no release in over 18 months
Compare side by side CodeColorer
Syntax highlighting for code snippets in posts, comments, and RSS, with inline code, themes, and line numbers.
1,000+ installs4.9★ (11)updated 15 Aug 2026
Compare side by side Auto SyntaxHighlighter
Auto SyntaxHighlighter is a WordPress Code highlight plugin. Use editor botton, in the pop-up window, paste or write your code, oh, very simple.
100+ installs4.3★ (6)updated 07 May 2012
no release in over 18 months
Compare side by side Advance Custom HTML – Show Off Code Snippets with Live Preview
Display HTML, CSS, JavaScript, PHP & Python code snippets in WordPress with live preview, syntax highlighting, and a copy button.
10,000+ installs2.5★ (4)updated 11 Aug 2026
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 CodeMirror for CodeEditor: a person reads every submission, and corrections get a reply within 5 business days.