updated 2026-08-19 05:02 UTC

Cube Sandbox

TencentCloud/CubeSandbox

Instant, Concurrent, Secure & Lightweight Sandbox for AI Agents.

Sandboxes & Runtimes Go Grade D Listed NOASSERTION
46.4/100
Rank #519 of 1308
Compare Cube Sandbox

How does it stack up against its Sandboxes & Runtimes neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-19 · 0d ago
Recent change
Rank +1

Is Cube Sandbox safe? Cube Sandbox scores 46.4/100 (Grade D), ranked #519 of 1308 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 5.1/10; 86% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Sandboxes & Runtimes

#5 Agent Infra Sandbox — 53.6 (C) → #6 OpenSandbox — 47.8 (D) → #8 OpenShell — 42.3 (D) → #9 Zeroboot — 35.4 (D) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-17
Rank Moved
Rank rose 10 spots (#518 → #508)
2026-08-13
Rank Moved
Rank dropped 11 spots (#497 → #508)
2026-08-10
Rank Moved
Rank dropped 17 spots (#488 → #505)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/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 Cube Sandbox View Sandboxes & Runtimes Report missing data
88.3
Activity sub-score · out of 100
#7
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 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 →

Signals refreshed 2026-08-19 05:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
11.2k
Forks
1.0k
Last Push
2026-08-19
today
Commits (4 wk)
224
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
52
Rank Change
▼9
was #510

Analysis

HVTrust Dimensions vs Sandboxes & Runtimes

46.4 / 100 · 67.0% confidence

Cube Sandbox Sandboxes & Runtimes average (10 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.7 / 25
in line with 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
12.8 / 17
in line with avg 12.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.4 above avg 15.6
AdoptionLog-scaled stars · package downloads
9.7 / 20
1.5 below avg 11.2

Activity Inputs

88.3 / 100
StarsRepository reach
24.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.1 / 10
OpenSSF Scorecard · scanned Aug 18, 2026
Signed Commits
86%
of last 100 commits verified
Binary-Artifacts 6
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 6
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 10
License 9
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Cube Sandbox safe?

Public trust evidence for Cube Sandbox 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 Cube Sandbox publish package provenance?
No published build provenance is currently detected for Cube Sandbox. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Cube Sandbox have an OpenSSF Scorecard?
Cube Sandbox has an OpenSSF Scorecard score of 5.1/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 Cube Sandbox actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Cube Sandbox use?
Cube Sandbox ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cube Sandbox's commits signed?
86% of the last 100 commits to Cube Sandbox 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 Cube Sandbox head-to-head

Cube Sandbox vs BoxLite → Cube Sandbox vs E2B → Cube Sandbox 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
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
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Cube Sandbox?

For maintainers

HVTrust scores Cube Sandbox 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
Rank 6Listed 1HVTrust 1Scorecard 1
2026-08-17
Rank Moved
Rank rose 10 spots (#518 → #508)
2026-08-13
Rank Moved
Rank dropped 11 spots (#497 → #508)
2026-08-10
Rank Moved
Rank dropped 17 spots (#488 → #505)
2026-08-08
Rank Moved
Rank dropped 131 spots (#356 → #487)
2026-07-22
Rank Moved
Rank rose 11 spots (#338 → #327)
2026-07-15
Scorecard Added
OSSF Scorecard: 4.0/10
2026-07-15
Rank Moved
Rank rose 52 spots (#387 → #335)
2026-07-15
HVTrust Changed
HVTrust up 19.8pts (25.0 → 44.8)
2026-07-14
Newly Listed
First tracked at rank #387
GitHub → PyPI: cubesandbox

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 46.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/cube-sandbox.svg)](https://hvtracker.net/agents/cube-sandbox)
HTML:
<a href="https://hvtracker.net/agents/cube-sandbox"><img src="https://hvtracker.net/badge/cube-sandbox.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
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON