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.

Clearvoting/clearvoting

https://github.com/Clearvoting/clearvoting · scanned 2026-06-17 01:23 UTC (1 month, 2 weeks ago)

67 raw signals (0 security + 67 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -8.9 (diff) · 59 actionable findings from 1 signal source. 8 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 59 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 18 Medium 9 Low 31 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 59 Crowd 0 Layer: Hardware 2 Security 5 Cicd 3 Quality 12 Api 37

Exclude dismissed / FP Exclude test files

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 67.8/100 with 77.8% coverage. It contains 913 nodes across 25 cross-layer flows, written primarily in mixed languages. Engine surfaced 67 findings — concentrated in api (37), quality (15), cicd (8). Risk profile is high: 0 critical, 18 high, 9 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/bills/${congress}/${type}/${number} (static/js/bill.js:67)

`static/js/bill.js:67` calls `GET /api/bills/${congress}/${type}/${number}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bills///` If this points at an external API, prefix it with `https://` so the match…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/bills/${congress}/${type}/${number}/ai-summary (static/js/bill.js:232)

`static/js/bill.js:232` calls `GET /api/bills/${congress}/${type}/${number}/ai-summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bills////ai-summary` If this points at an external API, prefix it with …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/bills/${congress}/${type}/${number}/votes (static/js/bill.js:302)

`static/js/bill.js:302` calls `GET /api/bills/${congress}/${type}/${number}/votes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bills////votes` If this points at an external API, prefix it with `https://`…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/members/${bioguideId}/donations (static/js/member.js:921)

`static/js/member.js:921` calls `GET /api/members/${bioguideId}/donations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/members//donations` If this points at an external API, prefix it with `https://` so the ma…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/members/${bioguideId}/sponsored (static/js/member.js:370)

`static/js/member.js:370` calls `GET /api/members/${bioguideId}/sponsored` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/members//sponsored` If this points at an external API, prefix it with `https://` so the ma…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/members/${bioguideId}/summary (static/js/member.js:460)

`static/js/member.js:460` calls `GET /api/members/${bioguideId}/summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/members//summary` If this points at an external API, prefix it with `https://` so the matche…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/members/${bioguideId}/votes?limit=2000 (static/js/member.js:459)

`static/js/member.js:459` calls `GET /api/members/${bioguideId}/votes?limit=2000` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/members//votes` If this points at an external API, prefix it with `https://` so the…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/members/${stateCode}/overview (static/js/state.js:77)

`static/js/state.js:77` calls `GET /api/members/${stateCode}/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/members//overview` If this points at an external API, prefix it with `https://` so the matcher…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/members/counts (static/js/app.js:107)

`static/js/app.js:107` calls `GET /api/members/counts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/members/counts` 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/members/detail/${bioguideId} (static/js/member.js:52)

`static/js/member.js:52` calls `GET /api/members/detail/${bioguideId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/members/detail/` If this points at an external API, prefix it with `https://` so the matcher s…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/members/detail/${bioguideId}?show_party=true (static/js/member.js:149)

`static/js/member.js:149` calls `GET /api/members/detail/${bioguideId}?show_party=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/members/detail/` If this points at an external API, prefix it with `https://`…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/members/detail/${bioguideId}?show_party=true (static/js/member.js:97)

`static/js/member.js:97` calls `GET /api/members/detail/${bioguideId}?show_party=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/members/detail/` If this points at an external API, prefix it with `https://` …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/search/bills?q=${encodeURIComponent(query)}&limit=50 (static/js/app.js:499)

`static/js/app.js:499` calls `GET /api/search/bills?q=${encodeURIComponent(query)}&limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/search/bills` If this points at an external API, prefix it with `https://` …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/votes/latest (static/js/app.js:121)

`static/js/app.js:121` calls `GET /api/votes/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/votes/latest` 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: POST /api/feedback (static/js/feedback.js:144)

`static/js/feedback.js:144` calls `POST /api/feedback` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/feedback` 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: POST /api/notify (static/js/app.js:391)

`static/js/app.js:391` calls `POST /api/notify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/notify` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph security auth conf 1.00 FastAPI POST `submit_feedback` without auth dependency — app/routers/feedback.py:29

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

app/routers/feedback.py:29 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `submit_signup` without auth dependency — app/routers/notify.py:36

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

app/routers/notify.py:36 securityAuth fastapi unauth mutation

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — static/js/bill.js:395

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 — static/js/feedback.js:144

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 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: Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions

CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.

.github/workflows/weekly-sync.yml CI/CD securitySupply chainGithub actions

medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions

CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.

.github/workflows/ai-sync.yml CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in static/js/bill.js:9

Found a known-risky pattern (domparser_html_parse). Review and replace if possible.

static/js/bill.js:9 Domparser html parse

medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in static/js/bill.js:165

Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.

static/js/bill.js:165 Insert adjacent html

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

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, operator-readme. 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 269 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: python:3.12-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

Dockerfile:1 containersPinned dependencies

low System graph cicd CI/CD security conf 1.00 6 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

3 files, 6 locations

.github/workflows/ai-sync.yml:42, 46 (2 hits)

.github/workflows/tests.yml:19, 22 (2 hits)

.github/workflows/weekly-sync.yml:31, 34 (2 hits)

CI/CD securitySupply chainGithub actions

low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: sync.py:sync_bill_summaries, sync.py:sync_bill_arguments 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.

3 occurrences

repo-level (3 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: app/services/summary_grader.py:load_learnings, app/services/arguments_grader.py:load_learnings, app/services/member_narrative_grader.py:load_learnings This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai…

2 occurrences

repo-level (2 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places

Functions with the same first-5-line body hash: sync.py:writer_fn, sync.py:writer_fn, sync.py:writer_fn, sync.py:writer_fn 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 Docs conf 1.00 No README detected

No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.

ReadmeRepo hardeningGenerated repo pattern

low System graph api Wiring conf 1.00 Unused endpoint: GET /

`app/main.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /about

`app/main.py` declares `GET /about` 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 /bill

`app/main.py` declares `GET /bill` 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 /counts

`app/routers/members.py` declares `GET /counts` 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 /detail/{bioguide_id}

`app/routers/members.py` declares `GET /detail/{bioguide_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 /house/{congress}/{session}/{vote_number}

`app/routers/votes.py` declares `GET /house/{congress}/{session}/{vote_number}` 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 /latest

`app/routers/votes.py` declares `GET /latest` 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 /member

`app/main.py` declares `GET /member` 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 /senate/{congress}/{session}/{vote_number}

`app/routers/votes.py` declares `GET /senate/{congress}/{session}/{vote_number}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /state

`app/main.py` declares `GET /state` 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 /{bioguide_id}/donations

`app/routers/members.py` declares `GET /{bioguide_id}/donations` 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 /{bioguide_id}/sponsored

`app/routers/members.py` declares `GET /{bioguide_id}/sponsored` 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 /{bioguide_id}/summary

`app/routers/members.py` declares `GET /{bioguide_id}/summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /{bioguide_id}/votes

`app/routers/members.py` declares `GET /{bioguide_id}/votes` 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 /{congress}/{bill_type}/{bill_number}

`app/routers/bills.py` declares `GET /{congress}/{bill_type}/{bill_number}` 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 /{congress}/{bill_type}/{bill_number}/ai-summary

`app/routers/bills.py` declares `GET /{congress}/{bill_type}/{bill_number}/ai-summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /{congress}/{bill_type}/{bill_number}/votes

`app/routers/bills.py` declares `GET /{congress}/{bill_type}/{bill_number}/votes` 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 /{state_code}

`app/routers/members.py` declares `GET /{state_code}` 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 /{state_code}/overview

`app/routers/members.py` declares `GET /{state_code}/overview` 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 /{state_code}/{district}

`app/routers/members.py` declares `GET /{state_code}/{district}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /

`app/routers/notify.py` declares `POST /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph quality Complexity conf 1.00 Very large file: sync.py (2162 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/df64a179-3277-4d2e-98be-fecb01044e6a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/df64a179-3277-4d2e-98be-fecb01044e6a/

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.