django

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.

https://github.com/django/django · scanned 2026-05-16 16:20 UTC (1 day, 5 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)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 5 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

100.0% cov · 501 gaps

{# ── 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: critical × 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 3 of 549 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical Legacy security credential_exposure conf 0.90 [SEC001] Hardcoded Password: Hardcoded password found in source code.

Use environment variables or a secrets manager.

django/db/backends/oracle/creation.py:292 credential_exposurelegacy

critical 9-layer security secrets conf 1.00 Possible secret in django/contrib/auth/management/commands/changepassword.py

Detected pattern matching password_literal. Rotate the credential and move to a secret manager.

django/contrib/auth/management/commands/changepassword.py:17 secrets

critical 9-layer security secrets conf 1.00 Possible secret in django/db/backends/oracle/creation.py

Detected pattern matching password_literal. Rotate the credential and move to a secret manager.

django/db/backends/oracle/creation.py:292 secrets

{# ── 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.