updated 2026-07-29 00:30 UTC

Zeroboot

zerobootdev/zeroboot

Sub-millisecond VM sandboxes for AI agents via copy-on-write forking

Sandboxes & Runtimes Rust Grade D Listed Apache-2.0
Compare → Suggest correction
Listing state
Listed
HVTrust
15.4/100 · Grade D
Evidence coverage
Grade D · 1/5 signals
Last push
2026-03-21 · 130d ago
Recent change
New

Is Zeroboot safe? Zeroboot scores 15.4/100 (Grade D), ranked #438 of 441 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; 4% of recent commits are signed; last pushed 2026-03-21. 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.
15.4/100 · Grade D
Strongest Signal
Identity / Provenance
10.8/18
Weakest Signal
Safety / Integrity
0.2/25
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-07-28
Newly Listed
First tracked at rank #438
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.
Refresh maintenance signals The repo was last pushed 130 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Zeroboot View Sandboxes & Runtimes Report missing data
36.9
Activity sub-score · out of 100
15.4
HVTrust Score · out of 100
#438
Global Rank · of 441
#9
In Sandboxes & Runtimes

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 →

Signals refreshed 2026-07-29 00:30 UTC · Repo last pushed 130 days ago

Rank Trend

2026-07-28 2026-07-29

Activity & Reach

Stars
2.4k
Forks
107
Last Push
2026-03-21
130 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
6
Rank Change
=
was #438

Analysis

HVTrust Dimensions

15.4 / 100 · 50.0% confidence
Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.2 / 25
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
Maintenance60% last-push freshness · 40% commit activity
3.3 / 20
Adoption60% stars · 40% downloads, log-scaled
8.1 / 20

Activity Inputs

36.9 / 100
StarsRepository reach
20.3 / 30
FreshnessLast push recency
6.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
4%
of last 100 commits verified

Is Zeroboot safe?

Public trust evidence for Zeroboot 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 Zeroboot publish package provenance?
No published build provenance is currently detected for Zeroboot. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Zeroboot have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Zeroboot. 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 Zeroboot actively maintained?
Slowing down. Last push was 130 days ago — keep an eye on whether activity resumes.
What license does Zeroboot use?
Zeroboot ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Zeroboot's commits signed?
4% of the last 100 commits to Zeroboot 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.

Ranked neighbours in Sandboxes & Runtimes

#5 OpenSandbox — 48.1 (D) → #6 Cube Sandbox — 45.9 (D) → #7 OpenShell — 42.0 (D) → #8 Agent Infra Sandbox — 20.5 (D) →

AI agent 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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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 Zeroboot?

HVTrust scores Zeroboot 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

Listed 1
2026-07-28
Newly Listed
First tracked at rank #438
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Sandboxes & Runtimes

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