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.
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.
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.
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.
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.
MalGuard Core has earned the OpenSSF Best Practices Baseline Level 1 badge, based on project-submitted information. This badge is a self-assessment, not an independent security audit, a certification of detection accuracy, or an Authenticode signature for Windows installers.
The public badge entry shows the status and criteria. It applies to the MalGuard Core repository; other MalGuard products and download artifacts are not automatically certified.
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.
Include the affected version or commit, harmless reproduction steps, expected behavior and observed behavior. Do not attach or upload real malware.
See which claims are backed by inspectable public source, which test totals are project-reported, and which claims still lack independent evidence. No insurance-backed reimbursement or guaranteed protection is represented by this project profile.