ci-cd-pipeline-builder
Pass
Audited by Gen Agent Trust Hub on Nov 12, 2026
Risk Level: SAFECREDENTIALS_UNSAFEINDIRECT_PROMPT_INJECTIONEXTERNAL_DOWNLOADS
Full Analysis
- [CREDENTIALS_UNSAFE]: The sample workflow file
assets/sample_workflows/flawed-ci.ymlcontains a mock hardcoded GitHub token (ghp_...). Although intended as test data for the provided linter script, it demonstrates the pattern of hardcoding sensitive credentials in CI configuration files. - [INDIRECT_PROMPT_INJECTION]: The
pipeline_generator.pyscript reads the default branch name from the local.git/HEADfile and interpolates it into the generated pipeline YAML and GitHub Actionsifexpressions without sanitization. A maliciously crafted branch name could be used to inject arbitrary YAML keys or modify deployment logic in the generated CI/CD workflows. - Ingestion points: Reads branch information from
.git/HEADor user-provided CLI arguments inpipeline_generator.py. - Boundary markers: None; the branch string is directly inserted into template strings.
- Capability inventory: Generates executable YAML pipelines for GitHub Actions and GitLab CI; these pipelines can execute arbitrary shell commands and interact with secrets.
- Sanitization: Absent; the script performs simple string replacement without validation of the branch name's format or characters.
- [EXTERNAL_DOWNLOADS]: The generated CI/CD templates reference official actions and tools from well-known organizations such as GitHub, Docker, pnpm, and Astral for standard pipeline operations.
Audit Metadata