Screenshot reader™
🔍 Security Report Available View on Chrome Web StoreChrome will indicate if you already have this installed.
Overview
Screenshot reading support for Read&Write for Google Chrome™
Tags
Privacy Practices
✅ Does not collect your data
✅ Does not sell your data to third parties
✅ Does not use data for unrelated purposes
Security Analysis
Permissions
Code Patterns Detected
External Connections
Package Contents 43 files · 25.3MB
▾_locales2KB
▾en_GB
messages.json242B
▾en_US
messages.json242B
▾es
messages.json260B
▾fr
messages.json263B
▾id
messages.json242B
▾ms
messages.json242B
▾pt_BR
messages.json197B
▾pt_PT
messages.json197B
▾_metadata7KB
verified_contents.json7KB
▾assets26KB
▾icons24KB
icon128.png2KB
icon16.png412B
icon24.png283B
icon256.png12KB
icon32.png2KB
icon48.png512B
icon64.png4KB
off.png268B
on.png3KB
▾locales2KB
▾en_GB
messages.json242B
▾en_US
messages.json242B
▾es
messages.json260B
▾fr
messages.json263B
▾id
messages.json242B
▾ms
messages.json242B
▾nl
messages.json0B
▾pt_BR
messages.json197B
▾pt_PT
messages.json197B
▾features339KB
▾speech339KB
▾iframe339KB
speech-iframe.js142KBlarge
speech-iframe.legacy.js197KBlarge
speech.html76B
▾offscreendocument2KB
offscreendocument.bundle.js2KB
offscreendocument.html73B
▾pages
ocr.html220B
▾scripts124KB
init.js177B
main.js113KBlarge
ocr.js4KB
serviceworker.js6KB
▾tesseract24.8MB
▾traineddata14.7MB
eng.traineddata14.7MB
tesseract-core-simd.wasm.js4.6MBlarge
tesseract-core.asm.js5.3MBlarge
tesseract.min.js63KBlarge
worker.min.js99KBlarge
manifest.json3KB
What This Extension Does
The Screenshot reader™ extension provides screenshot reading support for users of Read&Write for Google Chrome, likely enhancing accessibility features.Permissions Explained
- activeTab: Allows the extension to access and manipulate the currently active tab in the browser.
- offscreen: Not explicitly described in this report. Typically allows an extension to run scripts on tabs that are not visible, which can be useful for background tasks.
- <all_urls>: Grants the extension permission to access and manipulate any URL, including those with sensitive or restricted content (e.g., internal company websites).
What We Found in the Code
- [high] eval() used — can execute arbitrary code: The use of
eval()is a high-risk pattern because it allows execution of arbitrary JavaScript code, which can lead to security vulnerabilities if not properly sanitized. However, without more context (e.g., whethereval()is called with user-provided strings), it's difficult to assess the risk. - [high] Function constructor used — dynamic code execution: Similar to
eval(), using the function constructor for dynamic code execution can pose a security risk if not properly managed. Again, without more context, it's hard to evaluate the specific risk here. - [medium] innerHTML assignment — potential XSS vector: Assigning HTML content directly to an element's
innerHTMLproperty is generally considered a medium-risk pattern because it can lead to cross-site scripting (XSS) vulnerabilities if untrusted data is used. However, in many cases, this is done for UI rendering purposes and not necessarily a security issue. - [info] Makes HTTP requests: This flag indicates that the extension makes external API calls or communicates with servers. While this is normal behavior for many extensions, it's worth noting for users who might be concerned about data transmission.
External Connections
The extension communicates with several domains:- www.w3.org, github.com, and unpkg.com are likely used for library dependencies or API calls.
- pajhome.org.uk is associated with a project called "naptha," which seems unrelated to the extension's purpose. This might be an error or an unexpected connection.
- speech.speechstream.net could be related to speech-to-text functionality, aligning with the extension's accessibility focus.
- tessdata.projectnaptha.com, opencollective.com, and pajhome.org.uk are less clear in their relevance without more context.
Things to Consider
Given the Screenshot reader™ extension's purpose as an accessibility tool for Read&Write users, it seems unusual that it requires such broad permissions (e.g.,<all_urls>). Users might want to consider whether this level of access is necessary or if there are alternative extensions that achieve similar functionality with more limited permissions. The use of eval() and the function constructor without further context raises some security concerns but should be evaluated in light of the extension's overall behavior and purpose.Similar Extensions
More in Make Chrome Yours/accessibility →Boost reading and writing confidence across all types of content and devices, in class, at work, and at home.
360 Internet Protection
Create, convert, connect: take your digital documents to the next level with OrbitNote.
Dark mode for every website. Take care of your eyes, use dark theme for night and daily browsing.