SECURITY REPORT · EXTENSHI SCAN
Jenkins Auto Proceed
Edge extension·by Hector Otavio
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
Jenkins Auto Proceed's safety score vs every other extension we've scanned
Globally
76%of extensions carry more risk
Riskier ←→ Safer
Ranked against 369,936 extensions
In Developer Tools
90%of developer tools extensions carry more risk
Riskier ←→ Safer
Ranked against 3,124 developer tools extensions
Findings
3
median 15Lower is safer
Critical findings
0
median 1Severity = Critical
Permissions
2
median 3Declared in manifest
Active users
5
median 69vs category median
Findings breakdown
Automated security signal · 3 distinct issues across 6 severities
3
distinct issues
detected
detected
Critical00%
High133%
Needs Review00%
Medium133%
Low133%
Info00%
Permissions requested
2 risky permissions of 2 total
2 high-risk permissions require attention
This extension requests 2 permissions in total. 2 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
High
View open tabs
Can see URLs and titles of all open tabs
Are you the author of Jenkins Auto Proceed?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show Jenkins Auto Proceed's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 15, 2026
Browser extensions made transparent.