English · 简体中文 · 繁體中文 · 日本語 · 한국어 · Español · Français · Deutsch · Português (Brasil) · Русский · العربية · हिन्दी
Understand software with REA. What will you build?
From legacy game ports to a small color picker, explore public projects using Reverse Engineer Anything. See what was built, how REA contributed, and what remains unverified.
Explore and star the collection on GitHub · Search software, purpose or keywords · Submit a case
38 public cases — 5 official showcases and 33 community projects or author experiments. Updated: 2026-10-26. Each case retains its own source-review date.
Sources reviewed; author tests not independently rerun.
CHANGELOG · Localization (English)
Snapshot: 2026-10-26. Source-reviewed catalog projects with at least 100 GitHub Stars, sorted by stars. Stars indicate attention, not independent reproduction or production readiness. Snapshot sources.
| Project / demo | The question | Primary source |
|---|---|---|
| DX-Ball: reconstructing stereo sound panning | How does an on-screen position become a sound-pan value? | Primary source |
| Notion: tracing the Electron rich-text clipboard bridge | How does a web editor write rich text through the desktop clipboard? | Primary source |
| TH04: recovering PC-98 bullet-ring angles | How are bullets evenly distributed around a ring and aimed toward the player? | Primary source |
| Aegis: finding the Android TOTP algorithm | How is a six-digit login code calculated every 30 seconds? | Primary source |
| DownUnderCTF: recovering flag-checking equations | How can input validation be recovered without symbols or source code? | Primary source |
| Project / demo | The question | Primary source |
|---|---|---|
| Desktop Games: porting a desktop toy to macOS and the browser | How can the Peter interpreter, program tree, interactions and assets be understood and ported? | Primary source |
| Ski or Die: rebuilding Snowball War in Rust | How can throwing, collision, spawning and scoring rules be recovered from a DOS game? | Primary source |
| OpenBattlefield2: function-level Evidence for a Battlefield 2 client | How can crosshair, HUD and binary-behavior research inform a traceable engine implementation? | Primary source |
| GunZRs: identifying a packing boundary before rebuilding from game data | How can reconstruction continue when a packed executable prevents static recovery of game logic? | Primary source |
| Co-op Anything: investigating campaign multiplayer entry points | How can a campaign retain its scripts and sides while letting a second player join? | Primary source |
| Open Scrantic: rebuilding the Johnny Castaway screensaver engine in Rust | How can a 16-bit screensaver’s script interpreter, story schedule and random behavior run on modern systems? | Primary source |
| Project / demo | The question | Primary source |
|---|---|---|
| Sketch (formerly paper-rs): a Paper-inspired Rust infinite canvas | How can canvas, layout and editor interactions inform an independent design tool? | Primary source |
| rec-rs: an OBS-inspired native macOS recorder | How can a focused screen, camera and audio recorder be built? | Primary source |
| terminal-rs: a market terminal informed by TradingView interactions | How can chart-interaction research inform an independent Rust market interface? | Primary source |
| Wispr Flow: a speech-input teardown and a small local prototype | How are recording, transcription, context and pasting connected? | Primary source |
| hexgrab: investigating the PowerToys color picker | How do global hotkeys, pixel sampling and the clipboard work together? | Primary source |
| AdamTerm: investigating Ghostty’s shell and building a terminal | How are the terminal core, native windows, menus and services divided? | Primary source |
| Ledger Reborn: a local ledger informed by QuickBooks research | How can desktop accounting workflows inform an independent local app? | Primary source |
| DiskLens: checking disk-scanning and treemap algorithms in a released binary | How can disk scanning, treemaps and duplicate detection be checked before building a new interface? | Primary source |
| Hyper3D: from captured web bundles to an independent 3D prototype | How can interface and API observations inform a prototype that exports 3D models? | Primary source |
| Open Claude UI: documenting desktop interactions and publishing reusable UI components | How can input composition, scrolling and desktop interaction rules inform reusable interface components? | Primary source |
| Project / demo | The question | Primary source |
|---|---|---|
| VSL-DSP: applying vendor-library findings to audio DSP tools | How does the vendor controller discover devices, register parameters and represent gain? | Primary source |
| Virtual Desktop Streamer: a Linux port through a replacement platform layer | How can capture, encoding, audio and input move to Linux while retaining the protocol library? | Primary source |
| Pixel Watch: an eSIM handoff helper informed by companion-APK analysis | How can a separate helper find and open the companion app’s existing watch-eSIM download flow? | Primary source |
| PicoPrint: connecting a mobile thermal printer to Windows printing | When a driver connects but does not print, how can handshake differences be found? | Primary source |
| V5VPN: protocol research for a scoped portal and tunnel client | How can authentication, resource discovery and connection research inform a scoped independent client? | Primary source |
| Project / demo | The question | Primary source |
|---|---|---|
| OpenBSD netcat: static analysis of a shipped ELF | Which network, proxy and security-related implementations are in the shipped netcat binary? | Primary source |
| REA on REA: investigating the tool and testing predictions | How does REA choose a native-analysis provider and detect an unavailable provider? | Primary source |
| rea-groundtruth: checking analysis blind spots against known source | Does a report of zero IPC calls or windows reflect the app or an analysis gap? | Primary source |
| rea-lab: measuring REA’s contribution to Windows reverse engineering | How does adding REA affect an agent’s success rate, time and cost? | Primary source |
| bzip2: checking stripped-binary findings against a symbolized build | How can a function be found from an output string and its call relationships checked? | Primary source |
| A local 27B model: a smaller MCP tool list enables function analysis | How can REA tool descriptions and analysis fit into a local model’s 32K context? | Primary source |
| Open-source REA Lab: pinning an npm artifact and analyzing its entry slice | How can a release artifact be identified before answering a bounded entry-file question? | Primary source |
| Project / demo | The question | Primary source |
|---|---|---|
| rea-playbook: turning Electron Evidence into a report and reconstruction | How can large Evidence JSON become readable facts and a checked reconstruction? | Primary source |
| ReaFuse: combining two libraries after investigating their behavior | How can two projects become behavior specifications and then a new combined tool? | Primary source |
| REA in Spanish: reconstructing an author-owned key validator | How can a small stripped program’s acceptance rule be reconstructed and checked against the original? | Primary source |
| Project / demo | The question | Primary source |
|---|---|---|
| sparkDash: integrating REA analysis into a multi-device dashboard | How can a web interface submit long-running remote REA jobs and load large results on demand? | Primary source |
| REA Safe Agent: brokering static analysis between two contained processes | How can an agent query REA while access to inputs, host tools and model requests remains bounded? | Primary source |
A public primary source must explicitly show REA use, a concrete question, a process and output. Analysis, independent implementation and historical work are attributed separately. Failed experiments, evaluations and implemented REA integrations are welcome. Tool introductions, mirrors and unimplemented plans are excluded.
Contributing · REA FAQ (English) · Source records · Open case data
For installation and version requirements, see the REA upstream project.
An independent community collection curated by Sanbu. Not affiliated with the REA upstream project.
Independent editorial summary. Credit belongs to the original authors. Target software, installers and complete decompiler output are not redistributed here. MIT.