Skip to content
PluginCanary

WP Deferred JavaScripts

by Willy Bahuaud · 800+ active installs · Checked 3 Nov 2026
At risk1 Critical1 Warning

At risk: no release in 123 months (last release 1 Sep 2016).

59/ 100 Canary Score

Capped at 59: a Critical signal is open.

Sub-scores for WP Deferred JavaScripts
Ownership100
Maintenance0
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is WP Deferred JavaScripts still maintained?
No. Last release 1 Sep 2016, over 10 years ago. 1 Sep 2016 · wordpress.org
Who owns WP Deferred JavaScripts, and has it changed hands?
No change recorded. 3 Nov 2026 · SVN log
Was WP Deferred JavaScripts removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is WP Deferred JavaScripts safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest WP Deferred JavaScripts update safe to install?
No ownership change before 2.0.5. No one-star spike after it. 31 Aug 2016 · Release history

Active signals

Facts we detected, with links to the source.

  • CriticalMNT-1No release in 123 months (last release 1 Sep 2016). Plan a replacement if the plugin is important to your site.1 Sep 2017Evidence
  • WarningMNT-2Tested up to WordPress 4.6.30, 25 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
Confridin4 Nov 2013 to 7 Dec 2018, 11 commits

1 committer recorded. No ownership change since 2013.

Maintenance

Last release
10 years ago
Releases, 24 months
0
Tested up to
4.6 vs 7.1
Requires PHP
not stated supported 8.2+
Releases per quarter
Releases per quarter for WP Deferred JavaScripts
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 Sep 2016. Tested up to 4.6, 25 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 3.2.

Rating distribution
5 star17
4 star1
3 star0
2 star6
1 star11

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

800+ 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.

Page OptimizeScore 100 · 200,000+Performance LabScore 100 · 100,000+Speculative LoadingScore 100 · 70,000+Optimization DetectiveScore 100 · 60,000+Embed OptimizerScore 100 · 50,000+

Facts

Version2.0.5
AuthorWilly Bahuaud
Added27 Jan 2013
Last updated1 Sep 2016
Active installs800+
Requires WordPress3.0
Tested up to4.6.30
Requires PHPnot stated
CategoryPerformance & Optimization > Caching Solutions
Tagslabjs, deferring, javascript, performance, optimization

Other plugins by this author: Multi Image Metabox, Pastacode, Nearby Map by Wabeo, Mention comment's Authors by Wabeo, Auto Generate Submenus, Crayon Syntax Highlighter to Pastacode, Advanced Remove Links in Comments, Camptix Invoices, SyntaxHighlighter Evolved to Pastacode

Questions

Is WP Deferred JavaScripts still maintained?

No. Last release 1 Sep 2016, over 10 years ago.

Who owns WP Deferred JavaScripts, and has it changed hands?

No change recorded.

Was WP Deferred JavaScripts removed from wordpress.org?

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

Is WP Deferred JavaScripts safe?

No known vulnerabilities on record.

Is the latest WP Deferred JavaScripts update safe to install?

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