FAQ · P0
What can this machine analyze?
A host-oriented capability sketch — not a promise that every provider is installed.
| Surface | Typical engine | Notes |
|---|---|---|
| Native binaries | Ghidra / Hopper / IDA (BYO) | OS + arch gates; Windows Ghidra is a specific P0 story |
| JavaScript / Electron | REA static JS graph | No native engine required; large ASAR has its own FAQ |
| .NET | Managed / native paths per docs | NativeAOT may fall through to native providers |
| Android | JADX (BYO) + Java | Often smoother on Linux/macOS; Windows users hit “not available here” prompts |
| Firmware / packs | Optional unpackers (BYO) | Separate prerequisites; do not invent tool installs |
| Browser / pages | Local Chrome-family + REA browser tools | May need REA_BROWSER_EXECUTABLE; profile isolation matters |
Ask doctor for the providers you care about. A missing Android/JADX path on Windows is frequently an environment limitation, not a broken npm install.