Local Time Clock · Security record
Is Local Time Clock safe?
No known vulnerabilities are on record for Local Time Clock.
Checked 2 days ago against the WPVulnerability database, for version 1.3.
How it’s looked after
- Last release
- May 14, 2024 (2 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.5.14 (current: 7.1)
- Active installs
- 1K+
Known vulnerabilities
None on record for Local Time Clock.
Questions about Local Time Clock’s security
Is Local Time Clock safe to use?
No known vulnerabilities are on record for Local Time Clock. That isn’t a guarantee, so keep it updated like any plugin.
Does Local Time Clock have known security vulnerabilities?
No. WPVulnerability’s database lists no known vulnerabilities for Local Time Clock.
Is Local Time Clock still maintained?
Its last release was 2 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is Local Time Clock compatible with the latest WordPress?
Local Time Clock’s readme says it’s tested up to WordPress 6.5.14, 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.