Use OpenThunder in CI

Run the same verdict that gates your local commits in your pipeline, so nothing merges without evidence. OpenThunder ships as a GitHub Action, a GitLab component, and an Azure DevOps task; the checks are keyless and deterministic, so they run without an AI key.

Gate a merge

Two checks catch most of what AI-authored changes get wrong:

openthunder can-i-ship        # SHIP / CAUTION / HOLD verdict with file:line evidence
openthunder security check    # fails on new critical findings, secrets, or unauthenticated protected routes

Fail the job on HOLD (and on a non-zero security check) to block the merge. Attach the Evidence Pack to the pull request so reviewers see what was checked, not just a green tick:

openthunder pr-evidence

Scaffold the workflow

For a ready-made GitHub Actions workflow that scans, optionally publishes to the Cloud, and gates:

openthunder cloud ci-init

Publish results to the Cloud (optional, privacy-first)

If your team uses OpenThunder Cloud, publish the scan result , not your source , for trends and shared visibility:

openthunder cloud publish

Raw code is never uploaded by default; the Cloud receives derived results only. See OpenThunder Cloud and the Privacy FAQ.