Skip to content
PluginCanary

Conditional Widgets

by Jason LeMahieu (MadtownLems) · 7,000+ active installs · Checked 3 Nov 2026
Watch2 Warnings

Watch: tested up to WordPress 6.7.11, 4 major versions behind 7.1.4.

71/ 100 Canary Score
Sub-scores for Conditional Widgets
Ownership100
Maintenance20
Security100
Support70
Reputation70

How the score works

Quick answers

Is Conditional Widgets still maintained?
No. Last release 13 Feb 2025, over 1 year ago. 13 Feb 2025 · wordpress.org
Who owns Conditional Widgets, and has it changed hands?
No change recorded. Main committer MadtownLems since Mar 2011. 3 Nov 2026 · SVN log
Was Conditional Widgets removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Conditional Widgets safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest Conditional Widgets update safe to install?
No ownership change before 3.3. No one-star spike after it. 2 Mar 2021 · Release history

Active signals

Facts we detected, with links to the source.

  • WarningMNT-2Tested up to WordPress 6.7.11, 4 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence
  • WarningMNT-1No release in 20 months (last release 13 Feb 2025). Plan a replacement if the plugin is important to your site.13 Feb 2026Evidence

Ownership timeline

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

Committers and their active periods
MadtownLems28 Mar 2011 to 13 Feb 2025, 57 commits

1 committer recorded. No ownership change since 2011.

Maintenance

Last release
21 months ago
Releases, 24 months
0
Tested up to
6.7 vs 7.1
Requires PHP
not stated supported 8.2+
Releases per quarter
Releases per quarter for Conditional Widgets
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 13 Feb 2025. Tested up to 6.7, 4 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 4.5.

Rating distribution
5 star20
4 star0
3 star2
2 star1
1 star1

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

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

Weekly downloads, last 27 weeks
Weekly downloads for Conditional Widgets
4 May 202650
11 May 2026122
18 May 2026120
25 May 2026108
1 Jun 202698
8 Jun 202693
15 Jun 2026112
22 Jun 202669
29 Jun 202683
6 Jul 202682
13 Jul 202686
20 Jul 2026104
27 Jul 2026102
3 Aug 2026124
10 Aug 2026113
17 Aug 2026120
24 Aug 202696
31 Aug 202699
7 Sep 2026100
14 Sep 2026111
21 Sep 2026121
28 Sep 2026167
5 Oct 2026132
12 Oct 2026202
19 Oct 2026233
26 Oct 2026182
2 Nov 202630

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

Version3.3
AuthorJason LeMahieu (MadtownLems)
Added28 Mar 2011
Last updated13 Feb 2025
Active installs7,000+
Requires WordPress3.0
Tested up to6.7.11
Requires PHPnot stated
CategorySite Administration & Utilities > Site Health & Diagnostics
Tagswidgets

Other plugins by this author: Media File Sizes

Questions

Is Conditional Widgets still maintained?

No. Last release 13 Feb 2025, over 1 year ago.

Who owns Conditional Widgets, and has it changed hands?

No change recorded. Main committer MadtownLems since Mar 2011.

Was Conditional Widgets removed from wordpress.org?

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

Is Conditional Widgets safe?

No known vulnerabilities on record.

Is the latest Conditional Widgets update safe to install?

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