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.

Stormrider66/Konditionsapp

https://github.com/Stormrider66/Konditionsapp · scanned 2026-06-16 00:25 UTC (2 months, 2 weeks ago)

585 raw signals (0 security + 585 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 577 actionable findings from 1 signal source. 8 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 · 577 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 1 Medium 191 Low 155 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 577 Crowd 0 Layer: Api 1 Frontend 273 Hardware 3 Security 14 Cicd 2 Quality 284

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 Stray `console.log` in TS/JS — scripts/audit-legacy-routes.ts:163
low Old/deprecated-named symbol `totalLegacy` in scripts/audit-legacy-routes.ts:164

View all legacy markers findings →

Commented-out code 48 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 (5 lines) in eslint.config.mjs:28
info Commented-code block (5 lines) in proxy.ts:430
info Commented-code block (6 lines) in next.config.ts:7
info Commented-code block (5 lines) in types/ai-models.ts:381
info Commented-code block (5 lines) in scripts/verify-percent-resolution.ts:110
info Commented-code block (6 lines) in components/programs/wizard/configuration-form…
info Commented-code block (6 lines) in components/agility-studio/AgilityWorkoutBuild…
info Commented-code block (5 lines) in components/coach/video-analysis/pose-analyzer…
info Commented-code block (5 lines) in components/athlete/AthleteTestProfileCard.tsx…
info Commented-code block (7 lines) in components/athlete/cardio/IntervalTimer.tsx:1…
info Commented-code block (5 lines) in components/athlete/cardio/CardioFocusModeWork…
info Commented-code block (5 lines) in components/athlete/strength/StrengthFocusMode…

View all commented-out code findings →

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

9 matching findings on this repo

low Stray `console.log` in TS/JS — scripts/qa-launch-config.ts:111
low Stray `console.log` in TS/JS — scripts/configure-hockey-beta.ts:65
info `truncate` class without `title=` for hover reveal — components/programs/wizard…
low Very large file: components/programs/wizard/ConfigurationForm.tsx (1425 lines)
info Commented-code block (5 lines) in eslint.config.mjs:28
info Commented-code block (6 lines) in next.config.ts:7
medium `fetch()` without try/.catch or AbortSignal — components/programs/wizard/Config…
info Commented-code block (6 lines) in components/programs/wizard/configuration-form…
info Commented-code block (6 lines) in lib/ai/user-ai-config.ts:118

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/49942676-f5e6-4e4e-8e39-b67c659b942d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/49942676-f5e6-4e4e-8e39-b67c659b942d/

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.