docker/sandbox-kit-spec

Docker Sandbox Kit Specification v3 - the kit descriptor grammar, the OCI artifact, the build frontend, and the conformance suites

Owned by Docker

View on GitHub ↗Jump to charts ↓Open shareable report →

docker/sandbox-kit-spec has 150+ stars and 20+ forks on GitHub, is written in Go, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 20 minutes ago
Added to GitGenius on October 12th, 2026
Created on September 16th, 2026
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 21
Total Stargazers: 154 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.5 hours
Mean response time: 19.4 hours
90th percentile: 2.8 days
Tracked items: 18

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 4
Closed in 7 days: 2
Avg open age: 6 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 4
Closed in 7 days: 1
Comments in 7 days: 2
Events in 7 days: 3

Top labels

  • specification (10)
  • bug (3)
  • enhancement (2)
  • documentation (1)
  • investigation (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Docker Sandbox Kit Specification is a specification for describing the runtime environment, capabilities, and authority model of containerized agents and workloads beyond what a Dockerfile can express.

The specification addresses the problem that Dockerfiles describe only the contents of a container image, leaving the runtime environment, network access, credential grants, and external dependencies to be managed separately through docker run flags, compose files, CI configs, and documentation. This fragmentation means authority decisions—what resources an agent can access—remain unversioned and unreviewable. The Kit specification brings these concerns into a single, versioned artifact by defining a descriptor grammar that captures both the content and the authority an agent requires, making those decisions diffable and reviewable as part of the image itself rather than scattered across deployment configurations.

The specification is most relevant for teams deploying agents and autonomous workloads that need explicit, auditable control over what resources and capabilities they can access. It suits projects where authority decisions are material to security and compliance, and where reproducibility of those decisions across different deployment environments matters. The approach is particularly valuable when agent versions introduce new capability requirements—those changes surface as diffs in the Kit descriptor rather than hidden in updated deployment scripts or documentation.

The project maintains a BuildKit frontend for building Kits and conformance suites for validating both published Kits and runtimes claiming to support them. Development activity shows consistent engagement with the specification itself, with updates to the descriptor grammar and the conformance test suites. The project includes tooling across multiple concerns—the grammar definition, OCI artifact handling, and build integration—indicating active work to make the specification practically usable rather than theoretical.