sipcapture/homer

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.

59 of your 284 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 3.13s · analysis 50.9s · 5.1 MB · GitHub preflight 409ms

https://github.com/sipcapture/homer · scanned 2026-06-05 19:25 UTC (4 days, 16 hours ago) · 10 languages

487 raw signals (271 security + 216 graph) 6th percentile · Go · large (100-500K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 16 hours ago · v2 · 229 actionable findings from 2 signal sources. 150 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 · 84 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	65.0	0.15	9.75
`security_score`	14.6	0.25	3.65
`testing_score`	80.0	0.20	16.00
`documentation_score`	81.6	0.15	12.24
`practices_score`	77.0	0.15	11.55
`code_quality`	36.7	0.10	3.67
Overall		1.00	56.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 96 Medium 33 Low 43 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 145 System graph 84 Crowd 0 Layer: Security 11 Software 129 Cicd 11 Quality 48 Frontend 23 Hardware 5 Api 2

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 1 finding

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.

1 matching finding on this repo

info npm package `@codemirror/legacy-modes` is patch version(s) behind (6.5.2 -> 6.5… src/ui/package.json

View all legacy markers findings →

Commented-out code 9 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/`.

9 matching findings on this repo

info Commented-code block (5 lines) in src/ui/src/dashboard/TransactionModal.tsx:164
info Commented-code block (5 lines) in src/ui/src/dashboard/components/SearchWidgetS…
info Commented-code block (6 lines) in src/ui/src/dashboard/widgets/registry.ts:281
info Commented-code block (6 lines) in src/ui/src/dashboard/widgets/ChessPanel.tsx:63
info Commented-code block (7 lines) in src/ui/src/dashboard/widgets/ChessBoard.tsx:42
info Commented-code block (5 lines) in src/ui/src/dashboard/widgets/SIPetrisPanel.ts…
info Commented-code block (7 lines) in src/ui/src/dashboard/widgets/NetrisPanel.tsx:…
info Commented-code block (5 lines) in src/ui/src/dashboard/widgets/PacketDefenderPa…
info Commented-code block (6 lines) in src/ui/src/dashboard/widgets/chessEngine.test…

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 File has no detected symbols: src/ui/eslint.config.js
low Very large file: src/config/config.go (1793 lines)

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/9a6b9d51-b227-4aae-8dc9-80771afa4e9d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9a6b9d51-b227-4aae-8dc9-80771afa4e9d/

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.