Use case · Package installs
Screen package installs and one-shot package execution
Send package-manager installs and one-shot execution through Guard’s package firewall instead of letting them run directly.
Agents install dependencies constantly, and install commands are a supply-chain boundary. The catalog documents three package-firewall entries — Node, Python, and system packages — that route their mapped executables through Guard’s package firewall rather than an operation-by-operation rule matrix.
Evidence grade: reviewed catalog facts · Last reviewed 2026-09-12
Every step below references coverage documented in the HOL Guard extension catalog. These workflows are derived from reviewed catalog facts, not independently run or benchmarked — verify the result in your own setup before relying on it.
When this is not the right fit
Skip this workflow if
- You need per-subcommand review decisions — these entries delegate enforcement to the package firewall and document mapped executables, not an operation matrix.
- The install runs inside a container build on a machine without Guard; the firewall only sees commands that run through Guard.
Prerequisites
Before you start
- Guard is installed on the machine where package commands run.
- You know which package managers your team and agents use.
Steps
The workflow
- 1
Route Node package commands through the firewall
The Node entry routes Node package installs and one-shot execution through Guard’s package firewall for npm, npx, pnpm, yarn, bun, and bunx.
- 2
Route Python package commands through the firewall
The Python entry routes Python dependency installs and isolated package execution through the package firewall for pip, pip3, pipx, uv, uvx, poetry, and pipenv.
- 3
Route system package commands through the firewall
The system entry routes operating-system package installation requests through the package firewall for apt, apt-get, yum, dnf, apk, pacman, zypper, and brew.
Expected result
What the documented coverage should do
Package-manager install and execution requests from the mapped executables are screened by Guard’s package firewall before they run, under the workspace’s package policy.
Limitations
What this workflow does not claim
- These entries carry no reviewed operation rules in the catalog; enforcement is delegated to the package firewall.
- Package managers outside the mapped executable lists are not covered by these entries.
Coverage referenced
Extensions in this workflow
- Node package protectioncommand.package.node
- Python package protectioncommand.package.python
- System package protectioncommand.package.system