Introduction
Basilisk is a reverse-engineering suite: it takes a compiled program, recovers its instructions, functions, data and control flow, and turns machine code back into readable C. It does this by reimplementing Ghidra in Rust, and it reads Ghidra’s processor specifications — the SLEIGH files that describe each instruction set — unchanged.
- Parity. Everything Ghidra does, module by module, the headless core first.
- Better where it can be. Behaviour from Ghidra, structure from Rust; each deliberate difference is documented.
- Speed. Language load, disassembly and decompilation at least as fast as Ghidra’s; analysis in parallel where it is safe; an interface that never blocks.
- Trustworthy. No crashes on hostile binaries, Ghidra’s own tests ported, output checked against Ghidra.
What exists today
Section titled “What exists today”Where Basilisk stands on the road to Ghidra
Section titled “Where Basilisk stands on the road to Ghidra”| Milestone | What it brings | State |
|---|---|---|
| M0 | Foundations: p-code model, language files, SLEIGH parser, ELF parser | Done |
| M1 | SLEIGH runtime: decoding and p-code for every language | Done, one later item open |
| M2 | SLEIGH compiler | Done, diagnostics parity open |
| M3 | The decompiler, standalone | In progress |
| M4 | Program database, loaders (ELF, PE, Mach-O, raw) | Planned |
| M5 | Flow-following disassembly and auto-analysis | Planned |
| M6 | Exporters, DWARF and PDB, demanglers, the emulator, the assembler | Planned |
| M7 | The full interface on real programs | Shell and core views exist on demo data |
| M8 | Projects, versioned programs, the multi-user server | Planned |
| M9 | Python scripting and plugins | Designed |
| M10 | The debugger, Version Tracking, BSim, the remaining formats | Planned |
The roadmap has every task of every milestone.
- Build and run Basilisk from source.
- Disassemble your first bytes.
- If you know Ghidra: coming from Ghidra.