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.

tkovack10/dumbroof-web

https://github.com/tkovack10/dumbroof-web · scanned 2026-06-16 00:38 UTC (2 months, 2 weeks ago)

726 raw signals (0 security + 726 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 712 actionable findings from 1 signal source. 14 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 · 712 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 287 Medium 69 Low 142 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 712 Crowd 0 Layer: Software 27 Frontend 76 Hardware 3 Security 14 Quality 268 Api 324

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 6 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.

6 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 17 places
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 9 places

View all duplicates & near-duplicates findings →

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

2 matching findings on this repo

low Old/deprecated-named symbol `cfg_legacy` in backend/tests/test_material_enum.py…
low Old/deprecated-named symbol `canSubmitLegacy` in src/app/sign/[id]/sign-form.ts…

View all legacy markers findings →

Commented-out code 156 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 (7 lines) in scripts/parity_harness_ship3.py:179
info Commented-code block (7 lines) in scripts/import_national_prices.py:38
info Commented-code block (6 lines) in scripts/import_pricing_to_tables.py:66
info Commented-code block (5 lines) in backend/code_compliance.py:16
info Commented-code block (6 lines) in backend/test_noaa_source_priority.py:73
info Commented-code block (10 lines) in backend/compliance_report.py:72
info Commented-code block (6 lines) in backend/qa_pdf_checks.py:295
info Commented-code block (7 lines) in backend/carrier_analyst.py:79
info Commented-code block (5 lines) in backend/email_voice.py:110
info Commented-code block (8 lines) in backend/model_config.py:170
info Commented-code block (5 lines) in backend/pdf_templates.py:1609
info Commented-code block (5 lines) in backend/xactimate_lookup.py:87

View all commented-out code findings →

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

4 matching findings on this repo

medium Runtime service client appears to use placeholder configuration
info Commented-code block (8 lines) in backend/model_config.py:170
low Old/deprecated-named symbol `claim_config_backup` in backend/reprocess_13_chris…
info Commented-code block (6 lines) in src/lib/stripe-config.test.ts:69

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/b1d7fa62-2fcd-45d8-8093-e4474899e5b1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b1d7fa62-2fcd-45d8-8093-e4474899e5b1/

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.