Plugin profile · observed daily since 02 Aug 2026
WP fail2ban – Advanced Security
PluginsPedia 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 invisnet 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 |
|---|---|---|---|
| invisnet | 47 | 19 Oct 2012 | 29 Apr 2025 |
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.
Widely adopted: 60,000+ active installs. Among the more broadly installed plugins in the directory.
1,274 downloads a day over the last 7 days, falling 70% 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 | 18 Oct | 19 Oct | 20 Oct | 21 Oct | 22 Oct | 23 Oct | 24 Oct | 25 Oct | 26 Oct | 27 Oct | 28 Oct | 29 Oct | 30 Oct | 31 Oct |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 293 | 861 | 1,127 | 21,296 | 4,028 | 1,554 | 1,104 | 929 | 2,104 | 1,296 | 693 | 1,768 | 1,026 |
| Version | 5.4.2 | 5.4.2 | 5.4.2 | 5.5.0 | 5.5.0 | 5.5.0 | 5.5.0 | 5.5.0 | 5.5.0 | 5.5.0 | 5.5.0 | 5.5.0 | 5.5.0 | 5.5.0 |
Unchanged throughout: ratings total (71) · active installs (60,000+) · support threads (1) · threads resolved (0)
91 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?
- Last released 20 Oct 2026, 19 days ago.
- Declares compatibility with WordPress 7.1.4, which is current.
- 0 of 1 support threads answered in the last two months.
- The same account maintains 9 other plugins, and none has been updated in over a year, the most recent on 01 May 2025.
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.
- 21 Oct 202618 days agoDormancy threshold crossed540 days since the last release (2025-04-29). Dormancy is a maintenance observation, not a judgement about the owner.
- 20 Oct 202619 days agoVersion 5.5.0 released
- 30 Sep 20261 month agoVersion 5.4.2 released
- 02 Aug 20263 months agoFirst observed by PluginsPediaDaily 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.
- 29 Apr 202518 months agoVersion 5.4.1 released
- 28 Jan 202521 months agoVersion 5.4.0.1 releasedfrom the release logCommitted by invisnet.
- 27 Jan 202521 months agoVersion 5.4.0 releasedfrom the release logCommitted by invisnet.
- 10 Nov 20241.5 years agoVersion 5.3.4 releasedfrom the release logCommitted by invisnet.
- 17 Oct 20242 years agoVersion 5.3.3 releasedfrom the release logCommitted by invisnet.
- 05 Aug 20242 years agoVersion 5.3.2 releasedfrom the release logCommitted by invisnet.
- 28 Jul 20242 years agoVersion 5.3.1 releasedfrom the release logCommitted by invisnet.
- 12 Jul 20242 years agoVersion 5.3.0 releasedfrom the release logCommitted by invisnet.
- 04 Apr 20242.5 years agoVersion 5.2.2.1 releasedfrom the release logCommitted by invisnet.
- 28 Jan 20242.5 years agoVersion 5.2.2 releasedfrom the release logCommitted by invisnet.
- 21 Sep 20233 years agoVersion 5.2.1 releasedfrom the release logCommitted by invisnet.
- 13 Aug 20233 years agoVersion 5.2.0 releasedfrom the release logCommitted by invisnet.
- 05 Jul 20233 years agoVersion 5.1.1 releasedfrom the release logCommitted by invisnet.
- 19 Oct 201214 years ago34 earlier releasesfrom the release logBetween 19 Oct 2012 and 18 Jun 2023. Listed individually in the public release log rather than here.
- 19 Oct 201214 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 invisnet for all 91 days we have observed it.
- It was last released 18 days ago (20 Oct 2026).
- Its author declares it tested up to WordPress 7.1.4, which is current.
- WordPress.org reports 60,000+ active installs.
- It carries 71 ratings, averaging 4.2 out of 5.
- 0 of 1 support threads in the last two months are marked resolved.
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.
WordPress login security with brute force protection, Two-factor authentication (2FA/MFA), firewall, IP/country blocking, and login monitoring
Hide My WP Ghost is a WordPress security plugin that hides WP paths and protects your site with Path Security, Firewall, Brute Force Protection, 2FA
XO Security is a plugin to enhance login related security.
This Anti-Malware scanner searches for Malware, Viruses, and other security threats and vulnerabilities on your server and it helps you fix them.
Secure your WordPress site from brute-force attacks, threats, malware, and bots. Free to use and easy to set up.
Protect WordPress from malware, hackers, brute-force attacks & suspicious traffic. Includes firewall, login security, 2FA & vulnerability checks.
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 WP fail2ban – Advanced Security: a person reads every submission, and corrections get a reply within 5 business days.