move-concurrently

Promises of moves of files or directories with rename, falling back to recursive rename/copy on EXDEV errors, with configurable concurrency and win32 junction support.

move-concurrently@1.0.1 was published on 2017-03-16. Its manifest declares 6 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.

Deprecated: This package is no longer supported.

All move-concurrently versions · Permanent reference to 1.0.1

Package specifications

Version1.0.1
License declarationISC
Published2017-03-16T23:24:29.189Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count6
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 entrymove.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies28
Repository stars18
Repository forks9

Install move-concurrently 1.0.1

npm install move-concurrently@1.0.1
pnpm add move-concurrently@1.0.1
yarn add move-concurrently@1.0.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.

SAST0/10 — no SAST tool detected
Binary-Artifacts10/10 — no binaries found in the repo
Code-Review0/10 — Found 0/6 approved changesets -- score normalized to 0
Maintained0/10 — project is archived
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy0/10 — security policy file not detected

Evidence and freshness