morluto/reaPublic

Reverse engineer anything with agents, from app behavior down to native binaries.

AI summary: Universal reverse engineering client for binaries, applications, and runtime behavior using the Model Context Protocol.

Stars
471.6K
+147 today
Forks
115.1K
Watchers
1.8K
Open issues
744
Open PRs
782
Contributors
~407
Commits
8.1K
Branches
228
Views (30d)
24

TypeScriptMITCreated Apr 14, 2026Last push todayLatest release rea-agents-6.9.0+11.8K stars this week+105.8K this month

Quick answers

What is rea?
Universal reverse engineering client for binaries, applications, and runtime behavior using the Model Context Protocol.
What does rea do?
REA provides a unified interface for analyzing compiled binaries and application runtime behavior without switching contexts. It connects to various reverse engineering tools and plugins via the Model Context Protocol to extract and interpret execution traces and memory dumps. The system allows seamless navigation from high-level application features down to specific machine instructions. By integrating multiple analytical backends, it eliminates the need to manually coordinate separate decompilers, debuggers, and static analysis utilities.
Who is rea for?
Security researchers, vulnerability analysts, and reverse engineers who need to analyze compiled binaries and complex runtime environments. Users should be familiar with assembly language, debuggers, and low-level system architecture.
How do I get started with rea?
git clone https://github.com/morluto/rea
How popular is rea on GitHub?
morluto/rea has 471,593 stars and 115,141 forks on GitHub, and gained 11,811 stars in the last 7 days.
What license does rea use?
morluto/rea is released under the MIT license.

Star history

since Oct 7, 2026
0200K400KOct 2026Oct 2026Nov 2026Nov 2026
471.6K stars as of Nov 21, 2026. Measured daily since Oct 7, 2026; GitHub no longer exposes earlier star timestamps.

Update history

4 recorded
  • Nov 16, 2026New release rea-agents-6.9.0 (previously rea-agents-6.8.0).
  • Oct 31, 2026New release rea-agents-6.8.0 (previously rea-agents-6.7.0).
  • Oct 23, 2026New release rea-agents-6.7.0 (previously rea-agents-6.5.0).
  • Oct 15, 2026New release rea-agents-6.5.0 (previously rea-agents-4.1.0).

Contribution activity

commits per day, last 52 weeks
NovDecJanFebMarAprMayJunJulAugSepOctNovMonWedFri2025-11-23: 0 commits2025-11-24: 0 commits2025-11-25: 0 commits2025-11-26: 0 commits2025-11-27: 0 commits2025-11-28: 0 commits2025-11-29: 0 commits2025-11-30: 0 commits2025-12-01: 0 commits2025-12-02: 0 commits2025-12-03: 0 commits2025-12-04: 0 commits2025-12-05: 0 commits2025-12-06: 0 commits2025-12-07: 0 commits2025-12-08: 0 commits2025-12-09: 0 commits2025-12-10: 0 commits2025-12-11: 0 commits2025-12-12: 0 commits2025-12-13: 0 commits2025-12-14: 0 commits2025-12-15: 0 commits2025-12-16: 0 commits2025-12-17: 0 commits2025-12-18: 0 commits2025-12-19: 0 commits2025-12-20: 0 commits2025-12-21: 0 commits2025-12-22: 0 commits2025-12-23: 0 commits2025-12-24: 0 commits2025-12-25: 0 commits2025-12-26: 0 commits2025-12-27: 0 commits2025-12-28: 0 commits2025-12-29: 0 commits2025-12-30: 0 commits2025-12-31: 0 commits2026-01-01: 0 commits2026-01-02: 0 commits2026-01-03: 0 commits2026-01-04: 0 commits2026-01-05: 0 commits2026-01-06: 0 commits2026-01-07: 0 commits2026-01-08: 0 commits2026-01-09: 0 commits2026-01-10: 0 commits2026-01-11: 0 commits2026-01-12: 0 commits2026-01-13: 0 commits2026-01-14: 0 commits2026-01-15: 0 commits2026-01-16: 0 commits2026-01-17: 0 commits2026-01-18: 0 commits2026-01-19: 0 commits2026-01-20: 0 commits2026-01-21: 0 commits2026-01-22: 0 commits2026-01-23: 0 commits2026-01-24: 0 commits2026-01-25: 0 commits2026-01-26: 0 commits2026-01-27: 0 commits2026-01-28: 0 commits2026-01-29: 0 commits2026-01-30: 0 commits2026-01-31: 0 commits2026-02-01: 0 commits2026-02-02: 0 commits2026-02-03: 0 commits2026-02-04: 0 commits2026-02-05: 0 commits2026-02-06: 0 commits2026-02-07: 0 commits2026-02-08: 0 commits2026-02-09: 0 commits2026-02-10: 0 commits2026-02-11: 0 commits2026-02-12: 0 commits2026-02-13: 0 commits2026-02-14: 0 commits2026-02-15: 0 commits2026-02-16: 0 commits2026-02-17: 0 commits2026-02-18: 0 commits2026-02-19: 0 commits2026-02-20: 0 commits2026-02-21: 0 commits2026-02-22: 0 commits2026-02-23: 0 commits2026-02-24: 0 commits2026-02-25: 0 commits2026-02-26: 0 commits2026-02-27: 0 commits2026-02-28: 0 commits2026-03-01: 0 commits2026-03-02: 0 commits2026-03-03: 0 commits2026-03-04: 0 commits2026-03-05: 0 commits2026-03-06: 0 commits2026-03-07: 0 commits2026-03-08: 0 commits2026-03-09: 0 commits2026-03-10: 0 commits2026-03-11: 0 commits2026-03-12: 0 commits2026-03-13: 0 commits2026-03-14: 0 commits2026-03-15: 0 commits2026-03-16: 0 commits2026-03-17: 0 commits2026-03-18: 0 commits2026-03-19: 0 commits2026-03-20: 0 commits2026-03-21: 0 commits2026-03-22: 0 commits2026-03-23: 0 commits2026-03-24: 0 commits2026-03-25: 0 commits2026-03-26: 0 commits2026-03-27: 0 commits2026-03-28: 0 commits2026-03-29: 0 commits2026-03-30: 0 commits2026-03-31: 0 commits2026-04-01: 0 commits2026-04-02: 0 commits2026-04-03: 0 commits2026-04-04: 0 commits2026-04-05: 0 commits2026-04-06: 0 commits2026-04-07: 0 commits2026-04-08: 0 commits2026-04-09: 0 commits2026-04-10: 0 commits2026-04-11: 0 commits2026-04-12: 0 commits2026-04-13: 0 commits2026-04-14: 1 commit2026-04-15: 0 commits2026-04-16: 0 commits2026-04-17: 0 commits2026-04-18: 0 commits2026-04-19: 0 commits2026-04-20: 0 commits2026-04-21: 0 commits2026-04-22: 0 commits2026-04-23: 0 commits2026-04-24: 0 commits2026-04-25: 0 commits2026-04-26: 0 commits2026-04-27: 0 commits2026-04-28: 0 commits2026-04-29: 0 commits2026-04-30: 0 commits2026-05-01: 0 commits2026-05-02: 0 commits2026-05-03: 0 commits2026-05-04: 0 commits2026-05-05: 0 commits2026-05-06: 0 commits2026-05-07: 0 commits2026-05-08: 0 commits2026-05-09: 0 commits2026-05-10: 0 commits2026-05-11: 0 commits2026-05-12: 0 commits2026-05-13: 0 commits2026-05-14: 0 commits2026-05-15: 0 commits2026-05-16: 0 commits2026-05-17: 0 commits2026-05-18: 0 commits2026-05-19: 0 commits2026-05-20: 0 commits2026-05-21: 0 commits2026-05-22: 0 commits2026-05-23: 0 commits2026-05-24: 0 commits2026-05-25: 0 commits2026-05-26: 0 commits2026-05-27: 0 commits2026-05-28: 0 commits2026-05-29: 0 commits2026-05-30: 0 commits2026-05-31: 0 commits2026-06-01: 0 commits2026-06-02: 0 commits2026-06-03: 0 commits2026-06-04: 0 commits2026-06-05: 0 commits2026-06-06: 0 commits2026-06-07: 0 commits2026-06-08: 0 commits2026-06-09: 0 commits2026-06-10: 0 commits2026-06-11: 0 commits2026-06-12: 0 commits2026-06-13: 0 commits2026-06-14: 0 commits2026-06-15: 0 commits2026-06-16: 0 commits2026-06-17: 0 commits2026-06-18: 0 commits2026-06-19: 0 commits2026-06-20: 0 commits2026-06-21: 0 commits2026-06-22: 0 commits2026-06-23: 0 commits2026-06-24: 0 commits2026-06-25: 0 commits2026-06-26: 0 commits2026-06-27: 0 commits2026-06-28: 0 commits2026-06-29: 0 commits2026-06-30: 0 commits2026-07-01: 0 commits2026-07-02: 0 commits2026-07-03: 0 commits2026-07-04: 0 commits2026-07-05: 0 commits2026-07-06: 0 commits2026-07-07: 0 commits2026-07-08: 0 commits2026-07-09: 0 commits2026-07-10: 0 commits2026-07-11: 0 commits2026-07-12: 81 commits2026-07-13: 54 commits2026-07-14: 79 commits2026-07-15: 15 commits2026-07-16: 59 commits2026-07-17: 34 commits2026-07-18: 27 commits2026-07-19: 0 commits2026-07-20: 19 commits2026-07-21: 4 commits2026-07-22: 28 commits2026-07-23: 13 commits2026-07-24: 44 commits2026-07-25: 14 commits2026-07-26: 6 commits2026-07-27: 0 commits2026-07-28: 11 commits2026-07-29: 17 commits2026-07-30: 7 commits2026-07-31: 0 commits2026-08-01: 3 commits2026-08-02: 0 commits2026-08-03: 0 commits2026-08-04: 2 commits2026-08-05: 1 commit2026-08-06: 0 commits2026-08-07: 0 commits2026-08-08: 0 commits2026-08-09: 1 commit2026-08-10: 7 commits2026-08-11: 2 commits2026-08-12: 0 commits2026-08-13: 0 commits2026-08-14: 1 commit2026-08-15: 0 commits2026-08-16: 0 commits2026-08-17: 0 commits2026-08-18: 0 commits2026-08-19: 0 commits2026-08-20: 0 commits2026-08-21: 0 commits2026-08-22: 0 commits2026-08-23: 0 commits2026-08-24: 0 commits2026-08-25: 0 commits2026-08-26: 0 commits2026-08-27: 0 commits2026-08-28: 0 commits2026-08-29: 1 commit2026-08-30: 0 commits2026-08-31: 0 commits2026-09-01: 0 commits2026-09-02: 0 commits2026-09-03: 0 commits2026-09-04: 0 commits2026-09-05: 0 commits2026-09-06: 0 commits2026-09-07: 0 commits2026-09-08: 1 commit2026-09-09: 0 commits2026-09-10: 0 commits2026-09-11: 0 commits2026-09-12: 0 commits2026-09-13: 0 commits2026-09-14: 0 commits2026-09-15: 0 commits2026-09-16: 0 commits2026-09-17: 0 commits2026-09-18: 0 commits2026-09-19: 0 commits2026-09-20: 0 commits2026-09-21: 0 commits2026-09-22: 0 commits2026-09-23: 0 commits2026-09-24: 0 commits2026-09-25: 0 commits2026-09-26: 0 commits2026-09-27: 0 commits2026-09-28: 0 commits2026-09-29: 97 commits2026-09-30: 2 commits2026-10-01: 0 commits2026-10-02: 1 commit2026-10-03: 1 commit2026-10-04: 6 commits2026-10-05: 96 commits2026-10-06: 134 commits2026-10-07: 157 commits2026-10-08: 103 commits2026-10-09: 323 commits2026-10-10: 245 commits2026-10-11: 305 commits2026-10-12: 166 commits2026-10-13: 320 commits2026-10-14: 294 commits2026-10-15: 145 commits2026-10-16: 114 commits2026-10-17: 190 commits2026-10-18: 81 commits2026-10-19: 66 commits2026-10-20: 105 commits2026-10-21: 160 commits2026-10-22: 197 commits2026-10-23: 322 commits2026-10-24: 769 commits2026-10-25: 99 commits2026-10-26: 159 commits2026-10-27: 391 commits2026-10-28: 62 commits2026-10-29: 173 commits2026-10-30: 38 commits2026-10-31: 39 commits2026-11-01: 32 commits2026-11-02: 25 commits2026-11-03: 36 commits2026-11-04: 66 commits2026-11-05: 95 commits2026-11-06: 69 commits2026-11-07: 38 commits2026-11-08: 57 commits2026-11-09: 141 commits2026-11-10: 85 commits2026-11-11: 341 commits2026-11-12: 47 commits2026-11-13: 61 commits2026-11-14: 105 commits2026-11-15: 303 commits2026-11-16: 223 commits2026-11-17: 11 commits2026-11-18: 0 commits2026-11-19: 0 commits2026-11-20: 0 commits2026-11-21: 0 commits
7,627 commits in the last yearLessMore

Signals and awards

derived from tracked data
  • Landmark project

    471,593 stars

  • Very active

    7,627 commits in 52 weeks

  • Community-driven

    ~407 contributors

  • Well documented

    High community health score

  • Permissive license

    MIT

  • Continuous integration

    Automated checks passing

  • Repeat trending

    36 trending appearances

  • Top 10% tracked

    Rank 4 of 1243

What rea does

REA provides a unified interface for analyzing compiled binaries and application runtime behavior without switching contexts. It connects to various reverse engineering tools and plugins via the Model Context Protocol to extract and interpret execution traces and memory dumps. The system allows seamless navigation from high-level application features down to specific machine instructions. By integrating multiple analytical backends, it eliminates the need to manually coordinate separate decompilers, debuggers, and static analysis utilities.

Security researchers, vulnerability analysts, and reverse engineers who need to analyze compiled binaries and complex runtime environments. Users should be familiar with assembly language, debuggers, and low-level system architecture.

  • Cross-tool protocol: Integrates diverse reverse engineering tools using the Model Context Protocol.
  • Binary analysis: Provides deep inspection capabilities for compiled executables across different architectures.
  • Runtime tracing: Captures and analyzes dynamic execution behavior directly from running applications.
  • Unified interface: Merges static and dynamic analysis workflows into a single cohesive client experience.
  • Extensible backend: Supports adding new disassemblers and debuggers via standardized plugins.

Where teams use it

Vulnerability Research

Analyze compiled binaries to discover memory corruption flaws and logical vulnerabilities.

Malware Analysis

Safely inspect malicious payloads to understand their runtime behavior and network callbacks.

Protocol Reverse Engineering

Deconstruct undocumented binary protocols by tracing how the application serializes data.

Legacy Code Maintenance

Understand the inner workings of legacy systems where source code is no longer available.

Getting started: git clone https://github.com/morluto/rea

README

main branch

English · 简体中文 · 繁體中文 · 日本語 · 한국어 · Türkçe · Русский · Tiếng Việt · ไทย · Deutsch · Español · Français · Українська · Polski · Português (Brasil) · العربية · فارسی · Bahasa Indonesia · Italiano · Ελληνικά · മലയാളം · Roman Urdu · Română · Български

REA: Reverse Engineer Anything

One MCP for reverse engineering across binaries, applications, and runtime behavior.

See a feature you like. Understand how it works, down to the binary level.

npm version MCP tool catalog Node.js requirements skills.sh MIT license Discord

morluto%2Frea | Trendshift

Website · Guides · Showcases

Join the REA community on Discord

Quick start · How REA works · What you can analyze · Showcases · Build RL environments · FAQ · Documentation

npx rea-agents setup

Important

Get REA from morluto/rea, rea.tools, or the rea-agents npm package. Follow the installation and release links from these official sources. A similar repository name or copied README does not establish that a download is official.


REA launching its analysis bridge inside Hopper while inspecting a native binary



Discord
Join the Reverse Engineering Community

Discord · Q&A · Show and Tell


See 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.

REA 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.

Setup registers REA with your agent and installs matching workflow instructions. Native analysis can use an existing Hopper, Ghidra, IDA or Kuna installation; setup can optionally install Hopper with approval. Static JavaScript analysis needs no native analysis engine.

Visit the REA website for setup instructions, illustrated guides, and real case studies.

Quick start

On Linux, Ghidra, JADX, firmware tool launches and static JavaScript/Electron analysis require a procps-compatible system ps for process ownership checks. Recovery steps are in docs/getting-started/installation.md under "Linux owned-process prerequisite".

Set up your agent

With Node.js and npm installed, run:

npx rea-agents setup

Choose your agents, review the proposed changes, and approve them. Setup adds REA's MCP server and matching workflow instructions, with backups of existing configuration. Restart your agent afterward. Setup records the selected runtime and REA entry script directly. If acquired through a package runner, keep its cache entry available. Run package acquisition from a trusted directory outside the target project. Installation and recovery details are in the setup guide below.

Setup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build and other agents. See installation and setup for provider configuration, manual MCP registration, Claude Code/Codex plugins, and the Cursor Marketplace plugin.

MCP advertises compact input schemas to reduce context overhead; guidance a compact schema omits follows the tool description. The full tool set and canonical server validation are unchanged. See "Compact input schema profile" in the MCP contracts guide.

Output schemas are omitted from tools/list by default: no model API reads them, and REA validates every result itself. Set REA_MCP_OUTPUT_SCHEMA_PROFILE=compact to advertise each output schema within a 4,096-byte budget. Both settings keep canonical server-side validation and complete structured results. See "Output schemas" in the MCP contracts guide.

Ask your agent

Understand how search works in the Notes app, show me the evidence, and build a
similar feature for my project.

Replace Notes with your target app and the feature you want to understand.

Use the terminal

Inspect an extracted JavaScript/Electron app directory or ASAR:

npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json

The result includes modules, imports, Electron boundaries and their evidence. Replace the path with your target, such as "D:/apps/example" on Windows.

To install the rea command for regular use:

npm install --global rea-agents
rea --help

For native analysis, configure a provider first. See the CLI and Evidence guide for native commands, provider selection, snapshots and scripting.

Update REA

REA changes quickly, and new releases include frequent bug fixes. Keep your installation up to date.

For a CLI installed with npm install --global or bun add --global:

rea update

rea --update is an alias for this verified workflow and accepts the same global output flags. Use rea update when combining it with other command controls.

Updater commands retain at most 4 MiB of stdout and stderr combined. Oversized metadata replies are rejected after the command exits; verbose installs continue with bounded diagnostics. Human progress output respects terminal backpressure and waits for submitted writes to finish.

Bun global updates require Bun 1.2.17 or later. With an older Bun release, upgrade Bun manually before running rea update.

To refresh your agent registrations and skill, run the setup command printed by the update.

If you use npx, update your agent setup with:

npx rea-agents@latest setup

Review the setup changes and restart your agent. For one-off CLI commands, use npx rea-agents@latest followed by the command. With Bun, use bunx rea-agents@latest in place of npx rea-agents@latest.

How REA works

Your agent calls REA through MCP to inspect the target and trace relevant code. REA returns findings with their evidence. The agent uses them to ask follow-up questions, explain the behavior, or write and test an implementation. CLI commands use the same workflows.

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.

Open the full-size figure.

What you can analyze

REA requires Node.js 22.x (>=22.23.4), 24.x (>=24.22.1), or 26.12.1+, plus npm. Additional tools and host support depend on the target:

Target What REA returns Requirements and guide
Desktop installations Runtime candidates, supporting files, component markers and next probes Built-in bounded directory/header inspection; desktop applications
Native binaries Pseudocode, assembly, strings, symbols, calls and references Hopper, Ghidra, IDA or Kuna; native analysis
Offline ELF layout Sections, segments, original symbols/relocations and static mitigation candidates Caller-supplied pwntools on Linux x64; binary diagnostics
Go binaries Embedded compiler version, modules, replacements and build settings Built-in static ELF/PE/thin Mach-O inspection; no Go installation required
GPU code objects CUDA/HIP targets, selected kernel parameters and resources, retained PTX text Built-in static ELF/PE/fatbin/CUBIN/PTX inspection; GPU code objects
Model artifacts GGUF / safetensors metadata, tensor declarations and derived totals Built-in header inspection; optional full-file hash; model files
IL2CPP metadata Unity global-metadata.dat assembly images, type and method names and index ranges Built-in static decoding of versions 24, 27, 29, 31 and 39; no Unity required
Godot PCK Archive inventory and extraction, original header/directory facts and selected content identities Built-in static formats 2, 3 and 4; no Godot required
Rust binaries Embedded cargo-auditable crate names, versions, sources and dependency edges Built-in static ELF/PE/thin Mach-O inspection; Rust binaries
PE certificates Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields Built-in static PE inspection; PE certificates
PE imports Import and delay-load DLL names, ordinals, IAT RVAs and pefile import hash Built-in static PE inspection; PE imports
Windows shortcuts Shell Link target, arguments, working dir, ExtraData and Tracker droid facts Built-in static LNK inspection; Windows shortcuts
ELF notes PT_NOTE/SHT_NOTE owners, types, GNU build-id and ABI-tag fields Built-in static ELF inspection; ELF notes
Binary hardening PIE, NX, RELRO, CFG and related header flags for ELF, PE and Mach-O Built-in static header inspection; binary hardening
Apple IPS crashes .ips metadata, threads, images, registers and documented crash classes Built-in static JSON inspection; Apple IPS
Linux kernel modules .modinfo keys, __versions CRCs, this_module presence, and signature trailer Built-in static ELF inspection; kernel modules
Erlang BEAM IFF chunks, atoms, exports, imports, lambdas and the Code header Built-in static BEAM inspection; Erlang BEAM
WASM artifact Validation, sections, exact import/export WAT forms and decoded WAT Caller-supplied WABT 1.0.42; inspect_wasm_artifact
EVM bytecode Dispatch selectors, byte offsets, inferred arguments and mutability Local raw/hex carrier on Linux x64; offline EVM guide
SQLite databases Tables, columns, indexes, views, triggers and selected ordinary-table rows Local database/WAL snapshot; Node.js 24.x >=24.15 or 26+ with native SQLite limits
Recorded Linux crashes Raw notes, every recorded thread's registers/signals and optional mapping candidates Caller-supplied pwntools on Linux x64; optional GDB/pwndbg; recorded crashes
JavaScript / Electron Modules, imports, source maps, routes, IPC, native add-ons, rea audit-release-exposure Node.js and npm; Linux: procps-compatible ps; application analysis
Websites Page structure, scripts, network observations and requested screenshots A Chrome-family browser; browser analysis
Saved network captures Requests, responses, exposed payloads and source locations HAR or Fiddler Everywhere SAZ; mitmdump on Linux for native mitmproxy; capture guide
.NET assemblies Metadata, CIL instructions, declared native dependencies and build comparisons None (static only); managed-code guide
Android APKs Manifest declarations, classes, decompiled methods and references Headless JADX and a full JDK on Linux/macOS/Windows x64; Android guide
APK signatures v1/v2/v3/v3.1 signers, certificate fingerprints, key rotation and digest self-consistency None (static only); inspect_apk_signature
Android devices Devices, packages, processes, logs, dumps, screen captures, and APK/file transfers Caller-supplied adb (emulator or hardware); ADB guide
JEB projects Engine-backed project units, artifact digests and type/method pseudo-code A caller-started JEB client serving MCP, selected with REA_JEB_MCP_URL; JEB guide
Android resources Decoded manifest, string tables, locales and version facts Caller-supplied Apktool launcher; resource guide
Flutter apps Dart snapshot hash, per-ABI library digests and engine build provenance None (static APK parsing); Flutter guide
Firmware Regions, extraction results and native-analysis handoffs Binwalk / Unblob on Linux; firmware guide
Recorded packets Selected fields, repeated values, filters and decode-as rules Linux: TShark 4.x + prlimit; capture guide
Packet summaries Endpoints, DNS, TLS SNI, protocol distribution and HTTP requests Caller-supplied tshark and capinfos (Linux-verified); pcap guide
Recorded logic signals Decoder annotations, sample ranges and diagnostics Linux: sigrok-cli 0.7.2 + prlimit; signal recordings
Packages and resources File inventories, digests, plists, Apple bundle anatomy and extracted resources Artifact and JavaScript guide, Apple applications
Process behavior Terminal output, interactions, exit and filesystem observations, and run comparisons Linux/macOS with a native PTY; process capture
PyInstaller executables CArchive members, Python version, entry scripts and extracted bytecode None (static only); Python packaged applications
Deno compile binaries Virtual files, entry point, recorded options, npm snapshot length None (static only); Deno compile executables

Static JavaScript and .NET inspection read the supplied files without running the application. Runtime capture runs or interacts with the selected target using your user permissions; each runtime guide describes its effects.

For offline native-binary inspection, REA also supports caller-supplied GNU objdump and Rizin. See the reverse-engineering tools guide for provider setup, CLI commands, and Evidence limitations. REA does not install or update either provider.

Native formats and host support vary by provider. See Hopper and Ghidra setup, the IDA guide (including an optional native MCP bridge), the Kuna decompiler guide, and experimental Windows Ghidra support. Ghidra also supports 16-bit DOS analysis. For large binaries, raise the provider's startup deadline with REA_GHIDRA_STARTUP_TIMEOUT_MS or REA_HOPPER_STARTUP_TIMEOUT_MS. For provider selection, see the CLI guide. Check release availability for features added since the latest npm release.

Showcases

Illustrations of the DX-Ball sound-pan, Notion clipboard-bridge, and TH04 bullet-ring showcases

DX-Ball: reconstruct a sound-pan calculation

Follow a sound call into its position-to-pan helper, inspect the instructions, and turn incomplete pseudocode into C. The reconstruction passes 3,205 original-x86 cases and reproduces all 63 compiled function bytes.

Read the case study · Reconstruction repository

Notion: trace the Electron clipboard bridge

Find the renderer's clipboard API, follow it through preload and IPC into the main process, and inspect the rich clipboard format.

Read the case study

TH04: recover a DOS bullet-ring calculation

Inspect the original PC-98 game's 16-bit instructions, recover the fixed and aimed angle calculations, and compare the reconstructed C++ with the historical compiler output.

Read the case study · Reconstruction repository

Build RL environments with REA

Record a web app session, turn its API into tools, and export an environment an AI agent can use. Run it with AgentEnv, then add tasks and reward checks for RL training or evaluation.

Read the guide · Watch the video

If you've used REA on something interesting, we'd love to see it. Share your case in an issue or a pull request, including the target, your question, how REA helped, and what you found.

Build RL environments

Give an AI agent a local environment to practice tasks such as finding an issue or creating a folder, without running the original app. Use it for reinforcement learning (RL) or to test how well an agent completes tasks.

REA turns recorded API requests and responses into tools the agent can call. The environment uses the recorded data and supports changes only when the recording confirms their effects.

With REA set up in your agent, replace the example URL and folder tasks below with your own:

Use REA to build an RL environment from my test web app at
http://127.0.0.1:3000.
Cover listing, creating, renaming, and deleting folders. You may create and
remove test folders. Leave existing data unchanged.
Save it in a folder named my-env. Check which operations work and tell me
how to run it.
Use the command line instead

Use these commands if you already have a file containing the app’s recorded browser requests and responses. Running the result also requires AgentEnv and Docker.

rea environment-build ./session.har ./my-env --name my-env --json
agent-env run ./my-env

REA exports a runnable environment with a basic test to check that it starts and responds. Use it with your RL framework to define task goals, add reward checks, and run training.

Build an environment · Environment reference · Watch the demo on X

Desktop app environments

REA can also build an environment of a Linux desktop app, which an agent uses through screenshots, the mouse and the keyboard. From a one-line request, such as "Build me a Gnote environment where the agent adds olive oil to the shopping list note", your agent installs the app on a local build computer, writes the task, exports the environment and checks the task in a fresh computer. The machine that builds it needs Linux on amd64 or arm64, Docker and the agentenv framework version the guide pins.

Set up desktop app environments

FAQ

Which agents can use REA?

Any agent that supports local MCP servers. Setup configures the supported agents; other clients can use manual MCP registration.

Do I need a native analysis engine?

Deep native analysis uses Hopper, Ghidra, IDA or Kuna, depending on the target and operation. Static JavaScript and .NET inspection work without a native analysis engine. Setup can install Hopper after approval; Ghidra, IDA and Kuna use your existing installations. See provider setup for the options and their supported targets.

Do I need to start Hopper first?

REA starts Hopper when an operation needs it. On macOS, a first-run dialog may ask you to choose demo mode or activate your license. Complete that prompt in the same user session before your first CLI/MCP operation or unattended job. Open Hopper manually if needed. See Hopper startup and troubleshooting.

What does installing the skill from skills.sh do?

The skill supplies investigation instructions for your agent. Use npx rea-agents setup to register REA's MCP server and install the matching instructions, then restart your agent. See skill-only installation.

What code does REA return?

Native analysis returns pseudocode and assembly. JavaScript/Electron analysis recovers modules and their relationships. Your agent uses these findings to write and test an implementation; the showcases give worked examples.

Does REA upload my app?

REA analyzes targets locally. Your agent receives the tool results, and its model provider has its own data policy.

What should I do if I hit a bug?

Update first; a recent release may already fix it.

For a CLI installed with npm install --global or bun add --global:

rea update

For agent setup through npx:

npx rea-agents@latest setup

If you're using an agent, complete the setup refresh and restart it. Retry the same task. If the problem persists, open an issue with your REA version, target type, steps to reproduce and error output.

Documentation

Start with the website's worked guides. For exact options, prerequisites and result contracts:

Report vulnerabilities through SECURITY.md.

Star history

🎉 400,000 GitHub stars — thank you!

Thanks to everyone using REA, reporting bugs, requesting features, testing builds, and contributing fixes.

REA GitHub star history

Disclaimer

See DISCLAIMER.md for responsible-use guidance.

The project's position on illegal or unauthorized use covers all REA versions, distribution channels, and platforms; each copy retains its applicable licenses.

REA is for lawful research, education, interoperability, software preservation, and analysis of software you own or are authorized to examine.

Contributing

We'd love your help with REA! Open an issue to report a bug or suggest a feature, or send a pull request to improve the code or docs.

See CONTRIBUTING.md for development setup and checks, testing for verification lanes, and the architecture map for selected layers and dependency paths.

License

MIT

REA-authored code is licensed under MIT. Third-party material retains its own licenses and copyright notices; see Third-party notices for the dependency inventory, preserved license texts, and external-tool terms.

You must legally obtain and be authorized to use commercial tools, including IDA Pro / Hex-Rays decompilers, Hopper, and JEB, under their applicable licenses. REA grants no tool license, key, or activation entitlement. Trials and demos remain subject to vendor terms, including user, feature, automation, and output sharing restrictions. Cracked copies, stolen keys, unauthorized key sharing, and bypassing license restrictions are not authorized. This guidance does not amend MIT or third-party licenses.

View on GitHub

Recent activity

commits and pull requests

Releases and announcements

40 total
  1. rea-agents: v6.9.0rea-agents-6.9.0Nov 12, 2026

    ## [6.9.0](https://github.com/morluto/rea/compare/rea-agents-6.8.0...rea-agents-6.9.0) (2026-11-11) ### Highlights - Build and test desktop tasks from recorded application state, including downloaded Linux apps, reusable build computers and multiple tasks per capture. - Inspect more shipped artifacts offline: standalone application bundles, embedded firmware, NTFS acquisitions, API contracts and V8 code-cache containers. - Keep native and runtime investigations grounded in retained Evidence, with paged results, explicit coverage and recoverable resource limits. ### Changes - Analyze targets and create private runtimes on fixed local ReFS volumes as well as NTFS, preserving persistent ACL, file identity, snapshot and cleanup checks. [#10086](https://github.com/morluto/rea/pull/10086). Thanks @QianNangong. - Capture, export and witness desktop tasks inside a build computer; keep an agentenv computer available through MCP and prepare a build host from one command. [#8954](https://github.com/morluto/rea/pull/8954), [#9041](https://github.com/morluto/rea/pull/9041), [#9045](https://github.com/morluto/rea/pull/9045), [#9049](https://github.com/morluto/rea/pull/9049), [#9199](https://

  2. rea-agents: v6.8.0rea-agents-6.8.0Oct 25, 2026

    ## [6.8.0](https://github.com/morluto/rea/compare/rea-agents-6.7.0...rea-agents-6.8.0) (2026-10-25) ### Highlights - Build local agent environments from network captures, browser scenarios, or a prompt, then serve derived reads and evidence-gated writes and compare them with fresh application captures. - Inspect more shipped formats, including GPU code objects, BEAM, Python bytecode, Unity IL2CPP metadata, Godot PCK, PyInstaller, Node.js SEA, devicetree, and additional PE/ELF tables. - Keep large investigations focused with retained summaries, selected fact queries, configurable recovery limits, and row-oriented CLI exports. Complete Evidence remains available. ### ⚠ BREAKING CHANGES - **Function analysis:** `analyze_function` now defaults to a retained summary. Set `detail: "complete"` for the previous inline dossier; the CLI retains its complete default and requires `--evidence_output` when selecting a summary. [#5660](https://github.com/morluto/rea/pull/5660). Thanks @CryptoJones, @gensokyo-dev, @RishTheFish21. - **Accessibility:** Accept JSON numbers and booleans in node `value`, alongside strings and null. Update consumers that previously assumed text-only values. [cc90771

  3. rea-agents: v6.7.0rea-agents-6.7.0Oct 18, 2026

    ## [6.7.0](https://github.com/morluto/rea/compare/rea-agents-6.6.0...rea-agents-6.7.0) (2026-10-18) ### Highlights - Client configuration edits follow the duplicate-member semantics used by MCP clients. ### Changes - Includes the [6.6.0 changes and migration notes](https://github.com/morluto/rea/releases/tag/rea-agents-6.6.0). That version was tagged but was not published to npm. ### Fixes - **Client configuration:** Setup edits the last repeated JSON/JSONC member, matching the value clients actually read. Setup and uninstall refuse a removal that would reactivate a shadowed duplicate, preserving the original configuration. ([#4957](https://github.com/morluto/rea/pull/4957), [morluto/rea#4952](https://github.com/morluto/rea/issues/4952)). Thanks @kaoru0822-kitauji, @xu91102. Full contribution record: [4 commits and 1 merged PR](https://github.com/morluto/rea/blob/rea-agents-6.7.0/docs/releases/6.7.0.contributions.json). ## [6.6.0](https://github.com/morluto/rea/compare/rea-agents-6.5.0...rea-agents-6.6.0) (2026-10-18) ### Highlights - Add Kuna as a caller-supplied static-analysis provider. - Query selected JavaScript facts and multiple APK locale tables without repeating

  4. rea-agents: v6.6.0rea-agents-6.6.0Oct 18, 2026

    ## [6.6.0](https://github.com/morluto/rea/compare/rea-agents-6.5.0...rea-agents-6.6.0) (2026-10-18) ### Highlights - Add Kuna as a caller-supplied static-analysis provider. - Query selected JavaScript facts and multiple APK locale tables without repeating the underlying analysis. - Extend Ghidra analysis to Windows ARM PE targets and explicit raw m68k images. - Preserve completed Evidence, cancellation reasons and retryable cleanup across provider and CLI finalization. ### Changes - **Kuna analysis:** Use a caller-installed Kuna for procedure listings, pseudocode, assembly, call relationships, exact-address xrefs and cached string searches. Project exports retain source spans and digests; repeated requests reuse completed work. Recorded real-provider coverage uses Kuna 1.833 on Linux; Windows, PE and universal Mach-O are unsupported. See [the provider guide](docs/kuna-provider.md). ([#3832](https://github.com/morluto/rea/pull/3832), [#3854](https://github.com/morluto/rea/pull/3854), [#4071](https://github.com/morluto/rea/pull/4071), [#4095](https://github.com/morluto/rea/pull/4095)). Thanks @gensokyo-dev, @kaoru0822-kitauji, @N0zoM1z0. - **Retained JavaScript facts:** Query exa

  5. rea-agents: v6.5.0rea-agents-6.5.0Oct 14, 2026

    ## [6.5.0](https://github.com/morluto/rea/compare/rea-agents-6.4.0...rea-agents-6.5.0) (2026-10-13) Provider prerequisites and recorded verification scope are listed in [the testing guide](docs/testing.md). ### Highlights - Analyze selected JavaScript files and recover cross-bundle relationships without expanding the selected source scope. - Read compact summaries and page retained Evidence across binary, managed, Android, Dart, WASM and network workflows. - Inspect SQLite snapshots, packet and signal recordings, WebAssembly, Rust dependency metadata and Electron fuses offline. - Keep completed Evidence and partial observations available when analysis or cleanup fails. ### Changes - **JavaScript source selection:** analyze exact application paths without expanding imports into the selected scope. Unselected files retain identity and explicit unknown coverage; summary delivery remains separate from source selection. ([#1944](https://github.com/morluto/rea/pull/1944), [issue morluto/rea#1848](https://github.com/morluto/rea/issues/1848)). Thanks @kaoru0822-kitauji, @N0zoM1z0. - **Code-split recovery:** recover related bundles from multiple selected inputs, retaining per-file prov

Code frequency

additions and deletions
+1.2M-1.2MWeek of 2026-04-12: +1,282 linesWeek of 2026-04-12: -0 linesWeek of 2026-04-19: +0 linesWeek of 2026-04-19: -0 linesWeek of 2026-04-26: +0 linesWeek of 2026-04-26: -0 linesWeek of 2026-05-03: +0 linesWeek of 2026-05-03: -0 linesWeek of 2026-05-10: +0 linesWeek of 2026-05-10: -0 linesWeek of 2026-05-17: +0 linesWeek of 2026-05-17: -0 linesWeek of 2026-05-24: +0 linesWeek of 2026-05-24: -0 linesWeek of 2026-05-31: +0 linesWeek of 2026-05-31: -0 linesWeek of 2026-06-07: +0 linesWeek of 2026-06-07: -0 linesWeek of 2026-06-14: +0 linesWeek of 2026-06-14: -0 linesWeek of 2026-06-21: +0 linesWeek of 2026-06-21: -0 linesWeek of 2026-06-28: +0 linesWeek of 2026-06-28: -0 linesWeek of 2026-07-05: +0 linesWeek of 2026-07-05: -0 linesWeek of 2026-07-12: +355,662 linesWeek of 2026-07-12: -84,729 linesWeek of 2026-07-19: +97,208 linesWeek of 2026-07-19: -135,588 linesWeek of 2026-07-26: +77,371 linesWeek of 2026-07-26: -63,422 linesWeek of 2026-08-02: +6,521 linesWeek of 2026-08-02: -602 linesWeek of 2026-08-09: +47,141 linesWeek of 2026-08-09: -45,894 linesWeek of 2026-08-16: +0 linesWeek of 2026-08-16: -0 linesWeek of 2026-08-23: +428 linesWeek of 2026-08-23: -116 linesWeek of 2026-08-30: +0 linesWeek of 2026-08-30: -0 linesWeek of 2026-09-06: +2,218 linesWeek of 2026-09-06: -1,779 linesWeek of 2026-09-13: +0 linesWeek of 2026-09-13: -0 linesWeek of 2026-09-20: +0 linesWeek of 2026-09-20: -0 linesWeek of 2026-09-27: +33,271 linesWeek of 2026-09-27: -49,275 linesWeek of 2026-10-04: +445,908 linesWeek of 2026-10-04: -198,169 linesWeek of 2026-10-11: +1,216,259 linesWeek of 2026-10-11: -294,699 linesWeek of 2026-10-18: +825,678 linesWeek of 2026-10-18: -107,005 linesWeek of 2026-10-25: +519,389 linesWeek of 2026-10-25: -387,467 linesWeek of 2026-11-01: +183,342 linesWeek of 2026-11-01: -23,293 linesWeek of 2026-11-08: +437,006 linesWeek of 2026-11-08: -100,099 linesWeek of 2026-11-15: +233,600 linesWeek of 2026-11-15: -143,389 linesApr 12, 2026Nov 15, 2026
+4.5M lines added, -1.6M removed over the last year.

Commits per week

last 52 weeks
17000Week of 2025-11-23: 0 commitsWeek of 2025-11-30: 0 commitsWeek of 2025-12-07: 0 commitsWeek of 2025-12-14: 0 commitsWeek of 2025-12-21: 0 commitsWeek of 2025-12-28: 0 commitsWeek of 2026-01-04: 0 commitsWeek of 2026-01-11: 0 commitsWeek of 2026-01-18: 0 commitsWeek of 2026-01-25: 0 commitsWeek of 2026-02-01: 0 commitsWeek of 2026-02-08: 0 commitsWeek of 2026-02-15: 0 commitsWeek of 2026-02-22: 0 commitsWeek of 2026-03-01: 0 commitsWeek of 2026-03-08: 0 commitsWeek of 2026-03-15: 0 commitsWeek of 2026-03-22: 0 commitsWeek of 2026-03-29: 0 commitsWeek of 2026-04-05: 0 commitsWeek of 2026-04-12: 1 commitsWeek of 2026-04-19: 0 commitsWeek of 2026-04-26: 0 commitsWeek of 2026-05-03: 0 commitsWeek of 2026-05-10: 0 commitsWeek of 2026-05-17: 0 commitsWeek of 2026-05-24: 0 commitsWeek of 2026-05-31: 0 commitsWeek of 2026-06-07: 0 commitsWeek of 2026-06-14: 0 commitsWeek of 2026-06-21: 0 commitsWeek of 2026-06-28: 0 commitsWeek of 2026-07-05: 0 commitsWeek of 2026-07-12: 349 commitsWeek of 2026-07-19: 122 commitsWeek of 2026-07-26: 44 commitsWeek of 2026-08-02: 3 commitsWeek of 2026-08-09: 11 commitsWeek of 2026-08-16: 0 commitsWeek of 2026-08-23: 1 commitsWeek of 2026-08-30: 0 commitsWeek of 2026-09-06: 1 commitsWeek of 2026-09-13: 0 commitsWeek of 2026-09-20: 0 commitsWeek of 2026-09-27: 101 commitsWeek of 2026-10-04: 1064 commitsWeek of 2026-10-11: 1534 commitsWeek of 2026-10-18: 1700 commitsWeek of 2026-10-25: 961 commitsWeek of 2026-11-01: 361 commitsWeek of 2026-11-08: 837 commitsWeek of 2026-11-15: 537 commitsNov 23, 2025Nov 15, 2026
7.6K commits in the last 52 weeks.

When work happens

weekday and hour
SunMonTueWedThuFriSat036912151821Sun 0:00 — 50 commitsSun 1:00 — 39 commitsSun 2:00 — 47 commitsSun 3:00 — 71 commitsSun 4:00 — 36 commitsSun 5:00 — 43 commitsSun 6:00 — 27 commitsSun 7:00 — 51 commitsSun 8:00 — 58 commitsSun 9:00 — 46 commitsSun 10:00 — 48 commitsSun 11:00 — 22 commitsSun 12:00 — 15 commitsSun 13:00 — 36 commitsSun 14:00 — 15 commitsSun 15:00 — 25 commitsSun 16:00 — 25 commitsSun 17:00 — 53 commitsSun 18:00 — 53 commitsSun 19:00 — 48 commitsSun 20:00 — 42 commitsSun 21:00 — 51 commitsSun 22:00 — 23 commitsSun 23:00 — 49 commitsMon 0:00 — 35 commitsMon 1:00 — 23 commitsMon 2:00 — 40 commitsMon 3:00 — 68 commitsMon 4:00 — 49 commitsMon 5:00 — 52 commitsMon 6:00 — 57 commitsMon 7:00 — 43 commitsMon 8:00 — 51 commitsMon 9:00 — 31 commitsMon 10:00 — 31 commitsMon 11:00 — 32 commitsMon 12:00 — 15 commitsMon 13:00 — 36 commitsMon 14:00 — 66 commitsMon 15:00 — 52 commitsMon 16:00 — 32 commitsMon 17:00 — 39 commitsMon 18:00 — 32 commitsMon 19:00 — 41 commitsMon 20:00 — 31 commitsMon 21:00 — 31 commitsMon 22:00 — 35 commitsMon 23:00 — 37 commitsTue 0:00 — 36 commitsTue 1:00 — 43 commitsTue 2:00 — 52 commitsTue 3:00 — 54 commitsTue 4:00 — 31 commitsTue 5:00 — 62 commitsTue 6:00 — 43 commitsTue 7:00 — 49 commitsTue 8:00 — 63 commitsTue 9:00 — 60 commitsTue 10:00 — 51 commitsTue 11:00 — 53 commitsTue 12:00 — 76 commitsTue 13:00 — 73 commitsTue 14:00 — 39 commitsTue 15:00 — 41 commitsTue 16:00 — 62 commitsTue 17:00 — 55 commitsTue 18:00 — 46 commitsTue 19:00 — 53 commitsTue 20:00 — 48 commitsTue 21:00 — 77 commitsTue 22:00 — 60 commitsTue 23:00 — 60 commitsWed 0:00 — 67 commitsWed 1:00 — 35 commitsWed 2:00 — 22 commitsWed 3:00 — 38 commitsWed 4:00 — 30 commitsWed 5:00 — 47 commitsWed 6:00 — 59 commitsWed 7:00 — 31 commitsWed 8:00 — 40 commitsWed 9:00 — 42 commitsWed 10:00 — 32 commitsWed 11:00 — 47 commitsWed 12:00 — 54 commitsWed 13:00 — 64 commitsWed 14:00 — 30 commitsWed 15:00 — 43 commitsWed 16:00 — 60 commitsWed 17:00 — 131 commitsWed 18:00 — 62 commitsWed 19:00 — 61 commitsWed 20:00 — 36 commitsWed 21:00 — 41 commitsWed 22:00 — 31 commitsWed 23:00 — 41 commitsThu 0:00 — 43 commitsThu 1:00 — 72 commitsThu 2:00 — 31 commitsThu 3:00 — 73 commitsThu 4:00 — 49 commitsThu 5:00 — 55 commitsThu 6:00 — 27 commitsThu 7:00 — 55 commitsThu 8:00 — 50 commitsThu 9:00 — 42 commitsThu 10:00 — 31 commitsThu 11:00 — 13 commitsThu 12:00 — 12 commitsThu 13:00 — 22 commitsThu 14:00 — 27 commitsThu 15:00 — 24 commitsThu 16:00 — 29 commitsThu 17:00 — 31 commitsThu 18:00 — 27 commitsThu 19:00 — 25 commitsThu 20:00 — 34 commitsThu 21:00 — 23 commitsThu 22:00 — 25 commitsThu 23:00 — 30 commitsFri 0:00 — 52 commitsFri 1:00 — 52 commitsFri 2:00 — 66 commitsFri 3:00 — 50 commitsFri 4:00 — 37 commitsFri 5:00 — 63 commitsFri 6:00 — 47 commitsFri 7:00 — 25 commitsFri 8:00 — 33 commitsFri 9:00 — 22 commitsFri 10:00 — 16 commitsFri 11:00 — 22 commitsFri 12:00 — 18 commitsFri 13:00 — 44 commitsFri 14:00 — 50 commitsFri 15:00 — 21 commitsFri 16:00 — 32 commitsFri 17:00 — 53 commitsFri 18:00 — 73 commitsFri 19:00 — 54 commitsFri 20:00 — 30 commitsFri 21:00 — 70 commitsFri 22:00 — 27 commitsFri 23:00 — 52 commitsSat 0:00 — 84 commitsSat 1:00 — 96 commitsSat 2:00 — 229 commitsSat 3:00 — 110 commitsSat 4:00 — 156 commitsSat 5:00 — 59 commitsSat 6:00 — 43 commitsSat 7:00 — 81 commitsSat 8:00 — 68 commitsSat 9:00 — 58 commitsSat 10:00 — 40 commitsSat 11:00 — 61 commitsSat 12:00 — 33 commitsSat 13:00 — 27 commitsSat 14:00 — 40 commitsSat 15:00 — 37 commitsSat 16:00 — 33 commitsSat 17:00 — 23 commitsSat 18:00 — 25 commitsSat 19:00 — 24 commitsSat 20:00 — 26 commitsSat 21:00 — 23 commitsSat 22:00 — 24 commitsSat 23:00 — 37 commits
Commit volume by weekday and hour (UTC). Larger dots mean more commits.

Who is committing

last 52 weeks
Maintainer commits4,763 (60%)
Community commits3,211 (40%)

7,974 commits in total over the last year.

DateListRankStars gained
Nov 16, 2026monthly#3+236,618
Nov 15, 2026monthly#3+236,618
Nov 14, 2026monthly#2+271,084
Nov 13, 2026monthly#2+325,178
Nov 12, 2026monthly#1+366,818
Nov 11, 2026monthly#1+389,832
Nov 10, 2026monthly#1+413,718
Nov 9, 2026monthly#1+425,123
Nov 8, 2026monthly#1+429,845
Nov 7, 2026monthly#1+431,436
Nov 6, 2026monthly#1+430,792
Nov 5, 2026monthly#1+430,285
Nov 4, 2026monthly#1+426,427
Nov 3, 2026monthly#1+422,104
Nov 2, 2026monthly#1+422,016
  • freeCodeCamp/freeCodeCamp

    freeCodeCamp.org's open-source codebase and curriculum. Learn math, programming, and computer science for free.

    459.4K stars · TypeScript

  • openclaw/openclaw

    The AI that really does things. Any OS. Any Platform. The lobster way. 🦞

    394.9K stars · TypeScript

  • donnemartin/system-design-primer

    Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.

    378.7K stars · Python

  • obra/superpowers

    An agentic skills framework & software development methodology that works.

    322.9K stars · Shell

  • affaan-m/ECC

    The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

    307.9K stars · JavaScript

  • practical-tutorials/project-based-learning

    Curated list of project-based tutorials

    290.1K stars · Python