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.

chngyicheng/pocket-teleop

https://github.com/chngyicheng/pocket-teleop · scanned 2026-06-17 01:47 UTC (1 month, 1 week ago)

48 raw signals (0 security + 48 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 47 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 14 Low 25 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 47 Crowd 0 Layer: Software 1 Frontend 8 Network 1 Hardware 2 Security 3 Quality 17 Api 15

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 51.4/100 with 77.8% coverage. It contains 507 nodes across 15 cross-layer flows, written primarily in mixed languages. Engine surfaced 48 findings — concentrated in quality (17), api (15), frontend (8). Risk profile is high: 0 critical, 2 high, 14 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 41 of 47 actionable findings. 48 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 /auth/session-status (web-client/src/hooks/useSessionStatus.ts:53)

`web-client/src/hooks/useSessionStatus.ts:53` calls `GET /auth/session-status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/session-status` If this points at an external API, prefix it with `https://` so the …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/heartbeat (web-client/src/hooks/useSessionStatus.ts:73)

`web-client/src/hooks/useSessionStatus.ts:73` calls `POST /auth/heartbeat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/heartbeat` If this points at an external API, prefix it with `https://` so the matcher s…

Dangling fetchFetch

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — web-client/src/perf_beacon.ts:65

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 — web-client/src/whep_client.ts:105

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: AGENTS.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.

AGENTS.md VerificationAgents md

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: auth-server/AGENTS.md

auth-server/AGENTS.md VerificationAgents md

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: server/AGENTS.md

server/AGENTS.md VerificationAgents md

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: video-bridge/AGENTS.md

video-bridge/AGENTS.md VerificationAgents md

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: web-client/AGENTS.md

web-client/AGENTS.md VerificationAgents md

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, ci. 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 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: Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in auth-server/views/change-password.html:72

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

auth-server/views/change-password.html:72 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in auth-server/views/login.html:69

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

auth-server/views/login.html:69 Direct innerhtml assignment

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

medium System graph network Security conf 1.00 Privileged port 123 in use

Port 123 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

mediamtx.yml Ports

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 6 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 2 occurrences Docker base image is tag-pinned but not digest-pinned: ros:humble

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

lines 2, 17

Dockerfile:2, 17 (2 hits)

containersPinned dependencies

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 software Dead code conf 1.00 Possibly dead Python function: generate_launch_description

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

server/launch/teleop.launch.py:8

low System graph frontend Frontend quality conf 1.00 React Flow <MiniMap> without dark background — web-client/src/views/MissionControl.tsx:536

A bare <MiniMap> renders with the vendor's white default in dark themes. Wrap the canvas in a class that overrides `.react-flow__minimap` background, or pass an explicit `style`/`maskColor`/`bgColor`. Why: P1 in CHECKLIST.md — vendor defaults bleed light through. Rule id: fq.minimap.no-bg

Fq minimap no bg

low System graph frontend Frontend quality conf 1.00 React Flow <MiniMap> without dark background — web-client/src/views/MissionTablet.tsx:614

Fq minimap no bg

low System graph frontend Frontend quality conf 1.00 React Flow <MiniMap> without dark background — web-client/test/shared.test.tsx:214

Fq minimap no bg

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — auth-server/src/app.ts:116

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — auth-server/src/index.ts:32

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — web-client/src/gamepad_handler.ts:94

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — web-client/src/views/MissionTablet.tsx:99

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

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

`auth-server/src/routes/auth.ts` declares `GET /change-password` 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 /login

`auth-server/src/routes/auth.ts` declares `GET /login` 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 /me

`auth-server/src/routes/auth.ts` declares `GET /me` 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 /session-status

`auth-server/src/routes/auth.ts` declares `GET /session-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: POST /change-password

`auth-server/src/routes/auth.ts` declares `POST /change-password` 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 /change-username

`auth-server/src/routes/auth.ts` declares `POST /change-username` 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 /heartbeat

`auth-server/src/routes/auth.ts` declares `POST /heartbeat` 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 /login

`auth-server/src/routes/auth.ts` declares `POST /login` 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 /logout

`auth-server/src/routes/auth.ts` declares `POST /logout` 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: USE /auth

`auth-server/src/app.ts` declares `USE /auth` 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: USE /auth-static

`auth-server/src/app.ts` declares `USE /auth-static` 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: USE /mediamtx-api

`auth-server/src/app.ts` declares `USE /mediamtx-api` 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: USE /video

`auth-server/src/app.ts` declares `USE /video` 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/94124fbc-4f52-46ee-a565-b987874b84bf/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/94124fbc-4f52-46ee-a565-b987874b84bf/

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.