Records/npm/debug/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.

• 4.4.3 FAIL
• 4.3.7 FAIL
• 3.2.7 PASS 11 passing observations
• 2.6.9 FAIL

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×32 2026-08-20 → 2026-08-29
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×16 2026-08-13 → 2026-08-18
• executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×12 2026-08-21 → 2026-08-30

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

  What differs across the boundary

  • ms 2.1.3 → 2.0.0 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last passing release 3.2.7 → first failing release 4.3.7

  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.
• 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
• debug 4.3.7: formatters 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. HOWdebug.formatters MIT-0 · 2026-09-07
• debug 4.3.7: disable, enable, enabled 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.disabledebug.enabledebug.enableddebug.extend MIT-0 · 2026-08-27
• debug 4.3.7 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-19
• debug 2.6.9: disable, enable, enabled 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.disabledebug.enabledebug.enableddebug.formatters MIT-0 · 2026-08-27