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 seven item checklist for reviewing the dependency changes in a pull request: purpose, maintainer, scope, license, advisories, size and the lockfile.
Yes. A green check without a coverage line can mislead. State languages, manifests and paths skipped, so a pass is not read as more than it is.
SARIF results carry a kind and a level. How to count them so passes, open questions and notes do not inflate your security finding numbers.
How the SARIF baselineState values new, unchanged, updated and absent let you count findings introduced and fixed per pull request instead of totals.
Sanitize at the last step, restrict the allowed profile, keep the library current and do not edit the HTML afterwards. A practical sanitizing routine.
The Safeguard CLI scans from a terminal and can also write code. What the download page lists for the local agent, cloud agent and sandboxes.
Use example.com, example.net, example.org or the reserved .test suffix for test emails. Random addresses on real domains can reach real people.
Short answers to ten questions on automating dependency fix PRs: grouping, tests, canaries, rollback, ownership and approvals, with links for detail.
The rust-version field sets a minimum Rust version. Learn how it affects dependency selection, and why an old MSRV can block fixed releases of crates.
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.
