# Installer anyenv avec Homebrew

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

## installation

```sh
sudo av install brew:anyenv
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install anyenv
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:anyenv
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.1.5
- **Résumé source:** All in one for **env
- **Page d'accueil:** <https://anyenv.github.io/>
- **Dépôt:** <https://github.com/anyenv/anyenv>
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- anyenv (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

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

anyenv is a wrapper for rbenv-style environment managers. It exists for developers who use several language-specific '*env' tools and do not want to clone and shell-initialize each one by hand.

### Historique du projet

The official README describes anyenv as 'All in one for **env' and a simple wrapper around rbenv-style environment managers. It installs managers such as rbenv, pyenv, and nodenv through manifest scripts, then lets the individual manager handle language/runtime installation.

The companion anyenv-install repository defines the manifest format. A manifest is just a shell script using install_env and optional install_plugin calls, which keeps anyenv's core small and pushes per-manager installation rules into a separate manifest directory.

### Historique d'adoption

anyenv is most common among shell users who already accept the rbenv/pyenv/nodenv style of shims and per-user runtime directories. The input facts show Homebrew packaging, and the official README starts with Homebrew setup for macOS users before describing manual git checkout.

The project is intentionally niche: it does not replace each language manager's ecosystem, it reduces the installation and shell-profile repetition around using many of them.

### Modes d'utilisation

A user installs anyenv, runs anyenv init, initializes the manifest directory with anyenv install --init, and then installs managers with commands such as anyenv install rbenv, anyenv install pyenv, and anyenv install nodenv. After restarting the shell, the installed manager commands are available.

Configuration centers on ANYENV_DEFINITION_ROOT, the directory containing install manifests. If not set, official docs fall back to ${XDG_CONFIG_HOME}/anyenv/anyenv-install or ${HOME}/.config/anyenv/anyenv-install.

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

anyenv is package-manager glue for package-manager people: it manages managers. Its interesting bit is not a runtime resolver, but the small manifest protocol that bootstraps many language-specific env tools from one command.

It is also a reminder that shell initialization is real packaging surface. anyenv's value is partly that it centralizes PATH and init setup, avoiding a growing dotfile pile of independent *env snippets.

### Chronologie

- 2010s: anyenv adopts the rbenv-style manager pattern as a wrapper around multiple '*env' tools.
- 2020s: The repository reaches the v1.1.x tag series and remains documented through anyenv.github.io and GitHub README.
- 2026: Homebrew package facts list anyenv as an available formula.

### Related projects

- rbenv, pyenv, and nodenv are examples shown in the official usage docs.
- anyenv-install is the official manifest repository used by anyenv install --init.
- anyenv-update and anyenv-git are plugins listed by the official README.

### Sources

- Official anyenv README, anyenv.github.io, anyenv-install README, and source_facts.package-manager.


## Notes de sécurité

narrow executable package without higher-risk signals.

- **Risque Geiger:** vert / faible
- narrow executable package without higher-risk signals


## 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: ${XDG_CONFIG_HOME}/anyenv/anyenv-install, ${HOME}/.config/anyenv/anyenv-install

## Combined YAML source

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