← The AI Hype Audit — all 646 verdicts
PARTLY
Partly true: REA is a real, free and very popular reverse-engineering tool, and mainstream assistants have been stopping these jobs partway, but it does not 'clone any app', and switching to a model that won't refuse does not make copying someone else's software legal
The claimCaption: a mainstream coding assistant 'blocked access to REA, the viral reverse engineering repo that clones any app.' OpenCode, 'a free open coding agent, enables use of any model.' Using a low-cost DeepSeek model with OpenCode 'lets you dissect apps and create working versions to learn and build your own.'
Most of the parts are real. REA, short for Reverse Engineer Anything, is an open-source project under the MIT license. GitHub's own API showed it at about 468,000 stars on November 18, 2026, with code pushed that same day. It is a connector and command-line tool that lets a coding assistant open a program and work out how a feature behaves, from an app's JavaScript down to a compiled binary. Its own documentation lists OpenCode among the assistants it supports. The refusals are real too: trade press reported this autumn that the leading commercial coding assistants began stopping reverse-engineering jobs midway, and one vendor said its limits were aimed at people recreating existing games. What the reel adds does not hold. REA analyzes software; it does not hand you a copy of it. Its README says it is for 'software you own or are authorized to examine', and that you must hold your own licenses for the commercial analysis tools it can drive. Native analysis also needs a separate tool such as Ghidra or Hopper installed. We found no evidence that the cheaper model route produces 'working versions' of real apps; the write-ups we found describe setup, not results. And a model that does not refuse changes nothing about the license on the app you are taking apart.
What holds up
- Reel opened in the logged-in browser Nov 18; full caption read; 33 seconds long.
- REA's repository queried on GitHub's API Nov 18: about 468,000 stars, about 114,000 forks, MIT license, last push the same day.
- REA's README confirms it works through an MCP server and CLI, and that OpenCode is a supported assistant.
- Trade press this autumn reported mainstream coding assistants halting reverse-engineering tasks, with one vendor confirming limits aimed at game cloning.
- OpenCode is a real open-source coding assistant that can be pointed at many models, including low-cost ones.
What doesn’t
- 'Clones any app' is not what the tool does; it explains how software behaves.
- The README limits use to software you own or are authorized to examine. The reel leaves that out.
- No example of a 'working version' is shown, and we found none we could check.
- Native binaries need a separate analysis tool installed; some of those are paid and licensed.
- Copying another company's app can breach its license and copyright whichever model you use.
- The reel's audio was not transcribed; the read is caption plus on-screen text.
The catch
The tool is real and the refusals are real. The pitch turns 'understand how it works' into 'copy it', and treats a model that says yes as if it were permission.
How to actually do it
- Use it on software you own or have written permission to examine: your own old app with no documentation, a vendor tool you license, a file format you need to read.
- Install it only from the project's official repository or its official package. Copies with similar names are circulating.
- Start with the static analysis of a JavaScript or Electron app, which needs no extra tools, before installing anything for native binaries.
- Ask the assistant to explain one feature and show the evidence it used. Check that evidence yourself before you build on it.
- If the goal is a competitor's feature, write down what it does from the outside and build your own version from that description. That is ordinary product work and needs no reverse engineering.
- Before you take apart anything you do not own, read its license or ask a lawyer. Interoperability and security research have legal room; copying does not.
A real tool with a real use: understanding software you are responsible for. For a small business that is usually an old system nobody documented. It is not a shortcut to owning someone else's product.
- Effort
- An hour to install and run a first analysis on a simple app; days for a native program
- Cost
- $0 for REA and OpenCode; model usage is billed; some analysis tools are paid
- Stack
- REA from its official source, a coding assistant that supports MCP, and Ghidra or Hopper for native code
- Confidence
- Medium
- Posted by
- a tech creator's page (about 395 likes, 6 comments, 79 shares); reel sent to Buddy Tue Nov 17, 2026
We test hype for free. We build the real thing for a living.
Thirty minutes, no pitch — and you'll leave with something useful either way.
Book a call with Todd or start with the free Business Checkup →The Verdict Weekly
Three verdicts every Friday. Free forever, unsubscribe anytime, no spam — that would be ironic.
© Schreier Group · schreiergroup.com · See a wild AI claim? Drop it here and we'll test it.