Is iCode Guard safe?
Checked version: 1.18.32 · Scan date (UTC): 2026-10-07
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
Findings breakdown
detected
Permissions requested
Communicate with desktop apps
Can exchange messages with applications installed on your computer
View open tabs
Can see URLs and titles of all open tabs
Execute scripts in pages
Can inject and execute JavaScript code in web pages
Access browser cookies
Can read and modify cookies, potentially accessing login sessions
Store local data
Can save data locally in the browser for persistence
Unlimited local storage
Can store large amounts of data locally without size limits
Monitor navigation
Can observe and track tab navigation events and URL changes
Show notifications
Can display desktop notifications outside the browser
Block requests with host access
Can block or redirect network requests and requires host permissions
Device attributes
Can read enterprise device attributes
Access user identity
Can get OAuth2 tokens and access your Google account identity
View email address
Can see the email address of the signed-in Chrome user
Are you the author of iCode Guard?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
What this assessment covers
- Store listing
- Edge
- Checked version
- 1.18.32
- Current listed version
- 1.18.32
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 4 critical and 4 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.