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

ykh00046/Server_API

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

69 raw signals (0 security + 69 graph)

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

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 68 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
Combined
79.3
/100
Security checks
79
0 findings
System graph
79
88.9% cov · 68 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 8 Medium 5 Low 49 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 68 Crowd 0 Layer: Software 20 Network 2 Frontend 1 Security 9 Quality 16 Api 20
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 79.3/100 with 88.9% coverage. It contains 1367 nodes across 24 cross-layer flows, written primarily in mixed languages. Engine surfaced 69 findings — concentrated in software (20), api (20), quality (17). Risk profile is high: 0 critical, 8 high, 5 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 62 of 68 actionable findings. 69 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 security auth conf 1.00 FastAPI DELETE `delete_webhook` without auth dependency — api/routers/notifications.py:104
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/notifications.py:104 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_webhook` without auth dependency — api/routers/notifications.py:87
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/notifications.py:87 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `bulk_retry_deliveries` without auth dependency — api/routers/notifications.py:185
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/notifications.py:185 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `chat_stream` without auth dependency — api/chat.py:362
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/chat.py:362 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `chat_with_data` without auth dependency — api/chat.py:298
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/chat.py:298 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_webhook` without auth dependency — api/routers/notifications.py:65
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/notifications.py:65 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `retry_delivery` without auth dependency — api/routers/notifications.py:222
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/notifications.py:222 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `test_webhook` without auth dependency — api/routers/notifications.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.
api/routers/notifications.py:114 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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — manager.py:518
`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 network Security conf 1.00 Privileged port 10 in use
Port 10 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/ci.yml Ports
medium System graph network Security conf 1.00 Privileged port 71 in use
Port 71 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/ci.yml Ports
low System graph quality Integrity conf 1.00 15 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `API_BASE_URL`, `GEMINI_FALLBACK_ENABLED`, `GEMINI_FALLBACK_MODEL`, `GEMINI_MODEL`, `STREAM_BUFFER_FLUSH_MS`, `STREAM_HEARTBEAT_SEC`, `STREAM_TIMEOUT_SEC`, `WEBHOOK_BLOCKED_HOSTS` + 7 more. Add them (with a placeholder/comment) to .env.example so o…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 21 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 quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: api/notifications/deliveries_repo.py:list_retryable_delivery_ids, api/notifications/deliveries_repo.py:requeue_deliveries This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate o…
2 occurrences
repo-level (2 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 `_ensure_schema_v2` in api/notifications/_store_connection.py:97
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 `_ensure_schema_v2` in api/notifications/store.py:23
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 `Server_v1` in tools/watcher.py:21
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 `verify_backup` in tools/backup_db.py:97
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: apply_dark_mode_css
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
shared/ui/theme.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: cleanup_expired_sessions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/_session_store.py:82
low System graph software Dead code conf 1.00 Possibly dead Python function: convert_korean_time
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard/data.py:89
low System graph software Dead code conf 1.00 Possibly dead Python function: decorator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
shared/cache.py:116
low System graph software Dead code conf 1.00 Possibly dead Python function: ensure_import_path
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
shared/path_setup.py:29
low System graph software Dead code conf 1.00 Possibly dead Python function: filter
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
shared/logging_config.py:53
low System graph software Dead code conf 1.00 Possibly dead Python function: manual_db_check
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
manager.py:471
low System graph software Dead code conf 1.00 Possibly dead Python function: open_portal_settings
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
manager.py:593
low System graph software Dead code conf 1.00 Possibly dead Python function: render
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard/components/notifications.py:143
low System graph software Dead code conf 1.00 Possibly dead Python function: run_portal_now
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
manager.py:601
low System graph software Dead code conf 1.00 Possibly dead Python function: run_query
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/tools/custom.py:195
low System graph software Dead code conf 1.00 Possibly dead Python function: run_vacuum
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
shared/db_maintenance.py:237
low System graph software Dead code conf 1.00 Possibly dead Python function: setup_path_for_file
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
shared/path_setup.py:49
low System graph software Dead code conf 1.00 Possibly dead Python function: show_skeleton_chart
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard/components/loading.py:108
low System graph software Dead code conf 1.00 Possibly dead Python function: show_skeleton_kpi
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard/components/loading.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: show_skeleton_table
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard/components/loading.py:75
low System graph software Dead code conf 1.00 Possibly dead Python function: start_api
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
manager.py:553
low System graph software Dead code conf 1.00 Possibly dead Python function: start_portal
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
manager.py:574
low System graph software Dead code conf 1.00 Possibly dead Python function: start_web
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
manager.py:528
low System graph software Dead code conf 1.00 Possibly dead Python function: toast_warning
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard/components/notifications.py:85
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 api Wiring conf 1.00 Unused endpoint: DELETE /webhooks/{webhook_id}
`api/routers/notifications.py` declares `DELETE /webhooks/{webhook_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 /
`api/routers/system.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 /events
`api/routers/notifications.py` declares `GET /events` 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 /items
`api/routers/records.py` declares `GET /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: GET /queue/stats
`api/routers/notifications.py` declares `GET /queue/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 /records
`api/routers/records.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 /records/{item_code}
`api/routers/records.py` declares `GET /records/{item_code}` 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 /summary/by_item
`api/routers/summary.py` declares `GET /summary/by_item` 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 /summary/monthly_by_item
`api/routers/summary.py` declares `GET /summary/monthly_by_item` 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 /summary/monthly_total
`api/routers/summary.py` declares `GET /summary/monthly_total` 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 /webhooks
`api/routers/notifications.py` declares `GET /webhooks` 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 /webhooks/{webhook_id}
`api/routers/notifications.py` declares `GET /webhooks/{webhook_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 /webhooks/{webhook_id}/deliveries
`api/routers/notifications.py` declares `GET /webhooks/{webhook_id}/deliveries` 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: PATCH /webhooks/{webhook_id}
`api/routers/notifications.py` declares `PATCH /webhooks/{webhook_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 /
`api/chat.py` declares `POST /` 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 /deliveries/bulk-retry
`api/routers/notifications.py` declares `POST /deliveries/bulk-retry` 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 /deliveries/{delivery_id}/retry
`api/routers/notifications.py` declares `POST /deliveries/{delivery_id}/retry` 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 /stream
`api/chat.py` declares `POST /stream` 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 /webhooks
`api/routers/notifications.py` declares `POST /webhooks` 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 /webhooks/{webhook_id}/test
`api/routers/notifications.py` declares `POST /webhooks/{webhook_id}/test` 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/40c0c09b-2447-4996-b827-7317b6af7fcf/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/40c0c09b-2447-4996-b827-7317b6af7fcf/

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.