Is django-timezone-field safe to use?

django-timezone-field has no known vulnerabilities on the latest version (7.2.1). DepScope rates its health at 71/100 (moderate risk).

What is the latest version of django-timezone-field?

The latest version of django-timezone-field is 7.2.1, released 2025-12-06.

Does django-timezone-field have known vulnerabilities?

No known vulnerabilities on the latest version of django-timezone-field.

Is django-timezone-field deprecated?

No, django-timezone-field is actively maintained. Latest release: 7.2.1 (2025-12-06).

What are alternatives to django-timezone-field?

Popular alternatives to django-timezone-field in PyPI include: boto3, packaging, certifi, urllib3, idna.

What license does django-timezone-field use?

django-timezone-field is licensed under BSD-2-Clause.

django-timezone-field

pypiv7.2.1

A Django app providing DB, form, and REST framework fields for zoneinfo and pytz timezone objects.

License BSD-2-Clausepermissive30 versions1 maintainers2 deps1,628,317 weekly dl

mfogel/django-timezone-field/

/ 100

Health

safe to use

[email protected] is safe to use (health: 71/100)

Health breakdown0 – 100

15/25

maintenance

17/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Quality signals

Publish security

API token

Health History

Dependency Tree

License Audit

Dependencies (2)

Django backports.zoneinfo

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/django-timezone-field