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.

danielssj80/Elevator-maintenance-flow-demo-project

https://github.com/danielssj80/Elevator-maintenance-flow-demo-project · scanned 2026-06-17 01:52 UTC (2 months, 4 weeks ago)

41 raw signals (0 security + 41 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v2 · last Δ -28.0 (diff) · 39 actionable findings from 1 signal source. 2 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: layer: api × excluding tests × Reset all

Severity: Critical 0 High 4 Medium 23 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 39 Crowd 0 Layer: Software 3 Hardware 4 Cicd 2 Quality 22 Security 2 Api 6

Exclude dismissed / FP Exclude test files

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.7/100 with 100.0% coverage. It contains 365 nodes across 10 cross-layer flows, written primarily in mixed languages. Engine surfaced 41 findings — concentrated in quality (23), api (6), hardware (5). Risk profile is high: 0 critical, 4 high, 24 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 6 of 39 actionable findings. 41 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/elevators (frontend/src/pages/Dashboard.tsx:31)

`frontend/src/pages/Dashboard.tsx:31` calls `GET /api/elevators` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/elevators` 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/elevators/${id} (frontend/src/pages/ElevatorDetail.tsx:18)

`frontend/src/pages/ElevatorDetail.tsx:18` calls `GET /api/elevators/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/elevators/<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: POST /api/elevators/${id}/report (frontend/src/pages/PostVisitReport.tsx:40)

`frontend/src/pages/PostVisitReport.tsx:40` calls `POST /api/elevators/${id}/report` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/elevators/<p>/report` If this points at an external API, prefix it with `https://` …

Dangling fetchFetch

low System graph api Wiring conf 1.00 Unused endpoint: GET /

`backend/app/routers/elevators.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 /{elevator_id}

`backend/app/routers/elevators.py` declares `GET /{elevator_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: POST /{elevator_id}/report

`backend/app/routers/elevators.py` declares `POST /{elevator_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

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/cd4c9ec5-3306-450a-88bd-a1eb87433eae/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cd4c9ec5-3306-450a-88bd-a1eb87433eae/

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.