CodeSampleX

Recordsnpmdebug4.4.3

Change the conditions
Fixed
Runtimenode 24 Symbolwhole package Package managerpnpm 10
Filter OSwindows 11 Package version4.4.3 Architecturex64 Execution contextnode Clear filters

Current conditions

debug @4.4.3windows 11 · x64 · node 24 · pnpm 10 · node

package-level total, not an API

0 of 229 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
326 / 424
Contract verifications
0 / 229
Usage records
1,256
Independent reporting peers
1
Failures with a captured fingerprint
95 / 98
Last recorded
2026-09-26

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

4.4.3

executionContext=node

60 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
ms 2.1.3 CANDIDATE Correlated change; unproven combination contract passed 434 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 333 recorded failure clusters. The rest are single reports.