write-file-atomic 1.3.1

Write files in an atomic fashion w/configurable ownership

write-file-atomic@1.3.1 was published on 2017-01-07. 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 1.3.1 · Latest release

Package specifications

Version1.3.1
License declarationISC
Published2017-01-07T08:02:24.984Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies3
Repository stars256
Repository forks53

Install write-file-atomic 1.3.1

npm install write-file-atomic@1.3.1
pnpm add write-file-atomic@1.3.1
yarn add write-file-atomic@1.3.1

Runtime dependencies

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.

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-Review10/10 — all changesets reviewed
Maintained0/10 — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST9/10 — SAST tool detected but not run on all commits

Evidence and freshness