container-use

Name: container-use
Rating: 3.24 (1 reviews)
Author: dagger

#804 · by dagger

agent tool-use multi-step

3.24/ 5.00

trustedBeta

Mar 3, 2026 at 7:21 AM6 signals analysed1 commits (90d)No manual reviews · fully automated

Trust Signal Breakdown

high3 sub-signals across 6 dimensions

CVEs, dependency health, and supply chain integrity

1 of 3 sub-signals with data

Known CVEs100%5.0

No known CVEs

via OSV.dev

Dependency Healthno data—

Weight redistributed to sub-signals with data

Supply Chainno data—

Weight redistributed to sub-signals with data

Uptime, latency, error rates, and incident history

0 of 0 sub-signals with data

Commit recency, release cadence, issue response, CI/CD

0 of 0 sub-signals with data

Downloads, stars, dependents, and growth trajectory

0 of 0 sub-signals with data

License, documentation, security policy, changelog

0 of 0 sub-signals with data

Track record, org maturity, community standing

0 of 0 sub-signals with data

About this score

Scored across 3 sub-signals in 6 dimensionsScoring engine v1 (beta) — actively being expandedPhase 1: Core sub-signal architecture (live)Phase 2: Permission scope & expanded collection (in progress)

Trust AssessmentAI Assessment

Containerized environments for coding agents. Multiple agents can work independently, isolated in fresh containers and git branches. No conflicts, many experiments. Full execution history, terminal access to agent environments, git workflow. Any agent/model/infra stack.

Package Availability (30d)

100.00%

p50: 217ms · p99: 217ms

Avg Latency

117ms

averaged across 30d health checks

Weekly Downloads

—

no package registry data

Transparency & Compliance5/5 passed

✓

Open Source CodePublic repository on GitHub