Automic VaultAutomic Vault

brew

Install vfox with Homebrew, Nix, scoop, winget

Version manager with support for Java, Node.js, Flutter, .NET & more. Version 1.0.11 via Homebrew; verified 2026-04-29.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install vfox

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#vfox

nixpkgs package indexes · pkgs/by-name/vf/vfox/package.nix · source: api.github.com

Windows

Scoopverified · 92%
scoop install main/vfox

Scoop official bucket manifest trees · bucket/vfox.json · source: api.github.com

Windows Package Managerverified · 92%
winget install --id version-fox.vfox -e

Windows Package Manager source index · version-fox.vfox · source: cdn.winget.microsoft.com

overview

Package summary

Version manager with support for Java, Node.js, Flutter, .NET & more

Commands and aliases

  • vfox

history

Project history and usage

vfox, also branded VersionFox, is a cross-platform SDK and runtime version manager. It follows the family of tools represented by nvm, sdkman, fvm, and asdf, but emphasizes native Windows support, a plugin system, and version scopes for global, project, and shell-session use.

Project history

The version-fox/vfox repository was created in December 2023. Its documentation presents the project as a multi-SDK manager for Java, Node.js, Flutter, .NET, Go, Python, and other runtimes, with plugins used to extend support beyond the built-in set.

Public interest became visible in early 2024 through community posts such as a Show HN submission describing vfox as a cross-platform version manager with plugin extensibility, per-project and per-shell version locking, and compatibility with common version files such as .node-version, .nvmrc, and .sdkmanrc.

Adoption history

vfox's adoption has centered on developers who want one runtime manager across Windows, Linux, and macOS. The GitHub project had grown to several thousand stars by 2026, and its package-manager presence includes Homebrew, Scoop, winget, and Nix, reflecting the project's cross-platform positioning.

The plugin ecosystem is central to adoption. vfox documents a public plugin registry where users can install plugins with commands such as vfox add <plugin-name>, and external tools such as mise document vfox plugins as a supported backend for installing development tools.

How it is used

The common workflow is to install vfox, activate its shell integration, add or auto-install a plugin, install a runtime version, and choose whether that version is global, project-local, or limited to the current shell session. The quick-start guide demonstrates commands such as vfox install nodejs@21.5.0 and vfox use -g nodejs@latest while warning that exact versions are preferable for production reproducibility.

For project teams, vfox matters because it can automatically switch runtime versions when entering a project directory and can understand existing ecosystem files such as .nvmrc or .sdkmanrc. That lowers migration friction from single-runtime managers or from asdf-style workflows.

Why package nerds care

vfox is part of the newer generation of meta-version-managers that treat language runtimes, SDKs, and developer tools as pluggable package targets. Its notable package-nerd angle is the attempt to make that model comfortable on native Windows as well as Unix-like shells.

Timeline

  • 2023-12: version-fox/vfox was created on GitHub.
  • 2024-04: vfox was posted to Hacker News as a multi-runtime version manager with project and shell version scopes.
  • 2026-04: GitHub releases show vfox v1.0.11.
  • 2026: GitHub metadata showed thousands of stars and ongoing releases, while documentation and downstream package-manager records continued to present it as a cross-platform SDK manager.

Related projects

  • vfox explicitly positions itself near nvm, fvm, sdkman, and asdf-vm. It is also related to mise through mise's vfox backend, which can consume vfox plugins for development-tool installation.

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 6 platform targets.
  • Build metadata lists 1 build dependencies.

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
~/.version-fox.vfox.tomlvfox.toml

executables

Installed executables

CommandKindExposureNote
vfoxcliglobal 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.0.11
manager updated2026-04-29
local dataok
upstreamcurrent
latest detectedv1.0.11

https://github.com/version-fox/vfox

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:vfox
Version1.0.11
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/vfox
Homepagehttps://vfox.dev/
Repositoryhttps://github.com/version-fox/vfox
Upstream docshttps://vfox.dev/
LicenseApache-2.0
Source archivehttps://github.com/version-fox/vfox/archive/refs/tags/v1.0.11.tar.gz
Last updated2026-04-29T19:14:02Z
Pulseupdated
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namevfox
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

vfox

nix profile install nixpkgs#vfox
  • normalized package name match
  • Matched by: Vfox
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/vf/vfox/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Scoop95%

main/vfox

scoop install main/vfox
  • normalized package name match
  • Matched by: Vfox
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/vfox.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
winget95%

version-fox.vfox

winget install --id version-fox.vfox -e
  • normalized package name match
  • Matched by: Vfox
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: version-fox.vfox from https://cdn.winget.microsoft.com/cache/source.msix

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.

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
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment