write-file-atomic 2.4.3
Write files in an atomic fashion w/configurable ownership
write-file-atomic@2.4.3 was published on 2019-05-24. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All write-file-atomic versions · Permanent reference to 2.4.3 · Latest release
Package specifications
| Version | 2.4.3 |
|---|---|
| License declaration | ISC |
| Published | 2019-05-24T16:48:52.689Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 11.96 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 256 |
| Repository forks | 53 |
Install write-file-atomic 2.4.3
npm install write-file-atomic@2.4.3 pnpm add write-file-atomic@2.4.3 yarn add write-file-atomic@2.4.3
Runtime dependencies
- graceful-fs ^4.1.11
- imurmurhash ^0.1.4
- signal-exit ^3.0.2
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- graceful-fs@4.2.11 — direct
- imurmurhash@0.1.4 — direct
- signal-exit@3.0.7 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 10/10 — all changesets reviewed |
|---|---|
| Maintained | 0/10 — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Security-Policy | 10/10 — security policy file detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 9/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/write-file-atomic/2.4.3 — retrieved 2026-10-29T10:26:33.727Z
- https://api.deps.dev/v3/projects/github.com%2Fnpm%2Fwrite-file-atomic — retrieved 2026-10-29T06:00:01.790Z
- https://api.deps.dev/v3/systems/npm/packages/write-file-atomic/versions/2.4.3 — retrieved 2026-10-29T10:26:34.255Z
- https://api.deps.dev/v3/systems/npm/packages/write-file-atomic/versions/2.4.3:dependencies — retrieved 2026-10-29T10:26:34.281Z