SECURITY REPORT · EXTENSHI SCAN
CSS Debug with Pesticide
Chrome extension·by Rob
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
CSS Debug with Pesticide's safety score vs every other extension we've scanned
Globally
98.71%of extensions carry more risk
Riskier ←→ Safer
Ranked across every extension we scan
In its category
88.71%of its category extensions carry more risk
Riskier ←→ Safer
Ranked within its category
Findings
1
median 38Lower is safer
Risky permissions
1
median 1Critical + high perms
Total permissions
2
median 4All declared perms
Critical findings
0
median 2Severity = Critical
Findings breakdown
Automated security signal · 1 distinct issue across 6 severities
1
distinct issues
detected
detected
Critical00%
High00%
Needs Review00%
Medium1100%
Low00%
Info00%
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
Execute scripts in pages
Can inject and execute JavaScript code in web pages
Medium
Access current tab
Can temporarily access the content of the active tab when you click the extension
Are you the author of CSS Debug with Pesticide?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show CSS Debug with Pesticide's live security score on GitHub or in your docs
Scan performed by extenshi.io · Jul 25, 2026· partial run (some scanners failed)
Browser extensions made transparent.