# cek mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:cek
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install cek
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:cek
- **Paketmanager:** Homebrew
- **Version:** 0.2.0
- **Quellzusammenfassung:** Explore the (overlay) filesystem and layers of OCI container images
- **Homepage:** <https://github.com/bschaatsbergen/cek>
- **Repository:** <https://github.com/bschaatsbergen/cek>
- **Zuletzt aktualisiert:** 2026-07-27T19:20:57+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- cek (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

cek, the container exploration kit, is a Go CLI for inspecting OCI container image filesystems and layers without running containers.

### Projektgeschichte

The official repository was created on December 27, 2025. The README positions cek as a command-line utility for browsing files, reading contents, inspecting layer mechanics, listing tags, exporting images, and showing image metadata.

### Adoptionsgeschichte

The project is young but has a clear package-manager path through Homebrew and Go installation. The official repository metadata showed more than 300 stars and its first listed GitHub release, v0.2.0, was published on May 16, 2026.

### Wie es verwendet wird

Users run commands such as `cek ls`, `cek cat`, `cek tags`, `cek export`, `cek tree`, and `cek inspect` against OCI image references. The tool can use local container daemon sockets through `DOCKER_HOST` or pull from remote registries.

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

cek is useful to package and container maintainers because it inspects image contents, layers, tags, and metadata without launching a container, which fits CI, registry triage, air-gapped transfer, and image-diff workflows.

### Zeitleiste

- 2025: The official GitHub repository was created.
- 2026: v0.2.0 was published on GitHub Releases.
- 2026: The official repository metadata recorded active development into July.

### Related projects

- Docker, Podman, and containerd are supported local daemon sources named in the README.
- OCI image registries are the remote source for image pulls and tag listing.

### Quellen

- <https://api.github.com/repos/bschaatsbergen/cek>
- <https://api.github.com/repos/bschaatsbergen/cek/releases>
- <https://github.com/bschaatsbergen/cek#readme>


## Sicherheitshinweise

infrastructure mutation or orchestration signal.

- **Geiger-Risiko:** orange / mittel
- infrastructure mutation or orchestration signal


## Combined YAML source

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


## Quellen

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