# Install gitlab-ci-local with Homebrew

Run gitlab pipelines locally as shell executor or docker executor. Version 4.74.0 via Homebrew; verified 2026-08-01.

## Install

```sh
sudo av install brew:gitlab-ci-local
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install gitlab-ci-local
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:gitlab-ci-local
- **Package manager:** Homebrew
- **Version:** 4.74.0
- **Source summary:** Run gitlab pipelines locally as shell executor or docker executor
- **Homepage:** <https://github.com/firecow/gitlab-ci-local>
- **Last updated:** 2026-08-01T12:21:26Z
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- gitlab-ci-local (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 4.74.0
## 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.

### Sources

- <https://api.github.com/repos/firecow/gitlab-ci-local>
- <https://formulae.brew.sh/formula/gitlab-ci-local>
- <https://github.com/firecow/gitlab-ci-local>
- <https://github.com/firecow/gitlab-ci-local/releases/tag/4.73.0>
- <https://raw.githubusercontent.com/firecow/gitlab-ci-local/master/README.md>
- <https://www.npmjs.com/package/gitlab-ci-local>


## Security Notes

generalized runtime or code generation signal.

- **Geiger risk:** yellow / medium
- generalized runtime or code generation signal


## 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

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

## Combined YAML source

View the package source record on GitHub. [combined/gitlab-ci-local.yml](https://github.com/automic-vault/db/blob/main/combined/gitlab-ci-local.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation