Scan a project and read its SBOM in the Safeguard desktop app
The desktop app scans local folders and runs the Safeguard CLI in its Terminal tab. Here is how to get an SBOM and read it in the web app.
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.
The desktop app scans local folders and runs the Safeguard CLI in its Terminal tab. Here is how to get an SBOM and read it in the web app.
Install the Safeguard CLI, scan a folder, read which findings are marked reachable and ask the web app chat why. The commands come from the CLI site.
Add Safeguard to ChatGPT as a custom MCP server, sign in with OAuth, then ask it to list SBOMs, find critical issues and compare versions. Verify results.
Check the file's format and fields, scan it for known flaws, then ask the Safeguard chat questions about the results. Here is a repeatable vendor review.
The desktop app has no documented SBOM import screen, but its Terminal tab runs the Safeguard CLI. Validate a vendor SBOM and scan it in four steps.
The extension scans your manifests and does not document SBOM import. In Cursor, use the Safeguard CLI in the terminal to validate and scan a vendor file.
The Safeguard VS Code extension generates and previews an SBOM from your lockfile. For a vendor's SBOM file, the CLI validate and scan commands do the job.
Connect Claude to the Safeguard MCP server, ask questions about a vendor SBOM, then confirm key facts with the CLI. Setup, example questions and limits.
Connect Claude to mcp.safeguard.sh, build an SBOM with the Safeguard CLI, then ask plain-language questions about components. Steps are from the docs.
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.