Automic VaultAutomic Vault

brew

Install hub-tool with Homebrew, scoop

Docker Hub experimental CLI tool. Version 04.6 via Homebrew; verified 2026-07-08.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install hub-tool

local Homebrew formula metadata

Windows

Scoopverified · 92%
scoop install extras/hub-tool

Scoop official bucket manifest trees · bucket/hub-tool.json · source: api.github.com

overview

Package summary

Docker Hub experimental CLI tool

Commands and aliases

  • hub-tool

history

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 posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 8 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to 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.

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.docker/config.json
Windows
%USERPROFILE%\.docker\config.json

executables

Installed executables

CommandKindExposureNote
hub-toolcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version04.6
manager updated2026-07-08
local dataok
upstreamcurrent
latest detectedv04.6

https://github.com/docker/hub-tool

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:hub-tool
Version04.6
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/hub-tool
Homepagehttps://github.com/docker/hub-tool
Repositoryhttps://github.com/docker/hub-tool
Upstream docshttps://github.com/docker/hub-tool
LicenseApache-2.0
Source archivehttps://github.com/docker/hub-tool/archive/refs/tags/v04.6.tar.gz
Last updated2026-07-08T11:39:20+09:00
Pulseupdated
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namehub-tool
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Scoop95%

extras/hub-tool

scoop install extras/hub-tool
  • normalized package name match
  • Matched by: Hub Tool
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/hub-tool.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment