crates.io trusted publishing: publish by hand once, then use OIDC
How crates.io trusted publishing replaces a stored API token with a short-lived one from GitHub Actions, and the first-release step people miss.
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.
How crates.io trusted publishing replaces a stored API token with a short-lived one from GitHub Actions, and the first-release step people miss.
How to correct an SBOM you already sent: issue a revised file, tell recipients, keep the old one, and record what changed. Based on NTIA guidance.
Code pasted from another project never appears in a dependency file. CISA's 2026 SBOM guidance suggests recording it as a named local fork with a link.
Converting every SBOM to one format simplifies processing but can drop fields. Compare convert on intake, keep native, and the hybrid most teams settle on.
Point-in-time scans find issues at build. Continuous monitoring catches advisories published later. How to decide what you need and how to test either.
Evaluate container scanners with real images: OS and language package coverage, layer attribution, registry fit, speed and SBOM output quality.
When a trusted maintainer account ships a bad release, four controls shrink exposure: inventory, version delay, short-lived publish tokens and monitoring.
Composer 2 repositories are canonical by default, and the only and exclude options narrow what each can serve. Setup steps to block name confusion.
allow-plugins is a Composer setting, added in 2.2.0, that lists which plugins may run code inside Composer. Here is how to review and set it safely.
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.