chainsaw uv

Run uv through Chainsaw — refuse malicious/typosquatted packages at install time

chainsaw uv [args...]

Run uv with an install-time supply-chain check in front of it.

Chainsaw evaluates the packages uv would install, refuses on a hit, and otherwise hands off to the real uv with your arguments untouched. Anything that is not an install verb (uv build, uv run, …) delegates immediately.

Guarded: uv add, uv sync, uv pip install, uv pip sync, uv tool install. uv sync scans the resolved lockfile, uv.lock first; -r requirements.txt scans the file.

Offline by default. The bundled checks — typosquat detection and a known-malicious floor — run entirely on your machine and send nothing. For the full OpenSSF malicious-packages feed, run the opt-in chainsaw guard update, which is the only networked step. Set CHAINSAW_OFFLINE=1 to refuse network access outright.

Fails open by default: when a signal cannot be evaluated, Chainsaw prints a visible notice and lets the install proceed, so a thin feed never breaks your build. See chainsaw guard coverage to make that fail closed instead.

Exit codes: 0 when the install proceeds (Chainsaw then returns the real tool’s own exit code), 1 when Chainsaw refuses.

--help and every other flag are forwarded to uv untouched, so chainsaw uv --help shows uv’s help, not this text. Use chainsaw help uv to see this page.

To make the check automatic, add the shell shims: eval "$(chainsaw guard init)".

Examples

chainsaw uv add requests

chainsaw uv pip install -r requirements.txt

# scans uv.lock
chainsaw uv sync

Flags

This command forwards its arguments to the underlying tool unchanged, so it parses no flags of its own. Anything after the command name goes to the wrapped package manager verbatim.