Is ZCode safe to use?

ZCode has an HVTrust score of 19.6/100 (Grade D), ranked #1340 of 1343 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for ZCode?

ZCode scores 19.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 7.2k GitHub stars and is categorized under Coding Agents.

ZCode

Repository

Website

Z.ai's coding agent harness. Powerful, intelligent, extensible.

Coding Agents TypeScript Listed Apache-2.0

Is ZCode safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result

Provenance None

Signed commits 0%

Last push today

Compare ZCode

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Suggest a correction

In detail: ZCode scores 19.6/100 (Grade D), ranked #1340 of 1343 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How ZCode could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +39.7 → 59.3 C · #39 of 75
Sign every commit0% signed today +2.5 → 22.1 D · #74 of 75

Already done? Suggest a correction Add the trust badge

How ZCode compares in Coding Agents

Bars show each HVTrust score; the tick marks ZCode’s 19.6.

Where the 19.6 comes from

HVTrust dimensions vs the Coding Agents average

19.6 / 100 · 50.0% confidence

ZCode Coding Agents average (75 agents)

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

0 / 25

9.0 below avg 9.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.0 below avg 11.8

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.2 below avg 11.7

Maintenance60% last-push freshness · 40% commit activity

13.2 / 20

1.7 below avg 14.9

AdoptionLog-scaled stars · package downloads

9.3 / 20

2.9 below avg 12.2

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-09-29

Newly Listed

First tracked at rank #1340

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for ZCode View Coding Agents Report missing data

71.1

Activity sub-score · out of 100

#75

In Coding Agents

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

Activity & Reach

Stars

7.2k

Forks

2.2k

Last Push

2026-09-29

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

NEW

Analysis

Activity Inputs

71.1 / 100

StarsRepository reach

23.1 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

7.5 / 25

CommunityFork signal

15.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

of last 100 commits verified

Common questions about ZCode

Public trust evidence for ZCode 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 ZCode publish package provenance?

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

Does ZCode have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for ZCode. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is ZCode actively maintained?

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

What license does ZCode use?

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

Are ZCode's commits signed?

0% of the last 100 commits to ZCode 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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

medium 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 ZCode?

For maintainers

HVTrust scores ZCode 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-29

Newly Listed

First tracked at rank #1340

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Coding Agents

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