Skip to content
PluginCanary

Certificate Verification

by SegWitz Sdn Bhd · 1,000+ active installs · Checked 3 Nov 2026
At risk1 Critical1 Warning

At risk: no release in 78 months (last release 8 Jun 2020).

59/ 100 Canary Score

Capped at 59: a Critical signal is open.

Sub-scores for Certificate Verification
Ownership100
Maintenance0
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Certificate Verification still maintained?
No. Last release 8 Jun 2020, over 6 years ago. 8 Jun 2020 · wordpress.org
Who owns Certificate Verification, and has it changed hands?
No change recorded. 3 Nov 2026 · SVN log
Was Certificate Verification removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Certificate Verification safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest Certificate Verification update safe to install?
No ownership change before 2.0. No one-star spike after it. 8 Jun 2020 · Release history

Active signals

Facts we detected, with links to the source.

  • CriticalMNT-1No release in 78 months (last release 8 Jun 2020). Plan a replacement if the plugin is important to your site.8 Jun 2021Evidence
  • WarningMNT-2Tested up to WordPress 4.8.34, 23 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
plugin-master11 May 2020 to 11 May 2020, 1 commits
segwitz17 May 2020 to 8 Jun 2020, 6 commits

2 committers recorded. No ownership change since 2020.

Maintenance

Last release
6 years ago
Releases, 24 months
0
Tested up to
4.8 vs 7.1
Requires PHP
5.4 supported 8.2+
Releases per quarter
Releases per quarter for Certificate Verification
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20260
Q4 20260

Last release 8 Jun 2020. Tested up to 4.8, 23 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

Rating distribution
5 star5
4 star0
3 star0
2 star0
1 star0

Security record

No published vulnerabilities on record for this plugin.

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Support

Support history appears after our first snapshots of the forum counts.

Momentum

1,000+ active installs. History builds with each weekly snapshot.

Weekly downloads, last 27 weeks
Weekly downloads for Certificate Verification
4 May 20266
11 May 202628
18 May 202616
25 May 202636
1 Jun 202624
8 Jun 202635
15 Jun 202621
22 Jun 202615
29 Jun 202622
6 Jul 202622
13 Jul 202624
20 Jul 202625
27 Jul 202631
3 Aug 202635
10 Aug 202636
17 Aug 202637
24 Aug 202630
31 Aug 202638
7 Sep 202639
14 Sep 202650
21 Sep 202642
28 Sep 202637
5 Oct 202644
12 Oct 202640
19 Oct 202682
26 Oct 202678
2 Nov 202613

Weekly downloads over the last 4 weeks are 59% above the 27-week average.

Healthier alternatives

Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.

No healthier plugin in the same category yet.

Facts

Version2.0
AuthorSegWitz Sdn Bhd
Added17 May 2020
Last updated8 Jun 2020
Active installs1,000+
Requires WordPress4.0
Tested up to4.8.34
Requires PHP5.4
CategoryCommunity & Social > Membership Sites & Subscriptions
Tagscertificate, verification

Questions

Is Certificate Verification still maintained?

No. Last release 8 Jun 2020, over 6 years ago.

Who owns Certificate Verification, and has it changed hands?

No change recorded.

Was Certificate Verification removed from wordpress.org?

No. Listed on wordpress.org as of 3 Nov 2026.

Is Certificate Verification safe?

No known vulnerabilities on record.

Is the latest Certificate Verification update safe to install?

No ownership change before 2.0. No one-star spike after it.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews and support forum, Wordfence Intelligence, CISA KEV, NVD.Plugin data refreshed 3 Nov 2026.Report a data issue