updated 2026-08-12 05:02 UTC

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 Grade C Listed AGPL-3.0
64.5/100
Rank #240 of 1283
Compare Cherry Studio

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-12 · 0d ago
Recent change
Rank +1

Is Cherry Studio safe? Cherry Studio scores 64.5/100 (Grade C), ranked #240 of 1283 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 4.6/10; 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 UI & App Builders

#4 Open WebUI — 83.3 (A) → #5 LibreChat — 74.7 (B) → #7 Odysseus — 64.4 (C) → #8 ToolJet — 61.8 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/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.3
Activity sub-score · out of 100
#6
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 C 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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
50.3k
Forks
4.8k
Last Push
2026-08-12
today
Commits (4 wk)
735
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
867
Rank Change
=
was #240

Analysis

HVTrust Dimensions vs UI & App Builders

64.5 / 100 · 100.0% confidence

Cherry Studio UI & App Builders average (17 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.8 / 25
0.7 above avg 10.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.7 below avg 12.5
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
0.5 above avg 11.9
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.0 above avg 16.0
AdoptionLog-scaled stars · package downloads
11.3 / 20
1.1 below avg 12.4

Activity Inputs

95.3 / 100
StarsRepository reach
28.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Aug 11, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests 10
CII-Best-Practices 0
Code-Review 10
Contributors 10
Dangerous-Workflow 0
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 0

Is Cherry Studio safe?

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 4.6/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 Tambo →

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
Rank 4Listed 1
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)
2026-06-24
Newly Listed
First tracked at rank #132
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.5 Grade C
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