You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Independent audit of the Node.js v24.22.1 API documentation (Nacodex, October 2026), in two parts #67509
These audits examined the Node.js API reference (doc/api) for release v24.22.1 as published on the dates given below, not this repository's issue tracker or its source at any particular commit. The pages may have changed since. Some findings may already be addressed or tracked elsewhere; we did not check existing issues. We did not compare the findings with later releases or commits.
Nacodex is an independent code and documentation audit service. The public audits are ready to read:
Node.js API documentation, part 1 of 2, 22 October 2026 (pages fetched 21 October 2026): 16 findings after review; 0 High after review, 5 Medium after review, 9 Low after review, 2 Info after review, 0 excluded on review.
Every finding on this page carries its evidence and a suggested fix.
Node.js API documentation, part 2 of 2, 22 October 2026 (pages fetched 21 October 2026): 35 findings after review; 0 High after review, 11 Medium after review, 17 Low after review, 7 Info after review, 0 excluded on review.
Every finding on this page carries its evidence and a suggested fix.
What we found (both parts):
Medium: Load-hook sample throws away its own source rewrite (module.md:1039)
Medium: Synchronous import-map hook sample calls readFileSync on the promises module (module.md:1813)
Medium: WebAssembly text sample exports an identifier it never defined (esm.md:805)
Medium: Suggested replacement for util.isDate() is never true (deprecations.md:1147)
Medium: Config-file example contains a key the page says is forbidden (cli.md:1033)
and 46 more findings (11 Medium, 26 Low, 9 Info), each with evidence and a suggested fix on the page.
These audits predate our updated detection guides and our new auditor. We recommend fixing the items already identified, then running a fresh audit with the current method, in which the auditor is asked to write a concrete fix for every finding: what to change, where, how, and how to confirm it.
Questions about these findings: support@nacodex.help
Nacodex.help
Pukapasoft.xyz
Activity
ondrejdvorak78 commentedon Nov 16, 2026
Finds are legit, they may have been fixed before as stated in audit. It was run on original repo.
MikeMcC399 commentedon Nov 16, 2026
Node.js does not allow automated posting of issues or advertising of services. It regards this as spam.
https://github.com/nodejs/admin/blob/main/Moderation-Policy.md#non-collaborator-posts advises: