# Install conda-lock with Homebrew

Lightweight lockfile for conda environments. Version 4.0.2 via Homebrew; verified 2026-07-25.

## Install

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

Additional install commands:

### macOS

- Homebrew (100%):

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

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:conda-lock
- **Package manager:** Homebrew
- **Version:** 4.0.2
- **Source summary:** Lightweight lockfile for conda environments
- **Homepage:** <https://conda.github.io/conda-lock/>
- **Last updated:** 2026-07-25T09:53:36Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- conda-lock (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 4.0.2
## Project history and usage

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.

### Project history

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.

### Adoption history

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.

### How it is used

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.

### Why package nerds care

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.

### Timeline

- 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.

### Sources

- <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>


## Security Notes

No matching local secret-handling manifest was found for conda-lock. Nucleus package metadata is still published here so future coverage has a stable package URL.



## 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)


## Sources

- 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