Is @cjser/fkill__v8_1_1 safe to use?

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

What is the latest version of @cjser/fkill__v8_1_1?

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

Does @cjser/fkill__v8_1_1 have known vulnerabilities?

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

Is @cjser/fkill__v8_1_1 deprecated?

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

What are alternatives to @cjser/fkill__v8_1_1?

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

What license does @cjser/fkill__v8_1_1 use?

@cjser/fkill__v8_1_1 is licensed under MIT.

@cjser/fkill__v8_1_1

npmv8.1.1-cjser.2

Fabulously kill processes. Cross-platform.

License MITpermissive1 versions1 maintainers6 deps8 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 (6)

execa process-exists ps-list @cjser/aggregate-error__v4_0_1 @cjser/pid-port__v0_2_0 @cjser/taskkill__v4_0_0

API access

Get this data programmatically — free, no authentication.

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