SECURITY REPORT · EXTENSHI SCAN
cc-inspector
Edge extension·by xiaomingho
42
/ 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
cc-inspector's safety score vs every other extension we've scanned
Globally
1%of extensions carry more risk
Riskier ←→ Safer
Ranked against 402,748 extensions
In Developer Tools
3%of developer tools extensions carry more risk
Riskier ←→ Safer
Ranked against 3,406 developer tools extensions
Findings
164
median 16Lower is safer
Critical findings
8
median 1Severity = Critical
Permissions
2
median 3Declared in manifest
Active users
943
median 50vs category median
Findings breakdown
Automated security signal · 164 distinct issues across 6 severities
164
distinct issues
detected
detected
Scanners reported 240 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical85%
High2415%
Needs Review00%
Medium5735%
Low5835%
Info1710%
Permissions requested
2 permissions declared
No risky permissions
2 permissions requested — none are flagged as risky.
Medium
Store local data
Can save data locally in the browser for persistence
Medium
Show notifications
Can display desktop notifications outside the browser
Are you the author of cc-inspector?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show cc-inspector's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 12, 2026
Browser extensions made transparent.