Plugin profile · observed daily since 02 Aug 2026
Prevent Password Reuse
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 simonbbrown 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: 50+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
3 downloads a day over the last 7 days, steady 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 50+ on 30 Oct 2026, from 40+. 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 | 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 | — | 0 | 0 | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 12 | 0 | 0 |
| Active installs | 50+ | 40+ | 40+ | 40+ | 50+ | 40+ | 40+ | 50+ | 50+ | 40+ | 50+ | 40+ | 50+ | 50+ |
Unchanged throughout: ratings total (1) · version (1.1) · support threads (0) · 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?
- No release in 4,394 days (12.0 years). The last was 28 Oct 2014.
- 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.
- simonbbrown publishes no other plugin in the directory, so there is no wider activity to compare against.
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.
- 29 Oct 202610 days agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 28 Oct 202611 days agoInstall band moved to 50+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 27 Oct 202612 days agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 25 Oct 202614 days agoInstall band moved to 50+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 23 Oct 202616 days agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 22 Oct 202617 days agoInstall band moved to 50+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 19 Oct 202620 days agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 18 Oct 202621 days agoInstall band moved to 50+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 17 Oct 202622 days agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 15 Oct 202624 days agoInstall band moved to 50+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 14 Oct 202625 days agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 13 Oct 202626 days agoInstall band moved to 50+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 11 Oct 202628 days agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 10 Oct 202629 days agoInstall band moved to 50+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 09 Oct 202630 days agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 06 Oct 20261 month agoInstall band moved to 50+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 20263 months agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 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.
- 20 Apr 201610 years agoDormancy threshold crossed540 days since the last release (2014-10-28). Dormancy is a maintenance observation, not a judgement about the owner.
- 28 Oct 201412 years agoVersion 1.1 released
- 28 Oct 201412 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 simonbbrown for all 91 days we have observed it.
- It was last released 12 years ago (28 Oct 2014).
- Its author declares it tested up to WordPress 4.0.38; WordPress is now on 7.1.
- WordPress.org reports 50+ active installs.
- It carries 1 rating, averaging 5.0 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.
- No release in the 91 days we have been watching, so how often it ships cannot be said. Every further day of silence tells you more.
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
Harden your site security with Login Security, Two-Factor Authentication (2FA), Vulnerability Scanner, Firewall, and more. Formerly iThemes Security.
Protect your uploads directory. Prevent browsing, password-protect files, add watermarks, and discourage right-click copying.
Secure WordPress login, registration, and comment form with Google reCAPTCHA or Cloudflare Turnstile. Prevent Brute-force attacks and more.
This WP plugin blocks XSS by encoding harmful URL characters & safely handling HTML in $_GET. Customizable settings for enhanced website security.
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 Prevent Password Reuse: a person reads every submission, and corrections get a reply within 5 business days.