Tauri React Desktop¶
Tauri desktop applications with a React/TypeScript frontend and privileged native commands.
Charter status¶
| Charter status | Value |
|---|---|
| Maturity | Draft charter |
| What this state means | Scope, composition, detection signals, and the VCQA-owned rule surface are recorded, but there are no judgeable candidate rules yet. Useful for planning, not for review. |
| Full rubric | Not authored yet. This page is a charter, not a judgeable standard. |
| Reference implementation | vibecodeqa/ref-tauri-react-desktop (experimental) — see Reference implementation below. |
| Blocking promotion | Scope, composition, detection signals, and rule surface are recorded, but no numbered candidate rules exist, so nothing here is judgeable yet. vibecodeqa/app is a live in-house consumer, and ref-tauri-react-desktop is now built and cataloged as experimental with a self-reported score and a green CI run (#21). Blocking a candidate rubric: the rule surface has to become numbered rules with severity, evidence, and an exception policy before either repo can be judged against it. |
Maturity states are defined in Standards Authoring.
Metadata lives in standards/registry.json.
Full rubric¶
No full versioned rubric has been authored yet.
Reference implementation¶
| Score evidence | Value |
|---|---|
| Repository | vibecodeqa/ref-tauri-react-desktop (experimental) |
| VCQA report | A 98/100 |
| Verification | self-reported |
| Assessed commit | 263d600 |
| Assessed on | 2026-08-09 |
| CI run | success (2026-08-08) |
| Independent assessment | None published yet. The score above is the reference repo's own claim, not third-party proof. |
| Catalog entry last verified | 2026-08-09 |
Scope¶
Tauri desktop applications with a React/TypeScript frontend and privileged native commands.
Not in scope¶
- Electron apps
- pure browser React SPAs
- Rust CLIs without a web frontend
Composes¶
VCQA-owned rule surface¶
- Tauri command/capability boundaries.
- keychain/secret storage.
- file-system watch safety.
- desktop packaging and signing.
- frontend/backend contract typing.
Detection signals¶
src-tauri/- React frontend dependencies
- Tauri config and command handlers
Combination-born guidelines¶
- Filesystem and shell access must be behind Tauri capabilities and commands.
- Secrets belong in OS-backed storage, not browser local storage.
- Frontend/backend command contracts need typed request and response shapes.
Benefits¶
- vibecodeqa/app desktop monitor.