morluto / rea Architecture and code health
Reverse engineer anything with agents, from app behavior down to native binaries.
This connects Repowise to morluto/rea's code. It does not install rea.
Repowise maps public repos from their source. Not affiliated with morluto. What is Repowise?
github.com/morluto/reaIndexed at eacbd25
What is rea?
rea is a reverse-engineering toolkit that lets AI agents and terminal users inspect native binaries, JavaScript and Electron apps, .NET assemblies, and websites without their source code. It connects an agent to these analysis tools through MCP, and the same workflows can be run from a terminal. Analysis runs locally, and results include the evidence and limitations behind each conclusion. The project is written mainly in TypeScript. To install it, run npx rea-agents setup and follow the steps below. Its code health is 8.3 out of 10 (Good), ranked #51 of 4,000+ indexed repos. The last commit to rea was on Nov 22, 2026, and 38 people have contributed.
As of commit eacbd25, indexed Nov 22, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.
For agentsrea.md
Repo facts: type, license, health, rank, contributors
| License | MIT |
|---|---|
| Code health | 8.3 / 10 (Good) |
| Health rank | #51 of 4,000+ indexed repos |
| Last commit | Nov 22, 2026 |
| Contributors | 38 |
| Bus factor | 1 |
| Size | 8,423 files, 2,048,585 lines |
Install rea
Commands copied from the README
- 1Connect your agent by running the setup command from a trusted directory outside the project you plan to analyze, with Node.js and npm installed.
npx rea-agents setup - 2Analyze an extracted JavaScript or Electron app directory from the terminal, replacing the path with your target.
npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json - 3Install the rea command for regular use.
npm install --global rea-agents - 4List the available rea command options.
rea --help
Releases on GitHub (latest rea-agents-6.10.1, Nov 20, 2026)
Explore rea
- DocumentationModule-by-module documentation, 4,718 pages.
- ArchitectureDependency graph, layers and third-party dependencies.
- Code healthEvery file's score and the findings behind it.
- CommitsEach commit's effect on code health.
- OverviewEverything else the index found: contributors, decisions, what changed this week.
Ask about this code in your agent
This connects Repowise to rea's code. It does not install rea. To install rea, use the install steps.
Useful if you want to change or fork rea: your agent can ask how it is put together and get answers that cite its files.
Ask about rea
Answers come from rea's README and source, with the files they cite. Two free answers a day without an account.
Want this for your own codebase? Map your repo free
About this page
Get a page like this for your own codebase
Repowise built this map of morluto/rea from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.
Free for 2 public repos, with a page like this one. No card. See how Repowise works
Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub
morluto/rea FAQ
What is rea?
rea is a reverse-engineering toolkit for AI agents and terminal users. It inspects native binaries, JavaScript and Electron apps, .NET assemblies, and websites without their source code.
How does rea work?
rea connects an agent to its analysis tools through MCP, and the same workflows can run from the rea command in a terminal. Analysis runs locally, and results include the evidence and limitations behind each conclusion.
How do I install rea?
rea is set up by running npx rea-agents setup from a trusted directory outside the project you plan to analyze, with Node.js and npm installed. Setup registers rea with your agent and installs its workflow instructions. See the install steps
What language is rea written in?
rea is written mainly in TypeScript, with 7089 TypeScript files and 512 JavaScript files. It also has smaller amounts of Python, Java, C and Swift code.
How is the rea code organized?
The src directory holds 4604 files, including domain analysis code under src/domain and native parsers under src/native. Tests live in the tests directory, and scripts, bridge and website hold 603, 47 and 17 files.
Who is rea for?
rea is for lawful research, education, interoperability, software preservation, and analysis of software you own or are authorized to examine. Developers also use it to ask an agent how an app feature works.
What license does rea use?
rea uses the MIT license, identified as MIT.
Code health
Hotspots average 5.9, the place fixes pay off most.
On the leaderboards:#20 of 70 TypeScript repos
Key features of rea
- rea lets an agent inspect native binaries, JavaScript and Electron apps, .NET assemblies, and websites without their source code.
- Analysis runs locally, and results include the evidence and limitations behind each conclusion.
- rea can analyze an extracted JavaScript or Electron app directory or ASAR file from the terminal and output JSON.
- Setup registers rea with an agent and installs matching workflow instructions.
- rea can build a local reinforcement learning environment from a recorded web session or a Linux desktop app.
How morluto/rea works
Input enters either through an agent's MCP connection or through the rea command in a terminal, and both use the same workflows. The src directory holds most of the code, 4604 files, including domain analysis code under src/domain/javascript and native analysis code under src/native. Parsers for binary formats live in src/native, such as src/native/elf/ElfNoteParser.ts for ELF notes and src/native/windows/WindowsShortcutParser.ts for Windows shortcut files. Native decompilation can use an existing Hopper, Ghidra, IDA or Kuna installation, while static JavaScript analysis needs no native engine. The tests directory holds 2465 files, and the bridge directory holds 47 files.
The codebase has 8,423 files and 52,773 symbols in 9 modules, led by TypeScript, JavaScript and Python. Code health is 8.3 out of 10, rated good.
Maintain morluto/rea?
Claim this page, add a badge to the README, or re-index it.
Claim this page
Sign in with GitHub and we check that you are an admin or maintainer of morluto/rea. Then add a badge to the README that links readers here.
Add a badge to your README
Readers click through to this page and can ask rea's code a question. A badge also re-indexes the repo every week and marks you as the verified maintainer.
[](https://repowise.dev/repo/morluto/rea?src=badge_ask)Paste it at the top of README.md, under the title.
Added it already? Verify to get the mark now instead of tomorrow.
Need HTML or the larger health card? More formatsHide more formats
This badge as HTML
<a href="https://repowise.dev/repo/morluto/rea?src=badge_ask"><img src="https://api.repowise.dev/badge/wiki/morluto/rea.svg?label=ask" alt="repowise: Ask this codebase"></a>Code health card
The score, its change since the last index, and when it was measured. Follows the reader's light or dark theme.
<a href="https://repowise.dev/repo/morluto/rea?src=badge_card"><picture><source media="(prefers-color-scheme: light)" srcset="https://api.repowise.dev/badge/health/morluto/rea.svg?style=card&theme=light"><img src="https://api.repowise.dev/badge/health/morluto/rea.svg?style=card" alt="repowise code health" width="500" height="168"></picture></a>