# Installer gitlab-ci-linter avec Homebrew, Nix

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de gitlab-ci-linter pour les workflows d'agents IA.

## installation

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

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install gitlab-ci-linter
```

  Preuve: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#gitlab-ci-linter
```

  Preuve: 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

## Faits du paquet

- **Clé du paquet:** brew:gitlab-ci-linter
- **Gestionnaire de paquets:** Homebrew
- **Version:** 2.4.0
- **Résumé source:** Command-line tool to lint GitLab CI YAML files
- **Page d'accueil:** <https://gitlab.com/orobardet/gitlab-ci-linter>
- **Dernière mise à jour:** 2026-07-29T16:05:02+02:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- gitlab-ci-linter (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 2.4.0
## Historique du projet et usages

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.

### Historique du projet

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.

### Historique d'adoption

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.

### Modes d'utilisation

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.

### Pourquoi les passionnés de paquets s'y intéressent

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.

### Chronologie

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

### Sources

- <https://docs.gitlab.com/ee/api/lint.html>
- <https://formulae.brew.sh/formula/gitlab-ci-linter>
- <https://gitlab.com/api/v4/projects/orobardet%2Fgitlab-ci-linter>
- <https://gitlab.com/orobardet/gitlab-ci-linter>
- <https://gitlab.com/orobardet/gitlab-ci-linter/-/raw/master/README.md>


## Notes de sécurité

narrow executable package without higher-risk signals.

- **Risque Geiger:** vert / faible
- narrow executable package without higher-risk signals


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

- Unix: ~/.netrc
- Windows: ~/_netrc
## Autres enregistrements de gestionnaires de paquets

- Nix - gitlab-ci-linter: normalized package name match | 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


## Combined YAML source

View the package source record on GitHub. [combined/gitlab-ci-linter.yml](https://github.com/mxcl/pkgdb/blob/main/combined/gitlab-ci-linter.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph