CodeSampleX

Recordsnpminit-package-json

Change the conditions
Fixed
Package version7.0.2 Package managernpm
Filter OSdebian glibc Runtimenode 22 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

init-package-json @7.0.2debian glibc · x64 · node 22 · npm · node

2 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (2)

Project observations
6 / 6
Contract verifications
2 / 2
Usage records
5
Independent reporting peers
2
Last recorded
2026-10-21
Evidence you can open

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Changed 7 · Steady 1

Dependency changes observed: 7. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
@npmcli/package-json 6.2.0 CHANGED Version changed, no linked failure contract passed 17 project-days
npm-package-arg 12.0.2 CHANGED Version changed, no linked failure contract passed 17 project-days
promzard 2.0.0 CHANGED Version changed, no linked failure contract passed 17 project-days
read 4.1.0 CHANGED Version changed, no linked failure contract passed 17 project-days
semver 7.7.4 CHANGED Version changed, no linked failure contract passed 13 project-days
semver 7.8.5 CHANGED Version changed, no linked failure contract passed 4 project-days
validate-npm-package-name 6.0.2 CHANGED Version changed, no linked failure contract passed 16 project-days
validate-npm-package-license 3.0.4 PASS All observations passed contract passed 17 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.

Library8.2.58.2.47.0.2
@npmcli/package-json 7.0.5 7.0.4 6.2.0
npm-package-arg 13.0.2 13.0.2 12.0.2
promzard 3.0.1 3.0.1 2.0.0
read 5.0.1 5.0.1 4.1.0
semver 7.8.5 7.7.3 7.8.5
validate-npm-package-name 7.0.2 7.0.2 6.0.2
validate-npm-package-license — 3.0.4 3.0.4

Moved: 6 · unchanged at every release: 1

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.