SECURITY REPORT · EXTENSHI SCAN
Clinical Terminal
Chrome extension·by Clinical Terminal
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
Clinical Terminal's safety score vs every other extension we've scanned
Globally
58%of extensions carry more risk
Riskier ←→ Safer
Ranked against 369,936 extensions
In Productivity
72%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 177,133 productivity extensions
Findings
19
median 16Lower is safer
Critical findings
0
median 0Severity = Critical
Permissions
3
median 3Declared in manifest
Active users
0
median 14vs category median
Findings breakdown
Automated security signal · 19 distinct issues across 6 severities
19
distinct issues
detected
detected
Scanners reported 20 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical00%
High00%
Needs Review00%
Medium211%
Low1684%
Info15%
Permissions requested
3 permissions declared
No risky permissions
3 permissions requested — none are flagged as risky.
Medium
Access user identity
Can get OAuth2 tokens and access your Google account identity
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 Clinical Terminal?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show Clinical Terminal's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 17, 2026
Browser extensions made transparent.