# liquibase mit Homebrew, apk, chocolatey, Nix, scoop, winget installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für liquibase in AI-Agent-Workflows.
## Installation
```sh
sudo av install brew:liquibase
```
Weitere Installationsbefehle:
### macOS
- Homebrew (100%):
```sh
brew install liquibase
```
Evidenz: local Homebrew formula metadata
### Linux
- apk (92%):
```sh
sudo apk add liquibase
```
Evidenz: Alpine Linux edge package indexes: liquibase from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
- Nix (92%):
```sh
nix profile install nixpkgs#liquibase
```
Evidenz: nixpkgs package indexes: pkgs/by-name/li/liquibase/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
### Windows
- Chocolatey (92%):
```sh
choco install liquibase
```
Evidenz: Chocolatey community package catalog: liquibase from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','lftp'
- Scoop (92%):
```sh
scoop install main/liquibase
```
Evidenz: Scoop official bucket manifest trees: bucket/liquibase.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- winget (92%):
```sh
winget install --id Liquibase.Liquibase -e
```
Evidenz: Windows Package Manager source index: Liquibase.Liquibase from https://cdn.winget.microsoft.com/cache/source.msix
## Paketfakten
- **Paketschlüssel:** brew:liquibase
- **Paketmanager:** Homebrew
- **Version:** 4.33.0
- **Quellzusammenfassung:** Library for database change tracking
- **Homepage:**
- **Repository:**
- **Generiert:** 2026-08-03T19:37:03+00:00
## Executables
- liquibase (Alias)
## Installationsverhalten
- Bottle: nicht verfügbar
## Version und Aktualität
- Seite generiert: 2026-08-03
- Manager-Version: 4.33.0
## Projektgeschichte und Nutzung
Liquibase is a database change management project and CLI that turns schema and data changes into versioned changelog files, records which changesets have run, and supports repeatable deployment and rollback workflows.
### Projektgeschichte
Nathan Voxland founded the Liquibase open-source project in 2006 to make database changes easier to track. The project developed into a Java-based database migration ecosystem with command-line usage, embeddable libraries, build-tool integrations, and commercial governance products around the same core workflow.
The main source repository is the liquibase/liquibase GitHub project. The documentation site distinguishes Liquibase Community from Liquibase Secure, but both build around the same core concepts of changelogs, changesets, checksums, update operations, rollback operations, and database history tables.
### Adoptionsgeschichte
Liquibase adoption followed the rise of database DevOps: teams wanted schema changes reviewed, versioned, and deployed alongside application code instead of kept as ad hoc DBA scripts. Support for SQL, XML, YAML, and JSON changelogs made it usable across teams with different preferences.
Package managers carry Liquibase because developers and CI workers need a reproducible CLI. The Homebrew formula also records packaging details that differ from the cask path: it uses the liquibase formula name, depends on openjdk, and tells users to set LIQUIBASE_HOME to the formula libexec directory.
### Wie es verwendet wird
A typical Liquibase project stores changelogs in the repository, points Liquibase at a target database and JDBC driver, then runs update or rollback commands. Liquibase records execution in DATABASECHANGELOG and uses checksums to notice changes to previously deployed changesets.
The Homebrew formula is the package-manager-oriented CLI path for brew install liquibase. In this batch it records stable version 4.33.0, while the cask:liquibase-community package records the vendor Community cask at version 5.0.3.
### Warum Paket-Nerds sich dafür interessieren
Liquibase is a classic developer-tool package because it lives in local shells, CI images, Docker workflows, and build systems but acts on external databases. Correct packaging has to balance Java runtime dependency, driver extensibility, config-file conventions, and command-line reproducibility.
The formula/cask split is package-nerd useful: the formula presents Liquibase as a Homebrew-managed CLI with an OpenJDK dependency and LIQUIBASE_HOME guidance, while the cask presents Liquibase Community as a vendor-distributed application archive.
### Zeitleiste
- 2006: Nathan Voxland founded the Liquibase open-source project.
- 2010s: Liquibase expanded from a Java database migration library into a broader DevOps command-line and integration ecosystem.
- 2020: Liquibase company branding aligned with the project name and the product family around Community and commercial offerings.
- 2025: Liquibase documentation described Community changelogs in SQL, XML, YAML, and JSON and continued documenting DATABASECHANGELOG behavior.
- 2026: The Homebrew formula record for this batch identifies liquibase stable 4.33.0 with an OpenJDK dependency and LIQUIBASE_HOME guidance.
### Related projects
- Flyway is Liquibase's closest package-manager neighbor in database migration tooling.
- Related tooling includes JDBC drivers, Maven and Gradle plugins, Docker images, database diff tools, CI/CD systems, and commercial database DevOps products.
### Quellen
-
-
-
-
-
-
-
## Sicherheitshinweise
broad file, network, media, or database tool signal.
- **Geiger-Risiko:** blue / mittel
- broad file, network, media, or database tool signal
## 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: ./liquibase.properties, $LIQUIBASE_HOME/examples//liquibase.properties
## Credential files
- Unix: ./liquibase.properties, path supplied with --driver-properties-file
## Andere Paketmanager-Einträge
- Nix - liquibase: normalized package name match | nixpkgs package indexes: pkgs/by-name/li/liquibase/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- apk - liquibase - 4.9.1-r0: normalized package name match | Alpine Linux edge package indexes: liquibase from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Source Control for your Database | https://www.liquibase.org/
- apk - liquibase-doc - 4.9.1-r0: normalized package name match | Alpine Linux edge package indexes: liquibase-doc from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Source Control for your Database (documentation) | https://www.liquibase.org/
- Chocolatey - liquibase: normalized package name match | Chocolatey community package catalog: liquibase from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','lftp'
- Scoop - main/liquibase: normalized package name match | Scoop official bucket manifest trees: bucket/liquibase.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- winget - Liquibase.Liquibase: normalized package name match | Windows Package Manager source index: Liquibase.Liquibase from https://cdn.winget.microsoft.com/cache/source.msix
## Verwandte Links
- [liquibase](https://pkg.so/de/pkg/npm/liquibase/) - Same normalized package name exists in another local package ecosystem.
## Combined YAML source
View the package source record on GitHub. [combined/liquibase.yml](https://github.com/mxcl/pkgdb/blob/main/combined/liquibase.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