CodeSampleX

Recordsnpmbuilder-util-runtime9.7.0builder-util-runtime.HttpExecutor

Change the conditions
Fixed
Symbolbuilder-util-runtime.HttpExecutor
Filter OSubuntu glibc Runtimenode 22 Package version9.7.0 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

builder-util-runtime.HttpExecutor @9.7.0ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 12 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
12 / 14
Contract verifications
0 / 12
Independent reporting peers
2
Last recorded
2026-08-30

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

9.7.0

windows · node@24.13 · moduleSystem=esm · executionContext=node

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

Library Version Health Measured there Projects
debug 4.4.3 PASS All observations passed contract passed 16 project-days
sax 1.6.1 PASS All observations passed contract passed 14 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.

Library9.7.09.2.10
debug 4.4.3 4.4.3
sax 1.6.1 1.6.1

Moved: 0 · unchanged at every release: 2

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 22 recorded failure clusters. The rest are single reports.