Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who let a coding agent execute generated code and want a real kernel-enforced boundary around it; for CI and build steps that need container semantics without a daemon or Docker Desktop; for anyone on WSL2 or an ARM board where a full container stack is too heavy.
Where this stands now
kern — rootless 1.52 MB container runtime that starts a real OCI sandbox in about 3.5 ms with no daemon ranks #223 of 3231 tracked Radar items by composite score (8.4 against a section median of 4.9). The section currently carries 2115 Bronze, 645 Gold, 471 Silver. Signal extremes versus the section: momentum at the 76th percentile; novelty at the 85th percentile.
Who should use it
Who should skip it
Move on from kern — rootless 1.52 MB container runtime that starts a real OCI sandbox in about 3.5 ms with no daemon if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
kern — rootless 1.52 MB container runtime that starts a real OCI sandbox in about 3.5 ms with no daemon is tracked by RepoRadar as a developer tool in the Radar section. First seen —; the source record was last checked on 2026-09-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for kern — rootless 1.52 MB container runtime that starts a real OCI sandbox in about 3.5 ms with no daemon are workflow potential (9.9) and maturity (9.1), 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 kern — rootless 1.52 MB container runtime that starts a real OCI sandbox in about 3.5 ms with no daemon record combines a 8.4/10 composite score with separate popularity (100.0), risk (conditional), 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
Isolation is built on an unprivileged Linux user namespace, a well-known source of kernel privilege-escalation bugs. The maintainers state this in SECURITY.md before any claim: a kernel LPE bug is an escape; This is not a hypervisor. It is documented as suitable for code you chose to run and own the blast radius of (agent tool-calls, CI jobs, build steps), and explicitly not for hostile code from strangers on a multi-tenant kernel. Use gVisor or Firecracker for that case; A bind mount is a trust decision you make, not a boundary kern enforces: -v $HOME:/host hands the box your home directory, and --net host and --privileged are opt-outs by name; The quickstart install is curl … | sh. The script verifies a SHA256 before installing and a manual two-line checksum path is documented, but read it first if a piped installer is against your policy; cargo install --git … --locked is the alternative.