https://github.com/timo-reymann/gitlab-ci-verify
Validate and lint your gitlab ci files using ShellCheck, the Gitlab API, curated checks or even build your own checks
https://github.com/timo-reymann/gitlab-ci-verify
gitlab-ci shellcheck work-in-progress
Last synced: about 2 months ago
JSON representation
Validate and lint your gitlab ci files using ShellCheck, the Gitlab API, curated checks or even build your own checks
- Host: GitHub
- URL: https://github.com/timo-reymann/gitlab-ci-verify
- Owner: timo-reymann
- License: gpl-3.0
- Created: 2024-08-30T08:29:11.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2026-01-27T15:50:36.000Z (about 2 months ago)
- Last Synced: 2026-01-28T02:19:48.704Z (about 2 months ago)
- Topics: gitlab-ci, shellcheck, work-in-progress
- Language: Go
- Homepage: https://gitlab-ci-verify.timo-reymann.de/
- Size: 45.4 MB
- Stars: 44
- Watchers: 1
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
gitlab-ci-verify
===
[](https://github.com/timo-reymann/gitlab-ci-verify/releases/latest)
[](https://pypi.org/project/gitlab-ci-verify)
[](https://pypi.org/project/gitlab-ci-verify)
[](https://hub.docker.com/r/timoreymann/gitlab-ci-verify)
[](https://github.com/timo-reymann/gitlab-ci-verify/releases)
[](https://dl.circleci.com/status-badge/redirect/gh/timo-reymann/gitlab-ci-verify/tree/main)
[](https://codecov.io/gh/timo-reymann/gitlab-ci-verify)
[](https://renovatebot.com)
[](https://sonarcloud.io/summary/new_code?id=timo-reymann_gitlab-ci-verify)
[](https://sonarcloud.io/summary/new_code?id=timo-reymann_gitlab-ci-verify)
[](https://goreportcard.com/report/github.com/timo-reymann/gitlab-ci-verify)
[](https://sonarcloud.io/summary/new_code?id=timo-reymann_gitlab-ci-verify)
Validate and lint your gitlab ci files using ShellCheck, the Gitlab API, curated checks or even build your own checks
## Features
- ShellCheck for scripts
- Validation against Pipeline Lint API for project
- Curated checks for common mistakes (feel free to [contribute new ones](https://gitlab-ci-verify.timo-reymann.de/add-builtin-check.html))
- Automatic detection of the current gitlab project with an option to overwrite
- Available as pre-commit hook
- Usable to valid dynamically generated pipelines using the [python wrapper](https://gitlab-ci-verify.timo-reymann.de/usage/python-library.html)
- Support for *gitlab.com* and self-hosted instances
- Support for [custom policies](https://gitlab-ci-verify.timo-reymann.de/extending/writing-custom-policies.html) written
in [Rego](https://www.openpolicyagent.org/docs/latest/policy-language/)
- Resolve and validate
includes ([how it works and limitations](https://gitlab-ci-verify.timo-reymann.de/how-it-works/include-resolution.html))
## Installation
See the [Installation section](https://gitlab-ci-verify.timo-reymann.de/installation.html) in the documentation.
## Documentation
You can find the full documentation on [GitHub Pages](https://gitlab-ci-verify.timo-reymann.de/), including:
- How it works
- How to add new checks
- How to write custom policies using rego
- How to authenticate with GitLab
## Motivation
Unfortunately, GitLab didn't provide a tool to validate CI configuration for quite a while.
Now that changed with the `glab` CLI providing `glab ci lint` but it is quite limited and under the hood just calls the
new CI Lint API.
Throughout the years quite some tools evolved, but most of them are either outdated, painful to use or install, and
basically also provide the lint functionality from the API.
As most of the logic in pipelines is written in shell scripts via the `*script` attributes these are lacking completely
from all tools out there as well as the official lint API.
The goal of gitlab-ci-verify is to provide the stock CI Lint functionality plus shellcheck.
Completed in the future some
rules to lint that common patterns are working as intended by GitLab
and void them from being pushed and leading to unexpected behavior.
## Contributing
I love your input! I want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the configuration
- Submitting a fix
- Proposing new features
- Becoming a maintainer
To get started, please read the [Contribution Guidelines](./CONTRIBUTING.md).
## Credits
This whole project wouldn't be possible with the great work of the
following libraries/tools:
- [Shellcheck by koalaman](https://github.com/koalaman/shellcheck)
- [go stdlib](https://github.com/golang/go)
- [pflag by spf13](https://github.com/spf13/pflag)
- [go-yaml](https://github.com/go-yaml/yaml), which I forked
to [timo-reymann/go-yaml](https://github.com/timo-reymann/go-yaml)