macOS
brew install nonolocal Homebrew formula metadata
安装
brew install nonolocal Homebrew formula metadata
nix profile install nixpkgs#nononixpkgs package indexes · pkgs/by-name/no/nono/package.nix · 来源: api.github.com
概览
Capability-based sandbox shell for AI agents with OS-enforced isolation
历史
nono is a capability-based sandbox CLI and SDK project for AI agents, MCP tools, and LLM workloads. Its docs describe a secure, kernel-enforced sandbox with capability-based isolation, secure key management, rollback, and an immutable audit chain.
The GitHub repository was created on 2026-01-31. Public launch material posted on 2026-02-02 framed nono as a response to local AI coding agents running with the user's full filesystem and network permissions.
The core design uses kernel primitives instead of a container runtime: Landlock on Linux and Seatbelt on macOS. The project also exposes SDK directions beyond the CLI, with docs for a Rust core library plus Go, TypeScript, and Python integration paths.
Release activity accelerated quickly in 2026. GitHub release metadata shows v0.66.0 published on 2026-06-29, and Homebrew packaged the same stable version in its 2026-07-01 formula data.
nono is young, but it had already become unusually visible for a 2026 security CLI: the GitHub repository had thousands of stars by 2026-07-01, Homebrew reported thousands of installs across 90 and 365 day windows in its 2026-07-01 formula data, and discussion/examples focus on sandboxing AI coding agents rather than generic process confinement.
Because the project is close to the AI-agent security wave, adoption should be treated as early-stage and volatile. The reliable source-backed claim is that it had rapid package-manager and GitHub traction by mid-2026, not that it had become a mature standard.
Typical CLI usage wraps an agent or command with explicit filesystem and network capabilities: examples include `nono run --allow . -- claude`, separate `--allow` and `--write` paths, `--net-block`, and `--dry-run`. The docs and launch post also describe default protection for sensitive paths such as SSH keys, AWS credentials, and shell configs.
Package users reach for it when they want OS-enforced guardrails around an AI agent, build step, test run, or data-processing command without building a container image. The important operational model is that child processes inherit restrictions once the sandbox is applied.
nono is notable because it packages a security boundary as a normal CLI wrapper for developer workstations. For package nerds, the interesting part is not only the Rust binary but the distribution of OS-specific confinement behavior through one command: Landlock-backed Linux behavior, Seatbelt-backed macOS behavior, and formula variants that differ by platform dependencies.
安全态势
generalized runtime or code generation signal.
yellow 风险 · 中 置信度 · runtime
在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。
可执行文件
| 命令 | 类型 | 暴露范围 | 备注 |
|---|---|---|---|
nono | cli | 全局可执行文件 |
新鲜度
这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。
https://github.com/nolabs-ai/nono
安装元数据
| 软件包键 | brew:nono |
|---|---|
| 版本 | 0.69.0 |
| 软件包管理器 | Homebrew |
| 软件包管理器页面 | https://formulae.brew.sh/formula/nono |
| 主页 | https://nono.sh |
| 仓库 | https://github.com/nolabs-ai/nono |
| 上游文档 | https://nono.sh/docs/introduction |
| 许可证 | Apache-2.0 |
| 源码归档 | https://github.com/nolabs-ai/nono/archive/refs/tags/v0.69.0.tar.gz |
| 最后更新 | 2026-07-24T17:00:43Z |
| Pulse | updated |
| 构建依赖 | pkgconf, rust |
| Bottle | 可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | 未定义 |
| 服务 | 未声明 |
注册表事实
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | nono |
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
源数据库匹配
匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。
nono
nix profile install nixpkgs#nono来源线索
此页面由 av-web 从 scripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。
View the package source record on GitHub.