Security & supply chain

A devops.com walkthrough stacks four open-source security gates into GitHub Actions

A devops.com walkthrough stacks four open-source security gates into GitHub Actions

For teams running GitHub Actions without an enterprise security budget, devops.com published a walkthrough on August 4 titled "Shift Left Security: 4 Automated Security Gates in GitHub Actions", which strings npm audit, Snyk, Trivy, CodeQL and OWASP ZAP into a single pipeline as four automated gates. The operational read is straightforward: none of those tools are new, and none of them require a paid seat to get a first result out of a workflow, so the piece is best understood as a build-your-own-baseline reference rather than an announcement.

What the four gates cover

The five tools the article lists map cleanly onto four well-worn categories of scanning. npm audit and Snyk both sit on the software composition analysis side, reading a lockfile against a vulnerability database and flagging known-bad transitive dependencies. Trivy covers the container and infrastructure surface, scanning built images and, in newer versions, IaC files for the same class of CVE lookups. CodeQL is the static analysis engine GitHub bundles into Actions and runs against source, and OWASP ZAP is the dynamic scanner, driving a running service with fuzzed HTTP traffic to find what static analysis cannot see. The piece frames all four as buildable inside a standard runner without an enterprise licence.

The catch the walkthrough does not price in

Every gate you add is a step that has to pass, be triaged when it fails, and be tuned when it drifts. Five scanners across every pull request is five sets of findings, five noise budgets, and five places a slow runtime lands on the critical path of a merge. The failure mode is not the scanner. It is the team that stops reading the output after the third false positive and starts adding continue-on-error: true, at which point the gate is decorative. The devops.com article is a good pointer at what is available; the harder question, which pipeline owner picks up after the demo, is which of these gates blocks a merge, which one only annotates, and which one has been quietly amber for three months because nobody owns it.

Source: devops.com (devops.com)

Related
Security & supply chain

GitHub secret scanning now reads your Actions logs, once the run is over

GitHub secret scanning can now scan GitHub Actions workflow logs after each run completes and raise findings in the repository's secret scanning alert list. The public preview is limited to GitHub Enterprise Cloud enterprises with Secret Protection or Advanced Security, and it is off by default.

November 10, 2026
Security & supply chain

GitHub Actions lockfiles pin the commit and leave your tags alone

GitHub Actions workflow dependency lockfiles are in public preview. A GitHub CLI extension records the exact commits behind a workflow's actions, their transitive dependencies and reusable workflows, and onboarded runs use those commits even if a tag or branch moves.

October 17, 2026
Security & supply chain

GTIG's agentic threat report is a CI/CD problem, not just an AI problem

Google's Threat Intelligence Group documents DUSTMAKER, an OIDC-stealing supply-chain payload from UNC6780 that ships valid SLSA Build 3 attestations. The moment a signed provenance line stops being a defence is the moment CI/CD owners have to rethink runner trust.

September 10, 2026

Turn this into your pipeline. Build it on Buddy.

Start free