Plugin profile · observed daily since 02 Aug 2026
WP-Login and WP-Admin Whitelist
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 SwiftNinjaPro 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.
Very early-stage: 10+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
2 downloads a day over the last 7 days, falling 50% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
Install band fell to 10+ on 12 Aug 2026, from 20+. 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 | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 0 |
Unchanged throughout: ratings total (0) · active installs (10+) · version (1.11.1) · 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 2,124 days (5.8 years). The last was 04 Nov 2020.
- Declares compatibility only up to WordPress 5.5.20, while 7.1 is current. The author has not confirmed it runs on the last 16 releases.
- The same account maintains 6 other plugins, and none has been updated in over a year, the most recent on 09 Nov 2022.
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.
- 09 Aug 202620 days agoInstall band moved to 20+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 202627 days agoInstall band moved to 10+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.
- 28 Apr 20224 years agoDormancy threshold crossed540 days since the last release (2020-11-04). Dormancy is a maintenance observation, not a judgement about the owner.
- 04 Nov 20205.5 years agoVersion 1.11.1 released
- 01 Mar 20197.5 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 SwiftNinjaPro for all 28 days we have observed it.
- It was last released 5.5 years ago (04 Nov 2020).
- Its author declares it tested up to WordPress 5.5.20; WordPress is now on 7.1.
- WordPress.org reports 10+ active installs.
What we don’t know yet
- Nobody has rated it. The first rating that arrives shows up here.
- 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.
Do you want to secure and customize the WordPress login page? Download the All in One Login plugin for login page security and customization.
Loginizer is a WordPress security plugin which helps you fight against bruteforce attacks.
Hide wp-login.php file, prevent attacks on login form, hide login & increase security. No files are changed.
Protect WordPress from malware, hackers, brute-force attacks & suspicious traffic. Includes firewall, login security, 2FA & vulnerability checks.
XO Security is a plugin to enhance login related security.
Secure WordPress login, registration, and comment form with Google reCAPTCHA or Cloudflare Turnstile. Prevent Brute-force attacks and more.
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-Login and WP-Admin Whitelist: a person reads every submission, and corrections get a reply within 5 business days.