Security & Trust

Trust should be inspectable.

MalGuard documents what the product does, what it does not prove, how releases are tied to source, and where security researchers can report problems privately.

LOCAL-FIRST

Privacy

Supported scanning is designed to stay on the user's device by default. Optional network features may look up metadata such as hashes, but a file itself must not be sent to a third party without an explicit action and clear disclosure.

Read the privacy summary →

FAIL-CLOSED

Security architecture

The core uses bounded parsing, integrity checks, worker isolation, and fail-closed verdicts. Missing required evidence should become inconclusive instead of being silently treated as safe.

UNSIGNED PREVIEW

Code signing

The current Windows preview is not Authenticode-signed. MalGuard's public policy forbids presenting an unsigned build as signed or equivalent to a future signed release.

Release integrity

Verify what you download.

The clean-room scanner release page publishes the verified build code, source commit and complete installer SHA-256. No scan or publisher signature guarantees safety.

Version
Clean-room Windows x64 · Unsigned preview
Source commit
See verified release details
SHA-256
See the full SHA-256 on the release page
Signing status
Unsigned preview. SmartScreen reputation and Smart App Control restrictions may apply; read the Microsoft guidance linked on the release page.
Known limitations

A clean result is not a guarantee.

Detection coverage

  • No scanner can prove that a file is harmless.
  • Coverage varies by file type, archive structure and available analysis layers.
  • Threat-intelligence coverage is not universal.

Platform coverage

  • Windows-only isolation features are not available in the iPhone browser preview.
  • Encrypted or unsupported payloads can remain unreadable; the current scanner does not execute samples.
  • Unsigned previews may trigger operating-system trust warnings.
Vulnerability disclosure

Report security problems privately first.

Include the affected version or commit, harmless reproduction steps, expected behavior and observed behavior. Do not attach or upload real malware.

Source documents

Policies live with the code.