Automic VaultAutomic Vault

brew

Install docker-ls with Homebrew, Nix

Tools for browsing and manipulating docker registries. Version 0.5.1 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install docker-ls

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#docker-ls

nixpkgs package indexes · pkgs/by-name/do/docker-ls/package.nix · source: api.github.com

overview

Package summary

Tools for browsing and manipulating docker registries

Commands and aliases

  • docker-ls
  • docker-rm

history

Project history and usage

docker-ls is a small Go command-line toolkit for browsing Docker Registry HTTP API v2 registries. Its package value is less about being a general Docker replacement and more about exposing registry-level details, especially tag lists, manifests, and sha256 content digests, that are useful when maintaining private registries or cleaning up old image tags.

Project history

The project presents itself as two CLI tools, docker-ls and docker-rm, centered on Docker registry browsing and tag manipulation. The README ties it to Docker Distribution/v2 registries, token authentication, OAuth2 credentials from docker login, basic auth, and Docker credential helpers, placing it in the ecosystem of registry operations rather than container runtime management.

Adoption history

Its README documents distribution through GitHub releases, Homebrew, Gentoo, NixOS, Arch AUR, Docker images, and Go source installation. That packaging spread is the main adoption signal: docker-ls became a convenience utility for users who wanted registry inspection from package managers instead of hand-written Registry API calls.

How it is used

Typical usage is listing repositories on a registry, listing tags for a repository, inspecting a tag's manifest, dumping raw manifests, parsing manifest history, and deleting tags through docker-rm. It can reuse credentials from docker login, target a custom registry with --registry, and output YAML, JSON, or configured templates.

Why package nerds care

For package maintainers and registry operators, docker-ls sits in the practical gap between the high-level docker CLI and the lower-level Registry API. It is notable because it packages registry inventory, manifest inspection, digest lookup, and deletion workflows into small executables that can be installed beside Docker.

Timeline

  • Docker Registry v2 era: The project targets only v2 registries and the Docker Distribution API.
  • Package-manager adoption: The README documents Homebrew, Gentoo, NixOS, and Arch AUR installation paths.
  • Credential integration: The tool documents reuse of Docker credential stores and helpers for authenticated registries.

Related projects

  • Related projects include Docker Distribution, Docker Hub, Docker credential helpers, the Docker CLI, and registry-cleanup scripts that operate directly against the Registry HTTP API.

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

Configuration files

Config paths the tool may read or write during local use.

Unix
~/.docker-ls.[yaml|json|toml|...]

executables

Installed executables

CommandKindExposureNote
docker-lscliglobal executable
docker-rmcliglobal 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 version0.5.1
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/mayflower/docker-ls

install metadata

Package metadata

Package keybrew:docker-ls
Version0.5.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/docker-ls
Homepagehttps://github.com/mayflower/docker-ls
Repositoryhttps://github.com/mayflower/docker-ls
Upstream docshttps://github.com/mayflower/docker-ls#readme
LicenseMIT
Source archivehttps://github.com/mayflower/docker-ls.git
Build dependenciesgo
Bottleavailable (on arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namedocker-ls
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.

Nix95%

docker-ls

nix profile install nixpkgs#docker-ls
  • normalized package name match
  • Matched by: Docker Ls
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/do/docker-ls/package.nix from https://api.github.com/repos/NixOS/nixpkgs/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