Is co-child-process safe to use?

co-child-process has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 45/100 (high risk).

What is the latest version of co-child-process?

The latest version of co-child-process is 1.1.0, released 2016-12-02.

Does co-child-process have known vulnerabilities?

No known vulnerabilities on the latest version of co-child-process.

Is co-child-process deprecated?

No, co-child-process is actively maintained. Latest release: 1.1.0 (2016-12-02).

What are alternatives to co-child-process?

Popular alternatives to co-child-process in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does co-child-process use?

co-child-process is licensed under MIT.

co-child-process

npmv1.1.0

easily spawn a child process with co

License MITpermissive5 versions7 maintainers0 deps16 weekly dl

cojs/child-process

/ 100

Health

use with caution

[email protected] low health (45/100) — consider alternatives

Moderate health score (45/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.0 KBminified

0.5 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/co-child-process