rz-ghidra
v0.8.0 open-sourceThe section your link pointed to isn't on rz-ghidra's page any more, so we've brought you to the top.
Rizin plugin integrating the Ghidra decompiler and Sleigh Disassembler for reverse engineering without requiring Ghidra itself.
Summary
rz-ghidra is an open-source Rizin plugin that brings Ghidra's decompiler and Sleigh disassembler into Rizin's analysis workflow, free to use and built self-contained since it relies only on Ghidra's C++ decompiler code rather than a full Ghidra install. It runs as a plugin invoked from Rizin's command line, with commands to decompile a function, dump it as XML or JSON, or view it alongside offsets, which makes it a fit for reverse engineers and firmware analysts already working in Rizin rather than Ghidra's own GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands.. It covers architectures including PIC microcontrollers and TriCore, useful for embedded and automotive targets. First committed in 2019, it has drawn 36 contributors and seen 22 commits and 11 releases in the past year, the most recent 61 days ago, indicating active maintenance.
Rizin plugin integrating the Ghidra decompiler and Sleigh Disassembler for reverse engineering without requiring Ghidra itself.
How rz-ghidra helps
What does this unreadable block of disassembly actually do?
decompiles the current function into readable pseudo-C right inside the Rizin session, without switching tools
Which line of source corresponds to this specific instruction offset?
shows the decompiled function laid out beside the original offsets, so a given address can be matched to the line it produced
Can this firmware from a microcontroller or automotive chip be decompiled at all, not just disassembled?
covers architectures such as PIC microcontrollers and TriCore, so those targets get the same pseudo-C treatment as mainstream CPUs
How do I get this decompiled function's structure into another script or tool?
dumps the decompiled function as XML or JSON so its structure can be parsed outside Rizin
Which Sleigh-supported architectures is this build actually able to decompile?
lists the Sleigh languages currently loaded, showing which instruction sets are available before a function is decompiled
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for rz-ghidra, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail rz-ghidra puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
1 entry
No entries match these filters.
- April 20251
Project health
Issue, contributor and maintainer activity in rizinorg/rz-ghidra, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 5 +3 vs prior 12 months
- Maintainers 2 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 83% of issues opened, last 12 months
- Median time to close 2.5 years first maintainer reply 41 hours
- Open backlog 54 of 184 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 54
- Contributors / month 0
- Commits / month 0
- Stars 980
- bugs 33%
- other 67%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.