Ysopwnableandfactory-droid[bot]
7ae3c50a9d
Put setup, developer commands, MCP replies, and investigation recipes before client details and implementation references. Preserve existing guide anchors, examples, provenance, partial-result recovery, and provider restrictions. Correct verified documentation drift, synchronize the Ghidra capability wording, and regenerate metadata for skill version 40. Keep uncertain platform and lifecycle findings unchanged. Refs #2156. Validation: 56 focused tests, check:fast, docs:check, VitePress production build, format and link/example checks. Real isolated CLI/MCP probes cover Ghidra, NativeAOT, HAR, cancellation, Chrome, large ELF delivery, native type limits, and the new JS/managed/process/setup recipes. Heavy work uses two CPUs; a resource-heavy DOM probe was stopped and replaced by a smaller real CDP payload-limit control. Windows, macOS GUI, ADB, and the full CI matrix were not executed. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@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, 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 |
| 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.
