# Installer xcenv avec Homebrew

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

## installation

```sh
sudo av install brew:xcenv
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install xcenv
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:xcenv
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.2.0
- **Résumé source:** Xcode version manager
- **Page d'accueil:** <https://github.com/xcenv/xcenv>
- **Dépôt:** <https://github.com/xcenv/xcenv>
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- xcenv (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

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

xcenv is an Xcode version manager modeled around project and global version files. Its README frames the tool as a way to document and manage the Xcode version required by a project or shell environment.

### Historique du projet

xcenv was created to solve a common Apple-development problem: teams often need multiple Xcode.app bundles installed, but `xcode-select` and `DEVELOPER_DIR` require agreement on exact application paths. The README explicitly calls out conflicting app naming conventions, such as `Xcode7.2.app` versus `Xcode_7_2.app`, as the kind of team-level friction the tool avoids.

### Historique d'adoption

The tool follows the family pattern of language and runtime managers that use shims plus local and global version files. In xcenv's case, those shims wrap tools such as `xcodebuild`, `xcrun`, and other Xcode binaries so third-party build tools can inherit the selected Xcode version.

### Modes d'utilisation

xcenv chooses the active Xcode version from `DEVELOPER_DIR`, then `XCENV_VERSION`, then the nearest `.xcode-version` file, then the global `~/.xcenv/.xcode-version` file. A project can commit `.xcode-version` so that switching branches or checking out old commits also records the expected Xcode toolchain.

The main commands are `xcenv local`, `xcenv global`, `xcenv shell`, `xcenv version`, and `xcenv rehash`. Its README names Fastlane, CocoaPods, Shenzhen, and existing scripts using `xcodebuild` or `xcrun` as examples of tools that can benefit from the shim approach.

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

xcenv is notable less as a large project than as an Apple-platform adaptation of the version-file convention familiar from tools such as rbenv. For package and build-system users, the important idea is that the required Xcode version can live with the source tree instead of in local machine notes.

### Chronologie

- 2010s: xcenv adopts a shim-and-version-file model for Xcode toolchains.
- 2020s: The `.xcode-version` convention remains visible in Apple build tooling discussions and related tools.

### Related projects

- The README names Fastlane, CocoaPods, and Shenzhen as tools that can run through xcenv shims.
- Later Xcode managers such as Xcodes and Xcodes.app focus more on downloading and switching installed Xcode versions, while xcenv centers on documenting and resolving the version to use.

### Sources

- <https://github.com/XcodesOrg/XcodesApp#readme>
- <https://github.com/XcodesOrg/xcodes#readme>
- <https://github.com/xcenv/xcenv#readme>


## Notes de sécurité

infrastructure mutation or orchestration signal.

- **Risque Geiger:** orange / moyen
- infrastructure mutation or orchestration signal


## 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: ./.xcode-version, ~/.xcenv/.xcode-version

## Combined YAML source

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