reverse-engineering-anything/docs/index.md at 2edf3b23c1465b7e6609b020d0eabfef438081a7

0 Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-10-26 17:35:11 +00:00

Files

T

Matt Van Horn 2edf3b23c1 feat(elf): inspect PT_NOTE and SHT_NOTE tables (#4837 )

Inspect selected ELF32/ELF64 PT_NOTE and SHT_NOTE declarations without executing
the artifact, retaining independent table identities, source ranges, descriptor
digests, GNU build-id/ABI fields and explicit coverage limitations.

Integrate mvanhorn's implementation and hardening with current main while
preserving byte-entropy registration and the Windows curated regression suite.
The maintainer follow-up uses ordinary merges/pushes, not history rewriting.

Executed validation: 96 focused/shared/docs tests, complete static/docs checks,
eleven real CLI/MCP pairs including GCC ELF32 and Clang big-endian PowerPC64,
and two actual Codex task traces checked against their Evidence. Full costs,
grader correction and verification limits are recorded in PR #4837.

Refs #6262.

2026-10-22 15:02:23 +08:00

7.7 KiB

Raw Blame History

layout, hero, features

layout

hero

features

home

name

text

tagline

actions

REA

Reverse Engineer Anything

Understand binaries, applications, and runtime behavior with one CLI and MCP server.

theme	text	link
brand	Get started	/installation

theme	text	link
alt	View on GitHub	https://github.com/morluto/rea

title	details	link
Investigate with your agent	Connect REA to your coding agent, describe the app or feature you want to understand, and follow the evidence.	/mcp-prompts

title	details	link
Inspect across formats	Explore native binaries, JavaScript and Electron apps, .NET assemblies, Android packages, firmware, and websites.	/installation

title	details	link
Keep the evidence	Analysis runs locally and returns observations, limitations, and unknowns through the CLI and MCP.	/mcp-contracts

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
Identify a desktop installation	Runtime candidates, evidence and follow-up files
Inspect native functions, references, or types	Native binaries, Go metadata, Rust dependencies, ELF notes, offline ELF layout, recorded crashes
Select a native provider or import format	Ghidra semantics, Windows, DOS, raw bytes, MIPS, PSP, NativeAOT, IDA, Kuna, 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	Godot PCK, .NET, Python packages, Android, Apktool resources, ADB acquisition, Apple, Harmony, firmware, WASM, EVM
Observe or compare a browser scenario	CDP observation, scenarios, runtime evidence, historical captures
Serve recorded behavior as an agent environment	Agent environments
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.

7.7 KiB Raw Blame History

Start with one command

Choose a guide

7.7 KiB

Raw Blame History