Skip to content
PluginCanary

Age Verify

by Chase Wiseman · 1,000+ active installs · Checked 3 Nov 2026
At risk1 Critical1 Warning

At risk: no release in 108 months (last release 28 Nov 2017).

59/ 100 Canary Score

Capped at 59: a Critical signal is open.

Sub-scores for Age Verify
Ownership100
Maintenance0
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Age Verify still maintained?
No. Last release 28 Nov 2017, over 8 years ago. 28 Nov 2017 · wordpress.org
Who owns Age Verify, and has it changed hands?
No change recorded. 3 Nov 2026 · SVN log
Was Age Verify removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Age Verify safe?
1 known vulnerability, fixed (latest in 0.2.9). Not on the exploited list. 20 Apr 2015 · Wordfence Intelligence
Is the latest Age Verify update safe to install?
No ownership change before 0.3.0. No one-star spike after it. 17 Jan 2016 · Release history

Active signals

Facts we detected, with links to the source.

  • CriticalMNT-1No release in 108 months (last release 28 Nov 2017). Plan a replacement if the plugin is important to your site.28 Nov 2018Evidence
  • WarningMNT-2Tested up to WordPress 4.4.34, 27 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.

No ownership change since 2012.

Maintenance

Last release
9 years ago
Releases, 24 months
0
Tested up to
4.4 vs 7.1
Requires PHP
not stated supported 8.2+
Releases per quarter
Releases per quarter for Age Verify
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 28 Nov 2017. Tested up to 4.4, 27 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 4.4.

Rating distribution
5 star16
4 star4
3 star2
2 star1
1 star1

Security record

1 vulnerability on record, patched (latest fixed in 0.2.9).

Show 1 patched vulnerability
PublishedIssueCVSSAffectedFixed inDays to patch
20 Apr 2015Age Verify <= 0.2.8 - Reflected Cross-Site Scripting6.1<= 0.2.80.2.91

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 Age Verify
4 May 202616
11 May 202628
18 May 202632
25 May 202645
1 Jun 202625
8 Jun 202636
15 Jun 202623
22 Jun 202618
29 Jun 202624
6 Jul 202616
13 Jul 202628
20 Jul 202629
27 Jul 202628
3 Aug 202644
10 Aug 202635
17 Aug 202632
24 Aug 202625
31 Aug 202628
7 Sep 202637
14 Sep 202659
21 Sep 202640
28 Sep 202647
5 Oct 202640
12 Oct 202643
19 Oct 202658
26 Oct 202697
2 Nov 202613

Weekly downloads over the last 4 weeks are 51% 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

Version0.3.0
AuthorChase Wiseman
Added14 Nov 2012
Last updated28 Nov 2017
Active installs1,000+
Requires WordPress3.2
Tested up to4.4.34
Requires PHPnot stated
CategoryUser Management & Authentication > User Registration & Login
Tagsage, verify, restrict

Questions

Is Age Verify still maintained?

No. Last release 28 Nov 2017, over 8 years ago.

Who owns Age Verify, and has it changed hands?

No change recorded.

Was Age Verify removed from wordpress.org?

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

Is Age Verify safe?

1 known vulnerability, fixed (latest in 0.2.9). Not on the exploited list.

Is the latest Age Verify update safe to install?

No ownership change before 0.3.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