Automic VaultAutomic Vault

brew

gitlab-ci-linter mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für gitlab-ci-linter in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install gitlab-ci-linter

local Homebrew formula metadata

Linux

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

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

Überblick

Paketzusammenfassung

Command-line tool to lint GitLab CI YAML files

Befehle und Aliase

  • gitlab-ci-linter

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

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

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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

Installierte Executables

BefehlArtSichtbarkeitHinweis
gitlab-ci-lintercliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version2.4.0
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:gitlab-ci-linter
Version2.4.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/gitlab-ci-linter
Homepagehttps://gitlab.com/orobardet/gitlab-ci-linter
Repositoryhttps://gitlab.com/orobardet/gitlab-ci-linter
Upstream-Dokumentationhttps://gitlab.com/orobardet/gitlab-ci-linter/-/blob/master/README.md
LizenzMIT
Quellarchivhttps://gitlab.com/orobardet/gitlab-ci-linter/-/archive/v2.4.0/gitlab-ci-linter-v2.4.0.tar.bz2
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

gitlab-ci-linter

nix profile install nixpkgs#gitlab-ci-linter
  • normalized package name match
  • Abgeglichen nach: 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

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • 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