Node.js #

Node.js is an open-source, cross-platform JavaScript runtime environment.

For information on using Node.js, see the Node.js website.

The Node.js project uses an open governance model. The
OpenJS Foundation provides support for the project.

Contributors are expected to act in a collaborative manner to move
the project forward. We encourage the constructive exchange of contrary
opinions and compromise. The TSC
reserves the right to limit or block contributors who repeatedly act in ways
that discourage, exhaust, or otherwise negatively affect other participants.

This project has a Code of Conduct.

Table of contents #

Support #

Looking for help? Check out the
instructions for getting support.

Release types #

Current and LTS releases follow semantic versioning. A
member of the Release Team signs each Current and LTS release.
For more information, see the
Release README.

Download #

Binaries, installers, and source tarballs are available at
https://nodejs.org/en/download/.

Current and LTS releases #

https://nodejs.org/download/release/

The latest directory is an
alias for the latest Current release. The latest-codename directory is an
alias for the latest release from an LTS line. For example, the
latest-hydrogen
directory contains the latest Hydrogen (Node.js 18) release.

Nightly releases #

https://nodejs.org/download/nightly/

Each directory and filename includes the version (e.g., v22.0.0),
followed by the UTC date (e.g., 20240424 for April 24, 2024),
and the short commit SHA of the HEAD of the release (e.g., ddd0a9e494).
For instance, a full directory name might look like v22.0.0-nightly20240424ddd0a9e494.

API documentation #

Documentation for the latest Current release is at https://nodejs.org/api/.
Version-specific documentation is available in each release directory in the
docs subdirectory. Version-specific documentation is also at
https://nodejs.org/download/docs/.

Verifying binaries #

Download directories contain a SHASUMS256.txt file with SHA checksums for the
files.

To download SHASUMS256.txt using curl:

curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt

To check that downloaded files match the checksum, use sha256sum:

sha256sum -c SHASUMS256.txt --ignore-missing

For Current and LTS, the GPG detached signature of SHASUMS256.txt is in
SHASUMS256.txt.sig. You can use it with gpg to verify the integrity of
SHASUMS256.txt. You will first need to import
the GPG keys of individuals authorized to create releases.

See Release keys for commands to import active release keys.

Next, download the SHASUMS256.txt.sig for the release:

curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt.sig

Then use gpg --verify SHASUMS256.txt.sig SHASUMS256.txt to verify
the file's signature.

Building Node.js #

See BUILDING.md for instructions on how to build Node.js from
source and a list of supported platforms.

Security #

For information on reporting security vulnerabilities in Node.js, see
SECURITY.md.

Contributing to Node.js #

Current project team members #

For information about the governance of the Node.js project, see
GOVERNANCE.md.

TSC (Technical Steering Committee) #

TSC voting members #

TSC regular members #

TSC emeriti members

TSC emeriti members #

Collaborators #

Emeriti

Collaborator emeriti #

Collaborators follow the Collaborator Guide in
maintaining the Node.js project.

Triagers #

Triagers follow the Triage Guide when
responding to new issues.

Release keys #

Primary GPG keys for Node.js Releasers (some Releasers sign with subkeys):

To import the full set of trusted release keys (including subkeys possibly used
to sign releases):

gpg --keyserver hkps://keys.openpgp.org --recv-keys C0D6248439F1D5604AAFFB4021D900FFDB233756 # Antoine du Hamel
gpg --keyserver hkps://keys.openpgp.org --recv-keys DD792F5973C6DE52C432CBDAC77ABFA00DDBF2B7 # Juan José Arboleda
gpg --keyserver hkps://keys.openpgp.org --recv-keys CC68F5A3106FF448322E48ED27F5E38D5B0A215F # Marco Ippolito
gpg --keyserver hkps://keys.openpgp.org --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600 # Michaël Zasso
gpg --keyserver hkps://keys.openpgp.org --recv-keys 890C08DB8579162FEE0DF9DB8BEAB4DFCF555EF4 # Rafael Gonzaga
gpg --keyserver hkps://keys.openpgp.org --recv-keys C82FA3AE1CBEDC6BE46B9360C43CEC45C17AB93C # Richard Lau
gpg --keyserver hkps://keys.openpgp.org --recv-keys 108F52B48DB57BB0CC439B2997B01419BD92F80A # Ruy Adorno
gpg --keyserver hkps://keys.openpgp.org --recv-keys A363A499291CBBC940DD62E41F10027AF002F8B0 # Ulises Gascón

See Verifying binaries for how to use these keys to
verify a downloaded file.

Other keys used to sign some previous releases

Security release stewards #

When possible, the commitment to take slots in the
security release steward rotation is made by companies in order
to ensure individuals who act as security stewards have the
support and recognition from their employer to be able to
prioritize security releases. Security release stewards manage security
releases on a rotation basis as outlined in the
security release process.

License #

Node.js is available under the
MIT License. Node.js also includes
external libraries that are available under a variety of licenses. See
LICENSE for the full
license text.