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

renanarturdemetrio-ai/agents-portal

https://github.com/renanarturdemetrio-ai/agents-portal · scanned 2026-06-15 23:49 UTC (2 months, 3 weeks ago)

220 raw signals (19 security + 201 graph)

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

Complete repo analysis

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

JSON
Combined
58.8
/100
Security checks
59
7 findings
System graph
59
100.0% cov · 201 findings
Critical
2
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 2 High 31 Medium 69 Low 100 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 201 Crowd 0 Layer: Quality 41 Security 52 Frontend 39 Cicd 1 Api 75
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 58.8/100 with 100.0% coverage. It contains 3701 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 201 findings — concentrated in api (75), security (51), frontend (39). Risk profile is high: 0 critical, 28 high, 67 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 202 of 208 actionable findings. 306 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 11 occurrences Foundry mined mock as real or placeholder: renanarturdemetrio-ai/agents-portal
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…
11 occurrences
repo-level (11 hits)
critical Security checks security auth conf 0.78 7 occurrences Foundry mined security auth guardrail gaps: renanarturdemetrio-ai/agents-portal
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
7 occurrences
repo-level (7 hits)
high Security checks quality Practices conf 0.84 10 occurrences Foundry mined bad chains: renanarturdemetrio-ai/agents-portal
Comment chain pattern product: bad_chains Repo: renanarturdemetrio-ai/agents-portal Thread: renanarturdemetrio-ai/agents-portal#295 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_gra…
10 occurrences
repo-level (10 hits)
high Security checks quality Quality conf 0.76 7 occurrences Foundry mined schema ui api mismatch: renanarturdemetrio-ai/agents-portal
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_high_confidence_link Rep…
7 occurrences
repo-level (7 hits)
high Security checks quality Testing conf 0.78 Foundry mined test ci gap after feedback: renanarturdemetrio-ai/agents-portal
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_high_confi…
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/regras (precos-app/src/app/precos/page.tsx:20)
`precos-app/src/app/precos/page.tsx:20` calls `GET /api/regras` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/regras` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/skus (precos-app/src/app/precos/page.tsx:19)
`precos-app/src/app/precos/page.tsx:19` calls `GET /api/skus` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skus` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/api/financeiro/analise-avancada?periodo=${periodo}&conta=${conta} (server.js:18189)
`server.js:18189` calls `GET http://localhost:${PORT}/api/financeiro/analise-avancada?periodo=${periodo}&conta=${conta}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/financeiro/analise-ava…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/api/financeiro/fluxo-caixa?dias=${dias} (server.js:18796)
`server.js:18796` calls `GET http://localhost:${PORT}/api/financeiro/fluxo-caixa?dias=${dias}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/financeiro/fluxo-caixa` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/api/financeiro/ml/recebimentos?conta=${conta}&dias=${dias} (server.js:17971)
`server.js:17971` calls `GET http://localhost:${PORT}/api/financeiro/ml/recebimentos?conta=${conta}&dias=${dias}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/financeiro/ml/recebimentos` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/api/financeiro/ml/recebimentos?conta=all&dias=${dias} (server.js:17669)
`server.js:17669` calls `GET http://localhost:${PORT}/api/financeiro/ml/recebimentos?conta=all&dias=${dias}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/financeiro/ml/recebimentos` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/api/financeiro/shopee/recebimentos?conta=${k}&dias=${Math.min(dias, 90)} (server.js:17674)
`server.js:17674` calls `GET http://localhost:${PORT}/api/financeiro/shopee/recebimentos?conta=${k}&dias=${Math.min(dias, 90)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/financeiro/shop…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/api/financeiro/tiny/contas-abertas (server.js:17668)
`server.js:17668` calls `GET http://localhost:${PORT}/api/financeiro/tiny/contas-abertas` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/financeiro/tiny/contas-abertas` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/api/financeiro/tiny/contas-abertas (server.js:17972)
`server.js:17972` calls `GET http://localhost:${PORT}/api/financeiro/tiny/contas-abertas` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/financeiro/tiny/contas-abertas` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.mercadolibre.com/items/${itemId}/health (pesquisador-central.js:135)
`pesquisador-central.js:135` calls `GET https://api.mercadolibre.com/items/${itemId}/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.mercadolibre.com/items/<p>/health` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.mercadolibre.com/items/${mlb}?attributes=price,status (scripts/price-sync-report.js:50)
`scripts/price-sync-report.js:50` calls `GET https://api.mercadolibre.com/items/${mlb}?attributes=price,status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.mercadolibre.com/items/<p>` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${PORT}/api/compras/sync-completo (server.js:14786)
`server.js:14786` calls `POST http://localhost:${PORT}/api/compras/sync-completo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/compras/sync-completo` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (core/ml-ai-analyst.js:122)
`core/ml-ai-analyst.js:122` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (core/shopee-ai-analyst.js:110)
`core/shopee-ai-analyst.js:110` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (domains/ml/atendimento-reputacao.js:331)
`domains/ml/atendimento-reputacao.js:331` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (server.js:14568)
`server.js:14568` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (server.js:14729)
`server.js:14729` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (server.js:16498)
`server.js:16498` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (server.js:8463)
`server.js:8463` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (server.js:8709)
`server.js:8709` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.mercadolibre.com/oauth/token (core/auth-ml.js:148)
`core/auth-ml.js:148` calls `POST https://api.mercadolibre.com/oauth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.mercadolibre.com/oauth/token` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.mercadolibre.com/oauth/token (server.js:121)
`server.js:121` calls `POST https://api.mercadolibre.com/oauth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.mercadolibre.com/oauth/token` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.mercadolibre.com/oauth/token (server.js:1717)
`server.js:1717` calls `POST https://api.mercadolibre.com/oauth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.mercadolibre.com/oauth/token` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.mercadolibre.com/oauth/token (server.js:1803)
`server.js:1803` calls `POST https://api.mercadolibre.com/oauth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.mercadolibre.com/oauth/token` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/skus/${skuId}/regra (precos-app/src/app/precos/page.tsx:88)
`precos-app/src/app/precos/page.tsx:88` calls `PUT /api/skus/${skuId}/regra` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skus/<p>/regra` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in core/mcp/tools/ml-item-get.js:58
Found a known-risky pattern (exec_used). Review and replace if possible.
core/mcp/tools/ml-item-get.js:58 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in core/mcp/tools/ml-itens-sync.js:64
Found a known-risky pattern (exec_used). Review and replace if possible.
core/mcp/tools/ml-itens-sync.js:64 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in core/mcp/tools/ml-orders-listar.js:61
Found a known-risky pattern (exec_used). Review and replace if possible.
core/mcp/tools/ml-orders-listar.js:61 Exec used
medium Security checks quality Practices conf 0.62 67 occurrences Foundry mined assumption checks: renanarturdemetrio-ai/agents-portal
Comment chain pattern product: assumption_checks Repo: renanarturdemetrio-ai/agents-portal Thread: renanarturdemetrio-ai/agents-portal#336 Outcome: ambiguous_needs_more_evidence Thread label: thread_needs_classification Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_…
67 occurrences
repo-level (67 hits)
medium Security checks quality Practices conf 0.70 2 occurrences Foundry mined unresolved feedback: renanarturdemetrio-ai/agents-portal
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
2 occurrences
repo-level (2 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/amazon-api.js:19
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/amazon-auth.js:21
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/auth-ml.js:148
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/b2b-mp.js:67
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/ml-api-client.js:14
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — olist-v3.js:69
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — pesquisador-central.js:19
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/central-ml.js:79
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/pricing-rules-client.js:90
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/shopee-estrategia.js:220
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/catalogo-residue/reversao.js:191
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/diagnostico-frete-sync/dump-raw.js:39
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/probe-tiny-kit-variacao.js:36
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — server.js:121
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tiny-erp.js:43
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in coverage/prettify.js:2
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
coverage/prettify.js:2 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in coverage/sorter.js:84
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
coverage/sorter.js:84 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in promo-ml/views/promo-admin.html:77
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
promo-ml/views/promo-admin.html:77 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in promo-ml/views/promo-config.html:131
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
promo-ml/views/promo-config.html:131 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/ads-central.html:276
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/ads-central.html:276 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/agente-shopee.html:182
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/agente-shopee.html:182 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/amazon-painel.js:348
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/amazon-painel.js:348 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/atacadaoshow.html:992
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/atacadaoshow.html:992 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/b2b-admin.html:189
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/b2b-admin.html:189 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/b2b.html:225
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/b2b.html:225 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/central-ml-view.js:154
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/central-ml-view.js:154 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/central-ml.js:210
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/central-ml.js:210 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/chocaprime.html:991
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/chocaprime.html:991 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/compras-olist-config.html:74
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/compras-olist-config.html:74 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/compras.html:608
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/compras.html:608 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/financeiro.html:226
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/financeiro.html:226 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/index.html:791
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/index.html:791 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/shopee-v2/componentes.js:34
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/shopee-v2/componentes.js:34 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/shopee-v2/main.js:236
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/shopee-v2/main.js:236 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/marketing.html:574
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/marketing.html:574 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/ml-ads-write.html:215
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/ml-ads-write.html:215 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/ml-central-bloco.js:450
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/ml-central-bloco.js:450 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/ml-modulos-agente.js:186
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/ml-modulos-agente.js:186 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/ml-planilha-promocao.js:31
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/ml-planilha-promocao.js:31 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/ml-reposicionamento.js:49
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/ml-reposicionamento.js:49 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/petbox.html:691
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/petbox.html:691 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/petshow.html:685
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/petshow.html:685 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-ads-granular.js:77
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-ads-granular.js:77 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-atendimento-modulo.js:111
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-atendimento-modulo.js:111 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-conexao-modulo.js:87
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-conexao-modulo.js:87 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-conexoes.html:150
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-conexoes.html:150 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-diagnostico-cards.js:37
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-diagnostico-cards.js:37 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-diagnostico.js:158
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-diagnostico.js:158 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-estrategia.js:36
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-estrategia.js:36 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-financeiro-bloco.js:70
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-financeiro-bloco.js:70 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-health-badge.js:25
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-health-badge.js:25 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-marketing-modulo.js:62
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-marketing-modulo.js:62 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-oportunidades.js:68
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-oportunidades.js:68 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/shopee-pedidos-modulo.js:160
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/shopee-pedidos-modulo.js:160 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/tiktok-painel.js:79
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/tiktok-painel.js:79 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in public/petbox.html:2789
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
public/petbox.html:2789 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in public/petshow.html:2723
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
public/petshow.html:2723 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/atacadaoshow.html:7237
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/atacadaoshow.html:7237 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/chocaprime.html:7119
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/chocaprime.html:7119 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/compras.html:1698
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/compras.html:1698 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/ml-modulos-agente.js:816
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/ml-modulos-agente.js:816 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/diagnostico-frete-sync/upload-session-prod.js:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/diagnostico-frete-sync/upload-session-prod.js:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server.js:2079
Found a known-risky pattern (node_child_process). Review and replace if possible.
server.js:2079 Node child process
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 42 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
low System graph quality Integrity conf 1.00 69 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_PASS`, `ADMIN_USER`, `AGENTE_VENDEDOR_ENABLED`, `AGENTS_PORTAL_URL`, `AMZ_SYNC_DIAS`, `AMZ_SYNC_HORA_MANHA`, `AMZ_SYNC_HORA_TARDE`, `AMZ_TOKEN_ENDPOINT` + 61 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't b…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 467 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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — public/shopee-atendimento-modulo.js:91
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: agente_compras.py:tiny_post, sync_historico.py:tiny_post This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
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 `migracao_listas_enviadas_v1` in server.js:1581
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 `migrateLegacy` in public/pricing-rules-client.js:47
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 `orders_v2` in tests/integration/logs-isolamento-agentes.test.js:105
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 domains/shopee/produtos-sync.js:55
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 tests/unit/shopee-produtos-sync.test.js:36
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 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 — core/auth-ml.js:117
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 — core/ml-painel-scraper.js:213
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 — core/persistence.js:34
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 — coverage/prettify.js:2
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 — precos-app/src/app/api/regras/[id]/route.ts:11
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 — precos-app/src/app/api/regras/route.ts:18
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 — precos-app/src/app/api/skus/[id]/regra/route.ts:27
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 — precos-app/src/app/precos/page.tsx:84
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 — promo-ml/scripts/rollback.js:34
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 — public/shopee-diagnostico.js:296
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 — scripts/amazon-ads-token-exchange.js:50
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 — scripts/catalogo-residue/reversao.js:237
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 — scripts/diagnostico-frete-sync/buscar-valor-painel.js:67
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 — scripts/diagnostico-frete-sync/debug-expanded.js:28
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 — scripts/diagnostico-frete-sync/debug-puppeteer.js:9
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 — scripts/diagnostico-frete-sync/dump-raw.js:32
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 — scripts/diagnostico-frete-sync/internos.js:57
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 — scripts/diagnostico-frete-sync/raw-row-target.js:46
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 — scripts/diagnostico-frete-sync/sync-local-to-prod.js:23
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/diagnostico-frete-sync/teste-puppeteer.js:17
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 — scripts/diagnostico-frete-sync/teste.js:169
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 — scripts/diagnostico-frete-sync/upload-session-prod.js:20
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 — scripts/diagnostico-shopee-petbox/teste-orders.js:115
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 — scripts/discovery/conectavenda/01-reconhecimento-passivo.js:44
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 — scripts/discovery/conectavenda/02-descoberta-auth.js:16
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 — scripts/discovery/conectavenda/03-endpoints-pedidos.js:19
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/discovery/conectavenda/04-endpoints-clientes.js:25
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 — scripts/discovery/conectavenda/05-endpoints-produtos.js:16
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 — scripts/discovery/conectavenda/06-webhooks.js:24
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 — scripts/discovery/conectavenda/07-paginacao-ratelimit.js:16
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 — scripts/discovery/conectavenda/08-casos-erro.js:34
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 — scripts/migracao-shopee-petbox/limpar-token-petbox.js:70
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 — scripts/price-sync-report.js:168
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/probe-tiny-kit-variacao.js:45
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 — server.js:1660
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 — tiny-erp.js:41
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 api Wiring conf 1.00 Unused endpoint: GET /
`server.js` 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 /api/amazon/:conta/ads
`server.js` declares `GET /api/amazon/:conta/ads` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/amazon/:conta/dashboard
`server.js` declares `GET /api/amazon/:conta/dashboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/amazon/:conta/financeiro
`server.js` declares `GET /api/amazon/:conta/financeiro` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/amazon/:conta/health
`server.js` declares `GET /api/amazon/:conta/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/amazon/:conta/inventory
`server.js` declares `GET /api/amazon/:conta/inventory` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/amazon/:conta/listing/:sku
`server.js` declares `GET /api/amazon/:conta/listing/:sku` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/amazon/:conta/listings
`server.js` declares `GET /api/amazon/:conta/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 /api/amazon/:conta/pedido/:orderId/itens
`server.js` declares `GET /api/amazon/:conta/pedido/:orderId/itens` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/amazon/:conta/pedidos
`server.js` declares `GET /api/amazon/:conta/pedidos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/amazon/:conta/simulador
`server.js` declares `GET /api/amazon/:conta/simulador` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/amazon/health
`server.js` declares `GET /api/amazon/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/connect
`server.js` declares `GET /api/connect` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/logs
`server.js` declares `GET /api/logs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/buybox
`server.js` declares `GET /api/ml-central/:conta/buybox` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/claims
`server.js` declares `GET /api/ml-central/:conta/claims` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/custo-reclamacoes
`server.js` declares `GET /api/ml-central/:conta/custo-reclamacoes` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/paridade
`server.js` declares `GET /api/ml-central/:conta/paridade` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/pedidos
`server.js` declares `GET /api/ml-central/:conta/pedidos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/perguntas
`server.js` declares `GET /api/ml-central/:conta/perguntas` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/precificacao
`server.js` declares `GET /api/ml-central/:conta/precificacao` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/promocoes
`server.js` declares `GET /api/ml-central/:conta/promocoes` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/qualidade
`server.js` declares `GET /api/ml-central/:conta/qualidade` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/reputacao
`server.js` declares `GET /api/ml-central/:conta/reputacao` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/:conta/resumo
`server.js` declares `GET /api/ml-central/:conta/resumo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/ads
`server.js` declares `GET /api/ml-central/ads` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml-central/contas
`server.js` declares `GET /api/ml-central/contas` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml/central/alertas
`server.js` declares `GET /api/ml/central/alertas` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml/central/dashboard
`server.js` declares `GET /api/ml/central/dashboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml/central/produtos
`server.js` declares `GET /api/ml/central/produtos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml/custos/reconciliacao
`server.js` declares `GET /api/ml/custos/reconciliacao` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml/item
`server.js` declares `GET /api/ml/item` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml/orders
`server.js` declares `GET /api/ml/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 /api/ml/orders/validar-ontem
`server.js` declares `GET /api/ml/orders/validar-ontem` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ml/precos
`server.js` declares `GET /api/ml/precos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/oauth/callback
`server.js` declares `GET /api/oauth/callback` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/token
`server.js` declares `GET /api/token` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/amazon/:conta/ads/campanhas/:id/estado
`server.js` declares `POST /api/amazon/:conta/ads/campanhas/:id/estado` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/amazon/:conta/ads/campanhas/:id/orcamento
`server.js` declares `POST /api/amazon/:conta/ads/campanhas/:id/orcamento` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/amazon/:conta/preco
`server.js` declares `POST /api/amazon/:conta/preco` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/amazon/:conta/token/limpar
`server.js` declares `POST /api/amazon/:conta/token/limpar` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/logs
`server.js` declares `POST /api/logs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/ml-central/:conta/atendimento/auto
`server.js` declares `POST /api/ml-central/:conta/atendimento/auto` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/ml-central/:conta/atendimento/rascunho
`server.js` declares `POST /api/ml-central/:conta/atendimento/rascunho` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/ml-central/:conta/claim/:id/responder
`server.js` declares `POST /api/ml-central/:conta/claim/:id/responder` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/ml-central/:conta/pergunta/:id/responder
`server.js` declares `POST /api/ml-central/:conta/pergunta/:id/responder` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/ml-central/:conta/promocao/aceitar
`server.js` declares `POST /api/ml-central/:conta/promocao/aceitar` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/ml/itens-sync/agora
`server.js` declares `POST /api/ml/itens-sync/agora` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/ml/precos/bulk-upsert
`server.js` declares `POST /api/ml/precos/bulk-upsert` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/set-token
`server.js` declares `POST /api/set-token` 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: public/ml-modulos-agente.js (830 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server.js (19780 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/92237c5c-f3b0-4f44-90e4-ca1f01c50dcb/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/92237c5c-f3b0-4f44-90e4-ca1f01c50dcb/

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.