Plugin Pulse Beta
← Pulse
H

Honeypot Comments

by gh0stpr3ss · Security

Plugin to stop most comment spam by adding in a simple honeypot for spam bots to get caught in.

Try it live opens a temporary test site in your browser, which can take about 20 seconds to load. Plugins that rely on outside services or a full server may not work completely there.

⚠ Stale⚠ Likely abandoned⚠ Few reviews

Health

D 40/100

Stale · Likely abandoned · Few reviews

Active installs

60+

≈68 estimated

Momentum

+12%

downloads vs prior 30d

Biggest opportunity: “comments” and “spam” aren't earning a slot. You list them, but you're not in the first 24 results for those searches. WordPress.org counts only your first five tags, so free the slot for a search you can win.

How scoring works →
40 Health · D
Maintenance 3/100
Rating quality 62/100
Support 70/100

40 health vs 66 average across 1,778 Security plugins

Install conversion

How it's measured →

0.9%

of downloads still active

At least 60 of 6.7K lifetime downloads are still running, below its category: the median Security plugin keeps 1.4%, across 1,061 plugins.

Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other Security plugins, not across the directory. wp.org reports active installs as the bottom of a band, so the real rate is this or higher.

High removal-risk signals

63/100

Maintenance and integrity signals that tend to precede a WordPress.org removal. Not an official status, a heads-up to act.

  • Long abandoned. No update in 12+ years — the top precursor to removal once a vulnerability is found.
  • Compatibility drift. Tested only up to WordPress 3.9.40, well behind 6.8.

Details

Version
1.1.0
Last updated
12.4y ago
Added
2014-06-11 · 12 yrs old
Requires WP
3.5.1
Tested up to
3.9.40
Requires PHP
—

Directory ranking optimization

How it's scored →

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

29 / 100

Under-optimized

Most to gain: Update recency

Update recency 0/100

Updated 4521 days ago, past the ~180 days where wp.org starts discounting

WP compatibility 3/100

Tested up to WordPress 3.9.40; the current branch is 6.8

Rating quality 53/100

2.3★ over 4 reviews, smoothed to 3.97★ and held back under 25 reviews

Listing tuning 68/100

2 of 5 tags set · short description in place

To rank higher: Last updated 4521 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.

Get the full rank-higher report →

Daily downloads

Since 5 Oct 2022 · 1,489 days · wp.org + Plugin Pulse archive

+12% vs prior 30d
51 Nov 2026

30-day downloads

Rolling 30-day volume · peak 79 · peaks are release surges

632 Nov 2026

Directory rank

Ranked about #19,000 to #20,000, alongside the other plugins at 60+ installs. Plugins with the same install count swap places between wp.org requests, so this is where most of them sit. Checked monthly, last on 1 Nov 2026.

Rating trend

Star average over time · dips mark rough releases

2.32 Nov 2026

Update activity

Downloads in the last 30 days for every 1,000 active sites.

Not enough installs to measure. This needs at least 100 active sites; below that, a handful of downloads reads as tens of thousands.

Release cadence

No release in a year
from wp.org release tags

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

0

releases in the last 12 months

12.4y ago

latest release · v1.1.0 · 17 Jun 2014

1

tagged releases on record

Recent releases

1.1.0 · 17 Jun 2014

What its installed base runs

via wordpress.org

Share of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

v1.1 100%

Estimated active installs

The public count shows “60+”. Our estimate pins where the real number sits.

tracked estimate
60–70 ≈68

Crossed into this band 2 months ago and a band this size takes about a year or more to cross, so the real count is still just under 70.

Install history since 23 Jan 2021

602 Nov 2026

Recent reviews

All reviews on wp.org ↗
  1. ★★★★★ RoamingPro
    10.9y ago

    I’ve been interested in the Honey Pot concept for eliminating SPAM comments. I didn’t really delve into the code of this plugin to see what it was trying to do, all I know is that it is totally ineffective on several of my sites.

    Read on wp.org ↗
  2. ★★★★★ jimbtek
    12.3y ago

    I am optimistic this plugin can get better, but right now it fails to block spambots for me on 3.9.1 with the Divi 2.0 theme. It does technically work and injects this code: <!-- the following input field has been added by the Honeypot Comments plugin to thwart spambots --> <input type="hidden" id="N1KaIulBlvp509a2NJsytPMGf" name="0r65HysCNM1H7w5xP5nXTUjhF" /> </form> </div> But i still get multiples spam comments a day in WP that are selling purses and all sorts of stuff. I am happy to try it again if there is a update that takes taekvideo’s comments into consideration and really makes it less obvious. Perhaps make it all called ’email-address’ or something and hide it.

    Read on wp.org ↗
  3. ★★★★★ taekvideo
    12.3y ago

    Just a few things… #1 if ( ! empty( $_POST['honeypot-comments'] ) ) How would this ever execute if the id and name of your honeypot are 25 character random strings? #2 <input type="hidden" id="'. RandomString(25) .'" name="'. RandomString(25) .'" />'; Bots aren’t really going to fill out a type=”hidden” field… that’s more of a vinegarpot than a honeypot. You should make it a textarea to entice them, and hide it from real users with css (or javascript is even better) #3 Even if both of those are done right, some spambots will still get through because they ignore the form you send them and just POST a standard WordPress form. To block those, you’d need to change the “name” attribute of the comment textarea to something else… which is a bit of a pain to do without breaking anything but it’s possible.

    Read on wp.org ↗
  4. ★★★★★ NickGoodchild
    12.4y ago

    I have been using Askimet but finding it increasingly falling behind and needing me to invest a lot of work to keep up to it. Unfortunately, sometimes I just can’t. I started playing with different options, including looking at blocking a huge number of IPs from visiting my site (which didn’t actually cut down the number of comments I was receiving as much as I hoped and did seem to affect traffic disproportionately to the decrease in spam comments) and deleting comments direct from the database (which may have cost me some legitimate comments.) This, so far, is working like a charm. As near as I can tell there isn’t any real server overhead for the plug in and my spam comments have fallen to zero. Of course, as soon as bots get wise to it I am in real trouble . . .

    Read on wp.org ↗

AI assistants

How it's measured →

Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.

Not measured yet for this plugin’s topics. Its tracked searches are not among the measured topics. See the topics measured so far.

Readme readiness

2 of 8 pass · checked 31 Oct 2026

Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.

  • ! Says what it does Short description names no action; say what the plugin does for the site.
  • ! Has a FAQ Only 2 questions in the FAQ; 3 or more gives an assistant something to match.
  • ! FAQ asks real questions 0 of 2 FAQ entries are headings, not questions ("undefined").
  • ! Names who it is for Never says who the plugin is for or what they use it for.
  • ! Names what it works with Names no plugin, service or platform it works with.
  • ! Headings and lists 1 heading and 0 lists; assistants quote headed sections and bullet lists, not paragraphs.
  • ✓ Enough to quote 1,079 characters of description.
  • ✓ Tags match the text All 2 tags appear in the text.

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

  1. 2026-08-31 70+ → 60+ down after 195 days in tier
  2. 2026-02-17 80+ → 70+ down after 94 days in tier
  3. 2025-11-15 90+ → 80+ down after 137 days in tier
  4. 2025-07-01 100+ → 90+ down after 17 days in tier
  5. 2025-06-14 90+ → 100+ up after 32 days in tier
  6. 2025-05-13 100+ → 90+ down after 35 days in tier
  7. 2025-04-08 90+ → 100+ up after 16 days in tier
  8. 2025-03-23 100+ → 90+ down after 10 days in tier

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

Embed this report card

Drop a live Pulse card for Honeypot Comments into a readme, a review or a deck. It updates itself.

<iframe src="https://plugins.wpmayor.com/embed/honeypot-comments" width="480" height="300" style="border:0" loading="lazy" title="Honeypot Comments — Plugin Pulse"></iframe>
Preview card ↗

Honeypot Comments: 60+ active installs, 2.3★ (4 reviews). Plugin Pulse (WP Mayor), as of 2026-11-02. https://plugins.wpmayor.com/plugin/honeypot-comments

Spotted a number that looks wrong? Report a data issue and we'll check it against the source.