Discofork
Repository brief

NationalSecurityAgency/ghidra

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T20:09:23.055Z
1mo ago

NationalSecurityAgency/ghidra

Ghidra is NSA’s software reverse engineering framework: a large, actively maintained, cross-platform SRE toolkit for analyzing compiled code on Windows, macOS, and Linux. It supports disassembly, assembly, decompilation, graphing, scripting, many processor instruction sets and executable formats, and extension development in Java or Python. The repo is highly popular and active, with 66,342 stars, 7,311 forks, and commits as recently as 2026-03-27.

GitHub
Loading tags...
Stars66,342
Forks7,311
Default branchmaster
Last pushed2026-03-27T13:51:50Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer this fork only if its custom scripts and decompiler changes directly match your workflow. For most adopters, upstream Ghidra is the safer choice because this fork is materially stale and likely misses many recent fixes and features.

Prefer upstream unless you specifically need this tiny typo fix on top of an old snapshot. This fork adds almost no new capability and is far too stale for most adopters.

Choose this fork if you want Ghidra with targeted workflow and UI ergonomics changes, especially around keybindings, detached windows, and location references. Choose upstream if you value staying current with NSA's mainline fixes and broad compatibility, because this fork is significantly behind upstream and looks more like a convenience patchset than a full-track alternative.

Choose this fork only if you specifically want its symbolic VSA and struct-inference research code. For normal Ghidra use, upstream is the better default because this fork is extremely stale and likely misses many fixes and features.

Prefer upstream unless you explicitly need this exact older snapshot; this fork adds no documented capabilities and is far behind active Ghidra development.

Choose this fork if your work centers on PowerPC/Gekko/Broadway analysis and you value the added processor support and decompiler cleanups. Choose upstream instead if you want the broadest, freshest Ghidra baseline with less maintenance burden.

Choose this fork if your work is specifically centered on MediaTek firmware or MIPS analysis and you want the added scripts and processor support. Choose upstream if you need current Ghidra fixes, broader compatibility, or active maintenance.

Prefer upstream unless you specifically need an old, frozen Ghidra snapshot. This fork shows no added capability and is materially behind current upstream maintenance.

Prefer upstream Ghidra unless you specifically need a frozen older baseline; this fork shows no visible enhancements and is far behind current upstream maintenance.

Choose this fork if ARCompact support is the requirement; otherwise upstream Ghidra is the better default because this fork is highly specialized and substantially behind upstream.