CodeSampleX

Recordsnpmnode-gyp9.4.1

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

Current conditions

node-gyp @9.4.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 48 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
36 / 36
Contract verifications
0 / 48
Usage records
85
Independent reporting peers
3
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 6

First observed break

9.4.1

linux · node@22.23 · moduleSystem=cjs · executionContext=node

15 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

View exact conditions View failure cluster
Library Version Health Measured there Projects
make-fetch-happen 10.2.1 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
nopt 6.0.0 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
semver 7.8.5 CANDIDATE Correlated change; unproven combination contract passed 22 project-days
tar 6.2.1 CANDIDATE Correlated change; unproven combination contract passed 22 project-days
which 2.0.2 CANDIDATE Correlated change; unproven combination contract passed 22 project-days
env-paths 2.2.1 PASS All observations passed contract passed 22 project-days
exponential-backoff 3.1.3 PASS All observations passed contract passed 22 project-days
glob 7.2.3 PASS All observations passed contract passed 22 project-days
graceful-fs 4.2.11 PASS All observations passed contract passed 22 project-days
npmlog 6.0.2 PASS All observations passed contract passed 18 project-days
rimraf 3.0.2 PASS All observations passed contract passed 21 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.

Library12.4.012.1.011.5.09.4.1
make-fetch-happen — 15.0.3 14.0.3 10.2.1
nopt 9.0.0 9.0.0 8.1.0 6.0.0
proc-log 6.1.0 6.1.0 5.0.0 —
semver 7.7.4 7.7.3 7.7.4 7.8.5
tar 7.5.22 7.5.4 7.5.22 6.2.1
tinyglobby 0.2.17 0.2.15 0.2.15 —
which 6.0.1 6.0.0 5.0.0 2.0.2
env-paths 2.2.1 2.2.1 2.2.1 2.2.1
exponential-backoff 3.1.3 3.1.3 3.1.3 3.1.3
glob — — — 7.2.3
graceful-fs 4.2.11 4.2.11 4.2.11 4.2.11
npmlog — — — 6.0.2
rimraf — — — 3.0.2
undici 6.28.1 — — —

Moved: 7 · unchanged at every release: 7

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