# cram mit Homebrew, MacPorts, apt installieren

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

## Installation

```sh
sudo av install brew:cram
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install cram
```

  Evidenz: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install cram
```

  Evidenz: MacPorts ports tree: devel/cram/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- Debian apt (92%):

```sh
sudo apt install python3-cram
```

  Evidenz: Debian stable package indexes: python3-cram from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

## Paketfakten

- **Paketschlüssel:** brew:cram
- **Paketmanager:** Homebrew
- **Version:** 0.7
- **Quellzusammenfassung:** Functional testing framework for command-line applications
- **Homepage:** <https://bitheap.org/cram>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- cram (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

Cram is a functional testing framework for command-line applications, built around test files that look like annotated interactive shell sessions.

### Projektgeschichte

Cram's official site describes tests as snippets of interactive shell sessions: commands are run, and their actual output is compared with expected output stored in `.t` files.

### Adoptionsgeschichte

The project's NEWS file shows a compact release history from 0.1 in 2010 through 0.7 in 2016. Over that period it gained interactive update support, regex and glob matching, temporary-directory isolation, Python 3 support, `.cramrc`, shell selection, and xUnit XML output.

### Wie es verwendet wird

Developers use Cram for black-box CLI tests where shell commands and expected output are easier to review than imperative test code. It prints unified diffs for failures, can write `.err` files, and can interactively merge observed output back into tests.

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

Cram has lasting package-manager appeal because it tests command-line behavior at the packaging boundary. A formula or distro maintainer can exercise installed commands exactly as users run them, without importing the application as a library.

### Zeitleiste

- 2010: Version 0.1 was released.
- 2010: Versions 0.3 and 0.4 added environment isolation, interactive updates, regex and glob matching.
- 2013: Version 0.6 added `.cramrc`, shell selection, and Arch Linux package metadata.
- 2016: Version 0.7 added debug mode, shell options, and xUnit XML output.

### Related projects

- Cram is conceptually close to shell transcript testing and Mercurial-style `.t` tests, but is distributed as its own Python command-line test runner.

### Quellen

- <https://bitheap.org/cram>
- <https://raw.githubusercontent.com/aiiie/cram/master/NEWS.rst>
- <https://github.com/aiiie/cram>
- <https://formulae.brew.sh/formula/cram>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals

## Andere Paketmanager-Einträge

- Debian apt - python3-cram - 0.7-6: normalized package name match | Debian stable package indexes: python3-cram from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | functional testing framework for command line applications - Python 3.x | https://bitheap.org/cram/
- Ubuntu apt - python3-cram - 0.7-5: normalized package name match | Ubuntu 24.04 LTS package indexes: python3-cram from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | functional testing framework for command line applications - Python 3.x | https://bitheap.org/cram/
- MacPorts - cram: normalized package name match | MacPorts ports tree: devel/cram/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/cram.yml](https://github.com/mxcl/pkgdb/blob/main/combined/cram.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