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.
Open volunteer contributions need a few guardrails. Use this minimum branch protection setup: required review, passing checks and no direct pushes to main.
Fail the build when a lock file adds a dependency that is not in your approved register. Steps for an allowlist check on Gradle, CocoaPods and SwiftPM.
On Bitbucket Cloud, merge checks warn on lower plans and block on Premium. The checks available, who sets them up, and how they pair with branch rules.
When a release misbehaves and the code diff is quiet, a diff of stored SBOMs shows which dependency changed. Here is how to bisect with SBOM history.
Sandboxing hides undeclared files from build actions. Without it, Bazel can store wrong entries in a shared cache that then reach every developer.
Batching saves review time, single upgrades save debugging time. A simple rule for choosing batch size, and how to bisect a batch that breaks the build.
Baseline old violations so a new rule blocks only new code. ESLint bulk suppressions show the pattern: commit the file, prune when fixed, track the count.
A four-week plan to measure the five DORA delivery metrics and a few security measures for one team, with no new tools and no targets set yet at all.
Yes. ESLint's no-restricted-syntax takes AST selectors and custom messages, so you can ban a call or pattern with a few lines of config and no plugin.
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.
