apkeep mit Homebrew, Nix, scoop installieren

Projektlinks

• Homepage
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• apkeep

Projektgeschichte

The public GitHub repository was created under EFForg in April 2021. The project describes itself as a command-line tool for downloading APK files from various sources and publishes prebuilt binaries, crates.io installation instructions, Docker images, and Termux guidance for Android users.

The changelog shows steady expansion after the initial public releases: versioned APK downloads for APKPure and F-Droid, F-Droid index caching, mirror and repository options, Huawei AppGallery support, Google Play split APKs and additional files, and a default config file for Google credentials. Later releases updated the Google Play API path, added F-Droid index support, exposed more device options, and reached 1.0.0 in April 2026.

Adoptionsgeschichte

Official installation paths include GitHub release binaries, crates.io via Cargo, Docker images from GitHub Container Registry, and Termux on Android. The supplied package metadata also records packaging in Homebrew, Nix, and Scoop, which is typical for a CLI used by cross-platform Android tooling people.

The repository's GitHub metadata showed roughly 1.9k stars and 148 forks at the time of research, enough to indicate adoption beyond a private EFF utility without needing non-official popularity sources.

Wie es verwendet wird

The normal CLI flow is to pass an app id, optional version, download source, and output path. APKPure is the default source and does not require credentials; Google Play requires an email plus AAS token or auth token; F-Droid and Huawei AppGallery are documented as alternate download sources.

For Google Play, apkeep documents a user config file named apkeep.ini under the user config directory, usually ~/.config/apkeep/apkeep.ini on Linux. That file can hold Google email and token values so they do not have to be supplied on every command line.

Warum Paket-Nerds sich dafür interessieren

apkeep matters to package nerds because it turns mutable Android app-store distribution into scriptable artifacts: package ids in, APK or XAPK outputs out. It is useful for APK archival, comparison, reproducible testing inputs, F-Droid mirror workflows, and cases where GUI app-store clients are a poor fit.

The interesting implementation angle is that one CLI abstracts several Android distribution ecosystems while still exposing source-specific options such as device profiles, locales, split APKs, F-Droid entry points, and APKPure version listing.

Zeitleiste

• 2021: Public EFForg/apkeep repository created on GitHub.
• 2021: Changelog records F-Droid package-index caching and versioned app download support.
• 2022: Huawei AppGallery, Google Play split APKs, additional files, and a default credential config file were added.
• 2024: Google Play API v3 support and documented Google Play workflow landed.
• 2026: Version 1.0.0 added dex metadata downloads, auth-token support, and custom device properties.

Related projects

• apkeep's Google Play workflow points to EFForg/rs-google-play device profiles. Its source list overlaps with F-Droid, APKPure, Google Play, Huawei AppGallery, and Android package-analysis tools that consume APK files.

Quellen

• https://api.github.com/repos/EFForg/apkeep
• https://github.com/EFForg/apkeep#readme
• https://github.com/EFForg/apkeep/blob/master/CHANGELOG.md
• https://github.com/EFForg/apkeep/blob/master/USAGE
• https://github.com/EFForg/apkeep/blob/master/USAGE-google-play.md
• source_facts.package-manager