Public report of tauri-apps/tauri, published 25 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 25 October 2026, 21:26 UTC · Survey ID cd_1f8d9ea4d5f74c57ab1319b36f2b0961
tauri-apps/tauri
Measured 25 October 2026, 21:04 UTC, at code version 1fc6d9c
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Down 3 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 104,446 lines of product code in 29 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Accessibility, 49
Findings by how serious they are
200 critical516 serious29 minor
12 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
25 October 2026, 21:04 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
84of 84 dimensions measured by tools.
725of 745 findings point to an exact file and line, so you can open each one in the code. The other 20 concern the repository as a whole, such as missing documentation.
84dimensions across 8 lenses, read from 104,446 lines of product code in 29 projects.
tauri-apps/tauri falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 52 out of 100 and is rated Adequate, and 196 of its 200 critical findings are security problems.
Accessibility, at 49, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 2 points. Automating accessibility checks would lift Accessibility itself, also worth about 2.
134 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty pipeline steps install packages that can change without warning, and thirteen secrets can leak from the build pipeline. Pinning each tool to an exact version, pinning what the pipeline installs and limiting each secret to its own step would close these risks. The 12 pipeline steps that run downloads without checking them need each download checked against a known checksum first. The six passwords or keys in the code's history and the two passwords or keys in the code need replacing, with the old ones switched off. The form field without a label needs a label.
The product code is 104,446 lines, about €110,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Outbound HTTP resilience · Outbound HTTP without resilience crates/tauri-bundler/src/utils/http_utils.rs
Visual & motion safety · Focus outline removed in CSS without a :focus replacement crates/tauri-cli/templates/plugin/__example-api/tauri-app/src/style.css
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 13 findings
These 13 critical or serious findings were in the previous survey, on 11 October 2026, and are gone from this one.
Large Files · packages/api/src/window.ts: 3078 lines of code packages/api/src/window.ts
Rebuild cost: about €110,000 · Estimate
Cost to rebuild
€36,000 to €180,000, for 592 to 1,877 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 104,446 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).
Raises the score by about 2 points · Low effort · Secret Scanning
2
Enforce accessibility in the toolchain: add eslint-plugin-svelte (a11y rules are built in), then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Raises the score by about 2 points · Medium effort · A11y enforcement
3
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 2 points · Medium effort · Page structure
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.7 person-years of work. Its weakest lens is Accessibility, at 49 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 2 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.4 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 39,097 lines over the last 90 days, which is about 158,560 lines a year. At that pace, the extra work comes to an estimated 7.9 to 52.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
311 modules, with 604 dependencies between them. 3 loops run through 56 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 271 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
Uses a module listed above itPart of a loopThe module itself
10→35 tauri.state uses tauri.ipc.commandpart of a loop✕
Connections
2 pairs of types, where a type in tauri.state uses a type in tauri.ipc.command.
The types involved
tauri.state.State → tauri.ipc.command.CommandArg
tauri.state.State → tauri.ipc.command.CommandItem
Direction
tauri.state uses tauri.ipc.command, so a change to tauri.ipc.command can break tauri.state, while a change to tauri.state can't break tauri.ipc.command.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in tauri_cli uses a type in tauri_cli.acl.capability.
The types involved
tauri_cli.Cli → tauri_cli.acl.capability.Commands
Direction
tauri_cli uses tauri_cli.acl.capability, so a change to tauri_cli.acl.capability can break tauri_cli, while a change to tauri_cli can't break tauri_cli.acl.capability.
Position
Below the diagonal: tauri_cli uses a module listed above it, which is the healthy direction.
tauri_cli uses tauri_utils.acl.value, so a change to tauri_utils.acl.value can break tauri_cli, while a change to tauri_cli can't break tauri_utils.acl.value.
Position
Below the diagonal: tauri_cli uses a module listed above it, which is the healthy direction.
tauri_cli.info uses tauri_cli.acl.capability.new, so a change to tauri_cli.acl.capability.new can break tauri_cli.info, while a change to tauri_cli.info can't break tauri_cli.acl.capability.new.
Position
Below the diagonal: tauri_cli.info uses a module listed above it, which is the healthy direction.
13→20 tauri_runtime.dpi uses tauri_utils.configpart of a loop✕
Connections
1 pair of types, where a type in tauri_runtime.dpi uses a type in tauri_utils.config.
tauri_runtime.dpi uses tauri_utils.config, so a change to tauri_utils.config can break tauri_runtime.dpi, while a change to tauri_runtime.dpi can't break tauri_utils.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→28 tauri_runtime.dpi uses tauri.image.pluginpart of a loop✕
Connections
1 pair of types, where a type in tauri_runtime.dpi uses a type in tauri.image.plugin.
The types involved
tauri_runtime.dpi.Rect → tauri.image.plugin.Size
Direction
tauri_runtime.dpi uses tauri.image.plugin, so a change to tauri.image.plugin can break tauri_runtime.dpi, while a change to tauri_runtime.dpi can't break tauri.image.plugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→29 tauri_runtime.dpi uses tauri_bundler.bundle.settingspart of a loop✕
Connections
1 pair of types, where a type in tauri_runtime.dpi uses a type in tauri_bundler.bundle.settings.
tauri_runtime.dpi uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri_runtime.dpi, while a change to tauri_runtime.dpi can't break tauri_bundler.bundle.settings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri.ipc.authority uses tauri_utils.acl.value, so a change to tauri_utils.acl.value can break tauri.ipc.authority, while a change to tauri.ipc.authority can't break tauri_utils.acl.value.
Position
Below the diagonal: tauri.ipc.authority uses a module listed above it, which is the healthy direction.
tauri.ipc.authority uses tauri.state, so a change to tauri.state can break tauri.ipc.authority, while a change to tauri.ipc.authority can't break tauri.state.
Position
Below the diagonal: tauri.ipc.authority uses a module listed above it, which is the healthy direction.
14→26 tauri.ipc.authority uses tauri.test.mock_runtimepart of a loop✕
Connections
2 pairs of types, where a type in tauri.ipc.authority uses a type in tauri.test.mock_runtime.
tauri.ipc.authority uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri.ipc.authority, while a change to tauri.ipc.authority can't break tauri.test.mock_runtime.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→34 tauri.ipc.authority uses tauri_utils.acl.resolvedpart of a loop✕
Connections
2 pairs of types, where a type in tauri.ipc.authority uses a type in tauri_utils.acl.resolved.
tauri.ipc.authority uses tauri_utils.acl.resolved, so a change to tauri_utils.acl.resolved can break tauri.ipc.authority, while a change to tauri.ipc.authority can't break tauri_utils.acl.resolved.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→35 tauri.ipc.authority uses tauri.ipc.commandpart of a loop✕
Connections
4 pairs of types, where a type in tauri.ipc.authority uses a type in tauri.ipc.command.
tauri.ipc.authority uses tauri.ipc.command, so a change to tauri.ipc.command can break tauri.ipc.authority, while a change to tauri.ipc.authority can't break tauri.ipc.command.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→37 tauri.ipc.authority uses tauri.apppart of a loop✕
Connections
2 pairs of types, where a type in tauri.ipc.authority uses a type in tauri.app.
tauri.ipc.authority uses tauri.app, so a change to tauri.app can break tauri.ipc.authority, while a change to tauri.ipc.authority can't break tauri.app.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri.menu.plugin uses tauri.image, so a change to tauri.image can break tauri.menu.plugin, while a change to tauri.menu.plugin can't break tauri.image.
Position
Below the diagonal: tauri.menu.plugin uses a module listed above it, which is the healthy direction.
tauri.menu.plugin uses tauri.state, so a change to tauri.state can break tauri.menu.plugin, while a change to tauri.menu.plugin can't break tauri.state.
Position
Below the diagonal: tauri.menu.plugin uses a module listed above it, which is the healthy direction.
15→26 tauri.menu.plugin uses tauri.test.mock_runtimepart of a loop✕
Connections
8 pairs of types, where a type in tauri.menu.plugin uses a type in tauri.test.mock_runtime.
tauri.menu.plugin uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri.menu.plugin, while a change to tauri.menu.plugin can't break tauri.test.mock_runtime.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→27 tauri.menu.plugin uses tauri.pluginpart of a loop✕
Connections
1 pair of types, where a type in tauri.menu.plugin uses a type in tauri.plugin.
tauri.menu.plugin uses tauri.plugin, so a change to tauri.plugin can break tauri.menu.plugin, while a change to tauri.menu.plugin can't break tauri.plugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→29 tauri.menu.plugin uses tauri_bundler.bundle.settingspart of a loop✕
Connections
1 pair of types, where a type in tauri.menu.plugin uses a type in tauri_bundler.bundle.settings.
tauri.menu.plugin uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri.menu.plugin, while a change to tauri.menu.plugin can't break tauri_bundler.bundle.settings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→37 tauri.menu.plugin uses tauri.apppart of a loop✕
Connections
1 pair of types, where a type in tauri.menu.plugin uses a type in tauri.app.
tauri_cli.interface.rust uses tauri_cli.acl.capability.new, so a change to tauri_cli.acl.capability.new can break tauri_cli.interface.rust, while a change to tauri_cli.interface.rust can't break tauri_cli.acl.capability.new.
Position
Below the diagonal: tauri_cli.interface.rust uses a module listed above it, which is the healthy direction.
tauri_cli.interface.rust uses tauri_cli.helpers.app_paths, so a change to tauri_cli.helpers.app_paths can break tauri_cli.interface.rust, while a change to tauri_cli.interface.rust can't break tauri_cli.helpers.app_paths.
Position
Below the diagonal: tauri_cli.interface.rust uses a module listed above it, which is the healthy direction.
tauri_cli.interface.rust uses tauri_cli.interface.rust.cargo_config, so a change to tauri_cli.interface.rust.cargo_config can break tauri_cli.interface.rust, while a change to tauri_cli.interface.rust can't break tauri_cli.interface.rust.cargo_config.
Position
Below the diagonal: tauri_cli.interface.rust uses a module listed above it, which is the healthy direction.
tauri_cli.interface.rust uses tauri_cli, so a change to tauri_cli can break tauri_cli.interface.rust, while a change to tauri_cli.interface.rust can't break tauri_cli.
Position
Below the diagonal: tauri_cli.interface.rust uses a module listed above it, which is the healthy direction.
16→20 tauri_cli.interface.rust uses tauri_utils.configpart of a loop✕
Connections
2 pairs of types, where a type in tauri_cli.interface.rust uses a type in tauri_utils.config.
tauri_cli.interface.rust uses tauri_utils.config, so a change to tauri_utils.config can break tauri_cli.interface.rust, while a change to tauri_cli.interface.rust can't break tauri_utils.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→29 tauri_cli.interface.rust uses tauri_bundler.bundle.settingspart of a loop✕
Connections
2 pairs of types, where a type in tauri_cli.interface.rust uses a type in tauri_bundler.bundle.settings.
tauri_cli.interface.rust uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri_cli.interface.rust, while a change to tauri_cli.interface.rust can't break tauri_bundler.bundle.settings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→30 tauri_cli.interface.rust uses tauri_cli.helpers.configpart of a loop✕
Connections
1 pair of types, where a type in tauri_cli.interface.rust uses a type in tauri_cli.helpers.config.
tauri_cli.interface.rust uses tauri_cli.helpers.config, so a change to tauri_cli.helpers.config can break tauri_cli.interface.rust, while a change to tauri_cli.interface.rust can't break tauri_cli.helpers.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri_runtime.webview uses tauri_runtime.dpi, so a change to tauri_runtime.dpi can break tauri_runtime.webview, while a change to tauri_runtime.webview can't break tauri_runtime.dpi.
Position
Below the diagonal: tauri_runtime.webview uses a module listed above it, which is the healthy direction.
17→20 tauri_runtime.webview uses tauri_utils.configpart of a loop✕
Connections
6 pairs of types, where a type in tauri_runtime.webview uses a type in tauri_utils.config.
tauri_runtime.webview uses tauri_utils.config, so a change to tauri_utils.config can break tauri_runtime.webview, while a change to tauri_runtime.webview can't break tauri_utils.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→29 tauri_runtime.webview uses tauri_bundler.bundle.settingspart of a loop✕
Connections
1 pair of types, where a type in tauri_runtime.webview uses a type in tauri_bundler.bundle.settings.
tauri_runtime.webview uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri_runtime.webview, while a change to tauri_runtime.webview can't break tauri_bundler.bundle.settings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri_utils.config_v1 uses tauri_cli.interface.rust.cargo_config, so a change to tauri_cli.interface.rust.cargo_config can break tauri_utils.config_v1, while a change to tauri_utils.config_v1 can't break tauri_cli.interface.rust.cargo_config.
Position
Below the diagonal: tauri_utils.config_v1 uses a module listed above it, which is the healthy direction.
tauri_utils.config_v1 uses tauri_cli.interface.rust, so a change to tauri_cli.interface.rust can break tauri_utils.config_v1, while a change to tauri_utils.config_v1 can't break tauri_cli.interface.rust.
Position
Below the diagonal: tauri_utils.config_v1 uses a module listed above it, which is the healthy direction.
18→20 tauri_utils.config_v1 uses tauri_utils.configpart of a loop✕
Connections
20 pairs of types, where a type in tauri_utils.config_v1 uses a type in tauri_utils.config.
tauri_utils.config_v1 uses tauri_utils.config, so a change to tauri_utils.config can break tauri_utils.config_v1, while a change to tauri_utils.config_v1 can't break tauri_utils.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→29 tauri_utils.config_v1 uses tauri_bundler.bundle.settingspart of a loop✕
Connections
1 pair of types, where a type in tauri_utils.config_v1 uses a type in tauri_bundler.bundle.settings.
tauri_utils.config_v1 uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri_utils.config_v1, while a change to tauri_utils.config_v1 can't break tauri_bundler.bundle.settings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri.menu uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri.menu, while a change to tauri.menu can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri.menu uses a module listed above it, which is the healthy direction.
19→26 tauri.menu uses tauri.test.mock_runtimepart of a loop✕
Connections
3 pairs of types, where a type in tauri.menu uses a type in tauri.test.mock_runtime.
tauri.menu uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri.menu, while a change to tauri.menu can't break tauri.test.mock_runtime.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri_utils.config uses tauri_cli.interface.rust.cargo_config, so a change to tauri_cli.interface.rust.cargo_config can break tauri_utils.config, while a change to tauri_utils.config can't break tauri_cli.interface.rust.cargo_config.
Position
Below the diagonal: tauri_utils.config uses a module listed above it, which is the healthy direction.
tauri_utils.config uses tauri_utils.acl.value, so a change to tauri_utils.acl.value can break tauri_utils.config, while a change to tauri_utils.config can't break tauri_utils.acl.value.
Position
Below the diagonal: tauri_utils.config uses a module listed above it, which is the healthy direction.
tauri_utils.config uses tauri_runtime.webview, so a change to tauri_runtime.webview can break tauri_utils.config, while a change to tauri_utils.config can't break tauri_runtime.webview.
Position
Below the diagonal: tauri_utils.config uses a module listed above it, which is the healthy direction.
tauri_utils.config uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri_utils.config, while a change to tauri_utils.config can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri_utils.config uses a module listed above it, which is the healthy direction.
20→28 tauri_utils.config uses tauri.image.pluginpart of a loop✕
Connections
2 pairs of types, where a type in tauri_utils.config uses a type in tauri.image.plugin.
tauri_utils.config uses tauri.image.plugin, so a change to tauri.image.plugin can break tauri_utils.config, while a change to tauri_utils.config can't break tauri.image.plugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→29 tauri_utils.config uses tauri_bundler.bundle.settingspart of a loop✕
Connections
3 pairs of types, where a type in tauri_utils.config uses a type in tauri_bundler.bundle.settings.
tauri_utils.config uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri_utils.config, while a change to tauri_utils.config can't break tauri_bundler.bundle.settings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→37 tauri_utils.config uses tauri.apppart of a loop✕
Connections
1 pair of types, where a type in tauri_utils.config uses a type in tauri.app.
tauri.manager uses tauri_cli.interface.rust.cargo_config, so a change to tauri_cli.interface.rust.cargo_config can break tauri.manager, while a change to tauri.manager can't break tauri_cli.interface.rust.cargo_config.
Position
Below the diagonal: tauri.manager uses a module listed above it, which is the healthy direction.
tauri.manager uses tauri.ipc.authority, so a change to tauri.ipc.authority can break tauri.manager, while a change to tauri.manager can't break tauri.ipc.authority.
Position
Below the diagonal: tauri.manager uses a module listed above it, which is the healthy direction.
tauri.manager uses tauri_utils.config, so a change to tauri_utils.config can break tauri.manager, while a change to tauri.manager can't break tauri_utils.config.
Position
Below the diagonal: tauri.manager uses a module listed above it, which is the healthy direction.
21→26 tauri.manager uses tauri.test.mock_runtimepart of a loop✕
Connections
2 pairs of types, where a type in tauri.manager uses a type in tauri.test.mock_runtime.
tauri.manager uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri.manager, while a change to tauri.manager can't break tauri.test.mock_runtime.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→27 tauri.manager uses tauri.pluginpart of a loop✕
Connections
1 pair of types, where a type in tauri.manager uses a type in tauri.plugin.
tauri_runtime.window uses tauri.menu.plugin, so a change to tauri.menu.plugin can break tauri_runtime.window, while a change to tauri_runtime.window can't break tauri.menu.plugin.
Position
Below the diagonal: tauri_runtime.window uses a module listed above it, which is the healthy direction.
tauri_runtime.window uses tauri_runtime.webview, so a change to tauri_runtime.webview can break tauri_runtime.window, while a change to tauri_runtime.window can't break tauri_runtime.webview.
Position
Below the diagonal: tauri_runtime.window uses a module listed above it, which is the healthy direction.
tauri_runtime.window uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri_runtime.window, while a change to tauri_runtime.window can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri_runtime.window uses a module listed above it, which is the healthy direction.
tauri_runtime.window uses tauri_utils.config, so a change to tauri_utils.config can break tauri_runtime.window, while a change to tauri_runtime.window can't break tauri_utils.config.
Position
Below the diagonal: tauri_runtime.window uses a module listed above it, which is the healthy direction.
22→25 tauri_runtime.window uses tauri.windowpart of a loop✕
Connections
1 pair of types, where a type in tauri_runtime.window uses a type in tauri.window.
tauri_runtime.window uses tauri.window, so a change to tauri.window can break tauri_runtime.window, while a change to tauri_runtime.window can't break tauri.window.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→28 tauri_runtime.window uses tauri.image.pluginpart of a loop✕
Connections
1 pair of types, where a type in tauri_runtime.window uses a type in tauri.image.plugin.
tauri_runtime.window uses tauri.image.plugin, so a change to tauri.image.plugin can break tauri_runtime.window, while a change to tauri_runtime.window can't break tauri.image.plugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in tauri.webview uses a type in tauri_runtime.dpi.
The types involved
tauri.webview.Webview → tauri_runtime.dpi.Rect
Direction
tauri.webview uses tauri_runtime.dpi, so a change to tauri_runtime.dpi can break tauri.webview, while a change to tauri.webview can't break tauri_runtime.dpi.
Position
Below the diagonal: tauri.webview uses a module listed above it, which is the healthy direction.
tauri.webview uses tauri.ipc.authority, so a change to tauri.ipc.authority can break tauri.webview, while a change to tauri.webview can't break tauri.ipc.authority.
Position
Below the diagonal: tauri.webview uses a module listed above it, which is the healthy direction.
tauri.webview uses tauri_runtime.webview, so a change to tauri_runtime.webview can break tauri.webview, while a change to tauri.webview can't break tauri_runtime.webview.
Position
Below the diagonal: tauri.webview uses a module listed above it, which is the healthy direction.
tauri.webview uses tauri_utils.config, so a change to tauri_utils.config can break tauri.webview, while a change to tauri.webview can't break tauri_utils.config.
Position
Below the diagonal: tauri.webview uses a module listed above it, which is the healthy direction.
tauri.webview uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri.webview, while a change to tauri.webview can't break tauri.test.mock_runtime.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→28 tauri.webview uses tauri.image.pluginpart of a loop✕
Connections
1 pair of types, where a type in tauri.webview uses a type in tauri.image.plugin.
tauri.webview uses tauri.image.plugin, so a change to tauri.image.plugin can break tauri.webview, while a change to tauri.webview can't break tauri.image.plugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→29 tauri.webview uses tauri_bundler.bundle.settingspart of a loop✕
Connections
1 pair of types, where a type in tauri.webview uses a type in tauri_bundler.bundle.settings.
tauri.webview uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri.webview, while a change to tauri.webview can't break tauri_bundler.bundle.settings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→35 tauri.webview uses tauri.ipc.commandpart of a loop✕
Connections
2 pairs of types, where a type in tauri.webview uses a type in tauri.ipc.command.
tauri.webview uses tauri.ipc.command, so a change to tauri.ipc.command can break tauri.webview, while a change to tauri.webview can't break tauri.ipc.command.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri_runtime uses tauri_runtime.dpi, so a change to tauri_runtime.dpi can break tauri_runtime, while a change to tauri_runtime can't break tauri_runtime.dpi.
Position
Below the diagonal: tauri_runtime uses a module listed above it, which is the healthy direction.
tauri_runtime uses tauri.menu.plugin, so a change to tauri.menu.plugin can break tauri_runtime, while a change to tauri_runtime can't break tauri.menu.plugin.
Position
Below the diagonal: tauri_runtime uses a module listed above it, which is the healthy direction.
tauri_runtime uses tauri_runtime.webview, so a change to tauri_runtime.webview can break tauri_runtime, while a change to tauri_runtime can't break tauri_runtime.webview.
Position
Below the diagonal: tauri_runtime uses a module listed above it, which is the healthy direction.
tauri_runtime uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri_runtime, while a change to tauri_runtime can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri_runtime uses a module listed above it, which is the healthy direction.
tauri_runtime uses tauri_utils.config, so a change to tauri_utils.config can break tauri_runtime, while a change to tauri_runtime can't break tauri_utils.config.
Position
Below the diagonal: tauri_runtime uses a module listed above it, which is the healthy direction.
tauri_runtime uses tauri_runtime.window, so a change to tauri_runtime.window can break tauri_runtime, while a change to tauri_runtime can't break tauri_runtime.window.
Position
Below the diagonal: tauri_runtime uses a module listed above it, which is the healthy direction.
24→25 tauri_runtime uses tauri.windowpart of a loop✕
Connections
2 pairs of types, where a type in tauri_runtime uses a type in tauri.window.
tauri_runtime uses tauri.image.plugin, so a change to tauri.image.plugin can break tauri_runtime, while a change to tauri_runtime can't break tauri.image.plugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→29 tauri_runtime uses tauri_bundler.bundle.settingspart of a loop✕
Connections
2 pairs of types, where a type in tauri_runtime uses a type in tauri_bundler.bundle.settings.
tauri_runtime uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri_runtime, while a change to tauri_runtime can't break tauri_bundler.bundle.settings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri.window uses tauri_runtime.dpi, so a change to tauri_runtime.dpi can break tauri.window, while a change to tauri.window can't break tauri_runtime.dpi.
Position
Below the diagonal: tauri.window uses a module listed above it, which is the healthy direction.
tauri.window uses tauri_runtime.webview, so a change to tauri_runtime.webview can break tauri.window, while a change to tauri.window can't break tauri_runtime.webview.
Position
Below the diagonal: tauri.window uses a module listed above it, which is the healthy direction.
tauri.window uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri.window, while a change to tauri.window can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri.window uses a module listed above it, which is the healthy direction.
tauri.window uses tauri_utils.config, so a change to tauri_utils.config can break tauri.window, while a change to tauri.window can't break tauri_utils.config.
Position
Below the diagonal: tauri.window uses a module listed above it, which is the healthy direction.
tauri.window uses tauri_runtime.window, so a change to tauri_runtime.window can break tauri.window, while a change to tauri.window can't break tauri_runtime.window.
Position
Below the diagonal: tauri.window uses a module listed above it, which is the healthy direction.
tauri.window uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri.window, while a change to tauri.window can't break tauri.test.mock_runtime.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→35 tauri.window uses tauri.ipc.commandpart of a loop✕
Connections
2 pairs of types, where a type in tauri.window uses a type in tauri.ipc.command.
tauri.window uses tauri.ipc.command, so a change to tauri.ipc.command can break tauri.window, while a change to tauri.window can't break tauri.ipc.command.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri.test.mock_runtime uses tauri_runtime.dpi, so a change to tauri_runtime.dpi can break tauri.test.mock_runtime, while a change to tauri.test.mock_runtime can't break tauri_runtime.dpi.
Position
Below the diagonal: tauri.test.mock_runtime uses a module listed above it, which is the healthy direction.
tauri.test.mock_runtime uses tauri.menu.plugin, so a change to tauri.menu.plugin can break tauri.test.mock_runtime, while a change to tauri.test.mock_runtime can't break tauri.menu.plugin.
Position
Below the diagonal: tauri.test.mock_runtime uses a module listed above it, which is the healthy direction.
tauri.test.mock_runtime uses tauri_runtime.webview, so a change to tauri_runtime.webview can break tauri.test.mock_runtime, while a change to tauri.test.mock_runtime can't break tauri_runtime.webview.
Position
Below the diagonal: tauri.test.mock_runtime uses a module listed above it, which is the healthy direction.
tauri.test.mock_runtime uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri.test.mock_runtime, while a change to tauri.test.mock_runtime can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri.test.mock_runtime uses a module listed above it, which is the healthy direction.
tauri.test.mock_runtime uses tauri_utils.config, so a change to tauri_utils.config can break tauri.test.mock_runtime, while a change to tauri.test.mock_runtime can't break tauri_utils.config.
Position
Below the diagonal: tauri.test.mock_runtime uses a module listed above it, which is the healthy direction.
tauri.test.mock_runtime uses tauri_runtime.window, so a change to tauri_runtime.window can break tauri.test.mock_runtime, while a change to tauri.test.mock_runtime can't break tauri_runtime.window.
Position
Below the diagonal: tauri.test.mock_runtime uses a module listed above it, which is the healthy direction.
tauri.test.mock_runtime uses tauri_runtime, so a change to tauri_runtime can break tauri.test.mock_runtime, while a change to tauri.test.mock_runtime can't break tauri_runtime.
Position
Below the diagonal: tauri.test.mock_runtime uses a module listed above it, which is the healthy direction.
tauri.test.mock_runtime uses tauri.window, so a change to tauri.window can break tauri.test.mock_runtime, while a change to tauri.test.mock_runtime can't break tauri.window.
Position
Below the diagonal: tauri.test.mock_runtime uses a module listed above it, which is the healthy direction.
26→28 tauri.test.mock_runtime uses tauri.image.pluginpart of a loop✕
Connections
3 pairs of types, where a type in tauri.test.mock_runtime uses a type in tauri.image.plugin.
tauri.test.mock_runtime uses tauri.image.plugin, so a change to tauri.image.plugin can break tauri.test.mock_runtime, while a change to tauri.test.mock_runtime can't break tauri.image.plugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→29 tauri.test.mock_runtime uses tauri_bundler.bundle.settingspart of a loop✕
Connections
2 pairs of types, where a type in tauri.test.mock_runtime uses a type in tauri_bundler.bundle.settings.
tauri.test.mock_runtime uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri.test.mock_runtime, while a change to tauri.test.mock_runtime can't break tauri_bundler.bundle.settings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri.plugin uses tauri_runtime.webview, so a change to tauri_runtime.webview can break tauri.plugin, while a change to tauri.plugin can't break tauri_runtime.webview.
Position
Below the diagonal: tauri.plugin uses a module listed above it, which is the healthy direction.
tauri.plugin uses tauri_utils.config, so a change to tauri_utils.config can break tauri.plugin, while a change to tauri.plugin can't break tauri_utils.config.
Position
Below the diagonal: tauri.plugin uses a module listed above it, which is the healthy direction.
tauri.plugin uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri.plugin, while a change to tauri.plugin can't break tauri.test.mock_runtime.
Position
Below the diagonal: tauri.plugin uses a module listed above it, which is the healthy direction.
tauri.image.plugin uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri.image.plugin, while a change to tauri.image.plugin can't break tauri.test.mock_runtime.
Position
Below the diagonal: tauri.image.plugin uses a module listed above it, which is the healthy direction.
tauri.image.plugin uses tauri.plugin, so a change to tauri.plugin can break tauri.image.plugin, while a change to tauri.image.plugin can't break tauri.plugin.
Position
Below the diagonal: tauri.image.plugin uses a module listed above it, which is the healthy direction.
tauri_bundler.bundle.settings uses tauri_utils.config, so a change to tauri_utils.config can break tauri_bundler.bundle.settings, while a change to tauri_bundler.bundle.settings can't break tauri_utils.config.
Position
Below the diagonal: tauri_bundler.bundle.settings uses a module listed above it, which is the healthy direction.
tauri_bundler.bundle.settings uses tauri.image.plugin, so a change to tauri.image.plugin can break tauri_bundler.bundle.settings, while a change to tauri_bundler.bundle.settings can't break tauri.image.plugin.
Position
Below the diagonal: tauri_bundler.bundle.settings uses a module listed above it, which is the healthy direction.
tauri_cli.helpers.config uses tauri_cli.interface.rust.cargo_config, so a change to tauri_cli.interface.rust.cargo_config can break tauri_cli.helpers.config, while a change to tauri_cli.helpers.config can't break tauri_cli.interface.rust.cargo_config.
Position
Below the diagonal: tauri_cli.helpers.config uses a module listed above it, which is the healthy direction.
tauri_cli.helpers.config uses tauri_utils.acl.value, so a change to tauri_utils.acl.value can break tauri_cli.helpers.config, while a change to tauri_cli.helpers.config can't break tauri_utils.acl.value.
Position
Below the diagonal: tauri_cli.helpers.config uses a module listed above it, which is the healthy direction.
tauri_cli.helpers.config uses tauri_utils.config, so a change to tauri_utils.config can break tauri_cli.helpers.config, while a change to tauri_cli.helpers.config can't break tauri_utils.config.
Position
Below the diagonal: tauri_cli.helpers.config uses a module listed above it, which is the healthy direction.
tauri_cli.helpers.config uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri_cli.helpers.config, while a change to tauri_cli.helpers.config can't break tauri_bundler.bundle.settings.
Position
Below the diagonal: tauri_cli.helpers.config uses a module listed above it, which is the healthy direction.
30→31 tauri_cli.helpers.config uses tauri_cli.mobilepart of a loop✕
Connections
2 pairs of types, where a type in tauri_cli.helpers.config uses a type in tauri_cli.mobile.
tauri_cli.helpers.config uses tauri_cli.mobile, so a change to tauri_cli.mobile can break tauri_cli.helpers.config, while a change to tauri_cli.helpers.config can't break tauri_cli.mobile.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri_cli.mobile uses tauri_cli.acl.capability.new, so a change to tauri_cli.acl.capability.new can break tauri_cli.mobile, while a change to tauri_cli.mobile can't break tauri_cli.acl.capability.new.
Position
Below the diagonal: tauri_cli.mobile uses a module listed above it, which is the healthy direction.
tauri_cli.mobile uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri_cli.mobile, while a change to tauri_cli.mobile can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri_cli.mobile uses a module listed above it, which is the healthy direction.
tauri_cli.mobile uses tauri_cli.helpers.config, so a change to tauri_cli.helpers.config can break tauri_cli.mobile, while a change to tauri_cli.mobile can't break tauri_cli.helpers.config.
Position
Below the diagonal: tauri_cli.mobile uses a module listed above it, which is the healthy direction.
31→37 tauri_cli.mobile uses tauri.apppart of a loop✕
Connections
1 pair of types, where a type in tauri_cli.mobile uses a type in tauri.app.
The types involved
tauri_cli.mobile.mobile$module → tauri.app.App
Direction
tauri_cli.mobile uses tauri.app, so a change to tauri.app can break tauri_cli.mobile, while a change to tauri_cli.mobile can't break tauri.app.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri_cli.mobile.android.dev uses tauri_cli.acl.capability.new, so a change to tauri_cli.acl.capability.new can break tauri_cli.mobile.android.dev, while a change to tauri_cli.mobile.android.dev can't break tauri_cli.acl.capability.new.
Position
Below the diagonal: tauri_cli.mobile.android.dev uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.android.dev uses tauri_cli.helpers.app_paths, so a change to tauri_cli.helpers.app_paths can break tauri_cli.mobile.android.dev, while a change to tauri_cli.mobile.android.dev can't break tauri_cli.helpers.app_paths.
Position
Below the diagonal: tauri_cli.mobile.android.dev uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.android.dev uses tauri_cli.interface.rust.cargo_config, so a change to tauri_cli.interface.rust.cargo_config can break tauri_cli.mobile.android.dev, while a change to tauri_cli.mobile.android.dev can't break tauri_cli.interface.rust.cargo_config.
Position
Below the diagonal: tauri_cli.mobile.android.dev uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.android.dev uses tauri_utils, so a change to tauri_utils can break tauri_cli.mobile.android.dev, while a change to tauri_cli.mobile.android.dev can't break tauri_utils.
Position
Below the diagonal: tauri_cli.mobile.android.dev uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.android.dev uses tauri_cli, so a change to tauri_cli can break tauri_cli.mobile.android.dev, while a change to tauri_cli.mobile.android.dev can't break tauri_cli.
Position
Below the diagonal: tauri_cli.mobile.android.dev uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.android.dev uses tauri_cli.interface.rust, so a change to tauri_cli.interface.rust can break tauri_cli.mobile.android.dev, while a change to tauri_cli.mobile.android.dev can't break tauri_cli.interface.rust.
Position
Below the diagonal: tauri_cli.mobile.android.dev uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.android.dev uses tauri_utils.config, so a change to tauri_utils.config can break tauri_cli.mobile.android.dev, while a change to tauri_cli.mobile.android.dev can't break tauri_utils.config.
Position
Below the diagonal: tauri_cli.mobile.android.dev uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.android.dev uses tauri_cli.helpers.config, so a change to tauri_cli.helpers.config can break tauri_cli.mobile.android.dev, while a change to tauri_cli.mobile.android.dev can't break tauri_cli.helpers.config.
Position
Below the diagonal: tauri_cli.mobile.android.dev uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.android.dev uses tauri_cli.mobile, so a change to tauri_cli.mobile can break tauri_cli.mobile.android.dev, while a change to tauri_cli.mobile.android.dev can't break tauri_cli.mobile.
Position
Below the diagonal: tauri_cli.mobile.android.dev uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri_runtime.dpi, so a change to tauri_runtime.dpi can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri_runtime.dpi.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri.menu.plugin, so a change to tauri.menu.plugin can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri.menu.plugin.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri_runtime.webview, so a change to tauri_runtime.webview can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri_runtime.webview.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri_utils.config, so a change to tauri_utils.config can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri_utils.config.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri_runtime.window, so a change to tauri_runtime.window can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri_runtime.window.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri_runtime, so a change to tauri_runtime can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri_runtime.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri.window, so a change to tauri.window can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri.window.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri.test.mock_runtime.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri.plugin, so a change to tauri.plugin can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri.plugin.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri.image.plugin, so a change to tauri.image.plugin can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri.image.plugin.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri_bundler.bundle.settings, so a change to tauri_bundler.bundle.settings can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri_bundler.bundle.settings.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
tauri_runtime_wry uses tauri_cli.mobile, so a change to tauri_cli.mobile can break tauri_runtime_wry, while a change to tauri_runtime_wry can't break tauri_cli.mobile.
Position
Below the diagonal: tauri_runtime_wry uses a module listed above it, which is the healthy direction.
33→37 tauri_runtime_wry uses tauri.apppart of a loop✕
Connections
2 pairs of types, where a type in tauri_runtime_wry uses a type in tauri.app.
tauri_utils.acl.resolved uses tauri_cli.acl.capability, so a change to tauri_cli.acl.capability can break tauri_utils.acl.resolved, while a change to tauri_utils.acl.resolved can't break tauri_cli.acl.capability.
Position
Below the diagonal: tauri_utils.acl.resolved uses a module listed above it, which is the healthy direction.
tauri_utils.acl.resolved uses tauri_utils.acl.value, so a change to tauri_utils.acl.value can break tauri_utils.acl.resolved, while a change to tauri_utils.acl.resolved can't break tauri_utils.acl.value.
Position
Below the diagonal: tauri_utils.acl.resolved uses a module listed above it, which is the healthy direction.
tauri_utils.acl.resolved uses tauri_cli.mobile, so a change to tauri_cli.mobile can break tauri_utils.acl.resolved, while a change to tauri_utils.acl.resolved can't break tauri_cli.mobile.
Position
Below the diagonal: tauri_utils.acl.resolved uses a module listed above it, which is the healthy direction.
tauri.ipc.command uses tauri_utils.acl.resolved, so a change to tauri_utils.acl.resolved can break tauri.ipc.command, while a change to tauri.ipc.command can't break tauri_utils.acl.resolved.
Position
Below the diagonal: tauri.ipc.command uses a module listed above it, which is the healthy direction.
35→36 tauri.ipc.command uses tauri.ipcpart of a loop✕
Connections
1 pair of types, where a type in tauri.ipc.command uses a type in tauri.ipc.
tauri.ipc uses tauri_utils.acl.value, so a change to tauri_utils.acl.value can break tauri.ipc, while a change to tauri.ipc can't break tauri_utils.acl.value.
Position
Below the diagonal: tauri.ipc uses a module listed above it, which is the healthy direction.
tauri.ipc uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri.ipc, while a change to tauri.ipc can't break tauri.test.mock_runtime.
Position
Below the diagonal: tauri.ipc uses a module listed above it, which is the healthy direction.
tauri.ipc uses tauri_utils.acl.resolved, so a change to tauri_utils.acl.resolved can break tauri.ipc, while a change to tauri.ipc can't break tauri_utils.acl.resolved.
Position
Below the diagonal: tauri.ipc uses a module listed above it, which is the healthy direction.
tauri.app uses tauri_cli.interface.rust.cargo_config, so a change to tauri_cli.interface.rust.cargo_config can break tauri.app, while a change to tauri.app can't break tauri_cli.interface.rust.cargo_config.
Position
Below the diagonal: tauri.app uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in tauri.app uses a type in tauri_utils.config_v1.
The types involved
tauri.app.App → tauri_utils.config_v1.Theme
tauri.app.AppHandle → tauri_utils.config_v1.Theme
Direction
tauri.app uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri.app, while a change to tauri.app can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri.app uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri.image, so a change to tauri.image can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri.image.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri_runtime.webview, so a change to tauri_runtime.webview can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri_runtime.webview.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri.menu, so a change to tauri.menu can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri.menu.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri_utils.config, so a change to tauri_utils.config can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri_utils.config.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri.manager, so a change to tauri.manager can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri.manager.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri_runtime.window, so a change to tauri_runtime.window can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri_runtime.window.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri.webview, so a change to tauri.webview can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri.webview.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri_runtime, so a change to tauri_runtime can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri_runtime.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri.window, so a change to tauri.window can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri.window.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri.test.mock_runtime.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri.ipc.command, so a change to tauri.ipc.command can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri.ipc.command.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
tauri.webview.webview_window uses tauri.app, so a change to tauri.app can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri.app.
Position
Below the diagonal: tauri.webview.webview_window uses a module listed above it, which is the healthy direction.
38→40 tauri.webview.webview_window uses tauripart of a loop✕
Connections
3 pairs of types, where a type in tauri.webview.webview_window uses a type in tauri.
tauri.webview.webview_window uses tauri, so a change to tauri can break tauri.webview.webview_window, while a change to tauri.webview.webview_window can't break tauri.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
tauri_cli.mobile.ios uses tauri_cli.acl.capability, so a change to tauri_cli.acl.capability can break tauri_cli.mobile.ios, while a change to tauri_cli.mobile.ios can't break tauri_cli.acl.capability.
Position
Below the diagonal: tauri_cli.mobile.ios uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in tauri_cli.mobile.ios uses a type in tauri_utils.
The types involved
tauri_cli.mobile.ios.ios$module → tauri_utils.Env
Direction
tauri_cli.mobile.ios uses tauri_utils, so a change to tauri_utils can break tauri_cli.mobile.ios, while a change to tauri_cli.mobile.ios can't break tauri_utils.
Position
Below the diagonal: tauri_cli.mobile.ios uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.ios uses tauri_cli, so a change to tauri_cli can break tauri_cli.mobile.ios, while a change to tauri_cli.mobile.ios can't break tauri_cli.
Position
Below the diagonal: tauri_cli.mobile.ios uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.ios uses tauri_utils.config_v1, so a change to tauri_utils.config_v1 can break tauri_cli.mobile.ios, while a change to tauri_cli.mobile.ios can't break tauri_utils.config_v1.
Position
Below the diagonal: tauri_cli.mobile.ios uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.ios uses tauri_cli.helpers.config, so a change to tauri_cli.helpers.config can break tauri_cli.mobile.ios, while a change to tauri_cli.mobile.ios can't break tauri_cli.helpers.config.
Position
Below the diagonal: tauri_cli.mobile.ios uses a module listed above it, which is the healthy direction.
tauri_cli.mobile.ios uses tauri_cli.mobile, so a change to tauri_cli.mobile can break tauri_cli.mobile.ios, while a change to tauri_cli.mobile.ios can't break tauri_cli.mobile.
Position
Below the diagonal: tauri_cli.mobile.ios uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in tauri_cli.mobile.ios uses a type in tauri.app.
The types involved
tauri_cli.mobile.ios.ios$module → tauri.app.App
Direction
tauri_cli.mobile.ios uses tauri.app, so a change to tauri.app can break tauri_cli.mobile.ios, while a change to tauri_cli.mobile.ios can't break tauri.app.
Position
Below the diagonal: tauri_cli.mobile.ios uses a module listed above it, which is the healthy direction.
tauri uses tauri_cli.interface.rust.cargo_config, so a change to tauri_cli.interface.rust.cargo_config can break tauri, while a change to tauri can't break tauri_cli.interface.rust.cargo_config.
Position
Below the diagonal: tauri uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in tauri uses a type in tauri.test.mock_runtime.
The types involved
tauri.Manager → tauri.test.mock_runtime.Webview
tauri.Manager → tauri.test.mock_runtime.Window
Direction
tauri uses tauri.test.mock_runtime, so a change to tauri.test.mock_runtime can break tauri, while a change to tauri can't break tauri.test.mock_runtime.
Position
Below the diagonal: tauri uses a module listed above it, which is the healthy direction.
tauri uses tauri.webview.webview_window, so a change to tauri.webview.webview_window can break tauri, while a change to tauri can't break tauri.webview.webview_window.
Position
Below the diagonal: tauri uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 52% · Adequate · gated by R3, X4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
190
High / Critical
A03:2025 — Software Supply Chain Failures
17
High / Critical
A07:2025 — Authentication Failures
9
High / Critical
A02:2025 — Security Misconfiguration
5
High / Critical
Roadmap
Immediately resolve the two leaked secrets in REDACTED to secure credentials. Enforce accessibility standards by integrating linting and automated testing into the CI pipeline, while simultaneously fixing structural HTML issues and ensuring visual safety through proper focus styles and contrast ratios. Finally, expand test coverage to include currently unreached production modules to improve overall code reliability.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).
Enforce accessibility in the toolchain: add eslint-plugin-svelte (a11y rules are built in), then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Per-file score 0–10 — a quality signature. Of 163 files carrying findings, judged against the Production bar: 2% slop · 69% mixed · 29% near-clean.
File
Score
Band
Worst signal
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
1.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
1.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.7
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 200
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 516
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 29
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 84 of 84 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 84 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 725 of 745 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 40 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 57 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for packages/cli/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/cli/ was NOT MEASURED: the dependency install for packages/cli/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 6 Maven/Gradle manifest(s) were read, stating a version for 21 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D28 Secrets (history) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `crates/tauri-cli/templates/tauri.conf.json`, `crates/tauri-cli/templates/app/src-tauri/tauri.conf.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `crates/tauri-cli/templates/mobile/android/app/build.gradle.kts`, `crates/tauri-cli/templates/mobile/android/app/src/main/MainActivity.kt`, `crates/tauri-cli/templates/mobile/android/build.gradle.kts`, `crates/tauri-cli/templates/plugin/android/src/main/java/Example.kt`, `crates/tauri-cli/templates/plugin/android/src/main/java/ExamplePlugin.kt`, … (+3 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is an unrecognised JSR-330 (javax.inject / jakarta.inject) container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (crates/tauri-cli/templates/mobile/android/app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: 0bfdb89d57e1aba3a/crates/tauri-cli/templates/mobile/android/settings.gradle line 2
> startup failed:
settings file 'crates/tauri-cli/templates/mo…; runtime evidence skipped (launch chosen because crates/tauri-cli/templates/mobile/android/app/build.gradle.kts applies the Android application plugin and crates/tauri-cli/templates/mobile/android/gradlew builds it).
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Kotlin, Rust, Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, Rust, Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 35 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
43 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was tauri_runtime_wry::handle_user_message at 192. A further 16 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being NativeIcon::from at 56 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/tauri/src/menu/mod.rs (NativeIcon::from at 56), crates/tauri-bundler/src/bundle/category.rs (AppCategory::canonical at 40), crates/tauri-runtime/src/window.rs (CursorIcon::deserialize at 36), crates/tauri-utils/src/config.rs (WindowEffect::to_tokens at 29), crates/tauri/src/menu/plugin.rs (PredefinedMenuItemPayload::create_item at 19), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with tauri_runtime_wry::handle_user_message (cyclomatic 192), tauri_cli::migrate::migrations::v1::config::allowlist_to_permissions (cyclomatic 149). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 5.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
98 method(s) exceeded the cognitive complexity threshold of 15; the worst was tauri_cli::migrate::migrations::v1::config::allowlist_to_permissions at 227.
+ 26 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with tauri_cli::migrate::migrations::v1::config::allowlist_to_permissions (cognitive 227), tauri_runtime_wry::handle_user_message (cognitive 213). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.0 to about 5.7/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.9 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 30 FunctionTooLong finding(s) in God Classes — start with lib.rs (5), dev.rs (3), mod.rs (2). — One of this dimension's main actionable groups (30 warning-level).
Resolve the 19 FileTooLong finding(s) in God Classes — start with mod.rs (8), lib.rs (2), config.rs. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 13 TooManyMethods finding(s) in God Classes — start with mod.rs (4), webview_window.rs (2), menu.rs (2). — One of this dimension's main actionable groups (13 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
90 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 1 of the 94 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 30 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with mod.rs (5), config.rs (4), lib.rs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 10 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), env_system.rs, android.rs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 8 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with project.rs, android.rs, mobile.rs. — One of this dimension's main actionable groups (8 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.7 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
29 production modules (Cargo+npm+SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 14 of the 29 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: tauri-utils
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (4), mock_runtime.rs. — One of this dimension's main actionable groups (5 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution8.7 / 10Strong✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
399 test methods: 357 unit, 3 integration, 0 BDD, 39 e2e. The JavaScript/TypeScript suite contributes 40 `it`/`test` case(s) across 12 test file(s) declaring at least one beside 3 .NET test method(s); its tier split is read from package names and paths only. The Rust suite contributes 356 `#[test]` function(s) across 93 file(s) declaring at least one; its unit/integration split is Cargo's own — 3 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
What to do
Improve Test Distribution — currently 8.7/10. — 399 test methods: 357 unit, 3 integration, 0 BDD, 39 e2e. The JavaScript/TypeScript suite contributes 40 `it`/`test` case(s) across 12 test file(s) declaring at least one beside 3 .NET test method(s); its tier split is read from package names and paths only. The Rust suite contributes 356 `#[test]` function(s) across 93 file(s) declaring at least one; its unit/integration split is Cargo's own — 3 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.2 / 10Stronggated by 3 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 40 tests. Measured on the JavaScript/TypeScript suite only — at least 57 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: init a project and builds it · ×2packages/cli/__tests__/template.spec.ts:26
Test project verifies nothing: packages/clipackages/cli/__tests__/template.spec.ts:26
What to do
Resolve the 2 No assertions finding(s) in Test Quality — start with template.spec.ts, app.spec.ts. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with template.spec.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 993 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 1 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under Apache-2.0 OR MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: crates/tauri-runtime-wry/src/lib.rs (15×192=2880); crates/tauri-build/src/lib.rs (11×41=451); crates/tauri-bundler/src/bundle/windows/nsis/mod.rs (7×57=399) Repeated repair below the complexity floor: crates/tauri-cli/src/interface/rust/desktop.rs (4 of 6 changes were fixes); crates/tauri-cli/src/mobile/mod.rs (4 of 6 changes were fixes); packages/api/src/webview.ts (3 of 4 changes were fixes)
Resolve the 16 Hotspot finding(s) in Churn × Complexity Hotspots — start with lib.rs (2), mod.rs (2), rpm.rs. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with desktop.rs, mod.rs, webview.ts. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.7 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
6 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/tauri-plugin/src/build/mobile.rs. Counted over 205 of the 292 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
67 deducted task-comment markers across 104446 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 62 TodoComment finding(s) in Explicit Debt — start with config.rs (11), mod.rs (10), build.rs (4). — One of this dimension's main actionable groups (62 warning-level).
Resolve the 5 FixmeComment finding(s) in Explicit Debt — start with build.rs (2), schema.rs (2), lib.rs. — One of this dimension's main actionable groups (5 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 32 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
4 of 19 build units (Cargo, Gradle, SwiftPM, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
190 finding(s): 0 critical, 183 high, 7 medium, 0 low. 134 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 11 file(s) — `.docker/cross/linux-runner` (line 74), `crates/tauri-cli/templates/app/src-tauri/tauri.conf.json`, `crates/tauri-cli/templates/mobile/ios/project.yml`, `crates/tauri-cli/templates/plugin/REDACTED`, `crates/tauri-cli/templates/plugin/.github/workflows/clippy.yml`, … (+6 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 10 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 12 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 20 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (20 issue-level).
Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (11 issue-level).
No action in Static Analysis (SAST) — all 134 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (134 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 4 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
4 of 205 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/tauri-bundler/src/bundle/linux/freedesktop/mod.rs. Counted over 205 of the 292 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 3 Change coupling finding(s) in Change Coupling — start with lib.rs, webview_window.rs, listener.rs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 17 platform declaration(s) and 21 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels5.2 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — crates/tauri-cli/templates/plugin/__example-api/tauri-app/src/lib/Greet.svelte:15
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure4.1 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — crates/tauri-cli/templates/plugin/__example-basic/vanilla/public/index.html:1
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — crates/tauri-cli/templates/plugin/__example-basic/vanilla/public/index.html:1
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — crates/tauri-cli/templates/plugin/__example-basic/vanilla/public/index.html:1
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — crates/tauri-cli/templates/plugin/__example-api/tauri-app/src/style.css:80
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no a11y linter (eslint-plugin-svelte (a11y rules are built in)) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-svelte (a11y rules are built in), then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 12 of 48 project(s) that lack one — worth up to 0.5 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability6.1 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 10/14 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/tauri-driver`, `crates/tauri-schema-generator`, `crates/tauri-schema-worker`, `packages/cli`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`ureq::Agent::config_builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — crates/tauri-bundler/src/utils/http_utils.rs:54, crates/tauri-bundler/src/utils/http_utils.rs:69, crates/tauri-cli/src/helpers/http.rs:11
`Client::builder(TokioExecutor` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — crates/tauri-driver/src/server.rs:199
`reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — crates/tauri/src/protocol/tauri.rs:41
What to do
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.existsSync` in `onPrepare` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×5) — packages/api-e2e/wdio.conf.ts:63, packages/api-e2e/wdio.conf.ts:108, packages/api-e2e/wdio.mobile.ts:104, …
`spawnSync` in `onPrepare` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/api-e2e/wdio.conf.ts:96
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety5.9 / 10Adequate✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
26 typed · 18 plain JS — the untyped files are crates/tauri-cli/src/dev/auto-reload.js, REDACTED, crates/tauri/scripts/core.js, crates/tauri/scripts/freeze_prototype.js, crates/tauri/scripts/init.js, crates/tauri/scripts/ipc-protocol.js (+12 more).
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
packages/api/src/menu/menu.ts:129 · packages/api/src/menu/submenu.ts:118 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/api/src/menu/menu.ts:129
packages/api/src/webview.ts:769 · packages/api/src/window.ts:2407 — the 2 copies are spread across 2 files, and the CITED SPAN is inside a TYPE DECLARATION, not executable code. There is no function to extract and no call site to call one from, so do not read this as an extract-a-helper row: the collapse a type offers is a generic — name the shape once, parameterised over the part that varies, and have each copy instantiate it. First check what actually differs between the copies: where they are a MATRIX of cases (one entry per input, differing precisely in the case each one pins), the repetition IS the enumeration and collapsing it would delete cases rather than de-duplicate anything — leave those alone. Reported because the copies that are not a matrix drift apart the first time only one of them is edited. — packages/api/src/webview.ts:769
packages/api/src/webview.ts:376 · packages/api/src/window.ts:547 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/api/src/webview.ts:376
packages/api/src/dpi.ts:131 · packages/api/src/dpi.ts:345 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/api/src/dpi.ts:131
packages/api/src/menu/checkMenuItem.ts:10 · packages/api/src/menu/iconMenuItem.ts:133 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/api/src/menu/checkMenuItem.ts:10
packages/api/src/dpi.ts:60 · packages/api/src/dpi.ts:278 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/api/src/dpi.ts:60
packages/api/src/webviewWindow.ts:58 · packages/api/src/window.ts:317 — the two spans are one implementation copied and then locally edited — 203 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/api/src/webviewWindow.ts:58
packages/api/src/menu/checkMenuItem.ts:13 · packages/api/src/menu/iconMenuItem.ts:145 · packages/api/src/menu/menuItem.ts:67 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/api/src/menu/checkMenuItem.ts:13
packages/api/src/webview.ts:266 · packages/api/src/window.ts:418 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/api/src/webview.ts:266
REDACTED:79 · REDACTED:40 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — REDACTED:79
packages/api/src/menu/checkMenuItem.ts:27 · packages/api/src/menu/iconMenuItem.ts:158 · packages/api/src/menu/menuItem.ts:77 · packages/api/src/menu/predefinedMenuItem.ts:183 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/api/src/menu/checkMenuItem.ts:27
packages/api/src/webview.ts:516 · packages/api/src/window.ts:1578 · packages/api/src/window.ts:1679 · packages/api/src/window.ts:1989 — the 4 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/api/src/webview.ts:516
packages/api/src/webviewWindow.ts:204 · packages/api/src/webviewWindow.ts:242 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/api/src/webviewWindow.ts:204
packages/api/src/window.ts:503 · packages/api/src/window.ts:541 — all 2 copies are in the same file, and the CITED SPAN is inside a TYPE DECLARATION, not executable code. There is no function to extract and no call site to call one from, so do not read this as an extract-a-helper row: the collapse a type offers is a generic — name the shape once, parameterised over the part that varies, and have each copy instantiate it. First check what actually differs between the copies: where they are a MATRIX of cases (one entry per input, differing precisely in the case each one pins), the repetition IS the enumeration and collapsing it would delete cases rather than de-duplicate anything — leave those alone. Reported because the copies that are not a matrix drift apart the first time only one of them is edited. — packages/api/src/window.ts:503
packages/api/src/menu/base.ts:63 · packages/api/src/menu/base.ts:113 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/api/src/menu/base.ts:63
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
newMenu has cyclomatic complexity 17 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/api/src/menu/base.ts:86
serializeIpcPayload has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:95
Do you agree with this assessment?
R3 · Large Files3.3 / 10Weak✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
packages/api/src/window.ts has 3081 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/window.ts:1
packages/api/src/webview.ts has 1010 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/webview.ts:1
packages/api/src/path.ts has 823 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/path.ts:1
packages/api/src/core.ts has 587 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/core.ts:1
packages/api/src/tray.ts has 472 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/tray.ts:1
packages/api/src/dpi.ts has 441 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/dpi.ts:1
packages/api-e2e/wdio.mobile.ts has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api-e2e/wdio.mobile.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage0.5 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×35) — packages/api/src/window.ts:1, packages/api/src/webview.ts:1, packages/api/src/path.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in packages/api-e2e/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
packages/api/src/image.ts → packages/api/src/menu/iconMenuItem.ts → packages/api/src/image.ts (one verified cycle inside a mutually-dependent group of 12 files) — packages/api/src/image.ts:30
What to do
Break each cycle by extracting the shared piece into a module both sides can import.
Other · Security — Read from this repository's Rust source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (`.serve_connection(` (crates/tauri-driver/src/server.rs:219)), so its Rust source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Rust spelling appears in production source, not proven on every route. A Rocket 0.5 application is credited the headers Rocket's default `Shield` sends unless it attaches its own, and its cookie jar's SameSite=Strict default; a session middleware its default cookie flags.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — crates/tauri-bundler/src/bundle/linux/debian.rs:312, crates/tauri-bundler/src/utils/http_utils.rs:127
Set: Content-Security-Policy, Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy, Cross-Origin-Resource-Policy, Permissions-Policy, X-Content-Type-Options. Missing: Strict-Transport-Security, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.0 on this card.) The server: `.serve_connection(` (crates/tauri-driver/src/server.rs:219).
No handler of this repository's Rust server answers 400, 413 or 422 (`StatusCode::BAD_REQUEST`, `HttpResponse::BadRequest()`, `Status::BadRequest`, tonic `Status::invalid_argument`), and nothing declares validation — no `validator`/`garde` derive, no body limit (`DefaultBodyLimit::max`, `RequestBodyLimitLayer`, `JsonConfig::default().limit(…)`, Rocket `Limits`) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: `.serve_connection(` (crates/tauri-driver/src/server.rs:219).
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `crates/tauri-bundler/src/bundle/linux/debian.rs:312` (`md5::Context::new`), `crates/tauri-bundler/src/utils/http_utils.rs:127` (`Sha1::new`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Add Strict-Transport-Security, X-Frame-Options beside the headers the Rust server already sets.
Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it: derive `validator::Validate` (or `garde::Validate`) on the request types and reject with `StatusCode::BAD_REQUEST`, and cap bodies with `DefaultBodyLimit::max`/`RequestBodyLimitLayer` or actix's `JsonConfig::default().limit(…)`.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — crates/tauri/mobile/android/src/main/java/app/tauri/FsUtils.kt:148
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — crates/tauri/mobile/android/src/main/java/app/tauri/PermissionHelper.kt:81
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`warn!` at line 1135 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tauri-runtime-wry/src/lib.rs:1135
`warn!` at line 3557 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tauri-runtime-wry/src/lib.rs:3557
`error!` at line 409 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tauri/src/webview/mod.rs:409
`error!` at line 422 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tauri/src/webview/mod.rs:422
`error!` at line 2013 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tauri/src/webview/mod.rs:2013
`trace!` at line 424 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/tauri/src/ipc/protocol.rs:424
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 46 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: 0bfdb89d57e1aba3a/crates/tauri-cli/templates/mobile/android/settings.gradle line 2
> startup failed:
settings file 'crates/tauri-cli/templates/mo…; runtime evidence skipped (launch chosen because crates/tauri-cli/templates/mobile/android/app/build.gradle.kts applies the Android application plugin and crates/tauri-cli/templates/mobile/android/gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D12 Dependency Hygiene — Not scored — 6 Maven/Gradle manifest(s) were read, stating a version for 21 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Kotlin, Rust, Swift, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, Rust, Swift surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .kt, .rs, .swift, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — packages/cli/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 61 value object(s); 10 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Kotlin and Swift code has 3,145 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC2 · Forms & labels· <input> without a programmatic label · ×1
<input> without a programmatic label crates/tauri-cli/templates/plugin/__example-api/tauri-app/src/lib/Greet.svelte:15— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<html> without a lang crates/tauri-cli/templates/plugin/__example-basic/vanilla/public/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> crates/tauri-cli/templates/plugin/__example-basic/vanilla/public/index.html:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
TodoComment packages/api/src/core.ts:70— // TODO: Make this not optional in v3 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/api/src/core.ts:300— // TODO(v3): remove this fallback — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/api/src/event.ts:58— // TODO(v3): mark this as Promise<void> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:863— // TODO: Change the alias to installer-icon in v3 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:2568— // TODO: Remove this in v3, use a BTreeMap instead of a HashMap — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:2752— // TODO: Remove this in v3, use a BTreeMap instead of a HashMap — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:2768— // TODO: Remove this in v3, use a BTreeMap instead of a HashMap — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:4161— // TODO: Remove this in v3, use a BTreeMap instead of a HashMap — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:4710— // TODO: Remove this in v3, use a BTreeMap instead of a HashMap — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:4773— // TODO: Remove this in v3, use a BTreeMap instead of a HashMap — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:4966— // TODO: Remove this in v3, use a BTreeMap instead of a HashMap — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:3522— // TODO: Remove in v3 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:3535— // TODO: Remove in v3 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config.rs:5012— // TODO: create a test that compares a config to a json config — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config_v1/mod.rs:3070— // TODO: create a test that compares a config to a json config — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/html.rs:284— // TODO: Verify this, this is not found in the HTML spec, see https://github.com/tauri-apps/tauri/pull/14265#discussion_r2415396842
TodoComment crates/tauri-utils/src/html2.rs:163— // TODO: Verify this, this is not found in the HTML spec, see https://github.com/tauri-apps/tauri/pull/14265#discussion_r2415396842
TodoComment crates/tauri-utils/src/resources.rs:236— // TODO: This behavior is a confusing special case, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/config_v1/mod.rs:1938— // TODO: in v2, parse into a String or a custom type that perserves the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/acl/build.rs:234— // TODO: remove this before stable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/acl/build.rs:403— // TODO: We have way too many duplicated code around getting the config files, e.g. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/acl/resolved.rs:131— // TODO: Take `base_scope_id` here and remove `resolve_with_base_scope_id` in v3, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-utils/src/acl/schema.rs:30— // TODO: once MSRV is high enough, remove generic and use impl <trait> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-runtime-wry/src/lib.rs:778— // TODO: find a proper way to prevent webview being pushed out of the window. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/tauri-runtime-wry/src/webview.rs:21— // not be mutated through. TODO: change these to `*const c_void` in v3 (breaking change). — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
tauri_cli::migrate::migrations::v1::config::allowlist_to_permissions (cognitive 227) crates/tauri-cli/src/migrate/migrations/v1/config.rs:470— tauri_cli::migrate::migrations::v1::config::allowlist_to_permissions has cognitive complexity 227 (threshold 15). Drivers by points: if/else 149 (155 pts), boolean chains 71, match/switch 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
tauri_cli::migrate::migrations::v1::frontend::migrate_imports (cognitive 93) crates/tauri-cli/src/migrate/migrations/v1/frontend.rs:137— tauri_cli::migrate::migrations::v1::frontend::migrate_imports has cognitive complexity 93 (threshold 15). Drivers by points: if/else 17 (55 pts), match/switch 4 (22 pts), loops 5 (13 pts), boolean chains 3 (nesting depth added 64). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::migrate::migrations::v1::config::process_bundle (cognitive 85) crates/tauri-cli/src/migrate/migrations/v1/config.rs:261— tauri_cli::migrate::migrations::v1::config::process_bundle has cognitive complexity 85 (threshold 15). Drivers by points: if/else 26 (84 pts), boolean chains 1 (nesting depth added 58). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tauri_cli::helpers::pbxproj::parse (cognitive 84) crates/tauri-cli/src/helpers/pbxproj.rs:13— tauri_cli::helpers::pbxproj::parse has cognitive complexity 84 (threshold 15). Drivers by points: if/else 23 (74 pts), loops 2 (8 pts), match/switch 1 (2 pts) (nesting depth added 58). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tauri_cli::dev::setup (cognitive 54) crates/tauri-cli/src/dev.rs:136— tauri_cli::dev::setup has cognitive complexity 54 (threshold 15). Drivers by points: if/else 17 (40 pts), loops 2 (7 pts), match/switch 2 (5 pts), boolean chains 2 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tauri_cli::acl::permission::rm::rm_permission_from_capabilities (cognitive 51) crates/tauri-cli/src/acl/permission/rm.rs:115— tauri_cli::acl::permission::rm::rm_permission_from_capabilities has cognitive complexity 51 (threshold 15). Drivers by points: if/else 9 (38 pts), match/switch 3 (12 pts), loops 1 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::mobile::android::device_prompt (cognitive 43) crates/tauri-cli/src/mobile/android/mod.rs:916— tauri_cli::mobile::android::device_prompt has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (30 pts), match/switch 4 (10 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::mobile::android::find_matching_brace (cognitive 41) crates/tauri-cli/src/mobile/android/mod.rs:429— tauri_cli::mobile::android::find_matching_brace has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (36 pts), boolean chains 4, loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::interface::rust::tauri_config_to_bundle_settings (cognitive 39) crates/tauri-cli/src/interface/rust.rs:1344— tauri_cli::interface::rust::tauri_config_to_bundle_settings has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (26 pts), match/switch 7 (10 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::plugin::init::command (cognitive 38) crates/tauri-cli/src/plugin/init.rs:82— tauri_cli::plugin::init::command has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (29 pts), boolean chains 5, match/switch 2 (4 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::mobile::android::android_studio_script::adb_forward_port (cognitive 36) crates/tauri-cli/src/mobile/android/android_studio_script.rs:189— tauri_cli::mobile::android::android_studio_script::adb_forward_port has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (29 pts), loops 3 (7 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::acl::permission::ls::command (cognitive 35) crates/tauri-cli/src/acl/permission/ls.rs:26— tauri_cli::acl::permission::ls::command has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 3 (8 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::add::run (cognitive 35) crates/tauri-cli/src/add.rs:47— tauri_cli::add::run has cognitive complexity 35 (threshold 15). Drivers by points: if/else 24 (34 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::acl::permission::add::command (cognitive 34) crates/tauri-cli/src/acl/permission/add.rs:159— tauri_cli::acl::permission::add::command has cognitive complexity 34 (threshold 15). Drivers by points: if/else 19 (28 pts), loops 2 (4 pts), match/switch 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::interface::rust::manifest::find_dependency (cognitive 34) crates/tauri-cli/src/interface/rust/manifest.rs:115— tauri_cli::interface::rust::manifest::find_dependency has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (28 pts), loops 2 (5 pts), match/switch 1 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tauri_cli::migrate::migrations::v1::manifest::find_dependency (cognitive 33) crates/tauri-cli/src/migrate/migrations/v1/manifest.rs:127— tauri_cli::migrate::migrations::v1::manifest::find_dependency has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (28 pts), loops 2 (5 pts) (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tauri_cli::mobile::ios::synchronize_project_config (cognitive 33) crates/tauri-cli/src/mobile/ios/mod.rs:551— tauri_cli::mobile::ios::synchronize_project_config has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (28 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::migrate::migrations::v1::config::migrate_config (cognitive 31) crates/tauri-cli/src/migrate/migrations/v1/config.rs:80— tauri_cli::migrate::migrations::v1::config::migrate_config has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 1 (4 pts) (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tauri_cli::mobile::android::ensure_sdk (cognitive 30) crates/tauri-cli/src/mobile/android/mod.rs:604— tauri_cli::mobile::android::ensure_sdk has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (30 pts) (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tauri_cli::mobile::ios::xcode_script::command (cognitive 30) crates/tauri-cli/src/mobile/ios/xcode_script.rs:55— tauri_cli::mobile::ios::xcode_script::command has cognitive complexity 30 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 7). Of this number, 28 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::mobile::init::exec (cognitive 27) crates/tauri-cli/src/mobile/init.rs:48— tauri_cli::mobile::init::exec has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 2, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::interface::rust::manifest::inject_features_table (cognitive 26) crates/tauri-cli/src/interface/rust/manifest.rs:199— tauri_cli::interface::rust::manifest::inject_features_table has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 3 (6 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::migrate::migrations::v1::manifest::migrate_manifest (cognitive 26) crates/tauri-cli/src/migrate/migrations/v1/manifest.rs:29— tauri_cli::migrate::migrations::v1::manifest::migrate_manifest has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (11 pts), match/switch 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::mobile::ios::get_config (cognitive 26) crates/tauri-cli/src/mobile/ios/mod.rs:122— tauri_cli::mobile::ios::get_config has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (24 pts), loops 1, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_cli::icon::android (cognitive 25) crates/tauri-cli/src/icon.rs:497— tauri_cli::icon::android has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 5 (9 pts), match/switch 2 (3 pts) (nesting depth added 8). Of this number, 24 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
+ 16 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×35
No test reaches this file packages/api/src/window.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/webview.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/path.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/core.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/tray.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/dpi.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/app.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/menu/menu.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/webviewWindow.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/event.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/menu/submenu.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/image.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/menu/iconMenuItem.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/menu/predefinedMenuItem.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/menu/base.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/tauri/src/window/scripts/drag.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/menu/menuItem.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/tauri/scripts/core.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/tauri/scripts/ipc-protocol.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/menu/checkMenuItem.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/api/src/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file crates/tauri/src/webview/scripts/zoom-hotkey.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
FunctionTooLong: tauri_runtime_wry::handle_user_message crates/tauri-runtime-wry/src/lib.rs:3172— FunctionTooLong — tauri_runtime_wry::handle_user_message runs 658 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 558 over it, 6.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_runtime_wry::create_webview crates/tauri-runtime-wry/src/lib.rs:4669— FunctionTooLong — tauri_runtime_wry::create_webview runs 409 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 309 over it, 4.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_bundler::bundle::windows::nsis::build_nsis_app_installer crates/tauri-bundler/src/bundle/windows/nsis/mod.rs:186— FunctionTooLong — tauri_bundler::bundle::windows::nsis::build_nsis_app_installer runs 406 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 306 over it, 4.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::interface::rust::tauri_config_to_bundle_settings crates/tauri-cli/src/interface/rust.rs:1344— FunctionTooLong — tauri_cli::interface::rust::tauri_config_to_bundle_settings runs 258 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 158 over it, 2.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_codegen::context::context_codegen crates/tauri-codegen/src/context.rs:134— FunctionTooLong — tauri_codegen::context::context_codegen runs 248 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::icon::android crates/tauri-cli/src/icon.rs:497— FunctionTooLong — tauri_cli::icon::android runs 195 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 95 over it, 1.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::mobile::ios::xcode_script::command crates/tauri-cli/src/mobile/ios/xcode_script.rs:55— FunctionTooLong — tauri_cli::mobile::ios::xcode_script::command runs 181 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_runtime_wry::create_window crates/tauri-runtime-wry/src/lib.rs:4407— FunctionTooLong — tauri_runtime_wry::create_window runs 181 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_build::try_build crates/tauri-build/src/lib.rs:652— FunctionTooLong — tauri_build::try_build runs 179 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri::ipc::protocol::handle_ipc_message crates/tauri/src/ipc/protocol.rs:185— FunctionTooLong — tauri::ipc::protocol::handle_ipc_message runs 176 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_runtime_wry::handle_event_loop crates/tauri-runtime-wry/src/lib.rs:4101— FunctionTooLong — tauri_runtime_wry::handle_event_loop runs 165 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 65 over it, 1.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::mobile::ios::project::generate crates/tauri-cli/src/mobile/ios/project.rs:34— FunctionTooLong — tauri_cli::mobile::ios::project::generate runs 155 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::migrate::migrations::v1::config::allowlist_to_permissions crates/tauri-cli/src/migrate/migrations/v1/config.rs:470— FunctionTooLong — tauri_cli::migrate::migrations::v1::config::allowlist_to_permissions runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_bundler::bundle::linux::rpm::bundle_project crates/tauri-bundler/src/bundle/linux/rpm.rs:19— FunctionTooLong — tauri_bundler::bundle::linux::rpm::bundle_project runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::dev::setup crates/tauri-cli/src/dev.rs:136— FunctionTooLong — tauri_cli::dev::setup runs 141 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_bundler::bundle::bundle_project crates/tauri-bundler/src/bundle.rs:112— FunctionTooLong — tauri_bundler::bundle::bundle_project runs 137 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_bundler::bundle::linux::appimage::linuxdeploy::bundle_project crates/tauri-bundler/src/bundle/linux/appimage/linuxdeploy.rs:21— FunctionTooLong — tauri_bundler::bundle::linux::appimage::linuxdeploy::bundle_project runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::plugin::init::command crates/tauri-cli/src/plugin/init.rs:82— FunctionTooLong — tauri_cli::plugin::init::command runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::acl::permission::add::command crates/tauri-cli/src/acl/permission/add.rs:159— FunctionTooLong — tauri_cli::acl::permission::add::command runs 132 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::migrate::migrations::v1::frontend::migrate_imports crates/tauri-cli/src/migrate/migrations/v1/frontend.rs:137— FunctionTooLong — tauri_cli::migrate::migrations::v1::frontend::migrate_imports runs 129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri::protocol::asset::get_response crates/tauri/src/protocol/asset.rs:33— FunctionTooLong — tauri::protocol::asset::get_response runs 123 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::add::run crates/tauri-cli/src/add.rs:47— FunctionTooLong — tauri_cli::add::run runs 122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::mobile::ios::get_config crates/tauri-cli/src/mobile/ios/mod.rs:122— FunctionTooLong — tauri_cli::mobile::ios::get_config runs 121 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_macros::command::wrapper::wrapper crates/tauri-macros/src/command/wrapper.rs:152— FunctionTooLong — tauri_macros::command::wrapper::wrapper runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tauri_cli::mobile::init::exec crates/tauri-cli/src/mobile/init.rs:48— FunctionTooLong — tauri_cli::mobile::init::exec runs 112 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: src/lib.rs crates/tauri-runtime-wry/src/lib.rs— FileTooLong — 3683 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 3183 over it, 7.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/config.rs crates/tauri-utils/src/config.rs— FileTooLong — 2447 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1947 over it, 4.89× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: config_v1/mod.rs crates/tauri-utils/src/config_v1/mod.rs— FileTooLong — 1691 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1191 over it, 3.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: window/mod.rs crates/tauri/src/window/mod.rs— FileTooLong — 1382 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 882 over it, 2.76× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: webview/mod.rs crates/tauri/src/webview/mod.rs— FileTooLong — 1329 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 829 over it, 2.66× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/app.rs crates/tauri/src/app.rs— FileTooLong — 1254 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 754 over it, 2.51× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: interface/rust.rs crates/tauri-cli/src/interface/rust.rs— FileTooLong — 1217 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 717 over it, 2.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: webview/webview_window.rs crates/tauri/src/webview/webview_window.rs— FileTooLong — 934 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 434 over it, 1.87× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: android/mod.rs crates/tauri-cli/src/mobile/android/mod.rs— FileTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 341 over it, 1.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: msi/mod.rs crates/tauri-bundler/src/bundle/windows/msi/mod.rs— FileTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 223 over it, 1.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/icon.rs crates/tauri-cli/src/icon.rs— FileTooLong — 720 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 220 over it, 1.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/window.ts packages/api/src/window.ts— FileTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded), about 62% of them inside a single declaration: Window (377-2570). The bar is 500 significant lines; this is 213 over it, 1.43× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: nsis/mod.rs crates/tauri-bundler/src/bundle/windows/nsis/mod.rs— FileTooLong — 709 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 209 over it, 1.42× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: menu/plugin.rs crates/tauri/src/menu/plugin.rs— FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 206 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: bundle/settings.rs crates/tauri-bundler/src/bundle/settings.rs— FileTooLong — 642 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 142 over it, 1.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: mobile/mod.rs crates/tauri-cli/src/mobile/mod.rs— FileTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 64 over it, 1.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ios/mod.rs crates/tauri-cli/src/mobile/ios/mod.rs— FileTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 30 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: manager/webview.rs crates/tauri/src/manager/webview.rs— FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: WebviewManager (3 blocks, 70-706). The bar is 500 significant lines; this is 18 over it, 1.04× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs crates/tauri/src/lib.rs— FileTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 3 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
tauri_cli::migrate::migrations::v1::config::allowlist_to_permissions (cyclomatic 149) crates/tauri-cli/src/migrate/migrations/v1/config.rs:470— tauri_cli::migrate::migrations::v1::config::allowlist_to_permissions has cyclomatic complexity 149 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
tauri_cli::migrate::migrations::v1::frontend::migrate_imports (cyclomatic 30) crates/tauri-cli/src/migrate/migrations/v1/frontend.rs:137— tauri_cli::migrate::migrations::v1::frontend::migrate_imports has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::helpers::pbxproj::parse (cyclomatic 29) crates/tauri-cli/src/helpers/pbxproj.rs:13— tauri_cli::helpers::pbxproj::parse has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::try_run (cyclomatic 25) crates/tauri-cli/src/lib.rs:205— tauri_cli::try_run has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
tauri_cli::dev::setup (cyclomatic 25) crates/tauri-cli/src/dev.rs:136— tauri_cli::dev::setup has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::migrate::migrations::v1::config::process_bundle (cyclomatic 25) crates/tauri-cli/src/migrate/migrations/v1/config.rs:261— tauri_cli::migrate::migrations::v1::config::process_bundle has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::plugin::init::command (cyclomatic 25) crates/tauri-cli/src/plugin/init.rs:82— tauri_cli::plugin::init::command has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::interface::rust::tauri_config_to_bundle_settings (cyclomatic 23) crates/tauri-cli/src/interface/rust.rs:1344— tauri_cli::interface::rust::tauri_config_to_bundle_settings has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::mobile::android::find_matching_brace (cyclomatic 23) crates/tauri-cli/src/mobile/android/mod.rs:429— tauri_cli::mobile::android::find_matching_brace has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::add::run (cyclomatic 22) crates/tauri-cli/src/add.rs:47— tauri_cli::add::run has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::mobile::ios::xcode_script::command (cyclomatic 21) crates/tauri-cli/src/mobile/ios/xcode_script.rs:55— tauri_cli::mobile::ios::xcode_script::command has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::acl::permission::add::command (cyclomatic 19) crates/tauri-cli/src/acl/permission/add.rs:159— tauri_cli::acl::permission::add::command has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::mobile::android::device_prompt (cyclomatic 18) crates/tauri-cli/src/mobile/android/mod.rs:916— tauri_cli::mobile::android::device_prompt has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::acl::permission::rm::rm_permission_from_capabilities (cyclomatic 17) crates/tauri-cli/src/acl/permission/rm.rs:115— tauri_cli::acl::permission::rm::rm_permission_from_capabilities has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::mobile::android::android_studio_script::adb_forward_port (cyclomatic 17) crates/tauri-cli/src/mobile/android/android_studio_script.rs:189— tauri_cli::mobile::android::android_studio_script::adb_forward_port has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_cli::mobile::init::exec (cyclomatic 17) crates/tauri-cli/src/mobile/init.rs:48— tauri_cli::mobile::init::exec has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Hotspot: crates/tauri-runtime-wry/src/lib.rs crates/tauri-runtime-wry/src/lib.rs:3172— crates/tauri-runtime-wry/src/lib.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 192 in tauri_runtime_wry::handle_user_message at line 3172. 5 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-runtime-wry/src/lib.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-build/src/lib.rs crates/tauri-build/src/lib.rs:652— crates/tauri-build/src/lib.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in tauri_build::try_build at line 652. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-build/src/lib.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-bundler/src/bundle/windows/nsis/mod.rs crates/tauri-bundler/src/bundle/windows/nsis/mod.rs:186— crates/tauri-bundler/src/bundle/windows/nsis/mod.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in tauri_bundler::bundle::windows::nsis::build_nsis_app_installer at line 186. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-bundler/src/bundle/windows/nsis/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-bundler/src/bundle/linux/rpm.rs crates/tauri-bundler/src/bundle/linux/rpm.rs:19— crates/tauri-bundler/src/bundle/linux/rpm.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in tauri_bundler::bundle::linux::rpm::bundle_project at line 19. 3 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-bundler/src/bundle/linux/rpm.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri/src/manager/webview.rs crates/tauri/src/manager/webview.rs:124— crates/tauri/src/manager/webview.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in WebviewManager::prepare_pending_webview at line 124. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri/src/manager/webview.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-cli/src/add.rs crates/tauri-cli/src/add.rs:47— crates/tauri-cli/src/add.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in tauri_cli::add::run at line 47. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-cli/src/add.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-codegen/src/context.rs crates/tauri-codegen/src/context.rs:134— crates/tauri-codegen/src/context.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in tauri_codegen::context::context_codegen at line 134. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-codegen/src/context.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-bundler/src/bundle.rs crates/tauri-bundler/src/bundle.rs:112— crates/tauri-bundler/src/bundle.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in tauri_bundler::bundle::bundle_project at line 112. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-bundler/src/bundle.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri/src/protocol/asset.rs crates/tauri/src/protocol/asset.rs:33— crates/tauri/src/protocol/asset.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in tauri::protocol::asset::get_response at line 33. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri/src/protocol/asset.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri/src/ipc/authority.rs crates/tauri/src/ipc/authority.rs:222— crates/tauri/src/ipc/authority.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in RuntimeAuthority::resolve_access_message at line 222. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri/src/ipc/authority.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-cli/src/mobile/ios/xcode_script.rs crates/tauri-cli/src/mobile/ios/xcode_script.rs:55— crates/tauri-cli/src/mobile/ios/xcode_script.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in tauri_cli::mobile::ios::xcode_script::command at line 55. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-cli/src/mobile/ios/xcode_script.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-cli/src/mobile/ios/mod.rs crates/tauri-cli/src/mobile/ios/mod.rs:551— crates/tauri-cli/src/mobile/ios/mod.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in tauri_cli::mobile::ios::synchronize_project_config at line 551. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-cli/src/mobile/ios/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-cli/src/mobile/init.rs crates/tauri-cli/src/mobile/init.rs:48— crates/tauri-cli/src/mobile/init.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in tauri_cli::mobile::init::exec at line 48. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-cli/src/mobile/init.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-bundler/src/bundle/macos/app.rs crates/tauri-bundler/src/bundle/macos/app.rs:212— crates/tauri-bundler/src/bundle/macos/app.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in tauri_bundler::bundle::macos::app::create_info_plist at line 212. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-bundler/src/bundle/macos/app.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-cli/src/mobile/android/android_studio_script.rs crates/tauri-cli/src/mobile/android/android_studio_script.rs:189— crates/tauri-cli/src/mobile/android/android_studio_script.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in tauri_cli::mobile::android::android_studio_script::adb_forward_port at line 189. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-cli/src/mobile/android/android_studio_script.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/tauri-cli/src/dev.rs crates/tauri-cli/src/dev.rs:136— crates/tauri-cli/src/dev.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in tauri_cli::dev::setup at line 136. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-cli/src/dev.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
TooManyMethods: WebviewWindow crates/tauri/src/webview/webview_window.rs:1560— TooManyMethods — 111 methods. The bar is 30 methods; this is 81 over it, 3.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Window crates/tauri/src/window/mod.rs:996— TooManyMethods — 99 methods. The bar is 30 methods; this is 69 over it, 3.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Window packages/api/src/window.ts:377— TooManyMethods — 89 methods. The bar is 30 methods; this is 59 over it, 2.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WebviewWindowBuilder crates/tauri/src/webview/webview_window.rs:48— TooManyMethods — 88 methods. The bar is 30 methods; this is 58 over it, 2.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WindowBuilder crates/tauri/src/window/mod.rs:120— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SubmenuBuilder crates/tauri/src/menu/builders/menu.rs:114— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Settings crates/tauri-bundler/src/bundle/settings.rs:815— TooManyMethods — 47 methods, declared across 2 files: bundle/settings.rs (46), windows/sign.rs (1). The bar is 30 methods; this is 17 over it, 1.57× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Webview crates/tauri/src/webview/mod.rs:1428— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MenuBuilder crates/tauri/src/menu/builders/menu.rs:40— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Plugin crates/tauri/mobile/android/src/main/java/app/tauri/plugin/Plugin.kt:45— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WebviewBuilder crates/tauri/src/webview/mod.rs:275— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AppHandle crates/tauri/src/app.rs:387— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: App crates/tauri/src/app.rs:747— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (7 lines × 2) crates/tauri-cli/src/mobile/android/mod.rs:1113— crates/tauri-cli/src/mobile/android/mod.rs:1113-1119 | crates/tauri-cli/src/mobile/ios/mod.rs:472-478 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/tauri-runtime-wry/src/lib.rs:3742— crates/tauri-runtime-wry/src/lib.rs:3742-3748 | crates/tauri-runtime-wry/src/lib.rs:3763-3769 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/tauri-utils/src/config.rs:4232— crates/tauri-utils/src/config.rs:4232-4238 | crates/tauri-utils/src/config.rs:4418-4424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/tauri-utils/src/config.rs:4685— crates/tauri-utils/src/config.rs:4685-4691 | crates/tauri-utils/src/config.rs:4761-4767 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/tauri/src/manager/mod.rs:530— crates/tauri/src/manager/mod.rs:530-536 | crates/tauri/src/manager/mod.rs:559-565 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/tauri/src/window/mod.rs:1458— crates/tauri/src/window/mod.rs:1458-1464 | crates/tauri/src/window/mod.rs:1490-1496 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/tauri-utils/src/config.rs:268— crates/tauri-utils/src/config.rs:268-274 | crates/tauri-utils/src/config_v1/mod.rs:259-265 — before extracting anything, compare `crates/tauri-utils/src/config.rs` and `crates/tauri-utils/src/config_v1/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) crates/tauri-utils/src/config_v1/mod.rs:3044— crates/tauri-utils/src/config_v1/mod.rs:3044-3050 | crates/tauri-utils/src/lib.rs:248-254 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/tauri-utils/src/config.rs:601— crates/tauri-utils/src/config.rs:601-607 | crates/tauri-utils/src/config_v1/mod.rs:333-339 — before extracting anything, compare `crates/tauri-utils/src/config.rs` and `crates/tauri-utils/src/config_v1/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) crates/tauri-bundler/src/bundle/windows/msi/mod.rs:762— crates/tauri-bundler/src/bundle/windows/msi/mod.rs:762-768 | crates/tauri-bundler/src/bundle/windows/msi/mod.rs:770-776 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/tauri/mobile/ios-api/Sources/Tauri/Channel.swift:44— crates/tauri/mobile/ios-api/Sources/Tauri/Channel.swift:44-50 | crates/tauri/mobile/ios-api/Sources/Tauri/Invoke.swift:47-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
tauri_bundler::bundle::windows::nsis::build_nsis_app_installer (cognitive 68) crates/tauri-bundler/src/bundle/windows/nsis/mod.rs:186— tauri_bundler::bundle::windows::nsis::build_nsis_app_installer has cognitive complexity 68 (threshold 15). Drivers by points: if/else 40 (54 pts), match/switch 7 (8 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_bundler::bundle::windows::msi::build_wix_app_installer (cognitive 57) crates/tauri-bundler/src/bundle/windows/msi/mod.rs:459— tauri_bundler::bundle::windows::msi::build_wix_app_installer has cognitive complexity 57 (threshold 15). Drivers by points: if/else 32 (42 pts), loops 7 (11 pts), match/switch 3 (4 pts) (nesting depth added 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::bundle_project (cognitive 48) crates/tauri-bundler/src/bundle.rs:112— tauri_bundler::bundle::bundle_project has cognitive complexity 48 (threshold 15). Drivers by points: if/else 20 (32 pts), loops 4 (7 pts), match/switch 2 (6 pts), boolean chains 3 (nesting depth added 19). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::linux::rpm::bundle_project (cognitive 36) crates/tauri-bundler/src/bundle/linux/rpm.rs:19— tauri_bundler::bundle::linux::rpm::bundle_project has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (19 pts), loops 11 (14 pts), match/switch 3 (nesting depth added 8). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::sign_binaries_if_needed (cognitive 25) crates/tauri-bundler/src/bundle.rs:345— tauri_bundler::bundle::sign_binaries_if_needed has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (6 pts) (nesting depth added 16). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::updater_bundle::bundle_update_windows (cognitive 24) crates/tauri-bundler/src/bundle/updater_bundle.rs:121— tauri_bundler::bundle::updater_bundle::bundle_update_windows has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 2, loops 2, match/switch 1 (2 pts) (nesting depth added 11). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::platform::target_triple (cognitive 21) crates/tauri-bundler/src/bundle/platform.rs:40— tauri_bundler::bundle::platform::target_triple has cognitive complexity 21 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 1, match/switch 1 (nesting depth added 2). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::windows::msi::generate_resource_data (cognitive 20) crates/tauri-bundler/src/bundle/windows/msi/mod.rs:995— tauri_bundler::bundle::windows::msi::generate_resource_data has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 9). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::linux::appimage::linuxdeploy::bundle_project (cognitive 18) crates/tauri-bundler/src/bundle/linux/appimage/linuxdeploy.rs:21— tauri_bundler::bundle::linux::appimage::linuxdeploy::bundle_project has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 2 (3 pts), match/switch 3 (nesting depth added 4). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::windows::nsis::generate_resource_data (cognitive 18) crates/tauri-bundler/src/bundle/windows/nsis/mod.rs:806— tauri_bundler::bundle::windows::nsis::generate_resource_data has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (10 lines × 2) crates/tauri-bundler/src/bundle/windows/msi/mod.rs:418— crates/tauri-bundler/src/bundle/windows/msi/mod.rs:418-427 | crates/tauri-bundler/src/bundle/windows/msi/mod.rs:443-452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/tauri-cli/src/info/env_system.rs:105— crates/tauri-cli/src/info/env_system.rs:105-114 | crates/tauri-cli/src/info/env_system.rs:119-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/tauri-cli/src/mobile/android/mod.rs:938— crates/tauri-cli/src/mobile/android/mod.rs:938-947 | crates/tauri-cli/src/mobile/android/mod.rs:1005-1014 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/tauri-cli/src/plugin/android.rs:48— crates/tauri-cli/src/plugin/android.rs:48-57 | crates/tauri-cli/src/plugin/ios.rs:54-63 — before extracting anything, compare `crates/tauri-cli/src/plugin/android.rs` and `crates/tauri-cli/src/plugin/ios.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) crates/tauri-cli/src/acl/capability/new.rs:131— crates/tauri-cli/src/acl/capability/new.rs:131-140 | crates/tauri-cli/src/acl/permission/new.rs:97-111 — `crates/tauri-cli/src/acl/capability/new.rs` and `crates/tauri-cli/src/acl/permission/new.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 33 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 2) crates/tauri-cli/src/mobile/android/project.rs:51— crates/tauri-cli/src/mobile/android/project.rs:51-60 | crates/tauri-cli/src/mobile/ios/project.rs:53-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) crates/tauri-cli/src/helpers/npm.rs:367— crates/tauri-cli/src/helpers/npm.rs:367-376 | crates/tauri-cli/src/helpers/npm.rs:420-429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/tauri-cli/src/mobile/android/run.rs:163— crates/tauri-cli/src/mobile/android/run.rs:163-172 | crates/tauri-cli/src/mobile/ios/run.rs:123-132 — `crates/tauri-cli/src/mobile/android/run.rs` and `crates/tauri-cli/src/mobile/ios/run.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 34 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 2) crates/tauri-cli/src/info/packages_nodejs.rs:76— crates/tauri-cli/src/info/packages_nodejs.rs:76-85 | crates/tauri-cli/src/info/packages_nodejs.rs:95-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/tauri-cli/templates/plugin/ios-spm/Sources/ExamplePlugin.swift:11— crates/tauri-cli/templates/plugin/ios-spm/Sources/ExamplePlugin.swift:11-20 | crates/tauri-cli/templates/plugin/ios-xcode/tauri-plugin-{{ plugin_name }}/ExamplePlugin.swift:11-20 — before extracting anything, compare `crates/tauri-cli/templates/plugin/ios-spm/Sources/ExamplePlugin.swift` and `crates/tauri-cli/templates/plugin/ios-xcode/tauri-plugin-{{ plugin_name }}/ExamplePlugin.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/tauri-cli/templates/plugin/ios-spm/Sources/ExamplePlugin.swift:11` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) crates/tauri-cli/src/mobile/android/project.rs:42— crates/tauri-cli/src/mobile/android/project.rs:42-50 | crates/tauri-cli/src/mobile/ios/project.rs:44-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) crates/tauri-cli/src/plugin/android.rs:70— crates/tauri-cli/src/plugin/android.rs:70-78 | crates/tauri-cli/src/plugin/ios.rs:78-86 — before extracting anything, compare `crates/tauri-cli/src/plugin/android.rs` and `crates/tauri-cli/src/plugin/ios.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) crates/tauri/src/plugin/mobile.rs:321— crates/tauri/src/plugin/mobile.rs:321-329 | crates/tauri/src/plugin/mobile.rs:350-358 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/tauri-cli/src/mobile/android/dev.rs:133— crates/tauri-cli/src/mobile/android/dev.rs:133-141 | crates/tauri-cli/src/mobile/ios/dev.rs:140-148 — `crates/tauri-cli/src/mobile/android/dev.rs` and `crates/tauri-cli/src/mobile/ios/dev.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 38 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) crates/tauri/src/app.rs:2342— crates/tauri/src/app.rs:2342-2350 | crates/tauri/src/plugin.rs:717-725 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) crates/tauri/src/webview/plugin.rs:54— crates/tauri/src/webview/plugin.rs:54-62 | crates/tauri/src/window/plugin.rs:13-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) crates/tauri-bundler/src/bundle/windows/msi/mod.rs:491— crates/tauri-bundler/src/bundle/windows/msi/mod.rs:491-499 | crates/tauri-bundler/src/bundle/windows/nsis/mod.rs:205-213 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) crates/tauri-cli/src/helpers/cargo.rs:48— crates/tauri-cli/src/helpers/cargo.rs:48-56 | crates/tauri-cli/src/helpers/cargo.rs:81-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
tauri::protocol::asset::get_response (cognitive 38) crates/tauri/src/protocol/asset.rs:33— tauri::protocol::asset::get_response has cognitive complexity 38 (threshold 15). Drivers by points: if/else 20 (31 pts), loops 1 (3 pts), boolean chains 2, match/switch 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri::manager::window::on_window_event (cognitive 32) crates/tauri/src/manager/window.rs:173— tauri::manager::window::on_window_event has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
tauri::app::on_event_loop_event (cognitive 31) crates/tauri/src/app.rs:2704— tauri::app::on_event_loop_event has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 4 (12 pts), match/switch 2 (3 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri::ipc::protocol::handle_ipc_message (cognitive 29) crates/tauri/src/ipc/protocol.rs:185— tauri::ipc::protocol::handle_ipc_message has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 4 (7 pts), boolean chains 5, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri::process::restart_macos_app (cognitive 27) crates/tauri/src/process.rs:92— tauri::process::restart_macos_app has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (23 pts), match/switch 1 (4 pts) (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tauri::ipc::protocol::get (cognitive 23) crates/tauri/src/ipc/protocol.rs:38— tauri::ipc::protocol::get has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 6 (20 pts), if/else 2 (3 pts) (nesting depth added 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
tauri::scope::fs::canonicalize_parent (cognitive 16) crates/tauri/src/scope/fs.rs:162— tauri::scope::fs::canonicalize_parent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (5 lines × 2) crates/tauri-cli/src/mobile/android/mod.rs:116— crates/tauri-cli/src/mobile/android/mod.rs:116-120 | crates/tauri-cli/src/mobile/ios/mod.rs:110-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/tauri-utils/src/config.rs:3196— crates/tauri-utils/src/config.rs:3196-3200 | crates/tauri/src/path/mod.rs:447-451 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/tauri-utils/src/config.rs:4407— crates/tauri-utils/src/config.rs:4407-4411 | crates/tauri-utils/src/config.rs:4417-4421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/tauri/src/app.rs:435— crates/tauri/src/app.rs:435-439 | crates/tauri/src/app.rs:458-462 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/tauri-cli/src/migrate/migrations/v1/config.rs:303— crates/tauri-cli/src/migrate/migrations/v1/config.rs:303-310 | crates/tauri-cli/src/migrate/migrations/v1/config.rs:315-319 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/tauri-bundler/src/bundle/linux/debian.rs:118— crates/tauri-bundler/src/bundle/linux/debian.rs:118-123 | crates/tauri-bundler/src/bundle/macos/app.rs:171-175 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/tauri-cli/src/acl/capability/new.rs:48— crates/tauri-cli/src/acl/capability/new.rs:48-52 | crates/tauri-cli/src/acl/permission/new.rs:47-51 — `crates/tauri-cli/src/acl/capability/new.rs` and `crates/tauri-cli/src/acl/permission/new.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 33 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
tauri_bundler::bundle::windows::nsis::build_nsis_app_installer (cyclomatic 57) crates/tauri-bundler/src/bundle/windows/nsis/mod.rs:186— tauri_bundler::bundle::windows::nsis::build_nsis_app_installer has cyclomatic complexity 57 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_bundler::bundle::windows::msi::build_wix_app_installer (cyclomatic 38) crates/tauri-bundler/src/bundle/windows/msi/mod.rs:459— tauri_bundler::bundle::windows::msi::build_wix_app_installer has cyclomatic complexity 38 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::linux::rpm::bundle_project (cyclomatic 35) crates/tauri-bundler/src/bundle/linux/rpm.rs:19— tauri_bundler::bundle::linux::rpm::bundle_project has cyclomatic complexity 35 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::bundle_project (cyclomatic 34) crates/tauri-bundler/src/bundle.rs:112— tauri_bundler::bundle::bundle_project has cyclomatic complexity 34 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::linux::appimage::linuxdeploy::bundle_project (cyclomatic 21) crates/tauri-bundler/src/bundle/linux/appimage/linuxdeploy.rs:21— tauri_bundler::bundle::linux::appimage::linuxdeploy::bundle_project has cyclomatic complexity 21 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri_bundler::bundle::platform::target_triple (cyclomatic 16) crates/tauri-bundler/src/bundle/platform.rs:40— tauri_bundler::bundle::platform::target_triple has cyclomatic complexity 16 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
tauri::path::resolve_path (cyclomatic 30) crates/tauri/src/path/mod.rs:316— tauri::path::resolve_path has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
tauri::vibrancy::macos::apply_effects (cyclomatic 30) crates/tauri/src/vibrancy/macos.rs:14— tauri::vibrancy::macos::apply_effects has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
tauri::app::on_event_loop_event (cyclomatic 22) crates/tauri/src/app.rs:2704— tauri::app::on_event_loop_event has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
tauri::manager::window::on_window_event (cyclomatic 22) crates/tauri/src/manager/window.rs:173— tauri::manager::window::on_window_event has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri::ipc::protocol::handle_ipc_message (cyclomatic 20) crates/tauri/src/ipc/protocol.rs:185— tauri::ipc::protocol::handle_ipc_message has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri::protocol::asset::get_response (cyclomatic 19) crates/tauri/src/protocol/asset.rs:33— tauri::protocol::asset::get_response has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_runtime_wry::handle_user_message (cognitive 213) crates/tauri-runtime-wry/src/lib.rs:3172— tauri_runtime_wry::handle_user_message has cognitive complexity 213 (threshold 15). Drivers by points: if/else 52 (169 pts), match/switch 13 (41 pts), loops 1 (3 pts) (nesting depth added 147). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
tauri_runtime_wry::handle_event_loop (cognitive 120) crates/tauri-runtime-wry/src/lib.rs:4101— tauri_runtime_wry::handle_event_loop has cognitive complexity 120 (threshold 15). Drivers by points: if/else 22 (85 pts), loops 5 (23 pts), match/switch 4 (12 pts) (nesting depth added 89). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tauri_runtime_wry::create_webview (cognitive 79) crates/tauri-runtime-wry/src/lib.rs:4669— tauri_runtime_wry::create_webview has cognitive complexity 79 (threshold 15). Drivers by points: if/else 44 (60 pts), match/switch 7 (16 pts), loops 2, boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_runtime_wry::create_window (cognitive 54) crates/tauri-runtime-wry/src/lib.rs:4407— tauri_runtime_wry::create_window has cognitive complexity 54 (threshold 15). Drivers by points: if/else 24 (51 pts), boolean chains 3 (nesting depth added 27). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
tauri_runtime_wry::undecorated_resizing::windows::drag_resize_window_proc (cognitive 21) crates/tauri-runtime-wry/src/undecorated_resizing.rs:265— tauri_runtime_wry::undecorated_resizing::windows::drag_resize_window_proc has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
tauri_runtime_wry::util::imp::hwnd_dpi (cognitive 16) crates/tauri-runtime-wry/src/util.rs:69— tauri_runtime_wry::util::imp::hwnd_dpi has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassTooLong: Window crates/tauri/src/window/mod.rs:996— ClassTooLong — 803 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 99 methods, 17 blocks, lines 996-2548. The bar is 400 significant lines; this is 403 over it, 2.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebviewBuilder crates/tauri/src/webview/mod.rs:275— ClassTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 41 methods, 3 blocks, lines 275-1424. The bar is 400 significant lines; this is 187 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Webview crates/tauri/src/webview/mod.rs:1428— ClassTooLong — 585 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 47 methods, 12 blocks, lines 1428-2609. The bar is 400 significant lines; this is 185 over it, 1.46× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebviewWindowBuilder crates/tauri/src/webview/webview_window.rs:48— ClassTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 88 methods, 7 blocks, lines 48-1555. The bar is 400 significant lines; this is 112 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Window packages/api/src/window.ts:377— ClassTooLong — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 89 methods. The bar is 400 significant lines; this is 40 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebviewManager crates/tauri/src/manager/webview.rs:70— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 3 blocks, lines 70-706. The bar is 400 significant lines; this is 30 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
MethodTooLong: WebviewManager.prepare_pending_webview crates/tauri/src/manager/webview.rs:124— MethodTooLong — prepare_pending_webview runs 187 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RuntimeAuthority.resolve_access_message crates/tauri/src/ipc/authority.rs:222— MethodTooLong — resolve_access_message runs 150 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Builder.build crates/tauri/src/app.rs:2408— MethodTooLong — build runs 136 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WindowConfig.to_tokens crates/tauri-utils/src/config.rs:4358— MethodTooLong — to_tokens runs 130 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebviewManager.prepare_webview crates/tauri/src/manager/webview.rs:455— MethodTooLong — prepare_webview runs 119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Webview.on_message crates/tauri/src/webview/mod.rs:2005— MethodTooLong — on_message runs 107 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (12 lines × 2) crates/tauri-bundler/src/bundle/platform.rs:82— crates/tauri-bundler/src/bundle/platform.rs:82-93 | crates/tauri-utils/src/platform.rs:218-229 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) crates/tauri-cli/src/mobile/android/dev.rs:313— crates/tauri-cli/src/mobile/android/dev.rs:313-324 | crates/tauri-cli/src/mobile/ios/dev.rs:333-344 — `crates/tauri-cli/src/mobile/android/dev.rs` and `crates/tauri-cli/src/mobile/ios/dev.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 38 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12 lines × 2) crates/tauri-cli/src/mobile/ios/dev.rs:164— crates/tauri-cli/src/mobile/ios/dev.rs:164-175 | crates/tauri-cli/src/mobile/ios/run.rs:64-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) crates/tauri-runtime-wry/src/lib.rs:4007— crates/tauri-runtime-wry/src/lib.rs:4007-4018 | crates/tauri-runtime-wry/src/lib.rs:4622-4633 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) crates/tauri/src/ipc/authority.rs:773— crates/tauri/src/ipc/authority.rs:773-784 | crates/tauri/src/ipc/authority.rs:814-825 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) crates/tauri-cli/src/helpers/plugins.rs:87— crates/tauri-cli/src/helpers/plugins.rs:87-98 | crates/tauri-cli/src/migrate/migrations/v1/manifest.rs:197-208 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/tauri/src/ipc/command.rs:104— crates/tauri/src/ipc/command.rs:104-109 | crates/tauri/src/ipc/command.rs:147-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/tauri/src/tray/plugin.rs:118— crates/tauri/src/tray/plugin.rs:118-123 | crates/tauri/src/tray/plugin.rs:215-220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/tauri-utils/src/config.rs:2518— crates/tauri-utils/src/config.rs:2518-2523 | crates/tauri-utils/src/config_v1/mod.rs:1135-1140 — before extracting anything, compare `crates/tauri-utils/src/config.rs` and `crates/tauri-utils/src/config_v1/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) crates/tauri-utils/src/config/parse.rs:351— crates/tauri-utils/src/config/parse.rs:351-356 | crates/tauri-utils/src/config_v1/parse.rs:226-231 — `crates/tauri-utils/src/config/parse.rs` and `crates/tauri-utils/src/config_v1/parse.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 82 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) crates/tauri-utils/src/config/parse.rs:377— crates/tauri-utils/src/config/parse.rs:377-382 | crates/tauri-utils/src/config_v1/parse.rs:234-239 — `crates/tauri-utils/src/config/parse.rs` and `crates/tauri-utils/src/config_v1/parse.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 82 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) crates/tauri-utils/src/config/parse.rs:393— crates/tauri-utils/src/config/parse.rs:393-398 | crates/tauri-utils/src/config_v1/parse.rs:250-255 — `crates/tauri-utils/src/config/parse.rs` and `crates/tauri-utils/src/config_v1/parse.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 82 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Sync-over-async blocking packages/api-e2e/wdio.conf.ts:63— `fs.existsSync` in `onPrepare` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/api-e2e/wdio.conf.ts:96— `spawnSync` in `onPrepare` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/api-e2e/wdio.conf.ts:108— `fs.existsSync` in `onPrepare` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/api-e2e/wdio.mobile.ts:104— `fs.existsSync` in `onPrepare` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/api-e2e/wdio.mobile.ts:121— `fs.existsSync` in `onPrepare` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/api-e2e/wdio.mobile.ts:152— `fs.existsSync` in `onPrepare` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
FixmeComment crates/tauri-utils/src/build.rs:23— // FIXME: This can be accessed from multiple threads — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment crates/tauri-utils/src/build.rs:34— // FIXME: This can be accessed from multiple threads — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment crates/tauri-build/src/lib.rs:729— // FIXME: This can be accessed from multiple threads — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment crates/tauri-utils/src/acl/schema.rs:320— // FIXME: in schemars@v1 this doesn't seem to be necessary anymore. If it is, find a better solution. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment crates/tauri-utils/src/acl/schema.rs:395— // FIXME: in schemars@v1 this doesn't seem to be necessary anymore. If it is, find a better solution. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (13 lines × 2) crates/tauri-build/src/lib.rs:216— crates/tauri-build/src/lib.rs:216-228 | crates/tauri-bundler/src/utils/fs_utils.rs:116-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) crates/tauri-bundler/src/bundle/windows/msi/mod.rs:721— crates/tauri-bundler/src/bundle/windows/msi/mod.rs:721-733 | crates/tauri-bundler/src/bundle/windows/nsis/mod.rs:566-578 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) crates/tauri-cli/src/mobile/android/android_studio_script.rs:82— crates/tauri-cli/src/mobile/android/android_studio_script.rs:82-94 | crates/tauri-cli/src/mobile/ios/xcode_script.rs:121-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) crates/tauri-cli/src/mobile/android/run.rs:69— crates/tauri-cli/src/mobile/android/run.rs:69-81 | crates/tauri-cli/src/mobile/ios/run.rs:65-77 — `crates/tauri-cli/src/mobile/android/run.rs` and `crates/tauri-cli/src/mobile/ios/run.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 34 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 2) crates/tauri-cli/src/acl/capability/new.rs:114— crates/tauri-cli/src/acl/capability/new.rs:114-126 | crates/tauri-cli/src/acl/permission/new.rs:80-92 — `crates/tauri-cli/src/acl/capability/new.rs` and `crates/tauri-cli/src/acl/permission/new.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 33 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 2) crates/tauri-bundler/src/bundle/platform.rs:68— crates/tauri-bundler/src/bundle/platform.rs:68-78 | crates/tauri-utils/src/platform.rs:206-216 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) crates/tauri-utils/src/config.rs:2526— crates/tauri-utils/src/config.rs:2526-2536 | crates/tauri-utils/src/config_v1/mod.rs:1143-1153 — before extracting anything, compare `crates/tauri-utils/src/config.rs` and `crates/tauri-utils/src/config_v1/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) crates/tauri-utils/src/config_v1/mod.rs:3007— crates/tauri-utils/src/config_v1/mod.rs:3007-3017 | crates/tauri-utils/src/lib.rs:211-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) crates/tauri/src/app.rs:2278— crates/tauri/src/app.rs:2278-2288 | crates/tauri/src/plugin.rs:647-657 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) crates/tauri-bundler/src/bundle/linux/debian.rs:211— crates/tauri-bundler/src/bundle/linux/debian.rs:211-221 | crates/tauri-bundler/src/bundle/linux/debian.rs:229-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: Submenu (LCOM4 10) crates/tauri/src/menu/mod.rs:162— Submenu's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Window (LCOM4 9) crates/tauri/src/test/mock_runtime.rs:50— Window's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TrayIcon (LCOM4 7) crates/tauri/src/tray/mod.rs:398— TrayIcon's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Menu (LCOM4 5) crates/tauri/src/menu/mod.rs:155— Menu's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: IconMenuItem (LCOM4 4) crates/tauri/src/menu/mod.rs:174— IconMenuItem's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Outbound HTTP without resilience crates/tauri-bundler/src/utils/http_utils.rs:54— `ureq::Agent::config_builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/tauri-bundler/src/utils/http_utils.rs:69— `ureq::Agent::config_builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/tauri-cli/src/helpers/http.rs:11— `ureq::Agent::config_builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/tauri-driver/src/server.rs:199— `Client::builder(TokioExecutor` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/tauri/src/protocol/tauri.rs:41— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
tauri_runtime_wry::handle_user_message (cyclomatic 192) crates/tauri-runtime-wry/src/lib.rs:3172— tauri_runtime_wry::handle_user_message has cyclomatic complexity 192 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_runtime_wry::handle_event_loop (cyclomatic 51) crates/tauri-runtime-wry/src/lib.rs:4101— tauri_runtime_wry::handle_event_loop has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_runtime_wry::create_webview (cyclomatic 50) crates/tauri-runtime-wry/src/lib.rs:4669— tauri_runtime_wry::create_webview has cyclomatic complexity 50 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_runtime_wry::create_window (cyclomatic 24) crates/tauri-runtime-wry/src/lib.rs:4407— tauri_runtime_wry::create_window has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: CursorIconWrapper::from (cyclomatic 36) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
Repeated repair: crates/tauri-cli/src/interface/rust/desktop.rs crates/tauri-cli/src/interface/rust/desktop.rs:46— crates/tauri-cli/src/interface/rust/desktop.rs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is tauri_cli::interface::rust::desktop::run_dev at line 46), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(cli): skip target validation when rustup target list fails (#16305)”; “fix(cli): do not add --release when --profile=<name> is passed (#16126)”; “fix(cli): avoid blocking dev app exit handling on the stderr reader (#16110)”; “Revert "Add cleanup_before_exit plugin hook, CLI kills entire app tree (#14443)" (#16134)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-cli/src/interface/rust/desktop.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: crates/tauri-cli/src/mobile/mod.rs crates/tauri-cli/src/mobile/mod.rs:656— crates/tauri-cli/src/mobile/mod.rs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is tauri_cli::mobile::ensure_init at line 656), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(cli): pass Cargo credential provider settings to mobile IDE builds”; “fix(cli): keep devUrl query and fragment and treat IPv6 loopback as localhost on mobile (#16103)”; “fix(cli): authenticate the mobile options server (#16099)”; “fix(cli/mobile): normalize gradlew CRLF on Windows hosts too (#16017)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri-cli/src/mobile/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/api/src/webview.ts packages/api/src/webview.ts:393— packages/api/src/webview.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is Webview.emit at line 393), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(api): return awaitable cleanup from combined event listeners (#16195)”; “fix: enable macos private apis regardless of feature flags (#16166)”; “fix(api): pass the color argument to setBackgroundColor commands (#16067)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- packages/api/src/webview.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: crates/tauri/mobile/android/src/main/java/app/tauri/plugin/PluginManager.kt crates/tauri/mobile/android/src/main/java/app/tauri/plugin/PluginManager.kt:206— crates/tauri/mobile/android/src/main/java/app/tauri/plugin/PluginManager.kt changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is PluginManager.dispatchPluginMessage at line 206), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(android): JSObject and JSArray serialization”; “fix(android): register result launchers per activity (#15949)”; “fix(android): use whichever activity in plugin manager (#15798)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-26..2026-10-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-26 16:07:12 +02:00' --until='2026-10-24 16:07:12 +02:00' --full-history --no-merges -- crates/tauri/mobile/android/src/main/java/app/tauri/plugin/PluginManager.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
TooManyFields: WindowConfig crates/tauri-utils/src/config.rs:1954— TooManyFields — 63 stored fields. The bar is 30 stored fields; this is 33 over it, 2.10× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: WindowAllowlistConfig crates/tauri-utils/src/config_v1/mod.rs:1456— TooManyFields — 34 stored fields. The bar is 30 stored fields; this is 4 over it, 1.13× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: WebviewAttributes crates/tauri-runtime/src/webview.rs:337— TooManyFields — 33 stored fields beside 26 methods. The bar is 30 stored fields; this is 3 over it, 1.10× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: WindowConfig crates/tauri-utils/src/config_v1/mod.rs:924— TooManyFields — 33 stored fields. The bar is 30 stored fields; this is 3 over it, 1.10× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×4
tauri_build::try_build (cognitive 75) crates/tauri-build/src/lib.rs:652— tauri_build::try_build has cognitive complexity 75 (threshold 15). Drivers by points: if/else 30 (56 pts), loops 4 (8 pts), match/switch 4 (8 pts), boolean chains 3 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_build::mobile::generate_file_association_intent_filters (cognitive 45) crates/tauri-build/src/mobile.rs:22— tauri_build::mobile::generate_file_association_intent_filters has cognitive complexity 45 (threshold 15). Drivers by points: loops 6 (20 pts), if/else 8 (19 pts), match/switch 1 (6 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_build::copy_frameworks (cognitive 16) crates/tauri-build/src/lib.rs:250— tauri_build::copy_frameworks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RuntimeAuthority::resolve_access_message (cognitive 59) crates/tauri/src/ipc/authority.rs:222— RuntimeAuthority::resolve_access_message has cognitive complexity 59 (threshold 15). Drivers by points: if/else 34 (78 pts), loops 4 (11 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 53). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 2 other methods here (RuntimeAuthority::resolve_access_message::print_allowed_on, RuntimeAuthority::resolve_access_message::has_permissions_allowing_command) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RuntimeAuthority::resolve_access_message::has_permissions_allowing_command (cognitive 18) crates/tauri/src/ipc/authority.rs:290— RuntimeAuthority::resolve_access_message::has_permissions_allowing_command has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (RuntimeAuthority::resolve_access_message, RuntimeAuthority::resolve_access_message::print_allowed_on) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RuntimeAuthority::resolve_access_message::print_allowed_on (cognitive 16) crates/tauri/src/ipc/authority.rs:243— RuntimeAuthority::resolve_access_message::print_allowed_on has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 1 (3 pts), loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (RuntimeAuthority::resolve_access_message, RuntimeAuthority::resolve_access_message::has_permissions_allowing_command) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Change coupling: lib.rs ↔ lib.rs crates/tauri-build/src/lib.rs:1— `crates/tauri-build/src/lib.rs` and `crates/tauri-codegen/src/lib.rs` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `7a9b920c` docs: Remove header images from inline docs (#11749); `1efa5e71` fix(core): rerun build script if platform config changes, closes #109…; `ccc3ea72` fix(codegen): use `TAURI_ENV_TARGET_TRIPLE` to determine the current … (at that commit the files were still `core/tauri-build/src/lib.rs` and `core/tauri-codegen/src/lib.rs`) — run `git show` on any of them.
Change coupling: webview_window.rs ↔ plugin.rs crates/tauri/src/webview/webview_window.rs:1— `crates/tauri/src/webview/webview_window.rs` and `crates/tauri/src/window/plugin.rs` change together 52% of the time (16 of the 31 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `6edc2f4d` feat(window): add command to set fullscreen on specific monitor (#14926); `68874c68` feat(core): webview window focusable property, closes #11130 (#13564); `be2e6b85` add `Window.is_always_on_top()` and `WebviewWindow.is_always_on_top()… — run `git show` on any of them.
Change coupling: listener.rs ↔ plugin.rs crates/tauri/src/event/listener.rs:1— `crates/tauri/src/event/listener.rs` and `crates/tauri/src/event/plugin.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6cbfc487` refactor: document `Emitter`/`Listner` traits panics, refactor check …; `93c8a77b` refactor: enhance event system rust apis (#7996) (at that commit the files were still `core/tauri/src/event/listener.rs` and `core/tauri/src/event/plugin.rs`); `2558fab8` refactor!: remove uuid and rand dependencies where applicable (#7939) (at that commit the files were still `core/tauri/src/event/listener.rs` and `core/tauri/src/event/commands.rs`) — run `git show` on any of them.
Duplicated block (8 lines × 2) crates/tauri-utils/src/config_v1/mod.rs:2996— crates/tauri-utils/src/config_v1/mod.rs:2996-3003 | crates/tauri-utils/src/lib.rs:200-207 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/tauri-utils/src/html.rs:151— crates/tauri-utils/src/html.rs:151-158 | crates/tauri-utils/src/html2.rs:70-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) crates/tauri-cli/src/mobile/android/mod.rs:691— crates/tauri-cli/src/mobile/android/mod.rs:691-698 | crates/tauri-cli/src/mobile/android/mod.rs:789-800 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
tauri_build::try_build (cyclomatic 41) crates/tauri-build/src/lib.rs:652— tauri_build::try_build has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_build::mobile::generate_file_association_intent_filters (cyclomatic 16) crates/tauri-build/src/mobile.rs:22— tauri_build::mobile::generate_file_association_intent_filters has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This is NOT this file's highest cyclomatic complexity: tauri_build::mobile::extension_to_mime_type (cyclomatic 24) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
WebviewManager::prepare_pending_webview (cyclomatic 28) crates/tauri/src/manager/webview.rs:124— WebviewManager::prepare_pending_webview has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebviewManager::prepare_webview (cyclomatic 27) crates/tauri/src/manager/webview.rs:455— WebviewManager::prepare_webview has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
No assertions: init a project and builds it packages/cli/__tests__/template.spec.ts:26— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: setTheme applies a theme and can be reset to the system default packages/api-e2e/test/specs/app.spec.ts:43— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
WebviewManager::prepare_pending_webview (cognitive 42) crates/tauri/src/manager/webview.rs:124— WebviewManager::prepare_pending_webview has cognitive complexity 42 (threshold 15). Drivers by points: if/else 22 (35 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebviewManager::prepare_webview (cognitive 41) crates/tauri/src/manager/webview.rs:455— WebviewManager::prepare_webview has cognitive complexity 41 (threshold 15). Drivers by points: if/else 22 (34 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResourcePathsIter::next_pattern (cognitive 24) crates/tauri-utils/src/resources.rs:253— ResourcePathsIter::next_pattern has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 3 (5 pts), loops 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResourcePathsIter::resource_from_path (cognitive 17) crates/tauri-utils/src/resources.rs:205— ResourcePathsIter::resource_from_path has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 2 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_utils::acl::resolved::with_resolved_permissions (cognitive 20) crates/tauri-utils/src/acl/resolved.rs:321— tauri_utils::acl::resolved::with_resolved_permissions has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_utils::platform::target_triple (cognitive 19) crates/tauri-utils/src/platform.rs:193— tauri_utils::platform::target_triple has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TooManyFunctions: tauri::window::plugin::desktop_commands crates/tauri/src/window/plugin.rs:132— TooManyFunctions — 43 free functions. The bar is 30 free functions; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyFunctions: tauri::window::plugin::commands crates/tauri/src/window/plugin.rs:61— TooManyFunctions — 36 free functions. The bar is 30 free functions; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/tauri-cli/src/mobile/android/dev.rs:143— crates/tauri-cli/src/mobile/android/dev.rs:143-228 | crates/tauri-cli/src/mobile/android/run.rs:66-184 | crates/tauri-cli/src/mobile/ios/dev.rs:150-283 | crates/tauri-cli/src/mobile/ios/run.rs:63-144 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/tauri-cli/src/mobile/android/mod.rs:820— crates/tauri-cli/src/mobile/android/mod.rs:820-868 | crates/tauri-cli/src/mobile/android/mod.rs:870-909 | crates/tauri-cli/src/mobile/ios/mod.rs:286-332 | crates/tauri-cli/src/mobile/ios/mod.rs:344-401 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (17–18 lines × 2) crates/tauri-bundler/src/bundle/updater_bundle.rs:63— crates/tauri-bundler/src/bundle/updater_bundle.rs:63-80 | crates/tauri-bundler/src/bundle/updater_bundle.rs:99-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–18 lines × 2) crates/tauri-runtime-wry/src/lib.rs:4192— crates/tauri-runtime-wry/src/lib.rs:4192-4209 | crates/tauri-runtime-wry/src/lib.rs:4219-4235 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) crates/tauri-cli/src/mobile/android/dev.rs:248— crates/tauri-cli/src/mobile/android/dev.rs:248-264 | crates/tauri-cli/src/mobile/ios/dev.rs:302-318 — `crates/tauri-cli/src/mobile/android/dev.rs` and `crates/tauri-cli/src/mobile/ios/dev.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 38 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (17 lines × 2) crates/tauri-utils/src/config.rs:2603— crates/tauri-utils/src/config.rs:2603-2619 | crates/tauri-utils/src/config_v1/mod.rs:1195-1211 — before extracting anything, compare `crates/tauri-utils/src/config.rs` and `crates/tauri-utils/src/config_v1/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15–16 lines × 2) crates/tauri-cli/src/mobile/ios/mod.rs:143— crates/tauri-cli/src/mobile/ios/mod.rs:143-157 | crates/tauri-cli/src/mobile/ios/mod.rs:169-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) crates/tauri-utils/src/acl/mod.rs:386— crates/tauri-utils/src/acl/mod.rs:386-400 | crates/tauri/src/ipc/authority.rs:157-172 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) crates/tauri-cli/src/mobile/android/android_studio_script.rs:52— crates/tauri-cli/src/mobile/android/android_studio_script.rs:52-66 | crates/tauri-cli/src/mobile/ios/xcode_script.rs:90-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) crates/tauri-cli/src/info/env_system.rs:27— crates/tauri-cli/src/info/env_system.rs:27-41 | crates/tauri-cli/src/info/env_system.rs:46-60 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/tauri-cli/src/mobile/ios/mod.rs:383— crates/tauri-cli/src/mobile/ios/mod.rs:383-396 | crates/tauri-cli/src/mobile/ios/mod.rs:431-444 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/tauri-runtime-wry/src/undecorated_resizing.rs:280— crates/tauri-runtime-wry/src/undecorated_resizing.rs:280-293 | crates/tauri-runtime-wry/src/undecorated_resizing.rs:327-340 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–11 lines × 2) crates/tauri-utils/src/config.rs:282— crates/tauri-utils/src/config.rs:282-292 | crates/tauri-utils/src/config_v1/mod.rs:273-282 — before extracting anything, compare `crates/tauri-utils/src/config.rs` and `crates/tauri-utils/src/config_v1/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 2) crates/tauri-utils/src/resources.rs:18— crates/tauri-utils/src/resources.rs:18-28 | crates/tauri/src/path/mod.rs:356-365 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2 locations) packages/api/src/webviewWindow.ts:204— packages/api/src/webviewWindow.ts:204 · packages/api/src/webviewWindow.ts:242 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2 locations) packages/api/src/window.ts:503— packages/api/src/window.ts:503 · packages/api/src/window.ts:541 — all 2 copies are in the same file, and the CITED SPAN is inside a TYPE DECLARATION, not executable code. There is no function to extract and no call site to call one from, so do not read this as an extract-a-helper row: the collapse a type offers is a generic — name the shape once, parameterised over the part that varies, and have each copy instantiate it. First check what actually differs between the copies: where they are a MATRIX of cases (one entry per input, differing precisely in the case each one pins), the repetition IS the enumeration and collapsing it would delete cases rather than de-duplicate anything — leave those alone. Reported because the copies that are not a matrix drift apart the first time only one of them is edited.
Weak hash algorithm crates/tauri-bundler/src/bundle/linux/debian.rs:312— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm crates/tauri-bundler/src/utils/http_utils.rs:127— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark crates/tauri-cli/templates/plugin/__example-basic/vanilla/public/index.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement crates/tauri-cli/templates/plugin/__example-api/tauri-app/src/style.css:80— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-svelte (a11y rules are built in)) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
tauri_codegen::context::context_codegen (cyclomatic 35) crates/tauri-codegen/src/context.rs:134— tauri_codegen::context::context_codegen has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RuntimeAuthority::resolve_access_message (cyclomatic 31) crates/tauri/src/ipc/authority.rs:222— RuntimeAuthority::resolve_access_message has cyclomatic complexity 31 (threshold 15). Of this number, 17 points are the body's own statements and 14 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tauri_macros::command::wrapper::wrapper (cyclomatic 18) crates/tauri-macros/src/command/wrapper.rs:152— tauri_macros::command::wrapper::wrapper has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
base.newMenu (cyclomatic 17) packages/api/src/menu/base.ts:86— base.newMenu has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
FsUtils.getFileUrlForUri (cyclomatic 16) crates/tauri/mobile/android/src/main/java/app/tauri/FsUtils.kt:28— FsUtils.getFileUrlForUri has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ipc.sendIsolationMessage (cyclomatic 16) REDACTED:70— ipc.sendIsolationMessage has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (serializeIpcPayload). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
checkFile (cyclomatic 16) .scripts/ci/check-license-header.js:35— checkFile has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: packages/cli packages/cli/__tests__/template.spec.ts:26— No conventional assertion call was detected in 1 of 1 tests in `packages/cli` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
tauri_codegen::context::context_codegen (cognitive 64) crates/tauri-codegen/src/context.rs:134— tauri_codegen::context::context_codegen has cognitive complexity 64 (threshold 15). Drivers by points: if/else 40 (55 pts), match/switch 3 (6 pts), boolean chains 3 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_macros::command::wrapper::wrapper (cognitive 41) crates/tauri-macros/src/command/wrapper.rs:152— tauri_macros::command::wrapper::wrapper has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (32 pts), match/switch 4 (7 pts), loops 1 (2 pts) (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Resolved::resolve_with_base_scope_id (cognitive 33) crates/tauri-utils/src/acl/resolved.rs:146— Resolved::resolve_with_base_scope_id has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 4 (8 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WrapperAttributes::parse (cognitive 32) crates/tauri-macros/src/command/wrapper.rs:47— WrapperAttributes::parse has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (24 pts), match/switch 2 (7 pts), loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
checkChangeFiles (cognitive 32) .scripts/ci/check-change-tags.js:25— checkChangeFiles has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 6 (13 pts), boolean chains 2 (nesting depth added 18). Of this number, 31 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FsUtils.getFileUrlForUri (cognitive 31) crates/tauri/mobile/android/src/main/java/app/tauri/FsUtils.kt:28— FsUtils.getFileUrlForUri has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (27 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Plugin.getPermissionStates (cognitive 31) crates/tauri/mobile/android/src/main/java/app/tauri/plugin/Plugin.kt:487— Plugin.getPermissionStates has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Plugin.requestPermissions (cognitive 27) crates/tauri/mobile/android/src/main/java/app/tauri/plugin/Plugin.kt:293— Plugin.requestPermissions has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContextItems::parse (cognitive 26) crates/tauri-macros/src/context.rs:25— ContextItems::parse has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Webview::on_message (cognitive 25) crates/tauri/src/webview/mod.rs:2005— Webview::on_message has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 1 (3 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 10). Of this number, 16 points are the body's own statements and 9 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tauri_driver::server::map_capabilities (cognitive 25) crates/tauri-driver/src/server.rs:139— tauri_driver::server::map_capabilities has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (25 pts) (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
(anonymous) (cognitive 23) REDACTED:567— (anonymous) has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 5, loops 2 (3 pts), other 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
checkFile (cognitive 22) .scripts/ci/check-license-header.js:35— checkFile has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 10). Of this number, 21 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Config::load (cognitive 21) crates/tauri-cli/src/interface/rust/cargo_config.rs:97— Config::load has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 1 (2 pts) (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Rust::run_dev_watcher (cognitive 21) crates/tauri-cli/src/interface/rust.rs:506— Rust::run_dev_watcher has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Pbxproj::set_build_settings (cognitive 20) crates/tauri-cli/src/helpers/pbxproj.rs:269— Pbxproj::set_build_settings has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 2 (5 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Builder::build (cognitive 19) crates/tauri/src/app.rs:2408— Builder::build has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 1, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WebviewBuilder::into_pending_webview (cognitive 18) crates/tauri/src/webview/mod.rs:759— WebviewBuilder::into_pending_webview has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RustAppSettings::get_binaries (cognitive 18) crates/tauri-cli/src/interface/rust.rs:928— RustAppSettings::get_binaries has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createFixture (cognitive 17) REDACTED:419— createFixture has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 1 (2 pts), other 2, boolean chains 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowEventWrapper::map_from_tao (cognitive 16) crates/tauri-runtime-wry/src/lib.rs:510— WindowEventWrapper::map_from_tao has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PluginManager.invoke (cognitive 16) crates/tauri/mobile/ios-api/Sources/Tauri/Tauri.swift:59— PluginManager.invoke has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (16 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (38 shared lines) crates/tauri-cli/src/plugin/android.rs:47— crates/tauri-cli/src/plugin/android.rs:47-133 | crates/tauri-cli/src/plugin/ios.rs:53-159 — These two members are variants of one another: 38 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (28 shared lines) crates/tauri-cli/src/acl/capability/new.rs:39— crates/tauri-cli/src/acl/capability/new.rs:39-148 | crates/tauri-cli/src/acl/permission/new.rs:40-124 — These two members are variants of one another: 28 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Duplicated block (64 lines × 2) crates/tauri-utils/src/config/parse.rs:272— crates/tauri-utils/src/config/parse.rs:272-335 | crates/tauri-utils/src/config_v1/parse.rs:161-224 — `crates/tauri-utils/src/config/parse.rs` and `crates/tauri-utils/src/config_v1/parse.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 82 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (26 lines × 2) crates/tauri-utils/src/config.rs:3943— crates/tauri-utils/src/config.rs:3943-3968 | crates/tauri-utils/src/config_v1/mod.rs:2778-2803 — before extracting anything, compare `crates/tauri-utils/src/config.rs` and `crates/tauri-utils/src/config_v1/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (25 lines × 2) crates/tauri-utils/src/html.rs:291— crates/tauri-utils/src/html.rs:291-315 | crates/tauri-utils/src/html2.rs:170-194 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (24 lines × 2) crates/tauri-cli/src/interface/rust/manifest.rs:125— crates/tauri-cli/src/interface/rust/manifest.rs:125-148 | crates/tauri-cli/src/migrate/migrations/v1/manifest.rs:132-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (19–23 lines × 2) crates/tauri-cli/src/plugin/android.rs:86— crates/tauri-cli/src/plugin/android.rs:86-108 | crates/tauri-cli/src/plugin/ios.rs:112-130 — before extracting anything, compare `crates/tauri-cli/src/plugin/android.rs` and `crates/tauri-cli/src/plugin/ios.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) crates/tauri/src/path/plugin.rs:19— crates/tauri/src/path/plugin.rs:19-36 | crates/tauri/src/path/plugin.rs:49-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–16 lines × 2) crates/tauri-build/src/acl.rs:215— crates/tauri-build/src/acl.rs:215-230 | crates/tauri-build/src/acl.rs:290-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) crates/tauri-utils/src/config.rs:246— crates/tauri-utils/src/config.rs:246-261 | crates/tauri-utils/src/config_v1/mod.rs:237-252 — before extracting anything, compare `crates/tauri-utils/src/config.rs` and `crates/tauri-utils/src/config_v1/mod.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 4) crates/tauri-cli/src/mobile/android/mod.rs:826— crates/tauri-cli/src/mobile/android/mod.rs:826-840 | crates/tauri-cli/src/mobile/android/mod.rs:872-886 | crates/tauri-cli/src/mobile/ios/mod.rs:290-304 | crates/tauri-cli/src/mobile/ios/mod.rs:350-364 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9–15 lines × 2) crates/tauri-cli/src/dev.rs:253— crates/tauri-cli/src/dev.rs:253-261 | crates/tauri-cli/src/mobile/mod.rs:263-277 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 3) crates/tauri/src/menu/plugin.rs:161— crates/tauri/src/menu/plugin.rs:161-172 | crates/tauri/src/menu/plugin.rs:217-228 | crates/tauri/src/menu/plugin.rs:256-267 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) crates/tauri-cli/src/mobile/android/dev.rs:169— crates/tauri-cli/src/mobile/android/dev.rs:169-179 | crates/tauri-cli/src/mobile/android/run.rs:69-79 | crates/tauri-cli/src/mobile/ios/run.rs:65-75 — `crates/tauri-cli/src/mobile/android/run.rs` and `crates/tauri-cli/src/mobile/ios/run.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 34 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8–10 lines × 2) crates/tauri-utils/src/config.rs:4367— crates/tauri-utils/src/config.rs:4367-4376 | crates/tauri-utils/src/config.rs:4406-4413 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 3) crates/tauri/src/webview/mod.rs:2503— crates/tauri/src/webview/mod.rs:2503-2512 | crates/tauri/src/webview/mod.rs:2520-2529 | crates/tauri/src/window/mod.rs:2488-2497 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (20 lines × 2) crates/tauri-cli/src/mobile/android/mod.rs:656— crates/tauri-cli/src/mobile/android/mod.rs:656-675 | crates/tauri-cli/src/mobile/android/mod.rs:756-775 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 3) crates/tauri-cli/src/info/env_system.rs:104— crates/tauri-cli/src/info/env_system.rs:104-111 | crates/tauri-cli/src/info/env_system.rs:118-125 | crates/tauri-cli/src/info/env_system.rs:132-139 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) crates/tauri-cli/src/migrate/migrations/v1/config.rs:271— crates/tauri-cli/src/migrate/migrations/v1/config.rs:271-276 | crates/tauri-cli/src/migrate/migrations/v1/config.rs:279-284 | crates/tauri-cli/src/migrate/migrations/v1/config.rs:287-292 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
End-of-life runtime: Node.js 10 packages/cli/package.json:50— packages/cli/package.json declares Node.js 10 as this project's engines.node, and Node.js 10, support ended 2021-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2021-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Off the main sequence: tauri-utils — tauri-utils: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — packages/cli/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
Duplicated block (109 lines × 2 locations) packages/api/src/menu/menu.ts:129— packages/api/src/menu/menu.ts:129 · packages/api/src/menu/submenu.ts:118 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (62 lines × 2 locations) packages/api/src/webview.ts:769— packages/api/src/webview.ts:769 · packages/api/src/window.ts:2407 — the 2 copies are spread across 2 files, and the CITED SPAN is inside a TYPE DECLARATION, not executable code. There is no function to extract and no call site to call one from, so do not read this as an extract-a-helper row: the collapse a type offers is a generic — name the shape once, parameterised over the part that varies, and have each copy instantiate it. First check what actually differs between the copies: where they are a MATRIX of cases (one entry per input, differing precisely in the case each one pins), the repetition IS the enumeration and collapsing it would delete cases rather than de-duplicate anything — leave those alone. Reported because the copies that are not a matrix drift apart the first time only one of them is edited.
Duplicated block (47 lines × 2 locations) packages/api/src/webview.ts:376— packages/api/src/webview.ts:376 · packages/api/src/window.ts:547 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (45 lines × 2 locations) packages/api/src/dpi.ts:131— packages/api/src/dpi.ts:131 · packages/api/src/dpi.ts:345 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (38 lines × 2 locations) packages/api/src/menu/checkMenuItem.ts:10— packages/api/src/menu/checkMenuItem.ts:10 · packages/api/src/menu/iconMenuItem.ts:133 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (37 lines × 2 locations) packages/api/src/dpi.ts:60— packages/api/src/dpi.ts:60 · packages/api/src/dpi.ts:278 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (36 matched lines × 2 locations) · ×1
Duplicated block with local edits (36 matched lines × 2 locations) packages/api/src/webviewWindow.ts:58— packages/api/src/webviewWindow.ts:58 · packages/api/src/window.ts:317 — the two spans are one implementation copied and then locally edited — 203 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (35 lines × 3 locations) packages/api/src/menu/checkMenuItem.ts:13— packages/api/src/menu/checkMenuItem.ts:13 · packages/api/src/menu/iconMenuItem.ts:145 · packages/api/src/menu/menuItem.ts:67 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) packages/api/src/webview.ts:266— packages/api/src/webview.ts:266 · packages/api/src/window.ts:418 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) REDACTED:79— REDACTED:79 · REDACTED:40 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (13 lines × 5 locations) packages/api/src/menu/checkMenuItem.ts:27— packages/api/src/menu/checkMenuItem.ts:27 · packages/api/src/menu/iconMenuItem.ts:158 · packages/api/src/menu/menuItem.ts:77 · packages/api/src/menu/predefinedMenuItem.ts:183 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 4 locations) packages/api/src/webview.ts:516— packages/api/src/webview.ts:516 · packages/api/src/window.ts:1578 · packages/api/src/window.ts:1679 · packages/api/src/window.ts:1989 — the 4 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (9 lines × 2 locations) packages/api/src/menu/base.ts:63— packages/api/src/menu/base.ts:63 · packages/api/src/menu/base.ts:113 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function newMenu (cyclomatic 17, cognitive 18) packages/api/src/menu/base.ts:86— newMenu has cyclomatic complexity 17 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function serializeIpcPayload (cyclomatic 12, cognitive 11) REDACTED:95— serializeIpcPayload has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
packages/api/src/window.ts: 3081 lines of code packages/api/src/window.ts:1— packages/api/src/window.ts has 3081 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/api/src/webview.ts · ×1
packages/api/src/webview.ts: 1010 lines of code packages/api/src/webview.ts:1— packages/api/src/webview.ts has 1010 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
packages/api/src/path.ts: 823 lines of code packages/api/src/path.ts:1— packages/api/src/path.ts has 823 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
packages/api/src/core.ts: 587 lines of code packages/api/src/core.ts:1— packages/api/src/core.ts has 587 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
packages/api/src/tray.ts: 472 lines of code packages/api/src/tray.ts:1— packages/api/src/tray.ts has 472 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
packages/api/src/dpi.ts: 441 lines of code packages/api/src/dpi.ts:1— packages/api/src/dpi.ts has 441 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/api-e2e/wdio.mobile.ts · ×1
packages/api-e2e/wdio.mobile.ts: 412 lines of code packages/api-e2e/wdio.mobile.ts:1— packages/api-e2e/wdio.mobile.ts has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Unused dependency 'appium-uiautomator2-driver' — Declared in packages/api-e2e/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'appium-xcuitest-driver' — Declared in packages/api-e2e/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Swallowed exception (caught, then discarded) crates/tauri/mobile/android/src/main/java/app/tauri/FsUtils.kt:148— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (empty catch) crates/tauri/mobile/android/src/main/java/app/tauri/PermissionHelper.kt:81— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Interpolated log message defeats structured logging crates/tauri-runtime-wry/src/lib.rs:1135— `warn!` at line 1135 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/tauri-runtime-wry/src/lib.rs:3557— `warn!` at line 3557 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/tauri/src/webview/mod.rs:409— `error!` at line 409 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/tauri/src/webview/mod.rs:422— `error!` at line 422 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/tauri/src/webview/mod.rs:2013— `error!` at line 2013 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/tauri/src/ipc/protocol.rs:424— `trace!` at line 424 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Orphaned file crates/tauri-bundler/src/bundle/linux/freedesktop/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/tauri-utils/src/tokens.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/tauri-utils/src/pattern/isolation.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/tauri-macros/src/runtime.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate REDACTED:97— `typeof data === 'object' && 'callback' in data && 'error' in data && !isIsolationMessage(data)` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/tauri-bundler/src/bundle/platform.rs:84— `cfg!(target_os = "macos") || cfg!(target_os = "freebsd")` appears character-identically in 2 files — crates/tauri-bundler/src/bundle/platform.rs, crates/tauri-utils/src/platform.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/tauri/src/manager/mod.rs:789— `cfg!(windows) || cfg!(target_os = "android")` appears character-identically in 2 files — crates/tauri/src/manager/mod.rs, crates/tauri/src/protocol/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: crates/tauri-plugin/src/build/mobile.rs, crates/tauri-cli/src/helpers/framework.rs, crates/tauri-cli/src/acl/mod.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 3 significant file(s) lose their only recent owner: crates/tauri-macros/src/menu.rs, crates/tauri/src/image/plugin.rs, crates/tauri/src/manager/tray.rs. Pair on, review, or document these before any departure.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 4 of 19 project(s) overshoot their size bounds, lowering Project Cohesion to 6.2/10. The most over is `crates/tauri` (30727 LoC, 186 module-visible types across 21 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 4 of 205 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 205 of the 292 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: crates/tauri-bundler/src/bundle/linux/freedesktop/mod.rs, crates/tauri-utils/src/tokens.rs, crates/tauri-utils/src/pattern/isolation.rs, crates/tauri-macros/src/runtime.rs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 10/14 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/tauri-driver`, `crates/tauri-schema-generator`, `crates/tauri-schema-worker`, `packages/cli`.
Security headers incomplete — Set: Content-Security-Policy, Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy, Cross-Origin-Resource-Policy, Permissions-Policy, X-Content-Type-Options. Missing: Strict-Transport-Security, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.0 on this card.) The server: `.serve_connection(` (crates/tauri-driver/src/server.rs:219).
No inbound request validation detected — No handler of this repository's Rust server answers 400, 413 or 422 (`StatusCode::BAD_REQUEST`, `HttpResponse::BadRequest()`, `Status::BadRequest`, tonic `Status::invalid_argument`), and nothing declares validation — no `validator`/`garde` derive, no body limit (`DefaultBodyLimit::max`, `RequestBodyLimitLayer`, `JsonConfig::default().limit(…)`, Rocket `Limits`) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: `.serve_connection(` (crates/tauri-driver/src/server.rs:219).
Hand-rolled JSON/XML parsing via regex crates/tauri-cli/src/helpers/npm.rs:240— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Rust code already uses a real parser in the same package; use it here too.
Silent fallback default in catch packages/api-e2e/wdio.mobile.ts:187— `mobileConfig.before` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 8 file(s) — `crates/tauri-cli/templates/mobile/android/app/build.gradle.kts`, `crates/tauri-cli/templates/mobile/android/app/src/main/MainActivity.kt`, `crates/tauri-cli/templates/mobile/android/build.gradle.kts`, `crates/tauri-cli/templates/plugin/android/src/main/java/Example.kt`, `crates/tauri-cli/templates/plugin/android/src/main/java/ExamplePlugin.kt`, … (+3 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a174e1-256c-7b4d-969e-728ffb99a020 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 200 · Warnings: 516 · Recommendations: 29 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 25-10-2026 @ 21:04 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.