REA, a Reverse-Engineering Toolkit for Coding Agents, Passes 73,000 Stars and Ships Five Releases in 54 Hours
Software / news
REA, a Reverse-Engineering Toolkit for Coding Agents, Passes 73,000 Stars and Ships Five Releases in 54 Hours
The MIT-licensed project leaves the legal question of analysing other people's software to the user, and an open P1 bug says its newest version breaks a job the previous one finished.
REA, a toolkit that lets coding agents take apart compiled programs, had 73,114 GitHub stars and 15,414 forks on Sunday, 180 days after its maintainer created the repository on April 14. It shipped five releases between Oct. 7 and Oct. 9, and an open bug report says the newest one breaks a job its predecessor finished.
The repository belongs to a GitHub user named morluto, according to the GitHub API. The account dates from December 2020, lists 251 public repositories and 1,272 followers, and the README names no team or company behind the project. It is MIT-licensed.
What REA does when an agent points it at a binary
The README's example prompt reads: "Understand how search works in the Notes app, show me the evidence, and build a similar feature for my project." REA is the layer in between. It is an MCP server, meaning a local tool an agent such as Claude Code, Codex, Cursor or Gemini CLI can call, plus a command-line interface.
The table in the README lists 15 target types. Native binaries return pseudocode, assembly and call references, but only through Hopper, Ghidra or IDA, which the user has to have installed. JavaScript and Electron apps, .NET assemblies and websites need only Node.js 22.19 or later. Setup is npx rea-agents setup.
The README's worked examples include a trace of Notion's Electron clipboard bridge and a reconstruction of a DX-Ball sound calculation that the project says passes 3,205 original-x86 test cases. Both are the project's own claims.
Five releases in 54 hours
The releases page shows the pace. Version 5.0.0 went out at 17:26 UTC on Oct. 7. Version 6.3.0 followed at 23:56 UTC on Oct. 9.
| Version | Published (UTC) |
|---|---|
| 5.0.0 | Oct. 7, 17:26 |
| 6.0.0 | Oct. 8, 09:40 |
| 6.1.0 | Oct. 9, 01:08 |
| 6.2.0 | Oct. 9, 16:51 |
| 6.3.0 | Oct. 9, 23:56 |
Issue #1387, opened Oct. 10 and labelled P1: high, reports that analyze-javascript-application --json aborts on a large bundle that 6.2.0 completes. The README itself warns that "REA changes quickly, and new releases include frequent bug fixes", and tells users to update before reporting a bug.
That advice has a catch. The recommended update command, npx rea-agents@latest, runs whichever version is newest on npm at that moment. The installation guide says registrations written by setup are pinned to the installed version, so the unpinned path applies only when a user chooses it.
What 73,114 stars do and do not show
The README banner still celebrates 60,000 stars. The live count passed that figure some time ago.
Stars measure attention. The fork count is a second number to read beside it. REA's 15,414 forks are 21.1 percent of its stars. The same GitHub API shows 8.4 percent for mattpocock/skills and 5.0 percent for Microsoft's mxc.
- morluto/rea21.1 %
- mattpocock/skills8.4 %
- microsoft/mxc5 %
Source: GitHub REST API, repository endpoints, accessed 2026-10-11; ratios calculated by The Terminal
The ratio does not say why. A tool people copy to modify and a tool people star to bookmark would produce different numbers, and so would many other things. Neither figure counts people who run the package.
A German-language AItoolly write-up dated Oct. 7 says implementation details were still sparse at that point and gives no adoption figure. Stars and use have also come apart on Diagram Design, another agent repository this site has covered.
Permissions and the legal line
Setup edits the configuration files of each agent the user selects, with backups, and adds a stdio MCP entry named rea. The README says static JavaScript and .NET analysis reads files without running them. It also says "Runtime capture runs or interacts with the selected target using your user permissions."
On legality the README leaves the question to the reader. Its disclaimer says "You are responsible for obtaining any required authorization and complying with applicable laws." The licence covers REA's code, not the software it is pointed at. Agent plugin repositories such as Anthropic's knowledge-work plugins ship instructions; REA ships a tool that reads other people's compiled code.
The next date to watch is the project's next release. The maintainer has not published a schedule, and issue #1387 was still open when this article was filed.
Sources
More in Software
- 01Rust Borrow Checker Bug 11 Years Old Lets Safe Code Hide a Short-Lived Reference in a 'static ValueIssue #164250 shows a Drop impl smuggling a stack reference past the compiler on stable releases back to 1.85.0, and commenters trace variants to Rust 1.4.
- 02REA, a Reverse-Engineering Tool for AI Agents, Gained 52,186 GitHub Stars in a Day. It Has 653 Watchers.Three trackers report three different star totals for morluto/rea, and the 15 newest issues and pull requests show an installer still being patched.
- 03QGIS Merges a 'Closed Door' on AI-Written Code 13 Days After Proposing ItQEP 428 bars LLM, AI and agent-assisted code from qgis/qgis after a vote that closed October 7, with two follow-up proposals still open.
- 04Anthropic Moved Its Monorepo Off Git to Scion as Daily Merges Grew From 2,500 to 30,000A seven-person team built Scion in five months. The post is candid about merge-queue conflicts and says the system is not a git replacement for general use.