Is Daytona safe to use?

Daytona has an HVTrust score of 67.6/100 (Grade B), ranked #188 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Daytona?

Daytona scores 67.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 71.9k GitHub stars and is categorized under Sandboxes & Runtimes.

Daytona

daytonaio/daytona

Daytona is a Secure and Elastic Infrastructure for Running AI-Generated Code

Sandboxes & Runtimes TypeScript Grade B Listed AGPL-3.0

67.6/100

Rank #188 of 1308

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.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-07-24 · 32d ago

Recent change

Rank +3

Is Daytona safe? Daytona scores 67.6/100 (Grade B), ranked #188 of 1308 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 6.0/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

#1 BoxLite — 85.2 (A) → #2 E2B — 78.3 (B) → #4 Container Use — 60.0 (C) → #5 Agent Infra Sandbox — 55.0 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-24

Rank Moved

Rank dropped 13 spots (#175 → #188)

2026-08-22

Rank Moved

Rank rose 11 spots (#185 → #174)

2026-08-21

Rank Moved

Rank rose 24 spots (#209 → #185)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.0/10. Tighten the weakest checks to improve public safety evidence.

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

Refresh maintenance signals The repo was last pushed 32 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with BoxLite Get email alerts for Daytona View Sandboxes & Runtimes Report missing data

67.1

Activity sub-score · out of 100

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 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 →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

71.9k

Forks

5.6k

Last Push

2026-07-24

32 days ago

Commits (4 wk)

Downloads (7d)

220,260

pypi

HN mentions (30d)

Open Issues

314

Rank Change

was #188

Analysis

HVTrust Dimensions vs Sandboxes & Runtimes

67.6 / 100 · 100.0% confidence

Daytona Sandboxes & Runtimes average (10 agents)

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

12.5 / 25

2.1 above avg 10.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.7 below avg 11.5

Transparency50% declared license · 50% OSSF Scorecard

13.6 / 17

1.1 above avg 12.5

Maintenance60% last-push freshness · 40% commit activity

9.9 / 20

5.7 below avg 15.6

AdoptionLog-scaled stars · package downloads

18.8 / 20

7.6 above avg 11.2

Activity Inputs

67.1 / 100

StarsRepository reach

29.1 / 30

FreshnessLast push recency

20.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

17.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.0 / 10

OpenSSF Scorecard · scanned Aug 24, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 1

CI-Tests 8

CII-Best-Practices 0

Code-Review 8

Contributors 10

Dangerous-Workflow -1

Dependency-Update-Tool 10

Fuzzing 0

License 0

Maintained 10

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 10

Is Daytona safe?

Daytona has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Daytona publish package provenance?

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

Does Daytona have an OpenSSF Scorecard?

Daytona has an OpenSSF Scorecard score of 6.0/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 Daytona actively maintained?

Slowing down. Last push was 32 days ago — keep an eye on whether activity resumes.

What license does Daytona use?

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

Are Daytona's commits signed?

100% of the last 100 commits to Daytona 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.

Compare Daytona head-to-head

Daytona vs BoxLite → Daytona vs E2B → Daytona vs Container Use →

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

Daytona appears to expose MCP server capabilities.

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

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-24

Rank Moved

Rank dropped 13 spots (#175 → #188)

2026-08-22

Rank Moved

Rank rose 11 spots (#185 → #174)

2026-08-21

Rank Moved

Rank rose 24 spots (#209 → #185)

2026-08-19

Rank Moved

Rank dropped 10 spots (#197 → #207)

2026-08-13

Rank Moved

Rank dropped 13 spots (#175 → #188)

2026-08-12

Rank Moved

Rank rose 14 spots (#189 → #175)

2026-08-10

Rank Moved

Rank dropped 11 spots (#178 → #189)

2026-08-08

Rank Moved

Rank dropped 28 spots (#144 → #172)

2026-07-25

Grade Changed

Trust grade B → C

2026-07-25

Rank Moved

Rank dropped 16 spots (#143 → #159)

2026-07-23

Rank Moved

Rank dropped 17 spots (#128 → #145)

2026-07-23

Activity Score Changed

Activity score down 7pts (82 → 76)

2026-07-19

Rank Moved

Rank dropped 10 spots (#117 → #127)

2026-07-13

Rank Moved

Rank dropped 11 spots (#78 → #89)

2026-06-24

Scorecard Added

OSSF Scorecard: 5.4/10

2026-06-24

Grade Changed

Trust grade D → B

2026-06-24

Rank Moved

Rank rose 159 spots (#216 → #57)

2026-06-24

HVTrust Changed

HVTrust up 27.1pts (47.1 → 74.2)

2026-06-23

Rank Moved

Rank dropped 15 spots (#201 → #216)

2026-06-21

Rank Moved

Rank dropped 10 spots (#182 → #192)

2026-06-18

Rank Moved

Rank dropped 13 spots (#164 → #177)

2026-06-02

Rank Moved

Rank dropped 10 spots (#142 → #152)

2026-06-01

Rank Moved

Rank dropped 17 spots (#125 → #142)

2026-05-29

HVTrust Changed

HVTrust up 7.4pts (34.1 → 41.5)

2026-05-28

Activity Score Changed

Activity score up 25pts (72 → 97)

GitHub → PyPI: daytona-sdk

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Sandboxes & Runtimes

Data sources
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