Skip to content
PluginCanary

Remove noreferrer

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

At risk: no release in 71 months (last release 4 Jan 2021).

59/ 100 Canary Score

Capped at 59: a Critical signal is open.

Sub-scores for Remove noreferrer
Ownership100
Maintenance0
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

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

Active signals

Facts we detected, with links to the source.

  • CriticalMNT-1No release in 71 months (last release 4 Jan 2021). Plan a replacement if the plugin is important to your site.4 Jan 2022Evidence
  • WarningMNT-2Tested up to WordPress 5.6.23, 15 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-master21 Mar 2019 to 21 Mar 2019, 1 commits
gruz021 Mar 2019 to 4 Jan 2021, 11 commits

2 committers recorded. No ownership change since 2019.

Maintenance

Last release
6 years ago
Releases, 24 months
0
Tested up to
5.6 vs 7.1
Requires PHP
5.6 supported 8.2+
Releases per quarter
Releases per quarter for Remove noreferrer
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 4 Jan 2021. Tested up to 5.6, 15 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

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

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

Weekly downloads, last 27 weeks
Weekly downloads for Remove noreferrer
4 May 202611
11 May 202620
18 May 202643
25 May 202633
1 Jun 202622
8 Jun 202635
15 Jun 202642
22 Jun 202627
29 Jun 202623
6 Jul 202624
13 Jul 202630
20 Jul 202639
27 Jul 202654
3 Aug 202663
10 Aug 202655
17 Aug 202661
24 Aug 202647
31 Aug 202650
7 Sep 202674
14 Sep 202677
21 Sep 202659
28 Sep 202664
5 Oct 202668
12 Oct 202678
19 Oct 2026111
26 Oct 2026101
2 Nov 202623

Weekly downloads over the last 4 weeks are 58% 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.0
Authorgruz0
Added21 Mar 2019
Last updated4 Jan 2021
Active installs5,000+
Requires WordPress5.1
Tested up to5.6.23
Requires PHP5.6
CategorySite Administration & Utilities > URL Redirects & 301 Management
Tagspage, post, widgets, comments, noreferrer

Other plugins by this author: Widget to Display Posts from Current Category, Social Media Popup

Questions

Is Remove noreferrer still maintained?

No. Last release 4 Jan 2021, over 5 years ago.

Who owns Remove noreferrer, and has it changed hands?

No change recorded.

Was Remove noreferrer removed from wordpress.org?

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

Is Remove noreferrer safe?

No known vulnerabilities on record.

Is the latest Remove noreferrer update safe to install?

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