# Installer envv avec Homebrew

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

## installation

```sh
sudo av install brew:envv
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install envv
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:envv
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.7
- **Résumé source:** Shell-independent handling of environment variables
- **Page d'accueil:** <https://github.com/jakewendt/envv>
- **Dépôt:** <https://github.com/jakewendt/envv>
- **Dernière mise à jour:** 2026-07-10T19:51:01-04:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- envv (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

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

envv is a small C utility for generating shell-specific commands that set environment variables and edit colon-separated paths. Its niche is old-school Unix software setup: one script can be sourced by users of csh, tcsh, bash, sh, ksh, and zsh without hard-coding separate initialization logic for each shell.

### Historique du projet

The README traces envv back to David F. Skoll of Roaring Penguin Software, with version 1.0 dated February 8, 1994. Early releases added zsh recognition, a `choose` directive, local variables, stdin directives, and fixes around path comparison and environment persistence.

The GitHub-hosted copy records a later 2011 license change to MIT and a segmentation fault fix, but otherwise presents envv as a deliberately small utility: build with `make`, copy the `envv` executable into a system directory, and consult the bundled `envv.1` manual page.

### Historique d'adoption

envv never became a broad ecosystem package, but its continued packaging in Homebrew keeps a 1990s Unix environment-management tool installable on modern developer machines. The README's example is aimed at commercial or site-local software that needs PATH entries and home variables set consistently for many user shells.

### Modes d'utilisation

A typical envv setup script evaluates commands such as `envv add PATH /usr/local/foobar/bin` and `envv set FOOHOME /usr/local/foobar`. Users source that script from their preferred shell, allowing system-wide software moves without each user editing `.cshrc`, `.profile`, or similar files by hand.

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

envv is interesting as a compact survivor from the era when Unix shops had to support several interactive shells at once. For package-manager history, it is a reminder that environment setup before modules, direnv, and modern shell frameworks often meant tiny C tools that printed shell code.

### Chronologie

- 1994-02-08: Version 1.0 first released.
- 1994-03-22: Version 1.1 added zsh recognition and the `choose` directive.
- 1994-04-18: Version 1.2 added local variables, command-line options, and stdin directives.
- 1995-07-11: Version 1.6 fixed path comparison behavior.
- 2011-07-14: Version 1.7 changed the license to MIT and fixed a segmentation fault.

### Related projects

- envv overlaps conceptually with shell profile snippets, environment modules, and later per-directory environment tools, but it solves a narrower problem by emitting commands for multiple shells.

### Sources

- <https://github.com/jakewendt/envv>
- <https://raw.githubusercontent.com/jakewendt/envv/master/README>


## Notes de sécurité

generalized runtime or code generation signal.

- **Risque Geiger:** yellow / moyen
- generalized runtime or code generation signal


## Combined YAML source

View the package source record on GitHub. [combined/envv.yml](https://github.com/mxcl/pkgdb/blob/main/combined/envv.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph