Pixie Reader: Text-to-Speech, TTS, PDF, Web Highlight & OpenDyslexic 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 reportEdge listing ID: hinaankffeaehkhgdiljhepdlinekogo
Permissions (5)
- Access current tab
- Store local data
- Add context menu items
Related extensions
Syllable ReaderLanguage Support
Pixie Reading Ruler: Boost Reading Focus ToolAccessibility
WebOutLoud - Text to Speech Web ReaderProductivity
Pixie: Accessibility and Productivity Reader AddonAppearance
Pixie Reader: Text-to-Speech, TTS, PDF, Web Highlight & OpenDyslexicMake Chrome Yours
Pi Reader: Free AI Text to Speech with Natural Voices, TTSAccessibility
Frequently asked questions
Is Pixie Reader: Text-to-Speech, TTS, PDF, Web Highlight & OpenDyslexic safe to use?
Our latest automated scan rates the Edge listing of Pixie Reader: Text-to-Speech, TTS, PDF, Web Highlight & OpenDyslexic at 54/100 (elevated 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 Pixie Reader: Text-to-Speech, TTS, PDF, Web Highlight & OpenDyslexic require?
Pixie Reader: Text-to-Speech, TTS, PDF, Web Highlight & OpenDyslexic requests 5 permissions. The most significant: Access current tab, Store local data, Add context menu items. See the full breakdown in the security report.
Who develops Pixie Reader: Text-to-Speech, TTS, PDF, Web Highlight & OpenDyslexic?
Pixie Reader: Text-to-Speech, TTS, PDF, Web Highlight & OpenDyslexic is published by Oziku Technologies LLC. 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
- Edge
- Checked version
- Not provided in this assessment
- Current listed version
- 4.4.1
- Assessment updated (UTC)
- Assessment status
- Completed
Recorded findings: 1 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.