pylint-gitlab

What it is and what it does

pylint-gitlab extends pylint with three custom output formatters designed to integrate code linting directly into GitLab CI workflows. It transforms pylint's analysis results into formats that GitLab understands natively: Code Climate JSON (for merge request code quality reports), an HTML page with linked linting details, and badge scores for visual feedback. The package wraps pylint itself as a runtime dependency, so installing pylint-gitlab automatically brings in pylint and its ecosystem (astroid, isort, mccabe, and others).

You run pylint as normal but specify one of the custom formatters via --output-format, either by full class name (pylint_gitlab.GitlabCodeClimateReporter) or by loading the plugin and using a short alias (gitlab-codeclimate). The package is most commonly used in .gitlab-ci.yml scripts to generate artifacts that GitLab's CI/CD pipeline consumes—code quality reports appear in merge requests, and badge SVGs can be published to GitLab Pages.

Use it for:

• Generate Code Climate JSON reports in GitLab CI to display code quality metrics on merge requests.
• Create HTML pages with pylint results and source code links for publishing to GitLab Pages.
• Produce badge SVGs showing linting scores that can be embedded in project documentation or CI artifacts.
• Integrate pylint linting into nbQA workflows using the CodeClimateReporterNoHash variant.
• Automate linting feedback in CI/CD pipelines without writing custom report parsing logic.

Worth the install?

AI-flagged interpretation of the facts on this page — verify before relying

Provides custom pylint output formatters that integrate linting results into GitLab CI—generating Code Climate JSON reports, HTML pages with linting details, and badge scores.

Yes, if you use GitLab CI and want pylint integration without custom report parsing. The package is stable, has no known vulnerabilities, and handles the boilerplate of formatting pylint output for GitLab's native tooling. The aging maintenance status (264 days since release) is a minor concern—verify compatibility with your pylint version before adopting in a new project, but the package is widely downloaded and appears functional.

Install

pylint-gitlab on PyPI

pip install pylint-gitlab

uv add pylint-gitlab

poetry add pylint-gitlab

Installing pylint-gitlab

Before you install

Low install friction; pure Python wheel. Maintenance status is aging (264 days since last release), though the package remains in the top 5000 by downloads and has no known vulnerabilities.

License in practice

GPLv3 copyleft license: you may use and modify the package freely, but any derivative work or distribution must also be licensed under GPLv3 and include source code.

Quickstart

pip install pylint-gitlab

pylint --exit-zero --output-format=pylint_gitlab.GitlabCodeClimateReporter . > codeclimate.json

# Or with plugin loaded:
pylint --exit-zero --load-plugins=pylint_gitlab --output-format=gitlab-codeclimate . > codeclimate.json

Requires pylint (installed automatically as a dependency) and Python >=3.7.

Verify before relying

• Whether the aging maintenance status (264 days since release) affects compatibility with recent pylint versions.
• Whether all three formatters (CodeClimate, CodeClimateNoHash, PagesHtml) remain fully functional in current GitLab CI environments.

Package facts

Evidence: pylint_gitlab-2.1.1-py3-none-any.whl

Tags

More Quality Assurance packages