Is Cline safe to use?

Cline has an HVTrust score of 90.9/100 (Grade A), ranked #10 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Cline?

Cline scores 90.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 66.8k GitHub stars and is categorized under Coding Agents.

Cline

cline/cline

Autonomous coding agent as an SDK, IDE extension, or CLI assistant.

Coding Agents TypeScript Grade A Listed Apache-2.0

90.9/100

Rank #10 of 1308

Compare Cline

How does it stack up against its Coding Agents 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 A · 4/5 signals

Last push

2026-08-25 · 0d ago

Recent change

No recent signal change

Is Cline safe? Cline scores 90.9/100 (Grade A), ranked #10 of 1308 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.8/10; 83% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#1 Codex — 93.8 (A) → #2 Qwen Code — 90.9 (A) → #4 ECC — 89.6 (A) → #5 Hermes Agent — 86.1 (A) →

Quick Trust Read

What Would Improve It

Improve safety / integrity to lift the weakest part of the trust profile.

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.8/10. Tighten the weakest checks to improve public safety evidence.

Compare with Codex Get email alerts for Cline View Coding Agents Report missing data

96.8

Activity sub-score · out of 100

In Coding Agents

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 A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

66.8k

Forks

7.2k

Last Push

2026-08-25

today

Commits (4 wk)

466

Downloads (7d)

4,425,910

npm+vscode

HN mentions (30d)

Open Issues

668

Rank Change

was #10

Analysis

HVTrust Dimensions vs Coding Agents

90.9 / 100 · 100.0% confidence

Cline Coding Agents average (70 agents)

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

18.9 / 25

11.3 above avg 7.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.4 above avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

13.4 / 17

2.3 above avg 11.1

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.1 above avg 14.9

AdoptionLog-scaled stars · package downloads

20.0 / 20

7.8 above avg 12.2

Activity Inputs

96.8 / 100

StarsRepository reach

28.9 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

17.9 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.8 / 10

OpenSSF Scorecard · scanned Aug 24, 2026

Signed Commits

83%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 4

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 6

Security-Policy 10

Signed-Releases 2

Token-Permissions 0

Vulnerabilities 0

Is Cline safe?

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

Does Cline publish package provenance?

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

Does Cline have an OpenSSF Scorecard?

Cline has an OpenSSF Scorecard score of 5.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Cline actively maintained?

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

What license does Cline use?

Cline ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Cline's commits signed?

83% of the last 100 commits to Cline 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 Cline head-to-head

Cline vs Codex → Cline vs Qwen Code → Cline vs ECC →

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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 Cline?

For maintainers

HVTrust scores Cline 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-05-29

HVTrust Changed

HVTrust up 10.0pts (78.4 → 88.4)

2026-05-28

Activity Score Changed

Activity score up 25pts (72 → 96)

GitHub → npm: cline

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/cline.svg)](https://hvtracker.net/agents/cline)
            
HTML:
            <a href="https://hvtracker.net/agents/cline"><img src="https://hvtracker.net/badge/cline.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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