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.

DevonWarrior/tqa-pathfinder

https://github.com/DevonWarrior/tqa-pathfinder · scanned 2026-06-17 01:28 UTC (1 month, 2 weeks ago)

583 raw signals (0 security + 583 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -24.8 (diff) · 521 actionable findings from 1 signal source. 62 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 · 521 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 18 Medium 253 Low 112 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 521 Crowd 0 Layer: Software 21 Frontend 56 Network 2 Hardware 2 Security 24 Cicd 2 Quality 400 Api 14

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

4 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 6 places

View all duplicates & near-duplicates findings →

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

12 matching findings on this repo

medium Insecure pattern 'node_child_process' in .claude/hooks-legacy/gsd-context-monit… .claude/hooks-legacy/gsd-context-monitor.js:24
medium Insecure pattern 'node_child_process' in .claude/hooks-legacy/gsd-check-update-… .claude/hooks-legacy/gsd-check-update-worker.js:14
medium Insecure pattern 'node_child_process' in .claude/hooks-legacy/gsd-check-update.… .claude/hooks-legacy/gsd-check-update.js:9
medium Agent authority lacks a verifier contract: .claude/settings-legacy.json .claude/settings-legacy.json
medium Agent instruction contains unpinned remote install: .claude/settings-legacy.json .claude/settings-legacy.json:15
medium Agent authority lacks a verifier contract: .claude/gsd-file-manifest-legacy.json .claude/gsd-file-manifest-legacy.json
medium Agent authority lacks a verifier contract: .claude/gsd-local-patches-legacy/age… .claude/gsd-local-patches-legacy/agents/gsd-ui-au…
medium Agent authority lacks a verifier contract: .claude/gsd-local-patches-legacy/get… .claude/gsd-local-patches-legacy/get-shit-done/te…
medium Agent authority lacks a verifier contract: .claude/gsd-local-patches-legacy/get… .claude/gsd-local-patches-legacy/get-shit-done/re…
medium Agent authority lacks a verifier contract: .claude/gsd-user-files-backup-legacy… .claude/gsd-user-files-backup-legacy/agents/pytho…
medium Agent authority lacks a verifier contract: .claude/gsd-user-files-backup-legacy… .claude/gsd-user-files-backup-legacy/skills/explo…
medium Agent authority lacks a verifier contract: .claude/gsd-user-files-backup-legacy… .claude/gsd-user-files-backup-legacy/skills/debug…

View all legacy markers findings →

Commented-out code 98 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 tests/services/test_enrichment_service.py:90
info Commented-code block (6 lines) in backend/config.py:220
info Commented-code block (6 lines) in backend/app_factory.py:243
info Commented-code block (5 lines) in backend/tests/test_vision_escalation.py:483
info Commented-code block (5 lines) in backend/tests/conftest.py:6
info Commented-code block (6 lines) in backend/tests/test_proposals_c06_cross_tenant…
info Commented-code block (6 lines) in backend/tests/test_benchmark_extraction_servi…
info Commented-code block (6 lines) in backend/tests/test_enrichment_service.py:115
info Commented-code block (5 lines) in backend/tests/test_file_extraction.py:117
info Commented-code block (8 lines) in backend/tests/test_knowledge_service.py:53
info Commented-code block (5 lines) in backend/tests/test_999_1_service_layer_admin_…
info Commented-code block (5 lines) in backend/tests/test_claude_api_wiring.py:93

View all commented-out code findings →

Config drift 15 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 Possibly dead Python function: patched_config_get backend/app_factory.py:220
high Agent instruction/config may expose a secret: .claude/plans/2026-02-17-composit… .claude/plans/2026-02-17-composite-matrix-scoring…:223
high Agent instruction/config may expose a secret: .claude/plans/2026-02-18-data-gap… .claude/plans/2026-02-18-data-gap-answers-plan.md:518
high Agent instruction/config may expose a secret: .claude/get-shit-done-legacy/refe… .claude/get-shit-done-legacy/references/workstrea…:101
high Agent instruction/config may expose a secret: .claude/get-shit-done/references/… .claude/get-shit-done/references/workstream-flag.…:101
info Commented-code block (6 lines) in backend/config.py:220
low Old/deprecated-named symbol `TestTaxonomyPostConfigDeprecated` in backend/tests…
low Old/deprecated-named symbol `update_config_deprecated` in backend/api/taxonomy.…
low Old/deprecated-named symbol `update_config_deprecated` in backend/scripts/lint_…
info Commented-code block (5 lines) in backend/config/cortex.py:6
info Commented-code block (9 lines) in backend/config/benchmarking.py:8
info Commented-code block (7 lines) in frontend/vitest.config.js:39

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/e5f509f3-b8ac-4bb3-bac2-434b6858932e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e5f509f3-b8ac-4bb3-bac2-434b6858932e/

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.