Claude Mem vs Larksuite Cli
Both are Grade A and 0.9 points apart, so choose on what you weigh most. Claude Mem leads on maintenance and adoption; Larksuite Cli leads on supply-chain integrity and transparency.
Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Choose Claude Mem if maintenance and adoption matter most.
- +2.6Maintenance
- +0.8Adoption: 115.5k GitHub stars against 18k
The official Lark/飞书 CLI tool, maintained by the larksuite team — built for humans and AI Agents. Covers core business domains including Messenger, Docs, Base, Sheets, Calendar, Mail, Tasks, Meetings, and more, with 200+ commands and 20+ AI Agent Skills.
Choose Larksuite Cli if supply-chain integrity and transparency matter most.
- +2.3Safety / Integrity: 100% of recent commits signed, against 91%
- +1.3Transparency: OSSF Scorecard 6.1 against 4.6
Where they differ
1 dimension identical: Identity 18.0 · Full evidence table
An independent, evidence-based trust comparison of Claude Mem and Larksuite Cli, two Agent Skills projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Full evidence
| Signal | Claude Memthedotmack/claude-mem | Larksuite Clilarksuite/cli |
|---|---|---|
| HVTrust score | 90.2 | 89.3 |
| Evidence grade | A | A |
| Coverage grade | B | B |
| Overall rank | #4 | #5 |
| Rank in Agent Skills | #4 | #5 |
| GitHub stars | 115.5k | 18.0k |
| Last updated | today | today |
| Build provenance | Yes | Yes |
| OSSF Scorecard | 4.6 / 10 | 6.1 / 10 |
| License | Apache-2.0 | MIT |
| Downloads | 36k/wk | 229k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 17.8 | 20.1 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 12.4 | 13.7 |
| Maintenance / 20 | 20.0 | 17.4 |
| Adoption / 20 | 18.2 | 17.4 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | — |
| External providers | 1 — Anthropic | — |
| Requires API keys | No | No |
| Plugin surface | plugins | — |
| Provenance drift | Match | Match |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →