Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want a more stateful coding-agent terminal than a plain chat loop, but the backend dependency on Kimchi's model infrastructure and the broad tool surface mean it should be evaluated like real developer infrastructure rather than a toy wrapper.
Who should use it
Who should skip it
Avoid running getkimchi/kimchi in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
getkimchi/kimchi is tracked by RepoRadar as a tool in the AI Coding section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, getkimchi/kimchi is strongest on workflow potential (9.5) and maturity (9.1) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned getkimchi/kimchi a composite score of 8.4 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 2005.0 and never affects the composite score or tier. The risk label of 'medium' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
kimchi depends on Kimchi-managed model infrastructure or external provider keys, so teams should review where prompts, code context, and shell output are being routed before production use; The setup path can import MCP server definitions from existing Claude Code, OpenCode, or Cursor installs, so the migration diff should be reviewed before letting it rewrite a working local tool stack; Remote teleport and broad shell-tool execution make this a powerful developer surface, so it should start in a disposable repo before being trusted on sensitive codebases.