install

Additional install commands

macOS

Homebrewverified · 100%

brew install xcenv

local Homebrew formula metadata

overview

Package summary

Xcode version manager

Project links

Commands and aliases

xcenv

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

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

security posture

Risk level: orange

infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

infrastructure mutation or orchestration signal

Signals

text:version manager

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 1 platform targets.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

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

Config paths the tool may read or write during local use.

Unix: ./.xcode-version~/.xcenv/.xcode-version

executables

Installed executables

Command	Kind	Exposure	Note
`xcenv`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version1.2.0

manager updated

local dataok

upstreamcurrent

latest detectedv1.2.0

https://github.com/xcenv/xcenv

infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package key	brew:xcenv
Version	1.2.0
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/xcenv
Homepage	https://github.com/xcenv/xcenv
Repository	https://github.com/xcenv/xcenv
Upstream docs	https://github.com/xcenv/xcenv#readme
License	MIT
Source archive	https://github.com/xcenv/xcenv/archive/refs/tags/v1.2.0.tar.gz
Bottle	available (on all)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	xcenv
Version Scheme	0
Revision	0
Head Version	HEAD
Requirements	macos
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/xcenv.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
package relationship graph
package version freshness
package-page enrichment

Install xcenv with Homebrew