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

vitaomf/horus-rj

https://github.com/vitaomf/horus-rj · scanned 2026-06-16 00:51 UTC (2 months, 1 week ago)

169 raw signals (4 security + 165 graph)

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

Complete repo analysis

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

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

Showing 116 of 145 actionable findings. 171 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 security auth conf 0.78 2 occurrences Foundry mined security auth guardrail gaps: vitaomf/horus-rj
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…
2 occurrences
repo-level (2 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET /geo/brazil-states.topojson (frontend/src/components/MapaAtuacaoParlamentar.tsx:139)
`frontend/src/components/MapaAtuacaoParlamentar.tsx:139` calls `GET /geo/brazil-states.topojson` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/geo/brazil-states.topojson` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /geo/brazil-states.topojson (frontend/src/components/MapaBrasil.tsx:39)
`frontend/src/components/MapaBrasil.tsx:39` calls `GET /geo/brazil-states.topojson` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/geo/brazil-states.topojson` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /geo/mun/${view.uf.toLowerCase()}.json (frontend/src/components/MapaAtuacaoParlamentar.tsx:158)
`frontend/src/components/MapaAtuacaoParlamentar.tsx:158` calls `GET /geo/mun/${view.uf.toLowerCase()}.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/geo/mun/<p>.json` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /municipios-rj.json (.claude/worktrees/bold-lichterman-5ba06f/frontend/src/components/MapaRJ.tsx:85)
`.claude/worktrees/bold-lichterman-5ba06f/frontend/src/components/MapaRJ.tsx:85` calls `GET /municipios-rj.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/municipios-rj.json` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://dadosabertos.camara.leg.br/api/v2/deputados?nome=${encodeURIComponent(data.nome)}&itens=5 (.claude/worktrees/bold-lichterman-5ba06f/frontend/src/pages/PoliticoPage.tsx:168)
`.claude/worktrees/bold-lichterman-5ba06f/frontend/src/pages/PoliticoPage.tsx:168` calls `GET https://dadosabertos.camara.leg.br/api/v2/deputados?nome=${encodeURIComponent(data.nome)}&itens=5` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized p…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `enviar_feedback` without auth dependency — backend/api.py:3368
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api.py:3368 securityAuth fastapi unauth mutation
medium Security checks quality Practices conf 0.62 3 occurrences Foundry mined assumption checks: vitaomf/horus-rj
Comment chain pattern product: assumption_checks Repo: vitaomf/horus-rj Thread: vitaomf/horus-rj#3 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_ha…
3 occurrences
repo-level (3 hits)
medium Security checks quality Practices conf 0.70 Foundry mined unresolved feedback: vitaomf/horus-rj
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: weak…
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — .claude/worktrees/bold-lichterman-5ba06f/frontend/src/pages/BuscaAvancadaPage.tsx:123
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 — .claude/worktrees/bold-lichterman-5ba06f/frontend/src/pages/PoliticoPage.tsx:168
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 — .claude/worktrees/bold-lichterman-5ba06f/frontend/src/pages/PoliticosListPage.tsx:44
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 — .claude/worktrees/bold-lichterman-5ba06f/vercel-proxy/api/proxy.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 — frontend/src/pages/BuscaAvancadaPage.tsx:126
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 — frontend/src/pages/ParlamentaresListPage.tsx:93
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 — frontend/src/pages/PoliticosListPage.tsx:52
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 — vercel-proxy/api/proxy.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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.local.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/settings.local.json VerificationClaude instruction
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 hardware Security conf 1.00 Dockerfile runs as root: .claude/worktrees/bold-lichterman-5ba06f/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: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 6 occurrences Frontend route `/regiao/:slugRegiao` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
6 occurrences
repo-level (6 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in .claude/static-server.js:44
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
.claude/static-server.js:44 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in .claude/worktrees/bold-lichterman-5ba06f/.claude/static-server.js:44
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
.claude/worktrees/bold-lichterman-5ba06f/.claude/static-server.js:44 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in .claude/worktrees/bold-lichterman-5ba06f/CLAUDE.md:89
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
.claude/worktrees/bold-lichterman-5ba06f/CLAUDE.md:89 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in CLAUDE.md:152
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
CLAUDE.md:152 Cors wildcard
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — .claude/worktrees/bold-lichterman-5ba06f/scripts/legacy/check_results.py:15
`urllib.request.urlopen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — .claude/worktrees/bold-lichterman-5ba06f/scripts/legacy/debug_json.py:5
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — .claude/worktrees/bold-lichterman-5ba06f/scripts/legacy/debug_orgaos.py:10
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — .claude/worktrees/bold-lichterman-5ba06f/scripts/legacy/debug_portal_contratos.py:17
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
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 57 placeholder/mock markers across 19 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
3 test file(s) for 175 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
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 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 609 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 Docker base image is tag-pinned but not digest-pinned: node:20-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:2 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
.claude/worktrees/bold-lichterman-5ba06f/Dockerfile:2 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:10 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
.claude/worktrees/bold-lichterman-5ba06f/Dockerfile:10 containersPinned dependencies
low System graph quality Integrity conf 1.00 19 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: coleta_emendas.py:processar_valor, .claude/worktrees/bold-lichterman-5ba06f/coleta_emendas.py:processar_valor 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…
19 occurrences
repo-level (19 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/fix_mandatos_legislaturas.py:main, scripts/migrate_votacoes_agg.py:main, scripts/coleta_indices_ibge.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or doc…
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 `rest_v1` in backend/api.py:2768
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 `rest_v1` in scripts/bio_wikipedia.py:7
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 `rest_v1` in scripts/download_fotos_governadores.py:83
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 `transparencia_rj_backup` in .claude/worktrees/bold-lichterman-5ba06f/rebuild_db.py:6
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 `transparencia_rj_backup` in rebuild_db.py:6
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: backup_banco
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scheduler/scheduler.py:92
low System graph software Dead code conf 1.00 Possibly dead Python function: coletar_ano_api
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
coleta_emendas.py:255
low System graph software Dead code conf 1.00 Possibly dead Python function: coletar_ano_api
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/worktrees/bold-lichterman-5ba06f/coleta_emendas.py:201
low System graph software Dead code conf 1.00 Possibly dead Python function: coletar_contratos
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/worktrees/bold-lichterman-5ba06f/scheduler/scheduler.py:77
low System graph software Dead code conf 1.00 Possibly dead Python function: coletar_contratos
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scheduler/scheduler.py:80
low System graph software Dead code conf 1.00 Possibly dead Python function: coletar_tse
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/worktrees/bold-lichterman-5ba06f/scheduler/scheduler.py:80
low System graph software Dead code conf 1.00 Possibly dead Python function: coletar_tse
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scheduler/scheduler.py:83
low System graph software Dead code conf 1.00 Possibly dead Python function: coletar_votacoes_camara
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scheduler/scheduler.py:86
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_and_update
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/worktrees/bold-lichterman-5ba06f/scripts/legacy/fix_politico_id.py:24
low System graph software Dead code conf 1.00 Possibly dead Python function: probe
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/varre_sapl.py:55
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 — .claude/static-server.js:53
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 — .claude/worktrees/bold-lichterman-5ba06f/.claude/static-server.js:53
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 /api/assembleia/casas
`backend/api.py` declares `GET /api/assembleia/casas` 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/busca/global
`backend/api.py` declares `GET /api/busca/global` 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/camara/agenda
`backend/api.py` declares `GET /api/camara/agenda` 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/camara/atividade
`backend/api.py` declares `GET /api/camara/atividade` 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/camara/bio
`backend/api.py` declares `GET /api/camara/bio` 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/camara/pauta/{evento_id}
`backend/api.py` declares `GET /api/camara/pauta/{evento_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 /api/camara/votacoes-recentes
`backend/api.py` declares `GET /api/camara/votacoes-recentes` 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/eleitos/estadual
`backend/api.py` declares `GET /api/eleitos/estadual` 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/eleitos/municipal
`backend/api.py` declares `GET /api/eleitos/municipal` 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/emendas/busca
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/emendas/busca` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/emendas/por_uf
`backend/api.py` declares `GET /api/emendas/por_uf` 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/emendas/total
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/emendas/total` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/estados/{uf}/stats
`backend/api.py` declares `GET /api/estados/{uf}/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/estatisticas
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/estatisticas` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/foto/{politico_id}
`backend/api.py` declares `GET /api/foto/{politico_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 /api/foto_tse/{kind}/{registro_id}
`backend/api.py` declares `GET /api/foto_tse/{kind}/{registro_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 /api/health
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/inconsistencias
`backend/api.py` declares `GET /api/inconsistencias` 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/indices/municipio_por_nome
`backend/api.py` declares `GET /api/indices/municipio_por_nome` 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/indices/{nivel}/{territorio_id}
`backend/api.py` declares `GET /api/indices/{nivel}/{territorio_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 /api/municipios
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/municipios` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/municipios/heatmap
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/municipios/heatmap` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/municipios/ranking
`backend/api.py` declares `GET /api/municipios/ranking` 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/municipios/{municipio_id}/emendas
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/municipios/{municipio_id}/emendas` 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 removin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/municipios/{municipio_id}/problemas
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/municipios/{municipio_id}/problemas` 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 remov…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/municipios/{nome}/contratos
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/municipios/{nome}/contratos` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/municipios/{nome}/detalhes
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/municipios/{nome}/detalhes` 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 do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/politicos
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/politicos` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/politicos/busca
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/politicos/busca` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/politicos/total
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/politicos/total` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/politicos/{politico_id}
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/politicos/{politico_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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/politicos/{politico_id}/cruzamento
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /api/politicos/{politico_id}/cruzamento` 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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/politicos/{politico_id}/distribuicao
`backend/api.py` declares `GET /api/politicos/{politico_id}/distribuicao` 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/politicos/{politico_id}/distribuicao_municipios
`backend/api.py` declares `GET /api/politicos/{politico_id}/distribuicao_municipios` 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/politicos/{politico_id}/emendas
`backend/api.py` declares `GET /api/politicos/{politico_id}/emendas` 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/politicos/{politico_id}/perfil_tipo
`backend/api.py` declares `GET /api/politicos/{politico_id}/perfil_tipo` 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/politicos/{politico_id}/ranking
`backend/api.py` declares `GET /api/politicos/{politico_id}/ranking` 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/politicos/{politico_id}/scorecard_legislativo
`backend/api.py` declares `GET /api/politicos/{politico_id}/scorecard_legislativo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/politicos/{politico_id}/trajetoria
`backend/api.py` declares `GET /api/politicos/{politico_id}/trajetoria` 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/politicos/{politico_id}/votacoes_nominais
`backend/api.py` declares `GET /api/politicos/{politico_id}/votacoes_nominais` 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/politicos/{politico_id}/votos
`backend/api.py` declares `GET /api/politicos/{politico_id}/votos` 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/politicos/{politico_id}/wikipedia
`backend/api.py` declares `GET /api/politicos/{politico_id}/wikipedia` 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/sapl/casas
`backend/api.py` declares `GET /api/sapl/casas` 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/sapl/resolver
`backend/api.py` declares `GET /api/sapl/resolver` 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/sapl/{casa}/agenda
`backend/api.py` declares `GET /api/sapl/{casa}/agenda` 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/sapl/{casa}/materias
`backend/api.py` declares `GET /api/sapl/{casa}/materias` 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/sapl/{casa}/votacoes
`backend/api.py` declares `GET /api/sapl/{casa}/votacoes` 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/status/coleta
`backend/api.py` declares `GET /api/status/coleta` 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 /{rest_of_path:path}
`.claude/worktrees/bold-lichterman-5ba06f/backend/api.py` declares `GET /{rest_of_path:path}` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/feedback
`backend/api.py` declares `POST /api/feedback` 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: .claude/worktrees/bold-lichterman-5ba06f/frontend/src/pages/PoliticoPage.tsx (1047 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/api.py (3944 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/PoliticoPage.tsx (2065 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/092029ee-d3cf-4b6f-a894-9d1f1294d3d5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/092029ee-d3cf-4b6f-a894-9d1f1294d3d5/

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.