Is Coze Studio safe?
Coze Studio scores 50.6/100 (Grade C), ranked #231 of 328 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-04-20. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
50.6/100 · Grade C
Strongest Signal
Transparency
12.7/17
Weakest Signal
Maintenance
6.5/20
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 4.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Refresh maintenance signalsThe repo was last pushed 82 days ago. Fresh activity helps separate stable projects from stale ones.
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 refreshed2026-07-11 05:00 UTC·Repo last pushed 82 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
21.1k
Forks
3.1k
Last Push
2026-04-20
82 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
482
Rank Change
▼1
was #230
Analysis
HVTrust Dimensions
50.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.1 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.7 / 17
MaintenanceFreshness and commits
6.5 / 20
AdoptionStars and downloads
10.4 / 20
Activity Inputs
56.0 / 100
StarsRepository reach
26.0 / 30
FreshnessLast push recency
13.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
16.2 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.9 / 10
OpenSSF Scorecard · scanned Jul 11, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests9
CII-Best-Practices0
Code-Review10
Contributors3
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies1
SAST7
Security-Policy0
Signed-Releases-1
Token-Permissions9
Vulnerabilities0
Is Coze Studio safe?
Public trust evidence for Coze Studio is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
Slowing down. Last push was 82 days ago — keep an eye on whether activity resumes.
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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
search
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.
Runtime surface grew — new detected provider dependency: OpenAI
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → declared
Maintain Coze Studio?
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.
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
