Skip to content
PluginCanary

HTTP 410 (Gone) responses

by Matt Calvert · 4,000+ active installs · Checked 3 Nov 2026
Healthy

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

87/ 100 Canary Score
Sub-scores for HTTP 410 (Gone) responses
Ownership100
Maintenance85
Security100
Support70
Reputation70

How the score works

Quick answers

Is HTTP 410 (Gone) responses still maintained?
Yes. Last release 5 Aug 2026, 4 releases in the last 24 months. 5 Aug 2026 · wordpress.org
Who owns HTTP 410 (Gone) responses, and has it changed hands?
No change recorded. Main committer xandercalvert since Jan 2026. 3 Nov 2026 · SVN log
Was HTTP 410 (Gone) responses removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is HTTP 410 (Gone) responses safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest HTTP 410 (Gone) responses update safe to install?
No ownership change before 1.2.1. No one-star spike after it. 5 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
xandercalvert10 Jan 2026 to 5 Aug 2026, 10 commits

1 committer recorded. No ownership change since 2011.

Maintenance

Last release
3 months ago
Releases, 24 months
4
Tested up to
7.0 vs 7.1
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for HTTP 410 (Gone) responses
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20262
Q2 20261
Q3 20261
Q4 20260

Last release 5 Aug 2026. Tested up to 7.0, 1 major version behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 4.6.

Rating distribution
5 star15
4 star5
3 star0
2 star0
1 star1

Security record

No published vulnerabilities on record for this plugin.

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Support

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

Momentum

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

Weekly downloads, last 27 weeks
Weekly downloads for HTTP 410 (Gone) responses
4 May 202660
11 May 2026145
18 May 20261,540
25 May 2026435
1 Jun 2026279
8 Jun 2026258
15 Jun 2026250
22 Jun 2026181
29 Jun 2026160
6 Jul 2026180
13 Jul 2026158
20 Jul 2026176
27 Jul 2026174
3 Aug 20261,668
10 Aug 2026473
17 Aug 2026361
24 Aug 2026377
31 Aug 2026323
7 Sep 2026265
14 Sep 2026193
21 Sep 2026218
28 Sep 2026218
5 Oct 2026256
12 Oct 2026208
19 Oct 2026322
26 Oct 2026255
2 Nov 202634

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

Healthier alternatives

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

RedirectionScore 93 · 100,000+Redirect 404 to HomepageScore 93 · 60,000+Remove Category URLScore 93 · 40,000+301 RedirectsScore 92 · 300,000+404 to 301Score 92 · 100,000+

Facts

Version1.2.1
AuthorMatt Calvert
Added15 Jan 2011
Last updated5 Aug 2026
Active installs4,000+
Requires WordPress5.0
Tested up to7.0.8
Requires PHP7.4
CategorySite Administration & Utilities > URL Redirects & 301 Management
Tagsgone, error, robots

Questions

Is HTTP 410 (Gone) responses still maintained?

Yes. Last release 5 Aug 2026, 4 releases in the last 24 months.

Who owns HTTP 410 (Gone) responses, and has it changed hands?

No change recorded. Main committer xandercalvert since Jan 2026.

Was HTTP 410 (Gone) responses removed from wordpress.org?

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

Is HTTP 410 (Gone) responses safe?

No known vulnerabilities on record.

Is the latest HTTP 410 (Gone) responses update safe to install?

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