Snapshot tests fail after a security bump: update or investigate?
A snapshot test fails after a dependency fix. Read the diff first: update the snapshot only when the change is intended, harmless and explained.
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.
A snapshot test fails after a dependency fix. Read the diff first: update the snapshot only when the change is intended, harmless and explained.
A smoke test after a dependency upgrade proves the app starts and its critical paths work. What to include, what to leave out, and how long it should take.
Read the image SBOM to spot build tools, shells and packages you do not need at runtime, then use multi-stage builds to leave them behind safely.
skops saves scikit-learn models without pickle and has you review untrusted types first. What it improves, what it cannot do, and how to adopt it.
Recent SignTool builds require /fd for the file digest and /td for the timestamp digest. Set both to SHA256, use /tr for RFC 3161, and check exit code 2.
Signed commits show who pushed, and required checks show tests passed. Neither proves the code is safe. Here is what each control does and misses.
A finding that includes the fix gets acted on faster. What a good fix suggestion contains, when to offer a pull request, and when a human must decide.
An internal tap gives developers one install path, and tap code runs with the user's privileges. Homebrew's tap trust model shapes how to run one safely.
A minimum supported app version lets you retire a vulnerable release of your companion app. Here is how to set it up without locking customers out.
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.