Seeing dependency risk and getting an SBOM from VS Code
What the Safeguard VS Code extension shows while you code, and which surface generates the SBOM: the CLI or the web app. Commands and steps from docs.
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.
What the Safeguard VS Code extension shows while you code, and which surface generates the SBOM: the CLI or the web app. Commands and steps from docs.
Connect ChatGPT to the Safeguard MCP server with OAuth or an MCP key, then ask it to list SBOMs, inspect components and diff builds. Setup steps inside.
The Safeguard Chrome extension opens Griffin search in a side panel while you read an SBOM. How to read one, and where SBOMs are generated and exported.
Connect Claude to the Safeguard MCP server, ask about findings, SBOMs and compliance in plain language, and file each answer with its source as evidence.
The local runner scans on your machine and pushes only the SBOM and findings. Run dated scans, keep outputs and map them to controls. Steps and limits.
Use the Safeguard CLI to scan, validate the SBOM, and run a report from the scan result, so you hand an auditor files that came from your own build.
The runner scans code on your machine and uploads only the SBOM and findings. For a vendor SBOM file, the CLI is the documented route. Here is the split.
Safeguard scans code, history, images and logs for leaked keys, checks if they are live, and guides revoke and rotate. Mobile beta is not covered.
The plugin scans on demand and on save or project open. Scheduled scans live in the platform and CLI. Here is how to set up each and what to expect.
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.