Where to Find the Source Code for Decompiler Explorer

Updated

Decompiler Explorer (dogbolt.org) is open source, and the project page links directly to its GitHub repository with an invitation to fork it. If you want to read the implementation, run your own instance, or contribute changes, GitHub is the place to start — the site itself only exposes the link, not the code.

What the site tells you

The Decompiler Explorer page ends with a short, explicit statement: the project is open source, and you can fork it on GitHub. That is the only source-code pointer the page provides. There is no separate "download" section, no tarball, and no self-hosted mirror mentioned in the page content.

How to get to the source

  1. Open dogbolt.org.
  2. Scroll to the bottom of the page.
  3. Follow the GitHub link in the "Decompiler Explorer is open source!" line.
  4. On GitHub, use Fork to create your own copy, or clone the repository if you only want to read and build locally.

Expected result: you land on the project's repository, where the full source, commit history, and issue tracker live. Because the page only says "fork it on GitHub" without naming the exact repository path, treat the link on the page as the authoritative entry point rather than guessing a URL.

What you can do once you have it

  • Read the implementation to see how the front end submits a binary and how it collects output from each decompiler.
  • Fork and modify — the page explicitly frames forking as the intended path, which suits experimenting with your own build.
  • Track updates — GitHub is where new decompiler integrations and fixes would appear, since the site content itself is static.

Practical notes before you start

  • The upload limit stated on the page is 2MB per file, which is a useful constraint to keep in mind if you are testing your own instance with the same sample set.
  • The page lists a set of built-in samples (for example, a CTF challenge on x86 Linux, Hello World on Arm Linux, and several "Megatest" binaries for arm64 FreeBSD, arm64 macOS, and x86 Windows). These are handy for verifying that a local build behaves like the hosted one.
  • The decompilers referenced on the page include angr, BinaryNinja, Boomerang, dewolf, Ghidra, Hex-Rays, Kuna, RecStudio, Reko, Relyze, RetDec, rev.ng, and Snowman. If you plan to contribute, expect the code to deal with wiring several independent tools together rather than a single decompiler.

If the GitHub link is not enough

The page does not document build steps, dependencies, or a contribution guide. Those details, if they exist, would live in the repository itself — check its README and issue tracker first. If you cannot find the link on the page, reload dogbolt.org and look at the footer text, since that is the only place the source reference appears.