# crane mit Homebrew, apk, pacman, zypper installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für crane in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:crane ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install crane ``` Evidenz: local Homebrew formula metadata ### Linux - apk (92%): ```sh sudo apk add crane ``` Evidenz: Alpine Linux edge package indexes: crane from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz - pacman (92%): ```sh sudo pacman -S crane ``` Evidenz: Arch Linux sync databases: crane from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz - zypper (92%): ```sh sudo zypper install crane ``` Evidenz: openSUSE Tumbleweed package metadata: crane from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst ## Paketfakten - **Paketschlüssel:** brew:crane - **Paketmanager:** Homebrew - **Version:** 0.21.8 - **Quellzusammenfassung:** Tool for interacting with remote images and registries - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-07-31T20:45:46Z - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - crane (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 0.21.8 ## Projektgeschichte und Nutzung crane is the command-line front end in Google's go-containerregistry project for working with remote container images and registries. It sits beside the Go library APIs and exposes common registry operations as shell commands. ### Projektgeschichte The go-containerregistry repository was created in 2018 as a Go library and set of CLIs for container registry work. Its README describes the library as largely based on Google's earlier Python containerregistry library and explains that crane, gcrane, and krane are tools built on top of the shared registry primitives. The crane README documents direct binary releases, Go installation, Homebrew, Arch Linux, GitHub Actions setup, and a container image form of the tool. The project published a v0.1.0 GitHub release in 2020 and was still publishing releases in 2026. ### Adoptionsgeschichte crane became common packaging material because it is useful without a Docker daemon: scripts can copy, tag, inspect, authenticate to, and move images directly against registries. Official installation instructions explicitly cover Homebrew, Arch Linux, release tarballs, Go install, and containerized usage. ### Wie es verwendet wird Package users reach for crane for registry automation: pulling and pushing images, copying between registries, tagging images in CI, listing tags, and authenticating to registries. The go-containerregistry README maps examples such as crane pull, crane push, and crane cp to library-level remote and tarball operations. ### Warum Paket-Nerds sich dafür interessieren For package maintainers, crane is a small, single-purpose registry CLI with signed release artifacts and documented SLSA provenance verification. That makes it attractive in build pipelines where installing a full container engine would be unnecessary overhead. ### Zeitleiste - 2018: google/go-containerregistry repository created. - 2020: v0.1.0 release published. - 2026: v0.21.7 release published. ### Related projects - go-containerregistry also includes gcrane, a GCR-oriented variant, and krane, a Kubernetes-workload-identity-aware drop-in replacement. The README notes that ko originally lived in the repository before moving to its own project. ### Quellen - - - - ## Sicherheitshinweise Für crane wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat. ## 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 - Unix: ~/.docker/config.json, ${DOCKER_CONFIG}/config.json, ${XDG_RUNTIME_DIR}/containers/auth.json - Windows: %USERPROFILE%\.docker\config.json ## Andere Paketmanager-Einträge - apk - crane - 0.21.8-r0: normalized package name match | Alpine Linux edge package indexes: crane from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | tool for interacting with remote images and registries | https://github.com/google/go-containerregistry/tree/main/cmd/crane - pacman - crane - 0.21.7-1: normalized package name match | Arch Linux sync databases: crane from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Interacting with remote container images and registries. | https://github.com/google/go-containerregistry - zypper - crane - 0.21.7-1.3: normalized package name match | openSUSE Tumbleweed package metadata: crane from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | CLI tool for interacting with remote images and registries | https://github.com/google/go-containerregistry ## Combined YAML source View the package source record on GitHub. [combined/crane.yml](https://github.com/mxcl/pkgdb/blob/main/combined/crane.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph