glab(1)

✨ NAME ✨

okay so bestie, you're on the glab(1) page for glab-dependency-firewall-pip — the command that runs Pip through the GitLab Dependency Firewall. It's in BETA, so handle with cute caution 🎀

🌸 SYNOPSIS 🌸

glab dependency-firewall pip  [flags]

💖 DESCRIPTION 💖

Run the Pip binary through the GitLab Dependency Firewall. This command checks each package download and upload against the policy for the current project, refuses blocked packages, and summarizes the results after the run. Very "security guard but make it package manager" energy 🫶

The command uses your package manager's registry or index configuration, and does not modify it. No cap — it leaves your config alone.

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

All arguments are forwarded to pip verbatim. Like, every single one — no remixing, no editing, just straight through.

⚠️ 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. Your little "wait what does this do again" safety blanket 💜

🌈 EXAMPLE 🌈

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

# Install from a requirements file through the Dependency Firewall
glab dependency-firewall pip install -r requirements.txt

👑 SEE ALSO 👑

• glab-dependency-firewall(1) — go peek at the parent command too, bestie 💖

---

mwah 💋 this page was auto generated by spf13/cobra, dated Nov 2026, and you're reading glab(1) — slay and stay safe out there 🧚‍♀️✨