Is coverage_enable_subprocess safe to use?

coverage_enable_subprocess has no known vulnerabilities on the latest version (1.0). DepScope rates its health at 40/100 (high risk).

What is the latest version of coverage_enable_subprocess?

The latest version of coverage_enable_subprocess is 1.0, released 2016-05-11.

No known vulnerabilities on the latest version of coverage_enable_subprocess.

No, coverage_enable_subprocess is actively maintained. Latest release: 1.0 (2016-05-11).

Popular alternatives to coverage_enable_subprocess in PyPI include: boto3, boto3/, packaging, urllib3/, certifi.

coverage_enable_subprocess is licensed under MIT.

pypiv1.0

enable python coverage for subprocesses

License MITpermissive2 versions1 maintainers1 deps50,007 weekly dl

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Dependencies (1)

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/coverage_enable_subprocess