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.

ChefaneFabio/sportdb

https://github.com/ChefaneFabio/sportdb · scanned 2026-06-17 01:23 UTC (1 month, 2 weeks ago)

76 raw signals (0 security + 76 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -2.8 (diff) · 63 actionable findings from 1 signal source. 13 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 73.9/100 with 88.9% coverage. It contains 1998 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 76 findings — concentrated in quality (54), frontend (10), security (5). Risk profile is high: 2 critical, 0 high, 32 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 54 of 63 actionable findings. 76 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 Possible secret in backend/core/management/commands/import_bak.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/core/management/commands/import_bak.py:63
critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: backend/.env
`backend/.env` looks like a runtime dotenv file. It contains secret-looking assignments for SECRET_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.
backend/.env ConfigEnv fileRuntime env
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/layout.tsx:51
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/components/json-ld.tsx:13
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/app/uscite/gestione/page.tsx:724
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/app/uscite/page.tsx:164
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/lib/api.ts:38
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/lib/auth.ts:100
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security auth conf 1.00 Django CBV `CustomTokenObtainPairView` lacks `LoginRequiredMixin` — backend/users/views.py:23
Class-based view defines mutating methods (post/put/delete) without inheriting `LoginRequiredMixin`. If auth is enforced via `dispatch()` override or middleware, dismiss this finding.
backend/users/views.py:23 Auth django unauth view
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/app/layout.tsx:51
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/layout.tsx:51 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/components/json-ld.tsx:13
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/components/json-ld.tsx:13 Dangerous innerhtml
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for assignment in …` triggers a query per row — backend/output/views.py:284
The loop iterates a Django queryset and accesses `assignment.template.file_encoding` 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 i…
backend/output/views.py:284 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for assignment in …` triggers a query per row — backend/output/views.py:349
The loop iterates a Django queryset and accesses `assignment.template.file_encoding` 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 i…
backend/output/views.py:349 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for club in …` triggers a query per row — backend/core/management/commands/seed_data.py:497
The loop iterates a Django queryset and accesses `club.sports.all` 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 queries inst…
backend/core/management/commands/seed_data.py:497 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for group in …` triggers a query per row — backend/core/management/commands/seed_data.py:1123
The loop iterates a Django queryset and accesses `group.annual_championship.championship` 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 everyth…
backend/core/management/commands/seed_data.py:1123 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for group in …` triggers a query per row — backend/core/management/commands/seed_data.py:934
The loop iterates a Django queryset and accesses `group.teams.values_list` 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 quer…
backend/core/management/commands/seed_data.py:934 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for lp in …` triggers a query per row — backend/output/services.py:622
The loop iterates a Django queryset and accesses `lp.player.last_name` 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 queries …
backend/output/services.py:622 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — backend/api/viewsets/stats.py:261
The loop iterates a Django queryset and accesses `m.away_team.name` 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 queries ins…
backend/api/viewsets/stats.py:261 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — backend/core/management/commands/reset_demo.py:75
The loop iterates a Django queryset and accesses `m.objects.count` 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 queries inst…
backend/core/management/commands/reset_demo.py:75 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — backend/core/management/commands/reset_demo.py:87
The loop iterates a Django queryset and accesses `m.objects.all` 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 queries instea…
backend/core/management/commands/reset_demo.py:87 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — backend/core/management/commands/seed_data.py:1150
The loop iterates a Django queryset and accesses `m.result.home_score` 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 queries …
backend/core/management/commands/seed_data.py:1150 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — backend/core/management/commands/seed_data.py:1169
The loop iterates a Django queryset and accesses `m.result.away_score` 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 queries …
backend/core/management/commands/seed_data.py:1169 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — backend/core/management/commands/seed_data.py:1237
The loop iterates a Django queryset and accesses `m.result.home_score` 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 queries …
backend/core/management/commands/seed_data.py:1237 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — backend/core/management/commands/seed_data.py:1244
The loop iterates a Django queryset and accesses `m.result.home_score` 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 queries …
backend/core/management/commands/seed_data.py:1244 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — backend/core/management/commands/seed_data.py:1270
The loop iterates a Django queryset and accesses `m.result.home_score` 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 queries …
backend/core/management/commands/seed_data.py:1270 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for match in …` triggers a query per row — backend/output/services.py:476
The loop iterates a Django queryset and accesses `match.home_team.name` 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 queries…
backend/output/services.py:476 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for match in …` triggers a query per row — backend/output/services.py:584
The loop iterates a Django queryset and accesses `match.home_team.name` 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 queries…
backend/output/services.py:584 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for match in …` triggers a query per row — backend/output/services.py:765
The loop iterates a Django queryset and accesses `match.result.home_score` 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 quer…
backend/output/services.py:765 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for r in …` triggers a query per row — backend/core/management/commands/seed_data.py:931
The loop iterates a Django queryset and accesses `r.sport.slug` 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 queries instead…
backend/core/management/commands/seed_data.py:931 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for row in …` triggers a query per row — backend/api/viewsets/stats.py:287
The loop iterates a Django queryset and accesses `row.table.group` 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 queries inst…
backend/api/viewsets/stats.py:287 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for team in …` triggers a query per row — backend/core/management/commands/seed_data.py:513
The loop iterates a Django queryset and accesses `team.sport.slug` 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 queries inst…
backend/core/management/commands/seed_data.py:513 N plus onePerformance
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 89 placeholder/mock markers across 37 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 9 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CI`, `INTERNAL_API_HOST`, `NEXT_PUBLIC_SENTRY_DSN`, `NEXT_PUBLIC_SENTRY_ENVIRONMENT`, `NEXT_RUNTIME`, `SENTRY_DSN`, `SENTRY_ENVIRONMENT`, `SENTRY_ORG` + 1 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 11 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
41 tests / 327 src (ratio 0.13).
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 10 places
Functions with the same first-5-line body hash: backend/output/tests.py:setUp, backend/output/tests.py:setUp, backend/output/tests.py:setUp, backend/output/tests.py:setUp This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate …
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 14 places
Functions with the same first-5-line body hash: backend/gare/tests_gabriele.py:setUp, backend/gare/tests_gabriele.py:setUp, backend/gare/tests_gabriele.py:setUp, backend/gare/tests_gabriele.py:setUp This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai…
duplicatesduplication
low System graph quality Integrity conf 1.00 9 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/api/tests.py:test_filter_by_status, backend/api/tests.py:test_filter_by_status This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
9 occurrences
repo-level (9 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/api/viewsets/gare.py:perform_create, backend/api/viewsets/gare.py:perform_create, backend/api/viewsets/gare.py:perform_create This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). C…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: backend/api/viewsets/core.py:list, backend/api/viewsets/core.py:list, backend/api/viewsets/core.py:list, backend/api/viewsets/core.py:list This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygien…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: backend/api/tests.py:setUp, backend/api/tests.py:setUp, backend/api/tests.py:setUp, backend/api/tests.py:setUp This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document …
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: backend/api/tests_standings_flow.py:setUp, backend/api/tests_standings_flow.py:setUp, backend/api/tests_standings_flow.py:setUp, backend/api/tests_standings_flow.py:setUp This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — …
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `deactivateOld` in frontend/components/transfer-person.tsx:43
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_filenames
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/api/serializers/output.py:109
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_sections
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/api/serializers/output.py:47
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_teams
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/api/serializers/champs.py:50
low System graph quality Complexity conf 1.00 Very large file: backend/core/management/commands/seed_data.py (1285 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/0e3d8175-64a1-437b-ada0-2770a998b145/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0e3d8175-64a1-437b-ada0-2770a998b145/

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.