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

BigBill1418/DroneOpsCommand

https://github.com/BigBill1418/DroneOpsCommand · scanned 2026-06-17 01:21 UTC (1 month, 2 weeks ago)

183 raw signals (0 security + 183 graph)

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

Complete repo analysis

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

JSON
Combined
53.2
/100
Security checks
53
0 findings
System graph
53
100.0% cov · 163 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 18 Medium 15 Low 76 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 163 Crowd 0 Layer: Software 7 Network 4 Hardware 6 Security 17 Cicd 2 Quality 71 Api 56
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 53.2/100 with 100.0% coverage. It contains 2816 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 183 findings — concentrated in quality (90), api (56), security (17). Risk profile is high: 0 critical, 18 high, 27 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 108 of 163 actionable findings. 183 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 https://nominatim.openstreetmap.org/search?format=json&addressdetails=1&limit=5&countrycodes=us&q=${encodeURIComponent(query)} (frontend/src/pages/CustomerIntake.tsx:131)
`frontend/src/pages/CustomerIntake.tsx:131` calls `GET https://nominatim.openstreetmap.org/search?format=json&addressdetails=1&limit=5&countrycodes=us&q=${encodeURIComponent(query)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used f…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://nominatim.openstreetmap.org/search?format=json&addressdetails=1&limit=5&countrycodes=us&q=${encodeURIComponent(query)} (frontend/src/pages/Customers.tsx:104)
`frontend/src/pages/Customers.tsx:104` calls `GET https://nominatim.openstreetmap.org/search?format=json&addressdetails=1&limit=5&countrycodes=us&q=${encodeURIComponent(query)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://nominatim.openstreetmap.org/search?format=json&addressdetails=1&limit=5&countrycodes=us&q=${encodeURIComponent(query)} (frontend/src/pages/MissionDetailsEdit.tsx:186)
`frontend/src/pages/MissionDetailsEdit.tsx:186` calls `GET https://nominatim.openstreetmap.org/search?format=json&addressdetails=1&limit=5&countrycodes=us&q=${encodeURIComponent(query)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path us…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/refresh (frontend/src/api/client.ts:49)
`frontend/src/api/client.ts:49` calls `POST /api/auth/refresh` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/auth/refresh` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/flight-library/import/opendronelog/stream (frontend/src/pages/settings/FlightDataTab.tsx:160)
`frontend/src/pages/settings/FlightDataTab.tsx:160` calls `POST /api/flight-library/import/opendronelog/stream` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/flight-library/import/opendronelog/stream` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/intake/form/${token} (frontend/src/pages/CustomerIntake.tsx:257)
`frontend/src/pages/CustomerIntake.tsx:257` calls `POST /api/intake/form/${token}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/intake/form/<p>` If this points at an external API, prefix it with `https://` so the …
Dangling fetchAxios
high System graph security auth conf 1.00 FastAPI POST `accept_terms` without auth dependency — backend/app/routers/tos.py:123
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/tos.py:123 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `client_login` without auth dependency — backend/app/routers/client_portal.py:146
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/client_portal.py:146 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_client_balance_payment` without auth dependency — backend/app/routers/client_portal.py:634
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/client_portal.py:634 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_client_deposit_payment` without auth dependency — backend/app/routers/client_portal.py:559
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/client_portal.py:559 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_client_payment` without auth dependency — backend/app/routers/client_portal.py:725
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/client_portal.py:725 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `device_upload_flights_async` without auth dependency — backend/app/routers/flight_library.py:1102
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/flight_library.py:1102 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `device_upload_flights` without auth dependency — backend/app/routers/flight_library.py:1005
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/flight_library.py:1005 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `initial_setup` without auth dependency — backend/app/routers/auth.py:114
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/auth.py:114 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh` without auth dependency — backend/app/routers/auth.py:292
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/auth.py:292 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stripe_webhook` without auth dependency — backend/app/routers/stripe_webhook.py:49
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/stripe_webhook.py:49 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_intake_form` without auth dependency — backend/app/routers/intake.py:401
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/intake.py:401 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `validate_client_token` without auth dependency — backend/app/routers/client_portal.py:88
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/client_portal.py:88 securityAuth fastapi unauth mutation
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: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 9 occurrences Frontend route `/missions/new` has no Link/navigate to it — frontend/src/__tests__/missions.routes.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
9 occurrences
repo-level (9 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 5 occurrences Frontend route `/tos/accept` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
5 occurrences
repo-level (5 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/auto-merge-claude.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in backend/app/main.py:591
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
backend/app/main.py:591 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/api/client.ts:53
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/api/client.ts:53 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/hooks/useAuth.ts:49
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/hooks/useAuth.ts:49 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/pages/settings/AccountTab.tsx:58
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/pages/settings/AccountTab.tsx:58 Local storage auth token
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 92 placeholder/mock markers across 29 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 network Security conf 1.00 Privileged port 17 in use
Port 17 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/snapshot.sh Ports
medium System graph network Security conf 1.00 Privileged port 23 in use
Port 23 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/snapshot.sh Ports
medium System graph network Security conf 1.00 Privileged port 3 in use
Port 3 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/snapshot.sh Ports
medium System graph network Security conf 1.00 Privileged port 70 in use
Port 70 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/init-standby.sh Ports
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 14 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: debian:bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
flight-parser/Dockerfile:9 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx:alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:21 containersPinned dependencies
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.
frontend/Dockerfile:2 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: rust:1.85-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
flight-parser/Dockerfile:2 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 2 occurrences 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.
2 files, 2 locations
.github/workflows/auto-merge-claude.yml:16
.github/workflows/secret-scan.yml:30
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/routers/invoices.py:get_invoice, backend/app/routers/missions.py:get_mission This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
7 occurrences
repo-level (7 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/app/routers/flight_library.py:get_flight, backend/app/routers/flight_library.py:get_track, backend/app/routers/flight_library.py:delete_flight This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: backend/app/routers/client_portal.py:get_client_mission, backend/app/routers/client_portal.py:get_client_invoice, backend/app/routers/client_portal.py:create_client_deposit_payment, backend/app/routers/client_portal.py:create_client_balance_payment T…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `MissionWizardLegacy` in frontend/src/__tests__/missions.routes.test.tsx:27
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 quality Integrity conf 1.00 Old/deprecated-named symbol `MissionWizardLegacy` in frontend/src/App.tsx:29
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 quality Integrity conf 1.00 Old/deprecated-named symbol `my_backup` in backend/tests/test_backup_nonblocking.py:168
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 quality Integrity conf 1.00 Old/deprecated-named symbol `test_reuse_returns_none_when_session_too_old` in backend/tests/test_pay_idempotency.py:99
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 quality Integrity conf 1.00 Old/deprecated-named symbol `uploaded_backup` in backend/app/routers/backup.py:276
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: delete_rotation_hint
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/rotation_hint.py:93
low System graph software Dead code conf 1.00 Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/alembic/versions/0002_p2_p3_indexes.py:98
low System graph software Dead code conf 1.00 Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/alembic/versions/0001_baseline_schema.py:86
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_map_geojson
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/map_renderer.py:172
low System graph software Dead code conf 1.00 Possibly dead Python function: is_password_compliant
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/auth/jwt.py:54
low System graph software Dead code conf 1.00 Possibly dead Python function: render_static_map
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/map_renderer.py:222
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_password
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/auth/jwt.py:104
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /records/{record_id}
`backend/app/routers/maintenance.py` declares `DELETE /records/{record_id}` 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: DELETE /records/{record_id}/images/{image_idx}
`backend/app/routers/maintenance.py` declares `DELETE /records/{record_id}/images/{image_idx}` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /schedules/{schedule_id}
`backend/app/routers/maintenance.py` declares `DELETE /schedules/{schedule_id}` 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: DELETE /{mission_id}/invoice/items/{item_id}
`backend/app/routers/invoices.py` declares `DELETE /{mission_id}/invoice/items/{item_id}` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`backend/app/routers/flight_library.py` declares `GET /` 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 /airspace/aircraft
`backend/app/routers/flight_library.py` declares `GET /airspace/aircraft` 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 /api/branding
`backend/app/main.py` declares `GET /api/branding` 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 /api/demo/status
`backend/app/main.py` declares `GET /api/demo/status` 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 /api/health
`backend/app/main.py` declares `GET /api/health` 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 /device-health
`backend/app/routers/flight_library.py` declares `GET /device-health` 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 /device-upload/status/{batch_id}
`backend/app/routers/flight_library.py` declares `GET /device-upload/status/{batch_id}` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /due
`backend/app/routers/maintenance.py` declares `GET /due` 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 /next-due
`backend/app/routers/maintenance.py` declares `GET /next-due` 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 /parser/status
`backend/app/routers/flight_library.py` declares `GET /parser/status` 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 /records
`backend/app/routers/maintenance.py` declares `GET /records` 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 /reprocess/status
`backend/app/routers/flight_library.py` declares `GET /reprocess/status` 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 /schedules
`backend/app/routers/maintenance.py` declares `GET /schedules` 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 /schedules/{aircraft_id}
`backend/app/routers/maintenance.py` declares `GET /schedules/{aircraft_id}` 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 /stats/summary
`backend/app/routers/flight_library.py` declares `GET /stats/summary` 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 /telemetry-stats
`backend/app/routers/flight_library.py` declares `GET /telemetry-stats` 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 /uploads/{filename:path}
`backend/app/main.py` declares `GET /uploads/{filename:path}` 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 /{flight_id}
`backend/app/routers/flight_library.py` declares `GET /{flight_id}` 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 /{flight_id}/telemetry
`backend/app/routers/flight_library.py` declares `GET /{flight_id}/telemetry` 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 /{flight_id}/track
`backend/app/routers/flight_library.py` declares `GET /{flight_id}/track` 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 /{mission_id}/invoice
`backend/app/routers/invoices.py` declares `GET /{mission_id}/invoice` 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 /{mission_id}/report
`backend/app/routers/reports.py` declares `GET /{mission_id}/report` 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 /{mission_id}/report/status/{task_id}
`backend/app/routers/reports.py` declares `GET /{mission_id}/report/status/{task_id}` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/webhooks/stripe
`backend/app/routers/stripe_webhook.py` declares `POST /api/webhooks/stripe` 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 /backfill-aircraft
`backend/app/routers/flight_library.py` declares `POST /backfill-aircraft` 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 /defer-all-overdue
`backend/app/routers/maintenance.py` declares `POST /defer-all-overdue` 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 /device-upload
`backend/app/routers/flight_library.py` declares `POST /device-upload` 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 /device-upload/async
`backend/app/routers/flight_library.py` declares `POST /device-upload/async` 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 /records
`backend/app/routers/maintenance.py` declares `POST /records` 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 /records/{record_id}/images
`backend/app/routers/maintenance.py` declares `POST /records/{record_id}/images` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /reprocess
`backend/app/routers/flight_library.py` declares `POST /reprocess` 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 /reprocess/all
`backend/app/routers/flight_library.py` declares `POST /reprocess/all` 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 /schedules
`backend/app/routers/maintenance.py` declares `POST /schedules` 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 /schedules/{schedule_id}/skip
`backend/app/routers/maintenance.py` declares `POST /schedules/{schedule_id}/skip` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /seed-defaults
`backend/app/routers/maintenance.py` declares `POST /seed-defaults` 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 /{mission_id}/invoice
`backend/app/routers/invoices.py` declares `POST /{mission_id}/invoice` 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 /{mission_id}/invoice/items
`backend/app/routers/invoices.py` declares `POST /{mission_id}/invoice/items` 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 /{mission_id}/report/generate
`backend/app/routers/reports.py` declares `POST /{mission_id}/report/generate` 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 /{mission_id}/report/pdf
`backend/app/routers/reports.py` declares `POST /{mission_id}/report/pdf` 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 /{mission_id}/report/send
`backend/app/routers/reports.py` declares `POST /{mission_id}/report/send` 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: PUT /records/{record_id}
`backend/app/routers/maintenance.py` declares `PUT /records/{record_id}` 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: PUT /schedules/{schedule_id}
`backend/app/routers/maintenance.py` declares `PUT /schedules/{schedule_id}` 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: PUT /{mission_id}/invoice
`backend/app/routers/invoices.py` declares `PUT /{mission_id}/invoice` 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: PUT /{mission_id}/invoice/items
`backend/app/routers/invoices.py` declares `PUT /{mission_id}/invoice/items` 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: PUT /{mission_id}/invoice/items/{item_id}
`backend/app/routers/invoices.py` declares `PUT /{mission_id}/invoice/items/{item_id}` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /{mission_id}/report
`backend/app/routers/reports.py` declares `PUT /{mission_id}/report` 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: backend/app/routers/flight_library.py (2371 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/Dashboard.tsx (1207 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/Flights.tsx (1165 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/MissionWizardLegacy.tsx (1441 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/d341c8e4-c404-450e-aee9-dd852342671b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d341c8e4-c404-450e-aee9-dd852342671b/

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.