pipeline-check 1.0.1

CI/CD Security Posture Scanner — scores AWS, Terraform, CloudFormation, GitHub Actions, GitLab CI, Azure DevOps, Bitbucket Pipelines, Jenkins, CircleCI, Google Cloud Build, Dockerfile, Kubernetes manifests, and Helm charts against OWASP Top 10 CI/CD Risks

Pipeline-Check

Find security risks in your CI/CD pipelines before attackers do.

Full documentation: https://dmartinochoa.github.io/pipeline-check/

Pipeline-Check is a security scanner for GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure DevOps, Bitbucket Pipelines, Buildkite, Drone, Tekton, Argo Workflows, and Google Cloud Build, plus Terraform, CloudFormation, Kubernetes, Helm, Dockerfile, OCI image manifests, and live AWS accounts. It maps every finding to the OWASP Top 10 CI/CD Security Risks, SLSA, NIST SSDF, PCI DSS, SOC 2, and nine other frameworks, and scores each scan A through D so you can gate merges on the result.

590+ checks across 19 providers, mapped to 14 compliance standards, with 111 autofixers, plus 36 attack chains correlating findings into MITRE ATT&CK-mapped kill chains. A dataflow taint engine catches multi-step and cross-job propagation that single-rule scanners miss.

Quick start | Usage guide | Providers | How it works | CI integration | Compliance | vs. Checkov / KICS / Semgrep | Docs

---

🚀 Quick start

pip install pipeline-check          # Python >= 3.10

pipeline_check                      # auto-detects every provider in cwd
pipeline_check init                 # scaffold .pipeline-check.yml
pipeline_check -p github -o json    # short flags work too
pipeline_check --pipeline aws       # force the live-AWS scan

Or run from the published container image (no Python install needed):

# Docker Hub
docker run --rm -v "$PWD:/scan" dmartinochoa/pipeline-check

# GHCR (same image, different registry)
docker run --rm -v "$PWD:/scan" ghcr.io/dmartinochoa/pipeline-check

The image is multi-arch (linux/amd64 + linux/arm64), ships with SLSA build provenance and an SBOM attached to the manifest, and is tagged per release (:0.5.0), per commit (:sha-<short>), and :latest on master. /scan is the image working directory, so mounting your repo there lets auto-detect Just Work.

Run pipeline_check with no flags in any supported repo. It walks the working directory for every supported provider's canonical file (.github/workflows/, .gitlab-ci.yml, Jenkinsfile, cloudbuild.yaml, Chart.yaml, template.yml, Dockerfile, …). One match runs a single-provider scan; two or more matches automatically switch to multi-provider mode (equivalent to --pipelines X,Y,Z) so cross-provider attack chains (XPC-NNN) fire. Falls back to aws (live account scan) when nothing matches.

No API tokens required. CI configs are parsed from disk; AWS uses the standard boto3 credential chain. The GitHub Actions provider can optionally follow remote reusable-workflow refs over HTTPS via --resolve-remote (off by default; see docs/providers/github.md for the full opt-in surface).

PR review comments

Pipe findings into pull-request review comments on the changed lines via the bundled composite action:

on: pull_request
permissions:
  contents: read
  pull-requests: write
jobs:
  scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: dmartinochoa/pipeline-check/.github/actions/pipeline-check-pr@v1
        with:
          severity-threshold: MEDIUM

Each finding lands as a review comment on its precise line (when the rule emits a Location); everything else goes into a single PR-level summary comment. See .github/actions/pipeline-check-pr/README.md for inputs, idempotency, and fork-PR fallback behavior.

---

🧩 Supported providers

Provider	Input	Auto-detect	Checks
AWS	Live account via boto3	--region	71 checks (CodeBuild, CodePipeline, CodeDeploy, ECR, IAM, PBAC, S3, CloudTrail, CloudWatch Logs, Secrets Manager, CodeArtifact, CodeCommit, Lambda, KMS, SSM, EventBridge, Signer)
Terraform	terraform show -json plan	--tf-plan	AWS-parity shift-left checks, pre-provisioning
CloudFormation	YAML or JSON template	--cfn-template	~63 AWS-parity shift-left checks; handles !Ref/!Sub/!GetAtt intrinsics (treats unresolved values as strict)
GitHub Actions	.github/workflows/*.yml	--gha-path	46 checks (GHA-001--043, plus TAINT-001..003). GHA-040 consults a curated registry of known-compromised action refs (CVE-2025-30066 et al.). GHA-041..043 form the action-reputation pack: single-maintainer / very-young repo / low-star + sensitive-permission detection behind --resolve-remote.
GitLab CI	.gitlab-ci.yml	--gitlab-path	33 checks (GL-001--033, plus TAINT-004 and TAINT-008)
Bitbucket Pipelines	bitbucket-pipelines.yml	--bitbucket-path	29 checks (BB-001--029)
Azure DevOps	azure-pipelines.yml	--azure-path	30 checks (ADO-001--030)
Jenkins	Jenkinsfile (Declarative/Scripted)	--jenkinsfile-path	32 checks (JF-001--032)
CircleCI	.circleci/config.yml	--circleci-path	31 checks (CC-001--031)
Google Cloud Build	cloudbuild.yaml	--cloudbuild-path	26 checks (GCB-001--026)
Buildkite	.buildkite/pipeline.yml	--buildkite-path	16 checks (BK-001--015, plus TAINT-005)
Drone CI	.drone.yml / .drone.yaml	--drone-path	11 checks (DR-001--011): image / plugin pinning, privileged steps, ${DRONE_*} injection, literal secrets, TLS bypass, sensitive host-path mount, pull: never policy, tainted cache key, unpinned package install, runner-targeting node map
Tekton	Task / Pipeline / *Run YAML	--tekton-path	16 checks (TKN-001--015, plus TAINT-006)
Argo Workflows	Workflow / WorkflowTemplate YAML	--argo-path	16 checks (ARGO-001--015, plus TAINT-007)
Dockerfile	Dockerfile / Containerfile	--dockerfile-path	20 checks (DF-001--020)
Kubernetes	Manifest YAML (Deployment, Pod, …)	--k8s-path	40 checks (K8S-001--040)
Helm	Chart directory (Chart.yaml) or .tgz	--helm-path	Renders via helm template, runs the 40 K8S-* rules on the result, plus 10 chart-supply-chain rules (HELM-001--010) read straight off Chart.yaml / Chart.lock. Requires helm (Helm 3) on PATH.
OCI image manifest	docker buildx imagetools inspect --raw <ref> JSON	--oci-manifest	11 checks (OCI-001--008 plus ATTEST-001..003): provenance annotations, build attestations (SLSA / SBOM), image.created timestamp, foreign-layer URL refs, license annotation, layer-count hygiene, legacy schemaVersion 1, weak (non-sha256) digest, builder identity, source-repo claim, SBOM floating versions
SCM (GitHub / GitLab / Bitbucket)	Platform REST API (--scm-platform github|gitlab|bitbucket --scm-repo …)	--scm-repo	19 checks (SCM-001--019). GitHub: full pack — branch protection presence / required reviews / required status checks / signed commits / force-push denial / deletion denial / admin enforcement; CODEOWNERS reviews + file presence / stale-review dismissal / conversation resolution / last-push approval; default code scanning, secret scanning + push protection, Dependabot security updates, private vulnerability reporting; PR-review bypass allowance + push-restriction allowlist auditing. GitLab and Bitbucket: 7-rule universal subset (SCM-001/002/006/007/008/009/017). Hermetic mode: --scm-fixture-dir DIR reads JSON responses from disk instead of hitting the network.

Each CI provider checks for: dependency pinning, script injection, credential leaks, deploy approval gates, artifact signing, SBOM generation, Docker security, package integrity, timeout enforcement, vulnerability scanning, TLS verification, and more. The Kubernetes provider focuses on workload posture (image digest pinning, securityContext, hostPath / host-namespace exposure, RBAC blast radius, Secret hygiene). The Helm provider renders charts via helm template and runs the Kubernetes rule pack on the result, plus ten chart-supply-chain rules (HELM-001--010: legacy apiVersion: v1, missing Chart.lock digests, non-HTTPS dependency / home / sources URLs, non-pinned dependency versions, missing maintainers / description / appVersion, missing kubeVersion range, stale Chart.lock > 90 days) read straight off the on-disk chart files. See docs/providers/ for the full per-check reference.

---

⚙️ How it works

                 +-----------+
  Config files   |  Scanner  |   590+ checks across 19 providers
  or live APIs ---->         +---> Findings (check_id, severity, resource)
                 +-----------+
                       |
                 +-----------+
                 |  Scorer   |   Severity-weighted: CRITICAL=20, HIGH=10, MED=5, LOW=2
                 |           +---> Score 0-100, Grade A/B/C/D
                 +-----------+
                       |
                 +-----------+
                 |   Gate    |   --fail-on, --min-grade, --max-failures, --baseline
                 |           +---> Exit 0 (pass) or 1 (fail)
                 +-----------+
                       |
                 +-----------+
                 | Reporter  |   Terminal, JSON, HTML, SARIF 2.1.0
                 +-----------+

Every finding is annotated with compliance controls from all enabled standards, so a single scan satisfies multiple audit frameworks.

---

⭐ Key features

Feature	Description
Autofix	--fix emits unified-diff patches; --fix --apply writes in place. 111 fixers cover script injection, secrets, timeouts, pinning, Docker flags, TLS, Kubernetes securityContext, Cloud Build options, Helm chart-supply-chain TODOs, and more.
CI gate	--fail-on HIGH, --min-grade B, --max-failures 5, --fail-on-check GHA-002. Any condition trips exit 1.
Baselines	--baseline prior.json or --baseline-from-git origin/main:report.json. Only gate on new findings.
Diff-mode	--diff-base origin/main scans only files changed by the branch.
Suppressions	.pipelinecheckignore (flat or YAML with expires: dates).
Custom secrets	--secret-pattern '^acme_[a-f0-9]{32}$' extends the credential scanner.
Glob selection	--checks 'GHA-*' or --checks '*-008' to scope checks.
Standard audit	--standard-report nist_ssdf prints the control-to-check matrix and coverage gaps.
Custom rule DSL	--custom-rules PATH loads YAML-defined rules that run alongside the built-in catalog. Supports GHA, GitLab, Bitbucket, Azure, CircleCI, Cloud Build, Kubernetes, and Helm. Rule shape: for_each: jsonpath + assert: predicate (eq / regex / exists / len_gt / all_of / not / …). Findings flow through the same scoring, gating, and SARIF as built-ins. See docs/writing_a_custom_rule.md.
Component inventory	--inventory emits the list of resources / workflows / templates the scanner discovered, with per-type metadata (encryption, runtime, tags, lifecycle policies). Filter with --inventory-type 'AWS::IAM::*'; skip checks entirely with --inventory-only. Feeds asset-register dashboards and drift detectors.
STRIDE threat model	--output threatmodel emits a self-contained Markdown threat-model document populated from the scan + inventory: assets, trust boundaries, findings grouped by STRIDE category, implemented controls, top-25 risk register. Mapping is derived from each rule's existing OWASP / CWE tags so re-policing is one table swap. Shaped for SOC 2 / PCI / NIST SSDF evidence packages.
MCP server	pipeline_check --serve runs as a Model Context Protocol server on stdio so AI clients (Claude Desktop, Claude Code, Cursor, Continue, Zed) can drive scans and introspect the rule catalog directly. Ten tools advertised: scan / inventory / explain_check / list_chains / threat_model / etc. The mcp SDK is an optional [mcp] extra so the default install stays slim. See docs/mcp.md.
Multi-scanner SARIF ingest	--ingest <file>.sarif (repeatable) absorbs findings from Trivy / Checkov / Snyk / KICS / CodeQL / any conformant scanner. External rules become INGEST-<tool>-<rule-id> Finding rows; the chain engine RE-EVALUATES over the union, so cross-tool chains (e.g. XPC-009 — ingested CVE finding + DF-001 mutable runtime image) fire on compositions no individual scanner would surface. Caps: 25 MiB / 5,000 results per file.
Vulnerable-by-design benchmark	bench/ ships intentionally-vulnerable fixtures (one folder per attack pattern, anchored to a real-world incident) plus a runner that asserts pipeline-check fires on every expected check ID. python bench/run.py prints a recall table; the same harness gates the CI suite. Demonstrates 100 % recall across the OWASP CICD-SEC top patterns; future cross-scanner matrix vs Zizmor / Poutine / Checkov / KICS / Trivy is tracked under bench/COMPARISON.md.

---

📤 Output formats

pipeline_check --output terminal            # rich table to stdout (default)
pipeline_check --output json                # machine-readable JSON
pipeline_check --output html --output-file report.html       # self-contained HTML
pipeline_check --output sarif --output-file scan.sarif       # SARIF 2.1.0 for GitHub/GitLab
pipeline_check --output junit --output-file junit.xml        # JUnit XML for test-runner UIs
pipeline_check --output markdown            # PR-comment shape (GFM)
pipeline_check --output threatmodel --output-file threats.md # STRIDE threat model
pipeline_check --output both                # terminal on stderr + JSON on stdout

---

🔁 CI integration

GitHub Actions

The marketplace action wraps install, scan, gate, and SARIF upload in one step. Findings show up in the GitHub Security tab.

permissions:
  contents: read
  security-events: write   # required by upload-sarif

jobs:
  scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: dmartinochoa/pipeline-check@v1
        with:
          pipeline: auto       # or: github, gitlab, terraform, k8s, ...
          fail-on: HIGH

Inputs (all optional): pipeline, path, fail-on, min-grade, max-failures, severity-threshold, baseline, baseline-from-git, diff-base, standard, output, output-file, upload-sarif, pipeline-check-version, python-version, resolve-remote, extra-args. Outputs: exit-code, findings-count, failed-count, score, grade, sarif-file. See action.yml for the full surface.

For PR review comments on the changed lines, see the companion pipeline-check-pr action.

For finer control, the manual three-step form still works:

- run: pip install pipeline-check
- run: pipeline_check --pipeline github --output sarif --output-file pipeline-check.sarif --fail-on HIGH
- if: always()
  uses: github/codeql-action/upload-sarif@v3
  with:
    sarif_file: pipeline-check.sarif

GitLab CI

security-scan:
  script:
    - pip install pipeline-check
    - pipeline_check --pipeline gitlab --fail-on HIGH --output json > report.json
  artifacts:
    reports:
      sast: report.json

Any CI system

# Gate on grade
pipeline_check --pipeline github --min-grade B

# Gate on new findings only (baseline diff)
pipeline_check --pipeline github --fail-on HIGH \
  --baseline-from-git origin/main:baseline.json

Exit codes: 0 = pass, 1 = gate failed, 2 = scanner error, 3 = config error.

Pre-commit

pipeline_check ships hook definitions for the pre-commit framework. Each hook is scoped to one provider so a Dockerfile change doesn't run the GitHub Actions scanner. Enable just the hooks for the providers your repo ships through:

# .pre-commit-config.yaml
repos:
  - repo: https://github.com/dmartinochoa/pipeline-check
    rev: v0.5.0   # pin to a release tag
    hooks:
      - id: pipeline-check-github
      - id: pipeline-check-dockerfile

All hooks default to --fail-on HIGH. Override with args: for a softer gate (e.g. args: [--fail-on, CRITICAL]).

---

🛠️ Configuration

Every CLI flag can be set in pyproject.toml, .pipeline-check.yml, or environment variables. Precedence: CLI > env > file > defaults.

# pyproject.toml
[tool.pipeline_check]
pipeline = "github"
severity_threshold = "MEDIUM"

[tool.pipeline_check.gate]
fail_on = "HIGH"
baseline = "artifacts/baseline.json"
ignore_file = ".pipelinecheckignore"

Full reference: docs/config.md.

---

📋 Compliance standards

Each finding is tagged with controls from all enabled frameworks. One scan covers multiple audits.

Standard	Version	Coverage
OWASP Top 10 CI/CD Security Risks	2022	10/10 risks
SLSA Build Track	1.0	6/7 levels (110 check mappings)
NIST SSDF (SP 800-218)	v1.1	CI/CD subset
NIST SP 800-53	Rev. 5	CI/CD subset
NIST SP 800-190	2017	Container CI/CD subset
NIST CSF 2.0	2.0	CI/CD subset
CIS Software Supply Chain	1.0	CI/CD subset
CIS AWS Foundations	3.0.0	CI/CD subset
PCI DSS v4.0	4.0	CI/CD subset
SOC 2 Trust Services Criteria	2017 (rev. 2022)	CC6/CC7/CC8 subset
NSA/CISA ESF Supply Chain	2022	CI/CD subset
OpenSSF Scorecard	v5	CI/CD subset
Microsoft S2C2F	2024-05	CI/CD subset

# Explore a standard's control-to-check matrix
pipeline_check --standard-report slsa

# Restrict a scan to specific standards
pipeline_check --standard owasp_cicd_top_10 --standard nist_ssdf

Standards are pure data. Adding SOC 2 or an internal policy is one Python module. See docs/standards/.

---

💻 CLI reference

Flag	Default	Description
--pipeline / -p	auto	auto (detect from cwd), aws, terraform, cloudformation, github, gitlab, bitbucket, azure, jenkins, circleci, cloudbuild, buildkite, drone, tekton, argo, dockerfile, kubernetes, helm, oci, scm
--pipelines		Comma-separated multi-provider list (e.g. --pipelines github,oci). Mutually exclusive with --pipeline. Activates cross-provider attack chains (XPC-NNN) by evaluating the chain engine over the union of every sub-scan's findings.
--output / -o	terminal	terminal, json, html, sarif, junit, markdown, both
--output-file / -O		Required with html; optional with sarif
--fail-on / -f		Fail if any finding >= severity (CRITICAL, HIGH, MEDIUM, LOW)
--min-grade		Fail if grade worse than A/B/C/D
--max-failures		Fail if > N effective findings
--fail-on-check		Fail if named check fails (repeat for multiple)
--baseline		Prior JSON report; existing findings don't gate
--baseline-from-git		REF:PATH. Resolves baseline via git show
--ignore-file	.pipelinecheckignore	Suppressions (flat or YAML with expires:)
--diff-base		Only scan files changed vs this git ref
--fix		Emit unified-diff patches to stdout
--apply		With --fix, write patches in place
--checks / -c	all	Check ID(s) or globs (GHA-*, *-008)
--severity-threshold	INFO	Minimum severity to display
--secret-pattern		Extra regex for credential scanning (repeat)
--custom-rules		YAML rule file or directory of rule files; loaded alongside the built-in catalog (repeatable)
--standard	all	Standard(s) to annotate findings with
--standard-report		Print control-to-check matrix and exit
--inventory		Emit scanned-component inventory alongside findings
--inventory-type		Glob pattern to scope inventory by type (repeatable, implies --inventory)
--inventory-only		Skip checks; emit inventory only (implies --inventory)
--ingest		SARIF 2.1.0 file from another scanner (Trivy, Checkov, Snyk, KICS, CodeQL, …). External rules become INGEST-<tool>-<rule-id> findings; chain engine re-evaluates over the union. Repeatable.
--scm-platform		SCM platform for --pipeline scm: github (full 19-rule pack), gitlab, or bitbucket (each gets a 7-rule universal subset)
--scm-repo		Repository to scan: owner/name (GitHub), group/subgroup/project (GitLab — nested subgroups OK), or workspace/repo_slug (Bitbucket Cloud)
--scm-fixture-dir		Read SCM API responses from JSON files under DIR instead of hitting the network. Useful for offline tests / CI runs without a token.
--gh-token	$GITHUB_TOKEN	Token for the GHA reusable-workflow resolver and the SCM provider's REST API calls
--resolve-remote		Follow remote uses: refs (reusable workflows + composite actions) over HTTPS. Off by default; opt in to take on the network surface.
--config	auto	Config file path (TOML or YAML)
--config-check		Validate config, exit non-zero on unknown keys
--man [TOPIC]		Extended docs (gate, autofix, diff, secrets, standards, config, output, lambda, recipes)
--region / -r	us-east-1	AWS region
--profile		AWS CLI named profile
--verbose / -v		Debug output to stderr
--quiet / -q		Suppress all output; exit code only
--version		Print version

Provider-specific path flags (--gha-path, --gitlab-path, --bitbucket-path, --cfn-template, --azure-path, --jenkinsfile-path, --circleci-path, --tf-plan, --cloudbuild-path, --buildkite-path, --drone-path, --tekton-path, --argo-path, --dockerfile-path, --k8s-path, --helm-path, --oci-manifest) are auto-detected from the working directory when omitted. The Helm provider also takes --helm-values FILE and --helm-set KEY=VALUE (both repeatable), forwarded to helm template. The SCM provider is API-only and takes --scm-platform github --scm-repo owner/name (plus --gh-token or $GITHUB_TOKEN); no on-disk path flag.

Subcommand: pipeline_check init writes a starter .pipeline-check.yml to the current directory, pre-filling the pipeline: key based on what it finds in cwd. Pass --path PATH to redirect the output, or --force to overwrite an existing file.

---

🏛️ Architecture

pipeline_check/
├── cli.py                     # Click CLI
├── lambda_handler.py          # AWS Lambda entry point
└── core/
    ├── scanner.py             # Provider-agnostic orchestrator
    ├── scorer.py              # Severity-weighted scoring (A/B/C/D)
    ├── gate.py                # CI gate (pass/fail thresholds + baselines)
    ├── autofix.py             # 111 fixers (text-based, comment-preserving)
    ├── reporter.py            # Terminal + JSON
    ├── html_reporter.py       # Self-contained HTML
    ├── sarif_reporter.py      # SARIF 2.1.0
    ├── config.py              # TOML/YAML/env config loader
    ├── providers/             # One module per provider (register + go)
    ├── standards/data/        # One module per compliance standard
    └── checks/
        ├── base.py            # Finding, Severity, shared detection patterns
        ├── aws/rules/         # 71 rule-based checks (CB, CP, CD, ECR, IAM, PBAC, S3, CT, CWL, SM, CA, CCM, LMB, KMS, SSM, EB, SIGN, CW)
        ├── terraform/         # AWS-parity checks against plan JSON
        ├── cloudformation/    # AWS-parity checks against CFN templates (YAML/JSON)
        ├── github/rules/      # GHA-001 .. GHA-046 + TAINT-001..003
        ├── gitlab/rules/      # GL-001 .. GL-033 + TAINT-004 / TAINT-008
        ├── bitbucket/rules/   # BB-001 .. BB-029
        ├── azure/rules/       # ADO-001 .. ADO-030
        ├── jenkins/rules/     # JF-001 .. JF-032
        ├── circleci/rules/    # CC-001 .. CC-031
        ├── cloudbuild/rules/  # GCB-001 .. GCB-026
        ├── buildkite/rules/   # BK-001 .. BK-015 + TAINT-005
        ├── drone/rules/       # DR-001 .. DR-011
        ├── tekton/rules/      # TKN-001 .. TKN-015 + TAINT-006
        ├── argo/rules/        # ARGO-001 .. ARGO-015 + TAINT-007
        ├── oci/rules/         # OCI-001 .. OCI-008 + ATTEST-001..003
        ├── dockerfile/rules/  # DF-001 .. DF-020
        ├── kubernetes/rules/  # K8S-001 .. K8S-040
        ├── helm/              # Renders charts; reuses the K8s rule pack
        ├── scm/rules/         # SCM-001 .. SCM-019 — repo governance via the platform REST API (GitHub full pack; GitLab + Bitbucket universal subset)
        └── custom/            # YAML rule loader + predicate engine

Adding a new check is a one-file change. Adding a new provider is three files. See docs/providers/ for the full pattern.

---

🐍 Python API

Embed pipeline-check in your own tooling without subprocess + JSON parsing. The top-level surface is small and stable across minor releases:

from pipeline_check import Scanner, Severity, score

scanner = Scanner(pipeline="github", gha_path=".github/workflows")
findings = scanner.run()

critical = [
    f for f in findings
    if not f.passed and f.severity is Severity.CRITICAL
]
result = score(findings)
print(f"score={result['score']} grade={result['grade']}")

Public surface: Scanner, Finding, Severity, Confidence, ControlRef, score, ScoreResult, Chain, ChainRule, evaluate_chains, list_chain_rules, available_providers(), available_standards(), load_custom_rules(), LoadedCustomRules, CustomRuleError, __version__. Anything reached through pipeline_check.core.* is internal and may move between releases.

---

☁️ Lambda deployment

Pipeline-Check can run as an AWS Lambda for scheduled scans. Run pipeline_check --man lambda for packaging, IAM permissions, event payload shapes, and SNS alerting.

---

🔌 Extending

New check: Drop a module in checks/<provider>/rules/ exporting RULE and check(). The orchestrator auto-discovers it.

New provider: Subclass BaseProvider, register in providers/__init__.py. Available via --pipeline <name> immediately.

New standard: Add a Python module under standards/data/ with a STANDARD object. The CLI and reporters pick it up automatically.

See docs/providers/README.md for the full contract.

---

🔐 Verifying a release

Every tagged release ships a SLSA Build L3 provenance attestation alongside the sdist and wheel. The attestation is generated by the slsa-framework/slsa-github-generator reusable workflow running in GitHub's isolated builder, signed via Sigstore using a short-lived OIDC token, and attached to the GitHub release as pipeline-check.intoto.jsonl. It proves the wheel you're about to install was built from this repository at the tagged commit, by this project's CI, and not falsifiable by anyone who later steals a maintainer's PyPI token.

To verify before installing:

# 1. Install slsa-verifier (one-off).
go install github.com/slsa-framework/slsa-verifier/v2/cli/slsa-verifier@v2.7.0

# 2. Download the wheel and the matching provenance file from the
#    GitHub release for the version you want.
TAG=v0.5.0
gh release download "$TAG" \
  --repo dmartinochoa/pipeline-check \
  --pattern '*.whl' \
  --pattern 'pipeline-check.intoto.jsonl'

# 3. Verify. slsa-verifier checks the attestation's Sigstore
#    signature, the source repo, and the source tag against the
#    builder's claims.
slsa-verifier verify-artifact pipeline_check-*.whl \
  --provenance-path pipeline-check.intoto.jsonl \
  --source-uri github.com/dmartinochoa/pipeline-check \
  --source-tag "$TAG"

# 4. Once verification passes, install the verified wheel directly.
pip install pipeline_check-*.whl

A passing verification means: the wheel was built by this project's own release.yml workflow, at the tagged commit, in GitHub's isolated SLSA builder, and the bytes you have on disk match the ones the builder signed. Skip this step and you trust PyPI, the network, and every cache in between.

PyPI's own PEP 740 attestations are produced separately at publish time (visible on the project's PyPI page); the SLSA provenance is the build-time attestation and is the stronger guarantee.

---

📜 License

MIT. See LICENSE.