SECURITY REPORT · EXTENSHI SCAN
readto
Chrome extension·by vthinkxie
0
/ 100 SAFETY SCORE
RISKY
Several elevated signals. Read the findings before sharing this with your team.
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
readto's safety score vs every other extension we've scanned
Globally
8%of extensions carry more risk
Riskier ←→ Safer
Ranked against 369,936 extensions
In Productivity
11%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 177,133 productivity extensions
Findings
33
median 16Lower is safer
Critical findings
1
median 0Severity = Critical
Permissions
1
median 3Declared in manifest
Active users
799
median 14vs category median
Findings breakdown
Automated security signal · 33 distinct issues across 6 severities
33
distinct issues
detected
detected
Scanners reported 34 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical13%
High26%
Needs Review00%
Medium1648%
Low1133%
Info39%
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 readto?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show readto's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 11, 2026
Browser extensions made transparent.