Ajaxify Comments
Healthy: maintained, last release 6 Sep 2026, 5 releases in 24 months, no unpatched vulnerabilities.
| Ownership | 100 |
|---|---|
| Maintenance | 100 |
| Security | 95 |
| Support | 70 |
| Reputation | 70 |
Quick answers
- Is Ajaxify Comments still maintained?
- Yes. Last release 6 Sep 2026, 5 releases in the last 24 months. 6 Sep 2026 · wordpress.org
- Who owns Ajaxify Comments, and has it changed hands?
- No change recorded. Main committer ronalfy since Aug 2023. 3 Nov 2026 · SVN log
- Was Ajaxify Comments removed from wordpress.org?
- No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
- Is Ajaxify Comments safe?
- 1 known vulnerability, fixed (latest in 3.2). Not on the exploited list. 27 Feb 2026 · Wordfence Intelligence
- Is the latest Ajaxify Comments update safe to install?
- No ownership change before 3.2.2. No one-star spike after it. 6 Apr 2026 · Release history
Active signals
Facts we detected, with links to the source.
No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
| weweave | 3 Nov 2016 to 30 Aug 2023, 52 commits |
|---|---|
| ronalfy | 30 Aug 2023 to 6 Sep 2026, 70 commits |
2 committers recorded. No ownership change since 2012.
Maintenance
- Last release
- 59 days ago
- Releases, 24 months
- 5
- Tested up to
- 7.1 current
- Requires PHP
- 7.2 supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 6 |
| Q3 2024 | 0 |
| Q4 2024 | 1 |
| Q1 2025 | 0 |
| Q2 2025 | 1 |
| Q3 2025 | 1 |
| Q4 2025 | 0 |
| Q1 2026 | 1 |
| Q2 2026 | 1 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 6 Sep 2026. Tested with WordPress 7.1 (current).
Reputation
Last 90 days: no reviews. Lifetime: 4.8.
| 5 star | 84 |
|---|---|
| 4 star | 2 |
| 3 star | 1 |
| 2 star | 0 |
| 1 star | 4 |
Security record
1 vulnerability in 24 months, patched (latest fixed in 3.2).
Show 1 patched vulnerability
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 27 Feb 2026 | Ajaxify Comments <= 3.1 - Unauthenticated HTTP Header Injection | 5.3 | <= 3.1 | 3.2 | n/a |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
3,000+ active installs. History builds with each weekly snapshot.
| 4 May 2026 | 73 |
|---|---|
| 11 May 2026 | 135 |
| 18 May 2026 | 162 |
| 25 May 2026 | 212 |
| 1 Jun 2026 | 123 |
| 8 Jun 2026 | 123 |
| 15 Jun 2026 | 103 |
| 22 Jun 2026 | 80 |
| 29 Jun 2026 | 162 |
| 6 Jul 2026 | 100 |
| 13 Jul 2026 | 103 |
| 20 Jul 2026 | 130 |
| 27 Jul 2026 | 205 |
| 3 Aug 2026 | 124 |
| 10 Aug 2026 | 150 |
| 17 Aug 2026 | 131 |
| 24 Aug 2026 | 88 |
| 31 Aug 2026 | 196 |
| 7 Sep 2026 | 136 |
| 14 Sep 2026 | 125 |
| 21 Sep 2026 | 131 |
| 28 Sep 2026 | 167 |
| 5 Oct 2026 | 152 |
| 12 Oct 2026 | 143 |
| 19 Oct 2026 | 176 |
| 26 Oct 2026 | 173 |
| 2 Nov 2026 | 30 |
Weekly downloads over the last 4 weeks are 3% below the 27-week average.
Healthier alternatives
Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.
Facts
| Version | 3.2.2 |
|---|---|
| Author | David Stone |
| Added | 14 May 2012 |
| Last updated | 6 Sep 2026 |
| Active installs | 3,000+ |
| Requires WordPress | 6.5 |
| Tested up to | 7.1.4 |
| Requires PHP | 7.2 |
| Category | Communication & Messaging > Transactional Email |
| Tags | ajax, errors, refresh, comments, lazy load |
Other plugins by this author: Simple Comment Editing, SD AI Agent, Ultimate AI Connector for Compatible Endpoints, Ultimate Multisite - WordPress Multisite SaaS & WaaS Platform, Superdav AI Language Packs
Questions
Is Ajaxify Comments still maintained?
Yes. Last release 6 Sep 2026, 5 releases in the last 24 months.
Who owns Ajaxify Comments, and has it changed hands?
No change recorded. Main committer ronalfy since Aug 2023.
Was Ajaxify Comments removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026.
Is Ajaxify Comments safe?
1 known vulnerability, fixed (latest in 3.2). Not on the exploited list.
Is the latest Ajaxify Comments update safe to install?
No ownership change before 3.2.2. No one-star spike after it.