- Reliability 5/20
- No server manifest was cached, and the README shows Kode is fundamentally a terminal coding-agent CLI that acts as an MCP *client* connecting out to external MCP servers (`kode mcp add/list/remove`), not an MCP server implementation itself — so no MCP init/tool-list handshake can be verified at all. The README mentions `bun test` and GitHub Releases, but no CI workflow files or committed tests are shown as evidence within the reviewed material, which is weak under a static review. Per the static calibration rule, reliability is capped at 12 without verifiable execution evidence, and given the category mismatch (client vs. server) plus thin evidence, it is scored 5.
- Security and permissions 3/20
- The README explicitly states Kode 'runs in YOLO mode by default for maximum productivity,' meaning permission prompts for file writes and shell command execution are skipped unless the user explicitly opts into `kode --safe` or sets `KODE_SYSTEM_SANDBOX=1` to enable the bwrap sandbox and checks; even then, network access in the sandbox is only disabled by default within that opt-in mode. This means an autonomous agent capable of Bash execution and file writes can, by default, take irreversible local actions without user confirmation — matching the rubric's red-line pattern for unconfirmed destructive/command defaults. The project does disclose no default telemetry and scoped network use, and offers a `--safe` flag, showing some risk awareness, but the unsafe default itself remains an unmitigated, disclosed red-line risk, warranting a score of 3 (0-4 band).
- Maintenance 11/20
- The project carries an Apache-2.0 license, ships via npm with a GitHub Releases page, and references a CONTRIBUTING.md, indicating some governance. However, '0 open issues' on a 5201-star repo is unusual and suggests issue tracking may be disabled or cleared, reducing transparency, and no explicit security-response channel is described. The README's own note that the project is 'undergoing a major maintenance and refactoring phase' from July–December 2026 signals active investment but also an unstable transition period that could affect near-term reliability. Overall scored 11.
- Documentation 13/20
- The README is well organized, covering installation, quick start, multi-model orchestration, agents/subagents, skills/plugins, MCP extensions, permissions/security, configuration, Docker, and development workflow, with concrete file paths and command examples. However, detailed tool/parameter documentation (full MCP server config fields, per-tool permission granularity) is deferred to an external docs/ directory not shown in the reviewed text, and there is little concrete discussion of cost or troubleshooting beyond mentioning a `/cost` command. Usable but with hidden assumptions and documentation gaps — scored 13.
- Setup experience 12/20
- Installation is clearly documented (`npm install -g @shareai-lab/kode`), with alternatives including a China mirror, a dev channel, standalone Bun-compiled binaries, and Docker, covering mainstream platforms. However, since this object is itself an MCP client rather than an MCP server exposed to clients, there is no direct 'connect to this server from a mainstream MCP client' configuration example. The README also notes a dependency on platform-specific `ripgrep` native binaries via optionalDependencies, requiring manual `KODE_RIPGREP_PATH` setup if installed with `--no-optional`, adding fragility. Per the static calibration rule, setup is capped at 15 absent verifiable execution evidence, so it is scored 12.