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.

teravinointelligence/Crm

https://github.com/teravinointelligence/Crm · scanned 2026-06-16 00:32 UTC (2 months, 2 weeks ago)

86 raw signals (0 security + 86 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 86 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 86 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 17 Low 13 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 86 Crowd 0 Layer: Api 1 Frontend 17 Security 1 Cicd 1 Quality 66

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

7 matching findings on this repo

low Old/deprecated-named symbol `is_legacy` in types/database.ts:28
low Old/deprecated-named symbol `is_legacy` in components/accounts/AccountForm.tsx:…
low Old/deprecated-named symbol `isLegacy` in components/cartera/RiesgoBadge.tsx:7
low Old/deprecated-named symbol `is_legacy` in app/api/cartera/[accountId]/pdf/rout…
low Old/deprecated-named symbol `is_legacy` in app/(app)/reparto/credito/page.tsx:29
low Old/deprecated-named symbol `is_legacy` in app/(app)/cartera/[accountId]/page.t…
low Old/deprecated-named symbol `isLegacy` in lib/cobranza.ts:67

View all legacy markers findings →

Commented-out code 39 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 (7 lines) in scripts/recordatorio-contactos-vendedores.mjs…
info Commented-code block (6 lines) in scripts/gen-plantilla-ventas.mjs:4
info Commented-code block (13 lines) in scripts/verify-incentivos-gb.mjs:6
info Commented-code block (5 lines) in scripts/migrate-reparto.mjs:10
info Commented-code block (8 lines) in scripts/snapshot-gb.mjs:1
info Commented-code block (6 lines) in components/ventas/ImportVentasClient.tsx:3
info Commented-code block (6 lines) in components/dashboard/ActivityCalendar.tsx:3
info Commented-code block (5 lines) in components/reparto/KanbanRutas.tsx:67
info Commented-code block (5 lines) in components/consignaciones/ConsignacionActions…
info Commented-code block (5 lines) in app/api/activities/calendar/route.ts:5
info Commented-code block (8 lines) in app/api/cron/clientes-inactivos/route.ts:1
info Commented-code block (5 lines) in app/api/reparto/diag/route.ts:1

View all commented-out code 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/7c9130ef-afa1-4732-84ef-071a7a9e72b3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7c9130ef-afa1-4732-84ef-071a7a9e72b3/

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.