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.

Nofollow Shortcode

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

Limited data: Nofollow Shortcode 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 Nofollow Shortcode
Ownership100
Maintenance0
Security100
Support70
Reputation70

How the score works

Quick answers

Is Nofollow Shortcode still maintained?
No. Last release 1 Jan 2013, over 13 years ago. 1 Jan 2013 · wordpress.org
Who owns Nofollow Shortcode, 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 Nofollow Shortcode removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
Is Nofollow Shortcode safe?
No known vulnerabilities on record. 4 Nov 2026 · Wordfence Intelligence
Is the latest Nofollow Shortcode update safe to install?
No ownership change before 1.1. No one-star spike after it. 1 Jan 2013 · Release history

Active signals

Facts we detected, with links to the source.

  • CriticalMNT-1No release in 168 months (last release 1 Jan 2013). Plan a replacement if the plugin is important to your site.1 Jan 2014Evidence
  • WarningMNT-2Tested up to WordPress 3.5.2, 36 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
14 years ago
Releases, 24 months
0
Tested up to
3.5 vs 7.1
Requires PHP
not stated supported 8.2+
Releases per quarter
Releases per quarter for Nofollow Shortcode
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 1 Jan 2013. Tested up to 3.5, 36 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

Version1.1
AuthorLuke Mlsna
Added15 Feb 2012
Last updated1 Jan 2013
Active installs10+
Requires WordPress2.8
Tested up to3.5.2
Requires PHPnot stated
Categorynot stated
Tagsrel, link, meta, nofollow, rel-nofollow

Other plugins by this author: Custom Meta Widget, Super Simple Google Analytics, Remove Image Links, Last Updated Shortcode, Meta Description, Count Posts in a Category, Tag, or Custom Taxonomy, WP-Blacklister, Literal Shortcode, Commission Junction Link Shortcode, Drug Half-Life Calculator, Too Many Shortcodes, Count Children

Questions

Is Nofollow Shortcode still maintained?

No. Last release 1 Jan 2013, over 13 years ago.

Who owns Nofollow Shortcode, and has it changed hands?

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

Was Nofollow Shortcode removed from wordpress.org?

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

Is Nofollow Shortcode safe?

No known vulnerabilities on record.

Is the latest Nofollow Shortcode 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 4 Nov 2026.Report a data issue