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

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 82.5/100 with 55.6% coverage. It contains 497 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 27 findings — concentrated in quality (24), software (2), cicd (1). Risk profile is low: 0 critical, 0 high, 4 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 13 of 25 actionable findings. 27 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected

No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.

CI/CD securityCoverage

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 13 placeholder/mock markers across 8 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 91 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: mojave_review/src/mojave_review/recommendations/apply.py:apply_recommendation_with_history, mojave_review/src/mojave_review/recommendations/apply.py:apply_recommendation This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — s…

3 occurrences

repo-level (3 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places

Functions with the same first-5-line body hash: mojave_review/src/mojave_review/recommendations/schema.py:from_dict, mojave_review/src/mojave_review/recommendations/schema.py:from_dict, mojave_review/src/mojave_review/recommendations/schema.py:from_dict, mojave_review/src/mojave_review/recommendati…

duplicatesduplication

low System graph quality License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated repo pattern

low System graph software Dead code conf 1.00 Possibly dead Python function: is_finalized

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mojave_review/src/mojave_review/recommendations/store.py:311

low System graph software Dead code conf 1.00 Possibly dead Python function: list_reviewer_files

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mojave_review/src/mojave_review/recommendations/store.py:79

low System graph quality Complexity conf 1.00 Very large file: mojave_review/src/mojave_review/ui/callbacks.py (1094 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

low System graph quality Complexity conf 1.00 Very large file: mojave_review/src/mojave_review/ui/recommendations_callbacks.py (1224 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

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.