Readwright – EPUB, MOBI & AZW3 Ebook Reader with Read Aloud 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: lnipfellabpcmdefapbodfgnejogdjai
Permissions (3)
- Store local data
- Unlimited local storage
- Add context menu items
Related extensions
Reading App — EPUB, MOBI & FB2 Reader | Comic ViewerLifestyle
EPUB Viewer — Open & Read EPUB Files Online | FB2 ReaderLifestyle
EPUB Reader — Open ePub in BrowserProductivity
EPUB Reader – Readkave: FB2, MOBI & CBZTools
EPUB Reader – Read E-books Offline | BookFitOther
EPUB Reader – Read E-books Offline | BookFitTools
Frequently asked questions
Is Readwright – EPUB, MOBI & AZW3 Ebook Reader with Read Aloud safe to use?
Our latest automated scan rates the Chrome listing of Readwright – EPUB, MOBI & AZW3 Ebook Reader with Read Aloud at 80/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 Readwright – EPUB, MOBI & AZW3 Ebook Reader with Read Aloud require?
Readwright – EPUB, MOBI & AZW3 Ebook Reader with Read Aloud requests 3 permissions. The most significant: Store local data, Unlimited local storage, Add context menu items. See the full breakdown in the security report.
Who develops Readwright – EPUB, MOBI & AZW3 Ebook Reader with Read Aloud?
Readwright – EPUB, MOBI & AZW3 Ebook Reader with Read Aloud is published by Tabwright. 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.1
- Current listed version
- 1.0.1
- 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.