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.

TSandvaer/MarianLearning

https://github.com/TSandvaer/MarianLearning · scanned 2026-06-16 00:43 UTC (2 months, 1 week ago)

289 raw signals (0 security + 289 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 285 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 44 Low 50 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 285 Crowd 0 Layer: Frontend 19 Security 37 Cicd 2 Quality 227

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 2 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.

2 matching findings on this repo

low Old/deprecated-named symbol `hasLegacy` in src/screens/Math/planFromServer.ts:3…
low Old/deprecated-named symbol `skillLevelsWithLegacy` in src/lib/progress/storage…

View all legacy markers findings →

Commented-out code 187 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 (8 lines) in playwright.config.ts:34
info Commented-code block (5 lines) in vite.config.ts:81
info Commented-code block (5 lines) in tests/qa/noFlameInUI.test.ts:59
info Commented-code block (5 lines) in tests/qa/mathScreenAccessibility.test.tsx:184
info Commented-code block (8 lines) in api/_progressStore.ts:3
info Commented-code block (5 lines) in api/voice-qa-report.test.ts:106
info Commented-code block (8 lines) in api/_tts.ts:3
info Commented-code block (5 lines) in api/_planner.ts:3
info Commented-code block (7 lines) in api/_tts.test.ts:172
info Commented-code block (5 lines) in api/_sessionCache.test.ts:73
info Commented-code block (7 lines) in api/claude.test.ts:102
info Commented-code block (8 lines) in api/_canon.ts:3

View all commented-out code findings →

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

4 matching findings on this repo

high Agent instruction/config may expose a secret: .claude/docs/skill-trees-and-cont… .claude/docs/skill-trees-and-content.md:352
high Agent instruction/config may expose a secret: .claude/docs/progress-and-persist… .claude/docs/progress-and-persistence.md:162
info Commented-code block (8 lines) in playwright.config.ts:34
info Commented-code block (5 lines) in vite.config.ts:81

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/25c3ca1f-2283-42cf-87bf-0c9337fb19ea/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/25c3ca1f-2283-42cf-87bf-0c9337fb19ea/

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.