install

Additional install commands

macOS

Homebrewverified · 100%

brew install nodebrew

local Homebrew formula metadata

overview

Package summary

Node.js version manager

Project links

Commands and aliases

nodebrew

history

Project history and usage

`nodebrew` is a Perl-based Node.js version manager by Kazuhito Hokamura. It predates many later Node version-manager workflows and keeps a simple model: download or compile Node.js versions under a per-user root, switch a `current` path, and put that path in the user's shell.

Project history

GitHub metadata shows the repository was created on 2011-11-15. The README presents a curl-to-Perl setup flow, a default root of `$HOME/.nodebrew`, and shell PATH setup using `$HOME/.nodebrew/current/bin`.

The tag history shows v1.0.0 committed on 2018-03-10, v1.1.0 on 2021-04-23, and v1.2.0 on 2022-03-19. Homebrew reported stable version 1.2.0 on 2026-07-01, matching the latest tag listed by GitHub.

Adoption history

By 2026-07-01, GitHub metadata reported 1067 stars and 66 forks. Homebrew's formula API reported 4600 installs over 365 days and 211 installs over 30 days. That places it below `nodenv` in Homebrew usage, but still visible as a long-lived Node version manager.

Its adoption story is strongest among users who prefer a small standalone version manager without the rbenv-style shim system. The README focuses on direct commands rather than project-local automatic switching.

How it is used

Typical usage is `nodebrew install <version>` to download a binary, `nodebrew compile <version>` to build from source, `nodebrew use <version>` to switch, and `nodebrew ls-remote` or `nodebrew ls-all` to inspect available and installed versions. It also supports aliases, pruning old versions, migrating global npm packages, and `nodebrew exec <version> -- <command>` for one-off execution.

The package-nerd distinction is that nodebrew changes the selected version by changing which installation is exposed through `$HOME/.nodebrew/current/bin`. That is simpler than shim dispatch but less project-automatic than `.node-version` managers.

Why package nerds care

It is a useful historical Node manager entry because it represents the single-purpose, per-user install-tree style: no plugin ecosystem, no Python virtualenv integration, and no rbenv ancestry required.

Timeline

2011-11-15: GitHub repository `hokaccha/nodebrew` was created.
2018-03-10: v1.0.0 tag commit.
2021-04-23: v1.1.0 tag commit.
2022-03-19: v1.2.0 tag commit.
2026-07-01: Homebrew formula API reported stable version 1.2.0.

Related projects

nvm
n
nodenv
nodeenv

Sources

security posture

Risk level: orange

infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

infrastructure mutation or orchestration signal

Signals

text:version manager

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 1 platform targets.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

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

Config paths the tool may read or write during local use.

Unix: ~/.bashrc~/.zshrc

executables

Installed executables

Command	Kind	Exposure	Note
`nodebrew`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-09-19

manager version1.2.0

manager updated

local dataok

upstreamcurrent

latest detectedv1.2.0

https://github.com/hokaccha/nodebrew

infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package key	brew:nodebrew
Version	1.2.0
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/nodebrew
Homepage	https://github.com/hokaccha/nodebrew
Repository	https://github.com/hokaccha/nodebrew
License	MIT
Source archive	https://github.com/hokaccha/nodebrew/archive/refs/tags/v1.2.0.tar.gz
Bottle	available (on all)
Homebrew post-install	not defined
Service	none declared
Caveats	You need to manually run setup_dirs to create directories required by nodebrew: $HOMEBREW_PREFIX/opt/nodebrew/bin/nodebrew setup_dirs Add path: export PATH=$HOME/.nodebrew/current/bin:$PATH To use Homebrew's directories rather than ~/.nodebrew add to your profile: export NODEBREW_ROOT=$HOMEBREW_PREFIX/var/nodebrew

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	nodebrew
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/nodebrew.yml

Used sources

Geiger risk classifier
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
package relationship graph
package version freshness
package-page enrichment
pkg.so package database
pkgdb category and tag curation

Install nodebrew with Homebrew