# dagger mit Homebrew, chocolatey, MacPorts, pacman, scoop, winget installieren

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

## Installation

```sh
sudo av install brew:dagger
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install dagger
```

  Evidenz: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install dagger
```

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

### Linux

- pacman (92%):

```sh
sudo pacman -S dagger
```

  Evidenz: Arch Linux sync databases: dagger from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

### Windows

- Chocolatey (92%):

```sh
choco install dagger
```

  Evidenz: Chocolatey community package catalog: dagger from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='6.7743998','highlight'

- Scoop (92%):

```sh
scoop install main/dagger
```

  Evidenz: Scoop official bucket manifest trees: bucket/dagger.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

- winget (92%):

```sh
winget install --id Dagger.Cli -e
```

  Evidenz: Windows Package Manager source index: Dagger.Cli from https://cdn.winget.microsoft.com/cache/source.msix

## Paketfakten

- **Paketschlüssel:** brew:dagger
- **Paketmanager:** Homebrew
- **Version:** 0.21.8
- **Quellzusammenfassung:** Portable devkit for CI/CD pipelines
- **Homepage:** <https://dagger.io>
- **Repository:** <https://github.com/dagger/dagger>
- **Zuletzt aktualisiert:** 2026-07-29T17:54:05Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- dagger (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

Dagger is a software-delivery automation platform and CLI. It packages CI/CD automation as programmable, container-backed modules and functions that run locally, in CI, or in Dagger Cloud.

### Projektgeschichte

Dagger's official launch post introduced it on March 30, 2022 as a portable devkit for CI/CD pipelines from the creators of Docker. The public repository itself dates back to 2019, and the launch post says the project had been developed with early adopters before continuing in the open.

### Adoptionsgeschichte

Dagger's adoption pitch is local-first CI/CD: write automation once, run it on a laptop or CI server, and avoid environment drift and CI lock-in. Current official docs emphasize a CLI, a Dagger Engine, generated SDKs, reusable modules, tracing, and container-runtime-backed execution.

### Wie es verwendet wird

Users invoke the dagger CLI to run functions, modules, checks, toolchains, and CI workflows. Current module configuration is centered on dagger-module.toml, while workspace commands such as dagger install, dagger config, and dagger settings update dagger.toml.

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

Dagger is interesting to package nerds because it treats delivery pipelines as portable code rather than vendor-specific YAML. Its formula installs a CLI that brokers a larger engine, SDK, module, and container ecosystem, making the package a doorway into programmable build and release workflows.

### Zeitleiste

- 2019: Public dagger/dagger GitHub repository is created.
- 2022: Dagger is publicly introduced as a portable devkit for CI/CD pipelines.
- 2022: Official launch post says development will continue in the open.
- 2026: Official docs describe Dagger as a platform for automating software delivery.

### Related projects

- The launch post says Dagger is powered by BuildKit; current docs place it alongside container runtimes, SDKs, Dagger modules, Dagger Cloud, and OpenTelemetry tracing.

### Quellen

- <https://dagger.io/blog/public-launch-announcement>
- <https://docs.dagger.io/>
- <https://docs.dagger.io/reference/configuration/modules>
- <https://api.github.com/repos/dagger/dagger>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

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


## 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.


## Configuration files

- Unix: ./dagger.json
## Andere Paketmanager-Einträge

- pacman - dagger - 0.21.8-1: normalized package name match | Arch Linux sync databases: dagger from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A portable devkit for CI/CD pipelines | https://dagger.io
- MacPorts - dagger: normalized package name match | MacPorts ports tree: devel/dagger/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Chocolatey - dagger: normalized package name match | Chocolatey community package catalog: dagger from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='6.7743998','highlight'
- Scoop - main/dagger: normalized package name match | Scoop official bucket manifest trees: bucket/dagger.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- winget - Dagger.Cli: normalized package name match | Windows Package Manager source index: Dagger.Cli from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

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