How do you check for end-of-life runtimes every quarter?
List every language runtime, framework and base image you run, look up each support end date, and schedule upgrades. A quarterly routine for small teams.
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.
List every language runtime, framework and base image you run, look up each support end date, and schedule upgrades. A quarterly routine for small teams.
A quarantined dependency should leave only when named criteria are met. Here is a release checklist covering age, scans, source, behaviour and sign-off.
Python libraries installed through the OS package manager do not appear in requirements files, so a pip focused scan misses them. Where to look instead.
Yes. The requires list names tools that run when your package is built, on your machine and for users installing from source. Keep it small and reviewed.
An advisory covers deserialization in PyArrow IPC and Parquet readers from 0.14.0 to 14.0.0. Who is exposed, how to check your version, and the fix.
When a package name stays but its namespace or supplier changes between releases, check for a rename, fork swap or lookalike before you accept it.
Yes. Every dependency you delete is an upgrade you never do. Here is a quarterly pruning pass that shrinks the upgrade backlog before work begins.
Shared Terraform modules should set only a minimum provider version with >=, while root modules pin with ~>. Why the split exists and how to review it.
Four build terms in plain English: provenance is the build record, an attestation a signed claim, the subject the artifact, the predicate the claim itself.
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.