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.

xxxcoolestFish/VLDB_Distance_experiment

https://github.com/xxxcoolestFish/VLDB_Distance_experiment · scanned 2026-06-16 01:03 UTC (2 months, 1 week ago)

74 raw signals (0 security + 74 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 59 actionable findings from 1 signal source. 15 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 5 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.
5 matching findings on this repo
  • low Near-duplicate function bodies in 6 places repo-level
  • low Near-duplicate function bodies in 14 places
  • low Near-duplicate function bodies in 8 places
  • low Near-duplicate function bodies in 2 places
  • low Near-duplicate function bodies in 3 places repo-level
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 (14 lines) in train.py:980
  • info Commented-code block (14 lines) in ablation_study/models/train.py:912
  • info Commented-code block (7 lines) in ablation_study/models/torch_utils.py:317
  • info Commented-code block (5 lines) in ablation_study/models/data_utils.py:983
  • info Commented-code block (8 lines) in models/sparse_matrix_model.py:82
  • info Commented-code block (14 lines) in modified/train.py:865
  • info Commented-code block (7 lines) in utils/torch_utils.py:317
  • info Commented-code block (5 lines) in utils/data_utils.py:983
  • info Commented-code block (14 lines) in original/train.py:865
  • info Commented-code block (8 lines) in original/sparse_matrix_model.py:82
  • info Commented-code block (7 lines) in original/torch_utils.py:317
  • info Commented-code block (5 lines) in original/data_utils.py:905
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/cbfd686e-05fa-4ebf-9ba9-14bcb5b11f84/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cbfd686e-05fa-4ebf-9ba9-14bcb5b11f84/

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.