CodeSampleX

Recordsnpmbuilder-util-runtime9.2.10

Change the conditions
Fixed
OSdebian glibc Runtimenode 22
Filter Package version9.2.10 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

builder-util-runtime @9.2.10debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
6
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

9.2.10

windows · executionContext=node

6 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
debug 4.4.3 PASS All observations passed contract passed 25 project-days
sax 1.6.1 PASS All observations passed contract passed 25 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