Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
The Safeguard CLI exits zero when a scan runs, whatever it finds. Two documented ways to block a merge: a platform policy gate, or a check you write.
A Jenkinsfile that installs the Safeguard CLI, runs detect with JSON output and archives the file, with the post block that keeps it on failure.
How the Safeguard CLI fits four CI systems: which command to run, where results go, and what each setup needs, based on the published CI documentation.
A GitLab CI job that installs the Safeguard CLI, scans the repository and saves the output as job artifacts, with notes on retention and exit codes.
A GitHub Actions recipe that installs the Safeguard CLI, runs detect, writes SARIF and uploads it to code scanning, with the permissions it needs.
What exit codes 0, 1 and 2 mean for safeguard scan, and why detect only fails when the command itself fails. A short reference for CI authors.
What the Safeguard CLI scan and detect commands return on exit, why a clean exit code is not a clean scan, and how to branch on 0, 1 and 2 in a script.
Safeguard documents CI examples for four systems but not CircleCI. A cautious adaptation using store_artifacts, and what to verify before relying on it.
An Azure DevOps YAML pipeline that installs the Safeguard CLI, writes SARIF to the artifact staging directory and publishes it as a pipeline artifact.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.
