# container-structure-test mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für container-structure-test in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:container-structure-test
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install container-structure-test
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#container-structure-test
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/co/container-structure-test/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:container-structure-test
- **Paketmanager:** Homebrew
- **Version:** 1.22.1
- **Quellzusammenfassung:** Validate the structure of your container images
- **Homepage:** <https://github.com/GoogleContainerTools/container-structure-test>
- **Repository:** <https://github.com/GoogleContainerTools/container-structure-test>
- **Zuletzt aktualisiert:** 2026-07-27T22:04:04+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- container-structure-test (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 1.22.1
## Projektgeschichte und Nutzung

Container Structure Tests is a GoogleContainerTools project for validating container image contents, command behavior, filesystem state, and metadata. It became a common package-manager entry because it is a standalone binary aimed at CI checks for built images.

### Projektgeschichte

The project released v0.1.0 in October 2017 and v1.0.0 in March 2018. Its README now describes the project as not officially supported by Google and in maintenance mode, while still accepting contributions.

### Adoptionsgeschichte

Official documentation emphasizes local binary use, Docker-image use, and Google Cloud Builder use. It also documents Homebrew installation for macOS, which helped make the CLI easy to install outside a larger Google Cloud SDK.

### Wie es verwendet wird

Users provide YAML or JSON test files to `container-structure-test test --image ... --config ...`. The test types cover command output, file existence, file contents, image metadata, and license checks, which are the concerns image publishers usually want to verify before release.

### Warum Paket-Nerds sich dafür interessieren

The package matters because it made container image assertions portable: the test spec can live beside a Dockerfile, and CI can fail the image artifact rather than only failing application unit tests. Its explicit schema versioning and single-purpose binary made it attractive to packaging and release pipelines.

### Zeitleiste

- 2017: v0.1.0 release published.
- 2018: v1.0.0 release published.
- 2025: v1.22.1 release published while the README described the project as in maintenance mode.

### Related projects

- The README references Docker, Google Cloud Builder, and container image metadata rather than a specific runtime integration.

### Quellen

- <https://github.com/GoogleContainerTools/container-structure-test#readme>
- <https://github.com/GoogleContainerTools/container-structure-test/releases/tag/v0.1.0>
- <https://github.com/GoogleContainerTools/container-structure-test/releases/tag/v1.0.0>
- <https://github.com/GoogleContainerTools/container-structure-test/releases/tag/v1.22.1>


## Sicherheitshinweise

broad file, network, media, or database tool signal. infrastructure mutation or orchestration signal.

- **Geiger-Risiko:** orange / mittel
- broad file, network, media, or database tool signal
- infrastructure mutation or orchestration signal

## Andere Paketmanager-Einträge

- Nix - container-structure-test: normalized package name match | nixpkgs package indexes: pkgs/by-name/co/container-structure-test/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/container-structure-test.yml](https://github.com/mxcl/pkgdb/blob/main/combined/container-structure-test.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph