Item detail
github.com

opensandbox-group/OpenSandbox

RepoRadar surfaced opensandbox-group/OpenSandbox — a developer tool — into the Radar section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Score8.5
Popularity90.0
Risknone
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum9.0
Maturity8.5
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for platform and infra teams running AI agents that need a multi-language, multi-runtime sandbox with policy-driven network and credential controls, plus a CNCF-aligned community for cross-team adoption.

Who should use it

platform teams running heterogeneous AI agent workloads (coding, GUI, evaluation, RL) that need one sandbox across all of them engineering teams in multi-language shops (Python / Java / JS / C# / Go) that need SDKs in their existing languages infra teams adopting CNCF-aligned open source with gVisor / Kata / Firecracker isolation options security teams that need credential vault with secret-less injection and per-sandbox network policy agent framework authors adding sandbox-as-a-service as a runtime layer

Who should skip it

Pass on opensandbox-group/OpenSandbox if its scope or audience does not match what your team is building right now.

About this signal

opensandbox-group/OpenSandbox is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-17; the source record was last checked on 2026-06-17. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for opensandbox-group/OpenSandbox are workflow potential (10.0) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The opensandbox-group/OpenSandbox record combines a 8.5/10 composite score with separate popularity (90.0), risk (none), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

No inherent user-impacting risk is flagged from the captured evidence.

Evidence links
Closest alternatives / related signals
sandbox agent-runtime multi-language kubernetes docker gvisor kata firecracker
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-14T00:34:39Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

49 dated snapshots retained from 2026-06-17 through 2026-08-14; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.5 current · +0.0 net
Repository momentum9.6 current · +0.6 net
GitHub stars (observed)12,526 current · +543 net
GitHub stars12,526 exact observation
Versiondocker/execd/v1.0.22
Last release2026-08-13T06:30:07Z
Maintenanceactive
Current risknone
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-148.59.612,526nonetry nowactive
2026-08-138.59.612,526nonetry nowactive
2026-08-128.59.612,495nonetry nowactive
2026-08-118.59.612,470nonetry nowactive
2026-08-108.59.612,438nonetry nowactive
2026-08-098.59.312,409nonetry nowactive
2026-08-088.59.612,401nonetry nowactive
2026-08-078.59.612,309nonetry nowactive
2026-08-068.59.0Not recordednonetry nownot recorded
2026-08-058.59.0Not recordednonetry nownot recorded
2026-08-048.59.612,309nonetry nowactive
2026-08-038.59.612,309nonetry nowactive

Why the record changed

version changed

Version changed: docker/egress/v1.1.6 → docker/execd/v1.0.22.

stars changed

Stars changed: 12495 → 12526.

version changed

Version changed: java/sandbox/v1.0.18 → docker/egress/v1.1.6.

stars changed

Stars changed: 12470 → 12495.

stars changed

Stars changed: 12438 → 12470.

stars changed

Stars changed: 12409 → 12438.

stars changed

Stars changed: 12401 → 12409.

version changed

Version changed: docker/egress/v1.1.5 → java/sandbox/v1.0.18.

stars changed

Stars changed: 12309 → 12401.

stars changed

Stars changed: 12283 → 12309.

stars changed

Stars changed: 12276 → 12283.

stars changed

Source-observed stars changed: 12269 → 12276. This reports the retained observation delta and does not infer why the upstream change occurred.