Understand what the checks mean.

“Verified release” means an exact download passed the checks required by its stated release policy. Open Release checks below the downloads on any listing to see what passed, what was not run, the check date, and the installer’s signing status.

Baseline release verification

Baseline verification checks publisher and distribution authorization, the release’s source identity, exact file size and checksum, package and platform identity, and a current malware scan of the installer. Unsigned installers may qualify when their status is disclosed. A release verification badge is separate from an operating system’s publisher signature.

Deeper validation

Source and dependency vulnerability analysis, secrets scanning, software bill of materials review, build provenance, and installation, launch, update, and removal tests are additional checks. Baseline verification does not establish that these checks passed. Each release lists checks that have not been run; full validation is identified separately only when its required checks complete.

An unavailable or failed required check cannot count as a pass. A malware scan is limited to the exact file and the scanner’s capabilities and definitions at that time. Release verification does not guarantee safety or all future behavior.

Where untrusted code runs

Automated installation and runtime validation require disposable isolated workers, separate from the marketplace service, its database, and production credentials. Reading package metadata and scanning an installer do not establish that its installation or runtime tests passed.

Versioned trust

Accepted metadata binds artifact IDs and final digests with expiry and signatures. Revocation blocks new acquisition and warns affected users. Prior releases must remain eligible under current policy; acceptance is not permanent.

Your installed apps

The marketplace verifies acquisition and installation boundaries. Tauri’s permissions restrict the marketplace itself; they do not automatically sandbox arbitrary installed applications or universally enforce a publisher’s declared network permissions.

Updates preserve application data by default. Reinstalling an older binary does not undo a database migration; rollback requires verified data compatibility or a usable backup.

Reporting a concern

The production reporting mailbox and delivery route have not yet been verified. Until a monitored reporting channel is published, public security/takedown intake remains a launch gate. Do not put passwords, API keys or sensitive personal data in public repository issues.