Is Coze Studio safe to use?

Coze Studio has an HVTrust score of 56.5/100 (Grade C), ranked #371 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Coze Studio?

Coze Studio scores 56.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 21.4k GitHub stars and is categorized under Workflow Platforms.

Coze Studio

coze-dev/coze-studio

An AI agent development platform with all-in-one visual tools, simplifying agent creation, debugging, and deployment lik

Workflow Platforms TypeScript Grade C Listed Apache-2.0

56.5/100

Rank #371 of 1204

Compare Coze Studio

How does it stack up against its Workflow Platforms 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-07-29 · 11d ago

Recent change

Rank +2

Is Coze Studio safe? Coze Studio scores 56.5/100 (Grade C), ranked #371 of 1204 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.9/10; 100% of recent commits are signed; last pushed 2026-07-29. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

#15 Xpert AI — 57.1 (C) → #16 Julep — 56.7 (C) → #18 Golem — 56.5 (C) → #19 Astron Agent — 55.9 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-08

Rank Moved

Rank dropped 90 spots (#279 → #369)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → marketplace

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: OpenAI

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.9/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 another agent Get email alerts for Coze Studio View Workflow Platforms Report missing data

69.5

Activity sub-score · out of 100

#17

In Workflow Platforms

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 →

Activity & Reach

Stars

21.4k

Forks

3.1k

Last Push

2026-07-29

11 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

486

Rank Change

▼2

was #369

Analysis

HVTrust Dimensions vs Workflow Platforms

56.5 / 100 · 100.0% confidence

Coze Studio Workflow Platforms average (24 agents)

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

11.1 / 25

0.8 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

12.7 / 17

in line with avg 12.4

Maintenance60% last-push freshness · 40% commit activity

12.5 / 20

5.7 below avg 18.2

AdoptionLog-scaled stars · package downloads

10.4 / 20

2.4 below avg 12.8

Activity Inputs

69.5 / 100

StarsRepository reach

26.0 / 30

FreshnessLast push recency

23.5 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

16.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.9 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 9

CII-Best-Practices 0

Code-Review 10

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 1

SAST 7

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0

Is Coze Studio safe?

Coze 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 Coze Studio publish package provenance?

No published build provenance is currently detected for Coze 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 Coze Studio have an OpenSSF Scorecard?

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

Maintained. Last push was 11 days ago.

What license does Coze Studio use?

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

Are Coze Studio's commits signed?

100% of the last 100 commits to Coze 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.

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

None detected

No clear third-party provider dependency detected.

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

Tool / Plugin Surface

high confidence

Marketplace

Marketplace 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

How this surface has changed

Detected changes to Coze Studio's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → marketplace

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: OpenAI

2026-07-29

Activity Resumed

Activity resumed

2026-07-19

Activity Went Stale

No commits for 90 days

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain Coze Studio?

For maintainers

HVTrust scores Coze 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-08-08

Rank Moved

Rank dropped 90 spots (#279 → #369)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → marketplace

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: OpenAI

2026-07-29

Activity Resumed

Activity resumed

2026-07-29

Grade Changed

Trust grade D → C

2026-07-29

Rank Moved

Rank rose 54 spots (#309 → #255)

2026-07-29

HVTrust Changed

HVTrust up 7.8pts (49.5 → 57.3)

2026-07-29

Activity Score Changed

Activity score up 18pts (53 → 71)

2026-07-21

Grade Changed

Trust grade C → D

2026-07-19

Activity Went Stale

No commits for 90 days

2026-07-15

Rank Moved

Rank dropped 22 spots (#275 → #297)

2026-07-14

Rank Moved

Rank dropped 14 spots (#261 → #275)

2026-07-13

Rank Moved

Rank dropped 31 spots (#230 → #261)

2026-06-24

Rank Moved

Rank dropped 27 spots (#192 → #219)

2026-06-23

Rank Moved

Rank dropped 13 spots (#179 → #192)

2026-06-18

Rank Moved

Rank dropped 13 spots (#144 → #157)

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-06-01

Rank Moved

Rank dropped 15 spots (#104 → #119)

2026-05-29

HVTrust Changed

HVTrust up 9.9pts (46.0 → 55.9)

2026-05-27

Scorecard Added

OSSF Scorecard: 5.3/10

2026-05-27

HVTrust Changed

HVTrust up 11.6pts (28.4 → 40.0)

2026-05-25

Rank Moved

Rank dropped 34 spots (#61 → #95)

2026-05-24

Newly Listed

First tracked at rank #61

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Workflow Platforms

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.2 · Raw JSON