mise-backends-overview

The recommended default backend for tool installation in mise is aqua, providing a secure and provenance-driven path. It serves as the standard choice during tool onboarding and registry updates unless specific guardrails dictate an alternative.

To choose the right backend for onboarding a new tool, evaluate its packaging format and security requirements. Use aqua by default, but select github, gitlab, pipx, npm, go, cargo, or dotnet based on the tool's specific source and build system.

A "no backend found" error occurs during tool installation when no suitable backend is defined in the registry. Troubleshooting involves checking the backend ranking and updating the registry to map the tool to a supported backend like aqua or pipx.

You should avoid using asdf or vfox backends for tool management because they are deprecated. The system discourages their use in favor of more secure and maintainable alternatives like aqua, github, or language-native backends such as go and cargo.

Yes, you can use pipx and npm backends for Python and Node.js tool installation respectively. They are explicitly supported alongside go, cargo, and dotnet to provide guardrails for language-native package management within the registry.

The best way to update the registry for safer tool installation is to apply the official backend ranking. This standardizes backend selection by prioritizing aqua and language-native options while removing deprecated entries like vfox and asdf.