CodeSampleX

Recordsnpm@npmcli/package-json6.2.0@npmcli/package-json.create

Change the conditions
Fixed
Symbol@npmcli/package-json.create Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Package version6.2.0 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

@npmcli/package-json.create @6.2.0ubuntu glibc · x64 · node 22 · npm 10 · node

1 of 1 passed

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
1 / 1
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 7 · Steady 1

First observed break

6.2.0

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/git 6.0.3 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
glob 10.5.0 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
hosted-git-info 8.1.0 CANDIDATE Correlated change; unproven combination contract passed 29 project-days
json-parse-even-better-errors 4.0.0 CANDIDATE Correlated change; unproven combination contract passed 29 project-days
proc-log 5.0.0 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
semver 7.7.4 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
semver 7.8.5 CANDIDATE Correlated change; unproven combination contract passed 26 project-days
validate-npm-package-license 3.0.4 PASS All observations passed contract passed 29 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.57.0.46.2.0
@npmcli/git 7.0.2 7.0.1 6.0.3
glob 13.0.6 13.0.0 10.5.0
hosted-git-info 9.0.3 9.0.2 8.1.0
json-parse-even-better-errors 5.0.0 5.0.0 4.0.0
proc-log 6.1.0 6.1.0 5.0.0
semver 7.8.5 7.7.3 7.7.4
spdx-expression-parse 4.0.0 — —
validate-npm-package-license — 3.0.4 3.0.4

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