Is django-pgcrypto-fields safe to use?

django-pgcrypto-fields has no known vulnerabilities on the latest version (2.6.0). DepScope rates its health at 49/100 (high risk).

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

The latest version of django-pgcrypto-fields is 2.6.0, released 2021-01-06.

Does django-pgcrypto-fields have known vulnerabilities?

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

Is django-pgcrypto-fields deprecated?

No, django-pgcrypto-fields is actively maintained. Latest release: 2.6.0 (2021-01-06).

What are alternatives to django-pgcrypto-fields?

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

What license does django-pgcrypto-fields use?

django-pgcrypto-fields is licensed under BSD.

django-pgcrypto-fields

pypiv2.6.0

Encrypted fields for Django dealing with pgcrypto postgres extension.

License BSDpermissive25 versions1 maintainers0 deps12,698 weekly dl

incuna/django-pgcrypto-fields

/ 100

Health

use with caution

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

Moderate health score (49/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

12/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-pgcrypto-fields