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.

kvcache-ai/ktransformers

https://github.com/kvcache-ai/ktransformers · scanned 2026-07-23 19:43 UTC (4 days, 21 hours ago)

626 raw signals (0 security + 626 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 21 hours ago · v4 · 606 actionable findings from 1 signal source. 20 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 · 606 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 18 High 143 Medium 272 Low 147 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 606 Crowd 0 Layer: Software 15 Frontend 6 Security 398 Hardware 6 Cicd 3 Quality 108 Dependencies 70

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 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
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

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

2 matching findings on this repo

medium FastAPI POST `create_completion` without auth dependency — archive/kt-sft/ktran… archive/kt-sft/ktransformers/server/api/openai/le…:14
medium FastAPI POST `create_completion` without auth dependency — archive/ktransformer… archive/ktransformers/server/api/openai/legacy/co…:14

View all legacy markers 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 (7 lines) in archive/kt-sft/withoutKT_PEFT.py:95 archive/kt-sft/withoutKT_PEFT.py:95
info Commented-code block (5 lines) in archive/kt-sft/merge_tensors/merge_safetensor… archive/kt-sft/merge_tensors/merge_safetensor_ggu…:42
info Commented-code block (8 lines) in archive/kt-sft/ktransformers/local_chat.py:238 archive/kt-sft/ktransformers/local_chat.py:238
info Commented-code block (6 lines) in archive/kt-sft/ktransformers/moe_test_module_… archive/kt-sft/ktransformers/moe_test_module_old.…:37
info Commented-code block (5 lines) in archive/kt-sft/ktransformers/lora_test_module… archive/kt-sft/ktransformers/lora_test_module.py:106
info Commented-code block (16 lines) in archive/kt-sft/ktransformers/util/custom_ggu… archive/kt-sft/ktransformers/util/custom_gguf.py:715
info Commented-code block (6 lines) in archive/kt-sft/ktransformers/operators/expert… archive/kt-sft/ktransformers/operators/experts.py:643
info Commented-code block (5 lines) in archive/kt-sft/ktransformers/operators/RoPE.p… archive/kt-sft/ktransformers/operators/RoPE.py:213
info Commented-code block (7 lines) in archive/kt-sft/ktransformers/operators/models… archive/kt-sft/ktransformers/operators/models.py:1570
info Commented-code block (13 lines) in archive/kt-sft/ktransformers/sft/flops_utils… archive/kt-sft/ktransformers/sft/flops_utils/lora…:142
info Commented-code block (10 lines) in archive/kt-sft/ktransformers/sft/peft_utils/… archive/kt-sft/ktransformers/sft/peft_utils/lora_…:415
info Commented-code block (5 lines) in archive/kt-sft/ktransformers/server/balance_s… archive/kt-sft/ktransformers/server/balance_serve…:241

View all commented-out code findings →

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

7 matching findings on this repo

high CVE-2025-25975: parse-git-config 3.0.0 — archive/kt-sft/ktransformers/website/p…
high CVE-2025-25975: parse-git-config 3.0.0 — archive/ktransformers/website/package-…
low Old/deprecated-named symbol `deepseek_v2` in archive/kt-sft/ktransformers/model…
low Old/deprecated-named symbol `deepseek_v2` in archive/kt-sft/ktransformers/confi…
low Old/deprecated-named symbol `deepseek_v2` in archive/ktransformers/models/confi…
low Old/deprecated-named symbol `_deep_copy` in kt-kernel/python/cli/config/setting…
medium Network/subprocess call without timeout or try/except — kt-kernel/python/cli/co… kt-kernel/python/cli/commands/config.py:115

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/5a2dcb17-955a-4003-a052-52b5eb857cff/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5a2dcb17-955a-4003-a052-52b5eb857cff/

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.