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.

thirstypig/TheFantasticLeagues

https://github.com/thirstypig/TheFantasticLeagues · scanned 2026-06-16 00:35 UTC (2 months, 2 weeks ago)

408 raw signals (17 security + 391 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 373 actionable findings from 2 signal sources. 154 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 365 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 15 Medium 34 Low 172 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 365 Crowd 0 Layer: Quality 207 Security 3 Cicd 2 Frontend 99 Api 62

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 1 finding

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 33 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

12 matching findings on this repo

info `truncate` class without `title=` for hover reveal — client/src/features/auctio…
low Very large file: client/src/features/teams/pages/TeamLegacy.tsx (1065 lines)
low Old/deprecated-named symbol `AuctionLegacy` in client/src/App.tsx:8
low Old/deprecated-named symbol `TeamLegacy` in client/src/pages/Changelog.tsx:99
low Old/deprecated-named symbol `HomeLegacy` in client/src/pages/Home.tsx:16
low Old/deprecated-named symbol `HomeLegacy` in client/src/pages/components/Histori…
low Old/deprecated-named symbol `HomeLegacy` in client/src/pages/components/NewsFee…
low Old/deprecated-named symbol `TeamLegacy` in client/src/features/transactions/li…
low Old/deprecated-named symbol `ActivityPageLegacy` in client/src/features/transac…
low Old/deprecated-named symbol `SeasonLegacy` in client/src/features/periods/compo…
low Old/deprecated-named symbol `PlayersLegacy` in client/src/features/players/page…
low Old/deprecated-named symbol `TeamLegacy` in client/src/features/teams/__tests__…

View all legacy markers findings →

Commented-out code 121 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (15 lines) in sync_db_to_csv.ts:6
info Commented-code block (5 lines) in client/src/test/setup.ts:4
info Commented-code block (5 lines) in client/src/components/GoogleSignInButton.tsx:…
info Commented-code block (8 lines) in client/src/components/AppShell.tsx:107
info Commented-code block (6 lines) in client/src/components/Sidebar.tsx:345
info Commented-code block (5 lines) in client/src/components/ui/ThemedTable.tsx:49
info Commented-code block (5 lines) in client/src/lib/extractServerError.ts:45
info Commented-code block (5 lines) in client/src/lib/__tests__/mlbStatus.test.ts:4
info Commented-code block (5 lines) in client/src/mobile/pages/MobileTeamMoveSheet.t…
info Commented-code block (5 lines) in client/src/mobile/pages/MobileTeam.tsx:440
info Commented-code block (7 lines) in client/src/pages/MyTeamRedirect.tsx:23
info Commented-code block (12 lines) in client/src/pages/components/MyTeamTodayPanel…

View all commented-out code findings →

Config drift 3 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

3 matching findings on this repo

low Stray `console.log` in TS/JS — scripts/verify_auth_config.ts:8
medium Insecure pattern 'node_child_process' in client/vite.config.ts:3 client/vite.config.ts:3
medium Runtime service client appears to use placeholder configuration

View all config drift findings →

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/10982991-fe96-4b85-964e-f0b30311ef45/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/10982991-fe96-4b85-964e-f0b30311ef45/

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.