# Installer varlock avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de varlock pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:varlock
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install varlock
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:varlock
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.16.0
- **Résumé source:** Add declarative schema to .env files using @env-spec decorator comments
- **Page d'accueil:** <https://varlock.dev>
- **Dernière mise à jour:** 2026-08-01T21:49:42Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- varlock (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 1.16.0
## Historique du projet et usages

Varlock is a young configuration and secrets tool for `.env`-based workflows. Its project tagline frames the tool around AI-safe `.env` files: schemas are safe for agents and collaborators to read, while actual secrets are resolved separately.

### Historique du projet

The project is built on `@env-spec`, a DSL that extends normal `.env` syntax with JSDoc-style decorator comments and function-call values. The initial `@env-spec` RFC was proposed on May 13, 2025 by maintainers Phil Millman and Theo Ephraim, describing the goal of richer validation, type coercion, sensitive-value handling, and dynamic loading while keeping the familiar `.env` format.

### Historique d'adoption

Varlock targets the pain point left by `.env.example`: example files are safe to commit but often drift from real runtime requirements. Varlock instead promotes a committed `.env.schema` as a single source of truth, with local or environment-specific `.env.*` files supplying values.

### Modes d'utilisation

Typical usage starts with `varlock init`, which scans existing `.env` files and creates a root `.env.schema`. Users then run `varlock load` to validate and inspect resolved environment variables or `varlock run -- <command>` to execute a process with resolved values. The tool also ships as a standalone binary, Docker image, editor support, and plugins for secret backends such as 1Password, AWS, Azure, Google Secret Manager, HashiCorp Vault, and others.

### Pourquoi les passionnés de paquets s'y intéressent

For package users, Varlock is notable as an attempt to standardize metadata around environment variables without forcing a new YAML, JSON, or TypeScript schema file. It is especially tuned for modern AI-assisted development, where agents need configuration context but should not be handed plaintext secrets.

### Chronologie

- 2025-05-13: Initial `@env-spec` RFC proposed.
- 2026: Repository documents Varlock as a CLI, Docker image, VS Code extension ecosystem, and plugin host for multiple secret backends.

### Related projects

- DMNO is cited by the maintainers as the predecessor whose lessons informed Varlock.
- `@env-spec` is the underlying specification and parser family used by Varlock.

### Sources

- Initial @env-spec RFC: https://github.com/dmno-dev/varlock/discussions/17
- Official @env-spec overview: https://varlock.dev/env-spec/overview/
- Official GitHub repository: https://github.com/dmno-dev/varlock
- Official installation guide: https://varlock.dev/getting-started/installation/


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour varlock. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.



## 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: .env.schema

## Credential files

- Unix: .env.local, .env.*

## Combined YAML source

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