TaskBound for ClickUp – Focus Timer & Website Blocker 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: gnllmmahpjdoifdabojlblphogpabial
Permissions (4)
- Store local data
- Schedule tasks
- Access current tab
Related extensions
Website Blocker — Block Sites, Focus Timer & Productivity ToolsProductivity
Focus TimerProductivity
Distraction Blocker with Focus TimerProductivity
Website Blocker & Screen Time Limit - Focus TimerProductivity
FocusBlock - Pomodoro Timer & Site BlockerProductivity
Block Site – Website Blocker & Focus TimerProductivity
Frequently asked questions
Is TaskBound for ClickUp – Focus Timer & Website Blocker safe to use?
Our latest automated scan rates the Chrome listing of TaskBound for ClickUp – Focus Timer & Website Blocker at 85/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 TaskBound for ClickUp – Focus Timer & Website Blocker require?
TaskBound for ClickUp – Focus Timer & Website Blocker requests 4 permissions. The most significant: Store local data, Schedule tasks, Access current tab. See the full breakdown in the security report.
Who develops TaskBound for ClickUp – Focus Timer & Website Blocker?
TaskBound for ClickUp – Focus Timer & Website Blocker is published by Kastovia. 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: 2 critical and 2 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.