CodeSampleX

Recordsnpmjs-yaml4.1.0dump

Change the conditions
Fixed
Symboldump Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Package version4.1.0 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

dump @4.1.0ubuntu glibc · x64 · node 22 · npm 10 · node

5 of 7 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 (2)

Project observations
5 / 7
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
argparse 2.0.1 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.

Library4.3.24.3.14.3.04.1.03.15.23.15.1
argparse 2.0.1 2.0.1 2.0.1 2.0.1 1.0.10 1.0.10
esprima 4.0.1 4.0.1

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

Recent failure clusters