SECURITY REPORT · EXTENSHI SCAN
Not a Jelly Fish!
Chrome extension·by joshiutsaha1
0
/ 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
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
Not a Jelly Fish!'s safety score vs every other extension we've scanned
Globally
61%of extensions carry more risk
Riskier ←→ Safer
Ranked against 369,936 extensions
In Productivity
76%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 177,133 productivity extensions
Findings
7
median 16Lower is safer
Critical findings
0
median 0Severity = Critical
Permissions
0
median 3Declared in manifest
Active users
95
median 14vs category median
Findings breakdown
Automated security signal · 7 distinct issues across 6 severities
7
distinct issues
detected
detected
Critical00%
High00%
Needs Review00%
Medium686%
Low114%
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 Not a Jelly Fish!?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show Not a Jelly Fish!'s live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 15, 2026
Browser extensions made transparent.