PAGES
← all tools
◆ Runtime Security

CubeSandbox

v0.7.2 open-source

CubeSandbox is a secure sandbox service built on RustVMM and KVMKVMA Linux kernel module that turns the kernel into a hypervisor, letting a process run fully isolated virtual machines using hardware virtualisation extensions. Cyber tools use it to sandbox execution environments at near-native speed. that creates hardware-isolated MicroVM sandboxes in under 60ms with less than 5MB memory overhead.

Summary

CubeSandbox is an open-source, Apache 2.0-licensed sandbox service that gives AI agents isolated, hardware-level execution environments to run code in, self-hosted as a cluster of components (CubeMaster, Cubelet, CubeProxy) with a systemd-based installer, a Web UI, and Go/Python SDKs for programmatic control. It targets teams building or operating AI agent infrastructure who need to run untrusted, agent-generated code without it touching the host, rather than security teams doing manual analysis. Its README describes it as E2B-compatible and positions it within CNCF's AI-native infra landscape, with features like copy-on-write snapshots, an OpenResty-based egress proxy for credential injection and domain filtering, and Prometheus metrics for cluster monitoring. First committed in 2026, it already has 68 contributors and 16 releases in the past year, the latest 28 days ago, suggesting active development.

CubeSandbox is a secure sandbox service built on RustVMM and KVM that creates hardware-isolated MicroVM sandboxes in under 60ms with less than 5MB memory overhead.

How CubeSandbox helps

Which of my agent's outbound connections are actually leaving the sandbox, and to where?

the egress proxy logs every L7 request as structured JSON with domain, route, and body detail, giving a per-sandbox audit trail of what left the box and through which allow/deny rule it passed

Can an agent I'm running get to a credential without ever seeing it in its own code or environment?

credentials are injected at the proxy layer per egress rule rather than into the sandbox, so anything captured in logs or by the agent itself shows only a redacted placeholder

Did an agent's runaway or misbehaving process actually stay contained, or did it touch the host?

each sandbox runs its own dedicated kernel inside a MicroVM boundary, so a compromise or crash inside one sandbox has no path to the host or to other sandboxes

What was running in a sandbox right before something went wrong, and can I get back to that exact state?

copy-on-write and incremental memory snapshots let a sandbox be checkpointed and rolled back to a prior point-in-time state, or forked to explore what would have happened differently

Are all my cluster nodes running compatible versions of the sandbox components?

the version matrix reports guest-image, agent, kernel and control-plane versions per node and surfaces skew, and template compatibility checks flag replicas whose node doesn't match what the template expects

How many concurrent agent sandboxes can this cluster actually hold before I run out of resources?

Cubelet reports live CPU, memory and disk usage per node to CubeMaster, and the low per-sandbox memory overhead from page sharing determines how many resident instances a given node can carry

all 42 features, with the evidence for each →

Languages

English, Chinese (Simplified) Interface: English, Chinese (Simplified) · Documentation: English, Chinese (Simplified) · Release notes: English, Chinese (Simplified) English, Chinese (Simplified) added in v0.3.0 (Jun 2, 2026) · Chinese (Simplified) added in v0.2.2 (May 18, 2026) · English added in v0.2.1 (May 14, 2026)

Features

42 capabilities across 6 areas · 5 backed by code, an API document or a real run

Built from CubeSandbox's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • CubeSandbox covers 1 of the 11 endpoint investigation and controls capabilities we track.

What CubeSandbox offers you

  • Command-line interface6
  • Client SDKs4
  • Scripting language support4
  • Python scripting support3
  • REST API2
  • Scripting API2
  • Web management console2
  • Air-gapped deployment1
  • CI/CD pipeline integration1
  • Disaster recovery1
  • JSON data export1
  • Kubernetes-native deployment1
  • Offline mode1
  • Plugin API support1
  • Plugin system1
  • Self-hosted deployment1
Sandbox Lifecycle and Scheduling 6 capabilities CubeSandbox's core function is creating and managing isolated sandbox environments from templates, with fine-grained control over timeouts, reclaim timing, and compute node placement. Operators can pause, resume, and delete sandboxes, drain nodes for maintenance, and tune scheduling deadlines independently of idle reclaim.
Sandbox lifecycle management verified Create, pause, resume, and delete sandboxes with configurable idle timeouts and never-expire sentinels. 14 releases · 4 other sources · first seen Apr 2026

Also counts toward: Python scripting support, Scripting language support, Client SDKs

release 14 total

  • Adds new top-level redis.db Helm config key applied to CubeMaster, CubeProxy, and CLM so multiple clusters sharing one Redis instance can isolate logical databases per cluster. v0.7.1 · Sep 2026 · source · release history
  • New top-level redis.db configuration key applies to CubeMaster / CubeProxy / CLM for logical-DB isolation when sharing one Redis instance v0.7.1 · Sep 2026 · source · release history
  • Introduces component multi-versioning so that templates and snapshots record their component dependency versions, allowing historical templates and snapshots to remain usable after compute-node component upgrades. v0.7.0 · Aug 2026 · source · release history
  • Support deleting sandboxes that are in the paused state. v0.6.0 · Jul 2026 · source · release history
  • Adds three-value idle-timeout semantics: omitted inherits cluster default, NEVER_TIMEOUT (-1) disables reclaim, 0 reclaims on first idle sweep, and N>0 sets an explicit TTL in seconds. v0.5.1 · Jul 2026 · source · release history
  • Adds three-value timeout semantics: omitted inherits cluster default, NEVER_TIMEOUT (-1) disables idle reclaim, 0 triggers immediate reclaim, and N>0 sets an idle TTL in seconds — with server-side defaults in CubeMaster. v0.5.1 · Jul 2026 · source · release history

command line

  • --detach, no-wait — submit and exit immediately instead of watching the redo job to completion v0.5.0-rc1 · Jul 2026 · command-line history

example

  • Set a Node SDK sandbox to never time out for long-running interactive sessions. await sandbox.setTimeout(Sandbox.NEVER_TIMEOUT); v0.7.0 · Aug 2026 · source
  • Pin a long-running sandbox so it is never reclaimed by the idle sweeper — useful for persistent dev environments or always-on agent workloads. # Python SDK sandbox = await client.create(options=CreateOptions(timeout=NEVER_TIMEOUT)) # Adjust an already-running sandbox await sandbox.set_timeout(NEVER_TIMEOUT) v0.5.1 · Jul 2026 · source
  • Set a sandbox to never be reclaimed on idle at runtime — useful for long-running interactive sessions where you control teardown explicitly. # Python SDK sandbox.set_timeout(NEVER_TIMEOUT) # Go SDK sandbox.SetTimeout(NeverTimeout) v0.5.1 · Jul 2026 · source
Template management verified Build and register sandbox templates by ID or human-readable alias, with optional shared-memory device support. 11 releases · 3 other sources · first seen Apr 2026

Also counts toward: Command-line interface

release 11 total

  • Allows Cubelet to configure the template install path so large templates can be moved to the data disk (#1675). v0.7.2 · Sep 2026 · source · release history
  • tpl delete in cubemastercli now accepts multiple template IDs to batch-delete templates in a single call v0.7.1 · Sep 2026 · source · release history
  • Adds tpl delete subcommand to cubemastercli accepting multiple template IDs in a single batch deletion call. v0.7.1 · Sep 2026 · source · release history
  • Supports pulling images from HTTP (private) image registries to build templates. v0.7.0 · Aug 2026 · source · release history
  • Adds full template alias support (build-time aliases and alias management for existing templates) across Go, Node, and Python SDKs. v0.7.0 · Aug 2026 · source · release history
  • Template aliases can be set at creation time, allowing sandboxes to be launched by alias name instead of template ID. v0.6.0 · Jul 2026 · source · release history

command line

  • --alias — human-readable stable alias for the template (e.g. my-app); sandboxes can reference the template by this alias instead of the generated template ID; valid: [a-z0-9-], max 64 chars v0.6.0-rc1 · Jul 2026 · command-line history
  • --enable-ivshmem — boot the template build sandbox with ivshmem enabled v0.6.0-rc1 · Jul 2026 · command-line history

example

  • Delete several obsolete templates in one API call instead of looping manually. cubemastercli tpl delete <template-id-1> <template-id-2> <template-id-3> v0.7.1 · Sep 2026 · source
Compute node isolation for maintenance shipped Drain a compute node so no new sandboxes are scheduled to it while existing ones keep running, then restore it when maintenance is done. 2 releases · 3 other sources · first seen Jul 2026

Also counts toward: Command-line interface

release

  • New compute node isolation commands (cubemastercli node isolate / unisolate) let operators drain a node for maintenance without disturbing running sandboxes. v0.6.0 · Jul 2026 · source · release history
  • Adds node isolation capability at the scheduling layer, controllable via cubemastercli node isolate and node unisolate v0.6.0 · Jul 2026 · source · release history

example

  • Lift isolation on a node after maintenance is complete to allow new sandbox scheduling to resume. cubemastercli node unisolate <node-id> v0.6.0 · Jul 2026 · source
  • Isolate a compute node before maintenance so no new sandboxes are scheduled to it while existing ones keep running. cubemastercli node isolate <node-id> v0.6.0 · Jul 2026 · source
  • Isolate a compute node to prevent new sandboxes from being scheduled while performing maintenance cubemastercli node isolate <node-id> v0.6.0 · Jul 2026 · source
RPC scheduling timeout and idle TTL decoupling shipped Set the RPC scheduling deadline separately from the sandbox idle TTL so creation timeouts and reclaim timing can be tuned independently. 2 releases · first seen Jul 2026

release

  • Decouples RPC scheduling deadline (create_timeout_insec, default 300s) from sandbox idle TTL in CubeMaster. v0.5.1 · Jul 2026 · source · release history
  • Adds a new create_timeout_insec RPC deadline (default 300 s) decoupled from the idle TTL, bounding only the create/scheduling RPC. v0.5.1 · Jul 2026 · source · release history
Cubelet state tmpfs dynamic expansion shipped Dynamically expand the tmpfs used for Cubelet state storage while a sandbox is running. 1 release · first seen Jul 2026

release

In-sandbox cgroup v2 support shipped Run processes inside a sandbox under cgroup v2 rather than v1. 1 release · first seen Jul 2026

release

Network Control and Egress 5 capabilities CubeSandbox enforces outbound traffic policies per sandbox and can transparently intercept and credential-inject both HTTP and HTTPS egress traffic. Routing configuration covers MAC addressing, Host header rewriting, and DNS resolution for sandbox domains.
Egress policy and transparent proxy shipped Enforce per-sandbox outbound egress policies via a transparent proxy, skipping re-evaluation for already-established TCP sessions. 8 releases · first seen Jun 2026

release 8 total

  • Adds minimum TTL clamping (≥300 s) for DNS-learned egress allow entries to prevent reconnect denials from short DNS TTLs. v0.5.1 · Jul 2026 · source · release history
  • CubeEgress transparent-proxy listen address is now derived from CUBE_SANDBOX_NETWORK_CIDR instead of the hard-coded 192.168.0.1; deployments using custom sandbox CIDRs must verify their TPROXY / OpenResty configuration matches the new derived address. v0.5.1 · Jul 2026 · source · release history
  • Skips egress policy re-evaluation for established TCP sessions in CubeVS, preventing DNS expiry from breaking live connections. v0.5.1 · Jul 2026 · source · release history
  • Skips egress policy re-evaluation for established TCP sessions in CubeVS so DNS TTL expiry no longer breaks live connections. v0.5.1 · Jul 2026 · source · release history
  • CubeEgress transparent-proxy listen address is no longer hard-coded to 192.168.0.1; it is now derived from CUBE_SANDBOX_NETWORK_CIDR, so deployments using custom sandbox network CIDRs will get a different TPROXY/OpenResty listen address. v0.5.1 · Jul 2026 · source · release history
  • Adds minimum TTL clamping (≥300s) for DNS-learned egress allow entries to prevent reconnect denials on short DNS TTLs. v0.5.1 · Jul 2026 · source · release history
Egress credential injection and MITM TLS inspection shipped Inject credentials into outbound HTTP and HTTPS traffic through a MITM proxy that issues leaf certificates with subjectAltName for broad TLS compatibility. 5 releases · first seen Jun 2026

Also counts toward: JSON data export, Scripting language support

release

  • CubeEgress MITM now writes subjectAltName on leaf certificates for broader TLS verification compatibility. v0.6.0 · Jul 2026 · source · release history
  • Enables CubeEgress credential injection against plain HTTP upstreams (not just TLS), keeping secrets out of sandbox code. v0.5.1 · Jul 2026 · source · release history
  • Supports CubeEgress credential injection against plain HTTP upstreams (not only TLS). v0.5.1 · Jul 2026 · source · release history
  • Adds structured JSON egress access logs with optional body redaction via a redactor Lua module for downstream compliance review. v0.4.0 · Jun 2026 · source · release history
  • Adds per-sandbox credential injection at the proxy layer via EgressRule.inject, so user code inside the sandbox never handles raw credentials; credential material is redacted as ***REDACTED*** in safe-log output. v0.4.0 · Jun 2026 · source · release history
Host header masking for sandbox HTTP routing shipped Configure the Host header forwarded into a sandbox to improve compatibility with Host-based routing inside it. 2 releases · 1 other source · first seen Jul 2026

release

  • Enables masking the inbound Host header via the network.maskRequestHost parameter during sandbox creation v0.6.0 · Jul 2026 · source · release history
  • New network.maskRequestHost parameter lets operators configure the Host header forwarded into a sandbox (e.g. localhost:${PORT}), improving compatibility with Host-based routing inside sandboxes. v0.6.0 · Jul 2026 · source · release history

example

  • Create a sandbox forwarding a custom Host header for services relying on HTTP routing POST /api/v1/sandboxes\n{\n \"network\": {\n \"maskRequestHost\": \"localhost:3000\"\n }\n} v0.6.0 · Jul 2026 · source
DNS resolution fallback for sandbox domains shipped Install an optional dnsmasq fallback so sandbox domains resolve correctly in environments without systemd-resolved or NetworkManager's dnsmasq plugin. 2 releases · first seen Jul 2026

release

  • Adds optional one-click dnsmasq fallback for hosts where systemd-resolved is absent and NetworkManager's dnsmasq plugin never spawns, restoring cube.app resolution. v0.5.1 · Jul 2026 · source · release history
  • Adds optional dnsmasq fallback in one-click installer for environments where systemd-resolved and NetworkManager's dnsmasq plugin are absent, restoring cube.app resolution. v0.5.1 · Jul 2026 · source · release history
Cube router MAC address configuration verified Set the cube-router MAC address via a CLI flag when configuring network routing. 1 other source · first seen Jul 2026

command line

Multi-Tenancy and Isolation 2 capabilities CubeSandbox enforces boundaries between tenants by restricting which host paths sandboxes can bind-mount and by scaling the proxy layer across replicas with coordinated pause behaviour. These controls limit the blast radius of a misbehaving or malicious sandbox in a shared cluster.
CubeProxy horizontal scaling with auto-pause coordination shipped Scale CubeProxy across multiple replicas with Redis-based discovery and coordinated auto-pause and resume so the proxy tier remains consistent at any replica count. 7 releases · 1 other source · first seen May 2026

release 7 total

  • Adds CubeProxy support for a custom management port and the gRPC protocol. v0.7.0 · Aug 2026 · source · release history
  • The cube-proxy-sidecar in-image AutoPause coordinator has been extracted into a standalone cube-lifecycle-manager service; deployments that relied on the sidecar for AutoPause coordination must now deploy the separate CLM service. v0.5.1 · Jul 2026 · source · release history
  • Adds TencentCloud Terraform support for multi-replica CubeProxy (TENCENTCLOUD_CUBE_PROXY_REPLICAS) with CLM replica count, discovery refresh interval, and admin token configuration. v0.5.1 · Jul 2026 · source · release history
  • Introduces cube-lifecycle-manager (CLM), a standalone control-plane service extracted from the CubeProxy sidecar, enabling CubeProxy to scale horizontally with Redis-based replica discovery and coordinated auto-pause/resume. v0.5.1 · Jul 2026 · source · release history
  • New per-sandbox traffic_access_token (UUID v4): CubeProxy enforces it on every inbound request when network.allow_public_traffic=false, returning HTTP 403 for missing or mismatched tokens; values are redacted from all logs. v0.5.0 · Jul 2026 · source · release history
  • CUBE_PROXY_HOST_PORT is deprecated and split into CUBE_PROXY_HTTP_PORT and CUBE_PROXY_HTTPS_PORT — existing configs using CUBE_PROXY_HOST_PORT will need to be updated. v0.5.0 · Jul 2026 · source · release history

example

  • Scale CubeProxy horizontally with CLM coordinating auto-pause across replicas, configured via Terraform. # terraform.tfvars TENcentCLOUD_CUBE_PROXY_REPLICAS = 3 cube_lifecycle_manager_replicas = 1 cube_lifecycle_manager_discovery_refresh_interval = 30 v0.5.1 · Jul 2026 · source
Host bind-mount path allowlisting shipped Restrict sandbox bind-mounts to configured path prefixes, preventing traversal attempts from exposing arbitrary host paths in multi-tenant clusters. 7 releases · 1 other source · first seen Jun 2026

Shared capability: Security baseline enforcement

release 7 total

  • Host bind-mounts are now restricted to paths under configurable allowlist prefixes (default /data/shared/); sandboxes that previously mounted arbitrary host paths will be rejected after upgrade. v0.5.1 · Jul 2026 · source · release history
  • Host-mount paths are now restricted to configurable prefixes (default /data/shared/); previously any absolute path was accepted, so existing sandboxes using host bind-mounts outside the allowed prefix will be rejected. v0.5.1 · Jul 2026 · source · release history
  • Introduces host-mount path allowlisting restricted to configurable prefixes (default /data/shared/), with filepath.Clean traversal neutralization and an explicit ban on / as a configured prefix. v0.5.1 · Jul 2026 · source · release history
  • Adds host-mount path allowlisting: bind-mounts are restricted to configurable prefixes (default /data/shared/) with filepath.Clean traversal neutralization; / is explicitly forbidden. v0.5.1 · Jul 2026 · source · release history
  • New optional cube-router kernel dummy device routes sandbox outbound traffic through any routable host interface (eth0, eth1, GRE, VXLAN, WireGuard) instead of hard-redirecting to the primary NIC. v0.5.0 · Jul 2026 · source · release history
  • Adds a three-tier GetTapFile strategy (fast/hot/recovery paths) delivering 35% faster network P50 (35.3→23.1 ms) and 41% faster P99 (86.6→51.2 ms), plus 8% higher throughput. v0.4.0 · Jun 2026 · source · release history

example

  • Restrict which host directories sandboxes may bind-mount to prevent arbitrary host path exposure in a multi-tenant cluster. # cubemaster config (yaml) host_mount: allowed_prefixes: - /data/shared/ - /data/project-a/ # '/' is explicitly forbidden and will be rejected at admission v0.5.1 · Jul 2026 · source
Developer SDKs and Programmatic Access 2 capabilities Go, Python, and Node.js/TypeScript SDKs let developers interact with the sandbox platform programmatically without calling the API directly. The SDK surface covers sandbox creation options, timeout control, and in-sandbox RPC operations.
Go and Python SDK shipped Interact with the sandbox platform from Go or Python code, including sandbox creation options, timeout control, and envd RPC operations. 19 releases · 1 other source · first seen Apr 2026

Also counts toward: Python scripting support, Scripting API, Scripting language support, Client SDKs

release 19 total

  • Adds timeout parameter to sandbox.connect to control connection deadlines (#1352).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v0.7.2 · Sep 2026 · source · release history
  • Adds timeout parameter to the sandbox.connect RPC method v0.7.2 · Sep 2026 · source · release history
  • Enables the Python SDK run_code (E2B-compatible code-interpreter interface) to read environment variables injected at sandbox creation (#1323). v0.7.2 · Sep 2026 · source · release history
  • Adds Files.ForUser in the Go SDK to isolate file access by user identity v0.7.0 · Aug 2026 · source · release history
  • Adds Files.ForUser to the Go SDK to isolate file access by user identity. v0.7.0 · Aug 2026 · source · release history
  • Adds Sandbox.create(distribution_scope=...) to the Python SDK to explicitly specify the nodes/zones a sandbox can be placed on. v0.7.0 · Aug 2026 · source · release history

example

  • Set a hard deadline on a sandbox connection so a hung connect attempt does not block automation pipelines indefinitely. sandbox.connect(timeout=10) v0.7.2 · Sep 2026 · source
Node.js / TypeScript SDK shipped Interact with the sandbox platform from Node.js or TypeScript via a preview SDK aligned with the Python and Go surface. 5 releases · first seen Jul 2026

Also counts toward: Client SDKs

release

  • Adds Sandbox.setTimeout(timeout) to the Node SDK with support for NEVER_TIMEOUT. v0.7.0 · Aug 2026 · source · release history
  • Adds Sandbox.setTimeout(timeout) with NEVER_TIMEOUT support in the Node SDK v0.7.0 · Aug 2026 · source · release history
  • Adds Volume CRUD and volumeMounts to the Go and Node SDKs, bringing all three languages to parity with Python. v0.7.0 · Aug 2026 · source · release history
  • Adds Node.js / TypeScript SDK (@cubesandbox/sdk) as a preview, aligned with the Python and Go SDK surface. v0.5.1 · Jul 2026 · source · release history
  • Adds Node.js / TypeScript SDK preview (@cubesandbox/sdk) aligned with the Python and Go surface. v0.5.1 · Jul 2026 · source · release history
Deployment, Infrastructure, and Storage 5 capabilities CubeSandbox can be deployed on Kubernetes, TKE, or k3s via Helm with rolling and canary upgrade support, and uses PostgreSQL as its metadata store. Storage is extensible through a volume plugin framework, and pre-built multi-arch proxy images and controlled schema migration reduce operational complexity.
Volume framework verified Extend sandbox storage with custom backends via Binary or RPC plugins that implement Create, Destroy, Attach, and Detach lifecycle hooks. 11 releases · 1 other source · first seen Jul 2026

Also counts toward: Command-line interface, Plugin API support, Plugin system

release 11 total

  • Adds JuiceFS storage plugin so sandboxes can mount a JuiceFS filesystem as a persistent volume with full POSIX semantics. v0.7.2 · Sep 2026 · source · release history
  • Adds JuiceFS storage plugin for mounting persistent volumes with POSIX semantics v0.7.2 · Sep 2026 · source · release history
  • Adds whole-object local S3 cache for cross-node restore reads so repeated reads and re-imports of the same snapshot hit the local cache instead of S3. v0.7.2 · Sep 2026 · source · release history
  • Enables same-bucket cross-node snapshot restore via object-storage server-side copy, adding snapshot cancellation and improved delayed-delete reclamation. v0.7.1 · Sep 2026 · source · release history
  • Nodes that were using the S3 backend without an explicit setting must set [cow.s3] enable = true (or ONE_CLICK_ENABLE_S3LVOL=1) after upgrading, or the S3 volume will be disabled. v0.7.1 · Sep 2026 · source · release history
  • S3 support is disabled by default in the new release; nodes that previously used S3 without an explicit setting must enable cow.s3.enable = true after upgrading v0.7.1 · Sep 2026 · source · release history

command line

PostgreSQL metadata backend shipped Use PostgreSQL as the CubeMaster metadata store in place of the default backend. 2 releases · 1 other source · first seen Jul 2026

release

  • Adds PostgreSQL support in the CubeMaster DAO layer for metadata storage v0.6.0 · Jul 2026 · source · release history
  • CubeMaster DAO layer now supports PostgreSQL as a metadata backend. v0.6.0 · Jul 2026 · source · release history

example

  • Connect the one-click installer to a self-managed PostgreSQL database instance. export CUBE_DATABASE_DRIVER=postgresql one-click-deploy.sh --mode install v0.7.1 · Sep 2026 · source
Controlled database schema migration shipped Suppress automatic database schema migration at startup via an environment variable to support controlled upgrade workflows. 3 releases · first seen Jun 2026

release

  • New CUBE_AUTO_MIGRATION environment variable allows skipping automatic DB schema migration at startup for controlled upgrade workflows. v0.6.0 · Jul 2026 · source · release history
  • Adds CUBE_AUTO_MIGRATION environment variable to skip automatic database migration at startup v0.6.0 · Jul 2026 · source · release history
  • Adds centralized database schema migration via goose in CubeMaster for versioned, automated schema management. v0.3.0 · Jun 2026 · source · release history
Kubernetes and Helm-based deployment shipped Deploy the CubeSandbox control plane and compute nodes on Kubernetes or k3s via Helm, with rolling upgrade and canary release support. 2 releases · first seen Jul 2026

Also counts toward: Kubernetes-native deployment

release

  • Adds Helm Chart-based Kubernetes deployment for the control plane and compute nodes on TKE, standard Kubernetes, or k3s v0.6.0 · Jul 2026 · source · release history
  • Deploy CubeSandbox control-plane and compute nodes on TKE, standard Kubernetes, or k3s via Helm Chart, with support for rolling upgrades and canary releases. v0.6.0 · Jul 2026 · source · release history
Pre-built multi-arch CubeProxy images shipped Pull pre-built multi-architecture CubeProxy images from a registry, with local-cache fallback for air-gapped environments. 1 release · 1 other source · first seen Jul 2026

Also counts toward: Air-gapped deployment, Offline mode

release

  • Publishes pre-built multi-arch CubeProxy images to TCR with MIRROR=cn|int selection and airgap local-cache fallback, eliminating on-host builds. v0.5.1 · Jul 2026 · source · release history

example

  • Pull the pre-built multi-arch CubeProxy image using the mainland China mirror instead of building on-host, suitable for airgap or low-bandwidth environments. MIRROR=cn bash one-click-install.sh v0.5.1 · Jul 2026 · source
Other 22 capabilities
Deployment and Configuration Flexibility shipped Support custom network CIDRs, external MySQL/Redis backends, ARM64 bare-metal deployment, and one-click upgrades with configuration merging. 17 releases · 5 other sources · first seen Apr 2026

Also counts toward: Command-line interface, Self-hosted deployment

release 17 total

  • Deployment config key CUBE_DATABASE_DRIVER allows connecting one-click deployments to self-managed MySQL or PostgreSQL instead of embedded DB v0.7.1 · Sep 2026 · source · release history
  • Enables CUBE_DATABASE_DRIVER to select MySQL or PostgreSQL and connect one-click deployments to a self-managed database instance.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v0.7.1 · Sep 2026 · source · release history
  • Adds configurable log rotation policy for Cubelet via the configuration file. v0.7.0 · Aug 2026 · source · release history
  • Allows configuring cubelet's log rotation policy via its configuration file v0.7.0 · Aug 2026 · source · release history
  • Derives CubeEgress transparent-proxy IP from CUBE_SANDBOX_NETWORK_CIDR instead of hard-coding 192.168.0.1, supporting custom sandbox networks. v0.5.1 · Jul 2026 · source · release history
  • New one-click upgrade mode (install.sh --mode=upgrade) performs three-way .env config merge, fail-fast preflight checks, and backs up configuration before any destructive change. v0.5.0 · Jul 2026 · source · release history

example

  • Opt the S3 backend back in after upgrading a node that previously relied on it without an explicit config. [cow.s3] enable = true v0.7.1 · Sep 2026 · source
  • Isolate logical Redis databases per cluster when multiple CubeSandbox clusters share one Redis instance. redis: db: 2 v0.7.1 · Sep 2026 · source
  • Use the one-click upgrade mode to safely migrate an existing installation to v0.5.0 with config preserved. bash install.sh --mode=upgrade v0.5.0 · Jul 2026 · source
  • Skip the CIDR conflict check when deploying in an advanced network topology where overlaps are intentional. CUBE_SANDBOX_NETWORK_CIDR=192.168.100.0/24 CUBE_SANDBOX_NETWORK_CIDR_SKIP_CONFLICT_CHECK=1 bash one-click-install.sh v0.3.1 · Jun 2026 · source
  • Override MySQL and Redis ports for a non-default deployment without hand-editing cubemaster.yaml. # In your .env file, set the desired ports before running install.sh: CUBE_SANDBOX_MYSQL_PORT=3307 CUBE_SANDBOX_REDIS_PORT=6380 bash install.sh v0.2.2 · May 2026 · source
Advanced Network Isolation and Routing shipped Enforce kernel-level inter-sandbox network isolation, fine-grained egress filtering, flexible outbound routing via dummy devices or direct transport, and traffic access tokens. 14 releases · 2 other sources · first seen Apr 2026

release 14 total

  • Adds cubeNode.network.mtu config key to pin guest MTU when node uplink NIC MTU cannot be auto-detected (#1674). v0.7.2 · Sep 2026 · source · release history
  • Supports dynamically updating network policies for running sandboxes. v0.7.0 · Aug 2026 · source · release history
  • Adds support for CubeEgress L7 forwarding rules with custom ports. v0.7.0 · Aug 2026 · source · release history
  • Adds CubeVS MAC address learning within the same subnet to avoid black-holed traffic in non-hairpin networks. v0.7.0 · Aug 2026 · source · release history
  • Adds support for dynamically updating network policies for running sandboxes v0.7.0 · Aug 2026 · source · release history
  • Merges NetworkAgent fully into Cubelet, reducing inter-process RPC calls during sandbox creation and preventing network rules from leaking across sandboxes. v0.7.0 · Aug 2026 · source · release history

example

  • Pin guest MTU to match a constrained overlay CNI uplink so sandbox networking is not silently broken on deployment. cubeNode: network: mtu: 1450 v0.7.2 · Sep 2026 · source
  • Lock down a sandbox so only callers presenting the issued traffic_access_token can reach it inbound. curl -X POST https://<cube-api>/cube/sandbox \ -H 'Content-Type: application/json' \ -d '{"network": {"allow_public_traffic": false}}' # Response includes traffic_access_token; pass it on subsequent… v0.5.0 · Jul 2026 · source
Snapshot and Rollback Mechanisms shipped Enable creation, cloning, and rollback of sandboxes using CoW snapshot pooling, reflink-based volume snapshots, and soft-dirty incremental memory snapshots. 8 releases · first seen Apr 2026

Also counts toward: Python scripting support, Scripting API, Scripting language support, Client SDKs

release 8 total

  • One-click deployment config key ONE_CLICK_ENABLE_S3LVOL=1 enables the new S3 backend for cross-node pause/resume and snapshots v0.7.1 · Sep 2026 · source · release history
  • Allows deleting a still-referenced snapshot immediately, with underlying storage reclaimed after the last reference is released. v0.7.1 · Sep 2026 · source · release history
  • Adds [cow.s3] enable = true config key (or ONE_CLICK_ENABLE_S3LVOL=1 env var) to opt in to the CubeS3lvol S3 backend for cross-node pause/resume and snapshots; disabled by default. v0.7.1 · Sep 2026 · source · release history
  • Adds snapshot support (snapshot, restore, rollback, and clone) for sandboxes with Host Mount and Volume Plugin external mounts. v0.7.1 · Sep 2026 · source · release history
  • Introduces cross-node pause/resume and snapshot cloning with an S3 backend (preview), backed by the new CubeS3lvol COW engine for remote snapshot storage on S3 object storage. v0.7.0 · Aug 2026 · source · release history
  • Adds official Python SDK (cubesandbox v0.1.0) with full sandbox lifecycle methods (create, connect, pause, kill, list, health), streaming code execution via run_code(), and filesystem access via files.read(). v0.2.1 · May 2026 · source · release history
MicroVM snapshot cloning and rollback shipped Create, clone, and roll back sandboxes using memory copy-on-write snapshot pooling, enabling sub-60ms cold starts and high-concurrency execution with minimal per-sandbox memory overhead. 3 releases · 4 other sources · first seen Apr 2026

release

  • Adds snapshot creation and rollback API endpoints to AgentHub, enabling the digital assistant console to manage sandbox checkpoints. v0.3.1 · Jun 2026 · source · release history
  • Adds soft-dirty incremental memory snapshots that capture only dirty pages after the first full snapshot, dramatically reducing snapshot time and storage. v0.3.0 · Jun 2026 · source · release history
  • Supports sub-60ms cold starts via resource pool pre-provisioning and snapshot cloning technology. v0.1.0 · Apr 2026 · source · release history

docs

  • Skip to content Cube Sandbox Empowering your AI Agents. 极速启动、高并发、安全且轻量化的 AI Agent 沙箱服务 快速开始 CubeSandbox 基于 RustVMM 与 KVM 内核构建 Apache-2.0 开源协议 CNCF Landscape 项目 E2B SDK 兼容 专为 AI Agent 构建的下一代虚拟化沙箱底座 从内核级 MicroVM 硬件隔离到百毫秒级内存写时复制分叉,以确定性安全与极低资源开销支撑海量自主智能体并发执行。 < 60ms 极速冷启动 快照池化克隆,跳过内核引导耗时 < 5MB 单沙箱内存底噪 内存写时复制共享,单机数千并发 1:1… docs update · Oct 2026 · source
  • Skip to content Cube Sandbox Empowering your AI Agents. Instant, Concurrent, Secure & Lightweight Sandbox Service for AI Agents Quick Start CubeSandbox Engineered with RustVMM & KVM Apache-2.0 License CNCF Landscape E2B SDK Compatible Next-Gen Virtualized Sandbox Infrastructure for AI Agents From hardware-isolated… docs update · Oct 2026 · source
  • Hardware-isolated MicroVM sandbox service built on RustVMM and KVM, providing sub-60ms startup and E2B-compatible API for AI agent code execution.

example

  • Use the AgentHub snapshot timeline to create a visual checkpoint and roll back an AI agent sandbox to a known-good state. In the AgentHub console, open the target assistant → Snapshot Timeline → Create Checkpoint, then select a prior checkpoint and click Rollback. v0.3.0 · Jun 2026 · source
Web Management Console shipped Provide a browser-accessible dashboard for cluster, node, sandbox, and template management, backed by new API endpoints. 6 releases · 1 other source · first seen May 2026

Also counts toward: REST API, Web management console

release

  • Adds node isolation/unisolation and node operation history viewing to the Web UI. v0.7.0 · Aug 2026 · source · release history
  • Decouples Web Console logic into a standalone CubeOps service separate from CubeAPI v0.6.0 · Jul 2026 · source · release history
  • Adds standardized build-time version metadata injection (version, commit, build time) to all Go and Rust binaries via ldflags/build.rs, plus a machine-readable release-manifest.json in release bundles. v0.4.0 · Jun 2026 · source · release history
  • Adds a node component version matrix that gives operators cluster-wide visibility of component versions (guest-image, cube-agent, kernel, control-plane) with version-skew surfacing via CubeAPI and a new Web UI Versions page. v0.4.0 · Jun 2026 · source · release history
  • Adds browser-accessible Web UI management dashboard for sandboxes, templates, and cluster nodes — including a template store for deploying pre-built images. v0.3.0 · Jun 2026 · source · release history
  • New Web Management Console (Dashboard) with cluster overview, node/sandbox status, template management, and API key management, backed by new CubeAPI web endpoints. v0.2.0 · May 2026 · source · release history

example

  • Access the new Dashboard to monitor sandbox/node status and manage API keys without touching the CLI. In the CubeAPI web UI, navigate to the Dashboard to view cluster overview, manage templates, and configure API keys under the API Key Management section. v0.2.0 · May 2026 · source
Template Build Optimizations shipped Improve template image building performance and resource efficiency via daemonless pipelines, loop-mount streaming, and disk-space safety margins. 5 releases · 1 other source · first seen May 2026

release

  • Adds pure-Go native rootfs export pipeline that bypasses Docker, skopeo, and umoci entirely. v0.5.0 · Jul 2026 · source · release history
  • Adds a daemonless template image build pipeline using skopeo/umoci, reducing peak disk usage by 72% (from ~4.2× to ~1.2× image size), with fallback to Docker for backward compatibility. v0.4.0 · Jun 2026 · source · release history
  • Adds CUBEMASTER_LOOP_MOUNT_EXT4_ENABLED flag (default false) to enable a loop-mount streaming ext4 build phase with CAP_SYS_ADMIN detection. v0.4.0 · Jun 2026 · source · release history
  • Adds CUBEMASTER_DISK_SPACE_SAFETY_MARGIN configurable safety margin for a fail-fast disk-space pre-check before template image builds. v0.4.0 · Jun 2026 · source · release history
  • Adds GitHub ARC (Actions Runner Controller) support for kernel and package build workflows. v0.2.1 · May 2026 · source · release history

example

  • Set a conservative disk-space safety margin so template image builds fail fast when the store directory is nearly full. CUBEMASTER_DISK_SPACE_SAFETY_MARGIN=2.0 cubemaster serve v0.4.0 · Jun 2026 · source
Advanced S3 Volume Backing shipped Use S3-compatible storage for volume snapshots and cross-node resume with local caching and server-side copy optimizations. 3 releases · 1 other source · first seen Aug 2026

release

  • Adds CubeS3lvol support on Kubernetes for cross-node pause/resume and snapshots in K8s deployments. v0.7.1 · Sep 2026 · source · release history
  • Deploys MinIO by default as the S3 backend for the volume feature and cross-node pause/resume, with the option to specify a custom S3 backend. v0.7.0 · Aug 2026 · source · release history
  • Enables creating sandboxes from snapshots with an S3 backend for cross-node pause/resume v0.7.0 · Aug 2026 · source · release history

example

  • Enable S3-backed persistent storage for sandbox snapshots and cross-node pause/resume in one-click deployments. export ONE_CLICK_ENABLE_S3LVOL=1 one-click-deploy.sh --mode install v0.7.1 · Sep 2026 · source
CLI Connection and Versioning Configuration verified Allows CLI clients to specify control-plane base URLs and restrict output to semantic version strings only. 4 other sources · first seen Sep 2026

Also counts toward: Command-line interface

command line

AgentHub Console and AI Agent Support with Sandbox Management shipped Provide a digital assistant console with snapshot timelines, visual checkpoints, rollback, parallel clone environments, template actions, and notification configuration. 4 releases · first seen May 2026

previously: AgentHub Console and AI Agent Support

Also counts toward: REST API, Web management console

release

  • New preview button and sandbox open logic in the AgentHub WebUI, with template store defaults corrected. v0.3.1 · Jun 2026 · source · release history
  • Adds snapshot creation and rollback API endpoints to AgentHub, enabling the digital assistant console to manage sandbox checkpoints. v0.3.1 · Jun 2026 · source · release history
  • Adds AgentHub digital assistant console (Preview) with snapshot timelines, visual checkpoint creation and rollback, parallel clone environments, template actions, and WeCom notification configuration. v0.3.0 · Jun 2026 · source · release history
  • Documents network port allocation ranges (10000–19999, 20000–29999, 30000–65535) in docs/architecture/network.md (EN & ZH). v0.2.2 · May 2026 · source · release history
Cluster node monitoring and lifecycle management shipped Enables cluster operators to report node resource usage, expose Prometheus metrics for real-time scheduling visibility, and delete nodes from the cluster to exclude them from future scheduling. 3 releases · first seen Jun 2026

release

  • Adds node deletion support so a node can be removed from the cluster and excluded from scheduling. v0.7.0 · Aug 2026 · source · release history
  • Adds node resource reporting (CPU, memory, disk) from Cubelet to CubeMaster for cluster-wide resource awareness. v0.3.0 · Jun 2026 · source · release history
  • Adds Prometheus scheduler metrics exposed as gauges on /v1/metrics via Cubelet for real-time monitoring. v0.3.0 · Jun 2026 · source · release history
PVM Deployment Mode shipped Enable running CubeSandbox on ordinary cloud servers via Pagetable-based Virtual Machine deployment mode without bare-metal or nested virtualization. 2 releases · 1 other source · first seen May 2026

release

  • Adds PVM consistency pre-check: when kvm_pvm is loaded, the installer verifies CUBE_PVM_ENABLE=1 is set, preventing silent installation of the wrong guest kernel. v0.3.1 · Jun 2026 · source · release history
  • New PVM (Pagetable-based Virtual Machine) deployment mode lets ordinary cloud servers run CubeSandbox without bare-metal or nested virtualization. v0.2.0 · May 2026 · source · release history

example

  • Skip the PVM pre-check when you have kvm_pvm loaded but need to override the installer's enforcement (e.g., controlled migration scenario). ONE_CLICK_SKIP_PVM_CHECK=1 bash one-click-install.sh v0.3.1 · Jun 2026 · source
ARM architecture support shipped Run CubeSandbox on ARM hardware in addition to x86, as introduced in the v0.5.0 release. 1 release · 1 other source · first seen Jul 2026

Also counts toward: CI/CD pipeline integration

release

  • Adds native ARM64 (aarch64) support across the full stack: hypervisor (MMIO SysCtrl device), guest agent, CubeShim, CubeNet BPF, multi-arch Docker images, and CI/CD with per-architecture release artifacts. v0.5.0 · Jul 2026 · source · release history

docs

  • Cube v0.5.0: Auto-Pause, ARM Support, One-Click Cluster Deploy — Taking Sandboxes to Production If Cube Sandbox v0.3.0 solved fast (millisecond snapshot / clone / rollback), and v0.4.0 solved governance (L7 egress control + observability + cluster consistency), then v0.5.0 aims to solve — "stable, efficient,… docs update · Oct 2026 · source
Host-Network Mode shipped Run compute node pods on the host network to preserve sandbox namespaces across restarts. 2 releases · first seen Sep 2026

release

  • cube-node Pods now run on the host network by default; upgrading an existing cluster requires draining compute nodes and explicit confirmation (hostNetworkChangeAck). v0.7.2 · Sep 2026 · source · release history
  • Changes cube-node Pod default to run on the host network via hostNetwork: true in K8s deployments v0.7.2 · Sep 2026 · source · release history
Cluster Component Isolation shipped Deploy independent control-plane services for lifecycle management and template handling to allow horizontal scaling. 2 releases · first seen Jul 2026

release

  • Introduces standalone CubeTemplateCenter service that splits template build, delete, and reclaim out of CubeMaster into an independently scalable multi-replica service, persisting build artifacts to S3/MinIO (AWS S3-compatible storage). v0.7.1 · Sep 2026 · source · release history
  • Introduces cube-lifecycle-manager (CLM), a standalone control-plane service extracted from the CubeProxy sidecar, enabling CubeProxy to scale horizontally with Redis-based replica discovery. v0.5.1 · Jul 2026 · source · release history
Container Log Forwarding and Access shipped Stream container stdout/stderr from the agent to host-side log files via vsock, with CLI access for reading logs. 1 release · 1 other source · first seen Jun 2026

Also counts toward: Command-line interface

release

  • Adds cubecli cubebox logs subcommand to read container stdout/stderr from outside the sandbox, with --tail N, --head N, --all, and --stderr flags. v0.4.0 · Jun 2026 · source · release history

example

  • Read the last 100 lines of a sandboxed container's stderr from outside the sandbox for rapid incident triage. cubecli cubebox logs --tail 100 --stderr <id> v0.4.0 · Jun 2026 · source
Automatic Guest Memory Reclamation shipped Automatically returns idle guest memory to the host to increase the number of sandboxes a single compute node can host. 1 release · first seen Sep 2026

release

  • Adds automatic reclaim of idle guest memory back to the host, allowing a single node to host more sandboxes. v0.7.2 · Sep 2026 · source · release history
Flexible Artifact and Component Storage shipped Extends storage backends for component repositories and template artifacts to support S3, local disk, PVC, and NFS. 1 release · first seen Sep 2026

release

  • Extends component repository and template artifact storage to support S3, local disk, PVC, and NFS backends (#1749). v0.7.2 · Sep 2026 · source · release history
Active/Standby Disaster Recovery shipped Provides active-standby failover capability for the lifecycle management service to maintain cluster continuity during service outages. 1 release · first seen Sep 2026

Also counts toward: Disaster recovery

release

  • Supports active/standby disaster recovery for the lifecycle management service (CLM). v0.7.1 · Sep 2026 · source · release history
Artifact Release Structuring shipped Publish kernel and guest images as separate versioned artifacts for independent management. 1 release · first seen Aug 2026

release

  • Publishes kernel and guest images as separate artifacts under dedicated kernel-release-* and guest-image-* releases. v0.7.0 · Aug 2026 · source · release history
Sandbox Placement Control shipped Pin specific sandboxes to designated availability zones or nodes for compliance and multi-region requirements. 1 other source · first seen Aug 2026

example

  • Pin a Python SDK sandbox to a specific zone or set of nodes to control placement in multi-region or compliance-sensitive deployments. sandbox = Sandbox.create(distribution_scope='zone-us-east-1') v0.7.0 · Aug 2026 · source
Multi-cloud Infrastructure Provisioning shipped Provision full cyber tooling clusters including VPC, databases, and storage via cloud-specific Terraform deployers. 1 release · first seen Jul 2026

release

  • New TencentCloud Terraform cluster deployer (deploy/one-click/terraform/tencentcloud/) provisions a full CubeSandbox cluster — VPC, NAT, TKE, MySQL, Redis, CFS, TCR — from a single create.sh entry point. v0.5.0 · Jul 2026 · source · release history
Performance benchmarking documented Measure and report cold-start latency and concurrency throughput for sandbox core operations. 1 other source

docs

  • CubeSandbox Core Operations Performance Benchmark Report 1. Overview CubeSandbox is designed for AI Agent code execution, where ultra-fast cold-start and high concurrency are the two most critical metrics. seen Oct 2026 · source

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for CubeSandbox, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail CubeSandbox puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Website history

cubesandbox.com, every change

Tencent Cloud's 2 pages as they looked each month from October 2026 to October 2026: 2 renders, 0 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

Show

17 entries

  1. October 20263
  2. September 20262
  3. August 20261
  4. July 20263
  5. June 20263
  6. May 20263
  7. April 20262
    Show

    17 entries

    Project health

    Issue, contributor and maintainer activity in TencentCloud/CubeSandbox, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 120 +120 vs prior 12 months
    2. Maintainers 16 +18 joined · −2 left, last 12 months
    3. Bus factor 4 committers behind half the commits
    4. Community-filed 78% of issues opened, last 12 months
    5. Median time to close 12 days first maintainer reply 23 hours
    6. Open backlog 65 of 419 issues ever filed
    1. Issues opened / month 22 · 14 communitymaintainers
    2. Open backlog 65
    3. Contributors / month 40
    4. Commits / month 136
    5. Stars 12,590
    Issue themes, last 12 months
    • bugs 57%
    • features 20%
    • questions 7%
    • docs 1%
    • other 15%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →