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.

Asynchronous Javascript

by Paris Holley · 100+ active installs · Checked 4 Nov 2026
Limited data2 Criticals1 Warning

Limited data: Asynchronous Javascript has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

39/ 100 Canary Score

Capped at 39: a vulnerability has no patch.

Sub-scores for Asynchronous Javascript
Ownership100
Maintenance0
Security35
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Asynchronous Javascript still maintained?
No. Last release 2 Nov 2013, over 13 years ago. 2 Nov 2013 · wordpress.org
Who owns Asynchronous Javascript, and has it changed hands?
No change recorded. 4 Nov 2026 · SVN log
Was Asynchronous Javascript removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
Is Asynchronous Javascript safe?
No. 1 known vulnerability has no fix in the current version. 27 Jan 2026 · Wordfence Intelligence
Is the latest Asynchronous Javascript update safe to install?
No ownership change before 1.3.5. No one-star spike after it. 2 Nov 2013 · Release history

Active signals

Facts we detected, with links to the source.

  • CriticalSEC-2Vulnerability published 27 Jan 2026 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.10 Feb 2026Evidence
  • CriticalMNT-1No release in 158 months (last release 2 Nov 2013). Plan a replacement if the plugin is important to your site.2 Nov 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 since 2013.

Maintenance

Last release
13 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 Asynchronous Javascript
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 2 Nov 2013. Tested up to 3.5, 36 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 3.7.

Rating distribution
5 star5
4 star1
3 star0
2 star1
1 star2

Security record

1 vulnerability in 24 months, 1 with no fix in the current version.

PublishedIssueCVSSAffectedFixed inDays to patch
27 Jan 2026Asynchronous Javascript <= 1.3.5 - Reflected Cross-Site Scripting6.1<= 1.3.5No fixn/a

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Support

Support history appears after our first snapshots of the forum counts.

Momentum

100+ 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.3.5
AuthorParis Holley
Added18 Jan 2013
Last updated2 Nov 2013
Active installs100+
Requires WordPress3.5
Tested up to3.5.2
Requires PHPnot stated
Categorynot stated
TagsJS, async, headjs, javascript, asynchronous

Other plugins by this author: MANTIS Ad Network

Questions

Is Asynchronous Javascript still maintained?

No. Last release 2 Nov 2013, over 13 years ago.

Who owns Asynchronous Javascript, and has it changed hands?

No change recorded.

Was Asynchronous Javascript removed from wordpress.org?

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

Is Asynchronous Javascript safe?

No. 1 known vulnerability has no fix in the current version.

Is the latest Asynchronous Javascript update safe to install?

No ownership change before 1.3.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 4 Nov 2026.Report a data issue