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.
VersionOverride lets a project bypass the central NuGet version list. Learn when that is useful, why it weakens control, and how to switch it off.
A decision guide for timing runtime upgrades: how LTS and standard releases differ, and a simple rule for moving after launch but before the old line ends.
Usually no. The semver spec marks a pre-release such as an alpha or release candidate as unstable. Keep bots on stable releases unless you opt in.
Scan every repo for visibility, but gate only the ones that ship. A tiered model keeps coverage high without blocking prototypes, forks and archived code.
CI artifacts expire, and deleting a run deletes them. Why release binaries need a permanent, access controlled home, and how to hand them over safely.
Non-LTS Java releases get about six months of updates. Production usually belongs on LTS unless you can upgrade every six months. How to decide.
Semantic versioning says pre-releases carry a lower precedence and may be unstable. When an rc is acceptable in production and how to gate it.
Auto-merge saves time for low risk updates but needs strong tests and branch rules. Here is when it is reasonable and the guardrails to set first.
Write logs to stdout and let the platform route them. Why the twelve factor model fits containers, what Docker captures, and the security checks to add.
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.
