glab(1)

okay bestie, welcome to the glab(1) manual — it’s giving command reference, and we’re gonna make it make sense 💖✨

🎀 NAME 🎀

glab-dependency-firewall-uv — run uv through the GitLab Dependency Firewall. (BETA)

✨ SYNOPSIS ✨

glab dependency-firewall uv  [flags]

🦋 DESCRIPTION 🦋

okay so this command runs the uv binary through the GitLab Dependency Firewall. It checks every package download and upload against the policy for the current project, refuses blocked packages, and summarizes the results after the run. Iconic, honestly.

It uses your package manager's registry or index configuration, and it does not modify it.

Package names are normalized as described in PEP 503, so Flask_Login and flask-login are treated as the same package. No cap.

All arguments are forwarded to uv verbatim.

🚨 BETA ALERT: this feature is in beta and might not be ready for production use. It might be unstable, and breaking changes can occur outside of major releases. For more information, see https://docs.gitlab.com/policy/development_stages_support/.

🫶 OPTIONS INHERITED FROM PARENT COMMANDS 🫶

• -h, --help[=false] — show help for this command.

🌸 EXAMPLE 🌸

# Install a package through the Dependency Firewall
glab dependency-firewall uv pip install requests

# Sync the project environment through the Dependency Firewall
glab dependency-firewall uv sync

🔥 SEE ALSO 🔥

• glab-dependency-firewall(1) — go check out this related manual page too 💅

---

Auto generated by spf13/cobra · Nov 2026 · glab(1) — mwah, go slay your dependency downloads 💖🎀