Is Voice Out: Read Aloud Text to Speech Reader Safe? — Extension Safety Profile

This extension requests permissions to read aloud text from the current page, which explains the need for activeTab, scripting, and tts. The contextMenus and storage permissions support convenient voice controls and settings. More notably, it also asks for webRequest access on specific Google domains, its own website, and a localhost address. While these could enable translation features or a local companion app, webRequest allows observation and potential modification of network requests to those hosts, which is a broader capability than simply fetching data.

For any text-to-speech tool, a careful user should be aware that reading aloud requires the extension to see page content, so it is wise to avoid using it on highly sensitive sites. In this case, the host-level webRequest permissions mean the extension could technically see information exchanged with Google Translate or Cloud services; if you are logged into those accounts, it might have access to authentication cookies. The localhost access suggests a possible local server, which could in turn interact with your system beyond the browser, so you should only trust such a configuration if you intentionally installed a companion application.

The safety score highlights a wide gap between the publisher’s identity transparency (60%) and its maintenance record (100%). The low identity score indicates limited public documentation about who develops the extension, making it harder to hold a party accountable. In contrast, the perfect maintenance score shows the extension is actively updated and well-managed, which reduces the risk of abandonment or unpatched vulnerabilities. This mixed profile is common for functional third-party tools: the extension may work well, but the user bears the burden of trusting a largely anonymous publisher.