bcc141549a
Add bounded, read-only inspection of packaged Electron fuse state for ELF, PE, and Mach-O applications through CLI and MCP workflows. Preserve artifact provenance and unknown values, resolve app bundles without execution, reject malformed or overlapping containers before scanning, and keep output compact for agent use. Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com> Co-authored-by: morluto <76467478+morluto@users.noreply.github.com> Co-authored-by: N0zoM1z0 <161784452+N0zoM1z0@users.noreply.github.com> Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
5.9 KiB
5.9 KiB
layout, hero, features
| layout | hero | features | |||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| home |
|
|
Start with one command
npx rea-agents setup
Choose your agent, review the planned changes, and approve setup. Native binary analysis can use an existing Hopper, Ghidra, or IDA installation; static JavaScript analysis needs no native analysis engine.
For a first result from an extracted JavaScript application or ASAR:
npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json
See installation and setup for requirements and configuration.
For runtime instrumentation, see the Frida guide.
Choose a guide
| Task | Guides |
|---|---|
| Inspect native functions, references, or types | Native binaries, Go metadata, Rust dependencies, offline ELF layout, recorded crashes |
| Select a native provider or import format | Ghidra semantics, Windows, DOS, raw bytes, MIPS, PSP, NativeAOT, IDA, JEB |
| Analyze JavaScript or Electron artifacts | Static analysis, tracing and comparisons, application graph, source recovery |
| Compare static JavaScript with runtime observations | Runtime attribution, reconciliation, Electron observation, Electron fuses |
| Inspect assemblies, packages, or firmware | .NET, Android, Apktool resources, ADB acquisition, Apple, Harmony, firmware, WASM, EVM |
| Observe or compare a browser scenario | CDP observation, scenarios, runtime evidence, historical captures |
| Trace captured website source | Source locations, module traces, script export |
| Capture and compare a command | Process capture |
| Use CLI/MCP and retain evidence | CLI, MCP contracts, agent prompts, obligation ledgers |
For development, use testing, client verification, tool design, and releasing. Reconstruction readiness describes a development conformance verifier. The 6.2 migration records that release's compatibility changes; the roadmap tracks future work.
