Included libraries, permissions, and explicit addresses recovered without opening the app.
ANDROID APK REVIEW
PLAIN REVIEWWhat's inside an APK, and what did it show while running?
This page does not produce one score. It places what the app carries in its package beside what a controlled run actually recorded.
Permission, file, Java, native, and endpoint events recorded in the selected scenario.
METHOD
How the two records fit
The first file describes the package. The second describes the recorded path. We do not join them until the APK identity matches.
- 01
Inside the package
Read manifest, permissions, SDKs, and native libraries.
- 02
While it was running
Open the real events from a controlled runtime record.
- 03
Check the same file
No comparison when the hash is different.
- 04
Read the difference
Keep seen and not recorded separate.
FILE SELECTION
Two files, one clear record
Choose both files first. They stay in this tab. The page does not execute an APK or send either file to a server.
PACKAGE RECORD
Static APK report
Records recovered without opening the app: included libraries, permissions, native files, and explicit addresses.
RUN RECORD
Runtime evidence package
Records from a controlled laboratory run: permission requests, endpoints, Java, and native events.
LIMITS
Read the result with its limits
- A static SDK namespace does not prove that the SDK was initialised or collected data.
- A runtime event does not prove application intent or cover every behaviour path.
- Network payloads, credentials, cookies, user content, and full file paths are not collected.
- This record is not a malware verdict, security guarantee, penetration test, or compliance certificate.