CodeSampleX

Recordsnpmwrite-file-atomic5.0.1

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

Current conditions

write-file-atomic @5.0.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 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 failed

Project observations
14 / 14
Contract verifications
0 / 3
Usage records
5
Independent reporting peers
2
Last recorded
2026-08-31
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
imurmurhash 0.1.4 contract passed 3 project-days
signal-exit 4.1.0 contract passed 3 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