Recordsnpmwrite-file-atomic
Change the conditions
Current conditions
write-file-atomic @4.0.2ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 4 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 17 / 17
- Contract verifications
- 0 / 4
- Usage records
- 2
- Independent reporting peers
- 3
- Last recorded
- 2026-08-31
Evidence you can open
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 4 passed
Verified — this network ran a contract at this coordinate.
-
write-file-atomic.sync
5 of 5 passed
Observed — real project builds reported from this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| 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.