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.
Sign up free Scan another repo

chalf-ai/velocidad

https://github.com/chalf-ai/velocidad · scanned 2026-06-17 01:47 UTC (1 month, 1 week ago)

149 raw signals (0 security + 149 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
48.8
/100
Security checks
49
0 findings
System graph
49
100.0% cov · 146 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 17 Medium 17 Low 37 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 146 Crowd 0 Layer: Software 6 Frontend 60 Hardware 4 Security 10 Cicd 2 Quality 42 Api 22
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 48.8/100 with 100.0% coverage. It contains 2704 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 149 findings — concentrated in frontend (60), quality (42), api (22). Risk profile is high: 0 critical, 17 high, 20 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 71 of 146 actionable findings. 149 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/users (src/app/usuarios/page.tsx:352)
`src/app/usuarios/page.tsx:352` calls `GET /api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/gestion (src/lib/gestion/store.ts:145)
`src/lib/gestion/store.ts:145` calls `GET /api/gestion` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gestion` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/notificaciones${FILTRO_QS[filtro]} (src/app/notificaciones/page.tsx:85)
`src/app/notificaciones/page.tsx:85` calls `GET /api/notificaciones${FILTRO_QS[filtro]}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/notificaciones/<p>` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/snapshot/active?${qs} (src/lib/snapshot-client.ts:177)
`src/lib/snapshot-client.ts:177` calls `GET /api/snapshot/active?${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/snapshot/active` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/snapshot?fuente=BASE_STOCK (src/components/Header.tsx:26)
`src/components/Header.tsx:26` calls `GET /api/snapshot?fuente=BASE_STOCK` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/snapshot` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/usuarios-asignables (src/components/AsignarTareaModal.tsx:111)
`src/components/AsignarTareaModal.tsx:111` calls `GET /api/usuarios-asignables` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/usuarios-asignables` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/users/${user.id} (src/app/usuarios/page.tsx:236)
`src/app/usuarios/page.tsx:236` calls `PATCH /api/admin/users/${user.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/users/${user.id} (src/app/usuarios/page.tsx:362)
`src/app/usuarios/page.tsx:362` calls `PATCH /api/admin/users/${user.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/users/${user.id} (src/app/usuarios/page.tsx:376)
`src/app/usuarios/page.tsx:376` calls `PATCH /api/admin/users/${user.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/notificaciones/${a.id} (src/app/notificaciones/page.tsx:111)
`src/app/notificaciones/page.tsx:111` calls `PATCH /api/notificaciones/${a.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/notificaciones/<p>` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users (src/app/usuarios/page.tsx:93)
`src/app/usuarios/page.tsx:93` calls `POST /api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users/${user.id}/reset-password (src/app/usuarios/page.tsx:168)
`src/app/usuarios/page.tsx:168` calls `POST /api/admin/users/${user.id}/reset-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>/reset-password` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/snapshot (src/lib/snapshot-client.ts:136)
`src/lib/snapshot-client.ts:136` calls `POST /api/snapshot` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/snapshot` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/snapshots/daily (src/app/tendencias/GenerarSnapshotHoy.tsx:20)
`src/app/tendencias/GenerarSnapshotHoy.tsx:20` calls `POST /api/snapshots/daily` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/snapshots/daily` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/tareas (src/components/AsignarTareaModal.tsx:174)
`src/components/AsignarTareaModal.tsx:174` calls `POST /api/tareas` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tareas` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/gestion/${encodeURIComponent(vin)} (src/lib/gestion/store.ts:178)
`src/lib/gestion/store.ts:178` calls `PUT /api/gestion/${encodeURIComponent(vin)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gestion/<p>` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `receive_webhook` without auth dependency — agent/webhook.py:54
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent/webhook.py:54 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/gestion/store.ts:178
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/snapshot-client.ts:177
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: agent/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
aws-actions/configure-aws-credentials@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 25, 33, 58, 65
.github/workflows/deploy.yml:25, 33, 58, 65 (4 hits)
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in diag/diagnostico-conflicto-ffactura.mjs:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
diag/diagnostico-conflicto-ffactura.mjs:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in diag/diagnostico-conflicto-finscripcion.mjs:27
Found a known-risky pattern (node_child_process). Review and replace if possible.
diag/diagnostico-conflicto-finscripcion.mjs:27 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in diag/validar-consolidador-actas-mono-corte.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
diag/validar-consolidador-actas-mono-corte.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in diag/validar-consolidador-actas-vs-csv.mjs:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
diag/validar-consolidador-actas-vs-csv.mjs:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in diag/validar-consolidador-vs-csv.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
diag/validar-consolidador-vs-csv.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in diag/validar-cruce-vs-csv.mjs:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
diag/validar-cruce-vs-csv.mjs:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in diag/validar-parser-actas-vs-csv.mjs:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
diag/validar-parser-actas-vs-csv.mjs:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in diag/validar-parser-roma-vs-csv.mjs:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
diag/validar-parser-roma-vs-csv.mjs:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in diag/validar-vista-vs-cruce.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
diag/validar-vista-vs-cruce.mjs:15 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 35 placeholder/mock markers across 12 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
9 test file(s) for 361 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/components/historico/EjeTabs.tsx:54
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/components/historico/ModoProcesoToggle.tsx:58
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/components/historico/ProcesoSelector.tsx:65
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Maintenance conf 1.00 81 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 2367 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
agent/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/deploy.yml:22 CI/CD securitySupply chainGithub actions
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `sgLegacy` in src/lib/historico/calcular-scores-por-dia.ts:76
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/tools.py:195
low System graph software Dead code conf 1.00 Possibly dead Python function: enviar_briefings
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/cron.py:37
low System graph software Dead code conf 1.00 Possibly dead Python function: enviar_seguimiento
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/cron.py:61
low System graph software Dead code conf 1.00 Possibly dead Python function: generar_snapshot_diario
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/cron.py:99
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/webhook.py:73
low System graph software Dead code conf 1.00 Possibly dead Python function: tendencia_capital
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/tools.py:205
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — src/lib/historico/vista-derivados.ts:1286
React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…
Fq edge label no bg
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/audit-stock-propio.ts:53
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/diagnostico-atribucion-marca.ts:61
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/ejemplos-fecha-factura.ts:54
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/historico-backfill.ts:77
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/historico-recalcular.ts:48
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/validar-cuadratura-marca.ts:81
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/app/api/snapshot/route.ts:82
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET /debug/estado
`agent/webhook.py` declares `GET /debug/estado` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /debug/tareas
`agent/webhook.py` declares `GET /debug/tareas` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /debug/tareas/ciclo
`agent/webhook.py` declares `GET /debug/tareas/ciclo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /debug/user/{telefono}
`agent/webhook.py` declares `GET /debug/user/{telefono}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /webhook
`agent/webhook.py` declares `GET /webhook` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /webhook
`agent/webhook.py` declares `POST /webhook` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: src/app/capital-trabajo/page.tsx (1365 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/centro-accion/page.tsx (2507 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/dashboard/page.tsx (2923 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/facturados-no-entregados/page.tsx (1439 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/kia/page.tsx (1397 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/historico/__tests__/vista-derivados.test.ts (1588 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/historico/vista-derivados.ts (2428 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/a7aec5ed-ffcc-40d0-a18a-c8fbf945226f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a7aec5ed-ffcc-40d0-a18a-c8fbf945226f/

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.