# Install hub-tool with Homebrew, scoop Docker Hub experimental CLI tool. Version 04.6 via Homebrew; verified 2026-07-08. ## Install ```sh sudo av install brew:hub-tool ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install hub-tool ``` Evidence: local Homebrew formula metadata ### Windows - Scoop (92%): ```sh scoop install extras/hub-tool ``` Evidence: Scoop official bucket manifest trees: bucket/hub-tool.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:hub-tool - **Package manager:** Homebrew - **Package manager page:** - **Version:** 04.6 - **Source summary:** Docker Hub experimental CLI tool - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-07-08T11:39:20+09:00 - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - hub-tool (cli) - hub-tool (alias) ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 04.6 - Package-manager updated: 2026-07-08 - Local data: ok - Upstream repository: https://github.com/docker/hub-tool - Upstream latest detected: v04.6 (current) ## Project history and usage 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. ### Project history 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. ### Adoption history 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. ### How it is used 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. ### Why package nerds care 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. ### Timeline - 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. ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - 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 ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** hub-tool - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** yes - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - 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 ## Related links - [Cloud CLI packages](https://www.automicvault.com/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family. - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Package publisher tools](https://www.automicvault.com/pkg/package-publishers/) - Belongs to a package publishing or registry command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [hub](https://www.automicvault.com/pkg/brew/hub/) - Package name indicates the same formula family. - [harbor-cli](https://www.automicvault.com/pkg/brew/harbor-cli/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers, registry. - [colima](https://www.automicvault.com/pkg/brew/colima/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers, docker. - [container-canary](https://www.automicvault.com/pkg/brew/container-canary/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers, docker. - [container-structure-test](https://www.automicvault.com/pkg/brew/container-structure-test/) - Shares av.db curated category or tags: cli, cloud-infrastructure, container-images, containers. - [dcp](https://www.automicvault.com/pkg/brew/dcp/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers, docker. - [dry](https://www.automicvault.com/pkg/brew/dry/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers, docker. - [dtop](https://www.automicvault.com/pkg/brew/dtop/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers, docker. - [mintoolkit](https://www.automicvault.com/pkg/brew/mintoolkit/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers, docker. ## Combined YAML source View the package source record on GitHub. [combined/hub-tool.yml](https://github.com/automic-vault/db/blob/main/combined/hub-tool.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph