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.

rafaelpapanaklis/mediflow

https://github.com/rafaelpapanaklis/mediflow · scanned 2026-06-15 23:45 UTC (2 months, 4 weeks ago)

578 raw signals (93 security + 485 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 493 actionable findings from 2 signal sources. 238 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 · 485 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 3 Medium 89 Low 58 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 485 Crowd 0 Layer: Quality 364 Security 16 Api 1 Frontend 110 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.

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

5 matching findings on this repo

low Old/deprecated-named symbol `routeReservasLegacy` in src/components/dashboard/t…
low Old/deprecated-named symbol `brokenLegacy` in src/components/xrays/xray-ai-pane…
low Old/deprecated-named symbol `SeverityLegacy` in src/app/api/xrays/[id]/analyze/…
low Old/deprecated-named symbol `medicationsLegacy` in src/app/api/prescriptions/ro…
low Old/deprecated-named symbol `orthodonticsLegacy` in src/app/dashboard/patients/…

View all legacy markers findings →

Commented-out code 268 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 prisma/seed.ts:132
info Commented-code block (8 lines) in prisma/seeds/ortho-demo.ts:11
info Commented-code block (8 lines) in prisma/seeds/endodontics-mock.ts:9
info Commented-code block (6 lines) in src/middleware.ts:38
info Commented-code block (5 lines) in src/components/clinical/dental-form.tsx:187
info Commented-code block (7 lines) in src/components/laboratorios/order-chat-dock.t…
info Commented-code block (5 lines) in src/components/laboratorios/order-route-map.t…
info Commented-code block (10 lines) in src/components/paciente/reagendar-modal.tsx:3
info Commented-code block (7 lines) in src/components/paciente/cancelar-modal.tsx:6
info Commented-code block (13 lines) in src/components/paciente/portal-shell.tsx:3
info Commented-code block (6 lines) in src/components/paciente/auth/registro-form.ts…
info Commented-code block (5 lines) in src/components/paciente/auth/verificar-form.t…

View all commented-out code findings →

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

6 matching findings on this repo

medium Runtime service client appears to use placeholder configuration
info Commented-code block (7 lines) in src/app/api/admin/affiliates/config/route.ts:1
medium `fetch()` without try/.catch or AbortSignal — src/app/dashboard/landing/landing…
medium `fetch()` without try/.catch or AbortSignal — src/app/proveedores/(panel)/confi…
info Commented-code block (6 lines) in src/app/actions/orthodontics/updateRetentionR…
info Commented-code block (7 lines) in src/lib/reminders/config.ts:176

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/1f8d938d-0c23-43c1-8a7d-9f999f5713e2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1f8d938d-0c23-43c1-8a7d-9f999f5713e2/

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.