GitHub Actions Validator

Check a GitHub Actions workflow for unknown keys, broken job needs, old or unpinned actions, missing runs-on and script injection risks.

Processed on your device. Files are not uploaded

How to check a workflow file

  1. Paste your workflow YAML

    Paste or type your workflow YAML into the box, or press Try an example.

  2. Read the problems

    Errors stop the workflow from running; warnings are risks and old versions.

  3. Fix and push

    Fewer failed runs while you get the YAML right.

When to use GitHub Actions Validator

A workflow does not start at all after a push, which usually means GitHub could not parse it.

You are reviewing a pull request that changes CI and want to catch risky patterns before they merge.

Tips for a better GitHub Actions Validator result

Pin third-party actions to a full commit SHA in sensitive workflows; a tag can be moved to point at different code.

Add timeout-minutes to every job so a hung test does not use six hours of runner time.

GitHub Actions Validator: limits and what to check

Expressions in double braces are only checked for balanced brackets, so a misspelled context name will still pass here.

Reusable workflows and composite actions in other repositories are not fetched, so their inputs are not checked.

About GitHub Actions Validator

Catch workflow mistakes before you push and wait for a failed run. Keys are checked at every level with suggestions for typos, job needs must point to real jobs with no loops, steps need either uses or run, and actions should be pinned to a version. Security checks flag event text pasted into shell commands and risky pull_request_target checkouts.

FAQs

Why warn about permissions?

Without a permissions block, the GITHUB_TOKEN gets the repository's default, which may be write access to everything.

Why is actions/checkout@v2 flagged?

Old major versions of the official actions run on retired Node.js versions and will stop working.

What is script injection?

Putting an expression such as github.event.issue.title straight into a run script lets anyone who opens an issue run commands. Pass it through env instead.

Related tools