danielssj80/Elevator-maintenance-flow-demo-project — Repobility public scan

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

danielssj80/Elevator-maintenance-flow-demo-project

https://github.com/danielssj80/Elevator-maintenance-flow-demo-project · scanned 2026-06-17 01:52 UTC (1 month, 1 week ago)

41 raw signals (0 security + 41 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week 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

Security checks

100.0% cov · 39 findings

click to filter

Severity distribution — click a segment to filter

Active filters: 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 35 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

high System graph security auth conf 1.00 FastAPI POST `submit_report` without auth dependency — backend/app/routers/elevators.py:38

`@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/elevators.py:38 securityAuth fastapi unauth mutation

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/pages/Dashboard.tsx:31

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/pages/ElevatorDetail.tsx:18

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/pages/PostVisitReport.tsx:40

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/apply.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/opsx/apply.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/archive.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/opsx/archive.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/propose.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/opsx/propose.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/sync.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/opsx/sync.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/code-auditing/references/audit-methodology.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/skills/code-auditing/references/audit-methodology.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/enrich-us/SKILL.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/skills/enrich-us/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/meta-prompt/SKILL.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/skills/meta-prompt/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/update-docs/SKILL.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/skills/update-docs/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/using-git-worktrees/SKILL.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/skills/using-git-worktrees/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/writing-skills/SKILL.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/skills/writing-skills/SKILL.md VerificationClaude instruction

medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: .claude/skills/code-auditing/references/dead-code-methodology.md

Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.

.claude/skills/code-auditing/references/dead-code-methodology.md:56 Supply chainClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

medium System graph hardware Security conf 1.00 Dockerfile runs as root: frontend/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 2 occurrences Frontend route `/elevators/:id` 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.

2 occurrences

repo-level (2 hits)

Orphan pageWiring

medium System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned

aws-actions/configure-aws-credentials@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

.github/workflows/deploy.yml:23 CI/CD securitySupply chainGithub actions

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/deploy.yml CI/CD securitySupply chainGithub actions

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:7 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-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:1 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 2 occurrences 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.

lines 1, 6

backend/Dockerfile:1, 6 (2 hits)

containersPinned dependencies

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: backend/app/routers/elevators.py:get_elevator_service, backend/app/routers/elevators.py:get_elevator 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'r…

duplicatesduplication

low System graph quality License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated repo pattern

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in backend/app/services/elevator_service.py:32

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: do_run_migrations

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/alembic/env.py:40

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/638e311fa8e1_create_elevators_features_trend_points_.py:76

low System graph software Dead code conf 1.00 Possibly dead Python function: upgrade

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/alembic/versions/638e311fa8e1_create_elevators_features_trend_points_.py:21

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.