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.

dominiclu82/pilot-sync-mobile

https://github.com/dominiclu82/pilot-sync-mobile · scanned 2026-06-17 01:58 UTC (1 month, 1 week ago)

177 raw signals (0 security + 177 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -21.5 (diff) · 177 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 177 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 8 Medium 51 Low 96 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 177 Crowd 0 Layer: Frontend 28 Security 26 Quality 65 Api 58

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

2 matching findings on this repo

low Old/deprecated-named symbol `__legacy` in src/morning.ts:61
low Old/deprecated-named symbol `_copyLegacy` in src/spa/js-core.ts:859

View all legacy markers findings →

Commented-out code 18 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/health-check.mjs:2
info Commented-code block (10 lines) in src/server.ts:709
info Commented-code block (7 lines) in src/morning-builder.ts:379
info Commented-code block (5 lines) in src/atfm-nop.ts:1
info Commented-code block (5 lines) in src/morning.ts:4955
info Commented-code block (5 lines) in src/pilot-log/crew-slots.ts:1
info Commented-code block (6 lines) in src/pilot-log/tsv-parser.ts:3
info Commented-code block (5 lines) in src/pilot-log/schema.ts:234
info Commented-code block (11 lines) in src/pilot-log/import-addressbook.ts:9
info Commented-code block (6 lines) in src/pilot-log/import-roster.ts:4
info Commented-code block (10 lines) in src/pilot-log/import-logatp.ts:3
info Commented-code block (5 lines) in src/pilot-log/routes.ts:4

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/43f03be3-4f52-4e95-a408-b1e35477f627/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/43f03be3-4f52-4e95-a408-b1e35477f627/

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.