# Install node with Homebrew

Open-source, cross-platform JavaScript runtime environment. Version 26.5.1 via Homebrew; verified 2026-07-31.

## Install

```sh
sudo av install brew:node
```

## Agent safety answer

node executes JavaScript tooling that commonly reads project secrets and launches npm package workflows.

- **Credential access:** Reads environment variables, dotenv files, npm tokens, and project config reachable to scripts.
- **Remote mutation:** Can run deploy scripts, API clients, and arbitrary package scripts.
- **Publish/artifact risk:** Can build and publish npm packages or generated application bundles.
- **Recommended control:** Gate package publishing and lifecycle scripts; scan project secrets before agent runs.
- **Agent-use guidance:** Allow test/build commands after scanning; require approval for publish, install scripts, and deploy actions.

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install node
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:node
- **Package manager:** Homebrew
- **Version:** 26.5.1
- **Source summary:** Open-source, cross-platform JavaScript runtime environment
- **Homepage:** <https://nodejs.org/>
- **Repository:** <https://github.com/nodejs/node>
- **Last updated:** 2026-07-31T17:47:51Z
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- node (alias)
- npm (alias)
- npx (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 26.5.1
## Project history and usage

Node.js is the JavaScript runtime that made server-side and command-line JavaScript mainstream. The official Node.js about page describes it as an asynchronous event-driven runtime designed for scalable network applications, with HTTP as a first-class feature and an event loop hidden behind ordinary JavaScript program execution.

### Project history

Ryan Dahl created Node.js around 2009 to run JavaScript outside the browser for network servers and other I/O-heavy programs. The runtime combined Google's V8 JavaScript engine with an event loop and low-level I/O APIs, giving web developers a single language across browser code, servers, tooling, and package scripts.

The early project was stewarded by Joyent, then hit a governance crisis in 2014 when prominent contributors forked it as io.js. The Node.js Foundation announced on 14 September 2015 that Node.js v4.0.0 combined the Node.js and io.js codebases under the foundation, added a long-term support plan, and moved the project to regular semver-based release lines.

The Node.js Foundation and JS Foundation announced their merger into the OpenJS Foundation on 12 March 2019. That put Node.js under the broader vendor-neutral JavaScript foundation that also houses projects such as Node-RED.

### Adoption history

Node.js adoption grew because it solved several developer and operational needs at once: fast startup for scripts, non-blocking network servers, JSON-native APIs, a giant npm ecosystem, and one language for browser and server teams. The 2015 foundation announcement said Node.js was used by tens of thousands of organizations in more than 200 countries and had more than 2 million downloads per month.

Homebrew's `node` formula is the rolling mainstream macOS/Linux package for the latest Node major. The Formulae page lists aliases including `node.js`, `node@26`, `nodejs`, and `npm`, and reports 3,116,013 installs over 365 days with 2,515,719 installs on request. Within Homebrew, that makes it the high-volume default path for developers who want Node, npm, and npx without a separate version manager.

### How it is used

Homebrew users install the rolling formula with `brew install node`, then get `node`, `npm`, and `npx`. The formula is convenient for system-level CLI tools, local development, and build dependencies, while teams that need exact per-project versions often layer nvm, fnm, asdf, volta, nodenv, or Homebrew's versioned `node@` formulas on top of that ecosystem.

Package nerds care about Node's release train because C++ addons, ESM/CommonJS behavior, OpenSSL, V8, npm, Corepack, test runner behavior, and web-platform APIs can all change across majors. The official release page explains that major versions historically enter Current for six months, even-numbered releases become LTS, and production applications should use Active LTS or Maintenance LTS releases.

### Why package nerds care

For package-manager data, `brew:node` is the anchor package. It is both a runtime and a build input for huge parts of the JavaScript, frontend, Electron, language-server, and CLI-tooling worlds. Its adoption stats often reflect not only developers explicitly wanting Node, but also downstream packages whose builds or runtime scripts need Node available.

### Timeline

- 2009: Ryan Dahl creates Node.js and presents the early runtime publicly.
- 2014: io.js fork forms during the Node.js governance dispute.
- 2015-09-14: Node.js v4.0.0 reunifies Node.js and io.js under the Node.js Foundation and introduces the modern LTS direction.
- 2019-03-12: Node.js Foundation and JS Foundation announce the OpenJS Foundation merger.
- 2026: Homebrew's rolling `node` formula tracks Node 26.x and lists node@24, node@22, node@20, and node@18 as adjacent versioned formulas.

### Related projects

- npm
- npx
- Corepack
- V8
- libuv
- OpenJS Foundation
- io.js

### Sources

- <https://formulae.brew.sh/formula/node>
- <https://nodejs.org/en/about>
- <https://nodejs.org/en/about/previous-releases>
- <https://nodejs.org/en/blog/announcements/foundation-v4-announce>
- <https://www.linuxfoundation.org/press/press-release/node-js-foundation-and-js-foundation-merge-to-form-openjs-foundation>
- <https://www.wired.com/2015/02/nodejs-foundation>


## Security Notes

doc example: JavaScript runtime and package ecosystem.

- **Geiger risk:** yellow / high
- doc example: JavaScript runtime and package ecosystem
- **Approval gate rules:** 7


## 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: ~/.npmrc
- Windows: %UserProfile%\.npmrc

## Credential files

- Unix: ~/.npmrc
- Windows: %UserProfile%\.npmrc

## Combined YAML source

View the package source record on GitHub. [combined/node.yml](https://github.com/automic-vault/db/blob/main/combined/node.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- approval-gate seed metadata
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- curated agent safety answer