version-fox/vfox
A cross-platform and extendable version manager with support for Java, Node.js, Golang, Python, Flutter, .NET & more observed · 2026-08-28
Health v2 · maintenance only
87/100
- Activity 98
- Release rhythm 81
- Longevity 71
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: 8.0
- age_days: 998
- days_rel: 126
- days_push: 12
- n_releases_24m: 29
Adoption not part of the score
3970 stars · 157 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
vfox is a cross-platform, plugin-extensible version manager (similar to nvm, sdkman, and asdf-vm) for installing and switching SDKs such as Java, Node.js, Go, Python, Flutter, and .NET. Written in Go, it unifies per-project, per-shell, and global version management behind one CLI and one .vfox.toml config, with a simple Lua plugin API and shell hooks for automatic version switching.
Use cases
- manage multiple java or node.js versions on windows without wsl
- switch sdk versions automatically when entering a project directory
- replace nvm, sdkman, fvm, and asdf with a single version manager
- install and switch between python, golang, and flutter from one cli
- share consistent tool versions across a team via one config file
- add version management for a custom runtime via plugins
- migrate from asdf keeping existing .tool-versions or .nvmrc files
When to choose
- You work across Windows, Linux, and macOS and want one consistent version manager everywhere
- You juggle many language runtimes and want a single CLI and config instead of per-language managers
- You need project-level, session-level, or global versions with automatic switching as you change directories
- You want to extend version management to any tool via a simple Lua plugin API
- You are coming from asdf/nvm/sdkman and want compatibility with .tool-versions, .nvmrc, .node-version, or .sdkmanrc
When to avoid
- You only need one language runtime, where a dedicated manager like nvm or pyenv may be simpler
- You rely on CMD, which only supports global scope and is not recommended
- Your CI/Docker pipelines are non-interactive and you prefer not to use vfox exec or container-native tooling
- You depend on a very specific asdf plugin ecosystem or shim-based behavior that vfox does not replicate
Facets
cli-tool · maturity active
cli package-manager developer-tools plugin-system configuration-management sdk developer-tools cross-platform windows cli cross-platform version-manager sdk-manager asdf-alternative nvm-alternative sdkman-alternative lua-plugins shell-integration runtime-switching toml-config environment-management command-line linux macos
4 sources
- readme: https://github.com/version-fox/vfox · fetched 2026-08-28 · 1b13911aa530
- homepage: https://vfox.dev · fetched 2026-08-29 · d5344c1015bc
- site_page: https://vfox.dev/guides/intro.html · fetched 2026-08-29 · 922fb92c2f2c
- site_page: https://vfox.dev/guides/faq.html · fetched 2026-08-29 · f8c317339054
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| version-fox/vfox | main | 87 |
For agents
markdown · JSON · MCP: product_card(name="version-fox/vfox")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem