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.

ZIJIAN004/UniCOP

https://github.com/ZIJIAN004/UniCOP · scanned 2026-06-16 01:12 UTC (2 months, 1 week ago)

93 raw signals (0 security + 93 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 69 actionable findings from 1 signal source. 24 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 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 6 places
  • low Near-duplicate function bodies in 2 places repo-level
View all duplicates & near-duplicates findings →
Commented-out code 22 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 (10 lines) in Latent-SFT/train.py:119
  • info Commented-code block (6 lines) in Latent-SFT/model.py:41
  • info Commented-code block (7 lines) in UniCOP-Distill/build_reverse_chains.py:249
  • info Commented-code block (5 lines) in UniCOP-Distill/stage2_reasoning/train_sft_sta…
  • info Commented-code block (5 lines) in FOARL/train_grpo_foarl.py:79
  • info Commented-code block (5 lines) in tools/merge_lora.py:47
  • info Commented-code block (11 lines) in UniCOP-Reason-Mask/train.py:32
  • info Commented-code block (5 lines) in UniCOP-Reason-Mask/grpo_prm_trainer.py:93
  • info Commented-code block (19 lines) in UniCOP-Reason-Mask/config.py:36
  • info Commented-code block (7 lines) in UniCOP-Reason-Mask/terminal_reward.py:56
  • info Commented-code block (5 lines) in UniCOP-Reason-Mask/merge_shards.py:25
  • info Commented-code block (5 lines) in UniCOP-Reason-Mask/pomo_prm.py:113
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
  • info Commented-code block (19 lines) in UniCOP-Reason-Mask/config.py:36
  • info Commented-code block (8 lines) in UniCOP-Reason/config.py:36
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/7fb9382d-d08a-4200-bb11-80bd3ced5411/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7fb9382d-d08a-4200-bb11-80bd3ced5411/

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.