Ansible-lint

ansible-lint checks playbooks for practices and behavior that could potentially be improved. As a community-backed project ansible-lint supports only the last two major versions of Ansible.

Visit the Ansible Lint docs site

Using ansible-lint as a GitHub Action

This action allows you to run ansible-lint on your codebase without having to install it yourself.

# .github/workflows/ansible-lint.yml
name: ansible-lint
on:
  pull_request:
    branches: ["main", "stable", "release/v*"]
jobs:
  build:
    name: Ansible Lint # Naming the build is important to use it as a status check
    runs-on: ubuntu-24.04
    steps:
      - uses: actions/checkout@v6
      - name: Run ansible-lint
        uses: ansible/ansible-lint@main # or vX.X.X version
        # optional (see below):
        with:
          args: ""
          gh_action_ref: "<version - e.g. `v25.5.0`>" # Not recommended for non-composite action use
          setup_python: "true"
          python_version: "3.14"
          working_directory: ""
          requirements_file: ""

By default, the workflow uses ansible-lint installed from main. For production or stable workflows, it is recommended to specify a particular release tag (in format v.X.X.X).

All the arguments are optional:

args: Arguments to be passed to ansible-lint command.
gh_action_ref: The git branch, tag, or commit to use for ansible-lint. Not recommended for standard use - only use with composite actions where GH_ACTION_REF is set to the parent action version.
requirements_file: Path to the requirements.yml file to install role and collection dependencies.
setup_python: If python should be installed. Default is true.
python_version: The version of python to install. Default is 3.14.
working_directory: The directory where to run ansible-lint from. Default is github.workspace. Needed if you want to lint only a subset of your repository.

For more details, see ansible-lint-action.

Communication

Refer to the Talk to us section of the Contributing guide to find out how to get in touch with us.

You can also find more information in the Ansible communication guide.

Contributing

Please read Contribution guidelines if you wish to contribute.

Code of Conduct

Please see the Ansible Community Code of Conduct.

Licensing

The ansible-lint project is distributed as GPLv3 due to use of GPLv3 runtime dependencies, like ansible and yamllint.

For historical reasons, its own code-base remains licensed under a more liberal MIT license and any contributions made are accepted as being made under original MIT license.

Authors

ansible-lint was created by Will Thames and is now maintained as part of the Ansible by Red Hat project.

Metadata

Release files for ansible-lint 26.10.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ansible-lint 26.10.0
File	Size	Uploaded
ansible_lint-26.10.0.tar.gz	828.7 kB	Oct 12, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for ansible-lint 26.10.0
File	Interpreter	ABI	Platform	Reset
ansible_lint-26.10.0-py3-none-any.whl 342.2 kB Oct 12, 2026	Python 3	none	any	Details

Total release size: 1.2 MB

Release files / ansible_lint-26.10.0.tar.gz

Download URL	ansible_lint-26.10.0.tar.gz
Size	828.7 kB
Tags	Source
SHA-256 checksum How to use checksums	`89590b86bf53cd1310099587d0ce91e22389514a37148cf5081553e5c278517e`
BLAKE2b-256 checksum How to use checksums	`0365bd7efd6b1cac6e103d4c7c99a2811ea5630bb89b2c95feeb6f776dbe456e`
Upload date	Oct 12, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/ansible/ansible-lint
Publishing commit: github.com/ansible/ansible-lint/tree/fac2489f3e4ccffa83a40b839770abbf4ab52327

Workflow

Publishing configuration: github.com/ansible/ansible-lint/blob/fac2489f3e4ccffa83a40b839770abbf4ab52327/.github/workflows/release.yml
Publishing logs: github.com/ansible/ansible-lint/actions/runs/38228060383/attempts/1

Artifact

Subject: ansible_lint-26.10.0.tar.gz
SHA-256 checksum: 89590b86bf53cd1310099587d0ce91e22389514a37148cf5081553e5c278517e Verifying attestations

Release files / ansible_lint-26.10.0-py3-none-any.whl

Download URL	ansible_lint-26.10.0-py3-none-any.whl
Size	342.2 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`eaf427a800a65312f4446c33e53d531ddca1d81b82915a3a07dadc79160ec9dc`
BLAKE2b-256 checksum How to use checksums	`e56fd34add95c96f3d8bb37ff430fb1e334d32003d1c6ee9f034f0b8d29b459d`
Upload date	Oct 12, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/ansible/ansible-lint
Publishing commit: github.com/ansible/ansible-lint/tree/fac2489f3e4ccffa83a40b839770abbf4ab52327

Workflow

Publishing configuration: github.com/ansible/ansible-lint/blob/fac2489f3e4ccffa83a40b839770abbf4ab52327/.github/workflows/release.yml
Publishing logs: github.com/ansible/ansible-lint/actions/runs/38228060383/attempts/1

Artifact

Subject: ansible_lint-26.10.0-py3-none-any.whl
SHA-256 checksum: eaf427a800a65312f4446c33e53d531ddca1d81b82915a3a07dadc79160ec9dc Verifying attestations