Automic VaultAutomic Vault

brew

Install gitlab-ci-local with Homebrew, Nix

Run gitlab pipelines locally as shell executor or docker executor. Version 4.73.0 via Homebrew; verified 2026-06-23.

Install commandSecurity notes

install

Additional install commands

macOS

Homebrewverified · 100%
brew install gitlab-ci-local

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#gitlab-ci-local

nixpkgs package indexes · pkgs/by-name/gi/gitlab-ci-local/package.nix · source: api.github.com

overview

Package summary

Run gitlab pipelines locally as shell executor or docker executor

Commands and aliases

  • gitlab-ci-local

history

Project history and usage

gitlab-ci-local is a command-line runner for executing GitLab CI pipelines on a developer machine with shell or Docker executors. It is built around the recurring developer problem described by its README: avoiding repeated pushes just to discover whether `.gitlab-ci.yml` behaves as expected.

Project history

The GitHub repository was created in January 2020. The README positions the tool as a replacement for project-specific shell scripts and make targets by letting developers run the same GitLab CI jobs locally.

The project expanded beyond a basic runner into a package with Debian repository instructions, AUR packaging, npm and Bun installation, Homebrew installation, Windows Git Bash support, dotenv-style defaults, tab completion, job listing modes, and documented behavior for includes, artifacts, variables, and local-only jobs.

Adoption history

gitlab-ci-local's adoption follows the spread of GitLab CI into projects that wanted faster feedback than remote pipeline runs. Repository metadata collected for this enrichment reported 3,978 GitHub stars, and the package is distributed through npm, Homebrew, distro-oriented channels, and Arch's AUR.

Its ecosystem significance comes from matching GitLab CI's YAML-centered workflow while accepting that a local runner has boundaries. The README documents tracked-file behavior, local-only rules, variables from home and project files, remote variables, and artifact handling so teams can decide what belongs in local feedback and what belongs in GitLab.

How it is used

Practitioners install the CLI, run `gitlab-ci-local` in a repository, use `.gitlab-ci-local-env` or `$HOME/.gitlab-ci-local/.env` for default CLI options, and use variables files to model CI/CD variables. They also use `--list`, `--list-all`, and CSV listing modes to inspect planned jobs before executing a pipeline.

Why package nerds care

For package nerds, gitlab-ci-local is interesting because it turns a hosted CI product's YAML dialect into a local executable distributed through several package ecosystems. It is the sort of package that saves time in inner-loop development while surfacing the hard parts of reproducing CI outside the hosted service.

Timeline

  • 2020: Repository created for local GitLab CI execution.
  • 2020: README described running GitLab pipelines locally as shell or Docker executor.
  • 2024: npm package metadata exposed the `gitlab-ci-local` binary entry point.
  • 2026: v4.73.0 release published on GitHub.

Related projects

  • Related surfaces include GitLab CI, Docker, shell executors, npm, Bun, Homebrew, Debian packaging, AUR, and Git Bash on Windows.

security posture

Risk level: yellow

generalized runtime or code generation signal.

Risk classifier

yellow risk · medium confidence · runtime

Why

  • generalized runtime or code generation signal

Signals

  • text:shell

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 1 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
.gitlab-ci.yml.gitlab-ci-local-env~/.gitlab-ci-local/.env

executables

Installed executables

CommandKindExposureNote
gitlab-ci-localcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version4.73.0
manager updated2026-06-23
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/firecow/gitlab-ci-local

install metadata

Package metadata

Package keybrew:gitlab-ci-local
Version4.73.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/gitlab-ci-local
Homepagehttps://github.com/firecow/gitlab-ci-local
Repositoryhttps://github.com/firecow/gitlab-ci-local
Upstream docshttps://github.com/firecow/gitlab-ci-local#readme
LicenseMIT
Source archivehttps://registry.npmjs.org/gitlab-ci-local/-/gitlab-ci-local-4.73.0.tgz
Last updated2026-06-23T12:38:37Z
Pulseupdated
Dependenciesnode
Bottleavailable (on all)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegitlab-ci-local
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

gitlab-ci-local

nix profile install nixpkgs#gitlab-ci-local
  • normalized package name match
  • Matched by: Gitlab Ci Local
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/gi/gitlab-ci-local/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

Related tools

  • nodeRuntime dependency declared by Homebrew.
  • gitlab-ci-localSame normalized package name appears in another local ecosystem. Shared terms: ci, gitlab, gitlab-ci-local, local, pipeline.

Same workflow

  • gitlab-ci-linterShares av.db curated category or tags: ci, ci-cd, cli, developer-tools, gitlab.
  • gitlab-runnerShares av.db curated category or tags: ci, ci-cd, cli, developer-tools, gitlab.
  • actShares av.db curated category or tags: ci-cd, cli, developer-tools, docker.
  • actionlintShares av.db curated category or tags: ci, ci-cd, cli, developer-tools.
  • actions-upShares av.db curated category or tags: ci, ci-cd, cli, developer-tools.
  • codecov-cliShares av.db curated category or tags: ci, ci-cd, cli, developer-tools.
  • gitlab-ci-localSame normalized package name in another local ecosystem.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment