Sign inGet started

reverse-engineer-anything

by morluto/rea · Coding & Development

Reverse-engineer compiled binaries, packages, firmware, and apps to explain features, compare versions, or guide reconstruction using shipped artifacts and runtime evidence.

Lift—not yet benchmarked
90
Trustsecurity · quality · license · upkeep
Scan Saferisk 0/100
LicenseMITserved via MCP

What it does

Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.

#reverse-engineering#binary-analysis#decompilation#firmware#electron#code-analysis

Quality judgment

completeness
9.0/10
clarity
5.5/10
trigger quality
7.5/10
examples
4.0/10
structure
7.5/10
overall
7.5/10

Exceptionally thorough coverage of targets, tool routing, recovery, and evidence discipline, with clear scope boundaries and a good trigger description; however, the prose is extremely dense and jargon-heavy, there are no worked end-to-end examples, and several passages (paging, evidence bundles, qlog rules) are hard to follow on first read, which risks misapplication despite the depth.

Files (8)

LICENSE · 1.0 KBreferences/android-applications.md · 1.9 KBreferences/connection-and-recovery.md · 8.6 KBreferences/evidence-workflows.md · 4.3 KBreferences/javascript-applications.md · 9.7 KBreferences/native-and-artifacts.md · 17.3 KBreferences/runtime-observation.md · 4.7 KBSKILL.md · 22.0 KB