What does package provenance prove, and what does it not?
Provenance links a package to its source and build, but does not prove the code is safe. What it shows, what it misses, and what to check when asked.
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 links a package to its source and build, but does not prove the code is safe. What it shows, what it misses, and what to check when asked.
Package source mapping filters restore, install and update, but not metadata queries or cached packages. Know these gaps before you rely on it.
Older composition analysis reads manifests and stops. Here is what that misses: resolved transitive versions, vendored code, images and reachability.
A VEX states whether a known vulnerability actually affects a specific product. Learn when to ask a supplier for one and how to read what comes back.
TUF secures how clients get trusted keys. Sigstore uses it to distribute the roots that verify Fulcio certificates and Rekor entries. Roles explained.
The Criticality Score rates a project's influence from 0 to 1. It is not a safety rating, and its public data pipeline has stopped. Use these instead.
The referrers API lists artifacts that point at an image digest, like signatures and SBOMs. See how the endpoint and tag fallback work and what to verify.
SPDX 3.0.1 AIPackage requires eight fields plus license relationships. See the minimum record for a model and the optional AI fields worth adding.
The integrity value in package-lock.json is a hash of the package tarball. What it catches, what it cannot, and why lockfile diffs still need review.
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.