# nave mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für nave in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:nave
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install nave
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:nave
- **Paketmanager:** Homebrew
- **Version:** 3.5.6
- **Quellzusammenfassung:** Virtual environments for Node.js
- **Homepage:** <https://github.com/isaacs/nave>
- **Repository:** <https://github.com/isaacs/nave>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- nave (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 3.5.6
## Projektgeschichte und Nutzung

nave is Isaac Z. Schlueter's shell-based Node.js version and environment switcher. Its signature idea is to put a chosen Node version and its global npm install space into a subshell, so leaving the shell exits the environment.

### Projektgeschichte

The GitHub repository was created on 2010-05-14, placing nave in the early Node.js tooling era when developers were still sorting out how to install and switch between Node versions. The README emphasizes that nave can be installed as a single shell script, symlinked, installed with npm, or run without editing shell startup files.

### Adoptionsgeschichte

nave had real early-ecosystem visibility, helped by Isaac Schlueter's central role in npm and Node tooling, but it became a smaller niche as tools such as nvm, n, asdf, fnm, and Volta absorbed most mainstream version-manager usage. Homebrew analytics consulted on 2026-07-01 listed 59 installs over the preceding 365 days, suggesting maintenance and legacy use rather than broad new adoption.

### Wie es verwendet wird

Typical use is `nave use <version>` to enter a subshell, `nave use <name> <version>` for a named environment, `nave install <version>` to install a Node version, and `nave auto` to find a `.naverc` or `.nvmrc` and enter the configured environment. The README documents project-specific profile hooks and environment variables such as `NAVE`, `NAVENAME`, and `NAVEVERSION`.

### Warum Paket-Nerds sich dafür interessieren

nave is package-nerd history from the pre-standardized Node toolchain era: a small shell program that treats version management as disposable process state rather than a permanent mutation of the user's login shell.

### Zeitleiste

- 2010-05-14: GitHub repository created.
- 2010s: nave served as one of the early Node version/environment managers alongside nvm and n.
- 2026-01-23: Repository metadata showed new commits pushed in 2026, while Homebrew packaged stable version 3.5.6.

### Related projects

- nvm, n, nodeenv, asdf-nodejs, fnm, Volta, npm, and Node.js distribution archives are the main related tools.

### Quellen

- <https://api.github.com/repos/isaacs/nave>
- <https://formulae.brew.sh/formula/nave>
- <https://github.com/isaacs/nave>
- <https://github.com/isaacs/nave/tags>
- <https://stackoverflow.com/questions/3653495/is-there-a-virtual-environment-for-node-js>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Combined YAML source

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


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph