CodeSampleX

Recordsnpmresolve1.22.12

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

Current conditions

resolve @1.22.12ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 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 failed (1)

Project observations
8 / 8
Contract verifications
0 / 2
Usage records
2
Independent reporting peers
3
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
es-errors 1.3.0 contract passed 5 project-days
is-core-module 2.16.2 contract passed 5 project-days
path-parse 1.0.7 contract passed 5 project-days
supports-preserve-symlinks-flag 1.0.0 contract passed 5 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.

Library2.0.0-next.51.22.121.22.111.22.8
is-core-module 2.16.1 2.16.2 2.16.1 2.16.1
es-errors 1.3.0
path-parse 1.0.7 1.0.7 1.0.7 1.0.7
supports-preserve-symlinks-flag 1.0.0 1.0.0 1.0.0 1.0.0

Moved: 1 · unchanged at every release: 3

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