Leukeleu Django Checks
Additional deploy checks and other tools to validate if a Django project is set up correctly.
Installation
Add 'leukeleu_django_checks' to INSTALLED_APPS.
Included checks
leukeleu.W001: Check ifFILE_UPLOAD_PERMISSIONSis set to0o644leukeleu.W002: Check ifEMAIL_BACKENDis set tobandit.backends.smtp.HijackSMTPBackend- Disable this for test/staging environments using
SILENCED_SYSTEM_CHECKS
- Disable this for test/staging environments using
leukeleu.W003: Check ifEMAIL_BACKENDis not set tobandit.backends.smtp.HijackSMTPBackend- Disable this for production environments using
SILENCED_SYSTEM_CHECKS
- Disable this for production environments using
leukeleu.W004: Check ifWAGTAIL_ENABLE_UPDATE_CHECKis set toFalse- This check only runs if wagtail is installed
leukeleu.W005: Check ifsentry-sdkis installedleukeleu.W006: Check ifsentry-sdkis configured correctlyleukeleu.W007: Make sure there is no/adminor/admin/urlleukeleu.I008: Check ifleukeleu-django-gdpris inINSTALLED_APPS
Run ./manage.py check --deploy to execute these checks (in addition to Django's default set).
List superusers
Run ./manage.py list_superusers to print a list of all (in)active superusers.
The name of each superuser is printed with a "+" (active) or "-" (inactive) prefix.
List staff users
Run ./manage.py list_staff_users to print a list of all (in)active staff users.
The name of each staff user is printed with a "+" (active) or "-" (inactive) prefix.
Metadata
Release files for leukeleu-django-checks 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| leukeleu_django_checks-1.3.0.tar.gz | 5.4 kB | With provenance | Details for leukeleu_django_checks-1.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| leukeleu_django_checks-1.3.0-py3-none-any.whl | Python 3 | none | any | Details for leukeleu_django_checks-1.3.0-py3-none-any.whl |
Total release size: 12.8 kB
Release files / leukeleu_django_checks-1.3.0.tar.gz
| Download URL | leukeleu_django_checks-1.3.0.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d13b94158eae90c3cc6c52462d230e6e5f3cb667d06063030087abf2eb90d9a
|
|
BLAKE2b-256 checksum How to use checksums |
61f5005ae057971da1f5c7f925b4caa0c8cdd5b031a366b7a005207b359f8f59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2025.
Transparency logRelease files / leukeleu_django_checks-1.3.0-py3-none-any.whl
| Download URL | leukeleu_django_checks-1.3.0-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
acc17369252658537b75460f9cde241e147ef6f912fabe3996013747d34506c1
|
|
BLAKE2b-256 checksum How to use checksums |
6b35f2becd3a328dc91209a57e71980e6f2fea7b0746ba2d875ccc106ca101b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2025.
Transparency logSecurity for leukeleu-django-checks 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for leukeleu_django_checks-1.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.