Skip to content
PluginCanary

Disable WPautop

by Nick Momrik · 2,000+ active installs · Checked 3 Nov 2026
At risk1 Critical1 Warning

At risk: no release in 108 months (last release 28 Nov 2017).

59/ 100 Canary Score

Capped at 59: a Critical signal is open.

Sub-scores for Disable WPautop
Ownership100
Maintenance0
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

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

Active signals

Facts we detected, with links to the source.

  • CriticalMNT-1No release in 108 months (last release 28 Nov 2017). Plan a replacement if the plugin is important to your site.28 Nov 2018Evidence
  • WarningMNT-2Tested up to WordPress 4.4.34, 27 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 since 2005.

Maintenance

Last release
9 years ago
Releases, 24 months
0
Tested up to
4.4 vs 7.1
Requires PHP
not stated supported 8.2+
Releases per quarter
Releases per quarter for Disable WPautop
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 28 Nov 2017. Tested up to 4.4, 27 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 4.2.

Rating distribution
5 star4
4 star0
3 star0
2 star0
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

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

Weekly downloads, last 27 weeks
Weekly downloads for Disable WPautop
4 May 202610
11 May 202626
18 May 202620
25 May 202642
1 Jun 202639
8 Jun 202650
15 Jun 202634
22 Jun 202631
29 Jun 202629
6 Jul 202635
13 Jul 202633
20 Jul 202632
27 Jul 202642
3 Aug 202655
10 Aug 202656
17 Aug 202652
24 Aug 202636
31 Aug 202642
7 Sep 202643
14 Sep 202658
21 Sep 202662
28 Sep 202657
5 Oct 202657
12 Oct 202651
19 Oct 202676
26 Oct 202699
2 Nov 202617

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

Version1.1
AuthorNick Momrik
Added20 Jan 2005
Last updated28 Nov 2017
Active installs2,000+
Requires WordPressnot stated
Tested up to4.4.34
Requires PHPnot stated
CategorySite Administration & Utilities > URL Redirects & 301 Management
Tagsdisable, wpautop

Other plugins by this author: Recent Posts, Most Commented Widget, Last Modified, Post Count, Moderate Pingbacks, Moderate Trackbacks, Comment Author URL Stripper, Post Word Count, Comment Count, Comment Plugger, Card Converter, Comments Posted Elsewhere

Questions

Is Disable WPautop still maintained?

No. Last release 28 Nov 2017, over 8 years ago.

Who owns Disable WPautop, and has it changed hands?

No change recorded.

Was Disable WPautop removed from wordpress.org?

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

Is Disable WPautop safe?

No known vulnerabilities on record.

Is the latest Disable WPautop 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