fs-safe
A simple fs wrapper that doesn't throw
fs-safe@1.2.0 was published on 2021-04-13. Its manifest declares 14 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 fs-safe versions · Permanent reference to 1.2.0
Package specifications
| Version | 1.2.0 |
|---|---|
| License declaration | MIT |
| Published | 2021-04-13T14:03:58.580Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 14 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 20.30 KiB |
| Published file count | 7 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./build/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 37 |
| Repository stars | 2 |
| Repository forks | 0 |
Install fs-safe 1.2.0
npm install fs-safe@1.2.0 pnpm add fs-safe@1.2.0 yarn add fs-safe@1.2.0
Runtime dependencies
- dir-exists-safe ^1.1.0
- file-exists-safe ^1.1.0
- make-executable ^1.0.1
- merge-json-file ^1.0.1
- read-dir-safe ^1.0.1
- read-file-safe ^1.0.10
- read-json-safe ^2.0.2
- remove-dir-safe ^1.0.1
- remove-file-safe ^1.0.1
- watch-dir-safe ^1.0.2
- watch-file-safe ^1.0.1
- write-dir-safe ^1.0.1
- write-file-safe ^1.3.1
- write-json-safe ^2.1.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.
- anymatch@3.1.3 — indirect
- binary-extensions@2.3.0 — indirect
- braces@3.0.3 — indirect
- char-to-string@1.0.0 — indirect
- chokidar@3.6.0 — indirect
- deepmerge@4.3.1 — indirect
- detect-newline@3.1.0 — indirect
- dir-exists-safe@1.1.0 — direct
- ends-with-string@1.0.1 — indirect
- file-exists-safe@1.1.0 — direct
- fill-range@7.1.1 — indirect
- fsevents@2.3.3 — indirect
- glob-parent@5.1.2 — indirect
- is-binary-path@2.1.0 — indirect
- is-extglob@2.1.1 — indirect
- is-glob@4.0.3 — indirect
- is-number@7.0.0 — indirect
- make-executable@1.0.2 — direct
- merge-json-file@1.0.1 — direct
- normalize-path@3.0.0 — indirect
- parse-json-object@2.0.1 — indirect
- picomatch@2.3.2 — indirect
- read-dir-safe@1.0.1 — direct
- read-file-safe@1.0.10 — direct
- read-json-safe@2.0.2 — direct
- readdirp@3.6.0 — indirect
- remove-dir-safe@1.0.1 — direct
- remove-file-safe@1.0.1 — direct
- stringify-json-object@1.0.7 — indirect
- terminating-newline@1.2.4 — indirect
- to-regex-range@5.0.1 — indirect
- types-json@1.2.2 — indirect
- watch-dir-safe@1.0.2 — direct
- watch-file-safe@1.0.1 — direct
- write-dir-safe@1.0.1 — direct
- write-file-safe@1.3.1 — direct
- write-json-safe@2.1.0 — 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.
| 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 |
| Code-Review | 0/10 — Found 0/12 approved changesets -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| 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 | 0/10 — license file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/fs-safe/1.2.0 — retrieved 2026-10-31T08:51:39.893Z
- https://api.deps.dev/v3/systems/npm/packages/fs-safe/versions/1.2.0 — retrieved 2026-10-31T08:51:40.321Z
- https://api.deps.dev/v3/systems/npm/packages/fs-safe/versions/1.2.0:dependencies — retrieved 2026-10-31T08:51:40.339Z
- https://api.deps.dev/v3/projects/github.com%2Fbconnorwhite%2Ffs-safe — retrieved 2026-10-31T08:51:40.822Z