Not reviewed
No code review on record
We have not reviewed this extension’s code, so we cannot vouch for it either way. Check the permissions below to decide whether it asks for more than it needs.
Want us to read this extension's code? Ask for a review and we'll queue it.
2 indicators in this extension
Every finding is verified by a security analyst. Unlock the code evidence, indicators and version history.
What our analysis found
EAR-i Parser is not yet reviewed by Extension Auditor. Its permissions mean it can inject scripts into pages. It was last updated in September 2026.
EAR-i Parser Chrome extension security report
ID: pflicdhmpggnoijpbomlfcifmohpmich
Supported Languages
Extension Info & Metadata
Publisher Contextual Analysis
- Author
- hello-eari.com
- Privacy
- Privacy Policy
- Help
- Help Center
- MX records exist
- Yes
- Domain exists
- Yes
- Is disposable
- No
- Is role-based
- No
- Mailbox exists
- Yes
You reached today's free scan limit (3/3 unique extensions).
Upgrade for full visibility.
Screenshots & videos
Install growth
2 indicators in this extension
Every finding is verified by a security analyst. Unlock the code evidence, indicators and version history.
About this extension
Convert messy text to EAR-i© format: E: A: R: I@ with editable fields
Read the publisher’s full description
Turn chaos into structure — right from the page you're reading. Select any messy text — an incident report, a meeting note, an email, a Slack thread, a job posting — right-click, and choose "Parse to EAR-i." One click atomizes it into a deterministic four-line schema built for humans and AI systems to read the same way, every time: E: [Entity#ID] A: [Fact1] ; [Fact2] ; [Fact3] R: [Cause] | [Effect] I@ [Owner]: [Action] ; By: [Deadline] ; Where: [Place/Tool] ⚙️ Why it's different Most "text cleanup" extensions these days just wrap an AI API and hope for the best. EAR-i™ doesn't. It runs entirely in your browser — no API calls, no accounts, no data leaves your machine, no hallucinated facts. What it finds, it finds for real. What it doesn't find, it leaves blank on purpose: a blank field means the source text didn't say who owns this or by when — which is exactly the gap you need to notice, not one an AI should quietly paper over for you. 🚀 See it work Raw input: "John reviewed server logs for bug #402 on Saturday. Disk usage reached 99%, which caused the API to crash. Need Sarah to clean up log files by Monday using SSH." EAR-i™ output: E: [Bug#402] A: [Server logs reviewed by John] ; [Disk usage at 99%] R: [High disk usage] | [API crash] I@ [Sarah]: [Clean up log files] ; By: [Monday] ; Where: [SSH] 🎯 Built for - Incident reports and postmortems - Meeting notes that need to become action items - Rambling emails that need to become ticket-ready structure - Structuring messy input before you hand it to an AI prompt - Anywhere "who owns this, and by when" keeps getting lost in prose 🛠️ Highlights - One right-click from any selected text on any webpage - Editable fields before you copy — you always get the final say - Deterministic regex engine: no AI, no data leaves your browser, no surprises - Clean, minimal popup for fast copy-paste into tickets, docs, or chat © 2026 Mario Havel Olivieri. All rights reserved. EAR-i™ | chaos<comms™ is a trademark of Mario Havel Olivieri.
User reviews
Extension files
Browse and explore files within this extension package
You reached today's free scan limit (3/3 unique extensions).
Upgrade for full visibility.
URLs
View the external URLs this extension communicates with to understand its network activity and data interactions.
2 indicators in this extension
Every finding is verified by a security analyst. Unlock the code evidence, indicators and version history.
Code Diff
Compare extension code between any two versions.
0 changed files detected
No comparable text files found between these versions.
You reached today's free scan limit (3/3 unique extensions).
Upgrade for full visibility.