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.

WindriderQc/aiOPs

https://github.com/WindriderQc/aiOPs · scanned 2026-06-16 00:59 UTC (2 months, 1 week ago)

683 raw signals (0 security + 683 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 682 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 682 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 243 Medium 202 Low 152 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 682 Crowd 0 Layer: Software 3 Frontend 89 Network 1 Hardware 5 Security 146 Cicd 3 Quality 156 Api 279

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.

Legacy markers 3 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.

3 matching findings on this repo

low Old/deprecated-named symbol `_notifyLegacy` in mc/src/lib/chat-store.ts:39
low Old/deprecated-named symbol `dropLegacy` in core/scripts/migrate-pinned-models.…
low Old/deprecated-named symbol `foundLegacy` in core/routes/nerve-center-host-pref…

View all legacy markers findings →

Commented-out code 60 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 (5 lines) in mc/src/components/chat-view.tsx:395
info Commented-code block (7 lines) in rag/src/services/ragStore.js:64
info Commented-code block (5 lines) in rag/src/services/embeddings.js:33
info Commented-code block (6 lines) in benchmark/server.js:301
info Commented-code block (10 lines) in benchmark/models/BenchmarkPrompt.js:127
info Commented-code block (5 lines) in benchmark/models/JudgeGroundTruth.js:69
info Commented-code block (5 lines) in benchmark/models/BenchmarkResult.js:296
info Commented-code block (7 lines) in benchmark/tests/unit/extractThinkingBlocks.te…
info Commented-code block (5 lines) in benchmark/tests/unit/judgeCall.test.js:108
info Commented-code block (5 lines) in benchmark/tests/unit/judgeFeedbackLoop.test.j…
info Commented-code block (6 lines) in benchmark/tests/unit/scoring/scorerCountEnfor…
info Commented-code block (5 lines) in benchmark/tests/unit/scoring/reasoningFormatG…

View all commented-out code findings →

Config drift 18 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

info `truncate` class without `title=` for hover reveal — mc/src/components/config-e…
low Icon-only button without accessible name — benchmark/public/js/benchmark-v2/bat…
medium Insecure pattern 'node_child_process' in mc/next.config.ts:2 mc/next.config.ts:2
medium Insecure pattern 'direct_innerhtml_assignment' in benchmark/public/js/benchmark… benchmark/public/js/benchmark-v2/batch-config.js:123
medium Insecure pattern 'insert_adjacent_html' in benchmark/public/js/benchmark-v2/bat… benchmark/public/js/benchmark-v2/batch-config.js:174
medium Insecure pattern 'direct_innerhtml_assignment' in benchmark/public/js/courthous… benchmark/public/js/courthouse-v2/judging-config.…:130
medium Insecure pattern 'direct_innerhtml_assignment' in core/public/js/models-executi… core/public/js/models-execution-config.js:76
medium Insecure pattern 'direct_innerhtml_assignment' in core/public/js/chat/chat-conf… core/public/js/chat/chat-config.js:540
low Very large file: mc/src/components/config-editor.tsx (2072 lines)
low Very large file: benchmark/public/js/benchmark-v2/batch-config.js (1797 lines)
medium `fetch()` without try/.catch or AbortSignal — mc/src/components/config-editor.t…
info Commented-code block (6 lines) in benchmark/public/js/benchmark-v2/batch-config…

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/9b8841e8-8bfe-43fb-8526-719180207dd5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9b8841e8-8bfe-43fb-8526-719180207dd5/

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.