validate-pipeline

You can validate GitHub Actions workflows by parsing the YAML configuration to detect syntax errors, identify missing required stages, and scan for hardcoded credentials to ensure CI/CD security and compliance. This generates a structured findings report.

Pipeline validation checks YAML files for syntax correctness, required stage presence, security vulnerabilities like hardcoded secrets, and un-gated deployment steps. It also provides warnings for missing dependency caching and info on parallelism.

Yes, pipeline validation applies to YAML-based pipeline definitions for both GitHub Actions and GitLab CI. It operates project-agnostically by integrating with workspace discovery to validate syntax, security vulnerabilities, and project standard adherence.

To check for hardcoded credentials before merging, validate the CI/CD configuration file to scan for security vulnerabilities and un-gated deploy steps. This generates CRITICAL findings to prevent broken deployments and mitigate security risks.

The best way to lint YAML pipeline definitions for project standard adherence is to validate the configuration for syntax correctness, required stage presence, and security vulnerabilities. This identifies missing stages and ensures pre-merge code review compliance.

Pipeline validation reports warnings for missing dependency caching because it checks for optimization opportunities alongside critical errors. It flags absent caching and missing pytest runs to help maintain pipeline efficiency and project standard adherence.