CodeSampleX

Recordsnpmbuilder-util25.1.7builder-util.archFromString

Change the conditions
Fixed
Symbolbuilder-util.archFromString
Filter OSubuntu glibc Runtimenode 22 Package version25.1.7 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

builder-util.archFromString @25.1.7ubuntu glibc · x64 · node 22 · npm 10 · node

0 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 failed

Project observations
nothing at this coordinate
Contract verifications
0 / 1
Last recorded
2026-08-31
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 14

First observed break

25.1.7

moduleSystem=cjs · executionContext=node

6 FAIL · stage: UNKNOWN · fingerprint: sha256:bc4d7ddc5bcdb4d412bf4a8bb2673c786c7e3852044dc88acdc3e1dc4e6f49cb

View exact conditions View failure cluster
Library Version Health Measured there Projects
builder-util-runtime 9.2.10 CANDIDATE Correlated change; unproven combination contract passed 24 project-days
js-yaml 4.3.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
js-yaml 4.3.2 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
7zip-bin 5.2.0 PASS All observations passed contract passed 24 project-days
@types/debug 4.1.13 PASS All observations passed contract passed 24 project-days
app-builder-bin 5.0.0-alpha.10 PASS All observations passed contract passed 24 project-days
bluebird-lst 1.0.9 PASS All observations passed contract passed 24 project-days
chalk 4.1.2 PASS All observations passed contract passed 24 project-days
cross-spawn 7.0.6 PASS All observations passed contract passed 24 project-days
debug 4.4.3 PASS All observations passed contract passed 24 project-days
fs-extra 10.1.0 PASS All observations passed contract passed 24 project-days
http-proxy-agent 7.0.2 PASS All observations passed contract passed 24 project-days
https-proxy-agent 7.0.6 PASS All observations passed contract passed 24 project-days
is-ci 3.0.1 PASS All observations passed contract passed 24 project-days
source-map-support 0.5.21 PASS All observations passed contract passed 24 project-days
stat-mode 1.0.0 PASS All observations passed contract passed 23 project-days
temp-file 3.4.0 PASS All observations passed contract passed 22 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