What this shape is

A src-tauri/ Rust core hosting a webview front end. The classifier detects the Tauri directory and reports it. The security model is deliberately not Electron's: the webview has no Node, and the front end can only reach the host through commands you expose.

Scanner behavior

PreFlight classifies this shape (informational). It does not raise a shape-specific finding for it; the Rust adapters run on the src-tauri core and the web probes run on the UI.

The failure mode: the allowlist is the boundary

Tauri's safety comes from the front end being unable to touch the host except through the capabilities you grant. The vibe-coded failure is widening that grant to make a feature work:

• An allowlist that enables broad shell execution or a filesystem scope of ** hands a webview-reachable bug a path to host command execution. When remote or untrusted content can load in that webview, it is remote code execution.
• A window pointed at a remote https:// origin instead of the bundled app, combined with a broad allowlist, turns "render this page" into "run host commands from that page."
• Commands that take a path or a shell string from the front end without validation re-expose the host the architecture was protecting.

When to use it

Tauri is the right shape when you want a small, native-feeling desktop app and are willing to keep the capability surface narrow. It is safe when the allowlist grants the minimum, windows load only bundled content, and exposed commands validate their inputs like any other trust boundary.

Related

• Desktop app (Electron) is the same product shape with the opposite default: Node is present unless you remove it.