affromero/flight-finder

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.

41 of your 166 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 6.14s · analysis 22.58s · 11.5 MB · GitHub preflight 411ms

https://github.com/affromero/flight-finder · scanned 2026-06-05 18:21 UTC (4 days, 19 hours ago) · 10 languages

389 raw signals (153 security + 236 graph) 44th percentile · Typescript · medium (20-100K LoC) System graph score 65 (higher by 2)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 19 hours ago · v2 · 205 actionable findings from 2 signal sources. 66 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 · 114 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	32.4	0.25	8.10
`testing_score`	95.0	0.20	19.00
`documentation_score`	86.1	0.15	12.91
`practices_score`	84.0	0.15	12.60
`code_quality`	59.5	0.10	5.95
Overall		1.00	67.6

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 47 Medium 38 Low 76 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 91 System graph 114 Crowd 0 Layer: Quality 64 Security 38 Software 69 Cicd 10 Api 1 Frontend 20 Network 1 Hardware 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 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `flightIdLegacy` in apps/web/src/lib/scraper/run-sc…

View all legacy markers findings →

Commented-out code 22 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 apps/web/src/middleware.ts:4
info Commented-code block (6 lines) in apps/web/src/test/llmock-setup.ts:25
info Commented-code block (5 lines) in apps/web/src/components/PriceHistory.test.tsx…
info Commented-code block (8 lines) in apps/web/src/app/api/analytics/track/route.ts…
info Commented-code block (7 lines) in apps/web/src/app/api/preview/route.ts:160
info Commented-code block (6 lines) in apps/web/src/app/api/queries/[id]/scrape/rout…
info Commented-code block (5 lines) in apps/web/src/app/admin/(dashboard)/layout.tsx…
info Commented-code block (5 lines) in apps/web/src/lib/admin-recovery.ts:5
info Commented-code block (5 lines) in apps/web/src/lib/preview-runner.ts:262
info Commented-code block (6 lines) in apps/web/src/lib/notifications/notify.ts:23
info Commented-code block (5 lines) in apps/web/src/lib/notifications/detect.ts:41
info Commented-code block (6 lines) in apps/web/src/lib/notifications/channels/email…

View all commented-out code findings →

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

4 matching findings on this repo

low File has no detected symbols: apps/web/vitest.config.ts
low File has no detected symbols: apps/web/src/lib/notifications/channels/config.te…
low File has no detected symbols: packages/cli/tsup.config.ts
medium `fetch()` without try/.catch or AbortSignal — apps/web/src/app/admin/(dashboard…

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/4263941a-5707-49ef-a12e-62529e923b9c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4263941a-5707-49ef-a12e-62529e923b9c/

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.