SECURITY REPORT · EXTENSHI SCAN
sorry-were-closed
Chrome extension·by Billal
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
sorry-were-closed's safety score vs every other extension we've scanned
Globally
48%of extensions carry more risk
Riskier ←→ Safer
Ranked against 369,936 extensions
In Productivity
60%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 177,133 productivity extensions
Findings
11
median 16Lower is safer
Critical findings
0
median 0Severity = Critical
Permissions
2
median 3Declared in manifest
Active users
3
median 14vs category median
Findings breakdown
Automated security signal · 11 distinct issues across 6 severities
11
distinct issues
detected
detected
Scanners reported 12 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical00%
High327%
Needs Review00%
Medium545%
Low19%
Info218%
Permissions requested
1 risky permission of 2 total
1 high-risk permission require attention
This extension requests 2 permissions in total. 1 of them grant broad capabilities that are worth a careful look.
High
View open tabs
Can see URLs and titles of all open tabs
Medium
Store local data
Can save data locally in the browser for persistence
Are you the author of sorry-were-closed?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show sorry-were-closed's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 11, 2026
Browser extensions made transparent.