Larksuite Cli
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.
Is Larksuite Cli safe? Strong public trust posture, backed by multiple independent signals.
Compare Larksuite Cli
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Larksuite Cli scores 90.4/100 (Grade A), ranked #2 of 351 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.0/10; 100% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →
How Larksuite Cli compares in Agent Skills
- #1 OmniRoute 93.3 +2.9
- #2 Larksuite Cli 90.4 this agent
- #3 Vercel Skills 89.9 −0.5
- #4 Notebooklm Py 88.7 −1.7
- #5 Avoid Ai Writing 88.2 −2.2
Bars show each HVTrust score; the tick marks Larksuite Cli’s 90.4.
Where the 90.4 comes from
HVTrust dimensions vs the Agent Skills average
90.4 / 100 · 100.0% confidenceLarksuite Cli Agent Skills average (351 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
89.2 / 100Supply Chain Trust
Common questions about Larksuite Cli
Does Larksuite Cli publish package provenance?
Does Larksuite Cli have an OpenSSF Scorecard?
Is Larksuite Cli actively maintained?
What license does Larksuite Cli use?
Are Larksuite Cli's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
Compare Larksuite Cli head-to-head
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Larksuite Cli's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Larksuite Cli?
For maintainers
HVTrust scores Larksuite Cli from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/larksuite-cli)
<a href="https://hvtracker.net/agents/larksuite-cli"><img src="https://hvtracker.net/badge/larksuite-cli.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON