Automatic Copyright Year · Security record
Is Automatic Copyright Year safe?
No known vulnerabilities are on record for Automatic Copyright Year.
Checked 2 days ago against the WPVulnerability database, for version 1.1.
How it’s looked after
- Last release
- Jul 22, 2019 (7 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 5.2.30 (current: 7.1)
- Active installs
- 6K+
Known vulnerabilities
None on record for Automatic Copyright Year.
Questions about Automatic Copyright Year’s security
Is Automatic Copyright Year safe to use?
No known vulnerabilities are on record for Automatic Copyright Year. That isn’t a guarantee, so keep it updated like any plugin.
Does Automatic Copyright Year have known security vulnerabilities?
No. WPVulnerability’s database lists no known vulnerabilities for Automatic Copyright Year.
Is Automatic Copyright Year still maintained?
Its last release was 7 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is Automatic Copyright Year compatible with the latest WordPress?
Automatic Copyright Year’s readme says it’s tested up to WordPress 5.2.30, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.