mise vs tenv
mise
mise.jdx.devtenv
tofuutils.github.ioSide by side
| Figure | mise | tenv |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Runtime Version Managers | 7.7 (#12) | 6.8 (#27) |
| Spec score · Development Environment Managers | 7.6 (#31) | 6.8 (#48) |
| License | The project is open source and MIT licensed. | The project is distributed under the Apache 2.0 license. |
| Purpose | mise manages development tools, environment variables, and project tasks through a project configuration file. | tenv is a Go version manager for OpenTofu, Terraform, Terragrunt, Terramate, and Atmos. |
| Support | The project directs questions to GitHub Discussions, bug reports to GitHub Issues, and security reports to the private process in SECURITY.md. | The project directs questions and suggestions to GitHub Issues and the tofuutils Slack community's #tofuutils channel. |
Plans
In their own words
mise
mise is a free, MIT-licensed open-source tool for managing development runtimes, command-line tools, environment variables, and project tasks from a configuration file. It runs on Linux, macOS, and Windows and lists a registry of more than 1,000 tools. Projects can pin tool versions and share those choices with teams and continuous-integration systems. Configuration can load variables from dotenv files, secrets, and shell commands. Tasks can define build, test, lint, and other commands with dependencies and arguments, with task graphs, affected-build handling, and remote caching listed. The bootstrap command can declare packages, dotfiles, repositories, and services for machine setup. Shell hooks cover bash, zsh, fish, nushell, PowerShell, and other shells. Documentation describes GitHub Actions, GitLab CI, and Xcode Cloud use. Community plugins are listed for Emacs, IntelliJ, Neovim, and VSCode, with support depending on editor, extension, and language. Security controls include trust settings, safe and paranoid modes, checksums, signatures, provenance, and artifact attestations.