SECURITY REPORT · EXTENSHI SCAN
JS Beautifier
Edge extension·by Lukas T.
61
/ 100 SAFETY SCORE
RISKY
Several elevated signals. Read the findings before sharing this with your team.
Likely abandonedsafety score reduced by 30 points
- No update in over 5 years
- Built on Manifest V2, which Chrome and Edge are retiring
Why this matters
An unmaintained extension keeps whatever flaws it shipped with, and a listing with users but no owner is an attractive target to buy and repurpose.
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
JS Beautifier's safety score vs every other extension we've scanned
Globally
66%of extensions carry more risk
Riskier ←→ Safer
Ranked against 403,022 extensions
In Developer Tools
83%of developer tools extensions carry more risk
Riskier ←→ Safer
Ranked against 3,406 developer tools extensions
Findings
7
median 16Lower is safer
Critical findings
0
median 1Severity = Critical
Permissions
0
median 3Declared in manifest
Active users
716
median 50vs category median
Findings breakdown
Automated security signal · 7 distinct issues across 6 severities
7
distinct issues
detected
detected
Scanners reported 11 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical00%
High00%
Needs Review00%
Medium457%
Low343%
Info00%
Permissions requested
0 permissions declared
No permissions requested
This extension doesn't request any browser permissions. That's unusually clean.
Are you the author of JS Beautifier?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show JS Beautifier's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 17, 2026
Browser extensions made transparent.