CodeSampleX

Recordsnpmwrite-file-atomic4.0.2writeFile.sync

Change the conditions
Fixed
SymbolwriteFile.sync Architecturex64
Filter OSalpine musl Runtimenode 22 Package version4.0.2 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

writeFile.sync @4.0.2alpine 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-27
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
imurmurhash 0.1.4 contract passed 8 project-days
signal-exit 3.0.7 contract passed 8 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.

Library5.0.14.0.2
signal-exit 4.1.0 3.0.7
imurmurhash 0.1.4 0.1.4

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