SECURITY REPORT · EXTENSHI SCAN
To Be Read
Chrome extension·by avikabra
0
/ 100 SAFETY SCORE
CAUTION
Mostly fine, but a few things worth reviewing before you install.
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
To Be Read's safety score vs every other extension we've scanned
Globally
52%of extensions carry more risk
Riskier ←→ Safer
Ranked against 369,936 extensions
In Productivity
65%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 177,133 productivity extensions
Findings
22
median 16Lower is safer
Critical findings
0
median 0Severity = Critical
Permissions
1
median 3Declared in manifest
Active users
7
median 14vs category median
Findings breakdown
Automated security signal · 22 distinct issues across 6 severities
22
distinct issues
detected
detected
Critical00%
High00%
Needs Review00%
Medium2195%
Low15%
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 To Be Read?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show To Be Read's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 5, 2026
Browser extensions made transparent.