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

subimeDev/FrittesRancagua-

https://github.com/subimeDev/FrittesRancagua- · scanned 2026-06-16 00:24 UTC (2 months, 2 weeks ago)

105 raw signals (0 security + 105 graph)

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

Complete repo analysis

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

JSON
Combined
64.4
/100
Security checks
64
0 findings
System graph
64
77.8% cov · 92 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 19 Medium 9 Low 55 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 92 Crowd 0 Layer: Software 10 Frontend 5 Security 11 Cicd 1 Quality 16 Api 49
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 64.4/100 with 77.8% coverage. It contains 667 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 105 findings — concentrated in api (49), software (22), quality (17). Risk profile is high: 0 critical, 19 high, 9 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 83 of 92 actionable findings. 105 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET /loyalty/admin/announce (frontends/frittes-pos/lib/api.ts:125)
`frontends/frittes-pos/lib/api.ts:125` calls `GET /loyalty/admin/announce` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/loyalty/admin/announce` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /loyalty/admin/menu (frontends/frittes-pos/lib/api.ts:164)
`frontends/frittes-pos/lib/api.ts:164` calls `GET /loyalty/admin/menu` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/loyalty/admin/menu` If this points at an external API, prefix it with `https://` so the …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /loyalty/admin/proximity (frontends/frittes-pos/lib/api.ts:103)
`frontends/frittes-pos/lib/api.ts:103` calls `GET /loyalty/admin/proximity` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/loyalty/admin/proximity` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /loyalty/admin/proximity (frontends/frittes-pos/lib/api.ts:110)
`frontends/frittes-pos/lib/api.ts:110` calls `PATCH /loyalty/admin/proximity` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/loyalty/admin/proximity` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /loyalty/admin/announce (frontends/frittes-pos/lib/api.ts:133)
`frontends/frittes-pos/lib/api.ts:133` calls `POST /loyalty/admin/announce` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/loyalty/admin/announce` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /loyalty/staff/auth/login (frontends/frittes-pos/lib/api.ts:74)
`frontends/frittes-pos/lib/api.ts:74` calls `POST /loyalty/staff/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/loyalty/staff/auth/login` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /loyalty/transactions/accrue (frontends/frittes-pos/lib/api.ts:81)
`frontends/frittes-pos/lib/api.ts:81` calls `POST /loyalty/transactions/accrue` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/loyalty/transactions/accrue` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /loyalty/transactions/redeem (frontends/frittes-pos/lib/api.ts:89)
`frontends/frittes-pos/lib/api.ts:89` calls `POST /loyalty/transactions/redeem` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/loyalty/transactions/redeem` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /loyalty/admin/menu (frontends/frittes-pos/lib/api.ts:171)
`frontends/frittes-pos/lib/api.ts:171` calls `PUT /loyalty/admin/menu` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/loyalty/admin/menu` If this points at an external API, prefix it with `https://` so the …
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI POST `accrue` without auth dependency — backend/app/loyalty/router.py:357
`@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/app/loyalty/router.py:357 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `confirm_password_reset` without auth dependency — backend/app/loyalty/router.py:478
`@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/app/loyalty/router.py:478 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dev_login` without auth dependency — backend/app/loyalty/router.py:83
`@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/app/loyalty/router.py:83 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `email_login` without auth dependency — backend/app/loyalty/router.py:149
`@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/app/loyalty/router.py:149 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `redeem` without auth dependency — backend/app/loyalty/router.py:405
`@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/app/loyalty/router.py:405 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `request_otp` without auth dependency — backend/app/loyalty/router.py:112
`@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/app/loyalty/router.py:112 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `request_password_reset` without auth dependency — backend/app/loyalty/router.py:455
`@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/app/loyalty/router.py:455 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sign_out` without auth dependency — backend/app/loyalty/router.py:206
`@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/app/loyalty/router.py:206 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `staff_login` without auth dependency — backend/app/loyalty/router.py:344
`@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/app/loyalty/router.py:344 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_otp` without auth dependency — backend/app/loyalty/router.py:121
`@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/app/loyalty/router.py:121 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontends/frittes-loyalty/public/sw.js:50
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 — frontends/frittes-pos/app/proximidad/page.tsx:169
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 — frontends/frittes-pos/public/sw.js:47
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontends/frittes-pos/app/login/page.tsx:42
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontends/frittes-pos/app/login/page.tsx:42 Local storage auth token
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 46 placeholder/mock markers across 12 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
0 test file(s) for 89 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/loyalty/admin_router.py:announce_status, backend/app/loyalty/admin_router.py:announce 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 s…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in backend/app/config.py:102
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: broadcast_class_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/loyalty/google_wallet.py:485
low System graph software Dead code conf 1.00 Possibly dead Python function: complete_profile_for_phone
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/loyalty/service.py:290
low System graph software Dead code conf 1.00 Possibly dead Python function: count_saved_passes
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/loyalty/google_wallet.py:456
low System graph software Dead code conf 1.00 Possibly dead Python function: create_loyalty_class_if_needed
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/loyalty/google_wallet.py:513
low System graph software Dead code conf 1.00 7 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.
7 files, 7 locations
backend/alembic/versions/0001_initial.py:75
backend/alembic/versions/0002_pending_otps.py:26
backend/alembic/versions/0003_restaurant_config.py:29
backend/alembic/versions/0004_reward_tiers.py:59
backend/alembic/versions/0005_card_levels.py:67
backend/alembic/versions/0006_proximity.py:31
backend/alembic/versions/0007_menu.py:49
low System graph software Dead code conf 1.00 Possibly dead Python function: render_frittes_stamps
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/loyalty/wallet_stamps.py:484
low System graph software Dead code conf 1.00 Possibly dead Python function: require_manager
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/loyalty/admin_router.py:29
low System graph software Dead code conf 1.00 Possibly dead Python function: send_redemption_email
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/loyalty/service.py:357
low System graph software Dead code conf 1.00 Possibly dead Python function: update_loyalty_object
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/loyalty/google_wallet.py:383
low System graph software Dead code conf 1.00 7 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.
7 files, 7 locations
backend/alembic/versions/0001_initial.py:18
backend/alembic/versions/0002_pending_otps.py:17
backend/alembic/versions/0003_restaurant_config.py:18
backend/alembic/versions/0004_reward_tiers.py:21
backend/alembic/versions/0005_card_levels.py:31
backend/alembic/versions/0006_proximity.py:22
backend/alembic/versions/0007_menu.py:21
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: GET /admin/menu
`backend/app/loyalty/menu_router.py` declares `GET /admin/menu` 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 /announce
`backend/app/loyalty/admin_router.py` declares `GET /announce` 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 /config
`backend/app/loyalty/admin_router.py` declares `GET /config` 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 /customers
`backend/app/loyalty/admin_router.py` declares `GET /customers` 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 /customers/check
`backend/app/loyalty/router.py` declares `GET /customers/check` 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 /customers/me
`backend/app/loyalty/router.py` declares `GET /customers/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 /levels
`backend/app/loyalty/admin_router.py` declares `GET /levels` 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 /passes/google/me
`backend/app/loyalty/router.py` declares `GET /passes/google/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 /passes/google/status
`backend/app/loyalty/router.py` declares `GET /passes/google/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /program-config
`backend/app/loyalty/router.py` declares `GET /program-config` 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 /proximity
`backend/app/loyalty/admin_router.py` declares `GET /proximity` 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 /public/menu
`backend/app/loyalty/menu_router.py` declares `GET /public/menu` 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 /public/wallet/{customer_id}/stamps.png
`backend/app/loyalty/router.py` declares `GET /public/wallet/{customer_id}/stamps.png` 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 /qr-tokens
`backend/app/loyalty/router.py` declares `GET /qr-tokens` 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 /staff
`backend/app/loyalty/admin_router.py` declares `GET /staff` 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/app/loyalty/admin_router.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 /tiers
`backend/app/loyalty/admin_router.py` declares `GET /tiers` 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 /top-customers
`backend/app/loyalty/admin_router.py` declares `GET /top-customers` 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 /transactions
`backend/app/loyalty/admin_router.py` declares `GET /transactions` 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 /config
`backend/app/loyalty/admin_router.py` declares `PATCH /config` 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 /proximity
`backend/app/loyalty/admin_router.py` declares `PATCH /proximity` 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 /staff/{staff_id}
`backend/app/loyalty/admin_router.py` declares `PATCH /staff/{staff_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 /announce
`backend/app/loyalty/admin_router.py` declares `POST /announce` 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 /auth/dev-login
`backend/app/loyalty/router.py` declares `POST /auth/dev-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 /auth/email-login
`backend/app/loyalty/router.py` declares `POST /auth/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 /auth/request-otp
`backend/app/loyalty/router.py` declares `POST /auth/request-otp` 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 /auth/sign-out
`backend/app/loyalty/router.py` declares `POST /auth/sign-out` 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 /auth/verify-otp
`backend/app/loyalty/router.py` declares `POST /auth/verify-otp` 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 /customers
`backend/app/loyalty/router.py` declares `POST /customers` 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 /customers/{customer_id}/adjust-stamps
`backend/app/loyalty/admin_router.py` declares `POST /customers/{customer_id}/adjust-stamps` 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 /customers/{customer_id}/redeem
`backend/app/loyalty/admin_router.py` declares `POST /customers/{customer_id}/redeem` 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 /staff
`backend/app/loyalty/admin_router.py` declares `POST /staff` 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 /staff/auth/confirm-password-reset
`backend/app/loyalty/router.py` declares `POST /staff/auth/confirm-password-reset` 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 /staff/auth/login
`backend/app/loyalty/router.py` declares `POST /staff/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 /staff/auth/request-password-reset
`backend/app/loyalty/router.py` declares `POST /staff/auth/request-password-reset` 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 /transactions/accrue
`backend/app/loyalty/router.py` declares `POST /transactions/accrue` 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 /transactions/redeem
`backend/app/loyalty/router.py` declares `POST /transactions/redeem` 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 /admin/menu
`backend/app/loyalty/menu_router.py` declares `PUT /admin/menu` 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 /levels
`backend/app/loyalty/admin_router.py` declares `PUT /levels` 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 /tiers
`backend/app/loyalty/admin_router.py` declares `PUT /tiers` 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: frontends/frittes-pos/app/admin/page.tsx (1493 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/4a4ccb79-dce7-4532-84a7-c4e2336a4ce9/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4a4ccb79-dce7-4532-84a7-c4e2336a4ce9/

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.