Census › Plugin profiles › Limit Login Attempts
Limit Login Attempts
Figures from the Plugin Directory Census · as of 28 Aug 2026
300,000
Active installs, lower bound
Group: 100,000 to 999,999 installs
1,242
Days since the last release
Group median: 12
4.6
out of 5, from 202 ratings
Group median: 4.7 (10+ ratings)
no threads
Support threads, two months
Group: 68.2%
Full profile on wordpress.orgShow on the mapCompare with your own plugins
What is Limit Login Attempts and who is behind it?
Limit Login Attempts is a WordPress plugin in the “Security” field, made by Automattic. It has been listed in the directory since 15 Jan 2009, so for 17 years. Automattic has 24 plugins with at least 10,000 installs in the census. With 300,000 to 399,999 active installs it belongs to the 100,000 to 999,999 installs group; its last release came 1,242 days before the reference date, and it is tested up to WordPress 6.2.
This is how the author describes the plugin on wordpress.org:
“Limit rate of login attempts, including by way of cookies, for each IP. Fully customizable.”
Self-description on wordpress.org, retrieved on 10 Sept 2026
When was Limit Login Attempts last released?
The last release of Limit Login Attempts came 1,242 days before the reference date; the group median is 12 days. That makes Limit Login Attempts silent in the census, meaning no release for more than 365 days, as are 5.3% of the group.
How many installs does Limit Login Attempts have?
Limit Login Attempts had 300,000 to 399,999 active installs on the reference date. Within its group, 88 plugins had a higher band and 50 plugins the same band.
The API reports installs only as a lower bound with one significant figure: 300,000 means at least 300,000 and at most 399,999.
Which WordPress version is Limit Login Attempts tested with?
On the reference date the plugin page on wordpress.org showed the notice “This plugin hasn’t been tested with the latest 3 major releases of WordPress”, because the “tested up to” field was below 6.9 (6.2). The notice describes only that field; it does not say whether the plugin runs on newer versions. 8.0% of the group carried it.
How does Limit Login Attempts compare with its group?
The group holds 399 listed plugins. 99.2% of them had a more recent last release than Limit Login Attempts; 5.3% had no release for more than 365 days.
| Figure | Limit Login Attempts | Group, 399 plugins |
|---|---|---|
| Days since the last release | 1,242 | median 12 |
| Rating | 4.6 (202) | median 4.7 (10+ ratings) |
| Support threads marked resolved | not stated | 68.2% |
| Tested up to | 6.2 | 47.6% on 7.1 |
| Requires PHP | not stated | most often 7.4 (41.6%) |
All values on the reference date
| Slug | limit-login-attempts |
|---|---|
| Author | Automattic |
| Active installs | 300,000 to 399,999 |
| Last release | 1,242 days before the reference date |
| Tested up to | WordPress 6.2 · core on the reference date: 7.1 |
| Requires WordPress | 2.8 |
| Requires PHP | not stated |
| Rating | 4.6 out of 5 from 202 ratings |
| Support threads, two months | none in the window |
| Listed since | 15 Jan 2009 |
| Total downloads | 2,300,657, updates included |
| Tags | authentication, login, security |
Tags
| Tag | Plugins with 10,000+ installs and this tag | Rank by installs | Median days since release |
|---|---|---|---|
| authentication | 9 | 1 | 154 |
| login | 38 | 4 | 71 |
| security | 79 | 16 | 16 |
Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.
Class of 2009
Limit Login Attempts has been listed since 15 Jan 2009. Of the 79 plugins with 10,000+ installs added in 2009, 84.8% released within the 365 days before the reference date.
Same group, shared tags
Not a recommendation; the same figures for comparison. Alphabetical.
| Plugin | Active installs | Last release | Rating |
|---|---|---|---|
| Activity Log | 200,000 to 299,999 | 2 days before the reference date | 4.3 (74) |
| Admin Menu Editor | 300,000 to 399,999 | 9 days before the reference date | 4.6 (312) |
| Advanced Access Manager | 100,000 to 199,999 | 95 days before the reference date | 4.2 (420) |
| Anti-Malware Security and Brute-Force Firewall | 100,000 to 199,999 | 60 days before the reference date | 4.9 (783) |
| BBQ Firewall | 100,000 to 199,999 | 19 days before the reference date | 4.9 (160) |
| CloudSecure WP Security | 100,000 to 199,999 | 1 day before the reference date | 5.0 (2) |
| InfiniteWP Client | 200,000 to 299,999 | 9 days before the reference date | 4.4 (177) |
| Jetpack Protect | 100,000 to 199,999 | 16 days before the reference date | 4.6 (123) |
Do you maintain Limit Login Attempts?
If you maintain Limit Login Attempts, you can link to this profile, for example from your readme or your website. Both snippets show this badge:
HTML
<a href="https://hafenstudios.com/en/census/plugins/limit-login-attempts/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="Limit Login Attempts in the Plugin Directory Census 01/2026" width="220" height="40"></a>
Markdown
[](https://hafenstudios.com/en/census/plugins/limit-login-attempts/)
The image is loaded from hafenstudios.com; as with every request, our server records the usual access data, which is deleted after 14 days. If you prefer not to, use a plain text link.
A value is wrong? Write to moin@hafenstudios.com; a documented correction leads to a new version.
How to cite
hafenstudios (2026): Limit Login Attempts, profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/limit-login-attempts/
Source and status
All values come from the full pull of the public wordpress.org API on 28 Aug 2026 (reference time 21:56:30 UTC). The analysis and text on this page are available under CC BY 4.0; the raw values come from the public wordpress.org API and are in the raw data. How the count was made is set out in the method, what the fields do not say under limits. hafenstudios builds WordPress plugins itself, see the conflict of interest. Corrections to moin@hafenstudios.com; a documented correction leads to a new version. From issue 02 this page will also show the change since the previous reference date. Collected and prepared by Horst Wenzel.
Plugin names and trademarks belong to their owners. hafenstudios is not affiliated with the authors named here.
