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.

Abdo20-Jan/SUNSET-ERP-V4

https://github.com/Abdo20-Jan/SUNSET-ERP-V4 · scanned 2026-06-17 01:13 UTC (1 month, 2 weeks ago)

153 raw signals (0 security + 153 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +12.4 (diff) · 152 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 4 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.
4 matching findings on this repo
  • low Stray `console.log` in TS/JS — prisma/migrar-pagos-legacy-sunset.ts:52
  • low Old/deprecated-named symbol `crearDespachoLegacy` in src/lib/actions/despachos.…
  • info Commented-code block (5 lines) in prisma/migrar-pagos-legacy-sunset.ts:4
  • low Old/deprecated-named symbol `despachoLegacy` in test/crear-costo-despacho-cruza…
View all legacy markers findings →
Commented-out code 74 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 vitest.config.ts:7
  • info Commented-code block (6 lines) in src/app/api/cron/cleanup-despachos-borrador/r…
  • info Commented-code block (6 lines) in src/app/api/comex/divergencia/upload/route.ts…
  • info Commented-code block (5 lines) in src/app/(dashboard)/ventas/_components/venta-…
  • info Commented-code block (6 lines) in src/app/(dashboard)/comex/embarques/[id]/desp…
  • info Commented-code block (6 lines) in src/app/(dashboard)/comex/embarques/_componen…
  • info Commented-code block (5 lines) in src/app/(dashboard)/comex/embarques/_componen…
  • info Commented-code block (5 lines) in src/app/(dashboard)/comex/contenedores/[id]/i…
  • info Commented-code block (5 lines) in src/app/(dashboard)/tesoreria/movimientos/nue…
  • info Commented-code block (6 lines) in src/lib/format.ts:15
  • info Commented-code block (6 lines) in src/lib/services/percepcion-iibb.ts:8
  • info Commented-code block (5 lines) in src/lib/services/contenedor.ts:394
View all commented-out code findings →
Config drift 1 finding
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.
1 matching finding on this repo
  • info Commented-code block (5 lines) in vitest.config.ts:7
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/6ed183d0-7395-4b60-8083-3993dd2d80c7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6ed183d0-7395-4b60-8083-3993dd2d80c7/

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.