Skip to content
PluginCanary

Bulk Delete Comments

by shahalomwordpress · 5,000+ active installs · Checked 3 Nov 2026
Healthy

Healthy: maintained, last release 13 Jul 2026, 7 releases in 24 months, no unpatched vulnerabilities.

96/ 100 Canary Score
Sub-scores for Bulk Delete Comments
Ownership100
Maintenance90
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Bulk Delete Comments still maintained?
Yes. Last release 13 Jul 2026, 7 releases in the last 24 months. 13 Jul 2026 · wordpress.org
Who owns Bulk Delete Comments, and has it changed hands?
No change recorded. Main committer shahalomwordpress since Jan 2017. 3 Nov 2026 · SVN log
Was Bulk Delete Comments removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Bulk Delete Comments safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest Bulk Delete Comments update safe to install?
No ownership change before 2.5. No one-star spike after it. 13 Jul 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.

Committers and their active periods
shahalomwordpress23 Jan 2017 to 13 Jul 2026, 23 commits
shahalomwp22 Dec 2021 to 22 Dec 2021, 2 commits

2 committers recorded. No ownership change since 2017.

Maintenance

Last release
4 months ago
Releases, 24 months
7
Tested up to
7.0 vs 7.1
Requires PHP
not stated supported 8.2+
Releases per quarter
Releases per quarter for Bulk Delete Comments
Q1 20240
Q2 20240
Q3 20242
Q4 20245
Q1 20250
Q2 20251
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20261
Q4 20260

Last release 13 Jul 2026. Tested up to 7.0, 1 major version behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 3.8.

Rating distribution
5 star9
4 star0
3 star0
2 star1
1 star3

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

5,000+ active installs. History builds with each weekly snapshot.

Weekly downloads, last 27 weeks
Weekly downloads for Bulk Delete Comments
4 May 202657
11 May 2026137
18 May 2026138
25 May 2026138
1 Jun 2026119
8 Jun 2026130
15 Jun 2026132
22 Jun 2026134
29 Jun 2026127
6 Jul 2026111
13 Jul 20261,829
20 Jul 2026464
27 Jul 2026433
3 Aug 2026428
10 Aug 2026387
17 Aug 2026390
24 Aug 2026361
31 Aug 2026314
7 Sep 2026311
14 Sep 2026301
21 Sep 2026307
28 Sep 2026312
5 Oct 2026295
12 Oct 2026279
19 Oct 2026399
26 Oct 2026350
2 Nov 202657

Weekly downloads over the last 4 weeks are 13% below the 27-week average.

Healthier alternatives

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

Disqus Comment SystemScore 100 · 30,000+Disable CommentsScore 97 · 100,000+

Facts

Version2.5
Authorshahalomwordpress
Added13 Jan 2017
Last updated13 Jul 2026
Active installs5,000+
Requires WordPress5.0
Tested up to7.0.8
Requires PHPnot stated
CategorySite Administration & Utilities > URL Redirects & 301 Management
Tagscomment, comments, delete all, delete comments, delete all comments

Questions

Is Bulk Delete Comments still maintained?

Yes. Last release 13 Jul 2026, 7 releases in the last 24 months.

Who owns Bulk Delete Comments, and has it changed hands?

No change recorded. Main committer shahalomwordpress since Jan 2017.

Was Bulk Delete Comments removed from wordpress.org?

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

Is Bulk Delete Comments safe?

No known vulnerabilities on record.

Is the latest Bulk Delete Comments update safe to install?

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