nodejs/node
Maintainers
The Node.js project uses GitHub teams (under the nodejs/ organization) as the unit of code ownership. The .github/CODEOWNERS file maps directories to teams; the teams themselves are listed in README.md under "Current project team members".
This page is a courtesy index — when something breaks in a subsystem, this is the team to ping.
Subsystem ownership
| Subsystem | GitHub team(s) |
|---|---|
| Top-level governance / policy | @nodejs/tsc |
| Build system / build infra | @nodejs/build, @nodejs/gyp |
| GitHub Actions / CI workflows | @nodejs/actions |
| Releasers | @nodejs/releasers |
| Streams | @nodejs/streams |
| Net / TCP / UDP / DNS | @nodejs/net |
| TLS / Crypto | @nodejs/crypto |
| HTTP/1 | @nodejs/http |
| HTTP/2 | @nodejs/http2 |
| QUIC + HTTP/3 | @nodejs/quic |
| Modules / Loaders | @nodejs/loaders |
| Node-API | @nodejs/node-api |
| WASI | @nodejs/wasi |
| FFI | @nodejs/ffi |
| Bootstrap / startup | @nodejs/startup (and @nodejs/realm for Realm code) |
| V8 updates | @nodejs/v8-update |
| Inspector | @nodejs/inspector |
| Test runner | @nodejs/test_runner |
| Permission Model | @nodejs/security-wg |
| Security release | @nodejs/security-stewards |
| Single Executable Applications | @nodejs/single-executable |
| TypeScript integration | @nodejs/typescript |
| URL / URLPattern | @nodejs/url |
| SQLite | @nodejs/sqlite |
| Config (CLI options + dotenv) | @nodejs/config |
| Path | @nodejs/path |
| Userland migrations / deprecations | @nodejs/userland-migrations |
| Devcontainer | @nodejs/devcontainer |
| Performance benchmarks | @nodejs/performance |
| Web standards | @nodejs/web-standards |
Web infra (nodejs.org) |
@nodejs/web-infra |
| Dependency update tooling | @nodejs/security-wg |
The full mapping (which file globs map to which team) is in .github/CODEOWNERS. CODEOWNERS in this repo is informational — it courtesy-pings teams; it does not enforce review approvals. Approval rules are in doc/contributing/collaborator-guide.md § "Code reviews".
Recently active contributors
Top contributors over the last 6 months (excluding bots) by commit count:
- Antoine du Hamel
- Joyee Cheung
- Filip Skokan
- Chengzhong Wu
- Michaël Zasso
- René
- Matteo Collina
- Richard Lau
- Marco Ippolito
The full list of currently-active Collaborators and the TSC roster lives in README.md under "Current project team members". Working-group rosters live in their respective repositories under https://github.com/nodejs/<wg-name>.
Pinging the right team
- Open the relevant pull request, then look at the auto-pings made by the GitHub-bot driven from
CODEOWNERS. - For non-PR questions, the OpenJS Foundation Slack (
#nodejs-core,#nodejs-build,#nodejs-platform-build,#nodejs-tsc) is faster than the issue tracker. - For security issues, follow
SECURITY.mdand emailsecurity@nodejs.org. Do not open a public issue.
Becoming a Collaborator
The criteria are documented in doc/contributing/collaborator-guide.md and onboarding.md. The short version: a sustained track record of high-quality PRs and reviews, demonstrated good judgement on the kind of trade-offs Node's users care about, and a TSC nomination.
Built by Factory AutoWiki from public repository content. It is a generated preview for codebase exploration, not source-maintained documentation.