glab(1)

🌸 NAME 🌸

glab-dependency-firewall-yarn — Run Yarn through the GitLab Dependency Firewall. (BETA) 💖

Okay bestie, this page is from the glab(1) manual and it's all about the glab-dependency-firewall-yarn command. Yes, the name is long. Yes, it ate. 💅

🧵 SYNOPSIS 🧵

glab dependency-firewall yarn  [flags]

🛡️ DESCRIPTION 🛡️

This command runs the yarn 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. Literally a whole security vibe check for your package traffic. ✨

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

Compatibility tea, important: this command requires Yarn 3.2 or later, or Yarn Classic (1.x). It refuses Yarn 2.x through 3.1, because those versions cannot stop a .yarnrc.yml file from routing registry traffic around the firewall. So Yarn 2.x through 3.1 is a hard pass — the firewall cannot be bypassed that way.

During the run, Yarn ignores per-host networkSettings from every .yarnrc.yml file, so every request goes through the firewall. Every. Request. 🔥

All arguments are forwarded to yarn verbatim. Exactly as you typed them, bestie.

Beta warning, for real: 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. The assistive icon we love. 🫶

🍓 EXAMPLE 🍓

# Install dependencies through the Dependency Firewall
glab dependency-firewall yarn install

# Add a package through the Dependency Firewall
glab dependency-firewall yarn add left-pad

👀 SEE ALSO 👀

• glab-dependency-firewall(1)

Auto generated by spf13/cobra, dated Nov 2026, and filed under glab(1). Bye bestie, go let the firewall handle it 💅✨