Plugin profile · observed daily since 02 Aug 2026
Shieldfy Security Firewall and Anti Virus
Active installs30+ rounded
Current authorShieldfy
Owner changesNone while we have been watching
Last release7.5 years ago 12 Nov 2018
Support— no recent threads
Releases on record8
Rating5.0 /5 · 3
Added to directory14 Nov 2015
Requires WP3.0.1
Requires PHPfalse
Version lag2.2 behind
Tested up toWP 4.9.31 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 Shieldfy 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 |
|---|---|---|---|
| eslamsalem | 6 | 10 Jan 2016 | 20 Jun 2018 |
| komicho1996 | 1 | 12 Nov 2018 | 12 Nov 2018 |
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.
Very early-stage: 30+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
8 downloads a day over the last 7 days, rising 62% 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 12/day29 Aug 2026
Install band fell to 30+ on 04 Aug 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 | 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 | — | 11 | 0 | 12 | 0 | 11 | 0 | 11 | 0 | 11 | 11 | 0 | 11 | 11 |
Unchanged throughout: ratings total (3) · active installs (30+) · version (3.6.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.
Added to directory10 years ago 14 Nov 2015
Requires WP3.0.1
Requires PHPfalse
Version lag2.2 behind
Is anyone still maintaining this?
- No release in 2,848 days (7.8 years). The last was 12 Nov 2018.
- Declares compatibility only up to WordPress 4.9.31, while 7.1 is current. The author has not confirmed it runs on the last 22 releases.
- The same account maintains 1 other plugin, and none has been updated in over a year, the most recent on 08 Oct 2016.
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 202628 days agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 202628 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.
- 05 May 20206 years agoDormancy threshold crossed540 days since the last release (2018-11-12). Dormancy is a maintenance observation, not a judgement about the owner.
- 12 Nov 20187.5 years agoVersion 3.6.0 released
- 12 Nov 20187.5 years agoVersion 3.6 releasedfrom the release logCommitted by komicho1996.
- 20 Jun 20188 years agoVersion 3.5.1 releasedfrom the release logCommitted by eslamsalem.
- 19 Apr 20188 years agoVersion 3.5 releasedfrom the release logCommitted by eslamsalem.
- 15 Jun 20179 years agoVersion 3.0 releasedfrom the release logCommitted by eslamsalem.
- 24 Sep 20169.5 years agoVersion 2.0 releasedfrom the release logCommitted by eslamsalem.
- 03 Apr 201610 years agoVersion 1.5 releasedfrom the release logCommitted by eslamsalem.
- 10 Jan 201610 years agoVersion 1.1 releasedfrom the release logCommitted by eslamsalem.
- 14 Nov 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 Shieldfy for all 28 days we have observed it.
- It was last released 7.5 years ago (12 Nov 2018).
- Its author declares it tested up to WordPress 4.9.31; WordPress is now on 7.1.
- WordPress.org reports 30+ active installs.
- It carries 3 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.
Prevent XSS Vulnerability
This WP plugin blocks XSS by encoding harmful URL characters & safely handling HTML in $_GET. Customizable settings for enhanced website security.
6,000+ installs5.0★ (7)updated 22 Jul 2025
Compare side by side AntiVirus
Security plugin to protect your blog or website against exploits and spam injections.
30,000+ installs4.1★ (23)updated 21 Dec 2025
Compare side by side Basic Security: Prevent Cross Site Scripting
It helps in preventing Cross Site Scripting (XSS) with just a few lines of code.
200+ installs5.0★ (1)updated 22 Aug 2026
Compare side by side Defender Security – Malware Scanner, Login Security & Firewall
WordPress security plugin with malware scanner, IP blocking, audit logs, antivirus scans, firewall, 2FA, brute force login security, and more.
80,000+ installs4.8★ (334)updated 24 Aug 2026
Compare side by side BoundaryGuard Headers
Automatically enforces essential HTTP security headers to protect your site from XSS, clickjacking, and protocol downgrade attacks.
10+ installsupdated 12 Aug 2026
Compare side by side MJP Security Tools
Lightweight WordPress hardening — XSS database scanner, POST request logging, failed login logging, and file permission checker.
10+ installsupdated 23 Feb 2026
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 Shieldfy Security Firewall and Anti Virus: a person reads every submission, and corrections get a reply within 5 business days.