PROVIDER - One tool for every runtime version

asdf

asdf manages hundreds of runtime versions for Node, Python, Ruby and more from 1 CLI, with 600+ plugins and .tool-versions enabling per-directory switching; however activity declined after 2024, plugin behaviour varies and the project recommends migrating to mise.

Developer Tools United States 2026.11.19
4.1pts

Detailed Notes

Pros 5 items

Manages hundreds of runtime versions for Node, Python, Ruby, Java and more from 1 CLI
A plugin mechanism extends coverage, with 600+ official and community plugins
1 .tool-versions file in the repository root pins versions so entering a directory switches automatically
Keeps 3 or more versions installed at once, replacing nvm, pyenv and rbenv with 1 tool
Implemented as dependency-free shell, so 1 setup step covers long-term use

Cons 4 items

Community activity declined after 2024, some plugins lag and the project points to mise
Plugin behaviour varies, and binary dependencies can still depend on the host system
No unified resolution or lock file, so consistency rests on .tool-versions discipline
After switching versions the PATH resolution order still needs confirmation

Service Overview

asdf is a multi-language runtime version manager. Plugins bring each language's version management under one command, and a .tool-versions file in the project directory decides which version applies.

In the development tools category it represents the unified version management layer: teams stop installing one manager per language and cover backend, frontend and infrastructure toolchains with a single asdf.

Key Strengths

  • Single entry point: 1 command covers hundreds of runtimes
  • Plugin ecosystem: 600+ official and community plugins
  • Per-directory switching: .tool-versions applies versions automatically
  • Less duplication: replaces nvm, pyenv and rbenv with one tool
  • Zero dependencies: pure shell implementation, simple setup

Product Ecosystem

Platform capabilities

Version install and switch, global and project scoping, plugin management, command shims and version queries.

Integrations

Works with direnv, GitHub Actions, Docker, Makefiles and each language's native toolchain.

Typical scenarios

Polyglot monorepos, team collaboration on pinned tool versions and runtime consistency in CI.

Limitations

  • Maintenance risk: activity declined after 2024 and migration to mise is recommended
  • Plugin variance: versions behave differently across plugins
  • No lock file: consistency relies on .tool-versions discipline
  • PATH ordering: multi-version setups still need verification

Use Cases

  • Polyglot repositories (★★★★☆): one tool for every runtime
  • Team-wide tool version alignment (★★★★☆): directory-level pins are easy to review
  • New projects (★★★☆☆): consider successor tools such as mise directly
  • Strong locking and task running (★★★☆☆): mise or dedicated tools fit better

Pricing

Item Price Notes
asdf itself $0 MIT open source, commercial use allowed
Community plugins $0 Maintained per project
Commercial support None Community discussions and issues

FAQ

How does asdf differ from nvm or pyenv?

nvm and pyenv handle one language each, while asdf unifies many languages through plugins and reduces tool count.

Should .tool-versions be committed?

Yes, it is what keeps the team and CI on identical versions.

Can asdf be migrated to mise?

Yes. mise supports .tool-versions and asdf plugins, so the migration is cheap.

What usually causes install failures?

Outdated plugins or missing system build dependencies; update the plugin and install build tools.

Code Examples

# Install asdf on macOS
brew install asdf

# Add a language plugin and install a version
asdf plugin add nodejs
asdf install nodejs 20.11.1
asdf global nodejs 20.11.1

# Pin a version for the current project
asdf local python 3.11.8
cat .tool-versions
# Example .tool-versions
nodejs 20.11.1
python 3.11.8
ruby 3.3.0

Community & Resources

Visit asdf Website → https://asdf-vm.com/
Visit Website ↗