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.

civdotiq/civ.iq

https://github.com/civdotiq/civ.iq · scanned 2026-06-17 01:50 UTC (1 month, 1 week ago)

675 raw signals (0 security + 675 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -28.2 (diff) · 665 actionable findings from 1 signal source. 10 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 · 665 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 156 Medium 286 Low 129 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 665 Crowd 0 Layer: Frontend 177 Security 53 Cicd 4 Quality 276 Api 155

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.

Legacy markers 8 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.

8 matching findings on this repo

info `truncate` class without `title=` for hover reveal — src/components/states/Lega…
medium `fetch()` without try/.catch or AbortSignal — src/app/(civic)/regulations/Legac…
medium `fetch()` without try/.catch or AbortSignal — src/app/api/legacy/redirect-helpe…
medium `fetch()` without try/.catch or AbortSignal — src/components/states/LegacyState…
low Old/deprecated-named symbol `cdLegacy` in src/lib/census-geocoder.ts:337
high Dangling fetch: GET /api/federal-register?${params} (src/app/(civic)/regulation…
high Dangling fetch: GET /api/state-legislature/${state.toUpperCase()} (src/componen…
high Dangling fetch: GET /api/state-bills/${state.toUpperCase()}?limit=10 (src/compo…

View all legacy markers findings →

Commented-out code 39 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 (8 lines) in jest.setup.js:126
info Commented-code block (8 lines) in packages/entity-resolution/src/bioguide-fec-m…
info Commented-code block (6 lines) in scripts/update-zip-mappings.js:88
info Commented-code block (6 lines) in scripts/rewrite-dist-js-extensions.mjs:4
info Commented-code block (7 lines) in scripts/diagnose-fec.js:12
info Commented-code block (5 lines) in src/app/api/search/route.ts:494
info Commented-code block (5 lines) in src/app/api/geocode/route.ts:65
info Commented-code block (5 lines) in src/app/api/districts/[districtId]/route.ts:2…
info Commented-code block (5 lines) in src/app/api/representative/[bioguideId]/finan…
info Commented-code block (5 lines) in src/hooks/useEnhancedDistrictData.ts:122
info Commented-code block (6 lines) in src/components/questions/CommitteeActivityAns…
info Commented-code block (5 lines) in src/components/ask/AskEntryPage/AskEntryPage.…

View all commented-out code findings →

Config drift 2 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.

2 matching findings on this repo

low Stray `console.log` in TS/JS — src/config/env-validation.ts:149
medium Runtime service client appears to use placeholder configuration

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/73390efb-77d4-452a-91fb-79470b85e34c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/73390efb-77d4-452a-91fb-79470b85e34c/

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.