Is Cherry Studio safe to use?

Cherry Studio has an HVTrust score of 67.9/100 (Grade B), ranked #379 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Cherry Studio?

Cherry Studio scores 67.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 52.2k GitHub stars and is categorized under UI & App Builders.

Cherry Studio

CherryHQ/cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs

UI & App Builders TypeScript Listed AGPL-3.0

Is Cherry Studio safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.2 / 10

Provenance None

Signed commits 100%

Last push today

Compare Cherry Studio

How does it stack up against its UI & App Builders neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Cherry Studio scores 67.9/100 (Grade B), ranked #379 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.2/10; 100% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cherry Studio compares in UI & App Builders

Bars show each HVTrust score; the tick marks Cherry Studio’s 67.9.

Where the 67.9 comes from

HVTrust dimensions vs the UI & App Builders average

67.9 / 100 · 100.0% confidence

Cherry Studio UI & App Builders average (17 agents)

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

12.8 / 25

1.2 above avg 11.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.1 below avg 12.9

Transparency50% declared license · 50% OSSF Scorecard

13.8 / 17

1.4 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.0 above avg 15.0

AdoptionLog-scaled stars · package downloads

11.3 / 20

1.2 below avg 12.5

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Rank Moved

Rank dropped 237 spots (#141 → #378)

2026-09-21

Rank Moved

Rank rose 228 spots (#369 → #141)

2026-09-13

Rank Moved

Rank rose 47 spots (#413 → #366)

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with Neo Get email alerts for Cherry Studio View UI & App Builders Report missing data

95.5

Activity sub-score · out of 100

In UI & App Builders

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

52.2k

Forks

5.0k

Last Push

2026-09-26

today

Commits (4 wk)

608

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

1103

Rank Change

▲3

was #382

Analysis

Activity Inputs

95.5 / 100

StarsRepository reach

28.3 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

17.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.2 / 10

OpenSSF Scorecard · scanned Sep 15, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 8

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Common questions about Cherry Studio

Cherry Studio has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Cherry Studio publish package provenance?

No published build provenance is currently detected for Cherry Studio. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Cherry Studio have an OpenSSF Scorecard?

Cherry Studio has an OpenSSF Scorecard score of 6.2/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 Cherry Studio actively maintained?

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

What license does Cherry Studio use?

Cherry Studio ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Cherry Studio's commits signed?

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

Cherry Studio vs Neo → Cherry Studio vs OpenUI → Cherry Studio vs Open WebUI →

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

high confidence

Implemented

Cherry Studio appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

6 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

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

Maintain Cherry Studio?

For maintainers

HVTrust scores Cherry Studio 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-09-23

Rank Moved

Rank dropped 237 spots (#141 → #378)

2026-09-21

Rank Moved

Rank rose 228 spots (#369 → #141)

2026-09-13

Rank Moved

Rank rose 47 spots (#413 → #366)

2026-09-11

Rank Moved

Rank dropped 13 spots (#397 → #410)

2026-09-08

Rank Moved

Rank dropped 16 spots (#378 → #394)

2026-09-07

Rank Moved

Rank dropped 22 spots (#356 → #378)

2026-09-05

Rank Moved

Rank dropped 64 spots (#284 → #348)

2026-09-03

Rank Moved

Rank dropped 13 spots (#263 → #276)

2026-08-31

Grade Changed

Trust grade C → B

2026-08-31

Rank Moved

Rank rose 19 spots (#275 → #256)

2026-08-29

Rank Moved

Rank dropped 11 spots (#270 → #281)

2026-08-26

Rank Moved

Rank dropped 21 spots (#243 → #264)

2026-08-24

Rank Moved

Rank dropped 14 spots (#232 → #246)

2026-08-22

Rank Moved

Rank rose 12 spots (#245 → #233)

2026-08-17

Rank Moved

Rank rose 11 spots (#248 → #237)

2026-08-13

Rank Moved

Rank dropped 14 spots (#233 → #247)

2026-08-10

Rank Moved

Rank dropped 15 spots (#224 → #239)

2026-08-08

Rank Moved

Rank dropped 43 spots (#179 → #222)

2026-07-14

Rank Moved

Rank dropped 10 spots (#152 → #162)

2026-07-13

Rank Moved

Rank dropped 18 spots (#134 → #152)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in UI & App Builders

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