# braid mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:braid
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install braid
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:braid
- **Paketmanager:** Homebrew
- **Version:** 1.1.10
- **Quellzusammenfassung:** Simple tool to help track vendor branches in a Git repository
- **Homepage:** <https://cristibalan.github.io/braid/>
- **Repository:** <https://github.com/cristibalan/braid>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- braid (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

Braid is a Ruby command-line tool for tracking vendored Git repositories inside another Git repository. It records vendored mirrors in .braids.json and provides commands to add, update, diff, and push changes back.

### Projektgeschichte

The GitHub repository for Braid was created in February 2008. Its official site frames the project around the old vendoring problem: projects often copied third-party source into their tree, then struggled to update it or send local changes upstream.

Braid's solution is to keep metadata about the external repository, branch, tag, revision, or subdirectory in .braids.json. That gives a plain Git repository enough memory to update a vendored copy later without converting the vendored directory into a nested repository.

### Adoptionsgeschichte

The official documentation presents RubyGems installation with gem install braid, while the input facts record Homebrew packaging. Its audience is narrower than Git itself: teams that deliberately vendor source and need repeatable updates.

Braid remained useful where teams preferred checked-in source copies over package-manager references, especially when local patches or co-evolution with the upstream library made binary package dependencies awkward.

### Wie es verwendet wird

Typical usage starts with braid add <repo> <path>, which vendors a remote Git repository into a project path and updates .braids.json. Later, braid update pulls upstream changes, braid diff emits local changes as a patch, and braid push can send local changes back to a source branch.

The documentation also covers pinning to branches, tags, or revisions and selecting subdirectories from a remote repository, making Braid a lightweight alternative to manual copy-and-patch vendoring.

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

Braid is interesting because it sits at the boundary between dependency management and version control. It preserves vendored source inside one repository while adding just enough metadata to make updates reproducible.

For package historians, it captures a pre-monorepo, pre-lockfile style of dependency handling common in Ruby and web projects: when package registries existed, but teams still wanted patched source in-tree.

### Zeitleiste

- 2008-02: The Braid GitHub repository was created.
- 2022-01: The documentation described supported environments as Linux, macOS, and Windows with recent Git and Ruby dependencies.
- 2024: The GitHub repository still showed recent activity in official repository metadata.

### Related projects

- Git is the underlying version-control system Braid extends.
- RubyGems is the installation channel shown in Braid's official documentation.
- Manual vendoring by copying source trees is the workflow Braid was built to improve.

### Quellen

- <https://api.github.com/repos/cristibalan/braid>
- <https://cristibalan.github.io/braid>
- source_facts.package-manager


## 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: <repository-root>/.braids.json

## Combined YAML source

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


## Quellen

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