cachix/devenv
Fast, Declarative, Reproducible, and Composable Developer Environments using Nix observed · 2026-08-28
Health v2 · maintenance only
98/100
- Activity 99
- Release rhythm 97
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 7.5
- age_days: 1411
- days_rel: 20
- days_push: 7
- n_releases_24m: 35
Adoption not part of the score
7408 stars · 549 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
devenv is a Rust CLI tool that lets developers declare their entire development environment—packages, language toolchains, services, tasks, and processes—in a devenv.nix file built on Nix. It delivers fast incremental evaluation, background shell rebuilding, a terminal UI, a process manager with dependency ordering, and the same environment for local work and CI.
Use cases
- set up a reproducible development environment that works identically on mac and linux
- run postgres, redis, and other services locally without docker compose files
- pin exact compiler and toolchain versions per project without polluting the global system
- give every teammate and CI the same environment from one committed config file
- onboard new developers with a single command that builds the whole stack
- run multiple dev processes with dependency ordering and readiness probes
- declare and load secrets from different providers without committing them
When to choose
- your team needs identical, reproducible environments across laptops and CI and is willing to adopt Nix under the hood
- you want declaratively managed services like PostgreSQL or Redis with a built-in process manager instead of hand-written scripts or containers
- you juggle many projects with conflicting language versions and want per-project, cached toolchains
- you want a friendlier interface to Nix with LSP support, instant caching, and shell reloading
When to avoid
- your team is not prepared to install Nix or learn its ecosystem, since devenv depends on it entirely
- your environment is already fully served by Docker Compose or dev containers and the team prefers that workflow
- you need native Windows support outside WSL2
- you want zero config: devenv is declarative config-first, so fully ad hoc one-off setups are better served by plain shell scripts
Facets
cli-tool · maturity active
configuration-management developer-tools cli package-manager developer-tools windows cli nix declarative-environments reproducible-builds devshell process-manager task-runner terminal-ui secrets nixpkgs command-line devops linux macos docker
5 sources
- readme: https://github.com/cachix/devenv · fetched 2026-08-28 · 5f6d28f1bed7
- homepage: https://devenv.sh · fetched 2026-08-29 · 4c68dbefd35b
- site_page: https://devenv.sh/getting-started · fetched 2026-08-29 · d498eb84b652
- site_page: https://devenv.sh/integrations/secretspec · fetched 2026-08-29 · 17e2e3d93c68
- site_page: https://devenv.sh/integrations/github-actions · fetched 2026-08-29 · e037e6cebba5
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| cachix/devenv | main | 98 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem