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.

scottring/symphonyOS

https://github.com/scottring/symphonyOS · scanned 2026-06-16 00:05 UTC (2 months, 3 weeks ago)

334 raw signals (8 security + 326 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 291 actionable findings from 2 signal sources. 80 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 · 286 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 4 Medium 108 Low 30 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 5 System graph 286 Crowd 0 Layer: Quality 130 Frontend 115 Security 45 Cicd 1

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 TODO/FIXME marker in shipping code — src/shell/LegacyDetailPanelHost.tsx:51
low Old/deprecated-named symbol `irisLegacy` in src/components/meals/day-detail/Day…
info Commented-code block (8 lines) in src/shell/LegacyDetailPanelHost.tsx:10

View all legacy markers findings →

Commented-out code 57 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 docs/design_handoff_onboarding_flow/design-ca…
info Commented-code block (5 lines) in docs/design_handoff_onboarding_flow/artboards…
info Commented-code block (6 lines) in vite/yaml-engine.ts:5
info Commented-code block (7 lines) in supabase/functions/places-proxy/index.ts:1
info Commented-code block (7 lines) in supabase/functions/extract-capture/index.ts:51
info Commented-code block (5 lines) in supabase/functions/extract-capture/lib/whatsa…
info Commented-code block (9 lines) in src/main.tsx:88
info Commented-code block (6 lines) in src/apps/tasks/TasksApp.tsx:13
info Commented-code block (5 lines) in src/apps/tasks/HomeViewContainer.tsx:3
info Commented-code block (5 lines) in src/apps/tasks/HorizonView.tsx:5
info Commented-code block (6 lines) in src/apps/tasks/index.ts:8
info Commented-code block (7 lines) in src/apps/tasks/TaskDetailPanel.tsx:59

View all commented-out code findings →

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

2 matching findings on this repo

high Agent instruction/config may expose a secret: .claude/commands/deploy.md .claude/commands/deploy.md:85
info Commented-code block (5 lines) in src/lib/cadence/config.ts:3

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/d1ed83f6-3113-44d7-ad9e-f2543b1d2f87/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d1ed83f6-3113-44d7-ad9e-f2543b1d2f87/

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.