jadx

Dex to Java decompiler

Runssource: GitHubJavaApache-2.0commit aebeed5ecbc9

Java, Apache-2.0 licensed. The project labels itself: android, decompiler, dex and java.

jadx runs. An Argusic agent installed it in 10 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The jadx project builds from source via Gradle with JDK 17, the CLI tool decompiles .class files to readable Java source code, and the full test suite (1138 tests) passes with zero failures or errors.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
50,761
forks
0
open issues
0
watchers
0
created
-
last push
-

Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
10 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
`./gradlew dist` exited 0, `jadx --version` printed 'dev', `jadx -d /tmp/jadx-out /tmp/classes/Hello.class` decompiled Hello.class to valid Java source, `./gradlew test` exited 0 with 1138 tests passed and 0 failures
Model tokens used
77,340
Exact commit tested
aebeed5ecbc9
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

/bin/sh -lc 'echo "Install & build time check:" && date -u +%s' in /work/repo
 succeeded in 0ms:
Install & build time check:
1791357905
exec
/bin/sh -lc 'date -u +%s' in /work/repo
 succeeded in 0ms:
1791357911
Everything is working. Let me compile the final report.
tokens used
77,340
Everything is working. Let me compile the final report.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Took 10 minutes to install, slower than the median of the 16 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 17 android projects Argusic has installed and timed, jadx was the 12th fastest to reach a running state, and 13 of 17 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 10 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

androiddecompilerdexjava

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/jadx.svg)](https://argusic.com/subject/jadx)

Questions

Does jadx run?
Yes. jadx runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test jadx?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit aebeed5ecbc9. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test jadx?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does jadx take to install?
10 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does jadx need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing jadx?
Nothing did, in the recorded run: zero errors between clone and running.
How does jadx compare with the alternatives?
Of the 17 android projects Argusic has installed and timed, jadx was the 12th fastest to reach a running state, and 13 of 17 reached one at all.
Where is the evidence for jadx?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion