- Reliability 10/20
- The README claims a CI badge, an 83% coverage badge, Python 3.10+, six MCP tools (rlm_projects/rlm_index/rlm_start/rlm_help/rlm_execute/rlm_end) and 62 sandbox helpers, and states pre-release testing on real ERP/EDT/CF codebases. These are self-reported claims: no CI workflow files, no committed tests, and no server manifest (SERVER MANIFEST shows [not cached]) are available for static verification, so declared tools cannot be checked against real behavior. The happy path is plausible but error handling and edge cases are undocumented. Per the static calibration rule, reliability is capped at 12; uncertainty lowers the score, giving 10.
- Security and permissions 9/20
- The README shows positive intent: project registration requires a password, index mutation (build/update/drop) and registry mutations require a password parameter for confirmation, the CLI skips the password, and a sandbox with timeouts is mentioned. However several risks are not fully disclosed: rlm_execute runs Python scripts on the host where the project is open, which is a high-privilege capability whose sandbox isolation, resource limits, and network restrictions are not described; install scripts use irm/curl to download and execute remote scripts, a remote-code-execution path; and optional LLM endpoints (OpenRouter/Ollama/Anthropic) send data externally with incomplete data-flow disclosure. No malware, credential theft, hardcoded secrets, or irreversible default actions were found, and drop requires a password, so this is not a red-line 0-4. Deductions: privilege boundaries and confirmation for script execution are under-specified, and external network data flow is not fully disclosed.
- Maintenance 12/20
- Evidence of active maintenance exists: MIT license, PyPI releases (badge), CHANGELOG.md, CI workflow badge, coverage badge, 193 stars, 2 open issues, not archived, README states pre-release testing on multiple real 1C codebases, and a cited April 2026 comparison test. But deeper evidence is missing: no visible issue-response record, dependency-update policy, security-response channel, or governance/release-cadence details, and ownership appears to be a single author (Dach-Coin). Medium score: active with a clear license, but governance/versioning/security-response gaps.
- Documentation 16/20
- Documentation is layered and extensive: README covers installation (one-line Windows PowerShell, one-line Linux systemd, Docker, source), client config examples (.claude.json / mcp.json, type http and stdio), tool and helper listings with links, environment-variable reference, FAQ, QUICKSTART, INDEXING, ARCHITECTURE, PROJECT_REGISTRY, AGENT_INSTRUCTIONS, LLM_QUERY, ENV_REFERENCE, TELEMETRY, plus disclosed boundaries (when not to use it, RLM vs RAG), performance limits (pre-indexing needed on HDD/network drives, full strategy for weak models), and cost figures (25-95% token savings). Deductions: key mechanisms (sandbox isolation, exact timeout values, password/security model) are only summarized in the README rather than shown in reviewable config files; the unavailable SERVER MANIFEST prevents verifying tool parameters; and the marketing-style comparison table (10/10) relies on an external repo and cannot be independently verified. Usable but with hidden assumptions and troubleshooting gaps, hence 16.
- Setup experience 13/20
- The install path is clear and short with multiple mainstream options: a one-line Windows PowerShell script (installs the pip package, registers the service, starts it, and checks health), a one-line Linux script, Docker Compose (example file provided), and source install, with client config JSON examples for Claude Code/Cursor/Kilo/Roo and a default HTTP endpoint of http://127.0.0.1:9000/mcp. Deductions: the one-line installers download and execute remote scripts, which cannot be verified without execution; Windows + Docker is explicitly discouraged without a quantified fallback; the Docker path requires manually editing REPOS_ROOT and other env vars; and there is no verifiable minimal example for an environment without 1C sources. Per the calibration rule, setup cannot exceed 15 without verifiable execution evidence, so 13.