Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want coding agents to run in real sandboxes rather than on a developer laptop. It makes the remote-control layer reusable, which is a much more practical step toward safe agent execution than another local-only wrapper.
Who should use it
Who should skip it
Skip rivet-dev/sandbox-agent if you cannot isolate its execution environment or audit what data it touches before connecting anything sensitive.
About this signal
rivet-dev/sandbox-agent is tracked by RepoRadar as a framework in the Radar section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'try now' with a Gold tier and advanced setup difficulty. rivet-dev/sandbox-agent leads on workflow potential (10.0) and practical usefulness (9.0); its lowest signal is setup ease (4.2), so factor that in before investing setup time. 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 rivet-dev/sandbox-agent record combines a 9.0/10 composite score with separate popularity (88.0), risk (medium), and setup (advanced) 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
This framework is designed to run real coding agents that can execute code and touch repositories inside a sandbox, so start with isolated environments and low-privilege credentials until you trust the permission flow.