UGT: Use the Geek ThingUGT: Use the Geek Thing

Browse projects/Developer tools/Inspect an application's code/REA

REAmorluto

See how a JavaScript app fits together

Map an app’s modules, imports and Electron boundaries, with evidence you can inspect later.

Licences & source

Give your agent an extracted JavaScript application or an ASAR archive. REA analyses the files locally and saves its findings, their evidence and the limits of the analysis. Your agent can then investigate the saved result without repeatedly analysing the app.

This setup supplies REA’s static JavaScript workflow and command line. It does not install a desktop disassembler, execute the application or establish what its code does at runtime. For native binary analysis, follow REA’s own provider setup.

You bring

  • an extracted JavaScript/Electron app directory; alternatively supply inputs/app.asarapp

You get

  • REA's complete static analysis, including evidence and limitationsapp-evidence.json
  • a compact view of the saved evidencesummary.json
  • REA's provider-free inspection commands, including views of saved evidence

Make it yours

UGT guides you through these settings.

  • maximum analysis time in seconds; defaults to 600

    Choose 10–1800. Large applications may need more time and memory; a timed-out analysis is a failure, not a partial success.

Good to know

  • Static analysis can be incomplete for obfuscated code, dynamic imports and missing files. Read the result's coverage and limitations. This CPU setup has a 4 GB memory limit.
  • Keep the full app directory, including manifests and source maps. A single JavaScript file is not the application-directory workflow. Network access and host GUI/native-analysis providers are not included.

Your files & access

Processing has no network access. The recipe can use only the files you give it. UGT downloads the software during setup.

Licences & source

REA MIT; bundled third-party notices are retained in its npm package. UGT's driver and checks are Apache-2.0.

What UGT sets up for you
How was it tested?

Run on clean x86-64 (Intel/AMD) and ARM64 machines on 10 Nov 2026. Its check passed on a known sample and rejected deliberately broken results.

This checks the job this page describes, not every feature of the original project.

Recipe files & version

The 4 recipe files

Recipe revision 03dc63620285, from 160d821ac9a0.

Developer tools

Run tools and services for the software you build.

All 3