Skip to content
PluginCanary

Floating Publish Button

by Son Do · 1,000+ active installs · Checked 3 Nov 2026
At risk1 Critical1 Warning

At risk: no release in 144 months (last release 12 Dec 2014).

59/ 100 Canary Score

Capped at 59: a Critical signal is open.

Sub-scores for Floating Publish Button
Ownership100
Maintenance0
Security100
Support70
Reputation70

How the score works

Quick answers

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

Active signals

Facts we detected, with links to the source.

  • CriticalMNT-1No release in 144 months (last release 12 Dec 2014). Plan a replacement if the plugin is important to your site.12 Dec 2015Evidence
  • WarningMNT-2Tested up to WordPress 4.0.38, 31 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 2014.

Maintenance

Last release
12 years ago
Releases, 24 months
0
Tested up to
4.0 vs 7.1
Requires PHP
not stated supported 8.2+
Releases per quarter
Releases per quarter for Floating Publish Button
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 12 Dec 2014. Tested up to 4.0, 31 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

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

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

Weekly downloads, last 27 weeks
Weekly downloads for Floating Publish Button
4 May 202611
11 May 202614
18 May 202625
25 May 202629
1 Jun 202623
8 Jun 202628
15 Jun 202625
22 Jun 202626
29 Jun 202613
6 Jul 202612
13 Jul 202624
20 Jul 202639
27 Jul 202649
3 Aug 202636
10 Aug 202634
17 Aug 202635
24 Aug 202640
31 Aug 202645
7 Sep 202640
14 Sep 202648
21 Sep 202671
28 Sep 202672
5 Oct 202657
12 Oct 202672
19 Oct 202669
26 Oct 202691
2 Nov 202611

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.

Custom Login Page CustomizerScore 93 · 50,000+Block VisibilityScore 93 · 40,000+Hide Admin Bar Based on User RolesScore 93 · 20,000+CMS Tree Page ViewScore 92 · 50,000+Widget ContextScore 92 · 30,000+

Facts

Version1.0.6
AuthorSon Do
Added16 Jan 2014
Last updated12 Dec 2014
Active installs1,000+
Requires WordPress3.0.1
Tested up to4.0.38
Requires PHPnot stated
CategorySite Administration & Utilities > Site Health & Diagnostics
Tagspage, post, admin, button, backend

Questions

Is Floating Publish Button still maintained?

No. Last release 12 Dec 2014, over 11 years ago.

Who owns Floating Publish Button, and has it changed hands?

No change recorded.

Was Floating Publish Button removed from wordpress.org?

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

Is Floating Publish Button safe?

No known vulnerabilities on record.

Is the latest Floating Publish Button update safe to install?

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