Lab

Find an export path in your Electron app

Static JS/Electron inspection on a build you ship — no native engine required.

Do not point REA at third-party apps you are not authorized to reverse. · Compliance

Goal

List entry modules and the function that writes the export file.

Why reverse engineer

Support asked “where does CSV leave the app?” and you want the agent to gather the graph first.

Sample prompt

› Use REA to inspect /absolute/path/to/our-electron-app (or the .asar we ship). Show export-related entry points, calls, and source locations. Mark anything unresolved.

Evidence path (illustrative)

Staggered reveal of a typical inspection chain.

entry main process

mod exportService

io writeCsv()

Return channel

REA returns Evidence / structured results into the agent session (MCP tools or CLI JSON).

Agent role

Interpret Evidence, explain the rule, list unknowns. Writes stay behind your approval.

Suggested steps

Use your own artifact

Company build, personal project, or a sample you have written permission to analyze.

Static first

JS/Electron static analysis does not need Ghidra/Hopper/IDA.

Keep writes gated

Ask for a report only; file changes stay behind your approval.

← All examples Install Showcase