# NousResearch/hermes-agent · Fix Node.js version requirement in contributing docs

## Open now

- Nothing open on GitHub.

Multiple issues and PRs addressing a mismatch between the Node.js version stated in CONTRIBUTING documentation and the actual version specified in package.json engines. The goal is to align the documented prerequisite with the real requirement.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #14357. Verify it addresses your case.
- **Recommended:** read PR #14357 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #11684: \[Docs\]: CONTRIBUTING says Node.js 18+, but package.json requires Node >=20

## Prior & competing PRs

- **#14357: docs(contributing): align Node.js prerequisite with package.json engines (salvage #11690)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `CONTRIBUTING.md`, `scripts/release.py`, `website/docs/developer-guide/contributing.md`
- **#11690: docs(contributing): align Node prerequisite with package engines**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#14357`
- **#11698: docs: align contributing node version with package engines**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#14357`

## Fix status

- Merged to main in PR #14357 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-23`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.