Which attestation predicate type do you need? A decision table
Provenance, SBOM, vulnerability scan, test result or VSA: match the in-toto predicate type to the question you need an attestation to answer.
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.
Provenance, SBOM, vulnerability scan, test result or VSA: match the in-toto predicate type to the question you need an attestation to answer.
composer audit asks the Packagist.org security advisories API, which records each advisory source. What the data includes, and what it cannot tell you.
Reset runners, caches, signing keys, build secrets and base images, then rebuild from a clean commit. A checklist based on the SLSA build threats.
Store the raw file untouched and index a handful of fields so you can answer who uses this component in seconds. Here is the field list and why.
When an approved MCP server stops getting updates, check its signals, freeze the version, limit its access, plan a replacement and set a removal date.
When a scanner flags a package with no patched version, check reachability, add a mitigation, replace the package, or accept with an expiry date.
Before adopting an open source scanner, check licence, maintenance status, data sources, release cadence and exit path. A short due diligence checklist.
The root component says what an SBOM describes. How SPDX DESCRIBES and the CycloneDX metadata component work, and what breaks when the subject is missing.
The GitHub dependency graph is built from manifest and lock files. See what it covers, where transitive and unsupported cases leave gaps, and fixes.
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.