Spider Analyser
Avoid: Spider Analyser is closed on wordpress.org and no longer gets updates.
Capped at 10: the plugin is closed on wordpress.org.
| Ownership | 100 |
|---|---|
| Maintenance | 10 |
| Security | 30 |
| Support | 70 |
| Reputation | 70 |
Quick answers
- Is Spider Analyser still maintained?
- No. Closed on wordpress.org on 18 Jun 2026. 18 Jun 2026 · wordpress.org
- Who owns Spider Analyser, and has it changed hands?
- Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist. 3 Nov 2026 · SVN log
- Was Spider Analyser removed from wordpress.org?
- Yes. Closed on 18 Jun 2026, reason: security issue. 18 Jun 2026 · wordpress.org
- Is Spider Analyser safe?
- No. 1 known vulnerability has no fix in the current version. 29 Jul 2026 · Wordfence Intelligence
- Is the latest Spider Analyser update safe to install?
- Not enough data. No release date on record for the current version. Release history
Active signals
Facts we detected, with links to the source.
- CriticalSEC-2Vulnerability published 29 Jul 2026 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.12 Aug 2026Evidence
- CriticalCLS-1Closed on wordpress.org on 18 Jun 2026, reason: security issue. Replace this plugin. It no longer receives updates from wordpress.org.18 Jun 2026Evidence
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
No ownership change recorded. Commit history is collected for plugins with 1,000+ installs or on a watchlist.
Maintenance
- Last release
- not recorded
- Releases, 24 months
- 0
- Tested up to
- not stated vs 7.1
- Requires PHP
- not stated supported 8.2+
Release history builds as we see new versions.
Reputation
Last 90 days: no reviews.
Security record
1 vulnerability in 24 months, 1 with no fix in the current version.
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 29 Jul 2026 | Spider Analyser – WordPress搜索引擎蜘蛛分析插件 <= 2.1.3 - Unauthenticated Remote Code Execution | 9.8 | <= 2.1.3 | No fix | n/a |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
Fewer than 10 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
| Version | not stated |
|---|---|
| Author | not stated |
| Added | not stated |
| Last updated | not stated |
| Active installs | Fewer than 10 |
| Requires WordPress | not stated |
| Tested up to | not stated |
| Requires PHP | not stated |
| Category | Analytics & Reporting > Traffic & Visitor Analytics |
| Tags | not stated |
Questions
Is Spider Analyser still maintained?
No. Closed on wordpress.org on 18 Jun 2026.
Who owns Spider Analyser, and has it changed hands?
Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist.
Was Spider Analyser removed from wordpress.org?
Yes. Closed on 18 Jun 2026, reason: security issue.
Is Spider Analyser safe?
No. 1 known vulnerability has no fix in the current version.
Is the latest Spider Analyser update safe to install?
Not enough data. No release date on record for the current version.