Hello-QM/catgo-LRG

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.

214 of your 317 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 30.94s for a 57.7 MB repo slow.
Repobility's analysis ran in 16.41s after the clone landed.

https://github.com/Hello-QM/catgo-LRG · scanned 2026-06-05 14:56 UTC (5 days, 3 hours ago) · 10 languages

1933 raw signals (297 security + 1636 graph) 11/13 scanners ran 83rd percentile · Typescript · huge (>500K LoC) System graph score 59 (higher by 32)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 744 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	94.0	0.15	14.10
`practices_score`	94.0	0.15	14.10
`code_quality`	45.0	0.10	4.50
Overall		1.00	90.5

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

Severity: Critical 3 High 308 Medium 57 Low 287 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 126 System graph 744 Crowd 0 Layer: Quality 383 Cicd 11 Software 73 Security 264 Frontend 70 Network 3 Hardware 7 Api 59

Exclude dismissed / FP Exclude test files

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 2 places repo-level
low Near-duplicate function bodies in 4 places repo-level
low Near-duplicate function bodies in 7 places
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Legacy markers 6 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

6 matching findings on this repo

low Old/deprecated-named symbol `clear_legacy` in tests/vitest/structure/controller…
low Old/deprecated-named symbol `wfApiLegacy` in server/tests/test_engine_tasks_api…
low Old/deprecated-named symbol `clear_legacy` in src/lib/structure/state/measureme…
low Old/deprecated-named symbol `clear_legacy` in src/lib/structure/controllers/ana…
low Old/deprecated-named symbol `has_forces_legacy` in src/lib/trajectory/parsers/x…
low Old/deprecated-named symbol `migrateLegacy` in src/lib/mobile/connections.ts:64

View all legacy markers findings →

Commented-out code 134 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 (6 lines) in vite.desktop.config.ts:747
info Commented-code block (5 lines) in vite-plugin-agent-bridge.ts:47
info Commented-code block (5 lines) in tests/test_catrender_bridge.py:6
info Commented-code block (6 lines) in tests/fidelity/run_fidelity.py:189
info Commented-code block (8 lines) in tests/playwright/trajectory.test.ts:79
info Commented-code block (5 lines) in tests/playwright/structure-trajectory.test.ts…
info Commented-code block (5 lines) in tests/playwright/structure/render-loop.test.t…
info Commented-code block (5 lines) in tests/playwright/helpers/project_to_pixel.ts:3
info Commented-code block (9 lines) in tests/playwright/helpers/project_to_pixel.tes…
info Commented-code block (6 lines) in tests/playwright/plot/colorbar.test.ts:133
info Commented-code block (6 lines) in tests/vitest/structure/qe-export.test.ts:6
info Commented-code block (5 lines) in tests/vitest/structure/index.test.ts:145

View all commented-out code findings →

Config drift 12 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.

12 matching findings on this repo

high [MINED131] pre-commit hook `https://github.com/pre-commit/pre-commit-hooks` pin… .pre-commit-config.yaml:6
low Possibly dead Python function: load_expanse_config_with_calc_templates server/templates/example_expanse_config.py:85
low File has no detected symbols: playwright.config.ts
low File has no detected symbols: svelte.config.js
low File has no detected symbols: eslint.config.js
low File has no detected symbols: vitest.config.ts
low Stray `console.log` in TS/JS — extensions/vscode/scripts/sync-config.ts:98
info Commented-code block (6 lines) in vite.desktop.config.ts:747
info Commented-code block (5 lines) in workers/cors-relay/vitest.config.ts:7
medium `fetch()` without try/.catch or AbortSignal — workers/cors-relay/vitest.config.…
info Commented-code block (6 lines) in extensions/vscode/vite.webview.config.ts:9
high FastAPI POST `connect_ssh_config` without auth dependency — server/catgo/router… server/catgo/routers/hpc.py:264

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/6b565384-68f5-42ad-a5cf-2addef33ce3d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6b565384-68f5-42ad-a5cf-2addef33ce3d/

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.