Can a VEX statement let a build pass a security gate?
A not affected VEX statement can suppress a finding in a gate, if you treat it as evidence with an author and a review. How to use VEX without hiding risk.
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.
A not affected VEX statement can suppress a finding in a gate, if you treat it as evidence with an author and a review. How to use VEX without hiding risk.
pip hash checking verifies each download against hashes you store and fails on anything unpinned. What it covers, what it does not, and how to adopt it.
CISA allows one VEX statement to cover many products if the status is true for all of them. Learn when to group, when to split, and how to name sets.
Wrangler bundles your npm dependencies into one file. Scan the lockfile and the bundle together to know which packages and versions actually ship.
Yes. NuGet packages can ship MSBuild props and targets, analyzers and tools that take part in your build. Learn what flows where and how to limit it.
Yes, any tool that upgrades packages can pick up a bad release. How cooldowns, provenance checks and review reduce the risk, and what they cannot do.
Buildroot can produce package CVE and upstream version reports, JSON package info, and a CycloneDX SBOM from that data. The commands and what they cover.
Buildroot produces CycloneDX from its package info, while Yocto's create-spdx class writes an SPDX document for the image. A plain look at what each emits.
A build system compromise ships a malicious artifact from clean source. Here are the questions that test whether a software vendor protects its build.
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.