move-file 1.1.0
Move a file - Even works across devices
move-file@1.1.0 was published on 2019-03-04. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.
All move-file versions · Permanent reference to 1.1.0 · Latest release
Package specifications
| Version | 1.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2019-03-04T05:24:19.746Z |
| Node.js requirement | >=8 |
| 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 | 5.83 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 208 |
| Repository forks | 9 |
Install move-file 1.1.0
npm install move-file@1.1.0 pnpm add move-file@1.1.0 yarn add move-file@1.1.0
Runtime dependencies
- cp-file ^6.0.0
- make-dir ^2.1.0
- path-exists ^3.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.
- cp-file@6.2.0 — direct
- graceful-fs@4.2.11 — indirect
- make-dir@2.1.0 — direct
- nested-error-stacks@2.1.1 — indirect
- path-exists@3.0.0 — direct
- pify@4.0.1 — indirect
- safe-buffer@5.2.1 — indirect
- semver@5.7.2 — 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.
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Security-Policy | 10/10 — security policy file detected |
| Code-Review | 1/10 — Found 5/30 approved changesets -- score normalized to 1 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge 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/move-file/1.1.0 — retrieved 2026-10-31T23:07:54.620Z
- https://api.deps.dev/v3/projects/github.com%2Fsindresorhus%2Fmove-file — retrieved 2026-10-31T22:28:44.779Z
- https://api.deps.dev/v3/systems/npm/packages/move-file/versions/1.1.0 — retrieved 2026-10-31T23:07:55.099Z
- https://api.deps.dev/v3/systems/npm/packages/move-file/versions/1.1.0:dependencies — retrieved 2026-10-31T23:07:55.127Z