Read 2026-10-04
tauri-apps/tauri: technical due diligence, read from its repository
What Borehole read in tauri-apps/tauri's code and history at d15cf9b: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
.github/CONTRIBUTING.md:8: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongcrates/tauri-utils/src/config.rs is 5,503 lines, 62× this codebase's median file
adequateThe median source file here is 88 lines. 21 files exceed 1,000 lines, the largest being 5,503. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
crates/tauri-utils/src/config.rs:1 — 5,503 lines (62× median) |
crates/tauri-runtime-wry/src/lib.rs:1 — 5,433 lines (61× median) |
packages/api/src/window.ts:1 — 3,216 lines (36× median) |
crates/tauri-utils/src/config_v1/mod.rs:1 — 3,158 lines (35× median) |
crates/tauri/src/webview/webview_window.rs:1 — 2,880 lines (32× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate4% of bug fixes add or change a test
adequateOf 480 fixes in the last 24 months, 21 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 21 of 480 |
Releases are cut from another branch than the one surveyed
adequateThe newest pre-release, tauri-v3.0.0-alpha.3, is not on the branch this survey read; the newest release on it is tauri-v2.12.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag tauri-v3.0.0-alpha.3 |
Security & Reliability Posture
strongThe build runs third-party code it does not pin
adequate17 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/audit.yml:43 — action pinned by tag |
.github/workflows/bench.yml:50 — action pinned by tag |
20 locked dependencies have published vulnerabilities, 23 high or critical
adequate20 of 2,195 locked dependencies match 54 published advisories in OSV, 23 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. None of the high or critical ones is in what the product ships: they are development dependencies. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
pnpm-lock.yaml — axios 1.19.0: GHSA-3pq3-5fj3-cg6v (high), fixed in 1.20.0; a development dependency |
pnpm-lock.yaml — basic-ftp 5.3.1: GHSA-c475-qrg2-pj4r (high), fixed in 6.2.1; a development dependency |
pnpm-lock.yaml — brace-expansion 1.1.18: GHSA-6j4f-fj2g-mc7p (high), fixed in 1.1.19; a development dependency |
7 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-09-26. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 5 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 2.12.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 6 records name tauri with nothing tying them to this repository (CVE-2025-59053, CVE-2026-45261, CVE-2026-55642, …).
| 2026-09-26: GHSA-w28w-mhc8-qvjv (high), fixed in >= 2.11.6: Improper Tauri IPC Access Control for Fetch Command |
| 2026-09-23: CVE-2026-95625 (moderate): The Tauri updater plugin verifies update binaries using minisign signatures, but the signature covers only the raw binary bytes. The update manifest -- which co |
| 2026-09-23: CVE-2026-95626 (high): Tauri's Content Security Policy hardening, which injects a random nonce to restrict script execution, provides zero protection when an application includes data |
| 2026-09-23: CVE-2026-95627 (high): When a Tauri application uses the dialog plugin's file or folder picker, an attacker with JavaScript execution (XSS) can force the scope expansion to be recursi |
| 2026-09-22: CVE-2026-95623 (moderate): The Tauri HTTP plugin validates requested URLs against the application's configured scope allowlist only once, on the initial request. When the remote server re |
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on tauri-apps/tauri: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.