Is atman-logging-config safe to use?

atman-logging-config has no known vulnerabilities on the latest version (0.1). DepScope rates its health at 27/100 (critical risk).

What is the latest version of atman-logging-config?

The latest version of atman-logging-config is 0.1, released 2018-12-21.

Does atman-logging-config have known vulnerabilities?

No known vulnerabilities on the latest version of atman-logging-config.

Is atman-logging-config deprecated?

No, atman-logging-config is actively maintained. Latest release: 0.1 (2018-12-21).

What are alternatives to atman-logging-config?

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

What license does atman-logging-config use?

atman-logging-config is licensed under MIT.

atman-logging-config

pypiv0.1

Logger with request id

License MITpermissive1 versions1 maintainers3 deps1 weekly dl

/ 100

Health

use with caution

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

Moderate health score (27/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (3)

flask-log-request-id flask python-json-logger

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/atman-logging-config