Harbor CLI

Why it's ranked here

Its breadth makes it credible as a daily operations tool, not merely a thin login wrapper. Multiple credential contexts, structured output, shell completion, configuration export and apply, log following, and broad installation choices suit both interactive work and pipelines. The remaining WebUI gaps keep the verdict mixed rather than unconditional.

What's good

Credential contexts let operators switch among Harbor instances or accounts without rewriting configuration manually. Explicit configuration precedence supports predictable local and pipeline behavior. Password input from standard input avoids exposing secrets in command arguments. Health, information, quotas, audit logs, LDAP, and system settings extend coverage beyond basic artifact operations.

Tradeoffs

The stated WebUI parity goal remains incomplete. Vulnerability dashboards, distribution, garbage collection, and job service dashboards are listed as missing. Harbor versions before 2.13 may lose functionality or behave unexpectedly, while releases before 2.0 are unsupported. Container use also requires mounting configuration and supplying a base64-encoded encryption key.

How to use it well

It best fits Harbor operators who repeat registry administration locally or inside deployment pipelines. Use structured output for scripts, named credential contexts for separate environments, and configuration export and apply for controlled settings changes. Keep the WebUI or another operational tool available for vulnerability dashboards, garbage collection, distribution, and job service dashboards.

Observed

License

Apache License 2.0

Primary language

Go

Interface

Command-line interface

Install surfaces

Container image, Homebrew, APT, Debian, RPM, Alpine, release artifacts, and source builds

Platform support

Linux, macOS, and Windows

Output formats

Table output with documented JSON, YAML, and CSV support