Analyzing Electron apps with REA

Last updated: · By the RepoRead editorial team · Unofficial guide
Quick answer

In REA 6.5.0 (released October 14, 2026), static Electron / JavaScript analysis is built into the CLI and MCP server. Point analyze-javascript-application at an authorized extracted app directory or ASAR; you do not need Hopper, Ghidra or IDA for that lane.

RepoRead (rea-github.com) is an unofficial guide. Prefer morluto/rea and rea.tools when anything conflicts.

What you get back

WorkflowStatic JavaScript / Electron application graph
CLIanalyze-javascript-application (also selected by generic rea analyze on dirs/.asar without --provider/--snapshot)
ReturnsModules, imports, source maps, routes, IPC, native add-on relationships (per README)
Native engineNot required for this lane
Verified2026-10-18 (UTC) against REA 6.5.0 docs

Steps

1. Authorize the target

Only analyze apps you own, open-source projects under their licenses, or software covered by a written engagement. See REA's DISCLAIMER.md.

2. Run the analyzer

npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json
# or, with a global install:
rea analyze-javascript-application /absolute/path/to/MyApp.app/Contents/Resources/app.asar --json

On Windows, upstream examples use shapes like "D:/apps/example".

3. Save Evidence and project a view

rea analyze-javascript-application /absolute/path/to/app --json > app-evidence.json
jq -c '{source: {kind: "inline", evidence: .}, view: {kind: "summary"}}' app-evidence.json > app-view.json
rea inspect-analysis-view app-view.json

Module page view example:

{"kind": "page", "collection": "modules", "offset": 0, "limit": 32}

Read more about Evidence semantics on What REA “evidence” means.

When static Electron analysis is enough

GoalUse
Module graph, IPC, routesanalyze-javascript-application
Deep code inside a .node addonNative provider (Ghidra/Hopper/IDA) separately
Live window / network behaviorBrowser / capture guides upstream — not this command

Linux prerequisite

Install procps or procps-ng so a compatible ps is on REA's PATH. Missing ps fails before the supervised child starts. See common errors.

FAQ

Do I need Ghidra or Hopper for Electron apps?

Not for the static JavaScript/Electron workflow. Native .node add-ons still need a configured native provider if you dig into compiled code.

ASAR or unpacked folder?

Upstream accepts an extracted application directory or an ASAR. Prefer absolute paths so CLI and MCP resolve the same target.

Will REA run the Electron app?

The static application workflow reads the files you supply. Runtime capture is a separate lane documented upstream — do not confuse the two.

Why is Evidence so large?

Upstream documents complete application Evidence that can reach hundreds of megabytes (example: ~334 MB Obsidian Evidence → ~10 KB summary view). Save to disk and project a view.

Can I analyze any Electron app from the store?

Only with authorization. DRM bypass and unauthorized copying are out of scope for RepoRead and for REA's disclaimer.

Sources