prepend-file 2.0.0
Prepend data to a file, creating it if it doesn't exist.
prepend-file@2.0.0 was published on 2020-08-01. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=10.17 <11 || >=11.14.
All prepend-file versions · Permanent reference to 2.0.0 · Latest release
Package specifications
| Version | 2.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2020-08-01T14:32:15.089Z |
| Node.js requirement | >=10.17 <11 || >=11.14 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 5.65 KiB |
| Published file count | 6 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 36 |
| Repository forks | 9 |
Install prepend-file 2.0.0
npm install prepend-file@2.0.0 pnpm add prepend-file@2.0.0 yarn add prepend-file@2.0.0
Runtime dependencies
- temp-write ^4.0.0
- path-exists ^4.0.0
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 — indirect
- is-stream@2.0.1 — indirect
- make-dir@3.1.0 — indirect
- path-exists@4.0.0 — direct
- semver@6.3.1 — indirect
- temp-dir@1.0.0 — indirect
- temp-write@4.0.0 — direct
- uuid@3.4.0 — indirect
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 | 2/10 — Found 7/26 approved changesets -- score normalized to 2 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/prepend-file/2.0.0 — retrieved 2026-10-30T09:43:57.536Z
- https://api.deps.dev/v3/projects/github.com%2Fhemanth%2Fnode-prepend-file — retrieved 2026-10-30T08:24:30.445Z
- https://api.deps.dev/v3/systems/npm/packages/prepend-file/versions/2.0.0:dependencies — retrieved 2026-10-30T09:43:58.229Z
- https://api.deps.dev/v3/systems/npm/packages/prepend-file/versions/2.0.0 — retrieved 2026-10-30T09:43:58.196Z