Skip to content
KitploitKITPLOIT
工具漏洞利用博客
Log in
提交
工具漏洞利用博客
提交

黑客、渗透测试和网络安全工具,武装您的安全武器库!

Kitploit 是一个黑客、网络安全和渗透测试工具的目录。发现最新的项目更新,查找漏洞、分析系统、自动化测试并加强你的安全。

订阅源联系隐私© 2026 Kitploit

工具目录

分类

查看所有分类
Loading categories
工具/GitHubGitHub/getkern/kern
Cloud Infrastructure SecurityContainer SecurityDynamic Analysis (Sandboxing)Security VirtualizationDevSecOpsAI Security
GitHubgetkern/kern

kern

Rootless container runtime and sandbox that launches kernel-enforced OCI images in milliseconds with no daemon, featuring resource profiles, seccomp allowlists, and compose support for untrusted and AI-generated code.

查看仓库
4911212013小时35分前Kitploit 审核通过
分享
网站
内容在请求的语言中不可用。显示英文版本。
kern

CI License: Apache-2.0 Release PyPI npm Runs on

kern: fast, rootless container runtime and sandbox with no daemon and full NVIDIA GPU support. Runs untrusted code and AI agent tool calls under kernel-enforced isolation.

A real, kernel-enforced container in a few milliseconds, out of one static binary with no daemon.

MCP support for Claude Code, Cursor, Claude Desktop and LM Studio, through Kern Sandbox.

Two windows. Container: kern box dev --image alpine -it -- sh; kern compose up -d, for your compose.yaml; kern ps. Sandbox: import kern_sandbox as kern; r = kern.run_code("print(6 * 7)"); print(r.stdout) prints 42. kern top, recorded live on one machine: the Boxes tab with a GPU box, a dev box, a worker and a compose stack (app and postgres, healthy); the Sandboxes tab with SDK calls running and finishing, ok, exit codes and runs on the GPU; the Logs tab with every box's output in one stream.

0 RAM at rest · no daemon, no socket, nothing to start · one static binary, libc its only Rust dependency

# Linux and macOS. Windows below.
curl -fsSL https://raw.githubusercontent.com/getkern/kern/main/install.sh | sh

What kern is

A rootless container runtime in one static binary, with no daemon. The same binary is the sandbox an agent's code runs in, called from Python, Node or any MCP client. kern calls a container a box.

  • Real OCI images: pull, build, commit, push, save/load. A box starts in single-digit milliseconds.
  • A sandbox for code your AI agent or LLM wrote. It runs where it can't reach your files unless you hand them over, with no network unless you ask.
  • No daemon, and root is never required. Six namespaces, a read-only or overlay root, a seccomp allowlist by default, cgroup v2 limits.
  • Your docker-compose.yml, unchanged, or kern's own stack.toml.
  • Full NVIDIA GPU support: --gpus all, --gpus 2, --gpus device=0,1, and compose's deploy.resources.reservations.devices, on Linux and WSL2.
  • Limits without a sandbox. kern run puts the same caps on a plain process on the host. docs/RESOURCES.md
  • The tools you expect: ps, logs, exec, stats, inspect, top, doctor.

Install

Linux, x86_64 or aarch64
curl -fsSL https://raw.githubusercontent.com/getkern/kern/main/install.sh | sh
Windows, through WSL2
irm https://raw.githubusercontent.com/getkern/kern/main/install.ps1 | iex
macOS, in a Linux VM
curl -fsSL https://raw.githubusercontent.com/getkern/kern/main/install.sh | sh

On macOS kern runs in a small Lima VM, created automatically, with no Docker inside; kern on the Mac runs it there, in the current directory. Kern Sandbox goes in the VM, with the code that calls it: limactl shell kern, then pip install kern-sandbox there.

Then kern doctor checks the host and says what to fix. Ubuntu 23.10 and newer need one root step first: docs/INSTALL.md.

Quickstart

What it doesCommand
A shell in a real OCI imagekern box dev --image alpine -it -- sh
A service, published on the hostkern box svc --image nginx:alpine -d -p 8080:80
Untrusted code, with the strict profilekern box job --image python:3.12-slim --security-profile untrusted -- python3 -c "print('hi')"
What is running (--json too)kern ps

--security-profile untrusted is the seccomp allowlist, --cap-drop ALL and --read-only in one flag. examples/ holds 96 runnable scripts, one per thing kern does.

Kern Sandbox: run an agent's code from Python or Node

In a terminal:

python3 -m venv .venv && . .venv/bin/activate
pip install -U kern-sandbox

Then in a Python file:

import kern_sandbox as kern

r = kern.run_code("print(sum(range(100)))")
print(r.stdout, r.fault)   # 4950  None

Your code runs in a container of its own, for one call or for a whole session, and a timeout or an out-of-memory comes back as a typed fault. On Linux, pip brings kern with it, and so does npm install kern-sandbox for Node.

On a GPU. gpus="all" (or "2", or "device=0,1") hands the sandbox NVIDIA cards, with the host's driver:

r = kern.run_code(
    "import ctypes; cuda = ctypes.CDLL('libcuda.so.1'); n = ctypes.c_int()\n"
    "cuda.cuInit(0); cuda.cuDeviceGetCount(ctypes.byref(n)); print(n.value)",
    gpus="all",
)
print(r.stdout)   # 2, on a host with two NVIDIA cards

The same from a terminal:

kern box --rm --gpus all --image nvidia/cuda:12.9.0-base-ubuntu24.04 -- nvidia-smi -L
Three windows. files.py: a Sandbox writes in.csv, runs a job, reads out.txt back. state.py: a kernel keeps x = 40 between calls and prints x + 2. package.py: a Sandbox with setup pip install numpy imports numpy.

These three and three more, ready to copy: the Python SDK, the same for Node.

MCP server for Claude Code, Cursor, Claude Desktop and LM Studio. The same block goes in claude_desktop_config.json, in Cursor's or LM Studio's mcp.json, or in .mcp.json at your project root for Claude Code:

{
  "mcpServers": {
    "kern": { "command": "uvx", "args": ["--from", "kern-sandbox", "kern-mcp"] }
  }
}

Every option: docs/MCP.md.

Run a whole stack: your docker-compose.yml, unchanged

# stack.toml - one table per service, keys spelled like the `kern box` flags
[box.cache]
image = "redis:7-alpine"

[box.web]
image      = "nginx:alpine"
ports      = ["8080:80"]
depends_on = ["cache"]
kern compose stack.toml up            # start it (or point it at your compose.yaml)
kern compose stack.toml ps            # what is running, and what each service publishes
kern compose stack.toml port web 80   # the host address serving a port
下载工具

最受欢迎

查看全部 →

发现我们社区最常用的工具。

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 终极 OSINT 工具包:调查图谱、置信度评分、别名家族、地图、时间线和报告。49 个模块、400+ 个站点,无需 API 密钥。

    717
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock 一键执行应用(CVE-2026-43499)

    504
  • 3

    ARTEX

    baarai/artex

    基于LLM的多智能体自主渗透测试平台,具备规划器/执行器智能体、资产与探索图谱、MITM流量记录以及漏洞复测功能。

    402
  • 4

    redforge

    cybersecurity91/redforge

    浏览器端红队工具包,包含 102 个离线工具,用于侦察、载荷生成、凭据攻击、加密、编码和交战报告。

    342
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI原生网络安全的行动系统——在这里,意图转化为受治理的执行,证据沉淀为运营记忆,每一次操作都让下一次更出色。

    260
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259

探索所有工具

浏览我们的工具集合

查看所有工具 →