SECURITY REPORT · EXTENSHI SCAN
Ugly HTTP
Chrome extension·by lgarron
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
Ugly HTTP's safety score vs every other extension we've scanned
Globally
65%of extensions carry more risk
Riskier ←→ Safer
Ranked against 347,108 extensions
In Productivity
80%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 170,403 productivity extensions
Findings
6
median 16Lower is safer
Critical findings
0
median 0Severity = Critical
Permissions
3
median 3Declared in manifest
Active users
36
median 14vs category median
Findings breakdown
Automated security signal · 6 distinct issues across 6 severities
6
distinct issues
detected
detected
Critical00%
High00%
Needs Review00%
Medium467%
Low233%
Info00%
Permissions requested
1 risky permission of 3 total
1 high-risk permission require attention
This extension requests 3 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
Are you the author of Ugly HTTP?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show Ugly HTTP's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 18, 2026
Browser extensions made transparent.