Nodejs/node
1
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-21 10:59:27 +00:00
Code Issues Actions 25 Packages Projects Releases Wiki Activity
Node.js JavaScript runtime ✨🐢🚀✨
23,879 Commits 48 Branches 857 Tags 1.8 GiB
JavaScript 61.7%
C++ 22.7%
Python 10.9%
C 3%
HTML 0.7%
Other 0.9%
9577946bed
Go to file
Matteo Collina 9577946bed test: add process.stdin.end() TTY regression test 
PR-URL: https://github.com/nodejs/node/pull/23051
Fixes: https://github.com/nodejs/node/issues/22814
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: George Adams <george.adams@uk.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
2018-10-04 05:31:46 +02:00
.github doc: add multiple issue templates for GitHub 2018-08-12 10:18:40 -07:00
benchmark benchmark: refactor util benchmarks 2018-09-07 19:58:36 +02:00
deps deps: patch V8 to 7.0.276.22 2018-10-02 11:08:07 +02:00
doc util: change %o depth default 2018-10-02 22:43:10 +02:00
lib src: use JS inheritance for AsyncWrap 2018-10-03 13:43:42 -07:00
src src: remove public API for option variables 2018-10-03 14:08:06 -07:00
test test: add process.stdin.end() TTY regression test 2018-10-04 05:31:46 +02:00
tools tools,gyp: don't force build actions with multiple outputs 2018-10-02 17:53:14 -04:00
.clang-format
.editorconfig tools: unify .editorconfig rules for 2-space 2018-10-01 18:43:55 +02:00
.eslintignore tools: use lint-md.js 2018-09-11 14:12:30 -04:00
.eslintrc.js tools: .eslintrc.js messages "default" typo style 2018-09-24 22:50:53 +02:00
.gitattributes
.gitignore tools: use lint-md.js 2018-09-11 14:12:30 -04:00
.mailmap doc: update AUTHORS list 2018-09-14 18:58:47 +02:00
.nycrc
.travis.yml build,doc: remove outdated lint-md-build 2018-09-22 15:48:15 +02:00
android-configure
AUTHORS doc: update AUTHORS list 2018-09-14 18:58:47 +02:00
BSDmakefile
BUILDING.md doc: add table of contents in BUILDING.md 2018-09-29 13:20:05 +03:00
CHANGELOG.md 2018-09-20, Version 10.11.0 (Current) 2018-09-20 13:32:38 +02:00
CODE_OF_CONDUCT.md
COLLABORATOR_GUIDE.md doc: clarify assigning issues to the TSC 2018-10-03 10:32:27 -07:00
common.gypi build: reduce chance of unneeded rebuild 2018-10-02 17:53:14 -04:00
configure build: move meta-shebang back to configure 2018-09-07 10:17:52 -04:00
configure.py src: deprecate global COUNTER_* and remove perfctr 2018-09-19 11:07:01 +02:00
CONTRIBUTING.md doc: add contents table to CONTRIBUTING.md 2018-10-01 09:16:57 -07:00
CPP_STYLE_GUIDE.md doc: formalize auto usage in C++ style guide 2018-09-30 11:31:52 -04:00
GOVERNANCE.md doc: require two approvals to land changes 2018-09-24 22:14:55 -07:00
LICENSE tools: use lint-md.js 2018-09-11 14:12:30 -04:00
Makefile build: reduce chance of unneeded rebuild 2018-10-02 17:53:14 -04:00
node.gyp src: use JS inheritance for AsyncWrap 2018-10-03 13:43:42 -07:00
node.gypi build: reduce chance of unneeded rebuild 2018-10-02 17:53:14 -04:00
README.md doc: move gibfahn to TSC Emeritus 2018-10-03 10:36:36 -07:00
vcbuild.bat build: exclude npm test directories on Windows 2018-10-02 13:19:49 -04:00

README.md

Node.js

Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. For more information on using Node.js, see the Node.js Website.

The Node.js project is supported by the Node.js Foundation. Contributions, policies, and releases are managed under an open governance model.

This project is bound by a Code of Conduct.

Table of Contents

Support

Node.js contributors have limited availability to address general support questions. Please make sure you are using a currently-supported version of Node.js.

When looking for support, please first search for your question in these venues:

If you didn't find an answer in the resources above, try these unofficial resources:

GitHub issues are for tracking enhancements and bugs, not general support.

The open source license grants you the freedom to use Node.js. It does not guarantee commitments of other people's time. Please be respectful and manage your expectations.

Release Types

  • Current: Under active development. Code for the Current release is in the branch for its major version number (for example, v10.x). Node.js releases a new major version every 6 months, allowing for breaking changes. This happens in April and October every year. Releases appearing each October have a support life of 8 months. Releases appearing each April convert to LTS (see below) each October.
  • LTS: Releases that receive Long-term Support, with a focus on stability and security. Every even-numbered major version will become an LTS release. LTS releases receive 18 months of Active LTS support and a further 12 months of Maintenance. LTS release lines have alphabetically-ordered codenames, beginning with v4 Argon. There are no breaking changes or feature additions, except in some special circumstances.
  • Nightly: Code from the Current branch built every 24-hours when there are changes. Use with caution.

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

Current and LTS releases are available at https://nodejs.org/download/release/, 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: https://nodejs.org/download/release/latest-argon.

Nightly Releases

Nightly builds are available at https://nodejs.org/download/nightly/, listed under their version string which includes their date (in UTC time) and the commit SHA at the HEAD of the release.

API Documentation

API documentation is available in each release and nightly directory under docs. https://nodejs.org/api/ points to the API documentation of the latest stable version.

Verifying Binaries

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

The SHASUMS256.txt can be downloaded using curl.

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

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 -

Current and LTS releases (but not Nightlies) also have the GPG detached signature of SHASUMS256.txt available as SHASUMS256.txt.sig. You can use gpg to verify that SHASUMS256.txt has not been tampered with.

To verify SHASUMS256.txt has not been altered, 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 pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D

See the bottom of this README for a full script 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

After downloading the appropriate SHASUMS256.txt and SHASUMS256.txt.sig files, you can then use gpg --verify SHASUMS256.txt.sig SHASUMS256.txt to verify that the file has been signed by an authorized member of the Node.js team.

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

Building Node.js

See BUILDING.md for instructions on how to build Node.js from source. The document also contains a list of officially supported platforms.

Security

Security flaws in Node.js should be reported by emailing security@nodejs.org. Please do not disclose security bugs publicly until they have been handled by the security team.

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

There are no hard and fast rules to determine if a bug is worth reporting as a security issue. The general rule is an issue worth reporting should allow an attacker to compromise the confidentiality, integrity, or availability of the Node.js application or its system for which the attacker does not already have the capability.

To illustrate the point, here are some examples of past issues and what the Security Response Team thinks of them. When in doubt, however, please do send us a report nonetheless.

Public disclosure preferred

  • #14519: Internal domain function can be used to cause segfaults. Causing program termination using either the public JavaScript APIs or the private bindings layer APIs requires the ability to execute arbitrary JavaScript code, which is already the highest level of privilege possible.

  • #12141: buffer: zero fill Buffer(num) by default. The buffer constructor behavior was documented, but found to be prone to mis-use. It has since been changed, but despite much debate, was not considered misuse prone enough to justify fixing in older release lines and breaking our API stability contract.

Private disclosure preferred

  • CVE-2016-7099: Fix invalid wildcard certificate validation check. This is a high severity defect that would allow a malicious TLS server to serve an invalid wildcard certificate for its hostname and be improperly validated by a Node.js client.

  • #5507: Fix a defect that makes the CacheBleed Attack possible. Many, though not all, OpenSSL vulnerabilities in the TLS/SSL protocols also affect Node.js.

  • CVE-2016-2216: Fix defects in HTTP header parsing for requests and responses that can allow response splitting. While the impact of this vulnerability is application and network dependent, it is remotely exploitable in the HTTP protocol.

When in doubt, please do send us a report.

Current Project Team Members

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

TSC (Technical Steering Committee)

  • addaleax - Anna Henningsen <anna@addaleax.net> (she/her)
  • apapirovski - Anatoli Papirovski <apapirovski@mac.com> (he/him)
  • ChALkeR - Сковорода Никита Андреевич <chalkerx@gmail.com> (he/him)
  • cjihrig - Colin Ihrig <cjihrig@gmail.com> (he/him)
  • danbev - Daniel Bevenius <daniel.bevenius@gmail.com> (he/him)
  • fhinkel - Franziska Hinkelmann <franziska.hinkelmann@gmail.com> (she/her)
  • Fishrock123 - Jeremiah Senkpiel <fishrock123@rocketmail.com>
  • gabrielschulhof - Gabriel Schulhof <gabriel.schulhof@intel.com>
  • jasnell - James M Snell <jasnell@gmail.com> (he/him)
  • joyeecheung - Joyee Cheung <joyeec9h3@gmail.com> (she/her)
  • mcollina - Matteo Collina <matteo.collina@gmail.com> (he/him)
  • mhdawson - Michael Dawson <michael_dawson@ca.ibm.com> (he/him)
  • MylesBorins - Myles Borins <myles.borins@gmail.com> (he/him)
  • ofrobots - Ali Ijaz Sheikh <ofrobots@google.com> (he/him)
  • rvagg - Rod Vagg <rod@vagg.org>
  • targos - Michaël Zasso <targos@protonmail.com> (he/him)
  • thefourtheye - Sakthipriyan Vairamani <thechargingvolcano@gmail.com> (he/him)
  • TimothyGu - Tiancheng "Timothy" Gu <timothygu99@gmail.com> (he/him)
  • Trott - Rich Trott <rtrott@gmail.com> (he/him)

TSC Emeriti

  • bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
  • chrisdickinson - Chris Dickinson <christopher.s.dickinson@gmail.com>
  • evanlucas - Evan Lucas <evanlucas@me.com> (he/him)
  • gibfahn - Gibson Fahnestock <gibfahn@gmail.com> (he/him)
  • indutny - Fedor Indutny <fedor.indutny@gmail.com>
  • isaacs - Isaac Z. Schlueter <i@izs.me>
  • joshgav - Josh Gavant <josh.gavant@outlook.com>
  • mscdex - Brian White <mscdex@mscdex.net>
  • nebrius - Bryan Hughes <bryan@nebri.us>
  • orangemocha - Alexis Campailla <orangemocha@nodejs.org>
  • piscisaureus - Bert Belder <bertbelder@gmail.com>
  • shigeki - Shigeki Ohtsu <ohtsu@ohtsu.org> (he/him)
  • trevnorris - Trevor Norris <trev.norris@gmail.com>

Collaborators

  • addaleax - Anna Henningsen <anna@addaleax.net> (she/her)
  • ak239 - Aleksei Koziatinskii <ak239spb@gmail.com>
  • andrasq - Andras <andras@kinvey.com>
  • AndreasMadsen - Andreas Madsen <amwebdk@gmail.com> (he/him)
  • AnnaMag - Anna M. Kedzierska <anna.m.kedzierska@gmail.com>
  • apapirovski - Anatoli Papirovski <apapirovski@mac.com> (he/him)
  • aqrln - Alexey Orlenko <eaglexrlnk@gmail.com> (he/him)
  • bcoe - Ben Coe <bencoe@gmail.com> (he/him)
  • bengl - Bryan English <bryan@bryanenglish.com> (he/him)
  • benjamingr - Benjamin Gruenbaum <benjamingr@gmail.com>
  • BethGriggs - Beth Griggs <Bethany.Griggs@uk.ibm.com> (she/her)
  • bmeck - Bradley Farias <bradley.meck@gmail.com>
  • bmeurer - Benedikt Meurer <benedikt.meurer@gmail.com>
  • bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
  • boneskull - Christopher Hiller <boneskull@boneskull.com> (he/him)
  • brendanashworth - Brendan Ashworth <brendan.ashworth@me.com>
  • BridgeAR - Ruben Bridgewater <ruben@bridgewater.de> (he/him)
  • bzoz - Bartosz Sosnowski <bartosz@janeasystems.com>
  • calvinmetcalf - Calvin Metcalf <calvin.metcalf@gmail.com>
  • ChALkeR - Сковорода Никита Андреевич <chalkerx@gmail.com> (he/him)
  • chrisdickinson - Chris Dickinson <christopher.s.dickinson@gmail.com>
  • cjihrig - Colin Ihrig <cjihrig@gmail.com> (he/him)
  • claudiorodriguez - Claudio Rodriguez <cjrodr@yahoo.com>
  • codebytere - Shelley Vohr <codebytere@gmail.com> (she/her)
  • danbev - Daniel Bevenius <daniel.bevenius@gmail.com> (he/him)
  • DavidCai1993 - David Cai <davidcai1993@yahoo.com> (he/him)
  • davisjam - Jamie Davis <davisjam@vt.edu> (he/him)
  • devsnek - Gus Caplan <me@gus.host> (he/him)
  • digitalinfinity - Hitesh Kanwathirtha <digitalinfinity@gmail.com> (he/him)
  • edsadr - Adrian Estrada <edsadr@gmail.com> (he/him)
  • eljefedelrodeodeljefe - Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com>
  • estliberitas - Alexander Makarenko <estliberitas@gmail.com>
  • eugeneo - Eugene Ostroukhov <eostroukhov@google.com>
  • evanlucas - Evan Lucas <evanlucas@me.com> (he/him)
  • fhinkel - Franziska Hinkelmann <franziska.hinkelmann@gmail.com> (she/her)
  • firedfox - Daniel Wang <wangyang0123@gmail.com>
  • Fishrock123 - Jeremiah Senkpiel <fishrock123@rocketmail.com>
  • gabrielschulhof - Gabriel Schulhof <gabriel.schulhof@intel.com>
  • gdams - George Adams <george.adams@uk.ibm.com> (he/him)
  • geek - Wyatt Preul <wpreul@gmail.com>
  • gibfahn - Gibson Fahnestock <gibfahn@gmail.com> (he/him)
  • gireeshpunathil - Gireesh Punathil <gpunathi@in.ibm.com> (he/him)
  • guybedford - Guy Bedford <guybedford@gmail.com> (he/him)
  • hashseed - Yang Guo <yangguo@chromium.org> (he/him)
  • hiroppy - Yuta Hiroto <hello@hiroppy.me> (he/him)
  • iarna - Rebecca Turner <me@re-becca.org>
  • imyller - Ilkka Myller <ilkka.myller@nodefield.com>
  • indutny - Fedor Indutny <fedor.indutny@gmail.com>
  • italoacasas - Italo A. Casas <me@italoacasas.com> (he/him)
  • JacksonTian - Jackson Tian <shyvo1987@gmail.com>
  • jasnell - James M Snell <jasnell@gmail.com> (he/him)
  • jasongin - Jason Ginchereau <jasongin@microsoft.com>
  • jbergstroem - Johan Bergström <bugs@bergstroem.nu>
  • jdalton - John-David Dalton <john.david.dalton@gmail.com>
  • jhamhader - Yuval Brik <yuval@brik.org.il>
  • jkrems - Jan Krems <jan.krems@gmail.com> (he/him)
  • joaocgreis - João Reis <reis@janeasystems.com>
  • joshgav - Josh Gavant <josh.gavant@outlook.com>
  • joyeecheung - Joyee Cheung <joyeec9h3@gmail.com> (she/her)
  • julianduque - Julian Duque <julianduquej@gmail.com> (he/him)
  • JungMinu - Minwoo Jung <minwoo@nodesource.com> (he/him)
  • kfarnung - Kyle Farnung <kfarnung@microsoft.com> (he/him)
  • kunalspathak - Kunal Pathak <kunal.pathak@microsoft.com>
  • lance - Lance Ball <lball@redhat.com> (he/him)
  • Leko - Shingo Inoue <leko.noor@gmail.com> (he/him)
  • lpinca - Luigi Pinca <luigipinca@gmail.com> (he/him)
  • lucamaraschi - Luca Maraschi <luca.maraschi@gmail.com> (he/him)
  • lundibundi - Denys Otrishko <shishugi@gmail.com> (he/him)
  • maclover7 - Jon Moss <me@jonathanmoss.me> (he/him)
  • mafintosh Mathias Buus <mathiasbuus@gmail.com> (he/him)
  • mcollina - Matteo Collina <matteo.collina@gmail.com> (he/him)
  • mhdawson - Michael Dawson <michael_dawson@ca.ibm.com> (he/him)
  • misterdjules - Julien Gilli <jgilli@nodejs.org>
  • mmarchini - Matheus Marchini <mat@mmarchini.me>
  • MoonBall - Chen Gang <gangc.cxy@foxmail.com>
  • mscdex - Brian White <mscdex@mscdex.net>
  • MylesBorins - Myles Borins <myles.borins@gmail.com> (he/him)
  • not-an-aardvark - Teddy Katz <teddy.katz@gmail.com> (he/him)
  • ofrobots - Ali Ijaz Sheikh <ofrobots@google.com> (he/him)
  • orangemocha - Alexis Campailla <orangemocha@nodejs.org>
  • othiym23 - Forrest L Norvell <ogd@aoaioxxysz.net> (he/him)
  • phillipj - Phillip Johnsen <johphi@gmail.com>
  • pmq20 - Minqi Pan <pmq2001@gmail.com>
  • princejwesley - Prince John Wesley <princejohnwesley@gmail.com>
  • Qard - Stephen Belanger <admin@stephenbelanger.com> (he/him)
  • refack - Refael Ackermann <refack@gmail.com> (he/him)
  • richardlau - Richard Lau <riclau@uk.ibm.com>
  • ronkorving - Ron Korving <ron@ronkorving.nl>
  • RReverser - Ingvar Stepanyan <me@rreverser.com>
  • rubys - Sam Ruby <rubys@intertwingly.net>
  • rvagg - Rod Vagg <rod@vagg.org>
  • ryzokuken - Ujjwal Sharma <usharma1998@gmail.com> (he/him)
  • saghul - Saúl Ibarra Corretgé <saghul@gmail.com>
  • sam-github - Sam Roberts <vieuxtech@gmail.com>
  • santigimeno - Santiago Gimeno <santiago.gimeno@gmail.com>
  • sebdeckers - Sebastiaan Deckers <sebdeckers83@gmail.com>
  • seishun - Nikolai Vavilov <vvnicholas@gmail.com>
  • shigeki - Shigeki Ohtsu <ohtsu@ohtsu.org> (he/him)
  • silverwind - Roman Reiss <me@silverwind.io>
  • srl295 - Steven R Loomis <srloomis@us.ibm.com>
  • starkwang - Weijia Wang <starkwang@126.com>
  • stefanmb - Stefan Budeanu <stefan@budeanu.com>
  • targos - Michaël Zasso <targos@protonmail.com> (he/him)
  • thefourtheye - Sakthipriyan Vairamani <thechargingvolcano@gmail.com> (he/him)
  • thekemkid - Glen Keane <glenkeane.94@gmail.com> (he/him)
  • thlorenz - Thorsten Lorenz <thlorenz@gmx.de>
  • TimothyGu - Tiancheng "Timothy" Gu <timothygu99@gmail.com> (he/him)
  • tniessen - Tobias Nießen <tniessen@tnie.de>
  • trevnorris - Trevor Norris <trev.norris@gmail.com>
  • trivikr - Trivikram Kamat <trivikr.dev@gmail.com>
  • Trott - Rich Trott <rtrott@gmail.com> (he/him)
  • vdeturckheim - Vladimir de Turckheim <vlad2t@hotmail.com> (he/him)
  • vkurchatkin - Vladimir Kurchatkin <vladimir.kurchatkin@gmail.com>
  • vsemozhetbyt - Vse Mozhet Byt <vsemozhetbyt@gmail.com> (he/him)
  • watilde - Daijiro Wachi <daijiro.wachi@gmail.com> (he/him)
  • watson - Thomas Watson <w@tson.dk>
  • whitlockjc - Jeremy Whitlock <jwhitlock@apache.org>
  • XadillaX - Khaidi Chu <i@2333.moe> (he/him)
  • yhwang - Yihong Wang <yh.wang@ibm.com>
  • yorkie - Yorkie Liu <yorkiefixer@gmail.com>
  • yosuke-furukawa - Yosuke Furukawa <yosuke.furukawa@gmail.com>

Collaborator Emeriti

  • imran-iq - Imran Iqbal <imran@imraniqbal.org>
  • isaacs - Isaac Z. Schlueter <i@izs.me>
  • lxe - Aleksey Smolenchuk <lxe@lxe.co>
  • matthewloring - Matthew Loring <mattloring@google.com>
  • micnic - Nicu Micleușanu <micnic90@gmail.com> (he/him)
  • mikeal - Mikeal Rogers <mikeal.rogers@gmail.com>
  • monsanto - Christopher Monsanto <chris@monsan.to>
  • Olegas - Oleg Elifantiev <oleg@elifantiev.ru>
  • petkaantonov - Petka Antonov <petka_antonov@hotmail.com>
  • piscisaureus - Bert Belder <bertbelder@gmail.com>
  • rlidwka - Alex Kocharin <alex@kocharin.ru>
  • rmg - Ryan Graham <r.m.graham@gmail.com>
  • robertkowalski - Robert Kowalski <rok@kowalski.gd>
  • romankl - Roman Klauke <romaaan.git@gmail.com>
  • tellnes - Christian Tellnes <christian@tellnes.no>
  • tunniclm - Mike Tunnicliffe <m.j.tunnicliffe@gmail.com>

Collaborators follow the COLLABORATOR_GUIDE.md in maintaining the Node.js project.

Release Team

Node.js releases are signed with one of the following GPG keys:

  • Colin Ihrig <cjihrig@gmail.com> 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
  • Evan Lucas <evanlucas@me.com> B9AE9905FFD7803F25714661B63B535A4C206CA9
  • Gibson Fahnestock <gibfahn@gmail.com> 77984A986EBC2AA786BC0F66B01FBB92821C587A
  • James M Snell <jasnell@keybase.io> 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
  • Jeremiah Senkpiel <fishrock@keybase.io> FD3A5288F042B6850C66B31F09FE44734EB7990E
  • Michaël Zasso <targos@protonmail.com> 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
  • Myles Borins <myles.borins@gmail.com> C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
  • Rod Vagg <rod@vagg.org> DD8F2338BAE7501E3DD5AC78C273792F7D83545D

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

gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
gpg --keyserver pool.sks-keyservers.net --recv-keys B9AE9905FFD7803F25714661B63B535A4C206CA9
gpg --keyserver pool.sks-keyservers.net --recv-keys 77984A986EBC2AA786BC0F66B01FBB92821C587A
gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
gpg --keyserver pool.sks-keyservers.net --recv-keys FD3A5288F042B6850C66B31F09FE44734EB7990E
gpg --keyserver pool.sks-keyservers.net --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
gpg --keyserver pool.sks-keyservers.net --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D

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 may also have been signed with one of the following GPG keys:

  • Chris Dickinson <christopher.s.dickinson@gmail.com> 9554F04D7259F04124DE6B476D5A82AC7E37093B
  • Isaac Z. Schlueter <i@izs.me> 93C7E9E91B49E432C2F75674B0A78B0A6C481CF6
  • Italo A. Casas <me@italoacasas.com> 56730D5401028683275BD23C23EFEFE93C4CFFFE
  • Julien Gilli <jgilli@fastmail.fm> 114F43EE0176B71C7BC219DD50A3051F888C628D
  • Timothy J Fontaine <tjfontaine@gmail.com> 7937DFD2AB06298B2293C3187D33FF9D0246406D

Contributing to Node.js