SECURITY REPORT · EXTENSHI SCAN
getsBee
Chrome extension·by qjatjs123123
0
/ 100 SAFETY SCORE
CAUTION
Mostly fine, but a few things worth reviewing before you install.
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
getsBee's safety score vs every other extension we've scanned
Globally
21%of extensions carry more risk
Riskier ←→ Safer
Ranked against 369,936 extensions
In Lifestyle
21%of lifestyle extensions carry more risk
Riskier ←→ Safer
Ranked against 43,972 lifestyle extensions
Findings
35
median 12Lower is safer
Critical findings
0
median 0Severity = Critical
Permissions
1
median 1Declared in manifest
Active users
5
median 26vs category median
Findings breakdown
Automated security signal · 35 distinct issues across 6 severities
35
distinct issues
detected
detected
Scanners reported 40 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical00%
High39%
Needs Review00%
Medium3189%
Low13%
Info00%
Permissions requested
1 permission declared
No risky permissions
1 permission requested — none are flagged as risky.
Medium
Store local data
Can save data locally in the browser for persistence
Are you the author of getsBee?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show getsBee's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 18, 2026
Browser extensions made transparent.