Plugin profile · observed daily since 02 Aug 2026
SecSign
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 SecSign 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.
Small but established: 200+ active installs. Enough sites to show it works in the wild, too few for adoption to say much on its own.
3 downloads a day over the last 7 days, falling 35% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
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 | 21 Aug | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 11 | 0 | 0 | 12 | 0 | 0 | 0 | 11 | 0 | 0 | 11 |
Unchanged throughout: ratings total (14) · active installs (200+) · version (1.8.1) · support threads (0) · threads resolved (0)
33 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 707 days (1.9 years). The last was 27 Sep 2024.
- Declares compatibility only up to WordPress 6.1.12, while 7.1 is current. The author has not confirmed it runs on the last 10 releases.
- SecSign 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.
- 02 Aug 20261 month 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.
- 21 Mar 20265 months agoDormancy threshold crossed540 days since the last release (2024-09-27). Dormancy is a maintenance observation, not a judgement about the owner.
- 27 Sep 202423 months agoVersion 1.8.1 released
- 22 May 201313 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 SecSign for all 33 days we have observed it.
- It was last released 23 months ago (27 Sep 2024).
- Its author declares it tested up to WordPress 6.1.12; WordPress is now on 7.1.
- WordPress.org reports 200+ active installs.
- It carries 14 ratings, averaging 4.6 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.
Get better WordPress login security; add two-factor authentication (2FA) for all your users with this easy-to-use plugin.
Enable one-click login with this WordPress Two-Factor Authentication (2FA) plugin, utilizing email for added security.
Free 2FA plugin for unlimited users with Passkey, Google Authenticator, Email/SMS OTP, Push Notification & passwordless login.
Easily add Duo Security two-factor authentication to your WordPress website. Enable two-factor authentication for your admins and/or users.
Easily improve site security with WordPress Hardening, Two-Factor Authentication (2FA), Login Protection, Vulnerability Detection and SSL certificate.
Harden your site security with Login Security, Two-Factor Authentication (2FA), Vulnerability Scanner, Firewall, and more. Formerly iThemes 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 SecSign: a person reads every submission, and corrections get a reply within 5 business days.