DEDUPEDAuthorization notice. rea is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forIT admin or security reviewer vetting an Android app before approving it for staff devices
The problemYou cannot tell what permissions and components an APK declares or how its key methods behave.
The outcomeA report of manifest declarations, classes and decompiled methods you can review.
What you need first
- Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+, plus npm
- An MCP-capable AI agent such as Claude Code, Codex, Cursor or Gemini CLI
- For native binaries: Hopper, Ghidra or IDA installed locally
- For websites: a Chrome-family browser
- On Linux: a procps-compatible ps on PATH for JavaScript/Electron analysis
Steps
- Install headless JADX if you do not have it.
- Run npx rea-agents setup and restart your agent.
- Ask the agent to analyze the APK with REA and list manifest declarations.
- Ask it to decompile and explain the methods that handle the behavior you worry about.
Prompt for your agent
Use REA to analyze the APK at <path to apk>, list its manifest declarations and explain what <suspicious behavior> does in the decompiled methods. Verify each claim cites a class or method.
Caveat. APK analysis depends on JADX being available. Only inspect apps you are authorized to review; decompiled output is an approximation of the original code.
About rea
A plug-in that lets your AI agent take apart an app and explain how a feature works. Part of this week's top 10 repos: ranked #1 on Repo Radar. View morluto/rea on GitHub.
More with rea
- Rebuild a feature you saw, in your own project Have your agent study a feature in an app, then write and test a version for your codebase.
- Map how a website's front end behaves Let your agent inspect a site's page structure, scripts and network calls and explain what the client does.
- Learn how a feature in another app works Point your agent at an installed app and get an explanation of one feature, with the evidence behind it.
- Pull apart a game's web build Use your agent to inspect a game's WASM web build and surface what it contains.
- Understand traffic from a saved HAR or SAZ file Feed a saved network capture to your agent to see requests, responses and the payloads they expose.
- List modules and IPC in an Electron app Run one command on an extracted Electron app or ASAR to see its modules, imports and process boundaries.
- List types and methods in a Unity game Decode a Unity IL2CPP metadata file to see assembly images, type names and method names.
- Get readable pseudocode from a native binary Connect your agent to Hopper, Ghidra or IDA and ask what a native program's function does.
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page