Skip to content
PluginCanary
Limited data: this plugin has under 1,000 active installs and less than 12 weeks of history with us, so we show signals but no status band yet.

Cookielander

by zaus · 10+ active installs · Checked 4 Nov 2026
Limited data1 Critical1 Warning

Limited data: Cookielander has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

59/ 100 Canary Score

Capped at 59: a Critical signal is open.

Sub-scores for Cookielander
Ownership100
Maintenance0
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Cookielander still maintained?
No. Last release 27 Oct 2016, over 10 years ago. 27 Oct 2016 · wordpress.org
Who owns Cookielander, and has it changed hands?
Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist. 4 Nov 2026 · SVN log
Was Cookielander removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
Is Cookielander safe?
No known vulnerabilities on record. 4 Nov 2026 · Wordfence Intelligence
Is the latest Cookielander update safe to install?
No ownership change before 0.7. No one-star spike after it. 27 Oct 2016 · Release history

Active signals

Facts we detected, with links to the source.

  • CriticalMNT-1No release in 122 months (last release 27 Oct 2016). Plan a replacement if the plugin is important to your site.27 Oct 2017Evidence
  • WarningMNT-2Tested up to WordPress 4.5.33, 26 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 recorded. Commit history is collected for plugins with 1,000+ installs or on a watchlist.

Maintenance

Last release
10 years ago
Releases, 24 months
0
Tested up to
4.5 vs 7.1
Requires PHP
not stated supported 8.2+
Releases per quarter
Releases per quarter for Cookielander
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 27 Oct 2016. Tested up to 4.5, 26 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews.

Rating distribution
5 star0
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

10+ active installs. History builds with each weekly snapshot.

Momentum history builds with each snapshot.

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.7
Authorzaus
Added18 Dec 2015
Last updated27 Oct 2016
Active installs10+
Requires WordPress3.0
Tested up to4.5.33
Requires PHPnot stated
Categorynot stated
Tagsppc, cookies, contact form, landing page, landing referrer

Other plugins by this author: Forms: 3rd-Party Integration, Forms: 3rd-Party Xml Post, Forms: 3rd-Party Dynamic Fields, Forms: 3rd-Party Migration, Gravity Forms Dynamic Fields, Forms: 3rd-Party File Attachments, Forms: 3rdparty Phone Numbers, Stop CF7 Multiclick, Forms: 3rd-Party Resend Gravity Forms, Countdown Timer, Forms: 3rd-Party Inject Results, Forms: 3rd-Party Submission Reformat

Questions

Is Cookielander still maintained?

No. Last release 27 Oct 2016, over 10 years ago.

Who owns Cookielander, and has it changed hands?

Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist.

Was Cookielander removed from wordpress.org?

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

Is Cookielander safe?

No known vulnerabilities on record.

Is the latest Cookielander update safe to install?

No ownership change before 0.7. 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 4 Nov 2026.Report a data issue