Automic VaultAutomic Vault

brew

Install gitlab-ci-linter with Homebrew, Nix

Command-line tool to lint GitLab CI YAML files. Version 2.4.0 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install gitlab-ci-linter

local Homebrew formula metadata

Linux

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

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

overview

Package summary

Command-line tool to lint GitLab CI YAML files

Commands and aliases

  • gitlab-ci-linter

history

Project history and usage

gitlab-ci-linter is a small Go command-line tool that validates a local `.gitlab-ci.yml` file by calling a GitLab instance's CI lint API. It is designed to catch invalid GitLab CI configuration before a developer commits or pushes changes.

Project history

The GitLab project was created in March 2017. Its README makes the architectural boundary explicit: the tool does not implement its own GitLab CI linter, but delegates validation to the GitLab API that belongs to the target project.

The project adapted to GitLab API evolution after the older `/ci/lint` endpoint was deprecated in GitLab 15.7 and removed in GitLab 16.0; the README documents use of the `projects/:project_path_or_id/ci/lint` endpoint and project path or project ID options.

Adoption history

Adoption appears specialized: the GitLab project metadata collected for this enrichment reported 53 stars. Its practical audience is teams that want local or pre-commit validation against gitlab.com or a private GitLab instance rather than waiting for a failed pipeline.

How it is used

Practitioners run `gitlab-ci-linter` from inside a Git repository with a GitLab origin and a `.gitlab-ci.yml` file. The README documents installation as a Git pre-commit hook, optional use through the `pre-commit` framework, explicit GitLab URL and project options, and authentication through a personal access token or `.netrc` account field.

Why package nerds care

For package-manager users, gitlab-ci-linter is a classic sharp-edged CLI: a cross-platform binary, a narrow API-backed job, and enough configuration to work with self-hosted GitLab. It fills the gap between static YAML syntax checks and a real GitLab CI validation request.

Timeline

  • 2017: GitLab project created.
  • 2017: README documented local `.gitlab-ci.yml` validation through GitLab's lint API.
  • 2022: GitLab 15.7 deprecated the older `/ci/lint` endpoint.
  • 2023: GitLab 16.0 removed the older endpoint, leading the tool's documented flow to use the project-scoped lint endpoint.

Related projects

  • Related projects and services include GitLab CI, GitLab's CI lint API, the `pre-commit` framework, Cloudsmith packages, and Docker-based CLI distribution.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build 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.

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.netrc
Windows
~/_netrc

executables

Installed executables

CommandKindExposureNote
gitlab-ci-lintercliglobal 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 version2.4.0
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://gitlab.com/orobardet/gitlab-ci-linter

install metadata

Package metadata

Package keybrew:gitlab-ci-linter
Version2.4.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/gitlab-ci-linter
Homepagehttps://gitlab.com/orobardet/gitlab-ci-linter
Repositoryhttps://gitlab.com/orobardet/gitlab-ci-linter
Upstream docshttps://gitlab.com/orobardet/gitlab-ci-linter/-/blob/master/README.md
LicenseMIT
Source archivehttps://gitlab.com/orobardet/gitlab-ci-linter/-/archive/v2.4.0/gitlab-ci-linter-v2.4.0.tar.bz2
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegitlab-ci-linter
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • 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-linter

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

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