Steadyline: Reading Ruler & Word Emphasis for ADHD and Dyslexic Readers 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: onabdahinifklhfjojjpenicmjiofmop
Permissions (3)
- Execute scripts in pages
Related extensions
ReadingRuler - Line Focus for ReadingMake Chrome Yours
Focus Reader — Dyslexia & ADHD Reading AidMake Chrome Yours
FocusLine – Reading Ruler & Line ReaderMake Chrome Yours
Reading RulerMake Chrome Yours
ReadFocus — Focus Reading: Bold Word Starts, Reading Ruler & Dyslexia FontsMake Chrome Yours
Steadyline: Reading Ruler & Word Emphasis for ADHD and Dyslexic ReadersAccessibility
Frequently asked questions
Is Steadyline: Reading Ruler & Word Emphasis for ADHD and Dyslexic Readers safe to use?
Our latest automated scan rates the Chrome listing of Steadyline: Reading Ruler & Word Emphasis for ADHD and Dyslexic Readers at 70/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 Steadyline: Reading Ruler & Word Emphasis for ADHD and Dyslexic Readers require?
Steadyline: Reading Ruler & Word Emphasis for ADHD and Dyslexic Readers requests 3 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops Steadyline: Reading Ruler & Word Emphasis for ADHD and Dyslexic Readers?
Check the developer line on the store listing before installing — impersonators copy popular extension names.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 0.1.1
- Current listed version
- 0.1.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 3 critical and 14 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.