How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/vince-winkintel/gitlab-cli-skills --skill glab-dependency-firewallBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
glab dependency-firewall
Inspect GitLab Dependency Firewall activity for local package-manager workflows. The current command group is marked experimental, and the verified release binary exposes ci-summary only; do not rely on older configure examples unless live help on the target machine still lists them.
Quick start
# Summarize the current working directory's Dependency Firewall CI log
glab dependency-firewall ci-summarySummarize CI activity
ci-summary reads .gitlab/df/ci-log.json relative to the current working directory. Run it from the same directory as the package-manager/Dependency Firewall operation that produced the log.
if glab dependency-firewall ci-summary; then
echo "No blocked dependency entries"
else
rc=$?
case "$rc" in
1) echo "Dependency Firewall log could not be read" >&2 ;;
3) echo "Dependency Firewall blocked one or more packages" >&2 ;;
*) echo "Unexpected Dependency Firewall failure: $rc" >&2 ;;
esac
exit "$rc"
fiExit codes:
0: no blocked entries; allow-only, warnings-only, or no recorded activity.1: the log could not be read or parsed.3: one or more entries were blocked.
Treat exit 3 as a policy result, not a transient command failure. Surface the blocked package, version, and reason; do not bypass the policy or rewrite the log. Treat warnings as review input even though they do not fail the command.
Troubleshooting
No activity is reported:
- Confirm
.gitlab/df/ci-log.jsonexists under the current working directory used for the command. - Do not assume a log in a repository root applies when the package manager ran in a nested workspace.
A `configure` example fails:
glab dependency-firewall configureis not exposed by the verified current release binary.- Re-check
glab dependency-firewall --helpon the target machine before using older docs or scripts.
Unsupported package manager:
- The current visible command surface does not configure package managers.
- Do not invent configuration for another manager; check live help or official docs for the target glab/GitLab version.
Command reference
See references/commands.md for captured help and flags.


