Plugin profile · observed daily since 02 Aug 2026
Jeba Limit Login Attempts
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 Md Jahed throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
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.
Small but established: 100+ active installs. Enough sites to show it works in the wild, too few for adoption to say much on its own.
3 downloads a day over the last 7 days, rising 100% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
Install band rose to 100+ on 22 Aug 2026, from 90+. 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 | 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 | 29 Aug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 11 | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 11 | 0 |
| Active installs | 100+ | 100+ | 100+ | 100+ | 100+ | 90+ | 100+ | 100+ | 100+ | 100+ | 100+ | 100+ | 100+ | 100+ |
Unchanged throughout: ratings total (6) · version (1.0) · support threads (0) · threads resolved (0)
28 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?
- No release in 4,170 days (11.4 years). The last was 31 Mar 2015.
- Declares compatibility only up to WordPress 4.0.38, while 7.1 is current. The author has not confirmed it runs on the last 31 releases.
- The same account maintains 18 other plugins, and none has been updated in over a year, the most recent on 04 Dec 2015.
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.
- 21 Aug 20268 days agoInstall band moved to 90+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 202627 days agoInstall band moved to 100+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 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.
- 21 Sep 20169.5 years agoDormancy threshold crossed540 days since the last release (2015-03-31). Dormancy is a maintenance observation, not a judgement about the owner.
- 31 Mar 201511 years agoVersion 1.0 released
- 20 Mar 201511 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 Md Jahed for all 28 days we have observed it.
- It was last released 11 years ago (31 Mar 2015).
- Its author declares it tested up to WordPress 4.0.38; WordPress is now on 7.1.
- WordPress.org reports 100+ active installs.
- It carries 6 ratings, averaging 3.8 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.
Login security: KeyLockr SSO scan login, 2FA, passwordless login, Cloudflare Turnstile, GeoLocation/IP limits, whitelist and blacklist.
WordPress login security with brute force protection, Two-factor authentication (2FA/MFA), firewall, IP/country blocking, and login monitoring
Enforce WordPress login and password security policies to protect user accounts and prevent unauthorized logins.
Protect your WordPress website from brute force attacks by limiting the number of failed login attempts. Improve security and stop bots.
Stop brute force attacks for free. Limit login attempts, add 2FA and reCAPTCHA, hide wp-login.php, block IPs and see every login on your site.
Essential security: password protection, AI crawler blocking, login limits, country restrictions, CPU monitoring & live-preview login customizer.
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 Jeba Limit Login Attempts: a person reads every submission, and corrections get a reply within 5 business days.