Attention Span & Screen Time Tracker | Website Blocker, Focus Timer extension
Security at a glance
Describes the Chrome listing; other stores are scanned separately and can score differently. 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: nadfeddpfjnlancednoohgkokgemjeim
Permissions (4)
- View open tabs
Related extensions
Watch & Focus Time TrackerPrivacy & Security
Attention Span & Screen Time Tracker | Website Blocker, Focus TimerProductivity
Focus Time TrackerAppearance
Chrome Time Tracker: Website & Focus ScoreProductivity
Screen Time: Website Tracker, Limits & FocusProductivity
Scolect – Screen Time & Website TrackerOther
Frequently asked questions
Is Attention Span & Screen Time Tracker | Website Blocker, Focus Timer safe to use?
Our latest automated scan rates the Chrome listing of Attention Span & Screen Time Tracker | Website Blocker, Focus Timer at 89/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 Attention Span & Screen Time Tracker | Website Blocker, Focus Timer require?
Attention Span & Screen Time Tracker | Website Blocker, Focus Timer requests 4 permissions. The most significant: View open tabs. See the full breakdown in the security report.
Who develops Attention Span & Screen Time Tracker | Website Blocker, Focus Timer?
Attention Span & Screen Time Tracker | Website Blocker, Focus Timer is published by mdanwarulislamshawn. 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
- 2.26.0
- Current listed version
- 2.26.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 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.