Is process_exists safe to use?

process_exists has no known vulnerabilities on the latest version (0.2.0). DepScope rates its health at 42/100 (high risk).

What is the latest version of process_exists?

The latest version of process_exists is 0.2.0, released 2018-05-22.

Does process_exists have known vulnerabilities?

No known vulnerabilities on the latest version of process_exists.

Is process_exists deprecated?

No, process_exists is actively maintained. Latest release: 0.2.0 (2018-05-22).

What are alternatives to process_exists?

Popular alternatives to process_exists in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does process_exists use?

process_exists is licensed under MIT.

process_exists

rubygemsv0.2.0

Sends a null signal to a process or a group of processes specified by pid to check if it exists.

License MITpermissive5 versions0 deps171,535 weekly dl

wilsonsilva/process_exists

/ 100

Health

use with caution

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

Moderate health score (42/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/process_exists