# Installer hub-tool avec Homebrew, scoop Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de hub-tool pour les workflows d'agents IA. ## installation ```sh sudo av install brew:hub-tool ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install hub-tool ``` Preuve: local Homebrew formula metadata ### Windows - Scoop (92%): ```sh scoop install extras/hub-tool ``` Preuve: Scoop official bucket manifest trees: bucket/hub-tool.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1 ## Faits du paquet - **Clé du paquet:** brew:hub-tool - **Gestionnaire de paquets:** Homebrew - **Version:** 04.6 - **Résumé source:** Docker Hub experimental CLI tool - **Page d'accueil:** - **Dépôt:** - **Dernière mise à jour:** 2026-07-27T14:32:26+02:00 - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - hub-tool (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 04.6 ## Historique du projet et usages Docker Hub Tool, packaged as `hub-tool`, is Docker's experimental CLI for interacting with Docker Hub from a terminal. It focuses on image information and Hub maintenance tasks such as login and tag listing. ### Historique du projet The docker/hub-tool repository was created in September 2020. Its README labels the project as a Docker experiment intended to gather user feedback and fold useful functionality into the Docker CLI. The GitHub releases show a compact 0.3 and 0.4 series from 2021 through 2024. The repository metadata marks the project as archived, which fits the README's stated experimental purpose rather than a permanent standalone CLI. ### Historique d'adoption hub-tool had enough distribution value to land in Homebrew and Scoop, but its adoption story is narrower than Docker itself. It served people who wanted Docker Hub operations from a shell while Docker evaluated which workflows belonged in the main Docker CLI. The README asks users to provide feedback in the issue tracker and says larger changes should be discussed first. That community posture makes it a feedback vehicle for Docker Hub UX rather than a broad plugin platform. ### Modes d'utilisation The README documents downloading a release binary, placing `hub-tool` on PATH, or building from source with Go modules. Users log in with a Docker Hub username, then run commands such as tag listing to inspect images, digests, status, update time, push time, pull time, and size. Credentials follow Docker's normal credential storage conventions rather than a hub-tool-specific config file; the curated credentials paths point to Docker's `config.json` locations on Unix-like systems and Windows. ### Pourquoi les passionnés de paquets s'y intéressent hub-tool is package-nerd significant as a snapshot of Docker experimenting with product functionality outside the core `docker` binary. It is the kind of short-lived official utility package that tells you how a platform vendor tested workflows before absorbing or retiring them. Its archived state also matters: package indexes may continue to know about an executable after the upstream project has served its experiment. That makes source-backed history useful for distinguishing a dead random CLI from an official Docker experiment. ### Chronologie - 2020: GitHub repository created under Docker. - 2021: v0.3.1 and v0.4.x releases published. - 2022: v0.4.5 release published. - 2024: v0.4.6 release published. - 2026: Repository metadata marks docker/hub-tool as archived. ### Related projects - Docker CLI is the intended destination for lessons from the experiment, according to the README. - Docker Hub is the service hub-tool interacts with. - Docker Desktop and Docker Engine provide the broader Docker environment expected by the README prerequisites. - Registry-oriented tools such as skopeo and crane overlap around container-image metadata, but hub-tool is specifically tied to Docker Hub. ### Sources - GitHub releases supply the 2021, 2022, and 2024 release timeline. - GitHub repository metadata supplies the creation date, description, license, popularity signal, and archived state. - Homebrew and input package-manager metadata support package-manager adoption. - The README supplies the experimental status, Docker CLI feedback goal, Docker Hub purpose, install method, login flow, tag-listing example, feedback request, and build instructions. ## Notes de sécurité narrow executable package without higher-risk signals. - **Risque Geiger:** vert / faible - narrow executable package without higher-risk signals ## 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. ## Credential files - Unix: ~/.docker/config.json - Windows: %USERPROFILE%\.docker\config.json ## Autres enregistrements de gestionnaires de paquets - Scoop - extras/hub-tool: normalized package name match | Scoop official bucket manifest trees: bucket/hub-tool.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/hub-tool.yml](https://github.com/mxcl/pkgdb/blob/main/combined/hub-tool.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph