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.
Sign up free Scan another repo

vedantgupta96/ScoutIQ

https://github.com/vedantgupta96/ScoutIQ · scanned 2026-06-16 00:48 UTC (2 months, 1 week ago)

54 raw signals (0 security + 54 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 40 actionable findings from 1 signal source. 14 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
80.6
/100
Security checks
81
0 findings
System graph
81
100.0% cov · 40 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 3 Medium 4 Low 29 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 40 Crowd 0 Layer: Software 4 Hardware 3 Security 4 Cicd 1 Quality 9 Api 19
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 80.6/100 with 100.0% coverage. It contains 745 nodes across 26 cross-layer flows, written primarily in mixed languages. Engine surfaced 54 findings — concentrated in api (19), software (14), quality (13). Risk profile is high: 0 critical, 3 high, 4 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 36 of 40 actionable findings. 54 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.

high System graph security auth conf 1.00 FastAPI POST `compare_contracts` without auth dependency — backend/scoutiq/api/routers/simulator.py:276
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/scoutiq/api/routers/simulator.py:276 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `simulate_cap` without auth dependency — backend/scoutiq/api/routers/simulator.py:242
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/scoutiq/api/routers/simulator.py:242 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `simulate_contract` without auth dependency — backend/scoutiq/api/routers/simulator.py:236
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/scoutiq/api/routers/simulator.py:236 securityAuth fastapi unauth mutation
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 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 Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
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 42 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: python:3.10-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:5 containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
12 tests / 84 src (ratio 0.14).
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/scoutiq/api/routers/players.py:get_player_cards, backend/scoutiq/api/routers/players.py:get_player 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 …
5 occurrences
repo-level (5 hits)
duplicatesduplication
low System graph software Dead code conf 1.00 6 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
6 files, 6 locations
backend/alembic/versions/0001_initial.py:90
backend/alembic/versions/0002_contracts.py:50
backend/alembic/versions/0003_player_current_team.py:31
backend/alembic/versions/0004_hot_path_indexes.py:45
backend/alembic/versions/0005_scout_reports.py:47
backend/alembic/versions/0006_player_rationales.py:37
low System graph software Dead code conf 1.00 Possibly dead Python function: predict_for_player
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scoutiq/model/predict.py:130
low System graph software Dead code conf 1.00 Possibly dead Python function: sort_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scoutiq/api/routers/players.py:573
low System graph software Dead code conf 1.00 6 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
6 files, 6 locations
backend/alembic/versions/0001_initial.py:19
backend/alembic/versions/0002_contracts.py:19
backend/alembic/versions/0003_player_current_team.py:18
backend/alembic/versions/0004_hot_path_indexes.py:17
backend/alembic/versions/0005_scout_reports.py:19
backend/alembic/versions/0006_player_rationales.py:19
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`backend/scoutiq/api/routers/teams.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest
`backend/scoutiq/api/routers/backtest.py` declares `GET /backtest` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/valuations
`backend/scoutiq/api/routers/backtest.py` declares `GET /backtest/valuations` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /cards
`backend/scoutiq/api/routers/players.py` declares `GET /cards` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /scout-ratings/eval
`backend/scoutiq/api/routers/llm_eval.py` declares `GET /scout-ratings/eval` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /valuation-cautions
`backend/scoutiq/api/routers/players.py` declares `GET /valuation-cautions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /watchlist
`backend/scoutiq/api/routers/players.py` declares `GET /watchlist` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{player_id}
`backend/scoutiq/api/routers/players.py` declares `GET /{player_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{player_id}/contract
`backend/scoutiq/api/routers/players.py` declares `GET /{player_id}/contract` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{player_id}/headshot
`backend/scoutiq/api/routers/headshots.py` declares `GET /{player_id}/headshot` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{player_id}/rationale
`backend/scoutiq/api/routers/players.py` declares `GET /{player_id}/rationale` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{player_id}/scout-ratings
`backend/scoutiq/api/routers/players.py` declares `GET /{player_id}/scout-ratings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{player_id}/similar
`backend/scoutiq/api/routers/players.py` declares `GET /{player_id}/similar` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{player_id}/valuation
`backend/scoutiq/api/routers/players.py` declares `GET /{player_id}/valuation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{team_id}/cap-sheet
`backend/scoutiq/api/routers/teams.py` declares `GET /{team_id}/cap-sheet` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{team_id}/logo
`backend/scoutiq/api/routers/teams.py` declares `GET /{team_id}/logo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /simulate/compare
`backend/scoutiq/api/routers/simulator.py` declares `POST /simulate/compare` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /simulate/contract
`backend/scoutiq/api/routers/simulator.py` declares `POST /simulate/contract` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /simulator/cap
`backend/scoutiq/api/routers/simulator.py` declares `POST /simulator/cap` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
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/3906da51-df3b-438a-860f-543571d47b30/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3906da51-df3b-438a-860f-543571d47b30/

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.