chruby
6.0#15 in runtime version managersFree planFree planLinuxmacOS
Visitchruby vs nvm
What both publish
| Fact | chruby | nvm |
|---|---|---|
| Automatic switching | Optional auto-switching checks the current and parent directories for a .ruby-version file. | Automatic directory switching is documented as user-added bash or zsh hooks rather than built into the core command. |
| Integrations | The project wiki links usage instructions for Capistrano, Chef, Cron, Emacs, Pow, Puppet, Sudo, Vim, and Fish. | Documented integrations include Docker, Ansible, zsh plugins, bash completion and optional nvshim shims. |
| License | The repository identifies its license as MIT. | nvm is distributed under the MIT License, permitting use, modification, distribution and sale subject to retaining notices. |
| Purpose | chruby changes the current Ruby version in a shell. | nvm lets users install and use different Node.js versions from the command line. |
| Security | The README says all releases are PGP signed and gives instructions to verify a release signature. | The GitHub repository links to a security policy, but the README does not state a security certification or compliance standard. |
| Shell support | It supports bash 3 or later and zsh. | It works on POSIX-compliant shells including sh, dash, ksh, zsh, and bash. |
chruby plans
- FreeFree
nvm plans
- nvmFree
Pick chruby if…
chruby suits Ruby developers who want to select installed Ruby versions from bash or zsh. Its optional directory-based switching may help those who use .ruby-version files.
Pick nvm if…
nvm suits developers who need to manage Node.js versions from the command line, including per-project version selection and CI/CD use. It is intended for per-user, per-shell installation.