# Install crane with Homebrew, apk, pacman, zypper Tool for interacting with remote images and registries. Version 0.21.7 via Homebrew; verified 2026-06-18. ## Install ```sh sudo av install brew:crane ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install crane ``` Evidence: local Homebrew formula metadata ### Linux - apk (92%): ```sh sudo apk add crane ``` Evidence: 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 ``` Evidence: 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 ``` Evidence: openSUSE Tumbleweed package metadata: crane from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst ## Package facts - **Package key:** brew:crane - **Package manager:** Homebrew - **Package manager page:** - **Version:** 0.21.7 - **Source summary:** Tool for interacting with remote images and registries - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-06-18T00:54:03Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - crane (cli) - crane (alias) ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 0.21.7 - Package-manager updated: 2026-06-18 - Local data: ok - Upstream repository: https://github.com/google/go-containerregistry - Upstream latest detected: v0.21.7 (current) ## Project history and usage 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. ### Project history 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. ### Adoption history 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. ### How it is used 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. ### Why package nerds care 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. ### Timeline - 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. ### Sources - - - - ## Security Notes No matching local secret-handling manifest was found for crane. Nucleus package metadata is still published here so future coverage has a stable package URL. ## 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 ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** crane - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - apk - crane - 0.21.6-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.6-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.3-1.2: normalized package name match | openSUSE Tumbleweed package metadata: crane from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst | CLI tool for interacting with remote images and registries | https://github.com/google/go-containerregistry ## Related links - [Cloud CLI packages](https://www.automicvault.com/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family. - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [ko](https://www.automicvault.com/pkg/brew/ko/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers, go, oci-images. - [harbor-cli](https://www.automicvault.com/pkg/brew/harbor-cli/) - Shares av.db curated category or tags: cli, cloud-infrastructure, container-registry, containers, go. - [amazon-ecs-cli](https://www.automicvault.com/pkg/brew/amazon-ecs-cli/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers. - [ansible-builder](https://www.automicvault.com/pkg/brew/ansible-builder/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers. - [colima](https://www.automicvault.com/pkg/brew/colima/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers. - [container](https://www.automicvault.com/pkg/brew/container/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers. - [container-canary](https://www.automicvault.com/pkg/brew/container-canary/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers. - [container-compose](https://www.automicvault.com/pkg/brew/container-compose/) - Shares av.db curated category or tags: cli, cloud-infrastructure, containers. - [skopeo](https://www.automicvault.com/pkg/brew/skopeo/) - Local package facts share a topical domain. Shared terms: cli, cloud, cloud-infrastructure, containers, images. - [container-structure-test](https://www.automicvault.com/pkg/brew/container-structure-test/) - Local package facts share a topical domain. Shared terms: cli, cloud, cloud-infrastructure, container, containers. ## Combined YAML source View the package source record on GitHub. [combined/crane.yml](https://github.com/automic-vault/db/blob/main/combined/crane.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph