DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to make minified JavaScript readable before auditing it with Awesome REA

Unpack bundles and rename minified identifiers so shipped JavaScript can be reviewed.

Authorization notice. Awesome REA is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Reverse engineering. Deobfuscating third-party JavaScript may conflict with the site's terms or the code's license, so confirm you have the right to analyze it first.

Who it is forA security reviewer or developer who needs to read a site's shipped JavaScript bundle to check what it does.

The problemMinified and bundled JavaScript has short, meaningless names and merged modules, which makes manual review slow.

The outcomeReadable module files and clearer identifiers that make the bundle's logic easier to follow.

What you need first

  • Access to the Awesome-REA README or the linked awesomerea.org directory to choose a tool
  • A website, app or captured file that you own or have permission to analyze
  • Node.js if you plan to run the Dembrandt CLI
  • A browser or proxy tool to capture the traffic or pages you want to study

Steps

  1. Open the JavaScript tools section in the Awesome REA README and pick a tool that matches your bundle, such as webcrack for webpack or Browserify bundles, or wakaru for recognized minifier and transpiler patterns.
  2. Save the bundle you are allowed to review as a local file.
  3. Run the chosen tool on the saved file by following its project page, and keep the output in a separate folder.
  4. For leftover short names, try humanify, which suggests names with an LLM and applies them with scope-aware AST rewriting.
  5. Compare the readable output with the original file to confirm the logic is unchanged before drawing conclusions.

Prompt for your agent

Using the webcrack or wakaru entries from the Awesome-REA README, make the minified bundle at <path-to-bundle.js> readable and save the output to <output-folder>. Report the modules and any endpoints or API calls you find. Verify that the bundle's exported names still match the original file.

Caveat. The README lists these tools as options with one-line descriptions, so their exact input formats must be checked on each project page.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page