Curfew: YouTube™ Time Limit, Study Mode & Shorts 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: jjomgdlbjpbhclmdiaileahebabjkhcm
Permissions (1)
- Store local data
Related extensions
YouDefineTube: Block YouTube distractions, hide shorts, set time limitsProductivity
YouTube Study ModeProductivity
YouTube Soft LimitLifestyle
Intentional YT - Block YouTube Shorts, Recommendations & Set Time LimitsLifestyle
YouTube BlockerProductivity
Aware: YouTube Blocker, Shorts Blocker & Time LimitsProductivity
Frequently asked questions
Is Curfew: YouTube™ Time Limit, Study Mode & Shorts Blocker safe to use?
Our latest automated scan rates the Chrome listing of Curfew: YouTube™ Time Limit, Study Mode & Shorts Blocker at 96/100 (low 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 Curfew: YouTube™ Time Limit, Study Mode & Shorts Blocker require?
Curfew: YouTube™ Time Limit, Study Mode & Shorts Blocker requests 1 permission. The most significant: Store local data. See the full breakdown in the security report.
Who develops Curfew: YouTube™ Time Limit, Study Mode & Shorts Blocker?
Curfew: YouTube™ Time Limit, Study Mode & Shorts Blocker is published by Mhase Technologies LLP. 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.5.0
- Current listed version
- 1.5.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 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.