CodeSampleX

Recordsnpmfs-extra11.4.0fs.outputJson

Change the conditions
Fixed
Symbolfs.outputJson Architecturex64
Filter OSalpine musl Runtimenode 22 Package version11.4.0 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

fs.outputJson @11.4.0alpine musl · x64 · node 22 · npm · node

1 of 1 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 (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-17

Dependencies

LibraryVersionMeasured thereProjects
graceful-fs 4.2.11 contract passed 7 project-days
jsonfile 6.2.1 contract passed 7 project-days
universalify 2.0.1 contract passed 7 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.

Library11.4.011.3.110.1.09.1.08.1.07.0.1
jsonfile 6.2.1 6.2.1 6.2.1 6.2.1 4.0.0 4.0.0
universalify 2.0.1 2.0.1 2.0.1 2.0.1 0.1.2 0.1.2
at-least-node 1.0.0
graceful-fs 4.2.11 4.2.11 4.2.11 4.2.11 4.2.11 4.2.11

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