Is django-log-request-id safe to use?

django-log-request-id has no known vulnerabilities on the latest version (2.1.2). DepScope rates its health at 68/100 (moderate risk).

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

The latest version of django-log-request-id is 2.1.2, released 2026-03-12.

Does django-log-request-id have known vulnerabilities?

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

Is django-log-request-id deprecated?

No, django-log-request-id is actively maintained. Latest release: 2.1.2 (2026-03-12).

What are alternatives to django-log-request-id?

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

What license does django-log-request-id use?

django-log-request-id is licensed under BSD-3-Clause.

django-log-request-id

pypiv2.1.2

Django middleware and log filter to attach a unique ID to every log message generated as part of a request

License BSD-3-Clausepermissive18 versions1 deps113,915 weekly dl

dabapps/django-log-request-id/

/ 100

Health

use with caution

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

Moderate health score (68/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

django

API access

Get this data programmatically — free, no authentication.

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