Skip to content
PluginCanary

Auto Copyright Year Updater

by eraplugins · 4,000+ active installs · Checked 3 Nov 2026
At risk1 Critical1 Warning

At risk: no release in 28 months (last release 10 Jul 2024).

59/ 100 Canary Score

Capped at 59: a Critical signal is open.

Sub-scores for Auto Copyright Year Updater
Ownership100
Maintenance0
Security100
Support70
Reputation70

How the score works

Quick answers

Is Auto Copyright Year Updater still maintained?
No. Last release 10 Jul 2024, over 2 years ago. 10 Jul 2024 · wordpress.org
Who owns Auto Copyright Year Updater, and has it changed hands?
No change recorded. 3 Nov 2026 · SVN log
Was Auto Copyright Year Updater removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Auto Copyright Year Updater safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest Auto Copyright Year Updater 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.

  • CriticalMNT-1No release in 28 months (last release 10 Jul 2024). Plan a replacement if the plugin is important to your site.10 Jul 2025Evidence
  • WarningMNT-2Tested up to WordPress 6.5.14, 6 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
ramielhabashy23 Jun 2018 to 17 Dec 2019, 4 commits
afazza16 Feb 2023 to 10 Jul 2024, 5 commits

2 committers recorded. No ownership change since 2018.

Maintenance

Last release
2 years ago
Releases, 24 months
0
Tested up to
6.5 vs 7.1
Requires PHP
7.2 supported 8.2+

Last release 10 Jul 2024. Tested up to 6.5, 6 major versions behind WordPress 7.1. Release history builds as we see new versions.

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

Rating distribution
5 star10
4 star0
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

Support history appears after our first snapshots of the forum counts.

Momentum

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

Weekly downloads, last 27 weeks
Weekly downloads for Auto Copyright Year Updater
4 May 202627
11 May 202656
18 May 202670
25 May 202660
1 Jun 202637
8 Jun 202662
15 Jun 202639
22 Jun 202630
29 Jun 202645
6 Jul 202638
13 Jul 202643
20 Jul 202641
27 Jul 202653
3 Aug 202669
10 Aug 202668
17 Aug 202683
24 Aug 202668
31 Aug 202645
7 Sep 202652
14 Sep 202678
21 Sep 202678
28 Sep 202683
5 Oct 202676
12 Oct 202670
19 Oct 2026125
26 Oct 2026129
2 Nov 202636

Weekly downloads over the last 4 weeks are 46% above the 27-week average.

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

Version1.3
Authoreraplugins
Added23 Jun 2018
Last updated10 Jul 2024
Active installs4,000+
Requires WordPress4.6
Tested up to6.5.14
Requires PHP7.2
CategorySite Administration & Utilities > URL Redirects & 301 Management
Tagswidget, copyright, shortcode

Other plugins by this author: My Digital Clock, ERA Autoplay Turn Sound ON, Recent Posts Easy

Questions

Is Auto Copyright Year Updater still maintained?

No. Last release 10 Jul 2024, over 2 years ago.

Who owns Auto Copyright Year Updater, and has it changed hands?

No change recorded.

Was Auto Copyright Year Updater removed from wordpress.org?

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

Is Auto Copyright Year Updater safe?

No known vulnerabilities on record.

Is the latest Auto Copyright Year Updater update safe to install?

Not enough data. No release date on record for the current version.

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