SECURITY REPORT · EXTENSHI SCAN
Screenshot to Component
Chrome extension·by GTS
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
Screenshot to Component's safety score vs every other extension we've scanned
Globally
50%of extensions carry more risk
Riskier ←→ Safer
Ranked against 369,936 extensions
In Productivity
63%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 177,133 productivity extensions
Findings
30
median 16Lower is safer
Critical findings
0
median 0Severity = Critical
Permissions
4
median 3Declared in manifest
Active users
8
median 14vs category median
Findings breakdown
Automated security signal · 30 distinct issues across 6 severities
30
distinct issues
detected
detected
Critical00%
High00%
Needs Review00%
Medium2997%
Low13%
Info00%
Permissions requested
1 risky permission of 4 total
1 high-risk permission require attention
This extension requests 4 permissions in total. 1 of them grant broad capabilities that are worth a careful look.
High
Execute scripts in pages
Can inject and execute JavaScript code in web pages
Medium
Store local data
Can save data locally in the browser for persistence
Medium
Access current tab
Can temporarily access the content of the active tab when you click the extension
Medium
Add context menu items
Can add custom items to the right-click context menu
Are you the author of Screenshot to Component?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show Screenshot to Component's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 1, 2026
Browser extensions made transparent.