Documentation

Understand the product before you trust the verdict.

Use these docs to find the correct scanner, understand the analysis depth, verify releases, review privacy behavior and contribute safely.

Getting started

Start with the clean-room Windows scanner release page. Read the verified build details, requirements, installation steps and troubleshooting before running the installer.

Release status →

Browser tools

File Fingerprint calculates SHA-256 locally. Link Inspector analyzes URL text without opening the destination or silently uploading it.

Open tools →

Analysis models

Static evidence and coverage

Analysis is bounded by shared deterministic work budgets. Missing required evidence must not be silently treated as a completed clean result.

01

Intake and reputation

Core file identity, bounded static inspection and security signals for supported workflows.

02

Structure and capabilities

PE, .NET, script and archive parsers contribute evidence while raw analysis survives structure failure.

03

Correlation and coverage

Only the verdict engine decides the result. Independent harm families, opacity, coverage and confidence are reported separately.

Security documentation

Policies and evidence.

Trust Center

Security architecture, code-signing status, known limitations, release integrity and vulnerability disclosure.

Open Trust Center →

Privacy

Local-first scanning and the boundary for optional network features and file transfer.

Privacy summary →

Source docs

README, SECURITY, PRIVACY, code-signing policy and contribution requirements live with MalGuard Core.

MalGuard Core →

Contributors

Defensive development only.

The repository forbids adding, downloading or executing real malware in development or CI. Use harmless synthetic fixtures and run the engineering suite before proposing security-sensitive changes.