Is django-request-id safe to use?

django-request-id has no known vulnerabilities on the latest version (1.0.0). DepScope rates its health at 30/100 (critical risk).

What is the latest version of django-request-id?

The latest version of django-request-id is 1.0.0, released 2016-10-23.

Does django-request-id have known vulnerabilities?

No known vulnerabilities on the latest version of django-request-id.

Is django-request-id deprecated?

No, django-request-id is actively maintained. Latest release: 1.0.0 (2016-10-23).

What are alternatives to django-request-id?

Popular alternatives to django-request-id in PyPI include: boto3, packaging, urllib3, idna, requests.

What license does django-request-id use?

django-request-id is licensed under MIT.

django-request-id

pypiv1.0.0

Augment each request with unique id for logging purposes

License MITpermissive2 versions1 maintainers0 deps

nigma/django-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

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/django-request-id