# Installer volta avec Homebrew, chocolatey, MacPorts, Nix, scoop, winget

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de volta pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:volta
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install volta
```

  Preuve: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install volta
```

  Preuve: MacPorts ports tree: www/volta/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#volta
```

  Preuve: nixpkgs package indexes: pkgs/by-name/vo/volta/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

### Windows

- Chocolatey (92%):

```sh
choco install volta
```

  Preuve: Chocolatey community package catalog: volta from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','visualstudio2022enterprise'

- Scoop (92%):

```sh
scoop install main/volta
```

  Preuve: Scoop official bucket manifest trees: bucket/volta.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

- winget (92%):

```sh
winget install --id Volta.Volta -e
```

  Preuve: Windows Package Manager source index: Volta.Volta from https://cdn.winget.microsoft.com/cache/source.msix

## Faits du paquet

- **Clé du paquet:** brew:volta
- **Gestionnaire de paquets:** Homebrew
- **Version:** 2.0.2
- **Résumé source:** JavaScript toolchain manager for reproducible environments
- **Page d'accueil:** <https://volta.sh>
- **Dépôt:** <https://github.com/volta-cli/volta>
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- volta (alias)
- volta-migrate (alias)
- volta-shim (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 2.0.2
## Historique du projet et usages

Volta is a Rust-built JavaScript toolchain manager whose central idea is to make Node.js, npm, Yarn, and package binaries project-aware through fast shims. Instead of asking developers to manually switch Node versions, it records tool choices in `package.json` and routes commands to the right cached executable.

### Historique du projet

Volta began publicly as a project called Notion. Its v0.1.0 pre-release, published on August 21, 2018, supported macOS and Linux, Node and Yarn installation, `notion use`, and a proof-of-concept plugin API. The release history shows the project adding npm/npx support, package-binary installation, fish support, a `which` command, and other toolchain-manager features during the 0.x line.

The project renamed to Volta in version 0.5.0, changing the `package.json` key from `toolchain` to `volta` and adopting the JavaScript Launcher branding. Version 1.0.0 was released on December 21, 2020 with support for `npm link`, global update commands, and npm/Yarn handling improvements.

By 2025, the repository README and pinned issue stated that Volta was unmaintained and that maintainers recommended migrating to mise. That status does not erase Volta's earlier role, but it changes its package-history context from active toolchain bet to a stable-but-maintenance-limited utility.

### Historique d'adoption

Volta gained traction among JavaScript developers as an alternative to shell-function based version switchers such as nvm because its shims work across projects and shells and because pinned versions live in a file already committed by most Node projects. Its GitHub repository shows broad open-source adoption, with thousands of stars and packaging across macOS, Linux, and Windows ecosystems.

Its documentation emphasizes reproducible collaborator environments: `volta pin node@20` writes the selected engine into `package.json`, and collaborators who install Volta automatically get the same Node version when they enter the project directory. This made Volta part of the broader shift toward checking toolchain versions into application repositories.

### Modes d'utilisation

Typical use starts with `volta install node` or `volta install node@22` to set a default Node runtime. Inside a project, `volta pin node@20` or a similar command records the exact runtime or package-manager version in `package.json`; later invocations of `node`, `npm`, or `yarn` are routed by Volta's shims.

Volta also manages globally installed package binaries. The docs describe installing command-line tools through npm or Yarn while Volta pins the Node version used for that tool, so a globally installed executable keeps working even when the user's default Node version changes.

### Pourquoi les passionnés de paquets s'y intéressent

Volta is package-nerd significant because it treats the JavaScript runtime as package metadata. The interesting bit is not merely downloading Node; it is committing the runtime and package-manager versions beside dependencies so developer laptops, CI jobs, and cloned repos converge on the same toolchain.

Its later unmaintained status is also instructive: toolchain managers sit in the blast radius of operating systems, package registries, and runtime distribution changes, so maintenance health becomes part of the package story, not just an upstream README footnote.

### Chronologie

- 2018-08-21: v0.1.0 pre-release was published under the original Notion command naming.
- 2019: The 0.x release line added npm/npx support, package binaries, fish support, and related toolchain-manager features.
- Version 0.5.0: The project renamed to Volta and changed the `package.json` key from `toolchain` to `volta`.
- 2020-12-21: Volta v1.0.0 was released.
- 2025-11-14: A pinned GitHub issue announced that Volta was unmaintained and recommended migration to mise.

### Related projects

- nvm, asdf, fnm, mise, and Corepack occupy adjacent JavaScript or multi-runtime toolchain-management space.
- Node.js, npm, Yarn, and pnpm are the runtimes and package managers that Volta routes or pins.

### Sources

- <https://api.github.com/repos/volta-cli/volta/releases/tags/v0.1.0>
- <https://api.github.com/repos/volta-cli/volta/releases/tags/v1.0.0>
- <https://docs.volta.sh/advanced/packages>
- <https://docs.volta.sh/guide/>
- <https://docs.volta.sh/guide/understanding>
- <https://github.com/volta-cli/volta>
- <https://github.com/volta-cli/volta/blob/main/RELEASES.md>
- <https://github.com/volta-cli/volta/issues/2080>


## Notes de sécurité

infrastructure mutation or orchestration signal.

- **Risque Geiger:** orange / moyen
- infrastructure mutation or orchestration signal


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: package.json
- Windows: package.json
## Autres enregistrements de gestionnaires de paquets

- Nix - volta: normalized package name match | nixpkgs package indexes: pkgs/by-name/vo/volta/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- MacPorts - volta: normalized package name match | MacPorts ports tree: www/volta/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Chocolatey - volta: normalized package name match | Chocolatey community package catalog: volta from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','visualstudio2022enterprise'
- Scoop - main/volta: normalized package name match | Scoop official bucket manifest trees: bucket/volta.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- winget - Volta.Volta: normalized package name match | Windows Package Manager source index: Volta.Volta from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

View the package source record on GitHub. [combined/volta.yml](https://github.com/mxcl/pkgdb/blob/main/combined/volta.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
