Plugin Pulse
← Pulse

Authentication Code

by Mitch · Uncategorized

Also makes 10 other plugins · 10.6K+ installs across the portfolio →

Adds an authentication field to your login form for better security.

⚠ Stale⚠ Likely abandoned⚠ Few reviews
How scoring works →
45 Health · D
Maintenance 3/100
Rating quality 74/100
Support 70/100

45 health vs 56 average across 16,376 Uncategorized plugins

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 9+ years — the top precursor to removal once a vulnerability is found.
  • Compatibility drift. Tested only up to WordPress 4.7.35, well behind 6.8.

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.

37 / 100

Under-optimized

Biggest win: Update recency

Update recency 0/100
WP compatibility 8/100
Rating quality 51/100
Listing tuning 100/100

To rank higher: Last updated 3590 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 2022-10-05 · 1,426 days · wp.org + Plugin Pulse archive

+16% vs prior 30d
3Downloads · Aug 26

30-day downloads

Rolling 30-day volume · peaks are release surges

167

now · peak 167

16730d downloads · Aug 26

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

Authentication Code · #17544 you WPCode · #19 Code Snippets · #35 Head & Footer Code · #287

Update activity

How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.

2.1Kper 1k installs · Aug 26

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

9.8y ago

latest release · v1.2.1

4

tagged releases on record

Recent releases

1.2.1 · 9.8y ago1.2.0 · 10.1y ago1.0.1 · 10.1y ago1.0 · 10.1y ago

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.2 100%

Estimated active installs

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

tracked estimate
80–90 ≈87

Refined from the date this plugin crossed into its current band.

Install history · since 2016-12-25 · 1,390 observations

80Installs · Aug 26

Estimated value

What this plugin might earn a year, and what it might sell for. Modeled from public signals; we don't see anyone's books.

Est. annual revenue

N/A

Est. acquisition value

N/A

No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price. A small install base leaves thin data to model from.

Details

Version
1.2.1
Last updated
9.8y ago
Added
2016-07-21 · 10 yrs old
Requires WP
3.0
Tested up to
4.7.35
Requires PHP

Recent reviews

All reviews on wp.org ↗
  1. nick6352683
    10.1y ago

    This is a very useful plugin, however there is a HUGE problem. THe moment this is fixed, I will rate it 5 stars immediately… So this is the problem: – You set the auth. key and everything works fine. – Then you go back to the settings screen, and remove the auth key from the field. having an empty field, and save that setting. The plugin is them disabled, but not entirely, and that’s the problem. What is disable? In the login screen, the Auth. field is disabled as it should. So there is no way to enter the Auth. key. What is the problem? When you try to logon now, you get an error message that that Auth. key is empty, and entry is denied. How is this possible when the plugin should be disabled if you have a blank Auth. key? This needs to be fixed please… otherwise this is a must use plugin for me. UPDATE: I can confirm the fix, so I’m updating my rating from 4 stars to 5. Thanks.

    Read on wp.org ↗

Behavioral tests

via WP Hive

Automated install-time checks, tested on PHP 7.2.16 · WP 5.2.4

Low memory footprint
Low page-speed impact
Runs on latest PHP + WP
No PHP errors
No JS errors
Activates cleanly
No resource errors
No external HTTP errors
Optimized database use
Frequently updated

Growth timeline

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

  1. 2026-06-13 90+ → 80+ down after 29 days in tier
  2. 2026-05-15 100+ → 90+ down after 1080 days in tier
  3. 2023-05-31 200+ → 100+ down after 1 days in tier
  4. 2023-05-30 100+ → 200+ up after 8 days in tier
  5. 2023-05-22 200+ → 100+ down

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).

Compare head to head →

Embed this report card

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

<iframe src="https://plugins.wpmayor.com/embed/authentication-code" width="480" height="300" style="border:0" loading="lazy" title="Authentication Code — Plugin Pulse"></iframe>
Preview card ↗

Authentication Code: 80+ active installs, 5.0★ (1 reviews). Plugin Pulse (WP Mayor), as of 2026-08-31. https://plugins.wpmayor.com/plugin/authentication-code