SECURITY REPORT · EXTENSHI SCAN
Working time counter
Firefox extension·by Anton
53
/ 100 SAFETY SCORE
RISKY
Several elevated signals. Read the findings before sharing this with your team.
Likely abandonedsafety score reduced by 30 points
- No update in over 5 years
Why this matters
An unmaintained extension keeps whatever flaws it shipped with, and a listing with users but no owner is an attractive target to buy and repurpose.
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
Working time counter's safety score vs every other extension we've scanned
Globally
53.1%of extensions carry more risk
Riskier ←→ Safer
Ranked across every extension we scan
In its category
43.1%of its category extensions carry more risk
Riskier ←→ Safer
Ranked within its category
Findings
12
median 38Lower is safer
Risky permissions
0
median 1Critical + high perms
Total permissions
1
median 4All declared perms
Critical findings
0
median 2Severity = Critical
Findings breakdown
Automated security signal · 12 distinct issues across 6 severities
12
distinct issues
detected
detected
Scanners reported 36 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical00%
High00%
Needs Review00%
Medium1083%
Low217%
Info00%
Permissions requested
1 permission declared
No risky permissions
1 permission requested — none are flagged as risky.
Medium
Store local data
Can save data locally in the browser for persistence
Are you the author of Working time counter?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show Working time counter's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 25, 2026· partial run (some scanners failed)
Browser extensions made transparent.