Back to Documentation

CI/CD Integration

Add DeepSweep to your CI/CD pipeline

GitHub Actions

Add the official GitHub Action to your workflow. The pull-requests: write permission lets the Action post results to the pull request. Comments are enabled by default; set comment-on-pr: false if you do not want results posted. Fork pull requests can have a read-only token. Review repository permissions before enabling comments:

# .github/workflows/deepsweep.yml
name: DeepSweep

on: [push, pull_request]

permissions:
  contents: read
  pull-requests: write

jobs:
  review:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Agent Environment Review
        uses: deepsweep-ai/action@v1
        with:
          path: .

Using the Result Downstream

The Action reviews supported agent configurations; it does not run the editor code-pattern review. It publishes the posture score (0-100), its band, the identity attestation the score was computed under and the finding count as step outputs, plus a ready-made README badge. Gate the merge with fail-below-score, or read the outputs yourself and decide. Note that score is empty when the repository has no agent configuration to score, which is not the same as scoring badly — fail-below-score fails the job in that case rather than passing a gate it cannot evaluate:

      - name: Agent Environment Review
        id: review
        uses: deepsweep-ai/action@v1
        with:
          path: .
          # Bands: weak <40, fair <70, good <90, strong above.
          # 40 blocks only genuinely weak posture; raise it as you harden.
          fail-below-score: 40

      - name: Report the posture
        run: |
          echo "Posture: ${{ steps.review.outputs.score }}/100 (${{ steps.review.outputs.posture-band }})"
          echo "Identity attestation: ${{ steps.review.outputs.attestation }}"
          echo "Findings: ${{ steps.review.outputs.findings }}"

Other CI Systems

The supported CI integration described here is the GitHub Action. For other CI systems, you can still review the project locally in Studio or the editor extension. An exported authorization policy describes the review; exporting it does not install a CI gate or apply controls.

Before You Commit

With automatic review enabled, the extension can flag findings as you work. Run an explicit review before committing and inspect incomplete-review notices. No review guarantees that every unsafe instruction or configuration will be detected.