0e6eca4085
* feat(native): read embedded cargo-auditable Rust dependency lists * fix(native): trim PE section padding and compute dependency cycles iteratively * fix(native): ignore SHT_NOBITS sections and validate dependency edges linearly * fix(native): bound compiler path scanning and retained hashes * fix(rust): pass package arrays as named parameterized test cases * fix(rust): admit graph expansion and preserve resource units * fix(rust): reject malformed packages, false cycles, and hidden compiler paths Fail the first malformed cargo-auditable package before Zod collects an issue per field. Require cyclic dependency indices to match the cycles in package dependencies. Keep read-only ELF ranges when a section name does not fit the bounded name window, so a rustc path in that range is still reported. * fix(ci): repair integrated checks and Hopper test baseline * fix(go): verify Mach-O sections against segments --------- 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: Cursor Agent <cursoragent@cursor.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 |
| 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.
