Rizin
v0.9.0 open-sourceThe section your link pointed to isn't on Rizin's page any more, so we've brought you to the top.
UNIX-like reverse engineering framework and command-line toolset.
/J p==Mv afvcs var0 ">0,<=9" rizin -qc '/ce' <firmware.bin> plf rz-bin -dd ./binary %$ var1=42 %$ var2=var1 + 10 rizin <binary> -c 'eco nord' $ rz-sign -aa -o /tmp/curl.pat curl-example-dbg $ rizin -e log.level=3 -qc B stm32f103-dapboot-v1.20-bluepill.bin $ rz-asm -a arm -b 32 -I 1233a0e1 rz-diff -e analysis.jmp.cref=1 bin1 bin2 rz-run --pid --pidfile /tmp/rz.pid <your_command> rz_core_cmd_new() e cfg.newshell.autocompletion=true
Summary
Rizin is an open-source reverse-engineering framework, free to use, run from the command line on Linux, Windows, macOS and several other operating systems. It lets a user disassemble and analyze binaries, debug running programs, and work as a scriptable hex editor, across architectures from x86 and ARMARMA family of RISC processor architectures designed by Arm Holdings and licensed to chip makers worldwide; tools target it to run natively on mobile, embedded, and increasingly server and desktop hardware. to less common targets like MIPSMIPSA RISC processor architecture originally developed at Stanford and commercialized by MIPS Technologies, widely used in embedded and network devices; cyber tools target it to analyze or exploit routers, cameras, and similar hardware., RISC-V and 6502, which makes it a fit for malware analysts, exploit developers and forensic examiners rather than casual users. It began as a fork of radare2 and keeps a similar command style while aiming for cleaner internals and documentation, so it sits alongside radare2 and other disassembly frameworks in the reverse-engineering space. Started in 2009, it now has over 1,100 contributors and more than 1,700 commits in the past year, with a release only 53 days old, so development is active.
UNIX-like reverse engineering framework and command-line toolset.
How Rizin helps
What architecture and instruction set is this unlabeled binary actually written in?
disassembles the code across a wide range of processors from common ones like x86 and ARM to obscure targets like 6502 and Z80, so a file with no metadata can still be read
Is there embedded key material or credentials hiding in this file?
scans the binary for patterns that match cryptographic material and reports where each match sits, without needing the analyst to know what to grep for
Which strings and byte patterns in this sample point to what it does?
runs a unified search across the file for text and byte sequences, covering multiple encodings and Unicode variants, and lists every hit with its location
Where in memory does this process behave differently from the static file on disk?
attaches to the running program and steps or runs it under control, stopping at calls or at a chosen address so state can be compared at that point
Are there regions of this file worth a closer look even without knowing what they contain?
measures entropy across the binary and flags the regions that stand out, which is often where packed or encrypted data lives
Which strings in this binary are actually reachable from other parts of the code, versus just sitting unused in the data section?
lists strings together with the locations in the binary that reference them, separating what the program actually uses from incidental text
Languages
Command line
No command matches.
| 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 Rizin, 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 Rizin 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
20 entries
No entries match these filters.
- June 20261
- February 20261
- April 20251
- December 20241
- February 20241
- October 20231
- August 20233
- March 20231
- February 20231
- September 20222
- June 20221
- January 20221
- December 20211
- November 20211
- September 20211
- April 20211
- January 20211
Project health
Issue, contributor and maintainer activity in rizinorg/rizin, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 64 +32 vs prior 12 months
- Maintainers 14 +12 joined · −4 left, last 12 months
- Bus factor 5 committers behind half the commits
- Community-filed 64% of issues opened, last 12 months
- Median time to close 402 days first maintainer reply 4.7 days
- Open backlog 449 of 1,494 issues ever filed
- Issues opened / month 0 · 13 communitymaintainers
- Open backlog 449
- Contributors / month 13
- Commits / month 51
- Stars 3,901
- bugs 18%
- features 17%
- questions 1%
- docs 2%
- other 62%
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
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.