Is Container Use safe to use?

Container Use has an HVTrust score of 59.8/100 (Grade C), ranked #383 of 1316 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Container Use?

Container Use scores 59.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 4.0k GitHub stars and is categorized under Sandboxes & Runtimes.

Container Use

dagger/container-use

Development environments for coding agents. Enable multiple agents to work safely and independently with your preferred

Sandboxes & Runtimes Go Grade C Listed Apache-2.0

59.8/100

Rank #383 of 1316

Compare Container Use

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 C · 2/5 signals

Last push

2026-08-17 · 12d ago

Recent change

Rank +2

Is Container Use safe? Container Use scores 59.8/100 (Grade C), ranked #383 of 1316 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 99% 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 Sandboxes & Runtimes

#3 Daytona — 67.3 (B) → #4 Fence — 59.8 (C) → #6 Agent Infra Sandbox — 53.6 (C) → #7 OpenSandbox — 47.2 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-26

Rank Moved

Rank dropped 34 spots (#333 → #367)

2026-08-24

Rank Moved

Rank dropped 18 spots (#315 → #333)

2026-08-22

Rank Moved

Rank rose 18 spots (#332 → #314)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.8/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.

Compare with BoxLite Get email alerts for Container Use 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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-29

Activity & Reach

Stars

4.0k

Forks

201

Last Push

2026-08-17

12 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼7

was #376

Analysis

HVTrust Dimensions vs Sandboxes & Runtimes

59.8 / 100 · 100.0% confidence

Container Use Sandboxes & Runtimes average (10 agents)

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

10.9 / 25

in line with avg 11.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.7 below avg 11.5

Transparency50% declared license · 50% OSSF Scorecard

12.6 / 17

0.5 below avg 13.1

Maintenance60% last-push freshness · 40% commit activity

14.8 / 20

0.6 below avg 15.4

AdoptionLog-scaled stars · package downloads

8.7 / 20

2.5 below avg 11.2

Activity Inputs

67.1 / 100

StarsRepository reach

21.6 / 30

FreshnessLast push recency

23.3 / 25

ActivityRecent commits

11.3 / 25

CommunityFork signal

10.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.8 / 10

OpenSSF Scorecard · scanned Aug 25, 2026

Signed Commits

99%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 8

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 6

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Container Use safe?

Container Use 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 Container Use publish package provenance?

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

Does Container Use have an OpenSSF Scorecard?

Container Use has an OpenSSF Scorecard score of 4.8/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 Container Use actively maintained?

Maintained. Last push was 12 days ago.

What license does Container Use use?

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

Are Container Use's commits signed?

99% of the last 100 commits to Container Use 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 Container Use head-to-head

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

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

Container Use 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

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 Container Use?

For maintainers

HVTrust scores Container Use 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-26

Rank Moved

Rank dropped 34 spots (#333 → #367)

2026-08-24

Rank Moved

Rank dropped 18 spots (#315 → #333)

2026-08-22

Rank Moved

Rank rose 18 spots (#332 → #314)

2026-08-19

Rank Moved

Rank dropped 18 spots (#313 → #331)

2026-08-17

Rank Moved

Rank rose 20 spots (#334 → #314)

2026-08-16

Rank Moved

Rank dropped 10 spots (#324 → #334)

2026-08-13

Rank Moved

Rank dropped 18 spots (#304 → #322)

2026-08-12

Rank Moved

Rank rose 46 spots (#350 → #304)

2026-08-11

Activity Score Changed

Activity score up 17pts (49 → 66)

2026-08-10

Rank Moved

Rank dropped 15 spots (#421 → #436)

2026-08-08

Rank Moved

Rank dropped 105 spots (#312 → #417)

2026-07-15

Scorecard Added

OSSF Scorecard: 4.4/10

2026-07-15

Grade Changed

Trust grade D → C

2026-07-15

Rank Moved

Rank rose 126 spots (#396 → #270)

2026-07-15

HVTrust Changed

HVTrust up 30.5pts (23.4 → 53.9)

2026-07-14

Newly Listed

First tracked at rank #396

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Sandboxes & Runtimes

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