Plugin profile · observed daily since 02 Aug 2026
VigilanTor
Active installs400+ rounded
Current authordrew010
Owner changesNone while we have been watching
Last release2.5 years ago 19 Oct 2023
Support— no recent threads
Releases on record16
Rating5.0 /5 · 12
Added to directory23 Oct 2015
Requires WP4.0
Requires PHP5.6
Version lag0.8 behind
Tested up toWP 6.3.10 WordPress is now on 7.1
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 drew010 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 |
|---|---|---|---|
| drew010 | 16 | 23 Oct 2015 | 19 Oct 2023 |
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.
Small but established: 400+ active installs. Enough sites to show it works in the wild, too few for adoption to say much on its own.
4 downloads a day over the last 7 days, rising 23% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
08 Aug 2026peak 16/day28 Aug 2026
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 | 15 Aug | 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 11 | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 11 | 0 | 16 | 0 | 0 |
Unchanged throughout: ratings total (12) · active installs (400+) · version (1.3.12) · support threads (0) · threads resolved (0)
27 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory10 years ago 23 Oct 2015
Requires WP4.0
Requires PHP5.6
Version lag0.8 behind
Is anyone still maintaining this?
- No release in 1,045 days (2.9 years). The last was 19 Oct 2023.
- Declares compatibility only up to WordPress 6.3.10, while 7.1 is current. The author has not confirmed it runs on the last 8 releases.
- drew010 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.
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.
- 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.
- 11 Apr 202517 months agoDormancy threshold crossed540 days since the last release (2023-10-19). Dormancy is a maintenance observation, not a judgement about the owner.
- 19 Oct 20232.5 years agoVersion 1.3.12 released
- 19 Oct 20232.5 years agoVersion 1.3.11 releasedfrom the release logCommitted by drew010.
- 20 Feb 20224.5 years agoVersion 1.3.10 releasedfrom the release logCommitted by drew010.
- 05 Jan 20215.5 years agoVersion 1.3.9 releasedfrom the release logCommitted by drew010.
- 12 May 20206 years agoVersion 1.3.7 releasedfrom the release logCommitted by drew010.
- 12 May 20206 years agoVersion 1.3.8 releasedfrom the release logCommitted by drew010.
- 05 May 20206 years agoVersion 1.3.6 releasedfrom the release logCommitted by drew010.
- 19 Jul 20197 years agoVersion 1.3.4 releasedfrom the release logCommitted by drew010.
- 19 Jul 20197 years agoVersion 1.3.5 releasedfrom the release logCommitted by drew010.
- 04 May 20188 years agoVersion 1.3.3 releasedfrom the release logCommitted by drew010.
- 26 Jul 20179 years agoVersion 1.3.2 releasedfrom the release logCommitted by drew010.
- 27 Nov 20169.5 years agoVersion 1.3.1 releasedfrom the release logCommitted by drew010.
- 28 Mar 201610 years agoVersion 1.3 releasedfrom the release logCommitted by drew010.
- 23 Oct 201510 years ago3 earlier releasesfrom the release logBetween 23 Oct 2015 and 05 Nov 2015. Listed individually in the public release log rather than here.
- 23 Oct 201510 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 drew010 for all 27 days we have observed it.
- It was last released 2.5 years ago (19 Oct 2023).
- Its author declares it tested up to WordPress 6.3.10; WordPress is now on 7.1.
- WordPress.org reports 400+ active installs.
- It carries 12 ratings, 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.
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.
Akismet Anti-spam: Spam Protection
The best anti-spam protection to block spam comments and spam in a contact form. The most trusted antispam solution for WordPress and WooCommerce.
5,000,000+ installs4.7★ (1,186)updated 18 Aug 2026
12,500× the installs
Compare side by side Proxy & VPN Blocker
Block VPNs, proxies, Tor, and spam on WordPress. Strengthen security and stop fake users with smart IP blocking via proxycheck.io.
1,000+ installs3.8★ (33)updated 20 Aug 2026
Compare side by side Throws SPAM Away
A powerful anti-spam plugin that silently discards spam comments without showing any error page.
10,000+ installs5.0★ (6)updated 26 Aug 2026
25× the installs
Compare side by side Kama SpamBlock
Light and invisible protection against basic automated comment spam. Pings and trackbacks check for real backlinks.
4,000+ installs5.0★ (17)updated 25 Jul 2026
10× the installs
Compare side by side Comment Blacklist Updater
Update "Comment Blacklist" spam terms to manage spam in forms and comments
1,000+ installs4.8★ (4)updated 11 May 2026
Compare side by side Spam protection, Honeypot, Anti-Spam by CleanTalk
Top-rated antispam for contact forms, comments, WooCommerce, eCommerce, and login. No CAPTCHAs, no friction, just background anti spam protection.
200,000+ installs4.8★ (3,208)updated 19 Aug 2026
500× the installs
Compare side by side 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 VigilanTor: a person reads every submission, and corrections get a reply within 5 business days.