Is multiprocessing-logging safe to use?

multiprocessing-logging has no known vulnerabilities on the latest version (0.3.4). DepScope rates its health at 36/100 (critical risk).

What is the latest version of multiprocessing-logging?

The latest version of multiprocessing-logging is 0.3.4, released 2023-02-05.

Does multiprocessing-logging have known vulnerabilities?

No known vulnerabilities on the latest version of multiprocessing-logging.

Is multiprocessing-logging deprecated?

No, multiprocessing-logging is actively maintained. Latest release: 0.3.4 (2023-02-05).

What are alternatives to multiprocessing-logging?

Popular alternatives to multiprocessing-logging in PyPI include: boto3, packaging, certifi, idna, urllib3.

What license does multiprocessing-logging use?

multiprocessing-logging is licensed under LGPLv3.

multiprocessing-logging

pypiv0.3.4

Logger for multiprocessing applications

License LGPLv3weak copyleft13 versions1 maintainers0 deps

jruere/multiprocessing-logging

/ 100

Health

use with caution

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

Low health score (36/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/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/pypi/multiprocessing-logging