Is move-concurrently safe to use?

move-concurrently has no known vulnerabilities on the latest version (1.0.1). DepScope rates its health at 28/100 (critical risk).

What is the latest version of move-concurrently?

The latest version of move-concurrently is 1.0.1, released 2017-03-16.

Does move-concurrently have known vulnerabilities?

No known vulnerabilities on the latest version of move-concurrently.

Is move-concurrently deprecated?

Yes, move-concurrently is deprecated: This package is no longer supported. Consider using semver instead.

What are alternatives to move-concurrently?

Popular alternatives to move-concurrently in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does move-concurrently use?

move-concurrently is licensed under ISC.

move-concurrently

npmv1.0.1deprecated

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.

License ISCpermissive2 versions4 maintainers6 deps4,063,984 weekly dl

npm/move-concurrently

/ 100

Health

find alternative

move-concurrently is deprecated — find an alternative

Moderate health score (28/100) — verify manually
Package is deprecated

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

12/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

11.1 KBminified

0.4 KB gzipped

6 direct dependencies

side effects

🌟

TypeScript

7/10typed

Types from @types/move-concurrently (DefinitelyTyped)

Health History

Dependency Tree

License Audit

Dependencies (6)

aproba mkdirp rimraf run-queue copy-concurrently fs-write-stream-atomic

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/move-concurrently