REA Gems

A curated, auto-updated gallery of excellent reverse-engineering cases built with REA.

REA ("reverse engineer anything") connects your
coding agent to tools for inspecting native binaries, JavaScript/Electron apps,
.NET assemblies and websites — and explains how features work, with evidence.
This repo tracks the best things people have understood, rebuilt or
reconstructed with it: official case studies, community projects, blog posts
and discussions, collected automatically from across the web.

104 cases collected · 104 added in the last 30 days · last refresh: 2026-10-17 (UTC)

This repository is an unofficial community project and is not affiliated with
the REA team. All case links point to their original authors. Reverse
engineering may be restricted by local law, software licenses or terms of
service — always respect them. Content is indexed for research and educational
purposes.

Table of contents

• Official case studies
• Community projects
• Posts & discussions
• How cases are collected
• Contributing

Live gallery: sqwu.github.io/rea-gems — interactive visual gallery with tag filtering and search.

Official case studies (rea.tools)

Curated deep dives published by the REA team.

Community projects

Open-source repos, rebuilds and reimplementations made with REA.

… 17 more in [data/cases.json]](data/cases.json).

Posts & discussions

Hacker News threads, GitHub discussions and Reddit posts showing REA in action.

How cases are collected

A scheduled GitHub Actions job (update.yml)
runs daily and executes scripts/fetch_cases.py,
which searches:

Results are deduplicated by URL, scored by engagement
(stars / HN points / comments) and freshness, then merged into
data/cases.json. README is regenerated from that file —
the JSON is the source of truth.

Contributing

Found a great case (yours or someone else's)? Two ways to add it:

1. Open a PR: append an entry to data/manual.json:

   [
     {
       "url": "https://github.com/you/your-rea-project",
       "title": "What was reversed and how",
       "category": "Electron · Feature tracing",
       "description": "One or two sentences about the case.",
       "published_at": "2026-10-12"
     }
   ]
   

2. Open an issue titled Case: <what it is> with a link.

Manually curated entries are pinned above the automatic ones.

Auto-generated by scripts/fetch_cases.py — please
don't edit this README by hand. Data © respective authors; repository code
under MIT.