glab-dependency-firewall

Installation
SKILL.md

glab dependency-firewall

Current captured help and immutable provenance: command reference. Older command captures retain their original provenance and describe earlier interfaces.

Check package URLs, run supported package managers through GitLab Dependency Firewall, and inspect recorded activity. This command group is beta. Confirm availability before relying on it in durable automation.

CI job-level proxy

job-proxy (alias session) starts one experimental proxy for an entire CI job; df aliases dependency-firewall. Obtain explicit user authorization for the project, actor, runner/container, all routed traffic, downloads/publications, runtime files, background process, and certificate trust changes before start, internal serve, or stop. Do not run these as help checks. Prefer a disposable CI container; a shell executor can retain host trust changes.

start prints shell exports intended for evaluation in the job's before_script, and starts a detached proxy. It prints false on failure so evaluation fails under CI's set -e. Evaluate output only from the approved trusted executable, never from fetched text. The exports route HTTP/HTTPS traffic (including supported raw package downloads) and add trust through the system store and a merged CA bundle; this has broader scope than a per-command wrapper. Existing NO_PROXY is retained and CI_SERVER_HOST is added for direct GitLab traffic. Bypassed destinations and tools that ignore proxy settings are outside inspection. Non-package requests are forwarded unchanged.

The daemon retains the caller's outbound proxy settings for corporate egress. JVM routing/trust setup is best-effort and can warn without failing start: verify Maven/Gradle coverage instead of treating successful startup as proof. Run ci-summary last in script to make a blocked package fail the job; GitLab ignores the exit code in after_script. Logs are anchored to the job project directory even after directory changes.

GLAB_DF_JOB_PROXY_STATE_DIR selects the per-run state directory and is exported by start; stop needs that same directory, signals its recorded process, and attempts to remove the installed system CA even if stopping fails. Cleanup is best-effort and does not restore the current shell's exported environment. Confirm cleanup on a persistent runner; do not share state directories across jobs. Hidden serve --state-dir is the internal foreground daemon, not an additional setup step. Captured upstream examples are reference output, not permission to start a proxy.

NuGet and blocked-package diagnostics

Versioned NuGet coordinates are mapped to the firewall API's NuGet ecosystem for policy evaluation. This does not add a nuget or dotnet wrapper subcommand; use supported package checks or the explicitly approved job proxy. Block reasons are reported when the proxy refuses a request, beside the package-manager failure. Keep the established distinction between blocked packages, evaluation errors, and a firewall that is not evaluating the project; a successful process exit alone does not prove complete policy coverage.

Installs
79
GitHub Stars
51
First Seen
Aug 4, 2026