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.

YuekSebrina/pose

https://github.com/YuekSebrina/pose · scanned 2026-06-16 01:08 UTC (2 months, 1 week ago)

106 raw signals (0 security + 106 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 89 actionable findings from 1 signal source. 17 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
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 66.3/100 with 100.0% coverage. It contains 492 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 106 findings — concentrated in api (50), quality (26), software (21). Risk profile is low: 0 critical, 0 high, 7 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 88 of 89 actionable findings. 106 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.

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 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 'local_storage_auth_token' in frontend/src/views/login/index.vue:84
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/views/login/index.vue:84 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/api/version.py:187
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
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 cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 48 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
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 hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-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.
Dockerfile:2 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nvcr.io/nvidia/tensorrt:24.12-py3
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:27 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.
Dockerfile:14 containersPinned dependencies
low System graph quality Integrity conf 1.00 18 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/config.py:add_or_update, backend/config.py:delete 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.
18 occurrences
repo-level (18 hits)
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 `execute_async_v2` in backend/inference/trt_runtime.py:125
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: add_class_record
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/mqtt_client.py:680
low System graph software Dead code conf 1.00 Possibly dead Python function: add_or_update
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/config.py:85
low System graph software Dead code conf 1.00 Possibly dead Python function: add_student_daily_trajectory
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/mqtt_client.py:526
low System graph software Dead code conf 1.00 Possibly dead Python function: add_student_record
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/mqtt_client.py:717
low System graph software Dead code conf 1.00 Possibly dead Python function: area
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/face_features.py:51
low System graph software Dead code conf 1.00 Possibly dead Python function: check_and_send_records
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/mqtt_client.py:977
low System graph software Dead code conf 1.00 Possibly dead Python function: check_device
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/camera_monitor.py:19
low System graph software Dead code conf 1.00 Possibly dead Python function: dump_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/inference/trt_models.py:712
low System graph software Dead code conf 1.00 Possibly dead Python function: gen_uuid
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/utils/auth.py:14
low System graph software Dead code conf 1.00 Possibly dead Python function: length
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/frame_queue.py:51
low System graph software Dead code conf 1.00 Possibly dead Python function: manager_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/detection_pipeline.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: norm_crop2
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/inference/face_align.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_shape
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/inference/trt_runtime.py:37
low System graph software Dead code conf 1.00 Possibly dead Python function: predict
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/inference/trt_models.py:639
low System graph software Dead code conf 1.00 Possibly dead Python function: run_scheduler
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/mqtt_client.py:967
low System graph software Dead code conf 1.00 Possibly dead Python function: send_daily_stats
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/mqtt_client.py:919
low System graph software Dead code conf 1.00 Possibly dead Python function: square_crop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/inference/face_align.py:37
low System graph software Dead code conf 1.00 Possibly dead Python function: trans_points
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/inference/face_align.py:98
low System graph software Dead code conf 1.00 Possibly dead Python function: transform
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/inference/face_align.py:52
low System graph software Dead code conf 1.00 Possibly dead Python function: update_daily_stats
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/mqtt_client.py:792
low System graph software Dead code conf 1.00 Possibly dead Python function: upload_pending_images_batch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/mqtt_client.py:467
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/views/app/FacelibPhoto.vue:62
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: ANY /
`backend/app.py` declares `ANY /` 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: ANY /<path:path>
`backend/app.py` declares `ANY /<path: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: ANY /camera/<camera_ip>
`backend/api/cameras.py` declares `ANY /camera/<camera_ip>` 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: ANY /camera/add
`backend/api/cameras.py` declares `ANY /camera/add` 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: ANY /camera/edit
`backend/api/cameras.py` declares `ANY /camera/edit` 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: ANY /camera/list
`backend/api/cameras.py` declares `ANY /camera/list` 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: ANY /camera/reload
`backend/api/cameras.py` declares `ANY /camera/reload` 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: ANY /check-update
`backend/api/version.py` declares `ANY /check-update` 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: ANY /do-update
`backend/api/version.py` declares `ANY /do-update` 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: ANY /extract-face-features
`backend/api/facelib.py` declares `ANY /extract-face-features` 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: ANY /face-recognition-status
`backend/api/detection.py` declares `ANY /face-recognition-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: ANY /folders
`backend/api/results.py` declares `ANY /folders` 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: ANY /get-reference-images
`backend/api/reference.py` declares `ANY /get-reference-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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /get_grades
`backend/api/facelib.py` declares `ANY /get_grades` 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: ANY /grade_photos/<grade>
`backend/api/facelib.py` declares `ANY /grade_photos/<grade>` 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: ANY /hello
`backend/api/system.py` declares `ANY /hello` 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: ANY /image/<filename>
`backend/api/media.py` declares `ANY /image/<filename>` 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: ANY /image/<folder>/<filename>
`backend/api/media.py` declares `ANY /image/<folder>/<filename>` 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: ANY /images/<folder>
`backend/api/results.py` declares `ANY /images/<folder>` 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: ANY /infer-image
`backend/api/image_inference.py` declares `ANY /infer-image` 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: ANY /latest_photos
`backend/api/detection.py` declares `ANY /latest_photos` 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: ANY /list-reference-folders
`backend/api/reference.py` declares `ANY /list-reference-folders` 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: ANY /login
`backend/api/auth.py` declares `ANY /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: ANY /logout
`backend/api/auth.py` declares `ANY /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: ANY /mqtt/send_heartbeat
`backend/api/mqtt.py` declares `ANY /mqtt/send_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: ANY /mqtt/start
`backend/api/mqtt.py` declares `ANY /mqtt/start` 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: ANY /mqtt/stats
`backend/api/mqtt.py` declares `ANY /mqtt/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: ANY /mqtt/status
`backend/api/mqtt.py` declares `ANY /mqtt/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: ANY /mqtt/stop
`backend/api/mqtt.py` declares `ANY /mqtt/stop` 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: ANY /mqtt/sync_device
`backend/api/mqtt.py` declares `ANY /mqtt/sync_device` 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: ANY /photo/<filename>
`backend/api/media.py` declares `ANY /photo/<filename>` 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: ANY /photos/del_all
`backend/api/facelib.py` declares `ANY /photos/del_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: ANY /photos/del_batch
`backend/api/facelib.py` declares `ANY /photos/del_batch` 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: ANY /photos/del_class
`backend/api/facelib.py` declares `ANY /photos/del_class` 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: ANY /photos/del_grades
`backend/api/facelib.py` declares `ANY /photos/del_grades` 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: ANY /photos/export
`backend/api/facelib.py` declares `ANY /photos/export` 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: ANY /photos/upload
`backend/api/facelib.py` declares `ANY /photos/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: ANY /reference/<camera_ip>
`backend/api/reference.py` declares `ANY /reference/<camera_ip>` 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: ANY /reference_images/<folder>/<filename>
`backend/api/media.py` declares `ANY /reference_images/<folder>/<filename>` 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: ANY /restart
`backend/api/system.py` declares `ANY /restart` 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: ANY /restart-face-recognition
`backend/api/detection.py` declares `ANY /restart-face-recognition` 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: ANY /run-face-recognition
`backend/api/detection.py` declares `ANY /run-face-recognition` 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: ANY /run-reference
`backend/api/reference.py` declares `ANY /run-reference` 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: ANY /stop-face-recognition
`backend/api/detection.py` declares `ANY /stop-face-recognition` 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: ANY /student/trajectory
`backend/api/trajectory.py` declares `ANY /student/trajectory` 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: ANY /student/trajectory/cleanup
`backend/api/trajectory.py` declares `ANY /student/trajectory/cleanup` 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: ANY /student/trajectory/cleanup_student
`backend/api/trajectory.py` declares `ANY /student/trajectory/cleanup_student` 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: ANY /student/trajectory/multi_days
`backend/api/trajectory.py` declares `ANY /student/trajectory/multi_days` 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: ANY /update-status
`backend/api/version.py` declares `ANY /update-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: ANY /upload-face-lib
`backend/api/facelib.py` declares `ANY /upload-face-lib` 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/611cf562-737b-4256-8fef-3b35771df832/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/611cf562-737b-4256-8fef-3b35771df832/

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.