install

Additional install commands

macOS

Homebrewverified · 100%

brew install anyenv

local Homebrew formula metadata

overview

Package summary

All in one for **env

Project links

Commands and aliases

anyenv

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

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.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

narrow executable package without higher-risk signals

Signals

metadata:no-higher-risk-signals

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

executables

Installed executables

Command	Kind	Exposure	Note
`anyenv`	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.1.5

manager updated

local dataok

upstreamcurrent

latest detectedv1.1.5

https://github.com/anyenv/anyenv

infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package key	brew:anyenv
Version	1.1.5
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/anyenv
Homepage	https://anyenv.github.io/
Repository	https://github.com/anyenv/anyenv
Upstream docs	https://anyenv.github.io/
License	MIT
Source archive	https://github.com/anyenv/anyenv/archive/refs/tags/v1.1.5.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	anyenv
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	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/anyenv.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 anyenv with Homebrew