SiteHush - Website Blocker & Focus Timer 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: gikdnegkmeebhelcjbgpmohahaiklgha
Permissions (4)
- Store local data
- Block network requests (declarative)
- Schedule tasks
Related extensions
SiteBlocker — Block Distracting Websites & Stay FocusedProductivity
SiteBlockade: Website Blocker & Focus ModeProductivity
Website Blocker - Block Distractions & FocusProductivity
Focus Tracker - Website Blocker and Focus TimerProductivity
Stay Focused: Free Website BlockerProductivity
Block Site – Website Blocker & Focus TimerProductivity
Frequently asked questions
Is SiteHush - Website Blocker & Focus Timer safe to use?
Our latest automated scan rates the Chrome listing of SiteHush - Website Blocker & Focus Timer at 82/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 SiteHush - Website Blocker & Focus Timer require?
SiteHush - Website Blocker & Focus Timer requests 4 permissions. The most significant: Store local data, Block network requests (declarative), Schedule tasks. See the full breakdown in the security report.
Who develops SiteHush - Website Blocker & Focus Timer?
SiteHush - Website Blocker & Focus Timer is published by EdenWorks. 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
- 1.0.2
- Current listed version
- 1.0.2
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 0 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.