pkg.soopen package index

brew / rang 3171

Installer apkeep avec Homebrew, Nix, scoop

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de apkeep pour les workflows d'agents IA.

Commande d'installationNotes de sécurité

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install apkeep

local Homebrew formula metadata

Linux

Nixvérifié · 92%
nix profile install nixpkgs#apkeep

nixpkgs package indexes · pkgs/by-name/ap/apkeep/package.nix · Source: api.github.com

Windows

Scoopvérifié · 92%
scoop install extras/apkeep

Scoop official bucket manifest trees · bucket/apkeep.json · Source: api.github.com

aperçu

Résumé du paquet

Command-line tool for downloading APK files from various sources

Commandes et alias

  • apkeep

historique

Historique du projet et usages

apkeep is an EFF-maintained Rust command-line tool for downloading Android APKs from several sources, including APKPure, F-Droid, Google Play, and Huawei AppGallery. In package-manager terms it sits in the small but useful niche between Android app-store clients, archival tooling, and reproducible APK collection workflows.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

  • 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.

posture de sécurité

Niveau de risque : blue

broad file, network, media, or database tool signal.

Classificateur de risque

risque blue · confiance moyen · tool

Pourquoi

  • broad file, network, media, or database tool signal

Signaux

  • text:download

Comportement d'installation

  • Aucune métadonnée de bottle Homebrew n’a été enregistrée.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux
~/.config/apkeep/apkeep.ini

Credential files

Credential-bearing paths to review before unattended agent runs.

Linux
~/.config/apkeep/apkeep.ini

exécutables

Exécutables installés

CommandeTypeExpositionNote
apkeepexécutableexécutable indexéDécouvert depuis l'index local des exécutables.

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-08-03
version du gestionnaire1.0.0
gestionnaire mis à jour
données localesinconnu
amontnon disponible
dernière version détectéenon détecté
  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:apkeep
Version1.0.0
Gestionnaire de paquetsHomebrew
Page d'accueilhttps://github.com/EFForg/apkeep
Dépôthttps://github.com/EFForg/apkeep
Bouteillenon enregistré
Serviceaucun déclaré

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

apkeep

nix profile install nixpkgs#apkeep
  • normalized package name match
  • Correspondance par : Apkeep
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ap/apkeep/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Scoop95%

extras/apkeep

scoop install extras/apkeep
  • normalized package name match
  • Correspondance par : Apkeep
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/apkeep.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1

graphe de paquets

Les liens viennent du graphe local de relations entre paquets, des suppléments, des dépendances, des correspondances d'écosystèmes et de l'appartenance aux hubs.

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation