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.

tyroneross/build-loop

https://github.com/tyroneross/build-loop · scanned 2026-06-16 00:44 UTC (2 months, 1 week ago)

229 raw signals (0 security + 229 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 205 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 6 Medium 25 Low 70 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 205 Crowd 0 Layer: Software 28 Frontend 12 Network 3 Security 8 Cicd 4 Quality 150

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

3 matching findings on this repo

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

View all duplicates & near-duplicates findings →

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

5 matching findings on this repo

low Old/deprecated-named symbol `feedback_legacy` in tests/test_memory_consolidatio…
info Commented-code block (6 lines) in tests/test_no_legacy_memory_paths.py:46
low Old/deprecated-named symbol `resolved_legacy` in scripts/test_dual_write_mirror…
low Old/deprecated-named symbol `sql_legacy` in scripts/write_decision/dbwrite.py:1…
low Old/deprecated-named symbol `runs_legacy` in scripts/write_run_entry/iohelpers.…

View all legacy markers findings →

Commented-out code 102 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 (11 lines) in conftest.py:32
info Commented-code block (5 lines) in tests/test_rerank_daemon.py:392
info Commented-code block (5 lines) in tests/test_recall_graph.py:203
info Commented-code block (5 lines) in tests/test_phase_6_gating_docs.py:56
info Commented-code block (6 lines) in tests/test_no_legacy_memory_paths.py:46
info Commented-code block (11 lines) in tests/test_capture_violation_contract.py:202
info Commented-code block (6 lines) in tests/test_orchestrator_skeleton.py:140
info Commented-code block (5 lines) in tests/test_migrate_project_memory.py:133
info Commented-code block (6 lines) in tests/architecture/test_analysis.py:68
info Commented-code block (6 lines) in scripts/rally_poll_gate.py:41
info Commented-code block (5 lines) in scripts/judgment_gate.py:73
info Commented-code block (5 lines) in scripts/promote_violation_to_lesson.py:302

View all commented-out code findings →

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

6 matching findings on this repo

low Stray `console.log` in TS/JS — src/config.ts:83
high Agent instruction/config may expose a secret: skills/spec-writing/SKILL.md skills/spec-writing/SKILL.md:291
high Agent instruction/config may expose a secret: skills/security-methodology/SKILL… skills/security-methodology/SKILL.md:84
high Agent instruction/config may expose a secret: skills/plan-verify/SKILL.md skills/plan-verify/SKILL.md:62
high Agent instruction/config may expose a secret: skills/model-tiering/SKILL.md skills/model-tiering/SKILL.md:204
high Agent instruction/config may expose a secret: skills/knowledge/SKILL.md skills/knowledge/SKILL.md:112

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/52a892a9-992b-4c7c-89d3-666e19a58326/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/52a892a9-992b-4c7c-89d3-666e19a58326/

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.