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.

D4vidHuang/CoRefusion

https://github.com/D4vidHuang/CoRefusion · scanned 2026-06-17 01:25 UTC (1 month, 2 weeks ago)

85 raw signals (0 security + 85 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 6 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.
6 matching findings on this repo
  • low Near-duplicate function bodies in 8 places repo-level
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 6 places
  • low Near-duplicate function bodies in 3 places repo-level
  • low Near-duplicate function bodies in 4 places repo-level
  • low Near-duplicate function bodies in 5 places repo-level
View all duplicates & near-duplicates findings →
Commented-out code 8 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/`.
8 matching findings on this repo
  • info Commented-code block (5 lines) in experiments/compare_math_vs_smell_noise.py:441
  • info Commented-code block (13 lines) in experiments/benchmark_codet5p_16b.py:330
  • info Commented-code block (8 lines) in experiments/experiment_deobfuscation.py:490
  • info Commented-code block (7 lines) in experiments/experiment_denoise_sbs.py:157
  • info Commented-code block (7 lines) in experiments/smell_as_noise_refactoring/run_ex…
  • info Commented-code block (11 lines) in analysis/plot_overconfidence.py:122
  • info Commented-code block (7 lines) in analysis/paper_figures.py:110
  • info Commented-code block (5 lines) in analysis/check_code_integrity.py:14
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/652ce6d6-07df-422e-8360-269c587074f0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/652ce6d6-07df-422e-8360-269c587074f0/

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.