Is Django Secured Fields Safe?

Django Secured Fields — Nerq Trust Score 57.2/100 (C grade). Score based on 2 independent trust signals. Last analyzed: 2026-10-01

Django Secured Fields is a Python package with a Nerq Trust Score of 57.2/100 (C), based on 3 independent data dimensions. Last analyzed: 2026-10-01 Security: 90/100. Popularity: 60/100. Data sourced from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-10-01. Machine-readable data (JSON).

Is Django Secured Fields safe?

Trust Score Breakdown — Django Secured Fields has a Nerq Trust Score of 57.2/100 (C). Measured across 2 independent trust signals (as of 2026-10-01).

Security Analysis → Django Secured Fields Privacy Report →

What is Django Secured Fields's trust score?

Django Secured Fields has a Nerq Trust Score of 57.2/100, earning a C grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
60

What are the key security findings for Django Secured Fields?

Django Secured Fields's strongest signal is security at 90/100. No known vulnerabilities have been detected.

✓Security score: 90/100 (strong)
⚠Popularity: 60/100 — community adoption

What is Django Secured Fields and who maintains it?

AuthorCODIUM
CategoryPython Packages
SourceN/A

Django Secured Fields Across Platforms

Same developer/company in other registries:

codium/foxhound
53/100 · packagist
codium/laravel-sms-capture
53/100 · packagist

Similar Pypi by Trust Score

arro3-core (67)avro-gen (67)azure-servicemanagement-legacy (67)azure-eventhub-checkpointstoreblob-aio (67)captum (67)
See all safest Pypi →

Compare

Django Secured Fields vs arro3-coreDjango Secured Fields vs avro-genDjango Secured Fields vs azure-servicemanagement-legacy

Safety Guide: Django Secured Fields

What is Django Secured Fields?

Django Secured Fields is a Python package — Django encrypted fields with search enabled..

How to Verify Safety

Run pip audit or safety check. Review on PyPI for download stats.

You can also check the trust score via API: GET /v1/preflight?target=django-secured-fields

Key Safety Concerns for Python package

When evaluating any Python package, watch for: dependency vulnerabilities, malicious uploads, maintenance status.

Measured Signals

Django Secured Fields has a Nerq Trust Score of 57/100 (C). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Django Secured Fields Safe?
django-secured-fields with a Nerq Trust Score of 57.2/100 (C). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (60/100).
What is Django Secured Fields's trust score?
django-secured-fields: 57.2/100 (C). Score based on Security (90/100), Popularity (60/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=django-secured-fields
What are safer alternatives to Django Secured Fields?
In the Python Packages category, more Python packages are being analyzed — check back soon. django-secured-fields scores 57.2/100.
Does Django Secured Fields have known vulnerabilities?
Nerq checks Django Secured Fields against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is Django Secured Fields actively maintained?
Django Secured Fields maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.

We use cookies for analytics and caching. Privacy