critical System graph security Secrets conf 1.00 Possible secret in backend/scripts/check_missing_tables.py

Detected pattern matching password_literal. Rotate the credential and move to a secret manager.

backend/scripts/check_missing_tables.py:27

critical System graph security Secrets conf 1.00 Possible secret in backend/scripts/create_samba_jobs.py

Detected pattern matching password_literal. Rotate the credential and move to a secret manager.

backend/scripts/create_samba_jobs.py:10

critical System graph security Secrets conf 1.00 Possible secret in backend/scripts/fill_missing_category_mappings.py

Detected pattern matching password_literal. Rotate the credential and move to a secret manager.

backend/scripts/fill_missing_category_mappings.py:204

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/auth/session (frontend/src/lib/api.ts:94)

`frontend/src/lib/api.ts:94` calls `DELETE /api/auth/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/session` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /product/info?prdtNo=${prdtNo} (extension/background-sourcing.js:2666)

`extension/background-sourcing.js:2666` calls `GET /product/info?prdtNo=${prdtNo}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/product/info` If this points at an external API, prefix it with `https://` so the mat…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:51425/device_id (frontend/src/app/samba/warroom/page.tsx:633)

`frontend/src/app/samba/warroom/page.tsx:633` calls `GET http://localhost:51425/device_id` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:51425/device_id` If this points at an external API, prefix it…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET https://${subdomain}/product/info?prdtNo=${productId} (extension/background-sourcing.js:2450)

`extension/background-sourcing.js:2450` calls `GET https://${subdomain}/product/info?prdtNo=${productId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>/product/info` If this points at an external API, pr…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET https://${subdomain}/product/info?prdtNo=${productId} (extension/background-sourcing.js:2519)

`extension/background-sourcing.js:2519` calls `GET https://${subdomain}/product/info?prdtNo=${productId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>/product/info` If this points at an external API, pr…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET https://httpbin.org/ip (frontend/src/app/samba/settings/hooks/useProxySettings.ts:80)

`frontend/src/app/samba/settings/hooks/useProxySettings.ts:80` calls `GET https://httpbin.org/ip` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/httpbin.org/ip` If this points at an external API, prefix it wi…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET https://pbf.lotteon.com/product/v2/detail/search/base/sitm/${sitmNo} (extension/background-sourcing.js:2393)

`extension/background-sourcing.js:2393` calls `GET https://pbf.lotteon.com/product/v2/detail/search/base/sitm/${sitmNo}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/pbf.lotteon.com/product/v2/detail/search…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.musinsa.com/order-service/my/order/get_order_view/${ordNo} (extension/background-sourcing.js:1727)

`extension/background-sourcing.js:1727` calls `GET https://www.musinsa.com/order-service/my/order/get_order_view/${ordNo}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.musinsa.com/order-service/my/order…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/session (frontend/src/lib/api.ts:67)

`frontend/src/lib/api.ts:67` calls `POST /api/auth/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/session` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph security auth conf 1.00 FastAPI POST `analyze_full` without auth dependency — backend/backend/api/v1/routers/samba/ai_sourcing.py:76

`@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/backend/api/v1/routers/samba/ai_sourcing.py:76 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `brand_discover` without auth dependency — backend/backend/api/v1/routers/samba/collector_collection/brands.py:428

`@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/backend/api/v1/routers/samba/collector_collection/brands.py:428 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `clear_collect_log_buffer` without auth dependency — backend/backend/api/v1/routers/samba/job.py:411

`@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/backend/api/v1/routers/samba/job.py:411 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `ebay_deletion_notification` without auth dependency — backend/backend/api/v1/routers/ebay.py:51

`@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/backend/api/v1/routers/ebay.py:51 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `get_product_detail_with_cookies` without auth dependency — backend/backend/api/v1/routers/samba/naverstore_sourcing.py:130

`@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/backend/api/v1/routers/samba/naverstore_sourcing.py:130 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `get_product_details_batch` without auth dependency — backend/backend/api/v1/routers/samba/naverstore_sourcing.py:148

`@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/backend/api/v1/routers/samba/naverstore_sourcing.py:148 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `kill_idle_in_transaction` without auth dependency — backend/backend/api/v1/routers/samba/db_pool.py:47

`@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/backend/api/v1/routers/samba/db_pool.py:47 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `kream_collect_result` without auth dependency — backend/backend/api/v1/routers/samba/proxy/kream.py:128

`@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/backend/api/v1/routers/samba/proxy/kream.py:128 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `kream_search_result` without auth dependency — backend/backend/api/v1/routers/samba/proxy/kream.py:171

`@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/backend/api/v1/routers/samba/proxy/kream.py:171 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `rebuild_exported_rules_endpoint` without auth dependency — backend/backend/api/v1/routers/samba/category.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/backend/api/v1/routers/samba/category.py:231 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `receive_collect_result` without auth dependency — backend/backend/api/v1/routers/samba/ai_sourcing.py:774

`@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/backend/api/v1/routers/samba/ai_sourcing.py:774 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `receive_ranking_data` without auth dependency — backend/backend/api/v1/routers/samba/ai_sourcing.py:588

`@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/backend/api/v1/routers/samba/ai_sourcing.py:588 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `search_issues` without auth dependency — backend/backend/api/v1/routers/samba/sns_posting.py:195

`@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/backend/api/v1/routers/samba/sns_posting.py:195 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `test_collect` without auth dependency — backend/backend/api/v1/routers/samba/ai_sourcing.py:812

`@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/backend/api/v1/routers/samba/ai_sourcing.py:812 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `test_proxy_connection` without auth dependency — backend/backend/api/v1/routers/samba/proxy/config.py:92

`@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/backend/api/v1/routers/samba/proxy/config.py:92 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `test_rate_limit` without auth dependency — backend/backend/api/v1/routers/samba/collector_refresh.py:900

`@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/backend/api/v1/routers/samba/collector_refresh.py:900 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `upload_preset_image` without auth dependency — backend/backend/api/v1/routers/samba/proxy/preset_images.py:38

`@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/backend/api/v1/routers/samba/proxy/preset_images.py:38 securityAuth fastapi unauth mutation

high System graph security security conf 1.00 Insecure pattern 'eval_used' in extension/recipe-executor.js:112

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

extension/recipe-executor.js:112 Eval used

high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: frontend/.env.production

`frontend/.env.production` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.

frontend/.env.production ConfigEnv fileRuntime env

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — extension/background-autologin.js:89

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 — extension/background-core.js:70

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 — extension/background-sourcing.js:421

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 — extension/background.js:268

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 — extension/content-musinsa-claimlist.js:7

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 — extension/content-reward-musinsa-attendance.js:36

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 — extension/offscreen-cancel.js:24

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 — extension/recipe-executor.js:109

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 — frontend/src/lib/api.ts:171

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 — frontend/src/lib/samba/api/license.ts:13

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 — frontend/src/lib/samba/legacy.ts:38

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: frontend/.claude/settings.local.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.

frontend/.claude/settings.local.json VerificationClaude instruction

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 lockfile. 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 cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned

astral-sh/setup-uv@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

2 files, 3 locations

.github/workflows/deploy-vm.yml:37, 42 (2 hits)

.github/workflows/alembic-check.yml:29

CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in backend/backend/api/v1/routers/samba/proxy/config.py:217

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

backend/backend/api/v1/routers/samba/proxy/config.py:217 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in backend/backend/api/v1/routers/samba/proxy/kream.py:294

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

backend/backend/api/v1/routers/samba/proxy/kream.py:294 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in tools/lotteon_daemon/daemon.py:2558

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

tools/lotteon_daemon/daemon.py:2558 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in extension/background-sourcing.js:3831

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

extension/background-sourcing.js:3831 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/app/samba/login/page.tsx:29

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

frontend/src/app/samba/login/page.tsx:29 Local storage auth token

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/scripts/check_migrations.py:17

`subprocess.run(...)` 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 quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 615 placeholder/mock markers across 54 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

39 test file(s) for 788 source file(s) (ratio 0.05). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Integrity conf 1.00 61 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `ALEMBIC_PRODUCTION_CONFIRMED`, `API_GATEWAY_KEY`, `APPDATA`, `AUTOTUNE_CYCLE_BATCH`, `AUTOTUNE_SOLDOUT_REASSERT_SEC`, `AUTOTUNE_TRANSMIT_MAX_CONCURRENCY`, `BACKEND_URL`, `BACKFILL_MAX` + 53 more. Add them (with a placeholder/comment) to .env.examp…

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 730 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.3-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:2 containersPinned dependencies

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/samba/collector/components/AiSourcingModal.tsx:69

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/samba/collector/components/DuplicatesModal.tsx:222

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/samba/manual-products/components/ImageManagerModal.tsx:83

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/samba/orders/components/AlarmSettingModal.tsx:58

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/samba/orders/components/OrderEditModal.tsx:38

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/samba/orders/components/PriceHistoryModal.tsx:47

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/samba/orders/components/TrackingModal.tsx:99

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/samba/orders/components/UrlInputModal.tsx:25

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/samba/returns/components/ReturnDetailModal.tsx:22

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 16 places

Functions with the same first-5-line body hash: backend/alembic/versions/4c81abda9e0e_samba_return에_customer_phone_check_date_.py:downgrade, backend/alembic/versions/z_add_return_phone_sourcing_cells.py:downgrade, backend/alembic/versions/zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz_backfill_market_accoun…

duplicatesduplication

low System graph quality Integrity conf 1.00 10 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: deploy/kill_idle.py:main, backend/scripts/backfill_tenant_isolation.py:main 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.

10 occurrences

repo-level (10 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: tools/snkr_build_idx.py:main, backend/scripts/create_tetris_board_idx.py:main, backend/scripts/collect_lottehome_orders.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consoli…

5 occurrences

repo-level (5 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places

Functions with the same first-5-line body hash: backend/scripts/validate_cs_classifier.py:main, backend/scripts/tracking_health_check.py:main, backend/scripts/ssg_discriminate.py:main, backend/scripts/ssg_tracking_detail.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-code…

2 occurrences

repo-level (2 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 6 places

Functions with the same first-5-line body hash: backend/alembic/versions/ad3d158aae34_merge_all_heads_for_autotune_fix.py:upgrade, backend/alembic/versions/37fd18b908e6_merge_heads_before_perf_index.py:upgrade, backend/alembic/versions/b3786b6834dc_merge_coupang_and_sourcing_order_heads.py:upgrade,…

2 occurrences

repo-level (2 hits)

duplicatesduplication

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

package.json LockfileReproducibilityGenerated repo pattern

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_disp_old` in backend/backend/api/v1/routers/samba/collector_autotune.py:2345

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 `_mp_copy` in backend/backend/domain/samba/shipment/service.py:1886

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 `exists_old` in backend/alembic/versions/zzzzzzzzzzzzzzzzzzzzzzzzzzzzzz_order_unique_with_seq.py:41

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 `female_v1` in backend/backend/api/v1/routers/samba/proxy/ai_tools.py:376

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 `female_v1` in backend/backend/domain/samba/image/service.py:50

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 `get_categories_v2` in backend/backend/domain/samba/category/sync_service.py:730

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 `get_categories_v2` in backend/backend/domain/samba/proxy/ssg.py:844

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 `is_legacy` in backend/backend/domain/samba/tetris/service.py:577

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 `is_legacy` in backend/backend/dtos/samba/tetris.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 `is_legacy` in frontend/src/app/samba/policies/tetris/UnassignedPool.tsx:113

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 `is_legacy` in frontend/src/app/samba/policies/tetris/useTetris.ts:93

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 `is_legacy` in frontend/src/lib/samba/api/tetris.ts:18

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 `onRemoveLegacy` in frontend/src/app/samba/policies/tetris/AccountBlock.tsx:250

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 `onRemoveLegacy` in frontend/src/app/samba/policies/tetris/BrandBlock.tsx:19

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 `product_copy` in backend/backend/domain/samba/plugins/markets/auction.py:192

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 `product_copy` in backend/backend/domain/samba/plugins/markets/cafe24.py:204

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 `product_copy` in backend/backend/domain/samba/plugins/markets/gmarket.py:193

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 `product_copy` in backend/backend/domain/samba/plugins/markets/lotteon.py:955

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 `product_copy` in backend/backend/domain/samba/plugins/markets/smartstore.py:136

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 `regs_old` in backend/backend/api/v1/routers/samba/shipment.py:968

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 `regs_old` in backend/backend/domain/samba/proxy/elevenst_ghost_reconciler.py:297

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 `regs_old` in backend/backend/domain/samba/proxy/ssg_status_reconciler.py:175

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 `samba_active_accounts_v1` in frontend/src/lib/samba/legacy.ts:1099

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 `t_old` in backend/backend/domain/samba/job/progress_tracker.py:41

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 `t_PDP_1280_v1` in backend/backend/domain/samba/proxy/nike.py:617

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 `uq_scp_tenant_source_product_v2` in backend/alembic/versions/zzzzzzzzzzzzzzz_dedupe_collected_product_unique.py:12

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 `uq_scp_tenant_source_product_v2` in backend/backend/domain/samba/collector/model.py:141

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 `v1_v2` in backend/backend/domain/samba/proxy/lotteon/detail_client.py:411

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: do_GET

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

tools/lotteon_daemon/daemon.py:2563

low System graph software Dead code conf 1.00 Possibly dead Python function: do_OPTIONS

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

tools/lotteon_daemon/daemon.py:2556

low System graph software Dead code conf 1.00 Possibly dead Python function: do_run_migrations

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

backend/alembic/env.py:100

low System graph software Dead code conf 1.00 10 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.

10 files, 10 locations

backend/alembic/versions/4f3493e4d2ef_add_source_url_to_samba_order.py:25

backend/alembic/versions/7c423005e6ab_add_market_product_nos_to_collected_.py:30

backend/alembic/versions/8355b1006c94_add_free_shipping_and_same_day_delivery_.py:38

backend/alembic/versions/ad3d158aae34_merge_all_heads_for_autotune_fix.py:24

backend/alembic/versions/d5dd6936b758_add_tenant_id_to_samba_return.py:53

backend/alembic/versions/u9v0w1x2y3z4_add_samba_sourcing_account.py:42

backend/alembic/versions/z_add_source_brand_name.py:28

backend/alembic/versions/zzzzzzzzzzzzzzz_dedupe_collected_product_unique.py:54

low System graph software Dead code conf 1.00 Possibly dead Python function: ensure_logged_in

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

tools/lotteon_daemon/daemon.py:1379

low System graph software Dead code conf 1.00 Possibly dead Python function: extract_lotteon_pdp

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

tools/lotteon_daemon/daemon.py:2128

low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_lotteon_credential

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

tools/lotteon_daemon/daemon.py:1042

low System graph software Dead code conf 1.00 Possibly dead Python function: forward

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

backend/scripts/export_clip_onnx.py:68

low System graph software Dead code conf 1.00 Possibly dead Python function: log_message

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

tools/lotteon_daemon/daemon.py:2553

low System graph software Dead code conf 1.00 Possibly dead Python function: lotteon_auto_login

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

tools/lotteon_daemon/daemon.py:1116

low System graph software Dead code conf 1.00 Possibly dead Python function: remove_watermark

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

backend/scripts/local_bg_worker.py:279

low System graph software Dead code conf 1.00 10 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.

10 files, 10 locations

backend/alembic/versions/4f3493e4d2ef_add_source_url_to_samba_order.py:21

backend/alembic/versions/7c423005e6ab_add_market_product_nos_to_collected_.py:22

backend/alembic/versions/8355b1006c94_add_free_shipping_and_same_day_delivery_.py:22

backend/alembic/versions/ad3d158aae34_merge_all_heads_for_autotune_fix.py:19

backend/alembic/versions/d5dd6936b758_add_tenant_id_to_samba_return.py:21

backend/alembic/versions/u9v0w1x2y3z4_add_samba_sourcing_account.py:20

backend/alembic/versions/z_add_source_brand_name.py:20

backend/alembic/versions/zzzzzzzzzzzzzzz_dedupe_collected_product_unique.py:35

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 — extension/background-autologin.js:96

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 — extension/background-bootstrap.js:7

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 — extension/background-kream.js:10

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 — extension/background-messages.js:51

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 — extension/background-sourcing.js:10

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 — extension/background.js:37

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 — extension/content-musinsa-balance.js:10

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 — extension/content-musinsa-claimlist.js:69

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 — extension/content-musinsa-orderlist.js:55

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 — extension/content-review-abcmart.js:252

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 — extension/content-review-gs.js:155

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 — extension/content-review-kream.js:206

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 — extension/content-review-lotteon.js:211

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 — extension/content-review-musinsa.js: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 — extension/content-review-naver.js:168

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 — extension/content-review-ssg.js:168

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 — extension/content-reward-abcmart-attend.js:19

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 — extension/content-reward-musinsa-attendance.js:22

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 — extension/content-reward-musinsa-snap.js:23

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 — extension/content-ssg-dialog-suppress.js:10

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 — extension/create-icons.js:30

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 — extension/kream-collect.js:21

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 — extension/recipe-cache.js:23

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 quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/202605011300_fix_lotteon_exchange_status.py:39

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/4c81abda9e0e_samba_return에_customer_phone_check_date_.py:24

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/add_ssg_cs_columns.py:31

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/w2x3y4z5a6b7_add_missing_samba_return_columns.py:64

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/z_add_return_editable_cells.py:31

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/z_add_return_phone_sourcing_cells.py:36

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/z_fix_autotune_missing_columns.py:40

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/zz_cs_automation_draft_cols.py:58

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/zzz_return_collect_tracking.py:64

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/zzzzzzzz_cs_inquiry_missing_columns.py:106

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz_backfill_market_account_esm_toss.py:98

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/alembic/versions/zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz_dedupe_market_default.py:48

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `upgrade` (body is just `pass`/`return`) — backend/alembic/versions/z_merge_upstream_ebay_heads.py:24

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `upgrade` (body is just `pass`/`return`) — backend/alembic/versions/zz_merge_ebay_and_dedup.py:24

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `upgrade` (body is just `pass`/`return`) — backend/alembic/versions/zzzzzzzzzzzz_merge_heads_lotteon_dedup_orderer_name.py:22

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `upgrade` (body is just `pass`/`return`) — backend/alembic/versions/zzzzzzzzzzzzzzzzzzzzzzzz_merge_heads_postal_sales.py:24

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /schedules/{schedule_id}

`backend/backend/api/v1/routers/samba/store_care.py` declares `DELETE /schedules/{schedule_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 /{account_id}

`backend/backend/api/v1/routers/samba/account.py` declares `DELETE /{account_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: DELETE /{user_id}

`backend/backend/api/v1/routers/user.py` declares `DELETE /{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 /

`backend/backend/app_factory.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 /active

`backend/backend/api/v1/routers/samba/account.py` declares `GET /active` 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/v1/health

`backend/backend/app_factory.py` declares `GET /api/v1/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 /ebay/deletion-notification

`backend/backend/api/v1/routers/ebay.py` declares `GET /ebay/deletion-notification` 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: GET /ghost-summary

`backend/backend/api/v1/routers/samba/shipment.py` declares `GET /ghost-summary` 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 /markets

`backend/backend/api/v1/routers/samba/account.py` declares `GET /markets` 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

`backend/backend/api/v1/routers/auth.py` declares `GET /me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /pending-with-context

`backend/backend/api/v1/routers/samba/cs_internal.py` declares `GET /pending-with-context` 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 /product/{product_id}

`backend/backend/api/v1/routers/samba/shipment.py` declares `GET /product/{product_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 con…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /purchases

`backend/backend/api/v1/routers/samba/store_care.py` declares `GET /purchases` 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 /schedules

`backend/backend/api/v1/routers/samba/store_care.py` declares `GET /schedules` 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 /stats

`backend/backend/api/v1/routers/samba/store_care.py` declares `GET /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 /{account_id}

`backend/backend/api/v1/routers/samba/account.py` declares `GET /{account_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 /{account_id}/secrets

`backend/backend/api/v1/routers/samba/account.py` declares `GET /{account_id}/secrets` 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 /{shipment_id}

`backend/backend/api/v1/routers/samba/shipment.py` declares `GET /{shipment_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 /{user_id}

`backend/backend/api/v1/routers/user.py` declares `GET /{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: PATCH /{user_id}

`backend/backend/api/v1/routers/user.py` declares `PATCH /{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 /

`backend/backend/api/v1/routers/user.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 /cancel

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /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 documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /coupang/cleanup-orphans

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /coupang/cleanup-orphans` 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 /coupang/clear-stale-mapping

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /coupang/clear-stale-mapping` 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: POST /coupang/delete-orphan

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /coupang/delete-orphan` 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 /ebay/deletion-notification

`backend/backend/api/v1/routers/ebay.py` declares `POST /ebay/deletion-notification` 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 consum…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /elevenst/cleanup-missing-prdno

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /elevenst/cleanup-missing-prdno` 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 document…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /elevenst/cleanup-orphans

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /elevenst/cleanup-orphans` 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 wh…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /elevenst/cleanup-orphans-v2

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /elevenst/cleanup-orphans-v2` 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: POST /email/login

`backend/backend/api/v1/routers/auth.py` declares `POST /email/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 /email/sign-up

`backend/backend/api/v1/routers/auth.py` declares `POST /email/sign-up` 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 /emergency-clear

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /emergency-clear` 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 /emergency-stop

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /emergency-stop` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /from-store-form

`backend/backend/api/v1/routers/samba/account.py` declares `POST /from-store-form` 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 /group-preview

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /group-preview` 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 /group-send

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /group-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 /license/verify

`backend/backend/api/v1/routers/license.py` declares `POST /license/verify` 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 /lotteon/cleanup-orphans

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /lotteon/cleanup-orphans` 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 /market-delete

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /market-delete` 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 /market-delete-by-account

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /market-delete-by-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 wh…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /refresh

`backend/backend/api/v1/routers/auth.py` declares `POST /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 api Wiring conf 1.00 Unused endpoint: POST /schedules

`backend/backend/api/v1/routers/samba/store_care.py` declares `POST /schedules` 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 /schedules/{schedule_id}/toggle

`backend/backend/api/v1/routers/samba/store_care.py` declares `POST /schedules/{schedule_id}/toggle` 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 docume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /smartstore/cleanup-orphans

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /smartstore/cleanup-orphans` 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: POST /start

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /start` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /{shipment_id}/retry

`backend/backend/api/v1/routers/samba/shipment.py` declares `POST /{shipment_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 con…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PUT /schedules/{schedule_id}

`backend/backend/api/v1/routers/samba/store_care.py` declares `PUT /schedules/{schedule_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 wh…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PUT /{account_id}

`backend/backend/api/v1/routers/samba/account.py` declares `PUT /{account_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: PUT /{account_id}/set-default

`backend/backend/api/v1/routers/samba/account.py` declares `PUT /{account_id}/set-default` 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: PUT /{account_id}/toggle

`backend/backend/api/v1/routers/samba/account.py` declares `PUT /{account_id}/toggle` 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 quality Complexity conf 1.00 Very large file: backend/backend/api/v1/routers/samba/collector.py (2457 lines)