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.

tomaszsb/Game_alpha

https://github.com/tomaszsb/Game_alpha · scanned 2026-06-16 00:39 UTC (2 months, 1 week ago)

253 raw signals (0 security + 253 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 253 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 19 Low 109 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 253 Crowd 0 Layer: Software 5 Frontend 39 Hardware 2 Security 8 Cicd 1 Quality 153 Api 45

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.

Legacy markers 3 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.

3 matching findings on this repo

info Commented-code block (5 lines) in docs/archive/legacy_data/process_game_data.py…
low Old/deprecated-named symbol `code2026_cards_backup` in docs/archive/legacy_data…
low Old/deprecated-named symbol `code2026_cards_backup` in docs/archive/legacy_data…

View all legacy markers findings →

Commented-out code 119 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 (6 lines) in vite.config.ts:190
info Commented-code block (6 lines) in vitest.config.dev.ts:56
info Commented-code block (5 lines) in tests/integration/cardTextMatchesColumns.test…
info Commented-code block (7 lines) in tests/integration/TransactionalLoggingFlow.te…
info Commented-code block (11 lines) in tests/ghost/finalReviewStaleIntent.test.ts:5
info Commented-code block (7 lines) in tests/ghost/dataIntegrity.test.ts:128
info Commented-code block (10 lines) in tests/ghost/ghostPlayer.test.ts:63
info Commented-code block (6 lines) in tests/ghost/coverage.test.ts:137
info Commented-code block (7 lines) in tests/ghost/ghostPlayer.ts:341
info Commented-code block (5 lines) in tests/utils/buttonFormatting.test.ts:108
info Commented-code block (5 lines) in tests/utils/consoleCapture.test.ts:1
info Commented-code block (6 lines) in tests/components/NegotiationModal.test.tsx:203

View all commented-out code findings →

Config drift 8 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.

8 matching findings on this repo

low Stray `console.log` in TS/JS — vite.config.ts:85
medium Insecure pattern 'node_child_process' in vite.config.ts:4 vite.config.ts:4
high Agent instruction/config may expose a secret: docs/core/CLAUDE.md docs/core/CLAUDE.md:886
high Agent instruction/config may expose a secret: .claude/settings.local.json .claude/settings.local.json:234
info Commented-code block (6 lines) in vite.config.ts:190
info Commented-code block (6 lines) in vitest.config.dev.ts:56
low Old/deprecated-named symbol `show_ad_copy` in src/utils/remoteConfig.ts:26
high Dangling fetch: POST https://ntfy.sh/${CONFIG.NTFY_TOPIC} (server/server.js:438)

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/6b984db9-cd01-4857-b3b1-962176392d72/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6b984db9-cd01-4857-b3b1-962176392d72/

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.