REA Analyzer Preparation

Choose a source-backed REA analysis route from your host, target type and existing tools. Generate a self-reported preparation checklist and scoped commands for Ghidra, Hopper, IDA or static inspection.

Three source-backed analysis routes

Choose native binaries, static JavaScript/Electron or managed .NET PE/CLI. Host OS/architecture, native format, existing tools, Node version and target permission are self-reported. This page scans no machine, target, license or connection. Export the source-linked checklist as Markdown or JSON and run generated diagnostic commands yourself.

  • Native: choose Ghidra, Hopper or an existing IDA MCP bridge, subject to the selected host, target and provider requirements.
  • JavaScript/Electron: static application analysis, without a native provider or executing the target. Native add-ons need a separate native route.
  • .NET: built-in managed metadata/CIL inspection without loading assemblies or a native analyzer. NativeAOT belongs to the native route.

Native provider prerequisites

  • Ghidra: Ghidra 12.1.x; native 64-bit full JDK within the installation's Java bounds (current 12.1: 21+); javac and matching native decompiler. Emulated/mismatched JDKs do not qualify. Exact source.
  • Hopper: Compatible existing launcher on a documented host; vendor license or demo terms and limitations. Linux installation/distribution and macOS automation permissions need local review. Exact source.
  • IDA MCP bridge: An existing IDA installation and explicit upstream MCP registration (REA_IDA_MCP_CONFIG). Legacy attached mode uses 1.4.0 GUI tools; headless needs idb_open/list/close, not merely a 2.0 version string. The separate native Free/Pro plugin profile is experimental. Exact source.

Windows Ghidra P0 is experimental and read-only. This selector admits its x64-host PE application/DLL route; other Windows native-format/architecture choices do not become ready automatically. Confirm fixed local NTFS storage and actual provider admission. Hopper is not offered for native Windows. IDA requires explicit existing MCP configuration and the correct upstream tool catalog.

Example preparation checklist

Offline, self-reported preparation only. No host, target, program, license or connection was scanned. Preparation items remain unresolved. Review the checklist before analysis.

  • Node runtime — unknown: REA 6.5.0: stable Node 22.19+, 24.11+ or 26+. This field is self-reported, not an executed version check.
  • Target permission — unknown: Confirm that you own the target or have permission to inspect it before replacing a sample path. This form cannot grant permission.
  • Linux process ownership prerequisite — action: Confirm procps-compatible ps on the REA process PATH. It is used for Ghidra and static JavaScript owned-process checks; no ps command ran in this page.
  • Native provider selection — reported: Ghidra: Documented Linux/macOS x64/arm64 host profile; exact installation prerequisites still need checking.
  • Existing provider installation — action: No existing installation was declared. Install/configure the selected tool using its own documentation before analysis.
  • Provider-specific prerequisites — action: Ghidra 12.1.x; native 64-bit full JDK within the installation's Java bounds (current 12.1: 21+); javac and matching native decompiler. Emulated/mismatched JDKs do not qualify.

No target-analysis example is emitted until all selected preparation conditions are confirmed. Even then, the result says self-reported; it is not a successful doctor or code execution result.

Baseline and sources

REA 6.5.0; revision 9e372c6bc914b15e2f778f969da4fd3e11483d78; source read 2026-10-18.