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.

MoonshotAI/kimi-cli

https://github.com/MoonshotAI/kimi-cli · scanned 2026-07-23 19:41 UTC (4 days, 18 hours ago)

557 raw signals (0 security + 557 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 18 hours ago · v7 · last Δ +5.7 (diff) · 535 actionable findings from 1 signal source. 22 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 2 places
  • low Near-duplicate function bodies in 4 places
View all duplicates & near-duplicates findings →
Legacy markers 7 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.
7 matching findings on this repo
  • low Old/deprecated-named symbol `OpenAILegacy` in packages/kosong/src/kosong/chat_p…
  • low Old/deprecated-named symbol `openai_legacy` in packages/kosong/src/kosong/contr…
  • low Stub function `trace_id` (body is just `pass`/`return`) — packages/kosong/src/k…
  • low Old/deprecated-named symbol `OpenAILegacy` in packages/kosong/src/kosong/contri…
  • low Old/deprecated-named symbol `OpenaiLegacy` in web/src/lib/api/models/ProviderTy…
  • low Old/deprecated-named symbol `openai_legacy` in src/kimi_cli/config.py:50
  • low Old/deprecated-named symbol `openai_legacy` in src/kimi_cli/llm.py:34
View all legacy markers findings →
Config drift 4 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.
4 matching findings on this repo
  • info Truncated text has no discoverable full-value affordance — web/src/features/cha… web/src/features/chat/global-config-controls.tsx:229
  • low Old/deprecated-named symbol `openai_legacy` in src/kimi_cli/config.py:50
  • high FastAPI PATCH `update_global_config` without auth dependency — src/kimi_cli/web… src/kimi_cli/web/api/config.py:128
  • high FastAPI PUT `update_config_toml` without auth dependency — src/kimi_cli/web/api… src/kimi_cli/web/api/config.py:187
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/6956907c-d7b0-476c-b5d1-09c54f834883/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6956907c-d7b0-476c-b5d1-09c54f834883/

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.