Integration · DevSecOps

HailBytes + CircleCI

External attack-surface scanning as a pipeline step, with SARIF you can gate on.

What you get

  • Reusable job template. An orb-style job wrapping the shared hailbytes-scan.sh, so adding a scan step is a few lines of config rather than a bespoke script.
  • SARIF 2.1.0 as a build artifact. Uploaded for downstream gating — fail on critical findings, or archive the result as release evidence.
  • Context-based credentials. The API key comes from a CircleCI context rather than being inlined in config.

The same hailbytes-scan.sh backs our GitHub Action and the GitLab CI, Jenkins, and Azure Pipelines templates. That means identical behaviour across all five, and a future API change is one update rather than five divergent ones.

Bring your own CircleCI organisation. Credit usage stays on your existing plan.

All CI/CD integrations → API reference → Talk to us →