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

ymjo140/rendezvous

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

120 raw signals (0 security + 120 graph)

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

Complete repo analysis

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

JSON
Combined
67.7
/100
Security checks
68
0 findings
System graph
68
100.0% cov · 114 findings
Critical
1
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 1 High 14 Medium 12 Low 76 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 114 Crowd 0 Layer: Software 11 Frontend 14 Security 17 Cicd 1 Quality 21 Api 50
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 67.7/100 with 100.0% coverage. It contains 1597 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 120 findings — concentrated in api (50), quality (27), security (17). Risk profile is high: 1 critical, 14 high, 12 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 103 of 114 actionable findings. 120 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.

critical System graph security Secrets conf 1.00 Possible secret in backend/src/services/user_service.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/src/services/user_service.py:123
high System graph security auth conf 1.00 FastAPI DELETE `delete_event` without auth dependency — backend/src/api/events.py:103
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/src/api/events.py:103 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_community_dummy` without auth dependency — backend/src/main.py:102
`@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/src/main.py:102 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_event` without auth dependency — backend/src/api/events.py:50
`@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/src/api/events.py:50 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `embed_all_places` without auth dependency — backend/src/api/routers/vector_ai.py:173
`@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/src/api/routers/vector_ai.py:173 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `embed_place` without auth dependency — backend/src/api/routers/vector_ai.py:136
`@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/src/api/routers/vector_ai.py:136 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `get_similar_places` without auth dependency — backend/src/api/routers/vector_ai.py:202
`@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/src/api/routers/vector_ai.py:202 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `kakao_callback_post` without auth dependency — backend/src/api/routers/auth.py:29
`@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/src/api/routers/auth.py:29 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `kakao_login` without auth dependency — backend/src/api/routers/auth.py:20
`@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/src/api/routers/auth.py:20 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `parse_schedule` without auth dependency — backend/src/api/routers/chat.py:231
`@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/src/api/routers/chat.py:231 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `run_meeting_flow` without auth dependency — backend/src/api/routers/meetings.py:258
`@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/src/api/routers/meetings.py:258 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_reservation_status` without auth dependency — backend/src/api/routers/reservations.py:55
`@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/src/api/routers/reservations.py:55 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sync_ical` without auth dependency — backend/src/api/routers/sync.py:32
`@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/src/api/routers/sync.py:32 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_business` without auth dependency — backend/src/api/routers/merchant.py:37
`@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/src/api/routers/merchant.py:37 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `vote_meeting` without auth dependency — backend/src/api/routers/meetings.py:262
`@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/src/api/routers/meetings.py:262 securityAuth fastapi unauth mutation
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — components/ui/chart.tsx:83
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — app/auth/callback/kakao/page.tsx:33
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 — app/onboarding/page.tsx:41
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 — app/places/[placeId]/page.tsx:381
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 — lib/api-client.ts:33
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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in components/ui/chart.tsx:83
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
components/ui/chart.tsx:83 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in app/auth/callback/kakao/page.tsx:41
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
app/auth/callback/kakao/page.tsx:41 Local storage auth token
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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 39 placeholder/mock markers across 18 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 193 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 286 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 7 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: make_2d_assets.py:new_img, components/ui/make_2d_assets.py:new_img 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.
7 occurrences
repo-level (7 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: backend/src/api/routers/game.py:get_game_profile, backend/src/api/routers/game.py:get_leaderboard, backend/src/api/routers/reservations.py:list_reservations, backend/src/api/routers/moderation.py:list_blocks This is *the* AI-coder failure mode (4× mo…
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 `home_tab_state_v1` in components/ui/home-tab.tsx:29
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 `rdv_decision_cell_v1` in lib/decision-cell.ts:14
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 `rule_based_v1` in backend/src/core/mlops.py:27
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: create_system_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/repositories/meeting_repository.py:63
low System graph software Dead code conf 1.00 Possibly dead Python function: predict_batch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/core/mlops.py:85
low System graph software Dead code conf 1.00 Possibly dead Python function: preferences_to_text
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/services/vector_embedding_service.py:199
low System graph software Dead code conf 1.00 Possibly dead Python function: reload_model
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/core/mlops.py:170
low System graph software Dead code conf 1.00 Possibly dead Python function: run_embedding
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/api/routers/vector_ai.py:184
low System graph software Dead code conf 1.00 Possibly dead Python function: score_places_batch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/core/mlops.py:214
low System graph software Dead code conf 1.00 Possibly dead Python function: search_places_by_keyword
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/repositories/meeting_repository.py:14
low System graph software Dead code conf 1.00 Possibly dead Python function: search_places_in_range
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/repositories/meeting_repository.py:22
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_calendar
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/services/sync_service.py:22
low System graph software Dead code conf 1.00 Possibly dead Python function: update_embedding_async
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/api/routers/vector_ai.py:494
low System graph software Dead code conf 1.00 Possibly dead Python function: use_coins
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/src/services/coin_service.py:47
low System graph quality Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
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 — components/ui/calendar-tab.tsx:166
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 — components/ui/chat-tab.tsx:26
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 — components/ui/discovery-tab.tsx:328
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 — components/ui/home-tab.tsx:144
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: DELETE /api/events/{event_id}
`backend/src/api/events.py` declares `DELETE /api/events/{event_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 /
`backend/src/main.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 /api/ai/recommendations
`backend/src/api/routers/ai_recommendations.py` declares `GET /api/ai/recommendations` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ai/recommendations/similar/{place_id}
`backend/src/api/routers/ai_recommendations.py` declares `GET /api/ai/recommendations/similar/{place_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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ai/stats
`backend/src/api/routers/ai_recommendations.py` declares `GET /api/ai/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 /api/auth/kakao/callback
`backend/src/api/routers/auth.py` declares `GET /api/auth/kakao/callback` 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/coins/wallet
`backend/src/api/routers/coins.py` declares `GET /api/coins/wallet` 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/communities
`backend/src/api/routers/community.py` declares `GET /api/communities` 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/events/
`backend/src/api/events.py` declares `GET /api/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 /api/game/leaderboard
`backend/src/api/routers/game.py` declares `GET /api/game/leaderboard` 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/game/profile
`backend/src/api/routers/game.py` declares `GET /api/game/profile` 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/offers/query
`backend/src/api/routers/offers.py` declares `GET /api/offers/query` 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/reservations
`backend/src/api/routers/reservations.py` declares `GET /api/reservations` 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/reservations/store/{place_id}
`backend/src/api/routers/reservations.py` declares `GET /api/reservations/store/{place_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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/shop/items
`backend/src/api/routers/users.py` declares `GET /api/shop/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 /api/users/me
`backend/src/api/routers/users.py` declares `GET /api/users/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 /api/vector/health
`backend/src/api/routers/vector_ai.py` declares `GET /api/vector/health` 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/vector/recommendation-metrics
`backend/src/api/routers/vector_ai.py` declares `GET /api/vector/recommendation-metrics` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/vector/recommendations
`backend/src/api/routers/vector_ai.py` declares `GET /api/vector/recommendations` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/vector/stats
`backend/src/api/routers/vector_ai.py` declares `GET /api/vector/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: POST /api/ai/actions
`backend/src/api/routers/ai_recommendations.py` declares `POST /api/ai/actions` 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/ai/recommendations
`backend/src/api/routers/ai_recommendations.py` declares `POST /api/ai/recommendations` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/ai/recommendations/click
`backend/src/api/routers/ai_recommendations.py` declares `POST /api/ai/recommendations/click` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/kakao
`backend/src/api/routers/auth.py` declares `POST /api/auth/kakao` 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/auth/kakao/callback
`backend/src/api/routers/auth.py` declares `POST /api/auth/kakao/callback` 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/auth/signup
`backend/src/api/routers/auth.py` declares `POST /api/auth/signup` 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/coins/charge
`backend/src/api/routers/coins.py` declares `POST /api/coins/charge` 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/coins/map-loot
`backend/src/api/routers/coins.py` declares `POST /api/coins/map-loot` 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/communities
`backend/src/api/routers/community.py` declares `POST /api/communities` 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/communities/{comm_id}/join
`backend/src/api/routers/community.py` declares `POST /api/communities/{comm_id}/join` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/communities_dummy
`backend/src/main.py` declares `POST /api/communities_dummy` 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/events/
`backend/src/api/events.py` declares `POST /api/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: POST /api/game/activity
`backend/src/api/routers/game.py` declares `POST /api/game/activity` 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/login
`backend/src/api/routers/auth.py` declares `POST /api/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 /api/offers/query
`backend/src/api/routers/offers.py` declares `POST /api/offers/query` 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/reservations
`backend/src/api/routers/reservations.py` declares `POST /api/reservations` 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/reservations/{reservation_id}/cancel
`backend/src/api/routers/reservations.py` declares `POST /api/reservations/{reservation_id}/cancel` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/reservations/{reservation_id}/status
`backend/src/api/routers/reservations.py` declares `POST /api/reservations/{reservation_id}/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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/shop/buy
`backend/src/api/routers/users.py` declares `POST /api/shop/buy` 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/sync/ical
`backend/src/api/routers/sync.py` declares `POST /api/sync/ical` 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/users/me/onboarding
`backend/src/api/routers/users.py` declares `POST /api/users/me/onboarding` 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/vector/embed-all-places
`backend/src/api/routers/vector_ai.py` declares `POST /api/vector/embed-all-places` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/vector/embed-place
`backend/src/api/routers/vector_ai.py` declares `POST /api/vector/embed-place` 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/vector/group-recommendations
`backend/src/api/routers/vector_ai.py` declares `POST /api/vector/group-recommendations` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/vector/interaction
`backend/src/api/routers/vector_ai.py` declares `POST /api/vector/interaction` 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/vector/similar-places
`backend/src/api/routers/vector_ai.py` declares `POST /api/vector/similar-places` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/vector/update-user-embedding
`backend/src/api/routers/vector_ai.py` declares `POST /api/vector/update-user-embedding` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/users/me
`backend/src/api/routers/users.py` declares `PUT /api/users/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: PUT /api/users/me/location
`backend/src/api/routers/users.py` declares `PUT /api/users/me/location` 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: PUT /api/users/me/preferences
`backend/src/api/routers/users.py` declares `PUT /api/users/me/preferences` 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 quality Complexity conf 1.00 Very large file: components/ui/discovery-tab.tsx (2502 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: components/ui/mypage-tab.tsx (1065 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/b0a8be17-bbf7-4c23-a800-a379f0b10c8c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b0a8be17-bbf7-4c23-a800-a379f0b10c8c/

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.