CodeSampleX

Recordsnpm@npmcli/git6.0.3@npmcli/git.spawn

Change the conditions
Fixed
Symbol@npmcli/git.spawn
Filter OSubuntu glibc Runtimenode 22 Package version6.0.3 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@npmcli/git.spawn @6.0.3ubuntu glibc · x64 · node 22 · npm 10 · node

2 of 2 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-10-18
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 8 · Steady 1

First observed break

6.0.3

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:536db39a2e089f7ed603954e4a67695a077090ed80e3d0d1ef21bd2d6a9e9b21

View exact conditions View failure cluster
Library Version Health Measured there Projects
@npmcli/promise-spawn 8.0.3 CANDIDATE Correlated change; unproven combination contract passed 27 project-days
ini 5.0.0 CANDIDATE Correlated change; unproven combination contract passed 27 project-days
lru-cache 10.4.3 CANDIDATE Correlated change; unproven combination contract passed 27 project-days
npm-pick-manifest 10.0.0 CANDIDATE Correlated change; unproven combination contract passed 27 project-days
proc-log 5.0.0 CANDIDATE Correlated change; unproven combination contract passed 27 project-days
semver 7.7.4 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
semver 7.8.5 CANDIDATE Correlated change; unproven combination contract passed 24 project-days
which 5.0.0 CANDIDATE Correlated change; unproven combination contract passed 27 project-days
promise-retry 2.0.1 PASS All observations passed contract passed 27 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.

Library7.0.27.0.16.0.3
@npmcli/promise-spawn 9.0.1 9.0.1 8.0.3
ini 6.0.0 6.0.0 5.0.0
lru-cache 11.5.1 11.2.4 10.4.3
npm-pick-manifest 11.0.3 11.0.3 10.0.0
proc-log 6.1.0 6.1.0 5.0.0
semver 7.8.5 7.7.3 7.7.4
which 6.0.1 6.0.0 5.0.0
@gar/promise-retry 1.0.3 — —
promise-retry — 2.0.1 2.0.1

Moved: 7 · 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