CodeSampleX

Recordsnpmdebug2.6.9debug

Change the conditions
Fixed
Package version2.6.9 Symboldebug Package managernpm
Filter OSalpine musl Runtimenode 22 Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

debug @2.6.9alpine musl · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-27

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

2.6.9

executionContext=node

60 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
ms 2.0.0 CANDIDATE Correlated change; unproven combination contract passed 27 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

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.

Library4.4.34.3.73.2.72.6.9
ms 2.1.3 2.1.3 2.1.3 2.0.0

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.

Recent failure clusters

Showing the 12 most-reported of 14 recorded failure clusters. The rest are single reports.