Fedor Indutny, a Node.js TSC Emeritus Member, published a petition on GitHub in early 2026 calling on the Node.js Technical Steering Committee (TSC) to vote against permitting LLM-generated contributions to the project’s core codebase. The petition, available at github.com/indutny/no-ai-in-nodejs-core, had accumulated 130 stars and 93 forks on GitHub as of April 2026.
- Fedor Indutny, a Node.js TSC Emeritus Member, launched a GitHub petition asking the TSC to prohibit LLM-generated contributions to Node.js core.
- The petition was triggered by a 19,000-line pull request submitted in January 2026 by a longtime Node.js contributor who disclosed using “a significant amount of Claude Code tokens.”
- Petitioners raise concerns about code reproducibility, contributor certification processes, and the governance of a runtime used on millions of servers.
- The OpenJS Foundation’s legal team reportedly concluded LLM-assisted contributions do not violate DCO requirements — a finding the petitioners say addresses only part of the problem.
What Happened
In early 2026, Fedor Indutny published a formal petition on GitHub urging the Node.js Technical Steering Committee to reject LLM-generated contributions to the runtime’s core. The petition requests that the TSC “vote NO on ‘Is AI-assisted development allowed?’ and not accept LLM generated rewrites of core internals.” Indutny is a Node.js TSC Emeritus Member with a long history of contributions to the project.
The petition was triggered by a 19,000-line pull request opened in January 2026 by a well-known, longtime Node.js contributor, who disclosed that the work involved “a significant amount of Claude Code tokens to create this PR.” The contributor stated they personally reviewed all AI-generated changes before submission. That disclosure nonetheless opened a formal question before the TSC about whether contributions produced primarily by LLMs satisfy the project’s Developer’s Certificate of Origin (DCO) — the mechanism through which contributors certify they have the right to submit the code.
Why It Matters
Node.js is described in the petition as “critical infrastructure running on millions of servers online and supporting engineers through command-line utilities that they use daily.” The petitioners argue that accepting LLM-generated changes would “break the reputational bedrock of public contributions that have brought Node.js to its current public standing and societal value.” This frames the issue as one of project identity and contributor trust, not only technical quality.
Node.js is governed by a formal TSC structure under the OpenJS Foundation, making it one of the first major server-side runtimes to face a formal recorded vote on AI-assisted contributions. A decision here could shape how other large open-source projects with comparable governance structures approach the same question.
Technical Details
The January 2026 pull request at the center of the petition comprised approximately 19,000 lines of code — a volume that presents a substantial burden for reviewers attempting to audit changes line by line. At that scale, maintainers must evaluate not only functional correctness but also adherence to the project’s internal architecture and long-term design principles. The petitioners do not claim the pull request contained defects, but challenge whether the contribution process itself can be adequately governed when LLMs generate code at this scale.
A central technical objection concerns reproducibility. The petition states that “submitted generated code should be reproducible by reviewers without having to go through the paywall of subscription based LLM tooling.” This argument holds that when code is produced by commercially gated tools that generate non-deterministic outputs, reviewers cannot independently verify the contribution’s provenance under the same conditions as the author — a baseline expectation in open-source review workflows. The concern is separate from a claim about the code’s correctness.
Who’s Affected
The petition has drawn signatures from contributors across the Node.js and broader JavaScript ecosystem. Jan Lehnardt, CEO of Neighbourhoodie Software and PMC Chair of Apache CouchDB, is among the named signatories. Node.js core maintainers face the most direct impact, as the TSC’s decision will establish binding standards for how pull requests are evaluated going forward. Enterprises and individual developers who rely on Node.js in production server environments have an indirect stake in both the integrity of the core and the governance precedent being established.
What’s Next
The OpenJS Foundation’s legal team reportedly issued an opinion that LLM-assisted contributions do not violate the project’s Developer’s Certificate of Origin requirements. The petitioners acknowledged this finding but argued it addresses “a small part of the issue with large LLM-written changes to the Node.js core,” leaving broader questions about code auditability and review standards unresolved. As of April 2026, the TSC had not announced a vote date. The petition remains open for new signatures at github.com/indutny/no-ai-in-nodejs-core via pull requests or issues.
