[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-97480":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":9,"totalLinesOfCode":9,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":9,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":16,"stars30d":16,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":17,"rankGlobal":9,"rankLanguage":9,"license":9,"archived":18,"fork":18,"defaultBranch":19,"hasWiki":18,"hasPages":18,"topics":20,"createdAt":9,"pushedAt":41,"updatedAt":42,"readmeContent":43,"aiSummary":44,"trendingCount":16,"starSnapshotCount":16,"syncStatus":45,"lastSyncTime":46,"discoverSource":47},97480,"rea","morluto\u002Frea","morluto","Reverse engineer anything with agents, from app behavior down to native binaries.",null,"https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea","TypeScript",365244,91563,1306,946,0,67,false,"main",[21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"ai-agents","binary-analysis","cli","coding-agents","decompiler","disassembler","mcp","mcp-server","model-context-protocol","reverse-engineering","static-analysis","agent-skills","reverse-engineering-tools","ai-agent-tools","dsh-plugin","cordis","dsh","hopper","ghidra","ctf","2026-10-22 20:06:00","2026-10-22 20:07:42","\u003Cdiv align=\"center\">\n\n**English** · [简体中文](README_zh.md) · [繁體中文](README_zh-TW.md) · [日本語](README_ja.md) · [한국어](README_ko.md) · [Türkçe](README_tr.md) · [Русский](README_ru.md) · [Tiếng Việt](README_vi.md) · [ไทย](README_th.md) · [Deutsch](README_de.md) · [Español](README_es.md) · [Français](README_fr.md) · [Українська](README_uk.md) · [Polski](README_pl.md) · [Português (Brasil)](README_pt-BR.md) · [العربية](README_ar.md) · [فارسی](README_fa.md)\n\n# REA: Reverse Engineer Anything\n\n### One MCP for reverse engineering across binaries, applications, and runtime behavior.\n\n**See a feature you like. Understand how it works, down to the binary level.**\n\n[![npm version](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002Frea-agents?style=flat-square&color=cb3837)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Frea-agents)\n[![CI](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Factions\u002Fworkflow\u002Fstatus\u002Fmorluto\u002Frea\u002Fci.yml?branch=main&style=flat-square&label=CI)](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Factions\u002Fworkflows\u002Fci.yml)\n[![MCP tool catalog](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FMCP-tool_catalog-5c4ee5?style=flat-square)](docs\u002Fmcp-contracts.md#generated-catalog)\n[![Node.js 22+](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FNode.js-22.19%2B-339933?style=flat-square&logo=nodedotjs&logoColor=white)](https:\u002F\u002Fnodejs.org\u002F)\n[![skills.sh](https:\u002F\u002Fskills.sh\u002Fb\u002Fmorluto\u002Frea?style=flat-square)](https:\u002F\u002Fskills.sh\u002Fmorluto\u002Frea\u002Freverse-engineer-anything)\n[![MIT license](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-MIT-f4c430?style=flat-square)](LICENSE)\n[![Discord](https:\u002F\u002Fimg.shields.io\u002Fdiscord\u002F1556595354999332884?logo=discord&logoColor=white&label=Discord&color=5865F2)](https:\u002F\u002Fdiscord.gg\u002FGkcryMnJDM)\n\n\u003Ca href=\"https:\u002F\u002Ftrendshift.io\u002Frepositories\u002F82054?utm_source=repository-badge&utm_medium=badge&utm_campaign=badge-repository-82054\" target=\"_blank\" rel=\"noopener noreferrer\">\u003Cimg src=\"https:\u002F\u002Ftrendshift.io\u002Fapi\u002Fbadge\u002Frepositories\u002F82054\" alt=\"morluto%2Frea | Trendshift\" width=\"250\" height=\"55\"\u002F>\u003C\u002Fa>\n\n**[Website](https:\u002F\u002Frea.tools\u002F) · [Guides](https:\u002F\u002Frea.tools\u002Fguides\u002F) · [Showcases](https:\u002F\u002Frea.tools\u002Fshowcase\u002F)**\n\n[Quick start](#quick-start) · [How REA works](#how-rea-works) · [What you can analyze](#what-you-can-analyze) · [Showcases](#showcases) · [FAQ](#faq) · [Documentation](#documentation)\n\n\u003Ccode>npx rea-agents setup\u003C\u002Fcode>\n\n\u003Cbr \u002F>\n\n\u003Cimg src=\"docs\u002Fassets\u002Frea-hopper-analysis.png\" alt=\"REA launching its analysis bridge inside Hopper while inspecting a native binary\" width=\"1200\" \u002F>\n\n\u003Cbr \u002F>\u003Cbr \u002F>\n\n\u003Ctable aria-label=\"REA community\">\n\u003Ctr>\n\u003Ctd align=\"center\" width=\"360\">\n  \u003Ca href=\"https:\u002F\u002Fdiscord.gg\u002FGkcryMnJDM\">\n    \u003Cimg src=\"docs\u002Fassets\u002Fdiscord.svg\" height=\"42\" alt=\"Discord\" \u002F>\u003Cbr \u002F>\n    \u003Cstrong>Join the Reverse Engineering Community\u003C\u002Fstrong>\n  \u003C\u002Fa>\u003Cbr \u002F>\n  \u003Csub>Discord · Q&A · Show and Tell\u003C\u002Fsub>\n\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftable>\n\n\u003Cbr \u002F>\n\n\u003C\u002Fdiv>\n\n---\n\nSee a feature in an app that you want in your own product? Ask your agent to investigate it with REA. It can inspect the app without its source code, explain how the feature works, show the evidence, and build a version for your project.\n\nREA connects your agent to tools for inspecting native binaries, JavaScript and Electron apps, .NET assemblies, and websites. You can also use the same tools from your terminal. Analysis runs locally, and results include the evidence and limitations behind each conclusion.\n\nSetup registers REA with your agent and installs matching workflow instructions. Native analysis can use an existing Hopper or Ghidra installation; setup can optionally install Hopper with approval. Static JavaScript analysis needs neither engine.\n\n> **[Visit the REA website](https:\u002F\u002Frea.tools\u002F)** for setup instructions, illustrated guides, and real case studies.\n\n## Quick start\n\n### Set up your agent\n\nWith Node.js and npm installed, run:\n\n```bash\nnpx rea-agents setup\n```\n\nChoose your agents, review the proposed changes, and approve them. Setup adds\nREA's MCP server and matching workflow instructions, with backups of existing\nconfiguration. Restart your agent afterward.\n\nSetup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build and\n[other agents](docs\u002Finstallation.md#supported-agents). See\n[installation and setup](docs\u002Finstallation.md) for provider configuration and\nmanual MCP registration.\n\n### Ask your agent\n\n```text\nUnderstand how search works in the Notes app, show me the evidence, and build a\nsimilar feature for my project.\n```\n\nReplace Notes with your target app and the feature you want to understand.\n\n### Use the terminal\n\nInspect an extracted JavaScript\u002FElectron app directory or ASAR:\n\n```bash\nnpx -y rea-agents@latest analyze-javascript-application \u002Fabsolute\u002Fpath\u002Fto\u002Fapp --json\n```\n\nThe result includes modules, imports, Electron boundaries and their evidence.\nReplace the path with your target, such as `\"D:\u002Fapps\u002Fexample\"` on Windows.\n\nTo install the `rea` command for regular use:\n\n```bash\nnpm install --global rea-agents\nrea --help\n```\n\nFor native analysis, configure a provider first. See the\n[CLI and Evidence guide](docs\u002Fcli.md) for native commands, provider selection,\nsnapshots and scripting.\n\n### Update REA\n\nREA changes quickly, and new releases include frequent bug fixes. Keep your\ninstallation up to date.\n\nFor an npm-installed CLI:\n\n```bash\nrea update\n```\n\nTo refresh your agent registrations and skill, run the setup command printed\nby the update.\n\nIf you use `npx`, update your agent setup with:\n\n```bash\nnpx rea-agents@latest setup\n```\n\nReview the setup changes and restart your agent. For one-off CLI commands,\nuse `npx rea-agents@latest` followed by the command.\n\n## How REA works\n\nYour agent calls REA through MCP to inspect the target and trace relevant code.\nREA returns findings with their evidence. The agent uses them to ask follow-up\nquestions, explain the behavior, or write and test an implementation.\nCLI commands use the same workflows.\n\n![REA investigation flow: your agent asks about a local target, REA inspects and traces it using analysis tools, and the agent uses the returned code, references and unknowns to explain, implement and test.](website\u002Fpublic\u002Fassets\u002Ffigures\u002Frea-investigation-flow.svg)\n\n[Open the full-size figure](website\u002Fpublic\u002Fassets\u002Ffigures\u002Frea-investigation-flow.svg).\n\n\u003Ca id=\"current-status\">\u003C\u002Fa>\n\n## What you can analyze\n\nREA requires Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+, plus npm.\nAdditional tools and host support depend on the target:\n\n| Target                 | What REA returns                                                                     | Requirements and guide                                                                                                                |\n| ---------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |\n| Native binaries        | Pseudocode, assembly, strings, symbols, calls and references                         | Hopper, Ghidra or IDA; [native analysis](https:\u002F\u002Frea.tools\u002Fguides\u002Fnative\u002F)                                                            |\n| Offline ELF layout     | Sections, segments, original symbols\u002Frelocations and static mitigation candidates    | Caller-supplied pwntools on Linux x64; [binary diagnostics](docs\u002Fbinary-diagnostics.md)                                               |\n| EVM bytecode           | Dispatch selectors, byte offsets, inferred arguments and mutability                  | Local raw\u002Fhex carrier; [offline EVM guide](docs\u002Fevm-bytecode.md)                                                                      |\n| Recorded Linux crashes | Raw notes, every recorded thread's registers\u002Fsignals and optional mapping candidates | Caller-supplied pwntools; optional GDB\u002Fpwndbg; [recorded crashes](docs\u002Frecorded-crashes.md)                                           |\n| JavaScript \u002F Electron  | Modules, imports, source maps, routes, IPC and native add-on relationships           | Node.js and npm; [application analysis](https:\u002F\u002Frea.tools\u002Fguides\u002Fjavascript\u002F)                                                         |\n| Websites               | Page structure, scripts, network observations and requested screenshots              | A Chrome-family browser; [browser analysis](https:\u002F\u002Frea.tools\u002Fguides\u002Fbrowser\u002F)                                                        |\n| Saved network captures | Requests, responses, exposed payloads and source locations                           | HAR; mitmdump on Linux for native mitmproxy captures; [capture guide](docs\u002Fweb-network-captures.md)                                   |\n| .NET assemblies        | Metadata, CIL instructions, declared native dependencies and build comparisons       | Static inspection; [managed-code guide](docs\u002Fmanaged-code-analysis.md)                                                                |\n| Android APKs           | Manifest declarations, classes, decompiled methods and references                    | Headless JADX and a full JDK on Linux\u002FmacOS\u002FWindows x64; [Android guide](docs\u002Fandroid-analysis.md)                                    |\n| Firmware               | Regions, extraction results and native-analysis handoffs                             | Binwalk \u002F Unblob on Linux; [firmware guide](docs\u002Ffirmware-analysis.md)                                                                |\n| Packages and resources | File inventories, digests, plists, Apple bundle anatomy and extracted resources      | [Artifact and JavaScript guide](docs\u002Fjavascript-artifact-reconstruction.md), [Apple applications](docs\u002Fapple-application-analysis.md) |\n| Process behavior       | Terminal output, interactions, exit and filesystem observations, and run comparisons | Linux\u002FmacOS with a native PTY; [process capture](docs\u002Fprocess-capture.md)                                                             |\n\nStatic JavaScript and .NET inspection read the supplied files without running\nthe application. Runtime capture runs or interacts with the selected target\nusing your user permissions; each runtime guide describes its effects.\n\n\u003Ca id=\"choosing-a-deep-analysis-provider\">\u003C\u002Fa>\n\nNative formats and host support vary by provider. See\n[Hopper and Ghidra setup](docs\u002Finstallation.md#hopper), the\n[IDA guide](docs\u002Fida-provider.md), and\n[experimental Windows Ghidra support](docs\u002Fwindows-ghidra-p0.md).\nGhidra also supports [16-bit DOS analysis](docs\u002Fghidra-dos.md).\nFor large binaries, raise its startup deadline with\n`REA_GHIDRA_STARTUP_TIMEOUT_MS`.\nFor provider selection, see the [CLI guide](docs\u002Fcli.md#choose-a-provider).\nCheck [release availability](docs\u002Finstallation.md#released-package-and-main)\nfor features added since the latest npm release.\n\n## Showcases\n\n[![Illustrations of the DX-Ball sound-pan, Notion clipboard-bridge, and TH04 bullet-ring showcases](docs\u002Fassets\u002Frea-showcases.png)](https:\u002F\u002Frea.tools\u002Fshowcase\u002F)\n\n### DX-Ball: reconstruct a sound-pan calculation\n\nFollow a sound call into its position-to-pan helper, inspect the instructions,\nand turn incomplete pseudocode into C. The reconstruction passes 3,205\noriginal-x86 cases and reproduces all 63 compiled function bytes.\n\n[Read the case study](https:\u002F\u002Frea.tools\u002Fshowcase\u002Fdx-ball\u002F) ·\n[Reconstruction repository](https:\u002F\u002Fgithub.com\u002FN0zoM1z0\u002Fdx-ball)\n\n### Notion: trace the Electron clipboard bridge\n\nFind the renderer's clipboard API, follow it through preload and IPC into the\nmain process, and inspect the rich clipboard format.\n\n[Read the case study](https:\u002F\u002Frea.tools\u002Fshowcase\u002Fnotion\u002F)\n\n### TH04: recover a DOS bullet-ring calculation\n\nInspect the original PC-98 game's 16-bit instructions, recover the fixed and\naimed angle calculations, and compare the reconstructed C++ with the\nhistorical compiler output.\n\n[Read the case study](https:\u002F\u002Frea.tools\u002Fshowcase\u002Fth04\u002F) ·\n[Reconstruction repository](https:\u002F\u002Fgithub.com\u002FN0zoM1z0\u002Fth04)\n\nIf you've used REA on something interesting, we'd love to see it. Share your\ncase in an [issue](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fissues) or a\n[pull request](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fpulls), including the target,\nyour question, how REA helped, and what you found.\n\n## FAQ\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Which agents can use REA?\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nAny agent that supports local MCP servers. Setup configures the\n[supported agents](docs\u002Finstallation.md#supported-agents); other clients can use\n[manual MCP registration](docs\u002Finstallation.md#mcp-registry).\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Do I need Hopper, Ghidra or IDA?\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nDeep native analysis uses one of them. Static JavaScript and .NET inspection\nwork without a native analysis engine. Setup can install Hopper after approval;\nGhidra and IDA use your existing installations. See [provider setup](docs\u002Finstallation.md#hopper).\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Do I need to start Hopper first?\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nREA starts Hopper when an operation needs it. On macOS, a first-run dialog may\nask you to choose demo mode or activate your license. See\n[Hopper startup and troubleshooting](docs\u002Finstallation.md#launcher-paths-and-troubleshooting).\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>What does installing the skill from skills.sh do?\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nThe skill supplies investigation instructions for your agent. Use `rea setup`\nto register REA's MCP server and install the matching instructions, then restart\nyour agent. See [skill-only installation](docs\u002Finstallation.md#skill-only-installation).\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>What code does REA return?\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nNative analysis returns pseudocode and assembly. JavaScript\u002FElectron analysis\nrecovers modules and their relationships. Your agent uses these findings to\nwrite and test an implementation; the [showcases](#showcases) give worked examples.\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Does REA upload my app?\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nREA analyzes targets locally. Your agent receives the tool results, and its\nmodel provider has its own data policy.\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>What should I do if I hit a bug?\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nUpdate first; a recent release may already fix it.\n\nFor an npm-installed CLI:\n\n```bash\nrea update\n```\n\nFor agent setup through `npx`:\n\n```bash\nnpx rea-agents@latest setup\n```\n\nIf you're using an agent, complete the [setup refresh](#update-rea) and restart\nit. Retry the same task. If the problem persists, [open an issue](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fissues)\nwith your REA version, target type, steps to reproduce and error output.\n\n\u003C\u002Fdetails>\n\n## Documentation\n\nStart with the website's [worked guides](https:\u002F\u002Frea.tools\u002Fguides\u002F).\nFor exact options, prerequisites and result contracts:\n\n- [Installation and setup](docs\u002Finstallation.md): agent registration, provider configuration, updates and uninstall.\n- [Readiness and troubleshooting](docs\u002Finstallation.md#check-readiness-for-your-task): diagnose one agent or analysis engine.\n- [CLI and Evidence](docs\u002Fcli.md): commands, provider selection, snapshots, import\u002Fexport and exit statuses.\n- [MCP contracts](docs\u002Fmcp-contracts.md) and [agent prompts](docs\u002Fmcp-prompts.md): tool results, sessions and guided investigations.\n- [Tool catalog](docs\u002Fmcp-contracts.md#generated-catalog): generated inventory of tools, providers and CLI commands.\n- [Roadmap](docs\u002Froadmap.md): planned work and capability trackers.\n\nReport vulnerabilities through [SECURITY.md](SECURITY.md).\n\n## Star history\n\n🎉 **30,000 GitHub stars — thank you!**\n\nThanks to everyone using REA, reporting bugs, requesting features, testing builds, and contributing fixes.\n\n\u003Ca href=\"https:\u002F\u002Fwww.star-history.com\u002F?repos=morluto%2Frea&type=date\">\n  \u003Cpicture>\n    \u003Csource media=\"(prefers-color-scheme: dark)\" srcset=\"https:\u002F\u002Fapi.star-history.com\u002Fchart?repos=morluto\u002Frea&type=date&theme=dark&legend=top-left\" \u002F>\n    \u003Csource media=\"(prefers-color-scheme: light)\" srcset=\"https:\u002F\u002Fapi.star-history.com\u002Fchart?repos=morluto\u002Frea&type=date\" \u002F>\n    \u003Cimg alt=\"REA GitHub star history\" src=\"https:\u002F\u002Fapi.star-history.com\u002Fchart?repos=morluto\u002Frea&type=date\" \u002F>\n  \u003C\u002Fpicture>\n\u003C\u002Fa>\n\n## Disclaimer\n\nREA provides tools for lawful reverse-engineering research, analysis, and reconstruction. You are responsible for obtaining any required authorization and complying with applicable laws. The project does not endorse illegal or unauthorized use.\n\nREA is an open-source software project. We have not issued or endorsed any cryptocurrency or token. Tokens using the REA name are not affiliated with the project.\n\n## Contributing\n\nWe'd love your help with REA! [Open an issue](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fissues) to\nreport a bug or suggest a feature, or [send a pull request](https:\u002F\u002Fgithub.com\u002Fmorluto\u002Frea\u002Fpulls)\nto improve the code or docs.\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and checks,\n[testing](docs\u002Ftesting.md) for verification lanes, and the\n[architecture map](docs\u002Farchitecture.mermaid) for the project structure.\n\n## License\n\n[MIT](LICENSE)\n","REA 是一个基于 AI 代理的逆向工程工具，支持对应用程序行为、运行时环境及原生二进制文件进行自动化分析与理解。它通过 MCP（Model Context Protocol）协议集成多种底层能力，内置反编译、反汇编、静态分析等技能，并可与 Hopper、Ghidra 等主流工具协同工作；采用 TypeScript 实现，提供 CLI 接口和插件化架构。适用于安全研究人员、CTF 参赛者、漏洞分析师及需要在无源码条件下理解第三方软件逻辑的开发者场景。",2,"2026-10-23 04:07:52","trending"]