Safeguard
Developer Tools•

Safeguard Desktop FAQ: what the download page confirms

Common Safeguard Desktop questions answered only from the download page: version, platforms, installers, signing, checksums and the CLI requirement.

Safeguard Security Team
3 min read

Safeguard Desktop is at version 3.2.2 on the download page. It is a native window for Windows 10 and 11, macOS 12 or later and 64-bit Linux, and it lets you query what you have scanned in plain English. This FAQ sticks to what that page states, and says so where it is silent.

What is it?

The page describes Desktop as a way to ask your supply chain anything, in a native window that opens instantly. It covers every CVE, component, project and control you have scanned, and you query it in plain English. The page also calls it the whole platform in its own window.

Which systems does it run on?

Windows 10 and 11 on x64 and ARM. macOS 12 or later, with Apple Silicon and Intel builds. Linux on 64-bit x86 with FUSE.

How big is the download?

The page lists about 205 MB for the Windows installer, about 115 MB for the macOS disk image and about 120 MB for the Linux AppImage.

Do I need administrator rights?

On Windows, no. The page says it installs per user. For macOS and Linux the page does not discuss administrator rights, so check on your own system.

Is it signed?

The page says the macOS builds are signed and notarized. The Windows builds are not yet code-signed, so SmartScreen may warn. The page's instructions are More info, then Run anyway. Verify the checksum first. See SmartScreen warning: what to do.

How do I verify the download?

SHA-256 checksums are listed for each build, with a SHA256SUMS file for each release. Commands for each system are in verifying a checksum.

What does Linux need besides FUSE?

The Safeguard CLI must be installed and on your PATH. See Desktop on Linux.

What does the page not say?

It gives no separate Desktop feature list, no offline behaviour, no statement on where scan data is processed, and no pricing. Treat those as open questions to ask Safeguard directly, and do not assume.

Why are there both a Desktop app and a CLI?

The page presents them as separate downloads, and on Linux it ties them together by requiring the CLI. It does not describe how they divide the work, so a reasonable rule is to use Desktop for exploring and the CLI for anything that must run unattended. That is a suggestion from this post, not a statement from the page.

Can I try the scanning without installing anything?

Yes. The free scan at gold.safeguard.sh/scan needs no login. The page says it checks up to 100 dependencies from a package.json, requirements.txt or an SBOM, and that files are parsed in your browser. It is separate from Desktop, so it is a way to see what scanning produces, not a Desktop feature.

Where should I start?

Install, verify, sign in, and ask one question about something you have already scanned. Then decide which tasks belong in Desktop, the CLI or a pipeline, using the surface choice guide.

Where Safeguard fits

Desktop sits beside the CLI, IDE extensions, browser extensions and mobile apps. For a first look with no install, use gold.safeguard.sh/scan.

Quick check

What version is current on the download page?

Version 3.2.2 at the time of review.

Does the page list offline behaviour for Desktop?

No. Ask Safeguard directly before relying on it.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.