CodeSampleX

Recordsnpmbuilder-util26.15.3

Change the conditions
Fixed
Runtimenode (version not recorded) Package managernpm
Filter OSwindows 11 Package version26.15.3 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

builder-util @26.15.3windows 11 · x64 · node (version not recorded) · 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
1
Independent reporting peers
1
Last recorded
2026-09-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 12

First observed break

26.15.3

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
builder-util-runtime 9.7.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
js-yaml 4.3.1 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
js-yaml 4.3.2 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@types/debug 4.1.13 PASS All observations passed contract passed 14 project-days
chalk 4.1.2 PASS All observations passed contract passed 11 project-days
cross-spawn 7.0.6 PASS All observations passed contract passed 11 project-days
debug 4.4.3 PASS All observations passed contract passed 14 project-days
fs-extra 10.1.0 PASS All observations passed contract passed 12 project-days
http-proxy-agent 7.0.2 PASS All observations passed contract passed 11 project-days
https-proxy-agent 7.0.6 PASS All observations passed contract passed 11 project-days
sanitize-filename 1.6.4 PASS All observations passed contract passed 12 project-days
source-map-support 0.5.21 PASS All observations passed contract passed 12 project-days
stat-mode 1.0.0 PASS All observations passed contract passed 11 project-days
temp-file 3.4.0 PASS All observations passed contract passed 12 project-days
tiny-async-pool 1.3.0 PASS All observations passed contract passed 12 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.

Library26.15.325.1.7
builder-util-runtime 9.7.0 9.2.10
js-yaml 4.3.2 4.3.0
7zip-bin — 5.2.0
@types/debug 4.1.13 4.1.13
app-builder-bin — 5.0.0-alpha.10
bluebird-lst — 1.0.9
chalk 4.1.2 4.1.2
cross-spawn 7.0.6 7.0.6
debug 4.4.3 4.4.3
fs-extra 10.1.0 10.1.0
http-proxy-agent 7.0.2 7.0.2
https-proxy-agent 7.0.6 7.0.6
is-ci — 3.0.1
sanitize-filename 1.6.4 —
source-map-support 0.5.21 0.5.21
stat-mode 1.0.0 1.0.0
temp-file 3.4.0 3.4.0
tiny-async-pool 1.3.0 —

Moved: 2 · unchanged at every release: 16

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