Plugin profile · observed daily since 02 Aug 2026
Log-Hero.com Plugin
Active installs10+ rounded
Current authorLog Hero
Owner changesNone while we have been watching
Last release15 days ago 20 Aug 2026
Support— no recent threads
Releases on record7
Rating5.0 /5 · 1
Added to directory14 Jun 2018
Requires WP6.0
Requires PHP7.4
Version lag0 up to date
Tested up toWP 7.1 up to date
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 Log Hero 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 |
|---|---|---|---|
| loghero | 7 | 14 Jun 2018 | 20 Aug 2026 |
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.
3 downloads a day over the last 7 days, falling 27% 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 29/day04 Sep 2026
Install band fell to 10+ on 23 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 | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 13 | 0 | 0 |
| Active installs | 20+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ | 10+ |
Unchanged throughout: ratings total (1) · version (0.3.0) · support threads (0) · threads resolved (0)
34 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 directory8 years ago 14 Jun 2018
Requires WP6.0
Requires PHP7.4
Version lagcurrent
Is anyone still maintaining this?
- Last released 20 Aug 2026, 15 days ago.
- Declares compatibility with WordPress 7.1, which is current.
- Log Hero 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.
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.
- 20 Aug 202615 days agoVersion 0.3.0 released
- 20 Aug 202615 days agoReleased after a long silenceA new release arrived 2,815 days after the previous one (2018-12-05). A break in dormancy is a maintenance observation, not a judgement about the release or the owner.
- 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.
- 28 May 20206 years agoDormancy threshold crossed540 days since the last release (2018-12-05). Dormancy is a maintenance observation, not a judgement about the owner.
- 05 Dec 20187.5 years agoVersion 0.2.5 released
- 18 Oct 20187.5 years agoVersion 0.2.4 releasedfrom the release logCommitted by loghero.
- 13 Sep 20187.5 years agoVersion 0.2.3 releasedfrom the release logCommitted by loghero.
- 13 Aug 20188 years agoVersion 0.2.2 releasedfrom the release logCommitted by loghero.
- 31 Jul 20188 years agoVersion 0.2.1 releasedfrom the release logCommitted by loghero.
- 14 Jun 20188 years agoVersion 0.2.0 releasedfrom the release logCommitted by loghero.
- 14 Jun 20188 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 Log Hero for all 34 days we have observed it.
- It was last released 15 days ago (20 Aug 2026).
- Its author declares it tested up to WordPress 7.1, which is current.
- 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.
Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning
Smart WordPress security that blocks bots automatically, guides you to what matters, and repairs problems — without drowning you in noise.
30,000+ installs4.8★ (1,038)updated 27 Aug 2026
Compare side by side Temso AI
Stream front-end request logs from your WordPress origin to Temso so AI-crawler and bot traffic shows up in your dashboard.
20+ installsupdated 23 Aug 2026
Compare side by side Block AI Crawlers
Adds robots.txt rules blocking AI crawlers and AI bots.
1,000+ installs4.4★ (8)updated 30 Aug 2026
Compare side by side Serve Markdown
Serve Markdown versions of your posts and pages to AI agents and crawlers. Content negotiation, .md URLs, auto-discovery, and crawler logging.
80+ installsupdated 15 Mar 2026
Compare side by side ACF Content Analysis for Yoast SEO
WordPress plugin that adds the content of all ACF fields to the Yoast SEO score analysis.
100,000+ installs4.1★ (35)updated 18 Aug 2026
Compare side by side CF LLMS Stats Tracker
Generates a dynamic llms.txt file for AI crawlers and tracks visitor statistics with detailed bot analysis.
20+ installsupdated 08 Jan 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 Log-Hero.com Plugin: a person reads every submission, and corrections get a reply within 5 business days.