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.

Rafael-2109/frete-sistema

https://github.com/Rafael-2109/frete-sistema · scanned 2026-06-15 23:48 UTC (2 months, 3 weeks ago)

1369 raw signals (0 security + 1369 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 1356 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 337 Medium 360 Low 383 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1356 Crowd 0 Layer: Software 24 Frontend 57 Network 5 Security 146 Cicd 1 Quality 784 Api 339

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 7 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

7 matching findings on this repo

low Near-duplicate function bodies in 17 places
low Near-duplicate function bodies in 10 places repo-level
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 23 places
low Near-duplicate function bodies in 5 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 6 places

View all duplicates & near-duplicates findings →

Legacy markers 11 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

11 matching findings on this repo

low Old/deprecated-named symbol `medir_consumo_mo_legacy` in tests/odoo/services/te…
low Old/deprecated-named symbol `is_utilities_legacy` in scripts/audits/ui_audit.py…
low Old/deprecated-named symbol `important_outside_legacy` in scripts/audits/ui_pol…
low Old/deprecated-named symbol `_tem_permissao_legacy` in app/auth/models.py:431
low Old/deprecated-named symbol `medir_consumo_mo_legacy` in app/odoo/estoque/scrip…
low Old/deprecated-named symbol `sub_legacy` in app/carvia/routes/frete_routes.py:2…
low Old/deprecated-named symbol `forma_legacy` in app/hora/services/venda_service.p…
low Old/deprecated-named symbol `pagamento_misto_legacy` in app/hora/services/tagpl…
low Old/deprecated-named symbol `rules_block_tail_legacy` in app/agente/sdk/memory_…
low Old/deprecated-named symbol `api_get_user_permissions_legacy` in backups/permis…
low Old/deprecated-named symbol `api_get_user_permissions_legacy` in backups/permis…

View all legacy markers findings →

Commented-out code 264 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (5 lines) in worker_render.py:197
info Commented-code block (7 lines) in tests/conftest.py:20
info Commented-code block (5 lines) in tests/odoo/services/test_faturamento_pipeline…
info Commented-code block (8 lines) in tests/odoo/services/test_stock_picking_servic…
info Commented-code block (6 lines) in tests/odoo/services/test_stock_internal_trans…
info Commented-code block (6 lines) in tests/carvia/test_a1_a2_linking.py:314
info Commented-code block (5 lines) in tests/carvia/test_peso_frete_carvia.py:124
info Commented-code block (5 lines) in tests/inventario/test_movimentacoes_drill_dow…
info Commented-code block (7 lines) in tests/agente/workers/test_plan_verifier.py:378
info Commented-code block (5 lines) in tests/agente/services/test_enrich_merge_versi…
info Commented-code block (6 lines) in tests/motos_assai/test_carregamento_finalizar…
info Commented-code block (6 lines) in tests/motos_assai/test_carregamento_service_c…

View all commented-out code findings →

Config drift 26 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

12 matching findings on this repo

low Very large file: app/agente/config/feature_flags.py (1279 lines)
low Very large file: app/agente/config/permissions.py (1129 lines)
high Agent instruction/config may expose a secret: app/whatsapp/CLAUDE.md app/whatsapp/CLAUDE.md:32
high Agent instruction/config may expose a secret: .claude/atualizacoes/sentry/atual… .claude/atualizacoes/sentry/atualizacao-2026-05-0…:41
high Agent instruction/config may expose a secret: .claude/atualizacoes/dominios/dom… .claude/atualizacoes/dominios/dominio-8-improveme…:67
high Agent instruction/config may expose a secret: .claude/atualizacoes/improvement-… .claude/atualizacoes/improvement-dialogue/dialogu…:27
high Agent instruction/config may expose a secret: .claude/atualizacoes/improvement-… .claude/atualizacoes/improvement-dialogue/dialogu…:27
high Agent instruction/config may expose a secret: .claude/atualizacoes/improvement-… .claude/atualizacoes/improvement-dialogue/dialogu…:26
high Agent instruction/config may expose a secret: .claude/atualizacoes/improvement-… .claude/atualizacoes/improvement-dialogue/dialogu…:25
high Agent instruction/config may expose a secret: .claude/atualizacoes/improvement-… .claude/atualizacoes/improvement-dialogue/dialogu…:25
high Agent instruction/config may expose a secret: .claude/atualizacoes/improvement-… .claude/atualizacoes/improvement-dialogue/dialogu…:118
high Agent instruction/config may expose a secret: .claude/atualizacoes/improvement-… .claude/atualizacoes/improvement-dialogue/dialogu…:26

View all config drift findings →

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/5e61fc03-fa9a-4f88-b66e-7751f209a3b4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5e61fc03-fa9a-4f88-b66e-7751f209a3b4/

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.