# conda-lock mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:conda-lock
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install conda-lock
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:conda-lock
- **Paketmanager:** Homebrew
- **Version:** 4.0.2
- **Quellzusammenfassung:** Lightweight lockfile for conda environments
- **Homepage:** <https://conda.github.io/conda-lock/>
- **Zuletzt aktualisiert:** 2026-07-25T09:53:36Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- conda-lock (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

conda-lock generates reproducible lock files for conda environments by solving for target platforms ahead of installation, so installers can consume pinned lock output without invoking the conda solver at deploy time.

### Projektgeschichte

The official repository was created in 2019. Version 1.0.0, published in March 2022, introduced the unified lock format as the default and documented the old explicit per-platform style as a compatibility mode. Version 2.0.0, published in May 2023, was the first release under the Conda organization after graduating from conda-incubator.

### Adoptionsgeschichte

conda-lock fits the reproducible-environments gap between human-authored conda environment.yml files and fully pinned, multi-platform deployment artifacts. Its documentation emphasizes environment.yml, meta.yaml, pyproject.toml, integrated pip support, and solveless conda installation.

### Wie es verwendet wird

Users typically provide one or more source files such as environment.yml, conda-lock.yml, pyproject.toml, or meta.yaml, choose target platforms, generate conda-lock.yml, and install or render platform-specific lock files in CI or deployment workflows.

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

For package-manager users, conda-lock is important because it makes conda environments behave more like lockfile-centered ecosystems: input specs remain readable while machine-resolved artifacts preserve exact packages across Linux, macOS, Windows, and architecture variants.

### Zeitleiste

- 2019: Official GitHub repository created.
- 2022: v1.0.0 released with the unified lock format.
- 2023: v2.0.0 released as the first release under the Conda organization.

### Related projects

- conda-lock is closely tied to conda, conda-forge, mamba, pip, Poetry-style pyproject metadata, and conda environment.yml workflows.

### Quellen

- <https://conda.github.io/conda-lock>
- <https://github.com/conda/conda-lock>
- <https://github.com/conda/conda-lock/releases/tag/v1.0.0>
- <https://github.com/conda/conda-lock/releases/tag/v2.0.0>


## Sicherheitshinweise

Für conda-lock 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: ./environment.yml, ./conda-lock.yml, ./pyproject.toml, ./meta.yaml

## Combined YAML source

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