Automic VaultAutomic Vault

brew

docker-ls mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für docker-ls in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install docker-ls

local Homebrew formula metadata

Linux

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

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

Überblick

Paketzusammenfassung

Tools for browsing and manipulating docker registries

Befehle und Aliase

  • docker-ls
  • docker-rm

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

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

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 13 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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

Installierte Executables

BefehlArtSichtbarkeitHinweis
docker-lscliglobales Executable
docker-rmcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version0.5.1
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:docker-ls
Version0.5.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/docker-ls
Homepagehttps://github.com/mayflower/docker-ls
Repositoryhttps://github.com/mayflower/docker-ls
Upstream-Dokumentationhttps://github.com/mayflower/docker-ls#readme
LizenzMIT
Quellarchivhttps://github.com/mayflower/docker-ls.git
Build-Abhängigkeitengo
Bottleverfügbar (auf 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-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

docker-ls

nix profile install nixpkgs#docker-ls
  • normalized package name match
  • Abgeglichen nach: 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

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • 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