Is django-field-history safe to use?

django-field-history has no known vulnerabilities on the latest version (0.8.0). DepScope rates its health at 41/100 (high risk).

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

The latest version of django-field-history is 0.8.0, released 2020-01-05.

Does django-field-history have known vulnerabilities?

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

Is django-field-history deprecated?

No, django-field-history is actively maintained. Latest release: 0.8.0 (2020-01-05).

What are alternatives to django-field-history?

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

What license does django-field-history use?

django-field-history is licensed under BSD.

django-field-history

pypiv0.8.0

A Django app to track changes to a model field.

License BSDpermissive8 versions1 maintainers0 deps6,394 weekly dl

grantmcconnaughey/django-field-history

/ 100

Health

use with caution

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

Moderate health score (41/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

6/15

maturity

4/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-field-history