Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

actionlint

rhysd.github.io

  • Free plan
  • Windows
  • macOS
  • Linux
  • Web
  • Self-hosted
7.6 Club score Visit rhysd.github.io

What actionlint is

actionlint is a static checker for GitHub Actions workflow files. It checks workflow syntax for missing or unexpected keys and evaluates `${{ }}` expressions for issues such as type mismatches and missing properties. It also validates action inputs and outputs, along with inputs, outputs, and secrets used by reusable workflows and workflow calls. Security checks flag script injection risks from untrusted inputs and hard-coded credentials. For scripts in `run:` steps, actionlint can connect to ShellCheck and Pyflakes; these integrations can be disabled. The project documents installation through prebuilt binaries, Docker, source builds, a CI download script, and package managers. A browser playground runs the checker through WebAssembly and states that data stays in the browser. Integrations are documented for several editors and CI tools, including VS Code, Vim and Neovim, reviewdog, and pre-commit. The project also offers Go APIs and configuration for self-hosted runner labels, configuration variables, and file-specific error ignore patterns. actionlint is free and MIT-licensed.

Who it suits

It suits people who maintain GitHub Actions workflows and want checks for syntax, expressions, action interfaces, or security risks. Developers can use the command-line tool, browser playground, editor and CI integrations, or Go APIs.

Good to know, and what to watch

  • Checks workflow syntax and expression types
  • Flags script injection risks and hard-coded credentials
  • Browser playground states data stays in the browser
  • Install options include binaries, Docker, and package managers
  • Free and MIT-licensed
  • Focused on GitHub Actions workflow files
  • ShellCheck and Pyflakes integrations are optional

actionlint

Free

Open source

Getting started

  1. Visit the actionlint website.
  2. Choose an installation route: prebuilt binary, Docker, source build, CI download script, or package manager.
  3. Run it from the command line, or use the browser playground.
  4. Connect it to a documented editor or CI integration if that fits your workflow.
  5. Configure runner labels, variables, or file-specific error-ignore patterns as needed.

The Club's review

Overview

actionlint is a free, open-source checker for GitHub Actions workflows. It suits developers and teams who maintain automation in GitHub and want to catch workflow mistakes before they affect a run. Its focused checks make it a strong workflow companion, though it does not analyze application code generally.

Key features

Structural checks catch unexpected and missing workflow keys. Strong type checking for ${{ }} expressions can also flag missing properties and mismatched types, which helps catch errors that a basic syntax check would miss. Validation extends to action inputs and outputs, as well as inputs, outputs, and secrets in reusable workflows and workflow calls.

Security checks look for script injection risks involving untrusted inputs and hard-coded credentials. These are useful safeguards around workflow automation, but their scope is the workflow rather than the broader application. For scripts in run: steps, actionlint can integrate ShellCheck and Pyflakes; either integration can be disabled.

Configuration supports self-hosted runner labels, configuration variables, and file-path-based ignore patterns. Developers can use documented integrations with reviewdog, GitHub Problem Matchers, super-linter, pre-commit, and several editors, or call actionlint through its Go APIs. Installation options include prebuilt binaries, Docker, source builds, a CI download script, and package managers.

The browser playground runs actionlint through WebAssembly and says it never sends data outside the browser. That gives users a convenient way to check workflows in a browser while keeping their data there.

Pricing

actionlint costs nothing under the MIT license. The free plan includes the command-line tool and browser playground, with no paid tier or trial to weigh. It is a practical choice for individual maintainers and teams that want workflow checks without a software subscription.

Platforms

Platforms include Linux, macOS, Windows, self-hosted environments, and the web. Prebuilt binaries, Docker, source builds, CI downloads, and package managers give teams several installation routes; the browser playground covers a separate, browser-based workflow.

Who it's for

Choose actionlint if you write or review GitHub Actions workflows and want checks for structure, expression semantics, action interfaces, and selected security risks. It is especially useful when workflows rely on reusable workflows, expressions, or scripts in run: steps. It is a poor fit as a general-purpose code analyzer; its checks are centered on GitHub Actions.

Pros and cons

Pros

  • Checks workflow meaning as well as structure: expression typing and interface validation reach beyond missing-key checks.
  • Workflow-specific security checks: it flags script injection risks from untrusted inputs and hard-coded credentials.
  • Flexible integration: editor, CI, shell and Python linting, browser, and Go options suit different development setups.
  • Free and open source: the MIT-licensed tool has a free plan that includes both command-line use and the browser playground.

Cons

  • Narrow scope: it checks GitHub Actions workflows, so application code needs a separate analyzer.
  • Some script checks depend on integrations: ShellCheck and Pyflakes can extend coverage for run: steps, but they are integrations that can also be disabled.

Alternatives

Browse Linters for more options. Cppcheck is another static-analysis tool with a free open-source plan and a freemium model. Astral offers free, open-source developer tools including Ruff, uv, and ty. Biome is a free open-source toolchain for web projects. PHPMD is a free PHP source-code analyzer. PMD is a free downloadable static code analyzer. Ruff is a free open-source tool in Astral's Python developer-tools portfolio. Staticcheck is a free open-source option. SwiftLint is a free, MIT-licensed Swift linting tool. These tools suit readers looking for analysis in their respective project areas rather than a checker focused on GitHub Actions workflows.

Verdict

For anyone maintaining GitHub Actions, actionlint is an easy recommendation: its free command-line and browser options combine workflow structure, expression, interface, and targeted security checks. Choose it for workflow quality; look elsewhere when you need a general-purpose analyzer for application code.

The verdict

actionlint covers workflow structure, expression semantics, action interfaces, and selected security risks. Its command-line, browser, editor, CI, and Go options support different development workflows.

Questions people ask

Does actionlint cost anything?

It is free and distributed under the MIT license.

What does actionlint check?

It checks GitHub Actions workflow syntax, expression semantics, action inputs and outputs, reusable-workflow data, and selected security risks.

Can I use it in a browser?

Yes. Its playground runs through WebAssembly and states that it does not send data outside the browser.

How can I install it?

The project documents prebuilt binaries, Docker, building from source, a CI download script, and package-manager options.

Does it integrate with editors and CI?

Yes. Documented integrations include several editors and CI-related tools such as reviewdog, GitHub Problem Matchers, and super-linter.

Is actionlint open source?

Yes. It is distributed under the MIT license.

What the maker publishes

Action and workflow validation
It checks action inputs and outputs, as well as inputs, outputs, and secrets in reusable workflows and workflow calls. source
Configuration
The README says configuration can set self-hosted runner labels, configuration variables, and error ignore patterns by file path. source
Developer integrations
The usage guide describes integrations with reviewdog, GitHub Problem Matchers, super-linter, pre-commit, VS Code, Emacs, Vim and Neovim, Pulsar Edit, Nova, and trunk. source
Expression checks
It strongly type-checks `${{ }}` expressions to catch semantic errors such as missing properties and type mismatches. source
Go library
The project provides Go APIs for using actionlint from a Go program. source
Install and run
The project documents prebuilt binaries, Docker, building from source, a CI download script, and package-manager installation options. source
License
The project is distributed under the MIT license. source
Online playground
The browser playground runs actionlint through WebAssembly and states that it never sends data outside the browser. source
Purpose
actionlint is a static checker for GitHub Actions workflow files. source
Security checks
Its security checks include detecting script injection risks from untrusted inputs and hard-coded credentials. source
Shell and Python integrations
It can integrate ShellCheck and Pyflakes for scripts in `run:` steps; these integrations can be disabled. source
Support and feedback
The README invites bug reports and feedback, including feature requests and ideas for additional checks, through GitHub issues. source
Workflow checks
It checks workflow syntax, including unexpected or missing keys. source

Checked against the maker's pages on 11 Oct 2026.