Is zerostack safe to use?

zerostack has an HVTrust score of 26.2/100 (Grade D), ranked #826 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for zerostack?

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

zerostack

gi-dellav/zerostack

Lightweight coding agent written in Rust, optimized for memory footprint and performance

Coding Agents Rust Grade D Listed GPL-3.0

26.2/100

Rank #826 of 1308

Compare zerostack

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-08-17 · 2d ago

Recent change

Rank +1

Is zerostack safe? zerostack scores 26.2/100 (Grade D), ranked #826 of 1308 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; 72% of recent commits are signed; last pushed 2026-08-17. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#55 Continue — 34.6 (D) → #56 PearAI — 32.8 (D) → #58 Kiro Crew — 25.7 (D) → #59 prime-agent — 25.1 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-17

Rank Moved

Rank rose 11 spots (#828 → #817)

2026-08-16

Rank Moved

Rank dropped 18 spots (#810 → #828)

2026-08-10

Rank Moved

Rank dropped 43 spots (#762 → #805)

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.

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

78.8

Activity sub-score · out of 100

#57

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 →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

1.6k

Forks

122

Last Push

2026-08-17

2 days ago

Commits (4 wk)

117

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼8

was #818

Analysis

HVTrust Dimensions vs Coding Agents

26.2 / 100 · 50.0% confidence

zerostack Coding Agents average (70 agents)

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

3.6 / 25

3.9 below avg 7.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

2.6 below avg 11.1

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

4.6 above avg 15.3

AdoptionLog-scaled stars · package downloads

7.7 / 20

4.6 below avg 12.3

Activity Inputs

78.8 / 100

StarsRepository reach

19.2 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

9.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

72%

of last 100 commits verified

Is zerostack safe?

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

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

Does zerostack have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for zerostack. 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 zerostack actively maintained?

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

What license does zerostack use?

zerostack ships under GPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are zerostack's commits signed?

72% of the last 100 commits to zerostack 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

Implemented

zerostack appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

OpenRouter

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool 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 zerostack?

For maintainers

HVTrust scores zerostack 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-17

Rank Moved

Rank rose 11 spots (#828 → #817)

2026-08-16

Rank Moved

Rank dropped 18 spots (#810 → #828)

2026-08-10

Rank Moved

Rank dropped 43 spots (#762 → #805)

2026-08-08

Rank Moved

Rank dropped 324 spots (#431 → #755)

2026-08-06

Newly Listed

First tracked at rank #464

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/zerostack.svg)](https://hvtracker.net/agents/zerostack)
            
HTML:
            <a href="https://hvtracker.net/agents/zerostack"><img src="https://hvtracker.net/badge/zerostack.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.3 · Raw JSON