Skip to content
PluginCanary

Security Headers

by SimonRWaters · 3,000+ active installs · Checked 3 Nov 2026
At risk1 Critical1 Warning

At risk: no release in 93 months (last release 26 Feb 2019).

59/ 100 Canary Score

Capped at 59: a Critical signal is open.

Sub-scores for Security Headers
Ownership100
Maintenance0
Security100
Support70
Reputation70

How the score works

Quick answers

Is Security Headers still maintained?
No. Last release 26 Feb 2019, over 7 years ago. 26 Feb 2019 · wordpress.org
Who owns Security Headers, and has it changed hands?
No change recorded. 3 Nov 2026 · SVN log
Was Security Headers removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Security Headers safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest Security Headers update safe to install?
No ownership change before 1.1. No one-star spike after it. 10 Apr 2015 · Release history

Active signals

Facts we detected, with links to the source.

  • CriticalMNT-1No release in 93 months (last release 26 Feb 2019). Plan a replacement if the plugin is important to your site.26 Feb 2020Evidence
  • WarningMNT-2Tested up to WordPress 5.1.28, 20 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
SimonRWaters10 Apr 2015 to 26 Feb 2019, 24 commits

1 committer recorded. No ownership change since 2015.

Maintenance

Last release
8 years ago
Releases, 24 months
0
Tested up to
5.1 vs 7.1
Requires PHP
5.6 supported 8.2+
Releases per quarter
Releases per quarter for Security Headers
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 26 Feb 2019. Tested up to 5.1, 20 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

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

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

Weekly downloads, last 27 weeks
Weekly downloads for Security Headers
4 May 202629
11 May 202665
18 May 202691
25 May 202667
1 Jun 202664
8 Jun 202674
15 Jun 202666
22 Jun 202658
29 Jun 202660
6 Jul 202672
13 Jul 202664
20 Jul 202689
27 Jul 202673
3 Aug 202696
10 Aug 202672
17 Aug 2026100
24 Aug 202670
31 Aug 202689
7 Sep 202682
14 Sep 2026102
21 Sep 202699
28 Sep 202699
5 Oct 2026101
12 Oct 202681
19 Oct 2026139
26 Oct 2026126
2 Nov 202620

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

Healthier alternatives

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

Disable WP REST APIScore 100 · 30,000+AntiVirusScore 100 · 30,000+CloudSecure WP SecurityScore 98 · 100,000+Disabled Source, Disabled Right ClickScore 97 · 10,000+IP Location BlockScore 96 · 10,000+

Facts

Version1.1
AuthorSimonRWaters
Added10 Apr 2015
Last updated26 Feb 2019
Active installs3,000+
Requires WordPress3.8.1
Tested up to5.1.28
Requires PHP5.6
CategorySecurity & Privacy > Security Scanning & Malware Protection
Tagstls, hsts, https, nosniff

Questions

Is Security Headers still maintained?

No. Last release 26 Feb 2019, over 7 years ago.

Who owns Security Headers, and has it changed hands?

No change recorded.

Was Security Headers removed from wordpress.org?

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

Is Security Headers safe?

No known vulnerabilities on record.

Is the latest Security Headers update safe to install?

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