Best Open-Source Agent Skills: Larksuite Cli vs Cc Safety Net
A data-backed comparison of the top two agent skills on HVTracker, built from public trust signals rather than stars alone.
Short answer: Larksuite Cli currently leads Cc Safety Net on HVTracker's evidence-weighted trust score: 80.0 vs 74.5/100. This is not a popularity ranking; it combines supply-chain safety, identity/provenance, transparency, maintenance, and adoption signals.
Larksuite Cli
The official Lark/飞书 CLI tool, maintained by the larksuite team — built for humans and AI Agents. Covers core business d
Cc Safety Net
An AI coding agent guardrail — a CLI hook that blocks destructive git and filesystem commands and secret file access bef
Larksuite Cli vs Cc Safety Net: trust signal breakdown
Both projects are tracked in the Agent Skills category, but they do not expose the same evidence. The table below compares the public signals that feed HVTrust.
| Signal | Larksuite Cli | Cc Safety Net |
|---|---|---|
| HVTrust score | 80.0 | 74.5 |
| Safety / Integrity | 12.5/25 | 12.3/25 |
| Identity / Provenance | 18.0/18 | 18.0/18 |
| Transparency | 8.5/17 | 8.5/17 |
| Maintenance | 20.0/20 | 20.0/20 |
| Adoption | 17.0/20 | 12.0/20 |
| OSSF Scorecard | Unavailable | Unavailable |
| Signed commits | 100% | 97% |
| Package provenance | Verified | Verified |
Which one should you evaluate first?
If your priority is the most verifiable trust profile today, start with Larksuite Cli. It has the stronger current HVTrust score and ranks higher in Agent Skills. If your use case depends on a specific runtime, language, license, or integration model, use the individual profiles rather than the headline score alone.
For production use, the practical checklist is: inspect the security policy, confirm package provenance or release signing where available, review recent maintenance cadence, and compare the exact trust breakdown. HVTracker is meant to reduce the first-pass research burden, not replace your own risk review.