Sweet Cricket for Google Web Site Management extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: allnafmdafaebedodjgjgoicjjhaleoi
Permissions (3)
- View open tabs
Related extensions
Sweet Cricket for Google Web Site ManagementProductivity
Sweet Cricket for Google Web Site ManagementProductivity
Sweet Cricket for Google Web Site ManagementProductivity
Sweet Cricket for Google Web Site ManagementProductivity
Sweet Cricket for Google Web Site ManagementProductivity
Sweet Cricket for Google Web Site ManagementProductivity
Frequently asked questions
Is Sweet Cricket for Google Web Site Management safe to use?
Our latest automated scan rates the Chrome listing of Sweet Cricket for Google Web Site Management at 72/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Sweet Cricket for Google Web Site Management require?
Sweet Cricket for Google Web Site Management requests 3 permissions. The most significant: View open tabs. See the full breakdown in the security report.
Who develops Sweet Cricket for Google Web Site Management?
Sweet Cricket for Google Web Site Management is published by tayyar.guvenc. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- Not provided in this assessment
- Current listed version
- 1.0.1
- Assessment updated (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 10 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.