License fields to require in a supplier SBOM
A checklist of license data to ask for in a supplier SBOM: identifiers, declared and concluded values, expressions, unknowns and how to check them.
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 checklist of license data to ask for in a supplier SBOM: identifiers, declared and concluded values, expressions, unknowns and how to check them.
In March 2016 an unpublish broke thousands of builds for about 2.5 hours. npm's own account of what happened and the policy changes that followed.
On 22 March 2016 an unpublished npm package broke builds for thousands of projects. Here is what happened and the policy that came out of it.
Lambda code signing checks that deployments come from a trusted signer. It will not catch a vulnerable dependency or code that was signed by mistake.
Safeguard hosts its MCP server and publishes no npm package or local bridge. Treat any package that claims otherwise as untrusted. Myths and facts here.
A Verified badge on a Hub commit shows the commit was signed with a key registered to an account. It proves origin, not that the model file is safe.
When a flaw lands in a shared component, which products are affected? How per-release SBOMs turn guesswork into a search, using the Jeep recall as a case.
A step by step checklist for reading a supplier's VEX file: who wrote it, what products it covers, which statuses it uses, and what to do with each statement.
Do not guess a component's producer or version. Mark it unknown, in the way your format supports. SPDX NOASSERTION, CycloneDX gaps, and the 2026 guidance.
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.