SECURITY REPORT · EXTENSHI SCAN
ng-inspect for Angular
Chrome extension·by Vinay Kaparthi
46
/ 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
ng-inspect for Angular's safety score vs every other extension we've scanned
Globally
29%of extensions carry more risk
Riskier ←→ Safer
Ranked against 409,539 extensions
In Developer Tools
51%of developer tools extensions carry more risk
Riskier ←→ Safer
Ranked against 3,713 developer tools extensions
Findings
12
median 16Lower is safer
Critical findings
0
median 1Severity = Critical
Permissions
0
median 3Declared in manifest
Active users
3000
median 44vs category median
Findings breakdown
Automated security signal · 12 distinct issues across 6 severities
12
distinct issues
detected
detected
Critical00%
High975%
Needs Review00%
Medium18%
Low18%
Info18%
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 ng-inspect for Angular?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show ng-inspect for Angular's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 7, 2026
Browser extensions made transparent.