CodeSampleX

Recordsnpmfs-extra11.3.0

Change the conditions
Fixed
Runtimenode 22 Package version11.3.0
Filter OSalpine musl Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

fs-extra @11.3.0alpine musl · x64 · node 22 · npm · node

package-level total, not an API

3 of 3 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
6 / 6
Contract verifications
3 / 3
Usage records
4
Independent reporting peers
1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Changed 2 · Steady 1

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

Library Version Health Measured there Projects
jsonfile 6.2.1 CHANGED Version changed, no linked failure contract passed 1 project-day
universalify 2.0.1 CHANGED Version changed, no linked failure contract passed 1 project-day
graceful-fs 4.2.11 PASS All observations passed contract passed 1 project-day

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.

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.