pkg.soopen package index

brew / Rang 2291

nodebrew mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install nodebrew

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Node.js version manager

Befehle und Aliase

  • nodebrew

Verlauf

Projektgeschichte und Nutzung

`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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:version manager

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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

Installierte Executables

BefehlArtSichtbarkeitHinweis
nodebrewcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-09-19
Manager-Version1.2.0
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.2.0

https://github.com/hokaccha/nodebrew

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:nodebrew
Version1.2.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/nodebrew
Homepagehttps://github.com/hokaccha/nodebrew
Repositoryhttps://github.com/hokaccha/nodebrew
LizenzMIT
Quellarchivhttps://github.com/hokaccha/nodebrew/archive/refs/tags/v1.2.0.tar.gz
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert
EinschränkungenYou 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-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namenodebrew
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • 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