# Pitfall Log / 踩坑日志 项目：memtomem/memtomem-stm 摘要：发现 36 个潜在踩坑项，其中 3 个为 high/blocking；最高优先级：安全/权限坑 - 失败模式：security_permissions: ci: supply-chain hardening — dependency audit, Dependabot, action SHA pinning, top-level work...。 ## 1. 安全/权限坑 · 失败模式：security_permissions: ci: supply-chain hardening — dependency audit, Dependabot, action SHA pinning, top-level work... - 严重度：high - 证据强度：source_linked - 发现：Developers should check this security_permissions risk before relying on the project: ci: supply-chain hardening — dependency audit, Dependabot, action SHA pinning, top-level workflow permissions - 对用户的影响：Developers may expose sensitive permissions or credentials: ci: supply-chain hardening — dependency audit, Dependabot, action SHA pinning, top-level workflow permissions - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/609 | ci: supply-chain hardening — dependency audit, Dependabot, action SHA pinning, top-level workflow permissions ## 2. 安全/权限坑 · 失败模式：security_permissions: privacy: disabling privacy_scan_enabled silently sends raw upstream text to external LLM prov... - 严重度：high - 证据强度：source_linked - 发现：Developers should check this security_permissions risk before relying on the project: privacy: disabling privacy_scan_enabled silently sends raw upstream text to external LLM providers — warn loudly; consider entropy heuristic - 对用户的影响：Developers may expose sensitive permissions or credentials: privacy: disabling privacy_scan_enabled silently sends raw upstream text to external LLM providers — warn loudly; consider entropy heuristic - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/610 | privacy: disabling privacy_scan_enabled silently sends raw upstream text to external LLM providers — warn loudly; consider entropy heuristic ## 3. 安全/权限坑 · 失败模式：security_permissions: tests: fill direct-coverage gaps — observability/tracing, mms/secrets, mms/detect, cli/daemon... - 严重度：high - 证据强度：source_linked - 发现：Developers should check this security_permissions risk before relying on the project: tests: fill direct-coverage gaps — observability/tracing, mms/secrets, mms/detect, cli/daemon_cmd, relevance embedding paths - 对用户的影响：Developers may expose sensitive permissions or credentials: tests: fill direct-coverage gaps — observability/tracing, mms/secrets, mms/detect, cli/daemon_cmd, relevance embedding paths - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/619 | tests: fill direct-coverage gaps — observability/tracing, mms/secrets, mms/detect, cli/daemon_cmd, relevance embedding paths ## 4. 安装坑 · 失败模式：installation: proxy: upstream call_tool path has no circuit breaker — SECURITY.md claims per-upstream break... - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this installation risk before relying on the project: proxy: upstream call_tool path has no circuit breaker — SECURITY.md claims per-upstream breaker isolation - 对用户的影响：Developers may fail before the first successful local run: proxy: upstream call_tool path has no circuit breaker — SECURITY.md claims per-upstream breaker isolation - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/608 | proxy: upstream call_tool path has no circuit breaker — SECURITY.md claims per-upstream breaker isolation ## 5. 安装坑 · 失败模式：installation: v0.1.29 - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this installation risk before relying on the project: v0.1.29 - 对用户的影响：Upgrade or migration may change expected behavior: v0.1.29 - 证据：failure_mode_cluster:github_release | https://github.com/memtomem/memtomem-stm/releases/tag/v0.1.29 | v0.1.29 ## 6. 安装坑 · 来源证据：config: unknown keys are silently ignored and parse failures silently fall back — add `mms config validate` and louder… - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：config: unknown keys are silently ignored and parse failures silently fall back — add `mms config validate` and louder failure - 对用户的影响：可能影响升级、迁移或版本选择。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/611 | 来源类型 github_issue 暴露的待验证使用条件。 ## 7. 安装坑 · 来源证据：proxy: ProxyManager.stop() never closes the sqlite pending stores (leaked connection on config-change rebuild) - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：proxy: ProxyManager.stop() never closes the sqlite pending stores (leaked connection on config-change rebuild) - 对用户的影响：可能增加新用户试用和生产接入成本。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/601 | 来源类型 github_issue 暴露的待验证使用条件。 ## 8. 安装坑 · 来源证据：server: stderr-only logging — add optional rotating file log under ~/.memtomem/ - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：server: stderr-only logging — add optional rotating file log under ~/.memtomem/ - 对用户的影响：可能阻塞安装或首次运行。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/612 | 来源类型 github_issue 暴露的待验证使用条件。 ## 9. 配置坑 · 可能修改宿主 AI 配置 - 严重度：medium - 证据强度：source_linked - 发现：项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。 - 对用户的影响：安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。 - 证据：capability.host_targets | https://github.com/memtomem/memtomem-stm | host_targets=claude, mcp_host, claude_code, cursor ## 10. 配置坑 · 失败模式：configuration: Harden non-startup exc_info cleanup logs against credential leaks (follow-up to #580/#593) - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: Harden non-startup exc_info cleanup logs against credential leaks (follow-up to #580/#593) - 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Harden non-startup exc_info cleanup logs against credential leaks (follow-up to #580/#593) - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/605 | Harden non-startup exc_info cleanup logs against credential leaks (follow-up to #580/#593) ## 11. 配置坑 · 失败模式：configuration: cli/docs polish batch: --json coverage, daemon run/start naming, status/list overlap, CHANGEL... - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: cli/docs polish batch: --json coverage, daemon run/start naming, status/list overlap, CHANGELOG upgrade-notes - 对用户的影响：Developers may misconfigure credentials, environment, or host setup: cli/docs polish batch: --json coverage, daemon run/start naming, status/list overlap, CHANGELOG upgrade-notes - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/614 | cli/docs polish batch: --json coverage, daemon run/start naming, status/list overlap, CHANGELOG upgrade-notes ## 12. 配置坑 · 失败模式：configuration: cli: mms tune --apply — apply stm_tuning_recommendations to stm_proxy.json instead of hand-ed... - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: cli: mms tune --apply — apply stm_tuning_recommendations to stm_proxy.json instead of hand-editing - 对用户的影响：Developers may misconfigure credentials, environment, or host setup: cli: mms tune --apply — apply stm_tuning_recommendations to stm_proxy.json instead of hand-editing - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/615 | cli: mms tune --apply — apply stm_tuning_recommendations to stm_proxy.json instead of hand-editing ## 13. 配置坑 · 失败模式：configuration: config: unknown keys are silently ignored and parse failures silently fall back — add `mms co... - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: config: unknown keys are silently ignored and parse failures silently fall back — add `mms config validate` and louder failure - 对用户的影响：Developers may misconfigure credentials, environment, or host setup: config: unknown keys are silently ignored and parse failures silently fall back — add `mms config validate` and louder failure - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/611 | config: unknown keys are silently ignored and parse failures silently fall back — add `mms config validate` and louder failure ## 14. 配置坑 · 失败模式：configuration: decide: wire an index engine into the bundled mms server, or retire the inert auto_index/extr... - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: decide: wire an index engine into the bundled mms server, or retire the inert auto_index/extraction config surface (follow-up to #288) - 对用户的影响：Developers may misconfigure credentials, environment, or host setup: decide: wire an index engine into the bundled mms server, or retire the inert auto_index/extraction config surface (follow-up to #288) - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/616 | decide: wire an index engine into the bundled mms server, or retire the inert auto_index/extraction config surface (follow-up to #288) ## 15. 配置坑 · 失败模式：configuration: proxy: ProxyManager.stop() never closes the sqlite pending stores (leaked connection on confi... - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: proxy: ProxyManager.stop() never closes the sqlite pending stores (leaked connection on config-change rebuild) - 对用户的影响：Developers may misconfigure credentials, environment, or host setup: proxy: ProxyManager.stop() never closes the sqlite pending stores (leaked connection on config-change rebuild) - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/601 | proxy: ProxyManager.stop() never closes the sqlite pending stores (leaked connection on config-change rebuild) ## 16. 配置坑 · 失败模式：configuration: server: stderr-only logging — add optional rotating file log under ~/.memtomem/ - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: server: stderr-only logging — add optional rotating file log under ~/.memtomem/ - 对用户的影响：Developers may misconfigure credentials, environment, or host setup: server: stderr-only logging — add optional rotating file log under ~/.memtomem/ - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/612 | server: stderr-only logging — add optional rotating file log under ~/.memtomem/ ## 17. 配置坑 · 失败模式：configuration: types: mypy burn-down — 9 errors in 4 files, then re-enable the attr-defined suppression - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: types: mypy burn-down — 9 errors in 4 files, then re-enable the attr-defined suppression - 对用户的影响：Developers may misconfigure credentials, environment, or host setup: types: mypy burn-down — 9 errors in 4 files, then re-enable the attr-defined suppression - 证据：failure_mode_cluster:github_issue | https://github.com/memtomem/memtomem-stm/issues/617 | types: mypy burn-down — 9 errors in 4 files, then re-enable the attr-defined suppression ## 18. 配置坑 · 失败模式：configuration: v0.1.27 - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: v0.1.27 - 对用户的影响：Upgrade or migration may change expected behavior: v0.1.27 - 证据：failure_mode_cluster:github_release | https://github.com/memtomem/memtomem-stm/releases/tag/v0.1.27 | v0.1.27 ## 19. 配置坑 · 失败模式：configuration: v0.1.30 - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: v0.1.30 - 对用户的影响：Upgrade or migration may change expected behavior: v0.1.30 - 证据：failure_mode_cluster:github_release | https://github.com/memtomem/memtomem-stm/releases/tag/v0.1.30 | v0.1.30 ## 20. 配置坑 · 失败模式：configuration: v0.1.31 - 严重度：medium - 证据强度：source_linked - 发现：Developers should check this configuration risk before relying on the project: v0.1.31 - 对用户的影响：Upgrade or migration may change expected behavior: v0.1.31 - 证据：failure_mode_cluster:github_release | https://github.com/memtomem/memtomem-stm/releases/tag/v0.1.31 | v0.1.31 ## 21. 配置坑 · 来源证据：cli/docs polish batch: --json coverage, daemon run/start naming, status/list overlap, CHANGELOG upgrade-notes - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：cli/docs polish batch: --json coverage, daemon run/start naming, status/list overlap, CHANGELOG upgrade-notes - 对用户的影响：可能影响升级、迁移或版本选择。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/614 | 来源类型 github_issue 暴露的待验证使用条件。 ## 22. 配置坑 · 来源证据：cli: mms tune --apply — apply stm_tuning_recommendations to stm_proxy.json instead of hand-editing - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：cli: mms tune --apply — apply stm_tuning_recommendations to stm_proxy.json instead of hand-editing - 对用户的影响：可能增加新用户试用和生产接入成本。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/615 | 来源类型 github_issue 暴露的待验证使用条件。 ## 23. 配置坑 · 来源证据：decide: wire an index engine into the bundled mms server, or retire the inert auto_index/extraction config surface (fol… - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：decide: wire an index engine into the bundled mms server, or retire the inert auto_index/extraction config surface (follow-up to #288) - 对用户的影响：可能增加新用户试用和生产接入成本。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/616 | 来源类型 github_issue 暴露的待验证使用条件。 ## 24. 配置坑 · 来源证据：tests: fill direct-coverage gaps — observability/tracing, mms/secrets, mms/detect, cli/daemon_cmd, relevance embedding… - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：tests: fill direct-coverage gaps — observability/tracing, mms/secrets, mms/detect, cli/daemon_cmd, relevance embedding paths - 对用户的影响：可能增加新用户试用和生产接入成本。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/619 | 来源类型 github_issue 暴露的待验证使用条件。 ## 25. 配置坑 · 来源证据：types: mypy burn-down — 9 errors in 4 files, then re-enable the attr-defined suppression - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：types: mypy burn-down — 9 errors in 4 files, then re-enable the attr-defined suppression - 对用户的影响：可能增加新用户试用和生产接入成本。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/617 | 来源类型 github_issue 暴露的待验证使用条件。 ## 26. 能力坑 · 能力判断依赖假设 - 严重度：medium - 证据强度：source_linked - 发现：README/documentation is current enough for a first validation pass. - 对用户的影响：假设不成立时，用户拿不到承诺的能力。 - 证据：capability.assumptions | https://github.com/memtomem/memtomem-stm | README/documentation is current enough for a first validation pass. ## 27. 运行坑 · 来源证据：proxy/relevance: embedding providers use synchronous httpx.post — blocks the event loop for up to the full timeout - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：proxy/relevance: embedding providers use synchronous httpx.post — blocks the event loop for up to the full timeout - 对用户的影响：可能增加新用户试用和生产接入成本。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/618 | 来源类型 github_issue 暴露的待验证使用条件。 ## 28. 维护坑 · 维护活跃度未知 - 严重度：medium - 证据强度：source_linked - 发现：未记录 last_activity_observed。 - 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。 - 证据：evidence.maintainer_signals | https://github.com/memtomem/memtomem-stm | last_activity_observed missing - 严重度：medium - 证据强度：source_linked - 发现：no_demo - 证据：downstream_validation.risk_items | https://github.com/memtomem/memtomem-stm | no_demo; severity=medium ## 30. 安全/权限坑 · 存在评分风险 - 严重度：medium - 证据强度：source_linked - 发现：no_demo - 对用户的影响：风险会影响是否适合普通用户安装。 - 证据：risks.scoring_risks | https://github.com/memtomem/memtomem-stm | no_demo; severity=medium ## 31. 安全/权限坑 · 来源证据：Harden non-startup exc_info cleanup logs against credential leaks (follow-up to #580/#593) - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Harden non-startup exc_info cleanup logs against credential leaks (follow-up to #580/#593) - 对用户的影响：可能影响授权、密钥配置或安全边界。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/605 | 来源类型 github_issue 暴露的待验证使用条件。 ## 32. 安全/权限坑 · 来源证据：ci: supply-chain hardening — dependency audit, Dependabot, action SHA pinning, top-level workflow permissions - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：ci: supply-chain hardening — dependency audit, Dependabot, action SHA pinning, top-level workflow permissions - 对用户的影响：可能影响授权、密钥配置或安全边界。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/609 | 来源类型 github_issue 暴露的待验证使用条件。 ## 33. 安全/权限坑 · 来源证据：privacy: disabling privacy_scan_enabled silently sends raw upstream text to external LLM providers — warn loudly; consi… - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：privacy: disabling privacy_scan_enabled silently sends raw upstream text to external LLM providers — warn loudly; consider entropy heuristic - 对用户的影响：可能影响授权、密钥配置或安全边界。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/610 | 来源类型 github_issue 暴露的待验证使用条件。 ## 34. 安全/权限坑 · 来源证据：proxy: upstream call_tool path has no circuit breaker — SECURITY.md claims per-upstream breaker isolation - 严重度：medium - 证据强度：source_linked - 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：proxy: upstream call_tool path has no circuit breaker — SECURITY.md claims per-upstream breaker isolation - 对用户的影响：可能增加新用户试用和生产接入成本。 - 证据：community_evidence:github | https://github.com/memtomem/memtomem-stm/issues/608 | 来源类型 github_issue 暴露的待验证使用条件。 ## 35. 维护坑 · issue/PR 响应质量未知 - 严重度：low - 证据强度：source_linked - 发现：issue_or_pr_quality=unknown。 - 对用户的影响：用户无法判断遇到问题后是否有人维护。 - 证据：evidence.maintainer_signals | https://github.com/memtomem/memtomem-stm | issue_or_pr_quality=unknown ## 36. 维护坑 · 发布节奏不明确 - 严重度：low - 证据强度：source_linked - 发现：release_recency=unknown。 - 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。 - 证据：evidence.maintainer_signals | https://github.com/memtomem/memtomem-stm | release_recency=unknown