Is @cjser/execa__v6_1_0 safe to use?

@cjser/execa__v6_1_0 has no known vulnerabilities on the latest version (6.1.0-cjser.2). DepScope rates its health at 47/100 (high risk).

What is the latest version of @cjser/execa__v6_1_0?

The latest version of @cjser/execa__v6_1_0 is 6.1.0-cjser.2, released 2026-05-07.

Does @cjser/execa__v6_1_0 have known vulnerabilities?

No known vulnerabilities on the latest version of @cjser/execa__v6_1_0.

Is @cjser/execa__v6_1_0 deprecated?

No, @cjser/execa__v6_1_0 is actively maintained. Latest release: 6.1.0-cjser.2 (2026-05-07).

What are alternatives to @cjser/execa__v6_1_0?

Popular alternatives to @cjser/execa__v6_1_0 in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @cjser/execa__v6_1_0 use?

@cjser/execa__v6_1_0 is licensed under MIT.

@cjser/execa__v6_1_0

npmv6.1.0-cjser.2

Process execution for humans

License MITpermissive1 versions1 maintainers9 deps2 weekly dl

https://code.moenext.com/3rdeye/cjser

/ 100

Health

use with caution

@cjser/[email protected] low health (47/100) — consider alternatives

Moderate health score (47/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (9)

cross-spawn get-stream merge-stream signal-exit @cjser/human-signals__v3_0_1 @cjser/is-stream__v3_0_0 @cjser/npm-run-path__v5_3_0 @cjser/onetime__v6_0_0 @cjser/strip-final-newline__v3_0_0

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@cjser/execa__v6_1_0