Tool
jnitrace
Frida-based dynamic-analysis tool that traces an Android app's use of the JNI API, similar to frida-trace or strace but for the Java Native Interface. It logs the JNI calls that native libraries make through the JNIEnv and JavaVM structures, with include and exclude filters, backtraces and optional JSON output for later post-processing. The tracing engine is also published as a separate jnitrace-engine library.
- Targets
- App
- Category
- Android tools
- Relationship
- Foundation tool
- Sources reviewed
Requirements & limits
- Installed from PyPI as jnitrace (setup.py marks version 3.3.1 and Python 3) and runs on a Linux, macOS or Windows host; building from source additionally needs Node.js.
- Tracing a target needs an arm, arm64, x86 or x64 Android device running a Frida server, which the README states must provide Frida support greater than 14, with the target package already installed on the device.
- Intended for apps the analyst is authorized to inspect. MIT licensed; the repository ships the tool only. The last reviewed upstream commit dates to 2023 and targets the Frida 14-era API. As checked on 2026-10-20, that 2023-04-01 commit is still the master head and the latest release is v3.3.1 from the same day; GitHub’s last recorded push was 2023-07-18, the repository is not archived and the README does not mark it as maintained, superseded or archived.
About this entry
The description was reviewed against primary sources.
Primary sources
- README.md GitHub · chame1eon/jnitrace · Revision 5be47cb
- LICENSE GitHub · chame1eon/jnitrace · Revision 5be47cb
- setup.py GitHub · chame1eon/jnitrace · Revision 5be47cb
- https://github.com/chame1eon/jnitrace/releases/tag/v3.3.1
More in Apps
- AsmResolver · Tool
- CodemerxDecompile · Tool
- wxapkg · Tool
- React Native Decompiler · Tool
- hermes-decomp · Tool
- MEDUSA · Tool