Clock Max - Alarm, Multi-Timer, World Clock, Stopwatch, To-Do List extension
Security at a glance
Describes the Edge listing; other stores are scanned separately and can score differently. Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportEdge listing ID: gphjplmjcobbckblbbhmccnfencjemhe
Permissions (5)
- Schedule tasks
- Show notifications
- Store local data
Related extensions
Timer, Alarm & StopwatchAppearance
Clock Max - Alarm, Multi-Timer, World Clock, Stopwatch, To-Do ListProductivity
Timer (alarm, timer and stopwatch)Appearance
Timer, Alarm & Stopwatch ProAlerts & Updates
Clock Max - Alarm, Multi-Timer, World Clock, Stopwatch, To-Do ListProductivity
Clock – World Clock, Alarm, Timer & StopwatchOther
Frequently asked questions
Is Clock Max - Alarm, Multi-Timer, World Clock, Stopwatch, To-Do List safe to use?
Our latest automated scan rates the Edge listing of Clock Max - Alarm, Multi-Timer, World Clock, Stopwatch, To-Do List at 91/100 (low risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Clock Max - Alarm, Multi-Timer, World Clock, Stopwatch, To-Do List require?
Clock Max - Alarm, Multi-Timer, World Clock, Stopwatch, To-Do List requests 5 permissions. The most significant: Schedule tasks, Show notifications, Store local data. See the full breakdown in the security report.
Who develops Clock Max - Alarm, Multi-Timer, World Clock, Stopwatch, To-Do List?
Clock Max - Alarm, Multi-Timer, World Clock, Stopwatch, To-Do List is published by ColinRong. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Edge
- Checked version
- 2.0.1
- Current listed version
- 2.0.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 0 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.