# CI/CD Pipeline Security Scanner

> CI/CD Pipeline Security Scanner is a paid API for AI agents from api.agentstools.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Statically analyzes GitHub Actions, GitLab CI, or CircleCI pipeline configs for security vulnerabilities and returns a verdict, risk score, and per-finding remediation hints.

## Facts

- Endpoint: POST https://api.agentstools.dev/ci/scan
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ci-cd-pipeline-security-scanner-d393a43a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wtvUiNW0VWCCVcrHvPvjs

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability ci-cd-pipeline-security-scanner-d393a43a -d '<json body>'
```

Example prompt: Can you scan my GitHub Actions workflow YAML for security issues — I want to know if there are unpinned actions, dangerous triggers, or leaked secrets, and get a pass/caution/block verdict with a risk score?

## When to prefer this

Use this endpoint when you need a fast, structured security verdict on a CI/CD config before merging or deploying — especially when you want per-finding rule citations and actionable fix hints rather than a generic linter output. It is purpose-built for GitHub Actions, GitLab CI, and CircleCI and targets supply-chain-specific risks like unpinned actions, injection, and token over-permissioning that general YAML validators miss.

## Known failure modes

- Unsupported CI platform type returns an error
- Malformed or unparseable YAML returns a parse error
- Empty or missing config body results in a validation error
- Very large config files may time out
- Ambiguous YAML that passes parsing but is semantically invalid may produce incomplete findings

## How this service works

Static security scan of a CI/CD pipeline config: GitHub Actions, GitLab CI or CircleCI. Detects unpinned actions / images / orbs, template and environment injection, dangerous triggers, over-broad workflow-token permissions, secrets leaked to logs, cache poisoning and more. Returns a verdict (pass, caution, block), a 0-100 risk score and per-finding rule, severity, object, location and a concrete fix hint. Security indicators, not a guarantee.

## Output

Returns a verdict of 'pass', 'caution', or 'block', a numeric risk score from 0 to 100, and a list of per-finding objects each containing the rule name, severity, affected object, location in the file, and a concrete fix hint. Security indicators only, not a guarantee of safety.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "format": {
   "enum": [
    "auto",
    "github-actions",
    "gitlab-ci",
    "circleci"
   ],
   "type": "string",
   "description": "CI system, or auto to detect from the content"
  },
  "content": {
   "type": "string",
   "description": "The CI/CD config text to scan (workflow file)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ci-cd-pipeline-security-scanner-d393a43a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agentstools.dev](https://www.zero.xyz/host/api.agentstools.dev/llms.txt)