# bee mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:bee
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install bee
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#bee
```

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

## Paketfakten

- **Paketschlüssel:** brew:bee
- **Paketmanager:** Homebrew
- **Version:** 1.115
- **Quellzusammenfassung:** Tool for managing database changes
- **Homepage:** <https://github.com/bluesoft/bee>
- **Repository:** <https://github.com/bluesoft/bee>
- **Zuletzt aktualisiert:** 2026-05-19T04:23:10Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- bee (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

Bee is a command-line database change manager from Bluesoft, used to manage database schema changes through project-local configuration.

### Projektgeschichte

The Bee GitHub repository was created in June 2011. Its README and project site describe it plainly as a tool for managing database changes, with documentation hosted on GitHub Pages.

Release history shows an established 1.x line: older GitHub releases are visible from 2013, and current releases continued through 2026.

### Adoptionsgeschichte

The supplied package metadata lists Homebrew and Nix packaging. The README also calls out Homebrew installation directly, suggesting macOS developer usage was part of the intended distribution story.

### Wie es verwendet wird

Bee is used from the command line to apply and manage database changes, with project settings stored in bee.properties.

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

Bee is a smaller package-nerd entry: it represents the long-running database-migration CLI niche where package managers preserve tools used by specific teams and legacy deployment workflows, even when the wider ecosystem has larger names.

### Zeitleiste

- 2011: GitHub repository created.
- 2013: 1.x GitHub releases visible.
- 2026: 1.115 release published.

### Related projects

- Related projects live in the database migration and schema-change-management category, such as JDBC-based migration tools.

### Quellen

- <https://api.github.com/repos/bluesoft/bee>
- <https://bluesoft.github.io/bee>
- <https://github.com/bluesoft/bee#readme>
- <https://github.com/bluesoft/bee/releases>
- source_facts.package-manager


## Sicherheitshinweise

Für bee wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.



## 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: bee.properties
## Andere Paketmanager-Einträge

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