Skip to content
PluginCanary

Sentry for WordPress

by stayallive · 10,000+ active installs · Checked 3 Nov 2026
Healthy

Healthy: maintained, last release 18 Aug 2026, 11 releases in 24 months, no unpatched vulnerabilities.

91/ 100 Canary Score
Sub-scores for Sentry for WordPress
Ownership100
Maintenance100
Security100
Support70
Reputation70

How the score works

Quick answers

Is Sentry for WordPress still maintained?
Yes. Last release 18 Aug 2026, 11 releases in the last 24 months. 18 Aug 2026 · wordpress.org
Who owns Sentry for WordPress, and has it changed hands?
No change recorded. Main committer stayallive since Oct 2016. 3 Nov 2026 · SVN log
Was Sentry for WordPress removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Sentry for WordPress safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest Sentry for WordPress update safe to install?
No ownership change before 8.12.0. No one-star spike after it. 18 Aug 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
stayallive27 Oct 2016 to 18 Aug 2026, 473 commits

1 committer recorded. No ownership change since 2016.

Maintenance

Last release
3 months ago
Releases, 24 months
11
Tested up to
7.1 current
Requires PHP
7.2.5 supported 8.2+
Releases per quarter
Releases per quarter for Sentry for WordPress
Q1 202411
Q2 20245
Q3 202411
Q4 20242
Q1 20250
Q2 20252
Q3 20253
Q4 20252
Q1 20260
Q2 20262
Q3 20261
Q4 20260

Last release 18 Aug 2026. Tested with WordPress 7.1 (current).

Reputation

Last 90 days: no reviews. Lifetime: 4.9.

Average rating stayed at 5.0 between Q4 2023 and Q4 2025.

Rating distribution
5 star15
4 star1
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

100% of 1 support threads resolved in the last 2 months.

Momentum

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

Weekly downloads, last 27 weeks
Weekly downloads for Sentry for WordPress
4 May 20261,596
11 May 20263,313
18 May 20266,907
25 May 20265,607
1 Jun 20264,738
8 Jun 20266,865
15 Jun 20264,772
22 Jun 20264,450
29 Jun 20264,205
6 Jul 20264,263
13 Jul 20263,904
20 Jul 20264,879
27 Jul 20264,168
3 Aug 20264,300
10 Aug 20264,037
17 Aug 20266,894
24 Aug 20265,400
31 Aug 20265,394
7 Sep 20266,431
14 Sep 20264,589
21 Sep 20265,360
28 Sep 20265,314
5 Oct 20265,139
12 Oct 20265,139
19 Oct 20266,458
26 Oct 20265,412
2 Nov 20261,152

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

Healthier alternatives

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

MCP AdapterScore 93 · 60,000+WP-SCSSScore 93 · 40,000+Show Pages IDsScore 93 · 10,000+WP ResetScore 92 · 300,000+

Facts

Version8.12.0
Authorstayallive
Added27 Oct 2016
Last updated18 Aug 2026
Active installs10,000+
Requires WordPress4.4
Tested up to7.1.4
Requires PHP7.2.5
CategoryCommunication & Messaging > Transactional Email
Tagslog, sentry, logging, error-handler, error monitoring

Questions

Is Sentry for WordPress still maintained?

Yes. Last release 18 Aug 2026, 11 releases in the last 24 months.

Who owns Sentry for WordPress, and has it changed hands?

No change recorded. Main committer stayallive since Oct 2016.

Was Sentry for WordPress removed from wordpress.org?

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

Is Sentry for WordPress safe?

No known vulnerabilities on record.

Is the latest Sentry for WordPress update safe to install?

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