Listen Anywhere: Read Aloud & Text to Speech 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: ajpfpbbclpohfdlmfmcciofhhpccbbnf
Permissions (10)
- View open tabs
- Execute scripts in pages
- Manage downloads
Related extensions
Read Aloud WebpageMake Chrome Yours
Read Aloud: Text to Speech for Any WebpageMake Chrome Yours
Article Audio - Read Aloud with AI Text to Speech (TTS)Productivity
TextReads: Listen to Articles — Text to Speech (TTS) ReaderProductivity
Web Reader - Listen to Any ArticleMake Chrome Yours
Audioread — Listen to Any PageProductivity
Frequently asked questions
Is Listen Anywhere: Read Aloud & Text to Speech safe to use?
Our latest automated scan rates the Chrome listing of Listen Anywhere: Read Aloud & Text to Speech at 75/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 Listen Anywhere: Read Aloud & Text to Speech require?
Listen Anywhere: Read Aloud & Text to Speech requests 10 permissions. The most significant: View open tabs, Execute scripts in pages, Manage downloads. See the full breakdown in the security report.
Who develops Listen Anywhere: Read Aloud & Text to Speech?
Listen Anywhere: Read Aloud & Text to Speech is published by jfriedman028. 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
- 0.2.1
- Current listed version
- 0.2.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 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.