Node.js JavaScript runtime 🐢🚀
JavaScript C++ C POV-Ray SDL HTML Python Other
Switch branches/tags
Pull request Compare This branch is 2309 commits behind nodejs:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


![Gitter]( Chat.svg) CII Best Practices

Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient. The Node.js package ecosystem, npm, is the largest ecosystem of open source libraries in the world.

The Node.js project is supported by the Node.js Foundation. Contributions, policies, and releases are managed under an open governance model. We are also bound by a Code of Conduct.

If you need help using or installing Node.js, please use the nodejs/help issue tracker.

Resources for Newcomers

Official Resources

Unofficial Resources

Please note that unofficial resources are neither managed by (nor necessarily endorsed by) the Node.js TSC/CTC. Specifically, such resources are not currently covered by the Node.js Moderation Policy and the selection and actions of resource operators/moderators are not subject to TSC/CTC oversight.

Release Types

The Node.js project maintains multiple types of releases:

  • Current: Released from active development branches of this repository, versioned by SemVer and signed by a member of the Release Team. Code for Current releases is organized in this repository by major version number. For example: v4.x. The major version number of Current releases will increment every 6 months allowing for breaking changes to be introduced. This happens in April and October every year. Current release lines beginning in October each year have a maximum support life of 8 months. Current release lines beginning in April each year will convert to LTS (see below) after 6 months and receive further support for 30 months.
  • LTS: Releases that receive Long-term Support, with a focus on stability and security. Every second Current release line (major version) will become an LTS line and receive 18 months of Active LTS support and a further 12 months of Maintenance. LTS release lines are given alphabetically ordered codenames, beginning with v4 Argon. LTS releases are less frequent and will attempt to maintain consistent major and minor version numbers, only incrementing patch version numbers. There are no breaking changes or feature additions, except in some special circumstances. More information can be found in the LTS README.
  • Nightly: Versions of code in this repository on the current Current branch, automatically built every 24-hours where changes exist. Use with caution.


Binaries, installers, and source tarballs are available at

Current and LTS releases are available at, listed under their version strings. The latest directory is an alias for the latest Current release. The latest LTS release from an LTS line is available in the form: latest-codename. For example:

Nightly builds are available at, listed under their version string which includes their date (in UTC time) and the commit SHA at the HEAD of the release.

API documentation is available in each release and nightly directory under docs. points to the API documentation of the latest stable version.

Verifying Binaries

Current, LTS and Nightly download directories all contain a SHASUM256.txt file that lists the SHA checksums for each file available for download.

The SHASUM256.txt can be downloaded using curl.

$ curl -O

To check that a downloaded file matches the checksum, run it through sha256sum with a command such as:

$ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -

(Where "node-vx.y.z.tar.gz" is the name of the file you have downloaded)

Additionally, Current and LTS releases (not Nightlies) have GPG signed copies of SHASUM256.txt files available as SHASUM256.txt.asc. You can use gpg to verify that the file has not been tampered with.

To verify a SHASUM256.txt.asc, you will first need to import all of the GPG keys of individuals authorized to create releases. They are listed at the bottom of this README under Release Team. Use a command such as this to import the keys:

$ gpg --keyserver --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D

(See the bottom of this README for a full script to import active release keys)

You can then use gpg --verify SHASUMS256.txt.asc to verify that the file has been signed by an authorized member of the Node.js team.

Once verified, use the SHASUMS256.txt.asc file to get the checksum for the binary verification command above.

Building Node.js

See for instructions on how to build Node.js from source.


All security bugs in Node.js are taken seriously and should be reported by emailing This will be delivered to a subset of the project team who handle security issues. Please don't disclose security bugs publicly until they have been handled by the security team.

Your email will be acknowledged within 24 hours, and you’ll receive a more detailed response to your email within 48 hours indicating the next steps in handling your report.

Current Project Team Members

The Node.js project team comprises a group of core collaborators and a sub-group that forms the Core Technical Committee (CTC) which governs the project. For more information about the governance of the Node.js project, see

CTC (Core Technical Committee)


Collaborators (which includes CTC members) follow the in maintaining the Node.js project.

Release Team

Releases of Node.js and io.js will be signed with one of the following GPG keys:

The full set of trusted release keys can be imported by running:

gpg --keyserver --recv-keys 9554F04D7259F04124DE6B476D5A82AC7E37093B
gpg --keyserver --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
gpg --keyserver --recv-keys FD3A5288F042B6850C66B31F09FE44734EB7990E
gpg --keyserver --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
gpg --keyserver --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
gpg --keyserver --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
gpg --keyserver --recv-keys B9AE9905FFD7803F25714661B63B535A4C206CA9

See the section above on Verifying Binaries for details on what to do with these keys to verify that a downloaded file is official.

Previous releases of Node.js have been signed with one of the following GPG keys:

  • Isaac Z. Schlueter <> 93C7E9E91B49E432C2F75674B0A78B0A6C481CF6
  • Julien Gilli <> 114F43EE0176B71C7BC219DD50A3051F888C628D
  • Timothy J Fontaine <> 7937DFD2AB06298B2293C3187D33FF9D0246406D