Skip to content
PluginCanary

Parse.ly

by Parse.ly · 1,000+ active installs · Checked 5 Nov 2026
Healthy1 Warning

Healthy: maintained, last release 4 Nov 2026, 35 releases in 24 months, no unpatched vulnerabilities.

Tested up to WordPress 6.9.11, 2 major versions behind 7.1.4.

96/ 100 Canary Score
Sub-scores for Parse.ly
Ownership100
Maintenance90
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Parse.ly still maintained?
Yes. Last release 4 Nov 2026, 35 releases in the last 24 months. 4 Nov 2026 · wordpress.org
Who owns Parse.ly, and has it changed hands?
No change recorded. Main committer parsely since Apr 2021. 5 Nov 2026 · SVN log
Was Parse.ly removed from wordpress.org?
No. Listed on wordpress.org as of 5 Nov 2026. 5 Nov 2026 · wordpress.org
Is Parse.ly safe?
No known vulnerabilities on record. 5 Nov 2026 · Wordfence Intelligence
Is the latest Parse.ly update safe to install?
No ownership change before 3.25.0. No one-star spike after it. 4 Nov 2026 · Release history

Active signals

Facts we detected, with links to the source.

  • WarningMNT-2Tested up to WordPress 6.9.11, 2 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
parsely_mike15 Jul 2012 to 21 Jan 2021, 95 commits
parsely13 Apr 2021 to 4 Nov 2026, 104 commits

2 committers recorded. No ownership change since 2012.

Maintenance

Last release
today
Releases, 24 months
35
Tested up to
6.9 vs 7.1
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for Parse.ly
Q1 20247
Q2 20244
Q3 20245
Q4 20241
Q1 20250
Q2 202510
Q3 20254
Q4 20254
Q1 20262
Q2 20264
Q3 20266
Q4 20264

Last release 4 Nov 2026. Tested up to 6.9, 2 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

Rating distribution
5 star1
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 Parse.ly
4 May 202638
11 May 2026197
18 May 2026209
25 May 2026442
1 Jun 2026399
8 Jun 2026201
15 Jun 2026171
22 Jun 2026162
29 Jun 2026159
6 Jul 2026183
13 Jul 2026254
20 Jul 2026519
27 Jul 2026510
3 Aug 2026212
10 Aug 2026247
17 Aug 2026719
24 Aug 2026854
31 Aug 2026312
7 Sep 2026273
14 Sep 2026405
21 Sep 2026375
28 Sep 2026266
5 Oct 2026627
12 Oct 2026648
19 Oct 2026443
26 Oct 2026733
2 Nov 2026116

Weekly downloads over the last 4 weeks are 35% above the 27-week average.

Healthier alternatives

Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.

Microsoft ClarityScore 100 · 200,000+Google Analytics for WooCommerceScore 100 · 100,000+WP-PostViewsScore 100 · 90,000+Pixel CatScore 100 · 40,000+Conversion Tracking for WooCommerceScore 100 · 20,000+

Facts

Version3.25.0
AuthorParse.ly
Added15 Jul 2012
Last updated4 Nov 2026
Active installs1,000+
Requires WordPress6.1
Tested up to6.9.11
Requires PHP7.4
CategoryAnalytics & Reporting > Traffic & Visitor Analytics
Tagsstats, parsely, analytics, statistics, content marketing

Questions

Is Parse.ly still maintained?

Yes. Last release 4 Nov 2026, 35 releases in the last 24 months.

Who owns Parse.ly, and has it changed hands?

No change recorded. Main committer parsely since Apr 2021.

Was Parse.ly removed from wordpress.org?

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

Is Parse.ly safe?

No known vulnerabilities on record.

Is the latest Parse.ly update safe to install?

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