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.

dan-homan/Clustering_Review

https://github.com/dan-homan/Clustering_Review · scanned 2026-06-17 01:52 UTC (1 month, 1 week ago)

27 raw signals (0 security + 27 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ +5.8 (diff) · 25 actionable findings from 1 signal source. 2 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

55.6% cov · 25 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 4 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 25 Crowd 0 Layer: Software 2 Cicd 1 Quality 22

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

2 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Commented-out code 12 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 mojave_review/src/mojave_review/app.py:60
info Commented-code block (8 lines) in mojave_review/src/mojave_review/auth/middlewa…
info Commented-code block (9 lines) in mojave_review/src/mojave_review/plots/overlay…
info Commented-code block (10 lines) in mojave_review/src/mojave_review/plots/summar…
info Commented-code block (7 lines) in mojave_review/src/mojave_review/ui/callbacks.…
info Commented-code block (5 lines) in mojave_review/src/mojave_review/ui/nwin_panel…
info Commented-code block (11 lines) in mojave_review/src/mojave_review/ui/recommend…
info Commented-code block (8 lines) in mojave_review/src/mojave_review/ui/layout.py:…
info Commented-code block (6 lines) in mojave_review/src/mojave_review/ui/recommenda…
info Commented-code block (8 lines) in mojave_review/src/mojave_review/ui/nwin_callb…
info Commented-code block (5 lines) in mojave_review/src/mojave_review/assets/resiza…
info Commented-code block (8 lines) in mojave_review/src/mojave_review/assets/keyboa…

View all commented-out code 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/a33d6df9-ad02-4ff2-9dfc-c787bb716ed8/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a33d6df9-ad02-4ff2-9dfc-c787bb716ed8/

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.