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

spectrum77br/davinci

https://github.com/spectrum77br/davinci · scanned 2026-06-16 00:19 UTC (2 months, 2 weeks ago)

194 raw signals (6 security + 188 graph)

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

Complete repo analysis

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

JSON
Combined
80.3
/100
Security checks
80
4 findings
System graph
80
100.0% cov · 169 findings
Critical
1
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 8 Medium 9 Low 105 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 4 System graph 169 Crowd 0 Layer: Quality 99 Software 3 Frontend 7 Hardware 5 Security 1 Cicd 2 Api 56
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 80.3/100 with 100.0% coverage. It contains 4048 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 188 findings — concentrated in quality (113), api (56), frontend (7). Risk profile is high: 0 critical, 6 high, 8 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

critical Security checks quality Practices conf 0.82 Foundry mined mock as real or placeholder: spectrum77br/davinci
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
high Security checks quality Practices conf 0.84 Foundry mined bad chains: spectrum77br/davinci
Comment chain pattern product: bad_chains Repo: spectrum77br/davinci Thread: spectrum77br/davinci#1 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_h…
high Security checks quality Quality conf 0.76 2 occurrences Foundry mined schema ui api mismatch: spectrum77br/davinci
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_verification_signal Repo…
2 occurrences
repo-level (2 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/marketplace-oauth/bling/start?integrationId=${integrationId}&origin=${encodeURIComponent(origin)} (reference/stock-sync-hub/client/src/pages/Integrations.tsx:232)
`reference/stock-sync-hub/client/src/pages/Integrations.tsx:232` calls `GET /api/marketplace-oauth/bling/start?integrationId=${integrationId}&origin=${encodeURIComponent(origin)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/marketplace-oauth/mercadolivre/start?integrationId=${integrationId}&origin=${encodeURIComponent(origin)} (reference/stock-sync-hub/client/src/pages/Integrations.tsx:192)
`reference/stock-sync-hub/client/src/pages/Integrations.tsx:192` calls `GET /api/marketplace-oauth/mercadolivre/start?integrationId=${integrationId}&origin=${encodeURIComponent(origin)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path us…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/marketplace-oauth/shopee/start?integrationId=${integrationId}&origin=${encodeURIComponent(origin)} (reference/stock-sync-hub/client/src/pages/Integrations.tsx:172)
`reference/stock-sync-hub/client/src/pages/Integrations.tsx:172` calls `GET /api/marketplace-oauth/shopee/start?integrationId=${integrationId}&origin=${encodeURIComponent(origin)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/marketplace-oauth/tiktok/start?integrationId=${integrationId}&origin=${encodeURIComponent(origin)} (reference/stock-sync-hub/client/src/pages/Integrations.tsx:212)
`reference/stock-sync-hub/client/src/pages/Integrations.tsx:212` calls `GET /api/marketplace-oauth/tiktok/start?integrationId=${integrationId}&origin=${encodeURIComponent(origin)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.mercadolibre.com/sites/MLB/search (reference/stock-sync-hub/server/routers.ts:2035)
`reference/stock-sync-hub/server/routers.ts:2035` calls `GET https://api.mercadolibre.com/sites/MLB/search` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/api.mercadolibre.com/sites/mlb/search` If this points…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/logout (apps/web/stores/auth.ts:100)
`apps/web/stores/auth.ts:100` calls `POST /api/auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/logout` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
medium Security checks quality maintenance conf 0.70 2 occurrences Foundry mined blueprint gap alignment: spectrum77br/davinci
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
2 occurrences
repo-level (2 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/web/stores/auth.ts:100
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, lockfile. 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 hardware Security conf 1.00 Dockerfile runs as root: apps/api/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: apps/web/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in apps/web/components/IntegrationFormModal.vue:316
Found a known-risky pattern (vue_v_html). Review and replace if possible.
apps/web/components/IntegrationFormModal.vue:316 Vue v html
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 117 placeholder/mock markers across 25 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 15 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `API_URL_PUBLIC`, `CI`, `DATABASE_URL_RAW`, `DUMP_DIR`, `E2E_BASE_URL`, `E2E_NO_WEBSERVER`, `E2E_PORT`, `ELETRO_XLSX` + 7 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 176 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 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 1, 13
apps/web/Dockerfile:1, 13 (2 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
apps/api/Dockerfile:1 containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
67 tests / 404 src (ratio 0.17).
low System graph quality Integrity conf 1.00 18 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: apps/api/scripts/backfill_bling_products.py:on_refresh, apps/api/app/services/listings_import.py:on_refresh 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…
18 occurrences
repo-level (18 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: apps/api/app/services/email.py:send, apps/api/app/services/email.py:send, apps/api/app/services/email.py:send This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document w…
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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/web/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.
apps/web/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: reference/stock-sync-hub/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.
reference/stock-sync-hub/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `0102_import_products_bling_sync_v2` in apps/api/alembic/versions/0102_import_products_bling_sync_v2.py:20
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 `0102_import_products_bling_sync_v2` in apps/api/alembic/versions/0103_devolver_estoque_bool.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 `cadastro_tipo_old` in apps/api/alembic/versions/0014_cadastro_tipo_servidor.py:29
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `catalog_copy` in apps/api/app/routers/pricing.py:514
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 `raw_v1` in apps/api/tests/test_webhook_bling_pedido.py:272
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 `skipped_old` in apps/api/scripts/recover_ship_dates_27052026.py:88
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 `stock_info_v2` in apps/api/app/services/marketplaces/shopee.py:450
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 `stocksync_legacy` in apps/api/app/cutover/cli.py:33
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 `stocksync_legacy` in apps/api/app/cutover/load_mysql_dump.py:1
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 `stocksync_legacy` in apps/api/app/cutover/migrate.py:3
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 `stocksync_legacy` in apps/api/app/cutover/restore_integrations.py:1
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 `stocksync_legacy` in apps/api/app/cutover/validate.py:52
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 `stocksync_legacy` in apps/api/tests/test_cutover.py:4
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 `test_alerts_cleanup_removes_only_old` in apps/api/tests/test_alerts_workers.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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
apps/web/package.json CI/CD securitySupply chainNpm
low System graph software Dead code conf 1.00 Possibly dead Python function: marketing_agent_cycle
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/app/worker.py:371
low System graph software Dead code conf 1.00 Possibly dead Python function: ml_discrepancy_check
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/app/worker.py:664
low System graph software Dead code conf 1.00 Possibly dead Python function: tiktok_token_refresh
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/app/worker.py:629
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 — reference/stock-sync-hub/client/src/pages/ComponentShowcase.tsx:197
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 — reference/stock-sync-hub/server/db.ts:36
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 — reference/stock-sync-hub/server/routers.ts:268
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`) — apps/api/alembic/versions/0019_refresh_bling_stock_enum.py:27
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`) — apps/api/alembic/versions/0021_cell_status_na_sv.py:29
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`) — apps/api/alembic/versions/0037_backfill_margens_conta_loja_nome.py:43
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`) — apps/api/alembic/versions/0041_auto_import_link_enum.py:27
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`) — apps/api/alembic/versions/0107_normalize_devolution_tags.py:46
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`) — apps/api/alembic/versions/0035_merge_heads.py:20
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`) — apps/api/alembic/versions/0063_merge_tarefas_product_categories.py:19
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`) — apps/api/alembic/versions/0070_merge_marketing_refunds_heads.py:23
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`) — apps/api/alembic/versions/0079_merge_controle_estoque_devolutions.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`) — apps/api/alembic/versions/0081_merge_controle_estoque_views.py:26
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`) — apps/api/alembic/versions/0089_merge_importacao_transporte.py:23
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`) — apps/api/alembic/versions/0093_merge_bling_sync_devolucoes.py:26
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`) — apps/api/alembic/versions/0095_merge_cotacao_endereco.py:26
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 /accounts/{account_id}
`apps/api/app/routers/pricing.py` declares `DELETE /accounts/{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: DELETE /overrides
`apps/api/app/routers/pricing.py` declares `DELETE /overrides` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /product-links/{link_id}
`apps/api/app/routers/products.py` declares `DELETE /product-links/{link_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /products/{product_id}
`apps/api/app/routers/products.py` declares `DELETE /products/{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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{integration_id}
`apps/api/app/routers/integrations.py` declares `DELETE /{integration_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 /
`apps/api/app/routers/integrations.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 /accounts
`apps/api/app/routers/pricing.py` declares `GET /accounts` 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 /actual-prices/{pricing_product_id}
`apps/api/app/routers/pricing.py` declares `GET /actual-prices/{pricing_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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`apps/api/app/main.py` declares `GET /api/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /catalog-listings
`apps/api/app/routers/pricing.py` declares `GET /catalog-listings` 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 /competitor-prices
`apps/api/app/routers/pricing.py` declares `GET /competitor-prices` 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 /discrepancies
`apps/api/app/routers/discrepancies.py` declares `GET /discrepancies` 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 /grid
`apps/api/app/routers/pricing.py` declares `GET /grid` 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 /overrides
`apps/api/app/routers/pricing.py` declares `GET /overrides` 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 /product-links
`apps/api/app/routers/products.py` declares `GET /product-links` 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 /products
`apps/api/app/routers/products.py` declares `GET /products` 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 /products/preview/bling
`apps/api/app/routers/products.py` declares `GET /products/preview/bling` 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 /products/{product_id}
`apps/api/app/routers/products.py` declares `GET /products/{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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /sales-map
`apps/api/app/routers/pricing.py` declares `GET /sales-map` 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-audit
`apps/api/app/routers/pricing.py` declares `GET /sku-audit` 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-audit/dismissed
`apps/api/app/routers/pricing.py` declares `GET /sku-audit/dismissed` 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 /stock-map
`apps/api/app/routers/pricing.py` declares `GET /stock-map` 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 /tiktok/callback
`apps/api/app/routers/integrations.py` declares `GET /tiktok/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 /tiktok/start
`apps/api/app/routers/integrations.py` declares `GET /tiktok/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: GET /{integration_id}
`apps/api/app/routers/integrations.py` declares `GET /{integration_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 /{integration_id}/bling-stores
`apps/api/app/routers/integrations.py` declares `GET /{integration_id}/bling-stores` 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: PATCH /accounts/{account_id}
`apps/api/app/routers/pricing.py` declares `PATCH /accounts/{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: PATCH /products/{product_id}
`apps/api/app/routers/products.py` declares `PATCH /products/{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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /{integration_id}
`apps/api/app/routers/integrations.py` declares `PATCH /{integration_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 /
`apps/api/app/routers/integrations.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 /accounts
`apps/api/app/routers/pricing.py` declares `POST /accounts` 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 /accounts/auto-match
`apps/api/app/routers/pricing.py` declares `POST /accounts/auto-match` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /jobs/sync-bling-costs
`apps/api/app/routers/pricing.py` declares `POST /jobs/sync-bling-costs` 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 /products
`apps/api/app/routers/products.py` declares `POST /products` 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 /products/bulk-delete
`apps/api/app/routers/products.py` declares `POST /products/bulk-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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /products/bulk-segment
`apps/api/app/routers/products.py` declares `POST /products/bulk-segment` 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 /products/import
`apps/api/app/routers/pricing.py` declares `POST /products/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 /products/import/bling
`apps/api/app/routers/products.py` declares `POST /products/import/bling` 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 /products/import/csv
`apps/api/app/routers/products.py` declares `POST /products/import/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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /products/{product_id}/catalog
`apps/api/app/routers/pricing.py` declares `POST /products/{product_id}/catalog` 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: POST /push
`apps/api/app/routers/pricing.py` declares `POST /push` 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 /push-batch
`apps/api/app/routers/pricing.py` declares `POST /push-batch` 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 /push-catalog
`apps/api/app/routers/pricing.py` declares `POST /push-catalog` 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 /push-report
`apps/api/app/routers/pricing.py` declares `POST /push-report` 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 /sku-audit/{sku}/dismiss
`apps/api/app/routers/pricing.py` declares `POST /sku-audit/{sku}/dismiss` 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 /sku-audit/{sku}/undismiss
`apps/api/app/routers/pricing.py` declares `POST /sku-audit/{sku}/undismiss` 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 /{integration_id}/test
`apps/api/app/routers/integrations.py` declares `POST /{integration_id}/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 /overrides
`apps/api/app/routers/pricing.py` declares `PUT /overrides` 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 /overrides/cell-color
`apps/api/app/routers/pricing.py` declares `PUT /overrides/cell-color` 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 /overrides/cell-status
`apps/api/app/routers/pricing.py` declares `PUT /overrides/cell-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 quality Complexity conf 1.00 Very large file: apps/api/app/routers/estoque.py (1375 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/app/routers/importacao.py (2045 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/app/routers/pricing.py (2406 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/app/services/marketplace_financials.py (1530 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/app/worker.py (1402 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: reference/stock-sync-hub/client/src/pages/ComponentShowcase.tsx (1437 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: reference/stock-sync-hub/client/src/pages/Pricing.tsx (3499 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: reference/stock-sync-hub/client/src/pages/Products.tsx (2109 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: reference/stock-sync-hub/server/routers.ts (2354 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/9394c339-2a31-499a-bc4d-de3471f11378/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9394c339-2a31-499a-bc4d-de3471f11378/

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.