rhysd/actionlint

:octocat: Static checker for GitHub Actions workflow files

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 minute ago
Added to GitGenius on September 16th, 2026
Created on May 25th, 2021
Open Issues & Pull Requests: 190 (+0)
GitHub issues: Enabled
Number of forks: 272
Total Stargazers: 4,250 (+1)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 days
Mean response time: 63.1 days
90th percentile: 227.7 days
Tracked items: 145

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 43% of issues opened in the past year have been closed. Three people close 77% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 94
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 546 days
Stale 30+ days: 73
Stale 90+ days: 56

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 2
Events in 7 days: 3

Top labels

  • enhancement (16)
  • bug (9)
  • question (4)
  • help wanted (3)
  • not-reproducible (2)
  • duplicate (1)
  • false-positive (1)
  • invalid (1)

Detailed Description

actionlint is a static linter for GitHub Actions workflow files.

The tool addresses the problem of catching errors in GitHub Actions YAML workflows before they run in CI. It parses workflow files and performs static analysis to detect issues such as syntax errors, undefined environment variables, type mismatches, and references to non-existent actions or steps. The linter works by analyzing the structure and content of workflow YAML against the GitHub Actions schema and common patterns, providing developers with immediate feedback during development rather than discovering problems only when workflows execute.

Teams using GitHub Actions should adopt actionlint if they want to shift left on workflow validation and reduce failed CI runs caused by configuration mistakes. It suits projects of any size that rely on GitHub Actions for automation, particularly those with complex or numerous workflows where manual review becomes error-prone. The tool integrates into local development environments and CI pipelines, allowing developers to catch issues before committing workflow changes.

The project shows consistent maintenance with regular updates addressing edge cases and expanding rule coverage. Development activity demonstrates responsiveness to user-reported issues and a pattern of incremental improvements to the linter's accuracy and capabilities. The maintainer actively refines the tool's detection logic and expands support for GitHub Actions features as the platform evolves.