Is django-crypto-fields safe to use?

django-crypto-fields has no known vulnerabilities on the latest version (1.2.0). DepScope rates its health at 54/100 (high risk).

What is the latest version of django-crypto-fields?

The latest version of django-crypto-fields is 1.2.0, released 2025-11-13.

Does django-crypto-fields have known vulnerabilities?

No known vulnerabilities on the latest version of django-crypto-fields.

Is django-crypto-fields deprecated?

No, django-crypto-fields is actively maintained. Latest release: 1.2.0 (2025-11-13).

What are alternatives to django-crypto-fields?

Popular alternatives to django-crypto-fields in PyPI include: boto3, packaging, idna, urllib3, typing-extensions.

What license does django-crypto-fields use?

django-crypto-fields is licensed under GPL-3.0-or-later.

django-crypto-fields

pypiv1.2.0

Add encrypted field classes and more to your Django models

License GPL-3.0-or-later44 versions1 maintainers6 deps

erikvw/django-crypto-fields

/ 100

Health

safe to use

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

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (6)

django-audit-fields django-extensions django-revision pycryptodomex python-dateutil tqdm

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/django-crypto-fields