Automic VaultAutomic Vault

brew

使用 Homebrew, scoop 安装 hub-tool

查看 hub-tool 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install hub-tool

local Homebrew formula metadata

Windows

Scoop已验证 · 92%
scoop install extras/hub-tool

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

概览

软件包摘要

Docker Hub experimental CLI tool

命令和别名

  • hub-tool

历史

项目历史与用法

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.

项目历史

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.

采用历史

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.

使用方式

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.

为什么软件包爱好者会关心

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.

时间线

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

来源

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

安全态势

风险级别:绿色

narrow executable package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • narrow executable package without higher-risk signals

信号

  • metadata:no-higher-risk-signals

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 8 个平台目标。
  • 构建元数据列出 1 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

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

可执行文件

已安装的可执行文件

命令类型暴露范围备注
hub-toolcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-25
管理器版本04.6
管理器更新时间2026-07-08
本地数据OK
上游当前
检测到的最新版本v04.6

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

  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:hub-tool
版本04.6
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/hub-tool
主页https://github.com/docker/hub-tool
仓库https://github.com/docker/hub-tool
上游文档https://github.com/docker/hub-tool
许可证Apache-2.0
源码归档https://github.com/docker/hub-tool/archive/refs/tags/v04.6.tar.gz
最后更新2026-07-08T11:39:20+09:00
Pulseupdated
构建依赖go
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

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

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

Scoop95%

extras/hub-tool

scoop install extras/hub-tool
  • normalized package name match
  • 匹配方式: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

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • 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