Records/npm/@types/node/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 26.4.0 PASS 93 passing observations
• 26.3.0 PASS 22 passing observations
• 26.2.0 FAIL
• 26.1.2 PASS 1 passing observations
• 24.13.3 PASS 29 passing observations
• 22.20.2 PASS 12 passing observations
• 22.20.1 FAIL
• 22.19.19 not measured
• 22.19.1 PASS 11 passing observations

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×9 2026-08-26 → 2026-08-27
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×4 2026-08-18 → 2026-08-18
• executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×3 2026-08-26 → 2026-08-26

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release 22.19.1 → first failing release 22.20.1

  Releases between them never measured at this stage: 1

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last failing release 22.20.1 → first passing release 22.20.2

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last passing release 26.1.2 → first failing release 26.2.0

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last failing release 26.2.0 → first passing release 26.3.0

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 1 · unchanged at every release: 0

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• Releases in this window never measured at PROJECT_PROCESS: 1
• No resolved dependency tree for 26.3.0 or for 26.2.0, so the versions either side of the boundary could not be compared.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• @types/node 26.2.0 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-23
• @types/node 22.20.1: dependencies Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW@types/node.dependencies MIT-0 · 2026-09-06
• @types/node 22.20.1: version Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW@types/node.version MIT-0 · 2026-08-26
• @types/node 22.20.1: types Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW@types/node.types MIT-0 · 2026-08-26