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

toydoxj/mornitoring

https://github.com/toydoxj/mornitoring · scanned 2026-06-16 00:41 UTC (2 months, 1 week ago)

129 raw signals (0 security + 129 graph)

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

Complete repo analysis

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

JSON
Combined
57.1
/100
Security checks
57
0 findings
System graph
57
100.0% cov · 95 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 3 Medium 8 Low 73 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 95 Crowd 0 Layer: Software 4 Frontend 9 Hardware 3 Security 7 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 57.1/100 with 100.0% coverage. It contains 1743 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 129 findings — concentrated in api (50), quality (29), software (27). Risk profile is high: 2 critical, 3 high, 8 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 85 of 95 actionable findings. 129 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 2 occurrences Possible secret in frontend/src/app/(dashboard)/audit/logins/page.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 36, 43
frontend/src/app/(dashboard)/audit/logins/page.tsx:36, 43 (2 hits)
high System graph security auth conf 1.00 FastAPI POST `find_account` without auth dependency — backend/routers/auth.py:654
`@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/routers/auth.py:654 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `link_account` without auth dependency — backend/routers/auth.py:499
`@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/routers/auth.py:499 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `setup_password` without auth dependency — backend/routers/auth.py:734
`@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/routers/auth.py:734 securityAuth fastapi unauth mutation
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .mcp.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.mcp.json VerificationMcp config
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/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/app/(auth)/kakao-callback/page.tsx:41
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/app/(auth)/kakao-callback/page.tsx:41 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/app/(auth)/link-account/page.tsx:57
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/app/(auth)/link-account/page.tsx:57 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/stores/authStore.ts:42
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/stores/authStore.ts:42 Local storage auth token
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 28 placeholder/mock markers across 19 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 7 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BACKUP_KMS_KEY_ID`, `BACKUP_LABEL`, `BACKUP_MIN_DUMP_BYTES`, `BACKUP_S3_PREFIX`, `ENVIRONMENT`, `NEXT_PUBLIC_API_URL`, `STRICT_RLS_HOOK`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
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 quality Debug conf 1.00 Debug logging residue appears in source files
Found 77 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 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.
backend/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-python@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 3 locations
.github/workflows/backend-ci.yml:24
.github/workflows/db-backup.yml:34
.github/workflows/frontend-ci.yml:24
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
36 tests / 167 src (ratio 0.22).
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/routers/notifications.py:list_my_notifications, backend/routers/reviews.py:list_my_inquiries This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they'r…
8 occurrences
repo-level (8 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/routers/kakao.py:unmatch_friend, backend/routers/kakao.py:unlink_kakao_oauth, backend/routers/kakao.py:diagnose_user_scopes This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Con…
2 occurrences
repo-level (2 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/routers/ledger.py:export_excel, backend/routers/buildings.py:get_stats, backend/routers/buildings.py:get_reviewer_names, backend/routers/buildings.py:reviewer_schedule This is *the* AI-coder failure mode (4× more duplication in vibe-coded rep…
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 `inquirystatus_old` in backend/alembic/versions/b1a7c3d49012_inquirystatus_next_phase_completed_통합.py:49
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 `list_objects_v2` in backend/services/s3_storage.py:103
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 `unified_old` in backend/routers/ledger.py:40
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: analyze_opinion_keywords
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/engines/review_keyword_analyzer.py:55
low System graph software Dead code conf 1.00 12 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
12 files, 12 locations
backend/alembic/versions/2179b4bec65d_review_stages에_inappropriate_note_컬럼_추가.py:28
backend/alembic/versions/388af05f7fc8_공지사항_및_댓글_테이블_추가.py:50
backend/alembic/versions/5f2c8a1d9e70_userrole_manager_추가.py:26
backend/alembic/versions/72fd6de98ff3_공지사항_첨부파일_테이블_추가.py:40
backend/alembic/versions/7f4d2c1a9b80_kakao_login_uuid_컬럼_추가.py:30
backend/alembic/versions/8d2b5c9f1a3e_dashboard_recent_indexes.py:49
backend/alembic/versions/934a1f38b94a_resulttype_대문자_라벨_추가.py:33
backend/alembic/versions/9c1a2b3d4e5f_notification_logs_sender_id.py:39
low System graph software Dead code conf 1.00 13 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
12 files, 12 locations
backend/alembic/versions/1ca5f9d0d398_kakao_link_sessions_테이블_추가.py:21
backend/alembic/versions/2179b4bec65d_review_stages에_inappropriate_note_컬럼_추가.py:21
backend/alembic/versions/388af05f7fc8_공지사항_및_댓글_테이블_추가.py:21
backend/alembic/versions/5f2c8a1d9e70_userrole_manager_추가.py:20
backend/alembic/versions/72fd6de98ff3_공지사항_첨부파일_테이블_추가.py:21
backend/alembic/versions/7f4d2c1a9b80_kakao_login_uuid_컬럼_추가.py:21
backend/alembic/versions/8d2b5c9f1a3e_dashboard_recent_indexes.py:22
backend/alembic/versions/934a1f38b94a_resulttype_대문자_라벨_추가.py:21
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_oauth_state
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/kakao.py:47
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 /api/discussions/attachments/{attachment_id}
`backend/routers/discussions.py` declares `DELETE /api/discussions/attachments/{attachment_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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/discussions/comment-attachments/{attachment_id}
`backend/routers/discussions.py` declares `DELETE /api/discussions/comment-attachments/{attachment_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 doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/discussions/comments/{comment_id}
`backend/routers/discussions.py` declares `DELETE /api/discussions/comments/{comment_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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/discussions/{discussion_id}
`backend/routers/discussions.py` declares `DELETE /api/discussions/{discussion_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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/users/{user_id}
`backend/routers/users.py` declares `DELETE /api/users/{user_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: DELETE /match/{user_id}
`backend/routers/kakao.py` declares `DELETE /match/{user_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: DELETE /oauth/{user_id}
`backend/routers/kakao.py` declares `DELETE /oauth/{user_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/auth/kakao/callback
`backend/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/auth/kakao/login
`backend/routers/auth.py` declares `GET /api/auth/kakao/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/auth/me
`backend/routers/auth.py` declares `GET /api/auth/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/auth/password-setup/validate
`backend/routers/auth.py` declares `GET /api/auth/password-setup/validate` 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/discussions
`backend/routers/discussions.py` declares `GET /api/discussions` 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/discussions/attachments/{attachment_id}/download
`backend/routers/discussions.py` declares `GET /api/discussions/attachments/{attachment_id}/download` 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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/discussions/comment-attachments/{attachment_id}/download
`backend/routers/discussions.py` declares `GET /api/discussions/comment-attachments/{attachment_id}/download` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/discussions/{discussion_id}
`backend/routers/discussions.py` declares `GET /api/discussions/{discussion_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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`backend/main.py` declares `GET /api/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/ledger/export
`backend/routers/ledger.py` declares `GET /api/ledger/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: GET /api/notifications
`backend/routers/notifications.py` declares `GET /api/notifications` 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/notifications/my
`backend/routers/notifications.py` declares `GET /api/notifications/my` 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
`backend/routers/users.py` declares `GET /api/users` 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/{user_id}
`backend/routers/users.py` declares `GET /api/users/{user_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 /friends
`backend/routers/kakao.py` declares `GET /friends` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /me/scopes
`backend/routers/kakao.py` declares `GET /me/scopes` 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 /reviewers
`backend/routers/kakao.py` declares `GET /reviewers` 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 /user/{user_id}/scopes
`backend/routers/kakao.py` declares `GET /user/{user_id}/scopes` 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 /api/discussions/comments/{comment_id}
`backend/routers/discussions.py` declares `PATCH /api/discussions/comments/{comment_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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/discussions/{discussion_id}
`backend/routers/discussions.py` declares `PATCH /api/discussions/{discussion_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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/users/{user_id}
`backend/routers/users.py` declares `PATCH /api/users/{user_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/auth/change-password
`backend/routers/auth.py` declares `POST /api/auth/change-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/find-account
`backend/routers/auth.py` declares `POST /api/auth/find-account` 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/link-account
`backend/routers/auth.py` declares `POST /api/auth/link-account` 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/login
`backend/routers/auth.py` declares `POST /api/auth/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/auth/password-setup
`backend/routers/auth.py` declares `POST /api/auth/password-setup` 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/discussions
`backend/routers/discussions.py` declares `POST /api/discussions` 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/discussions/comments/{comment_id}/attachments
`backend/routers/discussions.py` declares `POST /api/discussions/comments/{comment_id}/attachments` 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/discussions/{discussion_id}/attachments
`backend/routers/discussions.py` declares `POST /api/discussions/{discussion_id}/attachments` 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/discussions/{discussion_id}/comments
`backend/routers/discussions.py` declares `POST /api/discussions/{discussion_id}/comments` 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: POST /api/ledger/import
`backend/routers/ledger.py` declares `POST /api/ledger/import` 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/notifications/program-improvement
`backend/routers/notifications.py` declares `POST /api/notifications/program-improvement` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/notifications/review-reminder
`backend/routers/notifications.py` declares `POST /api/notifications/review-reminder` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/notifications/send
`backend/routers/notifications.py` declares `POST /api/notifications/send` 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
`backend/routers/users.py` declares `POST /api/users` 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/bulk-send-invite
`backend/routers/users.py` declares `POST /api/users/bulk-send-invite` 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/import-excel
`backend/routers/users.py` declares `POST /api/users/import-excel` 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/{user_id}/reset-password
`backend/routers/users.py` declares `POST /api/users/{user_id}/reset-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/users/{user_id}/send-consent-reminder
`backend/routers/users.py` declares `POST /api/users/{user_id}/send-consent-reminder` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/users/{user_id}/send-invite
`backend/routers/users.py` declares `POST /api/users/{user_id}/send-invite` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /login-uuids/sync
`backend/routers/kakao.py` declares `POST /login-uuids/sync` 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 /match
`backend/routers/kakao.py` declares `POST /match` 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 /tokens/refresh
`backend/routers/kakao.py` declares `POST /tokens/refresh` 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: backend/routers/buildings.py (1468 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/routers/reviews.py (1728 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/app/(dashboard)/admin/page.tsx (1822 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/lib/checklist-data.ts (1664 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/e47e0010-67e6-4f56-85e7-e941cd926d39/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e47e0010-67e6-4f56-85e7-e941cd926d39/

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.