GitLab CI Break Lint
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Names the .gitlab-ci.yml lines your runner will reject after the next GitLab major upgrade
Install
gitlab-ci-break-lint file
Node 18+. The same 16 rules as the VS Code extension, from a terminal or CI.
Free
- Lint the pipeline file you have open and get every retired keyword, GitHub Actions leftover and invalid job wiring with its line number and its replacement line.
--ruleslists every rule
With a licence ($29 once)
- Scan every pipeline file in the repository in one pass and export a dated Markdown upgrade report (file, line, keyword, replacement) to attach to the change ticket.
gitlab-ci-break-lint --dir ./templates --report html --out report.html
A freelance DevOps engineer's hour runs about $100, and reading a repository's pipelines by hand against a removals list is most of a morning.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "gitlab-ci-break-lint": { "command": "gitlab-ci-break-lint", "args": ["--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: GitLab CI Break Lint
run: pip install rulestamp-gitlab-ci-break-lint && gitlab-ci-break-lint --dir . --ci
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install rulestamp-gitlab-ci-break-lint
gitlab-ci-break-lint --help
Metadata
Release files for rulestamp-gitlab-ci-break-lint 1.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rulestamp_gitlab_ci_break_lint-1.0.5.tar.gz | 16.5 kB | Without provenance | Details for rulestamp_gitlab_ci_break_lint-1.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_gitlab_ci_break_lint-1.0.5-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_gitlab_ci_break_lint-1.0.5-py3-none-any.whl |
Total release size: 35.0 kB
Release files / rulestamp_gitlab_ci_break_lint-1.0.5.tar.gz
| Download URL | rulestamp_gitlab_ci_break_lint-1.0.5.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d72e5f1b18e6cd29f4c40bba00d33b281bdccc431e3a12fd84fc5f660f87a41
|
|
BLAKE2b-256 checksum How to use checksums |
8b966bb2fc40d96c068d6fd8a52319e70df8c7c62e134ddfabe0ad0f796c7f11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_gitlab_ci_break_lint-1.0.5-py3-none-any.whl
| Download URL | rulestamp_gitlab_ci_break_lint-1.0.5-py3-none-any.whl |
|---|---|
| Size | 18.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2fe5c7f934a2d80197d8ab93b2fc8662aa1384f67245bfec8aad1d8d354b590b
|
|
BLAKE2b-256 checksum How to use checksums |
7c8aa1fc110a498de479c278a6326b5efdb2d7cdc342aee91ede01650d8244b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-gitlab-ci-break-lint 1.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.