npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

github-actionlint

v1.7.12

Published

Run rhysd/actionlint from Node.js - downloads the official binary from GitHub Releases

Readme

github-actionlint

npm

Run actionlint—the linter for GitHub Actions workflows—from your Node.js project. No separate install step for a binary: add a dev dependency, wire a script, and catch workflow mistakes before they land on main.


Why this exists

GitHub Actions YAML looks simple until it isn’t: expression contexts, reusable workflows, secrets vs env, shell injection in run: blocks, and copy-pasted paths that only break in CI. actionlint was built to lint those workflows the way ESLint lints JavaScript.

Motivation for this package: many teams already standardize on npm for developer tooling. Installing actionlint through npm means:

  • One toolchainnpm install / pnpm add / yarn add alongside your other devDependencies.
  • No manual binary management on each machine or CI image; the first run downloads the official release for your OS/arch and caches it under ~/.github-actionlint.
  • Pinning—lock the linter version in package-lock.json (or equivalent) so everyone runs the same rules.

Use it locally before you push, in pre-commit hooks, and in CI so broken workflows fail fast.


Credits & upstream documentation

github-actionlint is not a reimplementation: it downloads and runs the official actionlint binary from rhysd/actionlint. All workflow checks, flags, and behavior come from that project.

For authoritative details—every CLI flag, configuration, ignore rules, and editor integrations—use the upstream docs, especially:

  • Usage — command-line options (including -shellcheck / -pyflakes)
  • Checks — what actionlint validates and how optional tools integrate

Optional integrations: shellcheck and pyflakes

actionlint can delegate to external linters for scripts inside run: steps. Per the shellcheck integration and pyflakes integration sections of the upstream checks documentation:

  • By default, actionlint looks for shellcheck and pyflakes on your PATH and uses each one only if it is found. If pyflakes (or shellcheck) is not installed or not on your path, that integration is skipped—actionlint still runs; you simply do not get those extra run:-script checks from the missing tool.
  • GitHub Actions: shellcheck is pre-installed on GitHub-hosted runners (e.g. ubuntu-latest, macos-latest, windows-latest), so shellcheck-backed checks for run: scripts work in CI without extra setup—see the runner image software lists. pyflakes is not included by default; install it in the job (e.g. pip install pyflakes) if you want those checks in Actions.
  • To point at a specific executable, use -shellcheck=/path/to/shellcheck or -pyflakes=/path/to/pyflakes.
  • To turn an integration off explicitly (and avoid spawning those processes), use -shellcheck= or -pyflakes= with an empty value—see Ignore some errors in the upstream usage guide.

On a local machine you may need to install shellcheck and/or pyflakes (e.g. pip install pyflakes) if they are not already on your PATH.


Install

npm install --save-dev github-actionlint

Use it in practice

Add a script to package.json

Most projects add a dedicated script so “check my workflows” is one command:

{
  "scripts": {
    "check:actions": "github-actionlint .github/workflows/"
  }
}

Then:

npm run check:actions

You can combine it with other checks:

{
  "scripts": {
    "check": "npm run check:actions && npm run lint && npm run test",
    "check:actions": "github-actionlint .github/workflows/"
  }
}

CLI examples

# Default: lint workflow files under .github/workflows/
npx github-actionlint .github/workflows/

# More detail
npx github-actionlint -color -verbose .github/workflows/

# Match what you run in CI (paths depend on your repo layout)
npx github-actionlint .github/workflows/*.yaml

Programmatic API

const { actionlint } = require("github-actionlint");

const result = await actionlint({
  args: [".github/workflows/", "-color"],
});
console.log(result.stdout.toString());
console.log(result.stderr.toString());
process.exit(result.code);

Environment variables

| Variable | Description | | ---------------------- | --------------------------------------------- | | ACTIONLINT_BIN | Path to actionlint binary (skip download) | | ACTIONLINT_RELEASE | actionlint version (default: package version) | | ACTIONLINT_CACHE_DIR | Cache directory for downloaded binary | | GITHUB_TOKEN | GitHub token for API rate limits (optional) |


Supported platforms

  • macOS: x64, arm64
  • Linux: x64, arm64, 386, arm
  • Windows: x64, arm64
  • FreeBSD: 386, amd64

Versioning

This package tracks rhysd/actionlint releases: the npm version matches the actionlint version it bundles. When upstream ships a new release, github-actionlint publishes a matching version so you stay aligned with the official linter.


Releasing & maintenance

Maintainers: see RELEASING.md for automated upstream sync, GitHub Releases, and npm publishing (including Trusted Publishers / OIDC).

License

MIT