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

rlsmth20/shopify-analytics-engine-

https://github.com/rlsmth20/shopify-analytics-engine- · scanned 2026-06-15 23:52 UTC (2 months, 3 weeks ago)

149 raw signals (0 security + 149 graph)

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

Complete repo analysis

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

JSON
Combined
51.1
/100
Security checks
51
0 findings
System graph
51
77.8% cov · 142 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 5 Medium 20 Low 111 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 142 Crowd 0 Layer: Software 21 Frontend 7 Security 12 Cicd 1 Quality 51 Api 50
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 51.1/100 with 77.8% coverage. It contains 1685 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 149 findings — concentrated in quality (58), api (50), software (21). Risk profile is high: 0 critical, 5 high, 20 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high System graph security auth conf 1.00 FastAPI POST `app_uninstalled` without auth dependency — backend/app/api/routes/shopify_privacy_webhooks.py:154
`@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/api/routes/shopify_privacy_webhooks.py:154 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `customers_data_request` without auth dependency — backend/app/api/routes/shopify_privacy_webhooks.py:82
`@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/api/routes/shopify_privacy_webhooks.py:82 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `customers_redact` without auth dependency — backend/app/api/routes/shopify_privacy_webhooks.py:105
`@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/api/routes/shopify_privacy_webhooks.py:105 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `shop_redact` without auth dependency — backend/app/api/routes/shopify_privacy_webhooks.py:127
`@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/api/routes/shopify_privacy_webhooks.py:127 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit` without auth dependency — backend/app/api/routes/contact.py:31
`@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/api/routes/contact.py:31 securityAuth fastapi unauth mutation
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/blog/how-to-clear-dead-stock-shopify/page.tsx:173
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/blog/inventory-planner-alternative/page.tsx:155
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/blog/shopify-safety-stock-formula/page.tsx:179
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/blog/stocky-alternatives-2026/page.tsx:95
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/blog/why-six-month-moving-average-overstocks-you/page.tsx:83
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/layout.tsx:93
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/pricing/page.tsx:117
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, tests. 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 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 'dangerous_innerhtml' in frontend/app/blog/how-to-clear-dead-stock-shopify/page.tsx:173
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/blog/how-to-clear-dead-stock-shopify/page.tsx:173 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/app/blog/inventory-planner-alternative/page.tsx:155
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/blog/inventory-planner-alternative/page.tsx:155 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/app/blog/shopify-safety-stock-formula/page.tsx:179
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/blog/shopify-safety-stock-formula/page.tsx:179 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/app/blog/stocky-alternatives-2026/page.tsx:95
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/blog/stocky-alternatives-2026/page.tsx:95 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/app/blog/why-six-month-moving-average-overstocks-you/page.tsx:83
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/blog/why-six-month-moving-average-overstocks-you/page.tsx:83 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/app/layout.tsx:93
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/layout.tsx:93 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/app/pricing/page.tsx:117
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/pricing/page.tsx:117 Dangerous innerhtml
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 56 placeholder/mock markers across 24 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 180 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 27 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_BOOTSTRAP_TOKEN`, `ADMIN_EMAILS`, `COOKIE_DOMAIN`, `GENERIC_WEBHOOK_TIMEOUT`, `NEXT_PUBLIC_SITE_URL`, `NODE_ENV`, `OPENAI_API_KEY`, `OPENAI_MODEL` + 19 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 5 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/api/routes/shipstation_import.py:import_shipstation, backend/app/api/routes/stocky_import.py:import_stocky_csv This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate …
8 occurrences
repo-level (8 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/app/services/shop_settings.py:upsert_vendor_lead_times, backend/app/services/shop_settings.py:upsert_category_lead_times, backend/app/services/shop_settings.py:upsert_sku_lead_times This is *the* AI-coder failure mode (4× more duplication in …
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: backend/app/api/routes/shopify_privacy_webhooks.py:customers_data_request, backend/app/api/routes/shopify_privacy_webhooks.py:customers_redact, backend/app/api/routes/shopify_privacy_webhooks.py:shop_redact, backend/app/api/routes/shopify_privacy_webh…
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 `mock_data_v2` in backend/app/services/shop_skus.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 `model_copy` in backend/app/services/action_feed.py:381
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 `schemas_v2` in backend/app/api/routes/alerts.py:10
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 `schemas_v2` in backend/app/api/routes/analytics.py:9
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 `schemas_v2` in backend/app/api/routes/audit.py:11
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 `schemas_v2` in backend/app/api/routes/bundles.py:9
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 `schemas_v2` in backend/app/api/routes/dashboard.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 `schemas_v2` in backend/app/api/routes/forecast.py:9
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 `schemas_v2` in backend/app/api/routes/liquidation.py:9
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 `schemas_v2` in backend/app/api/routes/reorder.py:10
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 `schemas_v2` in backend/app/api/routes/report_schedules.py:11
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 `schemas_v2` in backend/app/api/routes/suppliers.py:9
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 `schemas_v2` in backend/app/api/routes/transfers.py:9
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 `schemas_v2` in backend/app/services/abc_analysis.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 `schemas_v2` in backend/app/services/alert_evaluation.py:10
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 `schemas_v2` in backend/app/services/alerts.py:23
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `schemas_v2` in backend/app/services/bundle_analyzer.py: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 `schemas_v2` in backend/app/services/bundle_opportunities.py:16
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 `schemas_v2` in backend/app/services/buying_calendar.py: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 `schemas_v2` in backend/app/services/dashboard.py:17
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 `schemas_v2` in backend/app/services/dead_stock.py:15
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 `schemas_v2` in backend/app/services/forecasting.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 `schemas_v2` in backend/app/services/inventory_health.py:8
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 `schemas_v2` in backend/app/services/notifications.py:25
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 `schemas_v2` in backend/app/services/purchase_order_records.py:15
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 `schemas_v2` in backend/app/services/purchase_orders.py:10
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 `schemas_v2` in backend/app/services/reorder_optimizer.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 `schemas_v2` in backend/app/services/supplier_scoring.py:15
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 `schemas_v2` in backend/app/services/transfers.py:11
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 `schemas_v2` in backend/app/services/weekly_digest.py: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 software Dead code conf 1.00 Possibly dead Python function: analyze_bundles
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/bundle_analyzer.py:28
low System graph software Dead code conf 1.00 Possibly dead Python function: build_action_data_health_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/action_feed.py:148
low System graph software Dead code conf 1.00 Possibly dead Python function: build_inventory_action_feed
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/action_feed.py:76
low System graph software Dead code conf 1.00 Possibly dead Python function: consume_magic_link_token
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/auth.py:130
low System graph software Dead code conf 1.00 Possibly dead Python function: create_checkout_session
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/billing.py:262
low System graph software Dead code conf 1.00 Possibly dead Python function: daily_history
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/routes/reorder.py:236
low System graph software Dead code conf 1.00 Possibly dead Python function: daily_history
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/routes/dashboard.py:39
low System graph software Dead code conf 1.00 Possibly dead Python function: dependency
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/deps.py:203
low System graph software Dead code conf 1.00 Possibly dead Python function: history
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/abc_analysis.py:29
low System graph software Dead code conf 1.00 Possibly dead Python function: list_persisted_skus
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/action_feed.py:93
low System graph software Dead code conf 1.00 Possibly dead Python function: recent_daily_revenue
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/mock_data_v2.py:154
low System graph software Dead code conf 1.00 Possibly dead Python function: recent_deliveries
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/notifications.py:45
low System graph software Dead code conf 1.00 Possibly dead Python function: recent_revenue
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/routes/dashboard.py:43
low System graph software Dead code conf 1.00 Possibly dead Python function: require_active_access
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/deps.py:129
low System graph software Dead code conf 1.00 Possibly dead Python function: require_admin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/deps.py:117
low System graph software Dead code conf 1.00 Possibly dead Python function: run_alert_evaluation_once
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/alert_scheduler.py:39
low System graph software Dead code conf 1.00 Possibly dead Python function: send_contact_notification
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/transactional_email.py:192
low System graph software Dead code conf 1.00 Possibly dead Python function: send_magic_link_email
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/transactional_email.py:286
low System graph software Dead code conf 1.00 Possibly dead Python function: send_waitlist_confirmation
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/transactional_email.py:116
low System graph software Dead code conf 1.00 Possibly dead Python function: start_weekday_for_history
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/mock_data_v2.py:146
low System graph software Dead code conf 1.00 Possibly dead Python function: supplier_observations
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/mock_data_v2.py:164
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /rules/{rule_id}
`backend/app/api/routes/alerts.py` declares `DELETE /rules/{rule_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/app/api/routes/forecast.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 /buying-calendar
`backend/app/api/routes/reorder.py` declares `GET /buying-calendar` 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 /callback
`backend/app/api/routes/shopify_ingestion.py` declares `GET /callback` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /cash-plan
`backend/app/api/routes/reorder.py` declares `GET /cash-plan` 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 /category-lead-times
`backend/app/api/routes/shop_settings.py` declares `GET /category-lead-times` 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 /channels
`backend/app/api/routes/alerts.py` declares `GET /channels` 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 /connection
`backend/app/api/routes/shopify_ingestion.py` declares `GET /connection` 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 /count
`backend/app/api/routes/waitlist.py` declares `GET /count` 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 /dead-stock-pairings
`backend/app/api/routes/bundles.py` declares `GET /dead-stock-pairings` 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 /install
`backend/app/api/routes/shopify_ingestion.py` declares `GET /install` 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 /inventory-health
`backend/app/api/routes/analytics.py` declares `GET /inventory-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 /inventory-value
`backend/app/api/routes/analytics.py` declares `GET /inventory-value` 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 /leads
`backend/app/api/routes/inventory_risk_snapshot.py` declares `GET /leads` 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 /leads/export.csv
`backend/app/api/routes/inventory_risk_snapshot.py` declares `GET /leads/export.csv` 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: GET /leads/export.xlsx
`backend/app/api/routes/inventory_risk_snapshot.py` declares `GET /leads/export.xlsx` 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: GET /me
`backend/app/api/routes/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 /purchase-orders
`backend/app/api/routes/reorder.py` declares `GET /purchase-orders` 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 /rules
`backend/app/api/routes/alerts.py` declares `GET /rules` 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 /scorecards
`backend/app/api/routes/analytics.py` declares `GET /scorecards` 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 /sku-lead-times
`backend/app/api/routes/shop_settings.py` declares `GET /sku-lead-times` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /summary
`backend/app/api/routes/skus.py` declares `GET /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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /users
`backend/app/api/routes/admin.py` declares `GET /users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /vendor-lead-times
`backend/app/api/routes/shop_settings.py` declares `GET /vendor-lead-times` 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 /{sku_id}
`backend/app/api/routes/forecast.py` declares `GET /{sku_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 /rules/{rule_id}/toggle
`backend/app/api/routes/alerts.py` declares `PATCH /rules/{rule_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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /app/uninstalled
`backend/app/api/routes/shopify_privacy_webhooks.py` declares `POST /app/uninstalled` 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 /billing/reconcile
`backend/app/api/routes/admin.py` declares `POST /billing/reconcile` 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 /channels
`backend/app/api/routes/alerts.py` declares `POST /channels` 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 /chat
`backend/app/api/routes/ai_chat.py` declares `POST /chat` 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/data_request
`backend/app/api/routes/shopify_privacy_webhooks.py` declares `POST /customers/data_request` 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/redact
`backend/app/api/routes/shopify_privacy_webhooks.py` declares `POST /customers/redact` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import
`backend/app/api/routes/shipstation_import.py` declares `POST /import` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /invite
`backend/app/api/routes/admin.py` declares `POST /invite` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /leads
`backend/app/api/routes/inventory_risk_snapshot.py` declares `POST /leads` 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 /logout
`backend/app/api/routes/auth.py` declares `POST /logout` 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 /magic-link/request
`backend/app/api/routes/auth.py` declares `POST /magic-link/request` 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 /magic-link/verify
`backend/app/api/routes/auth.py` declares `POST /magic-link/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 /purchase-orders
`backend/app/api/routes/reorder.py` declares `POST /purchase-orders` 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 /purchase-orders/{po_id}/receive
`backend/app/api/routes/reorder.py` declares `POST /purchase-orders/{po_id}/receive` 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 /purchase-orders/{po_id}/status
`backend/app/api/routes/reorder.py` declares `POST /purchase-orders/{po_id}/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /rules
`backend/app/api/routes/alerts.py` declares `POST /rules` 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 /shop/redact
`backend/app/api/routes/shopify_privacy_webhooks.py` declares `POST /shop/redact` 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 /signup
`backend/app/api/routes/waitlist.py` declares `POST /signup` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /sync
`backend/app/api/routes/shopify_ingestion.py` declares `POST /sync` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /test
`backend/app/api/routes/alerts.py` declares `POST /test` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /
`backend/app/api/routes/shop_settings.py` declares `PUT /` 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 /category-lead-times
`backend/app/api/routes/shop_settings.py` declares `PUT /category-lead-times` 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 /sku-lead-times
`backend/app/api/routes/shop_settings.py` declares `PUT /sku-lead-times` 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 /vendor-lead-times
`backend/app/api/routes/shop_settings.py` declares `PUT /vendor-lead-times` 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: frontend/app/(app-shell)/purchase-orders/page.tsx (1720 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/app/(app-shell)/reports/page.tsx (1963 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/lib/demo-data.ts (1846 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/dec256e4-6a68-4561-9792-4eb0a65fdf2d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/dec256e4-6a68-4561-9792-4eb0a65fdf2d/

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.