Inside the REA Repository (morluto/rea): Contents, Install, Releases

People searching for the rea repository land on github.com/morluto/rea — and this page answers the question that search implies: what is actually in the rea repository, and what do I install from it? Below: a directory tour of the rea repository, the exact npm package and version to pin, the release cadence measured from the public GitHub API on 2026-10-21, and how the rea repository relates to the Developer-published site at rea.tools. Everything cites either public repository data (marked [official]) or our own lab run — no rumors.

What's in the rea repository? A directory tour

The rea repository is a single monorepo. Reading its root directory listing [official] (fetched 2026-10-21), the parts that matter to a new user are:

Three things ship out of the rea repository as user-facing products: the rea CLI, an MCP server (our lab enumerated 170 MCP tools over a live JSON-RPC handshake on 2026-10-12), and the MIT-licensed source for both.

One design point matters more than any feature list, and we verified it by running the tool: REA is an orchestration layer, not a decompiler. Its deep-analysis commands (analyze / decompile) fail-closed with provider_unavailable and a precise per-engine diagnosis unless you have Ghidra, Hopper, or IDA installed and licensed. A tool that says "I cannot know" instead of guessing is rare, and it is the main reason we recommend the rea repository to beginners.

How active is the rea repository? (public numbers)

All figures below come from the public GitHub API and the npm registry, fetched 2026-10-21 [official]. They will age — treat them as a snapshot and check the live repository for current values.

Read that release cadence the practical way: fast-moving means bugs get fixed in days, but it also means the @latest npm tag can move under you mid-week. So the version we pin below — rea-agents@6.7.0, published 2026-10-18 [official] — is the one you can reproduce our lab environment with, then upgrade on your own schedule.

What to install from the rea repository

The npm package is rea-agents (the rea repository and the npm distribution are the same project; npm is just the packaged channel). We recommend pinning the current release instead of @latest:

bash — lab@realearn verified: ran 2026-10-12
$ npm install rea-agents@6.7.0
$ npx rea --version
rea@6.7.0 — Reverse engineer anything from your terminal or agent.

Our original lab run (2026-10-12, Linux, Node v22.22.0) installed the then-current release with 35 dependencies and 0 vulnerabilities reported; two binaries land on your PATH: rea and rea-agents. For the full install → configure → first-run walkthrough, see our REA setup guide — every command there was run in the same lab.

Prefer zero install? npx rea doctor fetches and runs on demand. In our lab it correctly inventoried the environment and refused with a precise list of what was missing (unsupported host OS, three absent analysis engines) — the fail-closed design visible on the very first command. Cloning the rea repository from source (git clone https://github.com/morluto/rea.git, then npm install && npm run build per the README) is fully supported under MIT when you want to audit or pin an exact commit.

Environment note from our lab: REA documents support for macOS 12+, Ubuntu 24.04+, Fedora 41+, and selected Arch-family distributions. REA never installs Python for you; the free pwntools-elf engine expects a Python with pwntools 4.15.0 + pyelftools + Unicorn (full steps in the setup guide).

Release cadence of the rea repository (October 2026)

Because "how fresh is this repo" is half of what a repository search is really asking, here is the October 2026 release timeline for the rea repository [official] (fetched 2026-10-21): 6.2.0 (Oct 9), 6.3.0 (Oct 9), 6.4.0 (Oct 11), 6.5.0 (Oct 14), 6.6.0 (Oct 18), 6.7.0 (Oct 18 — current). Meanwhile the main branch sees double-digit commits per day; the last day we sampled was dominated by native/Apple fixes (Swift pointer nullability, dylib path handling, ObjC/Swift coverage accounting, Hopper Mach-O cleanup) — a stability push that typically precedes a minor release. When 6.8.0 ships, our REA 6.7.0 changelog breakdown will be joined by a 6.8 version — that page is also the place to see what a release actually changes, line by line.

The rea repository vs rea.tools — what is the relationship?

The rea repository and rea.tools are two faces of the same project, both maintained by the developer (morluto):

realearn is neither. We are an independent, third-party tutorial site: we ran REA ourselves, recorded the outputs, and teach from those records. Where our own runs disagreed with the Developer-published docs, we say so and cite both — see the evidence index for the raw artifacts our claims rest on.

What the rea repository does NOT contain

FAQ

What is inside the rea repository?

The rea repository at github.com/morluto/rea is a monorepo: src/ holds the CLI and MCP server source, docs/ the documentation, native/ the Apple/ObjC/Swift and binary-analysis integrations, bridge/ the process bridge layer, tests/ the test suites, plus scripts/, experiments/, website/ and the licensing/third-party notice files. A directory tour with what each part does is in the main text above.

Which npm package comes from the rea repository?

rea-agents. The GitHub source and the npm distribution are the same project: rea is the CLI command, rea-agents is the package name. Our lab guidance is to pin rea-agents@6.7.0 — the release published 2026-10-18 — rather than chasing @latest on a repo that ships several releases a week.

How often does the rea repository release?

Fast. The public GitHub API shows 38 tagged releases since mid-2026, fetched 2026-10-21 — including six releases in the first eighteen days of October alone (6.2.0 through 6.7.0). Practical read: bugs get fixed in days, but pin an exact version for anything you rely on.

Is REA on GitHub free?

Yes — the rea repository is free end to end. The source is MIT-licensed, the npm package is free, and the built-in pwntools-elf engine costs nothing. The only potential cost is optional third-party engines: Ghidra is free, while Hopper and IDA are paid commercial products you would license separately — REA drives them but does not include them.

Is realearn affiliated with morluto or rea.tools?

No. realearn is independent and non-affiliated; we link to the rea repository and rea.tools as references, run everything we publish in our own lab, and mark nothing "verified" that we did not run.

Where to go next