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.
54 of your 99 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 169.23s for a 204.7 MB repo slow.
  • Repobility's analysis ran in 2.51s after the clone landed.

Terriao/OpenPCQA

https://github.com/Terriao/OpenPCQA · scanned 2026-06-05 17:47 UTC (4 days, 21 hours ago) · 10 languages

258 raw signals (92 security + 166 graph) 11/13 scanners ran 29th percentile · Python · small (2-20K LoC) System graph score 97 (lower by 38)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 21 hours ago · v2 · 82 actionable findings from 2 signal sources. 93 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 34.0 0.20 6.80
documentation_score 65.0 0.15 9.75
practices_score 30.0 0.15 4.50
code_quality 67.0 0.10 6.70
Overall 1.00 58.8
security_score may be inflated — optional security scanners were skipped on this fast scan
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 2 places repo-level
  • low Near-duplicate function bodies in 4 places
View all duplicates & near-duplicates findings →
Commented-out code 26 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 (11 lines) in ResSCNN/ResSCNN-ms/lib/ms_tools.py:70
  • info Commented-code block (6 lines) in ResSCNN/ResSCNN-ms/lib/data_loaders.py:30
  • info Commented-code block (6 lines) in VQA_PC/mindspore/test/ResNet_mean_with_fast.p…
  • info Commented-code block (7 lines) in VQA_PC/mindspore/test/data_loader.py:5
  • info Commented-code block (6 lines) in VQA_PC/mindspore/train/ResNet_mean_with_fast.…
  • info Commented-code block (6 lines) in VQA_PC/mindspore/train/data_loader.py:5
  • info Commented-code block (7 lines) in PQA-Net/PQA-Net-mindspore/VideoTransforms.py:1
  • info Commented-code block (7 lines) in PQA-Net/PQA-Net-mindspore/TrainModelDTLQ.py:1
  • info Commented-code block (7 lines) in PQA-Net/PQA-Net-mindspore/ImageQualityDataset…
  • info Commented-code block (7 lines) in PQA-Net/PQA-Net-mindspore/Gdn.py:1
  • info Commented-code block (11 lines) in PQA-Net/PQA-Net-mindspore/torch2ms_tools.py:…
  • info Commented-code block (5 lines) in PQA-Net/PQA-Net-mindspore/TrainModelLQ.py:74
View all commented-out code findings →
Config drift 1 finding
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.
1 matching finding on this repo
  • medium No CI/CD configuration found
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/eaa0f019-80ff-461e-98b2-fd1e305cd3b3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/eaa0f019-80ff-461e-98b2-fd1e305cd3b3/

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.