reverse-engineering-anything/docs/index.md at b4938aed58737293a6987630476632619713f5cd

0 Fork 0

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

Files

T

gensokyo-dev b4938aed58 feat(artifacts): triage desktop installation directories (#5207 )

* feat(artifacts): triage desktop installation directories

* fix(artifacts): retain completed probes through failed file cleanup

* perf(artifacts): decode only assembly reference names for desktop triage

* fix(artifacts): enforce exact signatures and responsive directory probes

* fix(artifacts): recognize Unity bundles and bound FORM chunks

* fix(artifacts): retain bounded desktop omission evidence

* fix(artifacts): select ASAR targets before inventory probes

* chore: preserve tested upstream HTTP owner during integration

* fix(artifacts): reuse Mach-O signatures for FAT64 desktop probes

* fix(artifacts): expose bounded desktop probe diagnostics

* fix(artifacts): derive desktop snapshots from observed source identities

* fix(artifacts): admit desktop facts before JSON expansion

2026-10-20 04:01:36 +08:00

6.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, 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	.NET, 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.

6.7 KiB Raw Blame History

Start with one command

Choose a guide

6.7 KiB

Raw Blame History