getAPK
Pull an installed app off your Android phone as an .apk (or an .apks bundle for split apps) — in one command.
getapk talks to your device through adb, finds where an app is installed, copies every APK file it consists of, checks each one is a real APK, and writes a single ready-to-analyse file with its SHA-256. It is the Android counterpart of getIPA.
A tool by rudranetra.com · more at rudranetra.com/tools
Why not just adb pull?
Most Play Store apps are installed as split APKs: base.apk plus one file per CPU architecture, language and screen density. Pulling only base.apk gives you something that will not install and is missing native libraries and resources. getapk pulls them all and bundles them, base first, into one .apks file that AppSleuth and bundletool-style tools understand.
Install
pipx install getapk
Requires Python 3.9+ and Android platform-tools (adb) on your PATH. Works on macOS, Linux and Windows. No Python dependencies.
On the phone: enable Developer options → USB debugging, connect, and accept the authorisation prompt. No root needed.
Use
getapk --list # user-installed apps with versions and installer
getapk --list -m bank # filter by text
getapk com.example.app -o ./apps # one app
getapk com.a.app com.b.app # several
getapk --all -o ./apps # every user-installed app
getapk --all --include-system # include preinstalled apps
getapk -s SERIAL com.example.app # pick a device when several are connected
Single-APK apps are written as <package>-<version>.apk; split apps as <package>-<version>.apks. Use --format apks to always bundle. Then:
appsleuth scan com.example.app-1.2.3.apks
Security
- Package names, device serials and every path reported by the device are validated before use; nothing is passed through a shell on your computer, and the one command run on the phone only ever receives a validated package name.
- Output file names are sanitised, so a hostile device cannot write outside the output directory.
- Each pulled file must be a valid APK (a zip containing
AndroidManifest.xml). - Files are written to a temporary directory and moved into place only when complete.
Only use getapk on devices and apps you own or are authorised to analyse. Apps may be copyrighted; extraction is for your own security analysis.
Banner and colour
On a terminal each run starts with a short logo, the version and links. It goes to stderr, so piped output and --json stay clean. Hide it with --no-banner or NO_BANNER=1; NO_COLOR=1 turns colour off and NO_ANIM=1 skips the animation.
Tests
python -m unittest discover -s tests -t .
MIT licence · © Rudranetra India Private Limited
Metadata
Release files for getapk 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| getapk-1.0.1.tar.gz | 10.3 kB | With provenance | Details for getapk-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| getapk-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for getapk-1.0.1-py3-none-any.whl |
Total release size: 20.6 kB
Release files / getapk-1.0.1.tar.gz
| Download URL | getapk-1.0.1.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
661a9dc916aa66ce834a9e07383d44407e91426177d0b650a2d3d3f51a82009b
|
|
BLAKE2b-256 checksum How to use checksums |
297b46dcbda10466bc69db9bb035bb4944a3a52f5b7065f3977991f4eba242a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / getapk-1.0.1-py3-none-any.whl
| Download URL | getapk-1.0.1-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e7c1c8e0d8bf0c92395d1d3627ea1fec76565bfa803d45a9280838460639347e
|
|
BLAKE2b-256 checksum How to use checksums |
c99d135ca42f5c13b270b65e4555d4b531bcfebcb988db1d087f5a5cf8f93136
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logSecurity for getapk 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for getapk-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.