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.

dann1103-eng/caaa-app

https://github.com/dann1103-eng/caaa-app · scanned 2026-06-17 01:53 UTC (1 month, 1 week ago)

50 raw signals (0 security + 50 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -15.4 (diff) · 39 actionable findings from 1 signal source. 11 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 · 39 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 16 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 39 Crowd 0 Layer: Frontend 12 Network 1 Hardware 5 Security 4 Cicd 1 Quality 16

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

8 matching findings on this repo

low Stray `console.log` in TS/JS — legacy/CAA-backend/query.js:22
low Stray `console.log` in TS/JS — legacy/CAA-backend/run-sql.js:32
low Stray `console.log` in TS/JS — legacy/CAA-backend/server.js:93
low Stray `console.log` in TS/JS — legacy/CAA-backend/utils/mailer.js:39
low Stray `console.log` in TS/JS — legacy/CAA-backend/controllers/agendarController…
low Stray `console.log` in TS/JS — legacy/CAA-backend/controllers/admin/adminVueloC…
low Stray `console.log` in TS/JS — legacy/CAA-backend/services/metarService.js:161
medium Dockerfile runs as root: legacy/CAA-backend/Dockerfile

View all legacy markers findings →

Commented-out code 3 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/`.

3 matching findings on this repo

info Commented-code block (13 lines) in supabase/functions/administracion/index.ts:2…
info Commented-code block (5 lines) in supabase/functions/auth/index.ts:8
info Commented-code block (5 lines) in CAA-frontend/scripts/generate-config.mjs:1

View all commented-out code findings →

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

2 matching findings on this repo

medium Insecure pattern 'local_storage_auth_token' in CAA-frontend/src/api/axiosConfig… CAA-frontend/src/api/axiosConfig.js:52
info Commented-code block (5 lines) in CAA-frontend/scripts/generate-config.mjs:1

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/096f0f63-6c6b-460b-8ea6-4aeab41d5017/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/096f0f63-6c6b-460b-8ea6-4aeab41d5017/

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.