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.

walcocer1982/sophia_next

https://github.com/walcocer1982/sophia_next · scanned 2026-06-16 00:54 UTC (2 months, 1 week ago)

83 raw signals (7 security + 76 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 82 actionable findings from 2 signal sources. 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 · 76 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 4 Medium 21 Low 32 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 6 System graph 76 Crowd 0 Layer: Quality 39 Security 3 Api 1 Frontend 37 Cicd 2

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.

Commented-out code 12 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:20
info Commented-code block (5 lines) in components/learning/tutor-mode.tsx:53
info Commented-code block (7 lines) in components/eval/assessment-session.tsx:148
info Commented-code block (5 lines) in app/api/dashboard/[courseId]/route.ts:94
info Commented-code block (5 lines) in app/api/chat/stream/route.ts:119
info Commented-code block (5 lines) in app/api/eval/[code]/start/route.ts:56
info Commented-code block (5 lines) in app/(protected)/select-section/page.tsx:35
info Commented-code block (5 lines) in app/(protected)/dashboard/[courseId]/[student…
info Commented-code block (5 lines) in app/(protected)/programacion/page.tsx:966
info Commented-code block (5 lines) in lib/prompt-builder.ts:235
info Commented-code block (6 lines) in lib/hallucination-detector.ts:84
info Commented-code block (5 lines) in hooks/use-voice-chat.ts:274

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

medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:1275
info Commented-code block (5 lines) in eslint.config.mjs:20

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/19b516fa-9b76-43be-95f4-6e6e37091257/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/19b516fa-9b76-43be-95f4-6e6e37091257/

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.