macOS
brew install fencelocal Homebrew formula metadata
brew / Rang 3514
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für fence in AI-Agent-Workflows.
Installation
brew install fencelocal Homebrew formula metadata
nix profile install nixpkgs#fencenixpkgs package indexes · pkgs/by-name/fe/fence/package.nix · Quelle: api.github.com
Überblick
Lightweight sandbox for commands with network and filesystem restrictions
Verlauf
Fence is a command sandbox and permission layer for running semi-trusted commands with default-deny network access and configurable filesystem and command rules.
The official README states that Fence moved from github.com/Use-Tusk/fence to github.com/fencesandbox/fence, with migration instructions for Homebrew tap users and Go installs. GitHub releases show an initial v0.1.0 release in December 2025 and frequent v0.1.x releases through June 2026.
The documentation positions Fence as a host-native sandbox rather than a container or VM. On macOS it uses sandbox-exec; on Linux it uses bubblewrap with Landlock and seccomp.
Fence's official README emphasizes AI coding-agent workflows and names Claude Code, Codex, Amp, Gemini CLI, GitHub Copilot, OpenCode, and Factory CLI as compatible commands. Packaging is still young, with Homebrew tap, Nix, curl installer, Go install, and source builds documented by upstream.
Basic usage wraps a command with network access blocked by default. Users can apply templates, monitor blocked requests, deny dangerous commands, configure filesystem read/write rules, and inspect the merged config with fence config show.
Fence is significant as a post-agent-era CLI package: instead of being an agent, package manager, or container runtime, it wraps arbitrary developer commands with reusable policy. That makes it relevant to package installation scripts, build scripts, CI jobs, and coding-agent sessions.
Sicherheitslage
Für fence wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Config paths the tool may read or write during local use.
./fence.jsonc./fence.json~/.config/fence/fence.jsonc~/.config/fence/fence.jsonExecutables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
fence | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Installationsmetadaten
| Paketschlüssel | brew:fence |
|---|---|
| Version | 0.1.65 |
| Paketmanager | Homebrew |
| Homepage | https://github.com/fencesandbox/fence |
| Repository | https://github.com/fencesandbox/fence |
| Zuletzt aktualisiert | 2026-08-01T03:36:54Z |
| Pulse | updated |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Source-Datenbank-Treffer
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
fence
nix profile install nixpkgs#fenceQuellspur
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
View the package source record on GitHub.