updated 2026-10-13 04:10 UTC

Cube Sandbox

Repository Website by TencentCloud

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

Sandboxes & Runtimes Go Listed NOASSERTION

Is Cube Sandbox safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.0 / 10
Provenance None
Signed commits 82%
Last push yesterday
Advisories None known
Compare Cube Sandbox

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

Pick any agent to compare →
Suggest a correction

In detail: Cube Sandbox scores 71.7/100 (Grade B), ranked #319 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 82% of recent commits are signed; no published advisory affects its latest release (cubesandbox); last pushed 2026-10-12. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cube Sandbox could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Cube Sandbox and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/TencentCloud/CubeSandbox, NOASSERTION, last pushed 2026-10-12. 82% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.0/10 (scanned Sep 27, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review4
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 6
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 4
    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

  3. Published packages Linked, not attested

    • PyPI cubesandbox Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: cubesandbox 0.7.0. No published advisory affects it (OSV, checked 2026-10-12).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Cube Sandbox.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Cube Sandbox’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Cube Sandbox compares in Sandboxes & Runtimes

  1. #2 E2B 77.6 +5.9
  2. #3 OpenShell 74.1 +2.4
  3. #4 Cube Sandbox 71.7 this agent
  4. #5 OpenSandbox 70.6 −1.1
  5. #6 Fence 56.6 −15.1

Bars show each HVTrust score; the tick marks Cube Sandbox’s 71.7.

Where the 71.7 comes from

HVTrust dimensions vs the Sandboxes & Runtimes average

71.7 / 100 · 100.0% confidence

Cube Sandbox Sandboxes & Runtimes average (11 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.4 / 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
0.8 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
5.6 above avg 14.3
AdoptionLog-scaled stars · package downloads
14.1 / 20
1.4 above avg 12.7

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-26
Rank Moved
Rank dropped 10 spots (#282 → #292)
2026-09-23
Rank Moved
Rank dropped 162 spots (#107 → #269)
2026-09-21
Rank Moved
Rank rose 174 spots (#281 → #107)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.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.
Compare with BoxLite Get email alerts for Cube Sandbox View Sandboxes & Runtimes Report missing data
89.0
Activity sub-score · out of 100
#4
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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-13 04:10 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-13

Activity & Reach

Stars
12.9k
Forks
1.2k
Last Push
2026-10-12
yesterday
Commits (4 wk)
104
Downloads (7d)
1,509
pypi
HN mentions (30d)
—
Open Issues
89
Rank Change
▼1
was #318

Analysis

Activity Inputs

89.0 / 100
StarsRepository reach
24.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.3 / 20

Common questions about Cube Sandbox

Cube Sandbox 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 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.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 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?
82% 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 OpenShell →

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 24HVTrust 1Grade 1
2026-09-26
Rank Moved
Rank dropped 10 spots (#282 → #292)
2026-09-23
Rank Moved
Rank dropped 162 spots (#107 → #269)
2026-09-21
Rank Moved
Rank rose 174 spots (#281 → #107)
2026-09-08
Rank Moved
Rank dropped 11 spots (#263 → #274)
2026-09-07
Rank Moved
Rank dropped 17 spots (#246 → #263)
2026-09-06
Rank Moved
Rank rose 10 spots (#256 → #246)
2026-09-05
Rank Moved
Rank dropped 57 spots (#199 → #256)
2026-09-04
Grade Changed
Trust grade D → B
2026-09-04
Rank Moved
Rank rose 659 spots (#858 → #199)
2026-09-04
HVTrust Changed
HVTrust up 25.0pts (46.4 → 71.4)
2026-09-03
Rank Moved
Rank dropped 51 spots (#807 → #858)
2026-09-02
Rank Moved
Rank dropped 43 spots (#764 → #807)
2026-09-01
Rank Moved
Rank dropped 24 spots (#740 → #764)
2026-08-31
Rank Moved
Rank dropped 29 spots (#711 → #740)
2026-08-30
Rank Moved
Rank dropped 29 spots (#682 → #711)
2026-08-29
Rank Moved
Rank dropped 47 spots (#635 → #682)
2026-08-28
Rank Moved
Rank dropped 19 spots (#616 → #635)
2026-08-27
Rank Moved
Rank dropped 14 spots (#602 → #616)
2026-08-26
Rank Moved
Rank dropped 89 spots (#513 → #602)
2026-08-24
Rank Moved
Rank dropped 10 spots (#504 → #514)
2026-08-22
Rank Moved
Rank rose 11 spots (#518 → #507)
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)
GitHub → Website → PyPI: cubesandbox

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 71.7 Grade B
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.4 · Raw JSON