LinthelmIntroductions to linters, static analysis and code-quality tools

Linters

What is actionlint? An introduction to rhysd's GitHub Actions workflow linter

By the Linthelm editorial team · Published · Updated

actionlint is a static checker for GitHub Actions workflow files. It reads the workflows in a repository and reports syntax errors, expression type errors, incorrect action usage, script problems and security issues before the workflows run. It is open source and distributed under the MIT license.

Tool
actionlint
Made by
rhysd
Official site
github.com/rhysd/actionlint
Category
Linters

Who makes actionlint

actionlint is made by rhysd. The project is open source and distributed under the MIT license.

The official website for actionlint is its GitHub repository, linked below this page.

Official website: github.com/rhysd/actionlint

What actionlint is for

actionlint checks GitHub Actions workflow files statically, meaning it analyzes the files without running them. It is designed to catch as many errors as possible while keeping false positives minimal, so that its reports are worth acting on.

Its checks cover several layers of a workflow: the structure of the YAML against the workflow syntax, the expressions written inside ${{ }}, the inputs and outputs of the actions a workflow uses, and the scripts in run: steps. It also looks for security problems and for smaller mistakes such as invalid cron strings or unknown runner labels.

Who actionlint is for

The vendor does not state a target audience. In practice, actionlint is relevant to anyone who writes or maintains GitHub Actions workflow files and wants mistakes found before a workflow runs.

Because it can run from the command line, in Docker, in editors and in CI-adjacent tooling, it suits both individual contributors checking a file locally and teams that want the same checks applied to every change. Developers who want to embed workflow checks in their own Go programs can also use it as a library through its Go API.

Notable capabilities

actionlint combines workflow-specific checks with a few integrated checkers for the scripts inside workflows. The main capabilities are listed below.

  • Syntax checking: it checks workflow files for unexpected or missing keys according to the workflow syntax.
  • Expression type checking: it strictly type-checks ${{ }} expressions, catching semantic errors such as access to non-existent properties and type mismatches.
  • Action usage checks: it verifies that inputs under with: and outputs referenced through steps.{id}.outputs are correct.
  • Reusable workflow validation: it checks the inputs, outputs and secrets of reusable workflows and workflow calls.
  • Script checking: it integrates shellcheck and pyflakes to check scripts in run: steps.
  • Security checks: it detects script injection from untrusted inputs and hard-coded credentials.
  • Other validations: it covers glob syntax, needs: dependencies, runner labels and cron syntax.
  • Configuration: behavior can be adjusted, including self-hosted runner labels, configuration variables and per-file-path error ignore patterns.

How actionlint fits linters

Within the linters category, actionlint is specialized. Rather than analyzing a general-purpose programming language, it targets one file type: GitHub Actions workflow files. Those files mix YAML structure, an expression language and embedded shell or Python scripts, and actionlint checks each of those parts.

In Linthelm's wider niche of linters, static analysis and code quality, it covers the automation layer of a project, the part that builds, tests and ships the code. It is typically used alongside language linters, not in place of them.

Setup is light. It automatically detects workflows in a repository, so running the command in the repository is basically all that is needed. It can be installed from a released binary, Homebrew or go install, or run from a Docker image. An online playground runs actionlint in the browser through WebAssembly. Integrations include reviewdog, Problem Matchers, super-linter, pre-commit and VS Code.

Frequently asked questions

What is actionlint used for?

actionlint is used to statically check GitHub Actions workflow files. It finds syntax errors, expression type errors, wrong action inputs and outputs, script issues, and security problems such as script injection and hard-coded credentials.

Who develops actionlint?

actionlint is developed by rhysd. It is open source and distributed under the MIT license, and its official website is the GitHub repository.

How do I install and run actionlint?

You can install actionlint from a released binary, with Homebrew, or with go install, or run it from a Docker image. It automatically detects workflows in a repository, so running the command in the repository is basically all that is needed.

Does actionlint check shell scripts in workflows?

Yes. actionlint integrates shellcheck and pyflakes to check scripts in run: steps.

Can I try actionlint without installing it?

Yes. An online playground lets you run actionlint in the browser through WebAssembly.

Sources. This introduction is based on the vendor's official pages, checked on 21 November 2026 (Asia/Dhaka):

Linthelm is independent and is not affiliated with rhysd. Product names belong to their owners. Features change; confirm details on the official website.