# bork mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:bork
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install bork
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#bork
```

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

## Paketfakten

- **Paketschlüssel:** brew:bork
- **Paketmanager:** Homebrew
- **Version:** 0.14.0
- **Quellzusammenfassung:** Bash-Operated Reconciling Kludge
- **Homepage:** <https://bork.sh/>
- **Repository:** <https://github.com/borksh/bork>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- bork (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

bork is a Bash-based declarative configuration-management tool whose joke expansion, Bash-Operated Reconciling Kludge, accurately signals both its Unix minimalism and its Puppet-like reconciliation model.

### Projektgeschichte

The current borksh repository was created in February 2021, while the public project history includes an earlier mattly/bork repository. The official site describes bork as a Bash DSL for declarative assertions about system state.

bork intentionally targets Bash 3.2 and common Unix utilities such as sed, awk, and grep, which makes portability across macOS and Unix-like systems part of the design rather than an accident.

### Adoptionsgeschichte

bork is niche but packaged: the batch input records Homebrew and Nix availability, and the official packages page tracks package versions across channels. That suggests a tool maintained for small-scale operator and dotfile workflows rather than broad enterprise configuration management.

Its adoption is strongest where users want declarative host setup without agents, services, or a large language runtime.

### Wie es verwendet wird

Users write assertions using ok and no functions, declaring desired states such as files, directories, packages, or services. bork handlers then decide whether to check, install, upgrade, or otherwise reconcile that assertion.

The manpage frames bork files as config files in their own right, so there is no separate fixed config path; users pass or run the scripts that contain their assertions.

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

bork is interesting because it keeps configuration management inside the shell and standard Unix toolbox. It is the opposite of a heavy agent: package it, run a script, reconcile state.

For package curation, it is a reminder that some useful infrastructure tools are intentionally tiny DSLs rather than daemons or platforms.

### Zeitleiste

- 2021-02: Official GitHub repository metadata shows borksh/bork created.
- 2021-02: GitHub release metadata shows v0.11.1 in the public release feed.
- 2025: Repository metadata shows continued maintenance activity.
- 2026: Package-manager input records Homebrew and Nix packaging.

### Related projects

- Puppet is a conceptual reference point in bork's own tagline about configuration management.
- Bash and common Unix utilities are explicit runtime foundations.
- The borksh/homebrew-tap repository is related packaging infrastructure maintained by the project organization.

### Quellen

- <https://api.github.com/repos/borksh/bork>
- <https://bork.sh/>
- <https://bork.sh/manpage.html>
- <https://bork.sh/packages.html>
- <https://github.com/borksh/bork>
- source_facts.package-manager


## Sicherheitshinweise

narrow executable package without higher-risk signals.

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

## Andere Paketmanager-Einträge

- Nix - bork: normalized package name match | nixpkgs package indexes: pkgs/by-name/bo/bork/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/bork.yml](https://github.com/mxcl/pkgdb/blob/main/combined/bork.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