Is Larksuite Cli safe to use?

Larksuite Cli has an HVTrust score of 80.0/100 (Grade A), ranked #1 of 148 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Larksuite Cli?

Larksuite Cli scores 80.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 16.4k GitHub stars and is categorized under Agent Skills.

Larksuite Cli

larksuite/cli

The official Lark/飞书 CLI tool, maintained by the larksuite team — built for humans and AI Agents. Covers core business d

Agent Skills Go Grade A Listed MIT

80.0/100

Rank #1 of 148

Compare Larksuite Cli

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-12 · 0d ago

Recent change

New

Is Larksuite Cli safe? Larksuite Cli scores 80.0/100 (Grade A), ranked #1 of 148 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; no OSSF Scorecard result yet; 100% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#2 Cc Safety Net — 74.5 (B) → #3 Better Harness — 70.6 (B) → #4 Waza — 68.9 (B) → #5 Dev Browser — 65.3 (B) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-11

Newly Listed

First tracked at rank #1

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Compare with Cc Safety Net Get email alerts for Larksuite Cli View Agent Skills Report missing data

89.8

Activity sub-score · out of 100

In Agent Skills

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

2026-08-11 2026-08-12

Activity & Reach

Stars

16.4k

Forks

1.3k

Last Push

2026-08-12

today

Commits (4 wk)

248

Downloads (7d)

157,019

npm

HN mentions (30d)

—

Open Issues

186

Rank Change

was #1

Analysis

HVTrust Dimensions vs Agent Skills

80.0 / 100 · 100.0% confidence

Larksuite Cli Agent Skills average (148 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

12.5 / 25

9.8 above avg 2.7

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.7 above avg 11.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.5

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

4.9 above avg 15.1

AdoptionLog-scaled stars · package downloads

17.0 / 20

7.8 above avg 9.2

Activity Inputs

89.8 / 100

StarsRepository reach

25.3 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.5 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

—

Not available

Signed Commits

100%

of last 100 commits verified

Is Larksuite Cli safe?

Public supply-chain signals for Larksuite Cli are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Larksuite Cli carries less obvious unverified-evidence risk than projects with thin signals.

Does Larksuite Cli publish package provenance?

Yes. Larksuite Cli's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Larksuite Cli have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Larksuite Cli. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Larksuite Cli actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Larksuite Cli use?

Larksuite Cli ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Larksuite Cli's commits signed?

100% of the last 100 commits to Larksuite Cli are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Larksuite Cli vs Cc Safety Net → Larksuite Cli vs Better Harness → Larksuite Cli vs Waza →

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

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 Server Support

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-11

Newly Listed

First tracked at rank #1

GitHub → npm: @larksuite/cli

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/larksuite-cli.svg)](https://hvtracker.net/agents/larksuite-cli)
            
HTML:
            <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

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON