Plugin profile · observed daily since 02 Aug 2026
Secure Content Protector
Active installs30+ rounded
Current authoriSmart Web Service
Owner changesNone while we have been watching
Last release18 months ago 28 Apr 2025
Support— no recent threads
Releases on record1
Rating— no ratings yet
Added to directory25 Feb 2025
Requires WP5.0
Requires PHP7.0
Version lag0.3 behind
Tested up toWP 6.8.12 WordPress is now on 7.1
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 iSmart Web Service 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 |
|---|---|---|---|
| godswillinnovations | 1 | 28 Apr 2025 | 28 Apr 2025 |
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.
3 downloads a day over the last 7 days, rising 100% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
13 Sep 2026peak 11/day31 Oct 2026
No ratings on record, so there is no sentiment to report.
Install band fell to 30+ on 31 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 | — | 11 | 0 | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 11 | 0 |
| Active installs | 40+ | 40+ | 40+ | 40+ | 40+ | 30+ | 30+ | 30+ | 30+ | 30+ | 30+ | 30+ | 40+ | 30+ |
Unchanged throughout: ratings total (0) · version (1.1.0) · 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.
Added to directory20 months ago 25 Feb 2025
Requires WP5.0
Requires PHP7.0
Version lag0.3 behind
Is anyone still maintaining this?
- No release in 561 days (1.5 years). The last was 28 Apr 2025.
- Declares compatibility only up to WordPress 6.8.12, while 7.1 is current. The author has not confirmed it runs on the last 3 releases.
- The same account maintains 1 other plugin; the most recent update to any of them was 23 Feb 2026.
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.
- 30 Oct 202611 days agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 23 Oct 202618 days agoInstall band moved to 30+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 20 Oct 202621 days agoDormancy threshold crossed540 days since the last release (2025-04-28). Dormancy is a maintenance observation, not a judgement about the owner.
- 04 Oct 20261 month agoInstall band moved to 40+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Oct 20261 month agoInstall band moved to 30+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 01 Oct 20261 month 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 agoInstall band moved to 30+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.
- 28 Apr 202518 months agoVersion 1.1.0 released
- 25 Feb 202520 months 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 iSmart Web Service for all 91 days we have observed it.
- It was last released 18 months ago (28 Apr 2025).
- Its author declares it tested up to WordPress 6.8.12; WordPress is now on 7.1.
- WordPress.org reports 30+ 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.
- 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.
Secure Copy Content Protection and Content Locking
Copy Protection plugin is activated it disables the right click, copy paste, content selection and copy shortcut keys
20,000+ installs4.3★ (62)updated 23 Oct 2026
Right Click Ban – Disable Right Click & Content Copy Protection
Disable right click to protect your content. Blocks text copying, image dragging, keyboard shortcuts, F12 and developer tools access.
400+ installs4.3★ (7)updated 20 Aug 2026
eDarpan: Website Protection
The most complete website protection plugin for WordPress. Block IPs, disable right-click, prevent copy-paste, block countries, stop spam comments, an …
200+ installs3.8★ (5)updated 12 May 2026
WP Content Copy Protection with Color Design
This plugin will protect the posts content from copying by disable right click and disable selecting text. You can exclude pages and posts.
5,000+ installs4.5★ (25)updated 20 Aug 2026
Disable Right Click & Content Copy Protection
Content protection plugin that disables right-click, prevents copying, and blocks image dragging with customizable settings and notifications.
80+ installsupdated 07 Sep 2026
WP-Copyright-Protection
Simple copyright protection for your images and text. No right click, no text selections, no screenshots. A very lean and clean plugin.
5,000+ installs4.4★ (21)updated 23 Feb 2025
no release in over 18 months
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 Secure Content Protector: a person reads every submission, and corrections get a reply within 5 business days.