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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 45 days ago
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
20.9k
Forks
3.0k
Last Push
2026-04-20
45 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
516
Rank Change
▼10
was #127
Analysis
HVTrust Dimensions
54.8 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.6 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.0 / 17
MaintenanceFreshness and commits
9.0 / 20
AdoptionStars and downloads
10.4 / 20
Activity Inputs
60.9 / 100
StarsRepository reach
25.9 / 30
FreshnessLast push recency
18.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
16.2 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.3 / 10
via deps.dev · OpenSSF
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
Maintained5
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 5.3/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 45 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
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) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
