jadx
v1.5.6 open-sourceThe section your link pointed to isn't on jadx's page any more, so we've brought you to the top.
jadx is a Dex to Java decompiler providing command line and GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands. tools for producing Java source code from Android Dex and Apk files.
jadx -d output/ --decompilation-mode simple app.apk jadx --backend-dx-d8 input.apk -d output/ wget https://repo1.maven.org/maven2/io/github/skylot/jadx/jadx/1.3.1/jadx-1.3.1.zip
Summary
jadx is an open-source decompiler, free to use under the Apache license, that turns Android Dex and APK files back into readable Java source. It runs both as a command-line tool and as a desktop GUI, decoding AndroidManifest.xml and other resources alongside the code, with a deobfuscator included. It's aimed at reverse engineers and application security researchers examining Android apps rather than at teams doing broad mobile device managementmobile device managementMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.. The GUI adds syntax-highlighted browsing, usage search, a smali debugger, and Frida snippet generation for hooking methods during dynamic analysis, putting it in the same space as other Android reverse-engineering toolchains. First committed in 2013, it remains under active development, with 179 contributors, 187 commits in the past year, and a release only 42 days ago.
jadx is a Dex to Java decompiler providing command line and GUI tools for producing Java source code from Android Dex and Apk files.
How jadx helps
Which permissions and components does this app declare, and what do they point to in the code?
decodes the AndroidManifest.xml and resources.arsc alongside the source, so declared activities, services and permissions can be traced to the methods that use them
Has obfuscation renamed the classes and fields enough to hide what this code does?
the included deobfuscator rebuilds readable names before or during decompilation, so the output isn't a wall of single-letter identifiers
Can I step through this app's logic at the bytecode level while it runs?
the smali debugger attaches to a running app and steps through smali alongside the decompiled source, for cases where the Java reconstruction alone doesn't answer the question
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.
Screenshots
From the release notes, newest first. Click one to see it full size.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 jadx, 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 jadx 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
31 entries
No entries match these filters.
- July 20263
- February 20261
- September 20251
- June 20251
- November 20241
- April 20242
- April 20231
- February 20231
- October 20222
- August 20221
- July 20221
- June 20221
- May 20222
- April 20221
- March 20221
- February 20221
- December 20211
- November 20211
- November 20201
- December 20191
- June 20191
- February 20191
- August 20181
- December 20161
- April 20151
- November 20141
Project health
Issue, contributor and maintainer activity in skylot/jadx, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 31 ±0 vs prior 12 months
- Maintainers 2 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 95% of issues opened, last 12 months
- Median time to close 2.9 days first maintainer reply 8.1 hours
- Open backlog 431 of 2,124 issues ever filed
- Issues opened / month 5 · 0 communitymaintainers
- Open backlog 431
- Contributors / month 4
- Commits / month 6
- Stars 50,516
- bugs 47%
- features 10%
- questions 2%
- other 41%
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.
Choose a badge style and copy the code →