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

9 sources
OK. Here are just three I spot at the moment from the first 2 or 3 pages I see, when browsing the site by the /new sorting: 1: [dead] Protect your S3 buckets from breaches (mklein.io) [0] 2: [dead] The NSA just released the preview version of Ghidra Debugger on GitHub (github.com/nationalsecurityagency) [1] 3: [dead] How to Write a Terminal Multiplexer with Rust, Async, and Actors – Part 2 (hashnode.dev) [2] I'm not saying any of those is a fantastic article, or one that particularly interests me. But I can't see anything particularly 'wrong' with them in an abusive, spammy or 'irrelevant to HN's readership' sense. And, as I said before, there are usually at least one or two such submissions, which seem to have been killed for no apparent reason, on every page when browsing by '/new'. Interesting you should say there's more complicated
Read the rest
filtering going on behind the scenes because, from this side of the wizard's curtain, it does often look arbitrary, almost like people are flagging stories for personal reasons other than completely objective ones. And, as I said previously, one of the reasons I had turned 'showdead' on. [0] https://mklein.io/2020/12/17/protect-against-s3-breaches/ [1] https://github.com/NationalSecurityAgency/ghidra/tree/debugg... [2] https://github.com/NationalSecurityAgency/ghidra/tree/debugg...
In Why Is This Person Not [Shadow] Banned?
The latest news on that debugger is from a reply to an issue [0] on June 17th, 2020: >As @ryanmkurtz mentioned work is continuing on the debugger, it is a large job and there have been many issues that have come up, not the least of which is COVID. We would really like to give you a timeline, but I don't want to promise anything and not deliver in a timely manner. Dynamic analysis and easy integration of dynamic information is important to the Ghidra community as is evidenced in the thread. >IMHO, I would not hesitate to learn/use any tool, as the knowledge gained can always be ported to another tool. Time spent learning other debuggers, such as gdb or windbg, will not be wasted as the new Ghidra based debugger will be integrated with existing debuggers or have considerable overlap with their command sets and functionality. That said, if
Read the rest
another tool fits your needs, use it. There are many great things about each RE tool and reasons to use or not use each. >Rest assured we are diligently working on the debugger and we think it will be worth the wait. We'll share information on features and release when we have solid timelines. >Thanks for using Ghidra in whatever way fits your work. Feel free to request features/improvements you see lacking and we and the community will try to address them. >We'll close the issue for now. -------------------------- Also from the What's New 9.2 release notes: >Dynamic Analysis Framework - Debugger >The debugger is very much still in progress. You may have seen some commits, in the Ghidra GitHub master branch, to get in sync with the debugger. Stay tuned for more on the Dynamic Analysis Framework soon after the 9.2 release. [0] https://github.com/NationalSecurityAgency/ghidra/issues/24#i...
In Ghidra 9.2
Patching actually works for every architecture, since it's backed by sleigh (and disassembly wouldn't even work without that). AFAIK, The problem (and the reason behind the popup) is that on some architecture, the sleigh might give ambiguous assembly instructions, so the assembler might not select the right instruction if there are multiple possibilities. But the biggest problem is, exporting a runable binary is not currently supported by Ghidra. Ghidra has a Binary Export function, but it's used as a sort of memory dump. It won't try to make a runnable program. This is by design, see issue #19[0]. It will probably work for RAW images, but that's it. Exporting a runnable binary is a highly desirable feature, though I can't find any issue tracking it. There's an open PR, #1505[1], that might provide people what they need. [0]: https://gith
Read the rest
In IDA Home is coming

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.