Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

django

https://github.com/django/django · scanned 2026-05-16 16:20 UTC (1 day, 4 hours ago) · 10 languages

549 findings (48 legacy + 501 scanner) 8/10 scanners ran 75th percentile · Python · huge (>500K LoC) Scanner says 73 (higher by 2)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 4 hours ago · v1 · 549 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}
Score breakdown â 2026-05-17-v4 calibration-aware
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 69.5 0.25 17.38
testing_score 85.0 0.20 17.00
documentation_score 70.0 0.15 10.50
practices_score 90.0 0.15 13.50
code_quality 80.0 0.10 8.00
Overall 1.00 75.4
Calibrated penalty buckets (security_score): web: 1.6 · authz: 1.2 · threat: 27.8
security_score may be inflated — optional scanners skipped due to repo size/fast scan
Severity distribution — click a segment to filter
Active filters: severity: medium × excluding tests × Reset all
Scan summary Repository scanned at 73.4/100 with 100.0% coverage. It contains 41687 nodes across 23 cross-layer flows, written primarily in mixed languages. Engine surfaced 501 findings — concentrated in quality (317), software (78), cicd (54). Risk profile is high: 2 critical, 3 high, 31 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 36 of 549 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium Legacy security auth conf 0.92 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks but does not define .repobility/access.yml or equivalent authorization documentation.
Add .repobility/access.yml mapping routes to anonymous, authenticated, owner, admin, and super_admin. Keep business-specific rules in the repo so CI can enforce them.
authlegacy
medium Legacy security injection conf 0.50 [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input.
Use subprocess with shell=False and a list of args. Never eval user input.
django/utils/version.py:90 injectionlegacy
medium Legacy security deserialization conf 1.00 [SEC007] Unsafe Deserialization: Unsafe deserialization can execute arbitrary code.
Use yaml.safe_load() instead of yaml.load(). Avoid pickle for untrusted data.
django/core/cache/backends/locmem.py:43 deserializationlegacy
medium Legacy security deserialization conf 1.00 [SEC007] Unsafe Deserialization: Unsafe deserialization can execute arbitrary code.
Use yaml.safe_load() instead of yaml.load(). Avoid pickle for untrusted data.
django/core/cache/backends/filebased.py:38 deserializationlegacy
medium Legacy security deserialization conf 1.00 [SEC007] Unsafe Deserialization: Unsafe deserialization can execute arbitrary code.
Use yaml.safe_load() instead of yaml.load(). Avoid pickle for untrusted data.
django/core/cache/backends/db.py:96 deserializationlegacy
medium Legacy quality quality conf 0.78 Public web service has no security.txt
Add /.well-known/security.txt with Contact, Expires, Canonical, Preferred-Languages, and Policy fields. Keep the contact endpoint monitored.
.well-known/security.txt qualitylegacy
medium 9-layer security auth conf 1.00 Django CBV `CreateView` lacks `LoginRequiredMixin` — django/views/generic/edit.py:185
Class-based view defines mutating methods (post/put/delete) without inheriting `LoginRequiredMixin`. If auth is enforced via `dispatch()` override or middleware, dismiss this finding.
django/views/generic/edit.py:185 authauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django CBV `FormView` lacks `LoginRequiredMixin` — django/views/generic/edit.py:165
Class-based view defines mutating methods (post/put/delete) without inheriting `LoginRequiredMixin`. If auth is enforced via `dispatch()` override or middleware, dismiss this finding.
django/views/generic/edit.py:165 authauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django CBV `ProcessFormView` lacks `LoginRequiredMixin` — django/views/generic/edit.py:137
Class-based view defines mutating methods (post/put/delete) without inheriting `LoginRequiredMixin`. If auth is enforced via `dispatch()` override or middleware, dismiss this finding.
django/views/generic/edit.py:137 authauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django CBV `RedirectView` lacks `LoginRequiredMixin` — django/views/generic/base.py:231
Class-based view defines mutating methods (post/put/delete) without inheriting `LoginRequiredMixin`. If auth is enforced via `dispatch()` override or middleware, dismiss this finding.
django/views/generic/base.py:231 authauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django CBV `TemplateView` lacks `LoginRequiredMixin` — django/views/generic/base.py:221
Class-based view defines mutating methods (post/put/delete) without inheriting `LoginRequiredMixin`. If auth is enforced via `dispatch()` override or middleware, dismiss this finding.
django/views/generic/base.py:221 authauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django CBV `UpdateView` lacks `LoginRequiredMixin` — django/views/generic/edit.py:209
Class-based view defines mutating methods (post/put/delete) without inheriting `LoginRequiredMixin`. If auth is enforced via `dispatch()` override or middleware, dismiss this finding.
django/views/generic/edit.py:209 authauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django view `feed` may be unauthenticated — django/contrib/gis/views.py:5
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
django/contrib/gis/views.py:5 authowaspauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django view `flatpage` may be unauthenticated — django/contrib/flatpages/views.py:22
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
django/contrib/flatpages/views.py:22 authowaspauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django view `kml` may be unauthenticated — django/contrib/gis/sitemaps/views.py:10
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
django/contrib/gis/sitemaps/views.py:10 authowaspauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django view `kmz` may be unauthenticated — django/contrib/gis/sitemaps/views.py:61
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
django/contrib/gis/sitemaps/views.py:61 authowaspauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django view `render_flatpage` may be unauthenticated — django/contrib/flatpages/views.py:49
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
django/contrib/flatpages/views.py:49 authowaspauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django view `serve` may be unauthenticated — django/contrib/staticfiles/views.py:16
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
django/contrib/staticfiles/views.py:16 authowaspauth.django.unauth_view
medium 9-layer security auth conf 1.00 Django view `shortcut` may be unauthenticated — django/contrib/contenttypes/views.py:9
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
django/contrib/contenttypes/views.py:9 authowaspauth.django.unauth_view
medium 9-layer cicd supply-chain conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
psf/black@stable can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/linters.yml:71 supply-chaingithub-actionspinned-dependencies
medium 9-layer security owasp conf 1.00 Insecure pattern 'subprocess_shell_true' in django/utils/version.py:93
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
django/utils/version.py:93 owaspsubprocess_shell_true
medium 9-layer security owasp conf 1.00 Insecure pattern 'subprocess_shell_true' in scripts/manage_translations.py:201
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
scripts/manage_translations.py:201 owaspsubprocess_shell_true
medium 9-layer security owasp conf 1.00 Insecure pattern 'weak_hash' in django/db/backends/sqlite3/_functions.py:72
Found a known-risky pattern (weak_hash). Review and replace if possible.
django/db/backends/sqlite3/_functions.py:72 owaspweak_hash
medium 9-layer security owasp conf 1.00 Insecure pattern 'weak_hash' in django/db/models/functions/__init__.py:55
Found a known-risky pattern (weak_hash). Review and replace if possible.
django/db/models/functions/__init__.py:55 owaspweak_hash
medium 9-layer security owasp conf 1.00 Insecure pattern 'weak_hash' in django/db/models/functions/text.py:216
Found a known-risky pattern (weak_hash). Review and replace if possible.
django/db/models/functions/text.py:216 owaspweak_hash
medium 9-layer security owasp conf 1.00 Insecure pattern 'weak_hash' in scripts/verify_release.sh:63
Found a known-risky pattern (weak_hash). Review and replace if possible.
scripts/verify_release.sh:63 owaspweak_hash
medium 9-layer quality integrity conf 1.00 Likely N+1 query: `for field in …` triggers a query per row — django/contrib/contenttypes/views.py:57
The loop iterates a Django queryset and accesses `field.remote_field.model` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 que…
django/contrib/contenttypes/views.py:57 integrityn-plus-oneperformance
medium 9-layer quality integrity conf 1.00 Likely N+1 query: `for field in …` triggers a query per row — django/contrib/contenttypes/views.py:73
The loop iterates a Django queryset and accesses `field.remote_field.model` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 que…
django/contrib/contenttypes/views.py:73 integrityn-plus-oneperformance
medium 9-layer quality integrity conf 1.00 Network/subprocess call without timeout or try/except — django/db/backends/base/client.py:31
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
integrityfragile-runtimerobustness
medium 9-layer quality integrity conf 1.00 Network/subprocess call without timeout or try/except — django/db/backends/mysql/client.py:40
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
integrityfragile-runtimerobustness
medium 9-layer quality integrity conf 1.00 Network/subprocess call without timeout or try/except — django/db/backends/mysql/creation.py:78
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
integrityfragile-runtimerobustness
medium 9-layer quality integrity conf 1.00 Network/subprocess call without timeout or try/except — django/utils/autoreload.py:290
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
integrityfragile-runtimerobustness
medium 9-layer quality integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/do_django_release.py:165
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
integrityfragile-runtimerobustness
medium 9-layer quality integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/manage_translations.py:48
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
integrityfragile-runtimerobustness
medium 9-layer quality integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/prepare_commit_msg.py:28
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
integrityfragile-runtimerobustness
medium 9-layer security coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). Either auth lives in custom code, in a separate service, or is missing.
coverageauth
{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/ae0fafd5-ca42-4d82-9dcd-8a318ddbf0a9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ae0fafd5-ca42-4d82-9dcd-8a318ddbf0a9/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.