Skip to content

Category

CI/CD tools.

Validate and harden your pipeline configuration before it runs.

3toolsAll tools

CI/CD tools

  • CI/CDLive

    GitHub Actions Validator

    Check workflow YAML errors & security issues online — no install.

    Paste a GitHub Actions workflow and get YAML errors plus security-misconfiguration checks, instantly, with nothing to install.

    Open tool
  • CI/CDLive

    GitHub Actions Expression Tester

    Evaluate ${{ }} expressions and simulate workflow triggers.

    Test GitHub Actions if: conditions with GitHub’s exact coercion rules, catch the “always true” literal footgun, and simulate which jobs run for a push, PR or tag. Pure client-side.

    Open tool
  • CI/CDLive

    GitLab CI Validator

    Lint .gitlab-ci.yml for YAML errors and pipeline misconfigurations — in your browser, no login.

    A free gitlab ci validator that lints your .gitlab-ci.yml for YAML errors plus structural and pipeline misconfigurations — undefined stages, jobs without scripts, bad rules / needs / extends. Runs entirely in your browser, no login.

    Open tool

When you reach for CI/CD tools.

Pipeline configuration is code that only runs in production. There is no local execution, no type checker, and the feedback loop is a push, a wait, and a red X — which is why the average workflow accumulates a long tail of things that look right and are not.

The GitHub Actions expression footgun is the canonical example. Write if: ${{ github.event_name }} == 'push' and the runner substitutes the value, leaves the comparison as literal text, and evaluates a non-empty string — which is truthy. The step runs on every event. It has never once done what it looks like it does, and it has been an open issue since 2021.

These validate the YAML, flag the security misconfigurations linters usually skip, and — for expressions specifically — tell you the actual value GitHub would compute, using GitHub's coercion rules rather than JavaScript's.

Back to all tools