Is process-on-spawn safe to use?

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

What is the latest version of process-on-spawn?

The latest version of process-on-spawn is 1.1.0, released 2024-11-13.

Does process-on-spawn have known vulnerabilities?

No known vulnerabilities on the latest version of process-on-spawn.

Is process-on-spawn deprecated?

No, process-on-spawn is actively maintained. Latest release: 1.1.0 (2024-11-13).

What are alternatives to process-on-spawn?

Popular alternatives to process-on-spawn in npm include: debug, lru-cache, string-width, commander, picomatch.

What license does process-on-spawn use?

process-on-spawn is licensed under MIT.

process-on-spawn

npmv1.1.0

Execute callbacks when child processes are spawned

License MITpermissive2 versions1 maintainers1 deps

cfware/process-on-spawn

/ 100

Health

safe to use

[email protected] is safe to use (health: 44/100)

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.5 KBminified

0.8 KB gzipped

1 direct dependencies

side effects

🌟

TypeScript

10/10typed

bundled

Quality signals

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (1)

fromentries

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/process-on-spawn