- Reliability 8/20
- Evidence shows an active repository with a clear architecture, but static review found no test files or CI configuration, so actual startup and tool-list handshake cannot be verified. The README describes features, but there is no evidence that MCP initialization paths are tested. Deductions: lack of test evidence and error handling details.
- Security and permissions 12/20
- The repository uses an MIT license, and the README clearly discloses sandbox isolation mechanisms (WSL2, Lima) and path restrictions. However, no specific implementation of credential management was found, and remote control features (Feishu/Slack) and GUI operations may increase the attack surface. Deductions: lack of evidence for least privilege principles, and dangerous operations (e.g., file deletion) do not explicitly require confirmation. Red lines not met.
- Maintenance 14/20
- The repository has a clear MIT license, and star count and open issues indicate community activity. However, static review did not find release records, contribution guidelines, or a security response policy. Deductions: lack of evidence for detailed maintenance processes and version control.
- Documentation 13/20
- The README provides installation, configuration, feature overview, and architecture diagrams, but lacks detailed tool parameters, API reference, and troubleshooting guides. Deductions: documentation is incomplete, does not disclose model limitations, cost information, or error handling processes.
- Setup experience 11/20
- Multiple platform installation options are provided (Homebrew, installers, source build), but static review could not verify the reliability of installation scripts. Setup requires multiple manual steps (getting API key, configuring Base URL), and client configuration examples are insufficient. Deductions: installation steps are complex, and detailed examples for client connection are lacking.