Records/npm/debug/failure issue

Where it was measured

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

• 4.4.3 FAIL
• 4.3.7 not measured
• 3.2.7 PASS 8 passing observations
• 2.6.9 not measured

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=windows · runtime=node@22.16 ×1 2026-08-19 → 2026-08-19
• executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21

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 3.2.7 → first failing release 4.4.3

  Releases between them never measured at this stage: 1

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

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_TYPECHECK: 2
• No failure domain was inferred for this failure.

Published answers for the affected releases

• debug 4.4.3: enable, enabled, extend 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. HOWdebugdebug.enabledebug.enableddebug.extend MIT-0 · 2026-08-18