SECURITY REPORT · EXTENSHI SCAN
GitCharge
Edge extension·by Ajay Ravindran
15
/ 100 SAFETY SCORE
CRITICAL
Severe indicators. Treat as unsafe until the developer addresses these findings.
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
GitCharge's safety score vs every other extension we've scanned
Globally
0%of extensions carry more risk
Riskier ←→ Safer
Ranked against 391,591 extensions
In Developer Tools
0%of developer tools extensions carry more risk
Riskier ←→ Safer
Ranked against 3,298 developer tools extensions
Findings
52
median 16Lower is safer
Critical findings
6
median 1Severity = Critical
Permissions
3
median 3Declared in manifest
Active users
0
median 66vs category median
Findings breakdown
Automated security signal · 52 distinct issues across 6 severities
52
distinct issues
detected
detected
Scanners reported 61 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical612%
High1631%
Needs Review00%
Medium1835%
Low713%
Info510%
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
Low
Block network requests (declarative)
Can block or redirect network requests using predefined rules without seeing content
Are you the author of GitCharge?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show GitCharge's live security score on GitHub or in your docs
Scan performed by extenshi.io · Sep 17, 2026
Browser extensions made transparent.