HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
NationalSecurityAgency
ghidra
Java2019–2026
NationalSecurityAgency / ghidra

ghidra

Ghidra is a software reverse engineering (SRE) framework

76Distinct people
82Mentions
1Explicit recommenders
99.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Ghidra is a software reverse engineering (SRE) framework

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

In addition to IDA, I highly recommend looking into ghidra. It's open source, so you can peak under the hood and see how it does things.…

Godel_unicode used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 2:19:09 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year82 dated mentions

Observed mentions: 2019-03-05 23:58:31 UTC to 2026-06-24 19:50:49 UTC.

0510152019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 17 mentions; 4 submissions, 13 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 12 mentions; 5 submissions, 7 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 10 mentions; 2 submissions, 8 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 15 mentions; 5 submissions, 10 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC17413
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC918
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1257
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC1028
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC15510
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC826
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC716
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC413

What Hacker News says

10 sources
NSA has been working hard to shift some of the culture of bureaucracy. They realize that opening certain parts of their toolchain will allow then to find candidates with experience before they apply. Ghidra, an open sourced reverse engineering tool, has become a very popular disassembler. It's nice to see this shift in culture, especially from a black box agency like the NSA. https://github.com/NationalSecurityAgency/ghidra/
In NSA opens up to outsiders in fight for cybersecurity
The IDA decompiler is just generally more complete and more polished than Ghidra for the architectures it targets. One issue with Ghidra's that I keep hitting is its poor support for amd64 SIMD. There's a good example at <https://github.com/NationalSecurityAgency/ghidra/issues/249>: 0000000000000000 <intrinsics>: 0: f3 0f 1e fa endbr64 4: 0f c6 ca 1b shufps $0x1b,%xmm2,%xmm1 8: 0f 58 c1 addps %xmm1,%xmm0 b: c3 retq IDA produces great decompilation: __m128 __fastcall intrinsics(__m128 a1, __m128 a2, __m128 a3) { return _mm_add_ps(a1, _mm_shuffle_ps(a2, a3, 27)); } The Ghidra output is a mishmash of CONCAT pseudo-macros.
In IDA cybersecurity software provider Hex-Rays acquired
Not sure exactly what you mean by "best guess + fuzzing", but I have compiled code that was first decompiled by Ghidra. The problem is there are lots of invalid identifiers in the decompiled output. The worst are symbols that are used inconsistently within the same function, like a parameter which is passed in as a long and then used as a pointer to a struct or even as a function. The Ghidra community basically says you should not expect the exported decompiled code to be valid [1,2]. Which is fine, since rount-trip compile-decompile-compile is not exactly Ghidra's purpose. Maybe there's a setting to make Ghidra export asm literals when it can't figure out a valid disassembly, but I am pretty new to Ghidra so it could just be my own ignorance. [1]: https://github.com/NationalSecurityAgency/ghidra/issues/236 [2]: https://github.com/Nationa
Read the rest
In Decompiler Explorer

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.