How to use this developer tool
- Paste a Django file or a multi-file project sample.
- Select the project scope and optional framework version.
- Run the checker.
- Review errors, warnings, passed assumptions, and unresolved references.
Check Django settings, models, URLs, app registration, and project conventions for common omissions and structural problems.
Your code is processed locally in your browser and is not uploaded by this tool.
The checker looks for common Django configuration omissions, model conventions, URL naming issues, and deployment-sensitive settings.
It does not run manage.py check, inspect migrations on disk, connect to the database, or import the project.
A production-oriented settings file with DEBUG = True and an empty ALLOWED_HOSTS list produces explicit configuration warnings.
No. It applies static browser-based checks to the supplied source.
Yes. It checks common security, static, media, timezone, and host settings.
It can note migration references in supplied text but cannot inspect migration state or the database.
It detects common field and model conventions such as missing __str__ and mutable defaults.
No. Processing remains local in the browser.
| Settings | DEBUG, hosts, cookies, static and media settings |
|---|---|
| Models | Field declarations and model conventions |
| URLs | Patterns, names, includes, and namespaces |
| Apps | Registration and project structure signals |