CodeSampleX

Recordsnpmnode-gyp12.4.0

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

Current conditions

node-gyp @12.4.0debian 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
2
Independent reporting peers
1
Last recorded
2026-09-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 5

First observed break

12.4.0

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
nopt 9.0.0 CANDIDATE Correlated change; unproven combination contract passed 15 project-days
proc-log 6.1.0 CANDIDATE Correlated change; unproven combination contract passed 15 project-days
semver 7.7.4 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
semver 7.8.5 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
tar 7.5.22 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
tinyglobby 0.2.17 CANDIDATE Correlated change; unproven combination contract passed 15 project-days
which 6.0.1 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
env-paths 2.2.1 PASS All observations passed contract passed 16 project-days
exponential-backoff 3.1.3 PASS All observations passed contract passed 16 project-days
graceful-fs 4.2.11 PASS All observations passed contract passed 16 project-days
undici 6.28.0 PASS All observations passed contract passed 11 project-days
undici 6.28.1 PASS All observations passed contract passed 2 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