pylint-actions
Pylint plugin for GitHub Actions
Decision gist · record as of 2026-08-14
Yes, if you run Pylint in GitHub Actions workflows. It requires minimal setup, has low install friction, carries no security vulnerabilities, and directly solves the problem of making Pylint output actionable in GitHub's UI. The MIT license imposes no restrictions. Not relevant outside GitHub Actions environments.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later and an existing Pylint installation.
- Low friction install with a single runtime dependency on pylint.
- Active maintenance with a recent release 11 days ago.
License · maintenance · safety
MIT (permissive) — MIT license permits unrestricted use, modification, and distribution with minimal restrictions.
last release 2026-08-03 (11 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 456,926 downloads/mo, #6,553 on PyPI
Alternatives
Verify before relying
pip install pylint-actions
Add to pyproject.toml:
[tool.pylint.main]
load-plugins = "pylint_actions"
Run: pylint -f actions src- Whether the plugin works with all current Pylint versions or has specific version constraints beyond what the fact sheet states.
- Performance impact when processing large codebases with many violations.
What it is and what it does
pylint-actions is a Pylint plugin that bridges static code analysis and GitHub Actions CI/CD workflows. Instead of Pylint's default text output, it formats violations as GitHub Actions annotations—a structured format that GitHub's web interface understands natively. When run in a workflow, these annotations appear as inline comments on pull request changes and as grouped warnings in the Actions log, making code quality issues immediately visible to reviewers without requiring them to parse raw linter output.
The plugin is configured via Pylint's standard configuration mechanisms (pyproject.toml, .pylintrc, etc.) and activated by passing the `--output-format=actions` flag. It has a single runtime dependency on Pylint itself and supports current Python versions (3.10+). The project is actively maintained and carries no known security vulnerabilities.
Use it for
- Display Pylint violations as inline comments on GitHub pull requests during code review.
- Integrate static analysis into GitHub Actions workflows with native annotation support.
- Automatically surface code quality issues in CI/CD logs without post-processing linter output.
- Enforce code standards in team workflows by making Pylint violations visible at review time.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you run Pylint in GitHub Actions workflows.
It requires minimal setup, has low install friction, carries no security vulnerabilities, and directly solves the problem of making Pylint output actionable in GitHub's UI. The MIT license imposes no restrictions. Not relevant outside GitHub Actions environments.
Install
pylint-actions on PyPI
Before you install
Low friction install with a single runtime dependency on pylint. Active maintenance with a recent release 11 days ago.
Requires Python 3.10 or later and an existing Pylint installation.
License in practice
MIT license permits unrestricted use, modification, and distribution with minimal restrictions.
Quickstart
pip install pylint-actions
Add to pyproject.toml:
[tool.pylint.main]
load-plugins = "pylint_actions"
Run: pylint -f actions src
Verify before relying
- Whether the plugin works with all current Pylint versions or has specific version constraints beyond what the fact sheet states.
- Performance impact when processing large codebases with many violations.
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagepylint |
| Maintenance | Actively maintained 11 days since the last release |
| First released | |
| Downloads | 456,926 / month, #6,553 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 4 - BetaEnvironment :: ConsoleIntended Audience :: DevelopersLicense :: OSI Approved :: MIT LicenseOperating System :: OS IndependentProgramming Language :: PythonProgramming Language :: Python :: 3Programming Language :: Python :: Implementation :: CPythonProgramming Language :: Python :: Implementation :: PyPyTopic :: Software Development :: Libraries :: Python ModulesTopic :: Software Development :: Quality AssuranceTopic :: Software Development :: Testing |
Evidence: pylint_actions-0.7.0-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “pylint github actions annotations”
- pylint-actionsA Pylint plugin that formats linting output as GitHub Actions…
- pytest-github-actions-annotate-failuresA pytest plugin that automatically annotates failed tests in GitHub…
- bar-raiserBar-Raiser creates GitHub checks with inline annotations, autofix…
Give your agent the search over MCP, or paste the wish link into any chat.
More Python Modules packages
Converts domain names between Unicode and ASCII-compatible encoding (Punycode) according to IDNA 2008 and Unicode Technical Standard 46, with security validation and broader script coverage than the standard library.
Install it if you work with internationalized domain names, need to validate domains, or use HTTP clients that depend on it transitively.
Setuptools is a Python build backend and package management tool that handles building, distributing, and installing Python packages, including support for C/C++ extension modules.
PyYAML parses and emits YAML 1.1 data format, enabling serialization and deserialization of configuration files and Python objects to and from human-readable YAML text.
Pydantic validates Python data structures against type hints, coercing and checking input at runtime to ensure it matches a declared schema.
Provides reusable metadata objects for use with PEP-593 `typing.Annotated` to express common constraints like bounds, collection sizes, and predicates on types.
Install it if you use or build libraries that need to express type constraints in a standardized, inspectable way—or if you want to annotate your own types with…
Provides runtime tools to inspect and introspect Python type annotations, enabling programmatic examination of type hints at execution time.
See also pylint-gitlab · pylint-junit · pylint-protobuf · pylint-django · pylint-json2html · pylint-quotes · pylint-pytest · pylint-pydantic · gitlint-core · gitlint