SECURITY REPORT · EXTENSHI SCAN
DevClock
Chrome extension
0
/ 100 SAFETY SCORE
EXCELLENT
Looks clean. No meaningful risks detected in this scan.
Automated analysis of publicly available code — not a professional security audit. It may produce false positives and does not prove an extension is unsafe or safe. Treat it as one signal among many. Disclaimer · Report an issue
How it ranks
DevClock's safety score vs every other extension we've scanned
Globally
59%of extensions carry more risk
Riskier ←→ Safer
Ranked against 369,936 extensions
In Productivity
73%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 177,133 productivity extensions
Findings
13
median 16Lower is safer
Critical findings
0
median 0Severity = Critical
Permissions
3
median 3Declared in manifest
Active users
0
median 14vs category median
Findings breakdown
Automated security signal · 13 distinct issues across 6 severities
13
distinct issues
detected
detected
Scanners reported 15 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical00%
High00%
Needs Review00%
Medium1185%
Low215%
Info00%
Permissions requested
3 permissions declared
No risky permissions
3 permissions requested — none are flagged as risky.
Medium
Store local data
Can save data locally in the browser for persistence
Medium
Read clipboard
Can read text and data currently on your clipboard
Medium
Add context menu items
Can add custom items to the right-click context menu
Are you the author of DevClock?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show DevClock's live security score on GitHub or in your docs
Scan performed by extenshi.io · Jul 25, 2026
Browser extensions made transparent.