Why safeguard scan needs syft and grype on a fresh CI runner
A fresh CI runner lacks the scanners safeguard scan uses. Put syft and grype on the PATH or set TOOLS_DIR, or the scan can finish without matching.
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 fresh CI runner lacks the scanners safeguard scan uses. Put syft and grype on the PATH or set TOOLS_DIR, or the scan can finish without matching.
A decision guide to the Safeguard phone apps, web app and desktop app, with what each is for. Pick by the task in front of you, not by habit.
Short answers on the Safeguard mobile apps: where to get them, account needs, versions, the Safari extension, APK updates and what is not stated.
The Safeguard CLI fix command can preview changes and open a pull request. How to use dry run in CI, and keep a human review between the fix and merge.
Safeguard detect can print a table, JSON or SARIF. Which suits a person, a script and a code scanning tab, and what the documentation says about each.
A decision guide for choosing between a native desktop window, a web app and a command line tool for dependency security work, by task and team size.
Common Safeguard Desktop questions answered only from the download page: version, platforms, installers, signing, checksums and the CLI requirement.
The Safeguard CLI has two update commands. One refreshes vulnerability databases, the other replaces the binary. Here is when to run each of them.
A checklist for when the Safeguard CLI misbehaves: run doctor, read the log, then fix sign-in, network, scanner and PATH problems in a sensible order.
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.