Daytona
Daytona is a Secure and Elastic Infrastructure for Running AI-Generated Code
Compare Daytona
How does it stack up against its Sandboxes & Runtimes neighbours?
Pick any agent to compare →Promising trust profile, but some evidence still deserves review.
Is Daytona safe? Daytona scores 67.0/100 (Grade B), ranked #189 of 1283 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.3/10; 100% of recent commits are signed; last pushed 2026-07-24. Every point is earned from checkable signals — never paid placement. How scoring works →
Ranked neighbours in Sandboxes & Runtimes
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Activity & Reach
Analysis
HVTrust Dimensions vs Sandboxes & Runtimes
67.0 / 100 · 100.0% confidenceDaytona Sandboxes & Runtimes average (10 agents)
Activity Inputs
69.1 / 100Supply Chain Trust
Is Daytona safe?
Does Daytona publish package provenance?
Does Daytona have an OpenSSF Scorecard?
Is Daytona actively maintained?
What license does Daytona use?
Are Daytona's commits signed?
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.
Compare Daytona head-to-head
AI agent surface
MCP, providers, tool surface
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Daytona?
For maintainers
HVTrust scores Daytona 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/daytona)
<a href="https://hvtracker.net/agents/daytona"><img src="https://hvtracker.net/badge/daytona.svg" alt="HVTrust"></a>
Other agents in Sandboxes & Runtimes
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON