Unpublish, yank or deprecate: how registries pull a bad release
Registries offer three ways to retire a release: unpublish, yank and deprecate. Compare what each does to new installs, lockfiles and cached copies.
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.
Registries offer three ways to retire a release: unpublish, yank and deprecate. Compare what each does to new installs, lockfiles and cached copies.
Three ua-parser-js releases carried a miner and a password stealer in October 2021. Affected versions, the install script trick and the cleanup list.
Ken Thompson showed that clean source code can still produce a backdoored program. This explainer covers the idea and the diverse double-compiling defence.
A transitive dependency is a package your code needs only because another dependency needs it. Learn why they hold most of your risk and how to see them.
Open source risk is not one thing. Vulnerable, abandoned and malicious packages need different detection and responses, and scanners mostly cover one.
Ad, analytics and social SDKs run with your app's permissions. Inventory them, limit data, pin versions and review changes before each release.
AI vendors, hosted models and training data are supply chain risks. What the NIST AI RMF and generative AI profile say to inventory, monitor and plan for.
Commit the Terraform lock file. It pins provider versions and checksums, so any provider change shows up in code review. How it works and where it stops.
MITRE T1195 lists where software supply chains get tampered with and six mitigations. Here is how each one translates into daily developer work.
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.