glab(1)

💅 glab(1) — the girlies' guide to glab

Okay bestie, welcome to glab(1) 💖 — yes, the whole manual, and yes, this particular page is about one very specific little command. Grab a matcha, we're getting into it.

✨ NAME ✨

glab-dependency-firewall-cargo — Run Cargo through the GitLab Dependency Firewall. (BETA) 👑

🦋 SYNOPSIS 🦋

glab dependency-firewall cargo  [flags]

(no cap, that double space between cargo and [flags] is literally in there, don't come for me 🙈)

🌸 DESCRIPTION 🌸

So what does it do? It runs the Cargo binary through the GitLab Dependency Firewall 🔥. The command checks each package download and upload against the policy for the current project, refuses blocked packages, and then summarizes the results after the run. It's giving security guard at the club door, honestly 💅.

It uses your package manager's registry or index configuration, and — iconic behaviour — it does not modify it. Your config stays untouched, periodt 🎀.

All arguments are forwarded to cargo verbatim. Like, you say it, cargo hears it, word for word ✨.

🫶 Real talk, bestie: 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/ — read it, it's literally right there 😭

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

• -h, --help[=false] — Show help for this command. Your little emergency "what does this do again" button 💖

🌈 EXAMPLE 🌈

# Fetch dependencies through the Dependency Firewall
glab dependency-firewall cargo fetch

⭐ SEE ALSO ⭐

• glab-dependency-firewall(1) — go read the parent, she raised this one 🫶

---

auto generated by spf13/cobra 🌸 — this one's dated Nov 2026, and it's page glab(1) of the manual. mwah, bye bestie 💜✨