Aloud: Natural Text to Speech Reader, Offline 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: ilnojbdjpnnlkjbmldpgbgckkkifheeo
Permissions (7)
- Execute scripts in pages
Related extensions
ReadThis: Read Aloud Text to Speech with Natural Offline VoicesProductivity
Read Aloud: Text to Speech for Any WebpageMake Chrome Yours
PDF Reader Aloud — Read PDF Out Loud, Text to SpeechMake Chrome Yours
ReadThatOutProductivity
Aloudly – Text to Speech & AI Read Aloud: Natural Voice Reader for Any PageMake Chrome Yours
Aloud: Natural Text to Speech Reader, OfflineOther
Frequently asked questions
Is Aloud: Natural Text to Speech Reader, Offline safe to use?
Our latest automated scan rates the Chrome listing of Aloud: Natural Text to Speech Reader, Offline at 67/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 Aloud: Natural Text to Speech Reader, Offline require?
Aloud: Natural Text to Speech Reader, Offline requests 7 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops Aloud: Natural Text to Speech Reader, Offline?
Aloud: Natural Text to Speech Reader, Offline is published by Smail Oujaoura. 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.4
- Current listed version
- 1.0.4
- 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.