Compatibilitynpmwrite-file-atomic4.0.2
Change the conditions
Current conditions
write-file-atomic @4.0.2windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
2 of 2 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-18
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.
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.
| Library | 5.0.1 | 4.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.