Is flask_log_request_id safe to use?

flask_log_request_id has no known vulnerabilities on the latest version (0.10.1). DepScope rates its health at 30/100 (critical risk).

What is the latest version of flask_log_request_id?

The latest version of flask_log_request_id is 0.10.1, released 2019-10-31.

Does flask_log_request_id have known vulnerabilities?

No known vulnerabilities on the latest version of flask_log_request_id.

Is flask_log_request_id deprecated?

No, flask_log_request_id is actively maintained. Latest release: 0.10.1 (2019-10-31).

What are alternatives to flask_log_request_id?

Popular alternatives to flask_log_request_id in PyPI include: boto3, packaging, certifi, urllib3, idna.

What license does flask_log_request_id use?

flask_log_request_id is licensed under MIT.

flask_log_request_id

pypiv0.10.1

Flask extension that can parse and handle multiple types of request-id sent by request processors like Amazon ELB, Heroku or any multi-tier infrastructure as the one used for microservices.

License MITpermissive5 versions1 maintainers6 deps

http://github.com/Workable/flask-log-request-id

/ 100

Health

use with caution

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

Low health score (30/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (6)

Flask nose flake8 mock coverage celery

API access

Get this data programmatically — free, no authentication.

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