Public report of Zackriya-Solutions/meetily, published 26 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, 26 October 2026, 02:45 UTC · Survey ID cd_60c2741ae916455c88c0ad1bb5a572ce
Zackriya-Solutions/meetily
Measured 26 October 2026, 02:42 UTC, at code version a2cb62e
No regression since the last survey
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.
CAI scoreAt riskNo change 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 medium codebase: 72,854 lines of product code in 5 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 33
Findings by how serious they are
206 critical759 serious133 minor
11 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
26 October 2026, 02:42 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
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 ▸
88of 88 dimensions measured by tools.
1046of 1098 findings point to an exact file and line, so you can open each one in the code. The other 52 concern the repository as a whole, such as missing documentation.
88dimensions across 10 lenses, read from 72,854 lines of product code in 5 projects.
Zackriya-Solutions/meetily is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 44 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first steps are adding automated security scanning and documenting the recovery plan, each worth about 4 points. Raising Production Readiness to 62 would lift the score to about 51.
Fifty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fifty-three secrets can leak from the build pipeline, and nineteen known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. Passing outside input through environment variables would fix the 12 pipeline steps that put outside input straight into a shell command, and the ten unsafe settings in infrastructure or container files need changing to safe values. The 19 buttons or links with no name need a name, even when they only show an icon.
The product code is 72,854 lines, about €64,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.
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/components/MeetingDetails/SummaryPanel.tsx
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/components/ModelDownloadProgress.tsx
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/components/RecordingControls.tsx
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/components/RecordingControls.tsx
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/components/VirtualizedTranscriptView.tsx
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/components/VirtualizedTranscriptView.tsx
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/app/globals.css
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/app/globals.css
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/app/globals.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: 105 findings
These 105 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.
Code Duplication · Edited copy of a member (40 corresponding lines) backend/app/db.py
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) backend/app/db.py
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) backend/app/db.py
Test Coverage · No test reaches this file frontend/src/app/settings/page.tsx
Test Coverage · No test reaches this file frontend/src/components/molecules/form-components/form-input-item.tsx
Test Coverage · No test reaches this file scripts/test-update-locally.js
Test Coverage · No test reaches this file frontend/src/components/ModelDownloadProgress.tsx
Test Coverage · No test reaches this file frontend/src/components/ComplianceNotification.tsx
Test Coverage · No test reaches this file frontend/src/app/_components/TranscriptPanel.tsx
Test Coverage · No test reaches this file frontend/src/services/transcriptService.ts
Test Coverage · No test reaches this file frontend/src/components/onboarding/steps/SetupOverviewStep.tsx
Test Coverage · No test reaches this file frontend/src/components/BluetoothPlaybackWarning.tsx
Test Coverage · No test reaches this file frontend/src/components/onboarding/OnboardingContainer.tsx
Test Coverage · No test reaches this file REDACTED
Test Coverage · No test reaches this file frontend/src/components/SummaryLanguageSettings.tsx
Test Coverage · No test reaches this file frontend/src/lib/builtin-ai.ts
Test Coverage · No test reaches this file frontend/src/components/ConsoleToggle.tsx
Test Coverage · No test reaches this file frontend/src/components/molecules/form-components/form-select-item.tsx
Test Coverage · No test reaches this file frontend/src/hooks/usePermissionCheck.ts
Test Coverage · No test reaches this file frontend/src/hooks/usePlatform.ts
Test Coverage · No test reaches this file frontend/src/components/onboarding/shared/PermissionRow.tsx
Test Coverage · No test reaches this file frontend/src/components/UpdateCheckProvider.tsx
Test Coverage · No test reaches this file frontend/src/components/BetaSettings.tsx
Test Coverage · No test reaches this file frontend/src/hooks/useRecordingStateSync.ts
Test Coverage · No test reaches this file frontend/src/services/storageService.ts
Test Coverage · No test reaches this file frontend/src/components/onboarding/shared/ProgressIndicator.tsx
Test Coverage · No test reaches this file frontend/src/components/onboarding/steps/WelcomeStep.tsx
Test Coverage · No test reaches this file frontend/scripts/tauri-auto.js
Test Coverage · No test reaches this file frontend/src/hooks/useUpdateCheck.ts
Test Coverage · No test reaches this file frontend/src/components/SettingTabs.tsx
Test Coverage · No test reaches this file frontend/src/lib/recordingNotification.tsx
Test Coverage · No test reaches this file frontend/src/app/_components/StatusOverlays.tsx
Test Coverage · No test reaches this file frontend/src/contexts/RecordingPostProcessingProvider.tsx
Test Coverage · No test reaches this file frontend/src/components/molecules/form-components/form-input-switch.tsx
Test Coverage · No test reaches this file frontend/src/components/Logo.tsx
Test Coverage · No test reaches this file frontend/src/components/onboarding/OnboardingFlow.tsx
Test Coverage · No test reaches this file frontend/src/components/UpdateNotification.tsx
Test Coverage · No test reaches this file frontend/src/contexts/ImportDialogContext.tsx
Test Coverage · No test reaches this file frontend/src/components/Info.tsx
Test Coverage · No test reaches this file frontend/src/constants/audioFormats.ts
Test Coverage · No test reaches this file frontend/src/components/ConfirmationModel/confirmation-modal.tsx
Test Coverage · No test reaches this file frontend/src/components/CustomDialog.tsx
Test Coverage · No test reaches this file frontend/src/components/ui/progress.tsx
Test Coverage · No test reaches this file frontend/src/components/ImportAudio/ImportDropOverlay.tsx
Test Coverage · No test reaches this file frontend/src/components/MainContent/index.tsx
Test Coverage · No test reaches this file frontend/src/components/MessageToast.tsx
Test Coverage · No test reaches this file frontend/src/constants/modelDefaults.ts
Test Coverage · No test reaches this file frontend/src/components/ui/textarea.tsx
Rebuild cost: about €64,000 · Estimate
Cost to rebuild
€21,000 to €110,000, for 356 to 1,129 hours of work, about 0.4 person-years for one engineer
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 44. 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
Medium: 72,854 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
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
Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
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 €64,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 33 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for medium effort. 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 6.4 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 4% to 9% on every change. The history of the code shows how much it changes: about 17,165 lines over the last 90 days, which is about 69,614 lines a year. At that pace, the extra work comes to an estimated 7 to 41.8 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, never less than 2% to 5% and never more than 40% to 60% in all; 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: 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.
264 modules, with 195 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 224 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.
frontend.src.components.MeetingDetails.SummaryPanel uses frontend.src.components.ModelSettingsModal, so a change to frontend.src.components.ModelSettingsModal can break frontend.src.components.MeetingDetails.SummaryPanel, while a change to frontend.src.components.MeetingDetails.SummaryPanel can't break frontend.src.components.ModelSettingsModal.
Position
Below the diagonal: frontend.src.components.MeetingDetails.SummaryPanel uses a module listed above it, which is the healthy direction.
frontend.src.components.SettingTabs uses frontend.src.components.ModelSettingsModal, so a change to frontend.src.components.ModelSettingsModal can break frontend.src.components.SettingTabs, while a change to frontend.src.components.SettingTabs can't break frontend.src.components.ModelSettingsModal.
Position
Below the diagonal: frontend.src.components.SettingTabs uses a module listed above it, which is the healthy direction.
frontend.src.components.SettingTabs uses frontend.src.components.TranscriptSettings, so a change to frontend.src.components.TranscriptSettings can break frontend.src.components.SettingTabs, while a change to frontend.src.components.SettingTabs can't break frontend.src.components.TranscriptSettings.
Position
Below the diagonal: frontend.src.components.SettingTabs uses a module listed above it, which is the healthy direction.
frontend.src.contexts.ConfigContext uses frontend.src.components.ModelSettingsModal, so a change to frontend.src.components.ModelSettingsModal can break frontend.src.contexts.ConfigContext, while a change to frontend.src.contexts.ConfigContext can't break frontend.src.components.ModelSettingsModal.
Position
Below the diagonal: frontend.src.contexts.ConfigContext uses a module listed above it, which is the healthy direction.
frontend.src.contexts.ConfigContext uses frontend.src.components.TranscriptSettings, so a change to frontend.src.components.TranscriptSettings can break frontend.src.contexts.ConfigContext, while a change to frontend.src.contexts.ConfigContext can't break frontend.src.components.TranscriptSettings.
Position
Below the diagonal: frontend.src.contexts.ConfigContext uses a module listed above it, which is the healthy direction.
frontend.src.hooks uses frontend.src.components.TranscriptSettings, so a change to frontend.src.components.TranscriptSettings can break frontend.src.hooks, while a change to frontend.src.hooks can't break frontend.src.components.TranscriptSettings.
Position
Below the diagonal: frontend.src.hooks uses a module listed above it, which is the healthy direction.
frontend.src.hooks uses frontend.src.types, so a change to frontend.src.types can break frontend.src.hooks, while a change to frontend.src.hooks can't break frontend.src.types.
Position
Below the diagonal: frontend.src.hooks uses a module listed above it, which is the healthy direction.
frontend.src.hooks.meeting-details.useSummaryGeneration uses frontend.src.components.ModelSettingsModal, so a change to frontend.src.components.ModelSettingsModal can break frontend.src.hooks.meeting-details.useSummaryGeneration, while a change to frontend.src.hooks.meeting-details.useSummaryGeneration can't break frontend.src.components.ModelSettingsModal.
Position
Below the diagonal: frontend.src.hooks.meeting-details.useSummaryGeneration uses a module listed above it, which is the healthy direction.
frontend.src.lib.parakeet uses frontend.src.lib.whisper, so a change to frontend.src.lib.whisper can break frontend.src.lib.parakeet, while a change to frontend.src.lib.parakeet can't break frontend.src.lib.whisper.
Position
Below the diagonal: frontend.src.lib.parakeet uses a module listed above it, which is the healthy direction.
frontend.src.services.configService uses frontend.src.components.ModelSettingsModal, so a change to frontend.src.components.ModelSettingsModal can break frontend.src.services.configService, while a change to frontend.src.services.configService can't break frontend.src.components.ModelSettingsModal.
Position
Below the diagonal: frontend.src.services.configService uses a module listed above it, which is the healthy direction.
frontend.src.services.configService uses frontend.src.components.TranscriptSettings, so a change to frontend.src.components.TranscriptSettings can break frontend.src.services.configService, while a change to frontend.src.services.configService can't break frontend.src.components.TranscriptSettings.
Position
Below the diagonal: frontend.src.services.configService uses a module listed above it, which is the healthy direction.
meetily.audio.recording_saver uses meetily.api.api, so a change to meetily.api.api can break meetily.audio.recording_saver, while a change to meetily.audio.recording_saver can't break meetily.api.api.
Position
Below the diagonal: meetily.audio.recording_saver uses a module listed above it, which is the healthy direction.
meetily.audio.recording_state uses meetily.audio.core-old, so a change to meetily.audio.core-old can break meetily.audio.recording_state, while a change to meetily.audio.recording_state can't break meetily.audio.core-old.
Position
Below the diagonal: meetily.audio.recording_state uses a module listed above it, which is the healthy direction.
meetily.audio.stt uses meetily.audio.core-old, so a change to meetily.audio.core-old can break meetily.audio.stt, while a change to meetily.audio.stt can't break meetily.audio.core-old.
Position
Below the diagonal: meetily.audio.stt uses a module listed above it, which is the healthy direction.
meetily.audio.stt uses meetily.audio.vad, so a change to meetily.audio.vad can break meetily.audio.stt, while a change to meetily.audio.stt can't break meetily.audio.vad.
Position
Below the diagonal: meetily.audio.stt uses a module listed above it, which is the healthy direction.
meetily.audio_v2.recorder uses meetily.audio.core-old, so a change to meetily.audio.core-old can break meetily.audio_v2.recorder, while a change to meetily.audio_v2.recorder can't break meetily.audio.core-old.
Position
Below the diagonal: meetily.audio_v2.recorder uses a module listed above it, which is the healthy direction.
23→33 meetily.audio_v2.recorder uses meetily.audio_v2part of a loop✕
Connections
1 pair of types, where a type in meetily.audio_v2.recorder uses a type in meetily.audio_v2.
meetily.audio_v2.recorder uses meetily.audio_v2, so a change to meetily.audio_v2 can break meetily.audio_v2.recorder, while a change to meetily.audio_v2.recorder can't break meetily.audio_v2.
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.
meetily.notifications.manager uses meetily.notifications.types, so a change to meetily.notifications.types can break meetily.notifications.manager, while a change to meetily.notifications.manager can't break meetily.notifications.types.
Position
Below the diagonal: meetily.notifications.manager uses a module listed above it, which is the healthy direction.
meetily.parakeet_engine.parakeet_engine uses meetily.onboarding, so a change to meetily.onboarding can break meetily.parakeet_engine.parakeet_engine, while a change to meetily.parakeet_engine.parakeet_engine can't break meetily.onboarding.
Position
Below the diagonal: meetily.parakeet_engine.parakeet_engine uses a module listed above it, which is the healthy direction.
frontend.src.components uses frontend.src.components.ModelSettingsModal, so a change to frontend.src.components.ModelSettingsModal can break frontend.src.components, while a change to frontend.src.components can't break frontend.src.components.ModelSettingsModal.
Position
Below the diagonal: frontend.src.components uses a module listed above it, which is the healthy direction.
frontend.src.components uses frontend.src.components.TranscriptSettings, so a change to frontend.src.components.TranscriptSettings can break frontend.src.components, while a change to frontend.src.components can't break frontend.src.components.TranscriptSettings.
Position
Below the diagonal: frontend.src.components uses a module listed above it, which is the healthy direction.
frontend.src.components uses frontend.src.components.SettingTabs, so a change to frontend.src.components.SettingTabs can break frontend.src.components, while a change to frontend.src.components can't break frontend.src.components.SettingTabs.
Position
Below the diagonal: frontend.src.components uses a module listed above it, which is the healthy direction.
frontend.src.components.MeetingDetails uses frontend.src.components.MeetingDetails.SummaryPanel, so a change to frontend.src.components.MeetingDetails.SummaryPanel can break frontend.src.components.MeetingDetails, while a change to frontend.src.components.MeetingDetails can't break frontend.src.components.MeetingDetails.SummaryPanel.
Position
Below the diagonal: frontend.src.components.MeetingDetails uses a module listed above it, which is the healthy direction.
frontend.src.hooks.meeting-details uses frontend.src.components.ModelSettingsModal, so a change to frontend.src.components.ModelSettingsModal can break frontend.src.hooks.meeting-details, while a change to frontend.src.hooks.meeting-details can't break frontend.src.components.ModelSettingsModal.
Position
Below the diagonal: frontend.src.hooks.meeting-details uses a module listed above it, which is the healthy direction.
frontend.src.hooks.meeting-details uses frontend.src.types, so a change to frontend.src.types can break frontend.src.hooks.meeting-details, while a change to frontend.src.hooks.meeting-details can't break frontend.src.types.
Position
Below the diagonal: frontend.src.hooks.meeting-details uses a module listed above it, which is the healthy direction.
frontend.src.hooks.meeting-details uses frontend.src.hooks.meeting-details.useSummaryGeneration, so a change to frontend.src.hooks.meeting-details.useSummaryGeneration can break frontend.src.hooks.meeting-details, while a change to frontend.src.hooks.meeting-details can't break frontend.src.hooks.meeting-details.useSummaryGeneration.
Position
Below the diagonal: frontend.src.hooks.meeting-details uses a module listed above it, which is the healthy direction.
frontend.src.lib uses frontend.src.lib.whisper, so a change to frontend.src.lib.whisper can break frontend.src.lib, while a change to frontend.src.lib can't break frontend.src.lib.whisper.
Position
Below the diagonal: frontend.src.lib uses a module listed above it, which is the healthy direction.
frontend.src.lib uses frontend.src.lib.parakeet, so a change to frontend.src.lib.parakeet can break frontend.src.lib, while a change to frontend.src.lib can't break frontend.src.lib.parakeet.
Position
Below the diagonal: frontend.src.lib uses a module listed above it, which is the healthy direction.
meetily.audio.pipeline uses meetily.audio.core-old, so a change to meetily.audio.core-old can break meetily.audio.pipeline, while a change to meetily.audio.pipeline can't break meetily.audio.core-old.
Position
Below the diagonal: meetily.audio.pipeline uses a module listed above it, which is the healthy direction.
meetily.audio.pipeline uses meetily.audio.device_detection, so a change to meetily.audio.device_detection can break meetily.audio.pipeline, while a change to meetily.audio.pipeline can't break meetily.audio.device_detection.
Position
Below the diagonal: meetily.audio.pipeline uses a module listed above it, which is the healthy direction.
meetily.audio.pipeline uses meetily.audio.vad, so a change to meetily.audio.vad can break meetily.audio.pipeline, while a change to meetily.audio.pipeline can't break meetily.audio.vad.
Position
Below the diagonal: meetily.audio.pipeline uses a module listed above it, which is the healthy direction.
meetily.audio.pipeline uses meetily.audio.recording_state, so a change to meetily.audio.recording_state can break meetily.audio.pipeline, while a change to meetily.audio.pipeline can't break meetily.audio.recording_state.
Position
Below the diagonal: meetily.audio.pipeline uses a module listed above it, which is the healthy direction.
meetily.audio.system_audio_stream uses meetily.audio.core-old, so a change to meetily.audio.core-old can break meetily.audio.system_audio_stream, while a change to meetily.audio.system_audio_stream can't break meetily.audio.core-old.
Position
Below the diagonal: meetily.audio.system_audio_stream uses a module listed above it, which is the healthy direction.
meetily.audio.system_audio_stream uses meetily.audio.recording_state, so a change to meetily.audio.recording_state can break meetily.audio.system_audio_stream, while a change to meetily.audio.system_audio_stream can't break meetily.audio.recording_state.
Position
Below the diagonal: meetily.audio.system_audio_stream uses a module listed above it, which is the healthy direction.
meetily.audio.transcription.worker uses meetily.audio.recording_state, so a change to meetily.audio.recording_state can break meetily.audio.transcription.worker, while a change to meetily.audio.transcription.worker can't break meetily.audio.recording_state.
Position
Below the diagonal: meetily.audio.transcription.worker uses a module listed above it, which is the healthy direction.
meetily.audio_v2 uses meetily.audio.core-old, so a change to meetily.audio.core-old can break meetily.audio_v2, while a change to meetily.audio_v2 can't break meetily.audio.core-old.
Position
Below the diagonal: meetily.audio_v2 uses a module listed above it, which is the healthy direction.
meetily.audio_v2 uses meetily.audio_v2.recorder, so a change to meetily.audio_v2.recorder can break meetily.audio_v2, while a change to meetily.audio_v2 can't break meetily.audio_v2.recorder.
Position
Below the diagonal: meetily.audio_v2 uses a module listed above it, which is the healthy direction.
meetily.whisper_engine.whisper_engine uses meetily.onboarding, so a change to meetily.onboarding can break meetily.whisper_engine.whisper_engine, while a change to meetily.whisper_engine.whisper_engine can't break meetily.onboarding.
Position
Below the diagonal: meetily.whisper_engine.whisper_engine uses a module listed above it, which is the healthy direction.
meetily.whisper_engine.whisper_engine uses meetily.parakeet_engine.parakeet_engine, so a change to meetily.parakeet_engine.parakeet_engine can break meetily.whisper_engine.whisper_engine, while a change to meetily.whisper_engine.whisper_engine can't break meetily.parakeet_engine.parakeet_engine.
Position
Below the diagonal: meetily.whisper_engine.whisper_engine uses a module listed above it, which is the healthy direction.
meetily.audio.stream uses meetily.audio.core-old, so a change to meetily.audio.core-old can break meetily.audio.stream, while a change to meetily.audio.stream can't break meetily.audio.core-old.
Position
Below the diagonal: meetily.audio.stream uses a module listed above it, which is the healthy direction.
meetily.audio.stream uses meetily.audio.recording_state, so a change to meetily.audio.recording_state can break meetily.audio.stream, while a change to meetily.audio.stream can't break meetily.audio.recording_state.
Position
Below the diagonal: meetily.audio.stream uses a module listed above it, which is the healthy direction.
meetily.audio.stream uses meetily.audio.pipeline, so a change to meetily.audio.pipeline can break meetily.audio.stream, while a change to meetily.audio.stream can't break meetily.audio.pipeline.
Position
Below the diagonal: meetily.audio.stream uses a module listed above it, which is the healthy direction.
meetily.audio_v2.compatibility uses meetily.audio.recording_saver, so a change to meetily.audio.recording_saver can break meetily.audio_v2.compatibility, while a change to meetily.audio_v2.compatibility can't break meetily.audio.recording_saver.
Position
Below the diagonal: meetily.audio_v2.compatibility uses a module listed above it, which is the healthy direction.
meetily.audio_v2.compatibility uses meetily.audio_v2, so a change to meetily.audio_v2 can break meetily.audio_v2.compatibility, while a change to meetily.audio_v2.compatibility can't break meetily.audio_v2.
Position
Below the diagonal: meetily.audio_v2.compatibility uses a module listed above it, which is the healthy direction.
meetily.whisper_engine.parallel_processor uses meetily.audio.recording_state, so a change to meetily.audio.recording_state can break meetily.whisper_engine.parallel_processor, while a change to meetily.whisper_engine.parallel_processor can't break meetily.audio.recording_state.
Position
Below the diagonal: meetily.whisper_engine.parallel_processor uses a module listed above it, which is the healthy direction.
meetily.whisper_engine.parallel_processor uses meetily.whisper_engine.whisper_engine, so a change to meetily.whisper_engine.whisper_engine can break meetily.whisper_engine.parallel_processor, while a change to meetily.whisper_engine.parallel_processor can't break meetily.whisper_engine.whisper_engine.
Position
Below the diagonal: meetily.whisper_engine.parallel_processor uses a module listed above it, which is the healthy direction.
meetily.audio.recording_manager uses meetily.api.api, so a change to meetily.api.api can break meetily.audio.recording_manager, while a change to meetily.audio.recording_manager can't break meetily.api.api.
Position
Below the diagonal: meetily.audio.recording_manager uses a module listed above it, which is the healthy direction.
meetily.audio.recording_manager uses meetily.audio.core-old, so a change to meetily.audio.core-old can break meetily.audio.recording_manager, while a change to meetily.audio.recording_manager can't break meetily.audio.core-old.
Position
Below the diagonal: meetily.audio.recording_manager uses a module listed above it, which is the healthy direction.
meetily.audio.recording_manager uses meetily.audio.recording_saver, so a change to meetily.audio.recording_saver can break meetily.audio.recording_manager, while a change to meetily.audio.recording_manager can't break meetily.audio.recording_saver.
Position
Below the diagonal: meetily.audio.recording_manager uses a module listed above it, which is the healthy direction.
meetily.audio.recording_manager uses meetily.audio.recording_state, so a change to meetily.audio.recording_state can break meetily.audio.recording_manager, while a change to meetily.audio.recording_manager can't break meetily.audio.recording_state.
Position
Below the diagonal: meetily.audio.recording_manager uses a module listed above it, which is the healthy direction.
meetily.audio.recording_manager uses meetily.audio.pipeline, so a change to meetily.audio.pipeline can break meetily.audio.recording_manager, while a change to meetily.audio.recording_manager can't break meetily.audio.pipeline.
Position
Below the diagonal: meetily.audio.recording_manager uses a module listed above it, which is the healthy direction.
meetily.audio.recording_manager uses meetily.audio.stream, so a change to meetily.audio.stream can break meetily.audio.recording_manager, while a change to meetily.audio.recording_manager can't break meetily.audio.stream.
Position
Below the diagonal: meetily.audio.recording_manager uses a module listed above it, which is the healthy direction.
meetily.audio.recording_commands uses meetily.audio.core-old, so a change to meetily.audio.core-old can break meetily.audio.recording_commands, while a change to meetily.audio.recording_commands can't break meetily.audio.core-old.
Position
Below the diagonal: meetily.audio.recording_commands uses a module listed above it, which is the healthy direction.
meetily.audio.recording_commands uses meetily.audio.recording_state, so a change to meetily.audio.recording_state can break meetily.audio.recording_commands, while a change to meetily.audio.recording_commands can't break meetily.audio.recording_state.
Position
Below the diagonal: meetily.audio.recording_commands uses a module listed above it, which is the healthy direction.
meetily.audio.recording_commands uses meetily.audio.recording_manager, so a change to meetily.audio.recording_manager can break meetily.audio.recording_commands, while a change to meetily.audio.recording_commands can't break meetily.audio.recording_manager.
Position
Below the diagonal: meetily.audio.recording_commands uses a module listed above it, which is the healthy direction.
meetily.lib_old_complex uses meetily.api.api, so a change to meetily.api.api can break meetily.lib_old_complex, while a change to meetily.lib_old_complex can't break meetily.api.api.
Position
Below the diagonal: meetily.lib_old_complex uses a module listed above it, which is the healthy direction.
meetily.lib_old_complex uses meetily.audio.core-old, so a change to meetily.audio.core-old can break meetily.lib_old_complex, while a change to meetily.lib_old_complex can't break meetily.audio.core-old.
Position
Below the diagonal: meetily.lib_old_complex uses a module listed above it, which is the healthy direction.
meetily.lib_old_complex uses meetily.audio.transcription.worker, so a change to meetily.audio.transcription.worker can break meetily.lib_old_complex, while a change to meetily.lib_old_complex can't break meetily.audio.transcription.worker.
Position
Below the diagonal: meetily.lib_old_complex uses a module listed above it, which is the healthy direction.
meetily.lib_old_complex uses meetily.audio.recording_commands, so a change to meetily.audio.recording_commands can break meetily.lib_old_complex, while a change to meetily.lib_old_complex can't break meetily.audio.recording_commands.
Position
Below the diagonal: meetily.lib_old_complex uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 53% · Adequate · gated by D2, 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
144
High / Critical
A03:2025 — Software Supply Chain Failures
68
High / Critical
A02:2025 — Security Misconfiguration
18
High / Critical
Roadmap
First, integrate automated security scanning into the CI pipeline to block regressions and codify disaster recovery procedures with clear RTO/RPO documentation. Next, ensure all outbound HTTP calls include timeouts and retry logic to prevent indefinite hangs, while fixing keyboard accessibility issues in custom controls. Finally, enforce accessibility standards by adding linting and automated testing to the toolchain to catch violations early.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) 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.
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 — 206
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 — 759
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 — 133
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
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. 88 of 88 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 — 88 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, 1046 of 1098 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.
D8 Code Coverage — 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. Coverage NOT MEASURED: test source is present (.ts, .tsx, .rs, .mjs, .js). The coverage collector drives the JavaScript/TypeScript half of this repository's ecosystem, but no collector of ours measures its .rs test suite(s), so no coverage figure covers the repository. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`, or 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. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`, or 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 — a committed report is read whatever runner produced it.
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 44 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 1 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 source is present (.ts, .tsx, .rs, .mjs, .js) and this repository declares a Cargo test suite (repository root, 46 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
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 a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
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.
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. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — time="2026-10-26T02:42:28Z" level=warning msg="The \"MODEL_NAME\" variable is not set. Defaulting to a blank string." time="2026-10-26T02:42:28Z" level=warning msg="The \"MODEL_NAME\" variable is not set. Defaulting to a blank string." time="2026-10-26T02:42:28Z" level=warning msg="The \"MODEL_NAME\" variable is not set. Defaulting to a blank string." no service selected; runtime evidence skipped.
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 Python, Rust, Swift, c, cpp 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 Python, Rust, Swift, c, cpp 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.
R10 Code Duplication — 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. 47 further occurrence(s) are not listed individually; the score already reflects all 87.
R4 Test Coverage — 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. 50 further occurrence(s) are not listed individually; the score already reflects all 90.
R7 Dead Code — 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. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
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.
X4 Structured logging — 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. 141 further occurrence(s) are not listed individually; the score already reflects all 181.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
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 REDACTED, 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 Dockerfile (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.
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.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
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.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of 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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
84 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was index.AISummary at 93. A further 2 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 meetily::summary::processor::language_name_from_code at 32 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: frontend/src-tauri/src/summary/language_detection.rs (meetily::summary::language_detection::summary_code_from_whatlang at 30). 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.
+ 56 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with index.AISummary (cyclomatic 93), RecordingControls.RecordingControls (cyclomatic 84), ModelSettingsModal.ModelSettingsModal (cyclomatic 83). — 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 5 together lifts Cyclomatic Complexity from 4.4 to about 5.3/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.
+ 73 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 20 bodies over 60 down to 60 or less in Cognitive Complexity — start with meetily::lib_old_complex::audio_collection_task (cognitive 193), meetily::audio::core-old::get_windows_device (cognitive 158), meetily::audio::devices::platform::windows::get_windows_device (cognitive 158). — 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 20 together lifts Cognitive Complexity from 2.0 to about 3.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; 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 Classes4.9 / 10Weak✓ 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.
Resolve the 68 FunctionTooLong finding(s) in God Classes — start with REDACTED (3), index.tsx (2), WhisperModelManager.tsx (2). — One of this dimension's main actionable groups (68 warning-level).
Resolve the 16 FileTooLong finding(s) in God Classes — start with index.tsx (2), lib_old_complex.rs, ModelSettingsModal.tsx. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 9 MethodTooLong finding(s) in God Classes — start with pipeline.rs (2), model_manager.rs, parakeet_engine.rs. — One of this dimension's main actionable groups (9 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.
126 duplicated block group(s) detected. A further 13 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .tsx (25% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
+ 51 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with core-old.rs (5), db.py (2), api.rs. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 10 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with stream.rs (2), lib_old_complex.rs (2), commands.rs (2). — One of this dimension's main actionable groups (10 warning-level).
Resolve the 9 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with pipeline.rs (2), sidecar.rs (2), analytics.rs. — One of this dimension's main actionable groups (9 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 · Coupling10.0 / 10Exemplary✓ 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.
3 production modules (Cargo+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
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.
D9 · Test Distribution10.0 / 10Exemplary✓ 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.
296 test methods: 296 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 44 `it`/`test` case(s) across 9 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 252 `#[test]` function(s) across 46 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 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.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ 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, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 44 tests. Measured on the JavaScript/TypeScript suite only — at least 1 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
32 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: anyhow · ×32
What to do
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_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.
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 830 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 3 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry) and package.json, and the licences of those dependency graphs 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: frontend/src-tauri/src/audio/recording_commands.rs (18×28=504); frontend/src/components/RecordingControls.tsx (3×84=252); frontend/src/hooks/meeting-details/useSummaryGeneration.ts (8×29=232) Repeated repair below the complexity floor: frontend/src-tauri/src/audio/vad.rs (6 of 6 changes were fixes); frontend/src-tauri/src/audio/recording_manager.rs (5 of 7 changes were fixes); frontend/src/services/recordingService.ts (5 of 6 changes were fixes)
Resolve the 19 Hotspot finding(s) in Churn × Complexity Hotspots — start with recording_commands.rs, RecordingControls.tsx, useSummaryGeneration.ts. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 7 Repeated repair finding(s) in Churn × Complexity Hotspots — start with vad.rs, recording_manager.rs, recordingService.ts. — One of this dimension's main actionable groups (7 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 Factor8.0 / 10Strong✓ 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.
44 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is llama-helper/src/main.rs. Counted over 215 of the 323 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
Further sole-owners (lower concentration)
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
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.
24 deducted task-comment markers across 72854 LoC (0.0/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.
TodoComment · ×24llama-helper/src/main.rs:150
What to do
Resolve the 24 TodoComment finding(s) in Explicit Debt — start with lib.rs (3), resampler.rs (3), main.rs (2). — One of this dimension's main actionable groups (24 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. 10 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.
2 of 5 build units (Cargo, Python, 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.
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).
144 finding(s): 0 critical, 132 high, 11 medium, 1 low. 59 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 3 file(s) — `backend/build-docker.sh` (line 422), `backend/docker/entrypoint.sh` (line 119), `backend/whisper-custom/server/httplib.h` — 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 7 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
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 48 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (18), REDACTED (12), REDACTED (6). — One of this dimension's main actionable groups (48 issue-level).
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (12 issue-level).
No action in Static Analysis (SAST) — all 59 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 (59 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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 17 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (17 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 10 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 8 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 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.
5 of 215 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is frontend/src-tauri/src/audio/stt.rs. Counted over 215 of the 323 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 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with SummaryPanel.tsx. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 6 Change coupling finding(s) in Change Coupling — start with import.rs, retranscription.rs, AnalyticsProvider.tsx. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with REDACTED. — One of this dimension's main actionable groups (1 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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
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).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — 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 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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 10 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.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels4.6 / 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.
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×17) — frontend/src/app/_components/SettingsModal.tsx:69, frontend/src/app/_components/SettingsModal.tsx:174, frontend/src/app/_components/SettingsModal.tsx:215, …
This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×3) — frontend/src/app/_components/SettingsModal.tsx:90, frontend/src/components/AudioBackendSelector.tsx:94, frontend/src/components/ImportAudio/ImportAudioDialog.tsx:293
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×6) — frontend/src/app/_components/SettingsModal.tsx:94, frontend/src/app/_components/SettingsModal.tsx:114, frontend/src/components/AISummary/index.tsx:663, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×3) — frontend/src/components/AISummary/Block.tsx:235, frontend/src/components/LanguagePickerPopover.tsx:90, frontend/src/components/MeetingDetails/TranscriptPanel.tsx:103
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×7) — frontend/src/components/ImportAudio/ImportAudioDialog.tsx:352, frontend/src/components/ImportAudio/ImportAudioDialog.tsx:384, frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:310, …
This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — frontend/src/components/ModelSettingsModal.tsx:1086, frontend/src/components/TranscriptSettings.tsx:193
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.
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"). — backend/whisper-custom/server/public/index.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — backend/whisper-custom/server/public/index.html:2, frontend/src/app/layout.tsx:234
A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component. — frontend/src/app/layout.tsx:234
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 interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×7) — frontend/src/app/_components/SettingsModal.tsx:137, frontend/src/components/BuiltInModelManager.tsx:300, frontend/src/components/ModelSettingsModal.tsx:992, …
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×3) — frontend/src/components/EditableTitle.tsx:60, frontend/src/components/Sidebar/index.tsx:568, frontend/src/components/Sidebar/index.tsx:726
This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — frontend/src/components/LanguagePickerPopover.tsx:82
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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.
`button` sets color: white on background-color: #007bff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — backend/whisper-custom/server/public/index.html:5
<div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×9) — frontend/src/app/_components/StatusOverlays.tsx:30, frontend/src/components/AISummary/index.tsx:622, frontend/src/components/ChunkProgressDisplay.tsx:224, …
<textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — frontend/src/components/AISummary/Block.tsx:235
This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×3) — frontend/src/components/AudioBackendSelector.tsx:165, frontend/src/components/RecordingControls.tsx:373, frontend/src/components/RecordingControls.tsx:411
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — frontend/src/components/LanguagePickerPopover.tsx:90
`.animate-vibrate` moves (`animation: vibrate 0.3s linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/app/globals.css:32
`.animate-fade-in` moves (`animation: fade-in 0.4s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/app/globals.css:48
`.animate-fade-in-up` moves (`animation: fade-in-up 0.5s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/app/globals.css:64
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-jsx-a11y) 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 115 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-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) 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.
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.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
`SummaryService.process_transcript_background` performs two independent DURABLE writes — a durable state write (`SummaryProcessesRepository.update_process_completed`, :594) and a second independent durable store write — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox). — frontend/src-tauri/src/summary/service.rs:334
What to do
Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
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 a README to the 2 of 3 project(s) that lack one — worth up to 1.3 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 · Observability5.2 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 2/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `frontend`, `llama-helper`.
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.
No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 128238 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
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.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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.
`requests.post(` 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. — backend/debug_cors.py:30
`Client::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. — frontend/src-tauri/src/openrouter/openrouter.rs:43
`reqwest::Client::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. — frontend/src-tauri/src/summary/service.rs:546
What to do
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
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 · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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.
Do you agree with this assessment?
R1 · Type Safety9.7 / 10Exemplary✓ 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.
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.
19 duplicated blocks under frontend/src/ have copies in at least two of the sibling directories app, components, constants, contexts, hooks, services — 11 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 19 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:75
7 duplicated blocks under frontend/src/components/ have copies in at least two of the sibling directories DatabaseImport, ImportAudio, MeetingDetails, Sidebar, onboarding, shared — 6 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — frontend/src/components/ImportAudio/ImportAudioDialog.tsx:203
frontend/src/components/ParakeetModelManager.tsx:16 · frontend/src/components/WhisperModelManager.tsx:18 — the two spans are one implementation copied and then locally edited — 2778 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. — frontend/src/components/ParakeetModelManager.tsx:16
frontend/src/components/ui/dialog.tsx:9 · frontend/src/components/ui/sheet.tsx:10 — the two spans are one implementation copied and then locally edited — 446 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. — frontend/src/components/ui/dialog.tsx:9
frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:267 · frontend/src/components/UpdateDialog.tsx:181 — the two spans are one implementation copied and then locally edited — 409 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. — frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:267
frontend/src/hooks/useRecordingStart.ts:229 · frontend/src/hooks/useRecordingStart.ts:328 — 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. — frontend/src/hooks/useRecordingStart.ts:229
frontend/src/lib/parakeet.ts:162 · frontend/src/lib/whisper.ts:278 — 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. — frontend/src/lib/parakeet.ts:162
frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:75 · frontend/src/hooks/useImportAudio.ts:67 — the two spans are one implementation copied and then locally edited — 261 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. — frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:75
frontend/src/components/ImportAudio/ImportAudioDialog.tsx:203 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:243 — 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. — frontend/src/components/ImportAudio/ImportAudioDialog.tsx:203
frontend/src/components/ImportAudio/ImportAudioDialog.tsx:412 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:361 — 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. — frontend/src/components/ImportAudio/ImportAudioDialog.tsx:412
frontend/src/components/VirtualizedTranscriptView.tsx:300 · frontend/src/components/VirtualizedTranscriptView.tsx:356 — 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. — frontend/src/components/VirtualizedTranscriptView.tsx:300
frontend/src/components/DeviceSelection.tsx:316 · frontend/src/components/DeviceSelection.tsx:384 — 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. — frontend/src/components/DeviceSelection.tsx:316
frontend/src/hooks/meeting-details/useCopyOperations.ts:26 · frontend/src/hooks/meeting-details/useSummaryGeneration.ts:402 — 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. — frontend/src/hooks/meeting-details/useCopyOperations.ts:26
frontend/src/app/_components/SettingsModal.tsx:159 · frontend/src/app/_components/SettingsModal.tsx:200 — 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. — frontend/src/app/_components/SettingsModal.tsx:159
frontend/src/components/Sidebar/index.tsx:161 · frontend/src/components/SummaryModelSettings.tsx:79 — 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. — frontend/src/components/Sidebar/index.tsx:161
frontend/src/components/TranscriptView.tsx:351 · frontend/src/components/VirtualizedTranscriptView.tsx:239 — 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. — frontend/src/components/TranscriptView.tsx:351
frontend/src/components/molecules/form-components/form-input-item.tsx:59 · frontend/src/components/molecules/form-components/form-select-item.tsx:33 — 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. — frontend/src/components/molecules/form-components/form-input-item.tsx:59
frontend/src/components/ui/dropdown-menu.tsx:74 · frontend/src/components/ui/dropdown-menu.tsx:138 — 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. — frontend/src/components/ui/dropdown-menu.tsx:74
frontend/src/components/SummaryModelSettings.tsx:32 · frontend/src/hooks/meeting-details/useModelConfiguration.ts:37 — 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. — frontend/src/components/SummaryModelSettings.tsx:32
frontend/src/services/indexedDBService.ts:343 · frontend/src/services/indexedDBService.ts:393 — 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. — frontend/src/services/indexedDBService.ts:343
frontend/src/components/ImportAudio/ImportAudioDialog.tsx:346 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:304 — 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. — frontend/src/components/ImportAudio/ImportAudioDialog.tsx:346
frontend/src/components/ImportAudio/ImportAudioDialog.tsx:378 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:339 — 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. — frontend/src/components/ImportAudio/ImportAudioDialog.tsx:378
frontend/src/components/Sidebar/index.tsx:457 · frontend/src/components/Sidebar/index.tsx:516 — 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. — frontend/src/components/Sidebar/index.tsx:457
frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:252 · frontend/src/components/shared/DownloadProgressToast.tsx:286 — 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. — frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:252
frontend/src/hooks/useRecordingStart.ts:126 · frontend/src/hooks/useRecordingStart.ts:218 · frontend/src/hooks/useRecordingStart.ts:317 — 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. — frontend/src/hooks/useRecordingStart.ts:126
frontend/src/components/LanguagePickerPopover.tsx:106 · frontend/src/components/LanguagePickerPopover.tsx:152 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend/src/components/LanguagePickerPopover.tsx:106
frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:85 · frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:134 — 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. — frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:85
frontend/src/contexts/OnboardingContext.tsx:112 · frontend/src/contexts/OnboardingContext.tsx:400 — the two spans are one implementation copied and then locally edited — 69 tokens are still identical, in the same order in both spans, 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. — frontend/src/contexts/OnboardingContext.tsx:112
frontend/src/contexts/TranscriptContext.tsx:290 · frontend/src/contexts/TranscriptContext.tsx:409 — the two spans are one implementation copied and then locally edited — 99 tokens are still identical, in the same order in both spans, 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. — frontend/src/contexts/TranscriptContext.tsx:290
frontend/src/components/BuiltInModelManager.tsx:109 · frontend/src/components/BuiltInModelManager.tsx:130 · frontend/src/components/BuiltInModelManager.tsx:150 — all 3 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. — frontend/src/components/BuiltInModelManager.tsx:109
frontend/src/components/BuiltInModelManager.tsx:350 · frontend/src/components/BuiltInModelManager.tsx:379 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend/src/components/BuiltInModelManager.tsx:350
frontend/src/components/ui/select.tsx:35 · frontend/src/components/ui/select.tsx:52 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — frontend/src/components/ui/select.tsx:35
frontend/src/contexts/OllamaDownloadContext.tsx:82 · frontend/src/contexts/OllamaDownloadContext.tsx:110 — 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. — frontend/src/contexts/OllamaDownloadContext.tsx:82
frontend/src/app/settings/page.tsx:38 · frontend/src/contexts/ConfigContext.tsx:201 — 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. — frontend/src/app/settings/page.tsx:38
frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx:66 · frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx:88 — 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. — frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx:66
frontend/src/components/ImportAudio/ImportAudioDialog.tsx:162 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:84 — 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. — frontend/src/components/ImportAudio/ImportAudioDialog.tsx:162
frontend/src/lib/parakeet.ts:96 · frontend/src/lib/whisper.ts:127 — 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. — frontend/src/lib/parakeet.ts:96
frontend/src/lib/parakeet.ts:122 · frontend/src/lib/whisper.ts:142 — 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. — frontend/src/lib/parakeet.ts:122
frontend/src/app/layout.tsx:194 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:181 · frontend/src/hooks/useImportAudio.ts:142 — 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. — frontend/src/app/layout.tsx:194
frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:277 · frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:293 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:277
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.
ModelSettingsModal has cyclomatic complexity 81 and cognitive complexity 72; 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. — frontend/src/components/ModelSettingsModal.tsx:112
(anonymous) has cyclomatic complexity 41 and cognitive complexity 62; 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. — frontend/src/hooks/useRecordingStop.ts:121
handleKeyDown has cyclomatic complexity 35 and cognitive complexity 49; 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. — frontend/src/components/AISummary/Block.tsx:107
RecordingControls has cyclomatic complexity 35 and cognitive complexity 23; 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. — frontend/src/components/RecordingControls.tsx:32
ModelCard has cyclomatic complexity 33 and cognitive complexity 25; 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. — frontend/src/components/ParakeetModelManager.tsx:478
VirtualizedTranscriptView has cyclomatic complexity 33 and cognitive complexity 20; 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. — frontend/src/components/VirtualizedTranscriptView.tsx:113
(anonymous) has cyclomatic complexity 31 and cognitive complexity 29; 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. — scripts/generate-update-manifest-github.js:91
(anonymous) has cyclomatic complexity 31 and cognitive complexity 23; 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. — frontend/src/components/BuiltInModelManager.tsx:290
(anonymous) has cyclomatic complexity 29 and cognitive complexity 44; 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. — frontend/src/hooks/meeting-details/useSummaryGeneration.ts:170
handleSave has cyclomatic complexity 28 and cognitive complexity 30; 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. — frontend/src/components/ModelSettingsModal.tsx:617
ModelCard has cyclomatic complexity 26 and cognitive complexity 23; 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. — frontend/src/components/WhisperModelManager.tsx:577
ImportAudioDialog has cyclomatic complexity 25 and cognitive complexity 21; 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. — frontend/src/components/ImportAudio/ImportAudioDialog.tsx:67
renderItem has cyclomatic complexity 25 and cognitive complexity 20; 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. — frontend/src/components/Sidebar/index.tsx:554
poll has cyclomatic complexity 21 and cognitive complexity 21; 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. — frontend/src/components/Sidebar/SidebarProvider.tsx:216
RetranscribeDialog has cyclomatic complexity 21 and cognitive complexity 15; 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. — frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:54
detectGPU has cyclomatic complexity 20 and cognitive complexity 40; 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. — REDACTED:19
fetchModelConfig has cyclomatic complexity 20 and cognitive complexity 27; 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. — frontend/src/hooks/meeting-details/useModelConfiguration.ts:23
PermissionWarning has cyclomatic complexity 20 and cognitive complexity 17; 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. — frontend/src/components/PermissionWarning.tsx:14
TranscriptSettings has cyclomatic complexity 20 and cognitive complexity 16; 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. — frontend/src/components/TranscriptSettings.tsx:24
(anonymous) has cyclomatic complexity 19 and cognitive complexity 25; 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. — frontend/src/components/SummaryModelSettings.tsx:27
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files6.6 / 10Adequate✓ 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.
frontend/src/components/ModelSettingsModal.tsx has 1287 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/components/ModelSettingsModal.tsx:1
frontend/src/components/Sidebar/index.tsx has 783 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/components/Sidebar/index.tsx:1
frontend/src/lib/analytics.ts has 738 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/lib/analytics.ts:1
frontend/src/components/WhisperModelManager.tsx has 729 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/components/WhisperModelManager.tsx:1
frontend/src/components/AISummary/index.tsx has 725 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/components/AISummary/index.tsx:1
frontend/src/components/ParakeetModelManager.tsx has 629 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/components/ParakeetModelManager.tsx:1
frontend/src/contexts/OnboardingContext.tsx has 577 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/contexts/OnboardingContext.tsx:1
frontend/src/hooks/meeting-details/useSummaryGeneration.ts has 552 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/hooks/meeting-details/useSummaryGeneration.ts:1
frontend/src/components/onboarding/steps/DownloadProgressStep.tsx has 505 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:1
frontend/src/contexts/ConfigContext.tsx has 493 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/contexts/ConfigContext.tsx:1
frontend/src/components/RecordingControls.tsx has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/components/RecordingControls.tsx:1
frontend/src/contexts/TranscriptContext.tsx has 464 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/contexts/TranscriptContext.tsx:1
frontend/src/components/BuiltInModelManager.tsx has 458 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/components/BuiltInModelManager.tsx:1
frontend/src/components/ImportAudio/ImportAudioDialog.tsx has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/components/ImportAudio/ImportAudioDialog.tsx:1
frontend/src/hooks/useRecordingStop.ts has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/hooks/useRecordingStop.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 Coverage4.5 / 10Adequate✓ 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. (×40) — frontend/src/components/Sidebar/index.tsx:1, frontend/src/contexts/OnboardingContext.tsx:1, frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling6.6 / 10Strong✓ 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.
test ✗ · lint ✓ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add a test runner (vitest / jest / playwright) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code5.8 / 10Adequate✓ 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.
Unreachable from the 9 application, 8 tooling and 11 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (9 application, 8 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/hooks/useProcessingProgress.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/src/components/ChunkProgressDisplay.tsx
no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×22) — frontend/src/hooks/useAudioPlayer.ts, frontend/src/hooks/useProcessingProgress.ts, frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx, …
no import path from any entry point (9 application, 8 tooling, 11 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (frontend/src/components/molecules/form-components/form-input-item.tsx, frontend/src/components/molecules/form-components/form-input-switch.tsx, frontend/src/components/molecules/form-components/form-select-item.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/src/components/ui/form.tsx
no import path from any entry point (9 application, 8 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/src/components/DatabaseImport/HomebrewDatabaseDetector.tsx
Nothing imports this binding — it is safe to review for removal. (×10) — frontend/src/components/UpdateCheckProvider.tsx:72, frontend/src/lib/parakeet.ts:38, frontend/src/lib/parakeet.ts:79, …
Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/src/components/onboarding/shared/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/src/components/onboarding/shared/index.ts in the same commit, or the barrel will import a name that no longer exists. — frontend/src/components/onboarding/shared/StatusIndicator.tsx:5
Nothing imports THIS copy of 'getModelIcon' — but frontend/src/lib/whisper.ts:135 in the same directory exports that same name, and it is the copy every import site resolves to. Grepping the name therefore finds live callers that do not reach this binding: it is the dead half of a duplicated pair, left behind when the API moved. Delete it here and keep frontend/src/lib/whisper.ts's, or, if this one is meant to be the survivor, repoint the importers before removing the other. — frontend/src/lib/parakeet.ts:104
Nothing imports THIS copy of 'isQuantizedModel' — but frontend/src/lib/whisper.ts:173 in the same directory exports that same name, and it is the copy every import site resolves to. Grepping the name therefore finds live callers that do not reach this binding: it is the dead half of a duplicated pair, left behind when the API moved. Delete it here and keep frontend/src/lib/whisper.ts's, or, if this one is meant to be the survivor, repoint the importers before removing the other. — frontend/src/lib/parakeet.ts:140
Nothing imports THIS copy of 'getModelPerformanceBadge' — but frontend/src/lib/whisper.ts:178 in the same directory exports that same name, and it is the copy every import site resolves to. Grepping the name therefore finds live callers that do not reach this binding: it is the dead half of a duplicated pair, left behind when the API moved. Delete it here and keep frontend/src/lib/whisper.ts's, or, if this one is meant to be the survivor, repoint the importers before removing the other. — frontend/src/lib/parakeet.ts:145
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
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.
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.
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.
The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception. — backend/app/transcript_processor.py:305
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 document2.7 / 10Weak✓ Tool-verified
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.
`hasVisibleSummaryContent` is exported, takes a document from its caller (line 49) and hands it to `containsReasoningMarker`, which calls itself at line 14 (`containsReasoningMarker`) with a piece of `value` (and at line 26) — and nowhere in `containsReasoningMarker` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `containsReasoningMarker` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — frontend/src/lib/summary-content.ts:14
`hasVisibleSummaryContent` is exported, takes a document from its caller (line 49) and hands it to `hasBlockText`, which calls itself at line 35 (`hasBlockText`) with a piece of `value` (and at line 38) — and nowhere in `hasBlockText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `hasBlockText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — frontend/src/lib/summary-content.ts:35
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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 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 unescaped3.1 / 10Weak✓ Tool-verified
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.
`note.content.split('\n').map(line=>{if(line.startsWith('# ')){return`<h1>${line.slice(2)}</h1>`;}else if(line.startsW…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:174
`line.slice(2)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:176, REDACTED:180
`line.slice(3)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:178
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items 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.
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. (×6) — scripts/generate-update-manifest-github.js:45, frontend/src/lib/summary-language-preferences.ts:47, frontend/src/hooks/useRecentLanguages.ts:46, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — frontend/src/hooks/meeting-details/useSummaryGeneration.ts:378
What to do
Swallowed exception (empty catch)
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.
`error` at line 40 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:40
`info` at line 198 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:198
`error` at line 202 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:202
`error` at line 206 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:206
`error` at line 233 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:233
`error` at line 257 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:257
`warning` at line 269 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:269
`debug` at line 272 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:272
`error` at line 276 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:276
`error` at line 280 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:280
`info` at line 318 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:318
`error` at line 322 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:322
`error` at line 326 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:326
`info` at line 379 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:379
`error` at line 386 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:386
`error` at line 409 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:409
`error` at line 451 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:451
`warning` at line 495 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:495
`error` at line 513 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:513
`info` at line 518 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:518
`error` at line 523 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:523
`error` at line 527 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:527
`info` at line 570 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:570
`error` at line 574 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:574
`error` at line 578 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:578
`info` at line 616 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:616
`error` at line 620 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:620
`error` at line 624 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:624
`info` at line 690 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:690
`error` at line 694 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:694
`error` at line 698 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:698
`info` at line 737 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:737
`error` at line 741 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:741
`error` at line 745 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:745
`error` at line 860 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:860
`error` at line 909 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — backend/app/db.py:909
`error` at line 120 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:120
`info` at line 142 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:142
`info` at line 151 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:151
`error` at line 155 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:155
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.
~0.5 `!` null assertions per 1k TypeScript source lines — 15 assertion(s) across the 31152 source line(s) of the 171 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: frontend/src/services/indexedDBService.ts (10), frontend/src/components/ModelSettingsModal.tsx (1), frontend/src/components/Sidebar/index.tsx (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 12 of 55 WCAG 2.2 Level A/AA success criteria (22%; ≈24% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 43 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.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 24 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 50 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.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — time="2026-10-26T02:42:28Z" level=warning msg="The \"MODEL_NAME\" variable is not set. Defaulting to a blank string." time="2026-10-26T02:42:28Z" level=warning msg="The \"MODEL_NAME\" variable is not set. Defaulting to a blank string." time="2026-10-26T02:42:28Z" level=warning msg="The \"MODEL_NAME\" variable is not set. Defaulting to a blank string." no service selected; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
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 included — the .rs suite was found but not re-run
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, Python, Rust, Swift, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust 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 .py, .rs, .swift, .ts, .tsx, 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) — 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.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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 — no coverage collector for the .rs test suite
DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM5 Encapsulated state — this Rust crate declares no type implementing a hand-rolled Hash/PartialEq, so DM5's value-identity encapsulation read has no population to be taken over
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
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
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
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 Swift code has 21 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
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
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
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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· <button> with no accessible text · ×17
<button> with no accessible text frontend/src/app/_components/SettingsModal.tsx:69— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/app/_components/SettingsModal.tsx:174— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/app/_components/SettingsModal.tsx:215— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/app/_components/SettingsModal.tsx:253— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/AnalyticsDataModal.tsx:24— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/AudioBackendSelector.tsx:98— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/ComplianceNotification.tsx:83— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/DeviceSelection.tsx:298— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/RecordingControls.tsx:347— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/RecordingControls.tsx:373— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/Sidebar/index.tsx:461— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/Sidebar/index.tsx:496— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/Sidebar/index.tsx:511— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/Sidebar/index.tsx:529— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/onboarding/OnboardingContainer.tsx:54— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/onboarding/OnboardingContainer.tsx:67— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text frontend/src/components/onboarding/steps/SetupOverviewStep.tsx:71— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×9
Click handler on a non-interactive <div> frontend/src/app/_components/SettingsModal.tsx:137— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/src/components/BuiltInModelManager.tsx:300— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/src/components/ModelSettingsModal.tsx:992— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/src/components/ModelSettingsModal.tsx:1086— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/src/components/ModelSettingsModal.tsx:1119— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/src/components/ModelSettingsModal.tsx:1315— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> frontend/src/components/Sidebar/index.tsx:568— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> frontend/src/components/Sidebar/index.tsx:726— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> frontend/src/components/TranscriptSettings.tsx:193— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels· <textarea> without a programmatic label · ×5
<textarea> without a programmatic label frontend/src/components/AISummary/Block.tsx:235— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label frontend/src/components/AISummary/index.tsx:663— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label frontend/src/components/BlockNoteEditor/BasicBlockNoteTest.tsx:39— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label frontend/src/components/EditableTitle.tsx:40— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label frontend/src/components/MeetingDetails/TranscriptPanel.tsx:103— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC2 · Forms & labels· <label> that labels no control · ×3
<label> that labels no control frontend/src/app/_components/SettingsModal.tsx:90— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control frontend/src/components/AudioBackendSelector.tsx:94— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control frontend/src/components/ImportAudio/ImportAudioDialog.tsx:293— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC2 · Forms & labels· <select> without a programmatic label · ×3
<select> without a programmatic label frontend/src/app/_components/SettingsModal.tsx:94— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label frontend/src/app/_components/SettingsModal.tsx:114— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label frontend/src/components/LanguageSelection.tsx:186— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· Custom control with no accessible name on <div> · ×2
Custom control with no accessible name on <div> frontend/src/components/ModelSettingsModal.tsx:1086— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> frontend/src/components/TranscriptSettings.tsx:193— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels· <input> without a programmatic label · ×1
<input> without a programmatic label frontend/src/components/LanguagePickerPopover.tsx:90— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<html> without a lang backend/whisper-custom/server/public/index.html:2— 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> frontend/src/app/layout.tsx:234— A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
AC4 · Keyboard semantics· Click handler on a non-interactive <h1> · ×1
Click handler on a non-interactive <h1> frontend/src/components/EditableTitle.tsx:60— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Boundary-crossing change coupling: SummaryPanel.tsx ↔ useSummaryGeneration.ts frontend/src/components/MeetingDetails/SummaryPanel.tsx:1— `frontend/src/components/MeetingDetails/SummaryPanel.tsx` (context components) and `frontend/src/hooks/meeting-details/useSummaryGeneration.ts` (context hooks) sit in DIFFERENT parts of the tree yet change together 73% of the time (11 of the 15 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `03dfb7b2` fix(summary): enforce safe generation lifecycle [skip ci]; `902dfcab` fix(summary): harden Ollama summaries and editor state [skip ci]; `fd38fe99` fix(summary): address PR 455 language persistence follow-up [skip ci] — run `git show` on any of them.
Dual write (no outbox): SummaryService.process_transcript_background frontend/src-tauri/src/summary/service.rs:334— `SummaryService.process_transcript_background` performs two independent DURABLE writes — a durable state write (`SummaryProcessesRepository.update_process_completed`, :594) and a second independent durable store write — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox).
FunctionTooLong: ModelSettingsModal.ModelSettingsModal frontend/src/components/ModelSettingsModal.tsx:112— FunctionTooLong — ModelSettingsModal runs 964 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 864 over it, 9.64× 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: index.Sidebar frontend/src/components/Sidebar/index.tsx:42— FunctionTooLong — Sidebar runs 602 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 502 over it, 6.02× 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: index.AISummary frontend/src/components/AISummary/index.tsx:22— FunctionTooLong — AISummary runs 558 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 458 over it, 5.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: useSummaryGeneration.useSummaryGeneration frontend/src/hooks/meeting-details/useSummaryGeneration.ts:84— FunctionTooLong — useSummaryGeneration runs 391 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 291 over it, 3.91× 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: DownloadProgressStep.DownloadProgressStep frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:26— FunctionTooLong — DownloadProgressStep runs 388 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 288 over it, 3.88× 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: OnboardingContext.OnboardingProvider frontend/src/contexts/OnboardingContext.tsx:77— FunctionTooLong — OnboardingProvider runs 374 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 274 over it, 3.74× 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: RecordingControls.RecordingControls frontend/src/components/RecordingControls.tsx:32— FunctionTooLong — RecordingControls runs 370 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 270 over it, 3.70× 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: WhisperModelManager.ModelManager frontend/src/components/WhisperModelManager.tsx:25— FunctionTooLong — ModelManager runs 361 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 261 over it, 3.61× 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: BuiltInModelManager.BuiltInModelManager frontend/src/components/BuiltInModelManager.tsx:38— FunctionTooLong — BuiltInModelManager runs 329 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 229 over it, 3.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: ImportAudioDialog.ImportAudioDialog frontend/src/components/ImportAudio/ImportAudioDialog.tsx:67— FunctionTooLong — ImportAudioDialog runs 327 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 227 over it, 3.27× 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: meetily::run frontend/src-tauri/src/lib.rs:447— FunctionTooLong — meetily::run runs 317 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 217 over it, 3.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: TranscriptContext.TranscriptProvider frontend/src/contexts/TranscriptContext.tsx:27— FunctionTooLong — TranscriptProvider runs 310 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 210 over it, 3.10× 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: ParakeetModelManager.ParakeetModelManager frontend/src/components/ParakeetModelManager.tsx:23— FunctionTooLong — ParakeetModelManager runs 302 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 202 over it, 3.02× 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: ConfigContext.ConfigProvider frontend/src/contexts/ConfigContext.tsx:100— FunctionTooLong — ConfigProvider runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× 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: RetranscribeDialog.RetranscribeDialog frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:54— FunctionTooLong — RetranscribeDialog runs 289 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 189 over it, 2.89× 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: DeviceSelection.DeviceSelection frontend/src/components/DeviceSelection.tsx:40— FunctionTooLong — DeviceSelection runs 277 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 177 over it, 2.77× 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: SettingsModal.SettingsModals frontend/src/app/_components/SettingsModal.tsx:37— FunctionTooLong — SettingsModals runs 267 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 167 over it, 2.67× 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: useRecordingStop.useRecordingStop frontend/src/hooks/useRecordingStop.ts:40— FunctionTooLong — useRecordingStop runs 264 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 164 over it, 2.64× 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: meetily::audio::recording_commands::stop_recording frontend/src-tauri/src/audio/recording_commands.rs:676— FunctionTooLong — meetily::audio::recording_commands::stop_recording runs 259 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 159 over it, 2.59× 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: useRecordingStart.useRecordingStart frontend/src/hooks/useRecordingStart.ts:43— FunctionTooLong — useRecordingStart runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.52× 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: meetily::audio::import::run_import frontend/src-tauri/src/audio/import.rs:312— FunctionTooLong — meetily::audio::import::run_import runs 232 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 132 over it, 2.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: TranscriptRecovery.TranscriptRecovery frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:34— FunctionTooLong — TranscriptRecovery runs 232 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 132 over it, 2.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: SummaryPanel.SummaryPanel frontend/src/components/MeetingDetails/SummaryPanel.tsx:59— FunctionTooLong — SummaryPanel runs 228 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 128 over it, 2.28× 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: VirtualizedTranscriptView.VirtualizedTranscriptView frontend/src/components/VirtualizedTranscriptView.tsx:113— FunctionTooLong — VirtualizedTranscriptView runs 215 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× 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: meetily::audio::retranscription::run_retranscription frontend/src-tauri/src/audio/retranscription.rs:173— FunctionTooLong — meetily::audio::retranscription::run_retranscription runs 212 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 112 over it, 2.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.
+ 43 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file frontend/src/components/Sidebar/index.tsx: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 frontend/src/contexts/OnboardingContext.tsx: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 frontend/src/components/onboarding/steps/DownloadProgressStep.tsx: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 frontend/src/contexts/TranscriptContext.tsx: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 frontend/src/components/RecordingControls.tsx: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 frontend/src/components/ImportAudio/ImportAudioDialog.tsx: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 frontend/src/hooks/useRecordingStop.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 frontend/src/services/indexedDBService.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 frontend/src/hooks/useRecordingStart.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 frontend/src/components/shared/DownloadProgressToast.tsx: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 frontend/src/app/_components/SettingsModal.tsx: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 frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx: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 frontend/src/components/UpdateDialog.tsx: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 frontend/src/components/ChunkProgressDisplay.tsx: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 frontend/src/app/layout.tsx: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 frontend/src/hooks/useImportAudio.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 frontend/src/hooks/useAudioPlayer.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 frontend/src/components/RecordingSettings.tsx: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 frontend/src/hooks/useProcessingProgress.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 frontend/src/app/page.tsx: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 frontend/src/hooks/useTranscriptRecovery.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 frontend/src/components/AnalyticsConsentSwitch.tsx: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 frontend/src/components/LanguageSelection.tsx: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 frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx: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 frontend/src/components/PreferenceSettings.tsx: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.
meetily::lib_old_complex::audio_collection_task (cognitive 193) frontend/src-tauri/src/lib_old_complex.rs:270— meetily::lib_old_complex::audio_collection_task has cognitive complexity 193 (threshold 15). Drivers by points: if/else 59 (157 pts), loops 7 (17 pts), match/switch 4 (11 pts), boolean chains 8 (nesting depth added 115). 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.
meetily::audio::core-old::get_windows_device (cognitive 158) frontend/src-tauri/src/audio/core-old.rs:699— meetily::audio::core-old::get_windows_device has cognitive complexity 158 (threshold 15). Drivers by points: if/else 30 (114 pts), loops 6 (34 pts), match/switch 2 (6 pts), boolean chains 4 (nesting depth added 116). 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.
meetily::audio::devices::platform::windows::get_windows_device (cognitive 158) frontend/src-tauri/src/audio/devices/platform/windows.rs:97— meetily::audio::devices::platform::windows::get_windows_device has cognitive complexity 158 (threshold 15). Drivers by points: if/else 30 (114 pts), loops 6 (34 pts), match/switch 2 (6 pts), boolean chains 4 (nesting depth added 116). 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.
meetily::lib_old_complex::transcription_worker (cognitive 128) frontend/src-tauri/src/lib_old_complex.rs:859— meetily::lib_old_complex::transcription_worker has cognitive complexity 128 (threshold 15). Drivers by points: if/else 48 (117 pts), loops 2 (5 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 74). 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.
meetily::audio::transcription::worker::start_transcription_task (cognitive 92) frontend/src-tauri/src/audio/transcription/worker.rs:51— meetily::audio::transcription::worker::start_transcription_task has cognitive complexity 92 (threshold 15). Drivers by points: if/else 21 (58 pts), match/switch 7 (27 pts), loops 5 (6 pts), boolean chains 1 (nesting depth added 58). 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.
meetily::lib_old_complex::whisper_rs_transcription_worker (cognitive 79) frontend/src-tauri/src/lib_old_complex.rs:1112— meetily::lib_old_complex::whisper_rs_transcription_worker has cognitive complexity 79 (threshold 15). Drivers by points: if/else 28 (70 pts), loops 2 (5 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 47). 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.
meetily::summary::templates::loader::list_template_ids (cognitive 64) frontend/src-tauri/src/summary/templates/loader.rs:142— meetily::summary::templates::loader::list_template_ids has cognitive complexity 64 (threshold 15). Drivers by points: if/else 11 (48 pts), loops 2 (9 pts), match/switch 2 (7 pts) (nesting depth added 49). 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.
meetily::lib_old_complex::stop_recording (cognitive 61) frontend/src-tauri/src/lib_old_complex.rs:1480— meetily::lib_old_complex::stop_recording has cognitive complexity 61 (threshold 15). Drivers by points: if/else 30 (57 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 29). 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.
meetily::audio::core-old::configure_windows_audio (cognitive 54) frontend/src-tauri/src/audio/core-old.rs:118— meetily::audio::core-old::configure_windows_audio has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (42 pts), loops 4 (12 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.
meetily::audio::devices::platform::windows::configure_windows_audio (cognitive 54) frontend/src-tauri/src/audio/devices/platform/windows.rs:8— meetily::audio::devices::platform::windows::configure_windows_audio has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (42 pts), loops 4 (12 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.
meetily::audio::recording_commands::stop_recording (cognitive 45) frontend/src-tauri/src/audio/recording_commands.rs:676— meetily::audio::recording_commands::stop_recording has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (28 pts), match/switch 9 (14 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 13). Of this number, 41 points are the body's own statements and 4 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.
meetily::api::api::api_test_custom_openai_connection (cognitive 44) frontend/src-tauri/src/api/api.rs:1274— meetily::api::api::api_test_custom_openai_connection has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (39 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 29). 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.
meetily::summary::processor::generate_meeting_summary (cognitive 42) frontend/src-tauri/src/summary/processor.rs:364— meetily::summary::processor::generate_meeting_summary has cognitive complexity 42 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 3 (11 pts), loops 2 (7 pts), boolean chains 5 (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.
meetily::audio::import::run_import (cognitive 38) frontend/src-tauri/src/audio/import.rs:312— meetily::audio::import::run_import has cognitive complexity 38 (threshold 15). Drivers by points: if/else 26 (32 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 7). 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.
meetily::audio::ffmpeg::find_ffmpeg_path_internal (cognitive 35) frontend/src-tauri/src/audio/ffmpeg.rs:24— meetily::audio::ffmpeg::find_ffmpeg_path_internal has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (31 pts), boolean chains 2, loops 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.
meetily::audio::transcription::engine::get_or_init_whisper (cognitive 35) frontend/src-tauri/src/audio/transcription/engine.rs:225— meetily::audio::transcription::engine::get_or_init_whisper has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (26 pts), match/switch 4 (7 pts), boolean chains 1, loops 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.
meetily::ollama::ollama::pull_ollama_model (cognitive 35) frontend/src-tauri/src/ollama/ollama.rs:260— meetily::ollama::ollama::pull_ollama_model has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 20). 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.
meetily::audio::decoder::decode_audio_file_with_progress (cognitive 34) frontend/src-tauri/src/audio/decoder.rs:397— meetily::audio::decoder::decode_audio_file_with_progress has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (28 pts), match/switch 2 (4 pts), boolean chains 1, loops 1 (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.
meetily::audio::retranscription::run_retranscription (cognitive 34) frontend/src-tauri/src/audio/retranscription.rs:173— meetily::audio::retranscription::run_retranscription has cognitive complexity 34 (threshold 15). Drivers by points: if/else 23 (29 pts), loops 4 (5 pts) (nesting depth added 7). 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.
meetily::run (cognitive 31) frontend/src-tauri/src/lib.rs:447— meetily::run has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (25 pts), match/switch 5 (6 pts) (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.
meetily::audio::decoder::chunked_resample_with_progress (cognitive 31) frontend/src-tauri/src/audio/decoder.rs:126— meetily::audio::decoder::chunked_resample_with_progress has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 3 (7 pts), boolean chains 2, match/switch 1 (2 pts) (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.
meetily::audio::core-old::list_audio_devices (cognitive 30) frontend/src-tauri/src/audio/core-old.rs:235— meetily::audio::core-old::list_audio_devices has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 16). Of this number, 29 points are the body's own statements and 1 belongs 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.
meetily::lib_old_complex::start_recording (cognitive 30) frontend/src-tauri/src/lib_old_complex.rs:1307— meetily::lib_old_complex::start_recording has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (23 pts), loops 2 (4 pts), match/switch 2 (3 pts) (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.
meetily::summary::llm_client::generate_summary (cognitive 30) frontend/src-tauri/src/summary/llm_client.rs:259— meetily::summary::llm_client::generate_summary has cognitive complexity 30 (threshold 15). Drivers by points: if/else 20 (26 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 7). 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.
meetily::audio::recording_commands::trigger_mic_fallback_to_default (cognitive 29) frontend/src-tauri/src/audio/recording_commands.rs:1483— meetily::audio::recording_commands::trigger_mic_fallback_to_default has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (23 pts), match/switch 4 (6 pts) (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.
TodoComment llama-helper/src/main.rs:150— /// TODO: Vulkan VRAM detection — 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 llama-helper/src/main.rs:264— // TODO: Use actual model metadata instead of heuristics — 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 frontend/src-tauri/src/lib_old_complex.rs:1357— // TODO:Calling discover_models as workaround for updating the available_models, whihch is used in — 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 frontend/src-tauri/src/whisper_engine/parallel_processor.rs:363— // TODO: Add confidence scoring if available — 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 frontend/src-tauri/src/whisper_engine/system_monitor.rs:113— // TODO: Implement platform-specific temperature reading if needed — 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 frontend/src-tauri/src/audio_v2/compatibility.rs:86— // TODO: Return a sender for the modern system — 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 frontend/src-tauri/src/audio_v2/compatibility.rs:177— // TODO: Implement quality metrics — 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 frontend/src-tauri/src/audio_v2/lib.rs:94— // TODO: Implement initialization — 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 frontend/src-tauri/src/audio_v2/lib.rs:101— // TODO: Implement recording start — 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 frontend/src-tauri/src/audio_v2/lib.rs:108— // TODO: Implement recording stop — 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 frontend/src-tauri/src/audio_v2/limiter.rs:8— // TODO: Implement in Phase 3 — 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 frontend/src-tauri/src/audio_v2/resampler.rs:10— // TODO: Implement in Phase 3 — 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 frontend/src-tauri/src/audio_v2/limiter.rs:20— // TODO: Implement lookahead limiting in Phase 3 — 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 frontend/src-tauri/src/audio_v2/normalizer.rs:11— // TODO: Add EBU R128 analyzer when dependencies are available — 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 frontend/src-tauri/src/audio_v2/normalizer.rs:26— // TODO: Implement EBU R128 normalization when ebur128 dependency is available — 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 frontend/src-tauri/src/audio_v2/recorder.rs:139— // TODO: Send to transcription system — 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 frontend/src-tauri/src/audio_v2/recorder.rs:163— // TODO: Implement file saving — 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 frontend/src-tauri/src/audio_v2/resampler.rs:22— // TODO: Implement rate change handling in Phase 3 — 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 frontend/src-tauri/src/audio_v2/resampler.rs:27— // TODO: Implement dynamic resampling in Phase 3 — 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 frontend/src-tauri/src/audio_v2/sync.rs:19— // TODO: Implement in Phase 4 — 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 frontend/src-tauri/src/audio_v2/sync.rs:31— // TODO: Implement timestamp-based synchronization in Phase 4 — 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 frontend/src-tauri/src/audio/stt.rs:128— // TODO --optimize — 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 frontend/src-tauri/src/audio/system_audio_commands.rs:17— // TODO: Store the stream in global state if needed for management — 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 frontend/src-tauri/src/audio/capture/microphone.rs:2— // TODO: Extract microphone AudioStream logic from core.rs — 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.
meetily::lib_old_complex::audio_collection_task (cyclomatic 68) frontend/src-tauri/src/lib_old_complex.rs:270— meetily::lib_old_complex::audio_collection_task has cyclomatic complexity 68 (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.
meetily::audio::core-old::get_windows_device (cyclomatic 38) frontend/src-tauri/src/audio/core-old.rs:699— meetily::audio::core-old::get_windows_device has cyclomatic complexity 38 (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.
meetily::audio::devices::platform::windows::get_windows_device (cyclomatic 38) frontend/src-tauri/src/audio/devices/platform/windows.rs:97— meetily::audio::devices::platform::windows::get_windows_device has cyclomatic complexity 38 (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.
meetily::lib_old_complex::transcription_worker (cyclomatic 38) frontend/src-tauri/src/lib_old_complex.rs:859— meetily::lib_old_complex::transcription_worker has cyclomatic complexity 38 (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.
meetily::audio::transcription::worker::start_transcription_task (cyclomatic 30) frontend/src-tauri/src/audio/transcription/worker.rs:51— meetily::audio::transcription::worker::start_transcription_task 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.
meetily::audio::recording_commands::stop_recording (cyclomatic 28) frontend/src-tauri/src/audio/recording_commands.rs:676— meetily::audio::recording_commands::stop_recording has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong 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.
meetily::audio::import::run_import (cyclomatic 26) frontend/src-tauri/src/audio/import.rs:312— meetily::audio::import::run_import has cyclomatic complexity 26 (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.
meetily::lib_old_complex::whisper_rs_transcription_worker (cyclomatic 25) frontend/src-tauri/src/lib_old_complex.rs:1112— meetily::lib_old_complex::whisper_rs_transcription_worker 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.
meetily::lib_old_complex::stop_recording (cyclomatic 25) frontend/src-tauri/src/lib_old_complex.rs:1480— meetily::lib_old_complex::stop_recording 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.
meetily::audio::retranscription::run_retranscription (cyclomatic 22) frontend/src-tauri/src/audio/retranscription.rs:173— meetily::audio::retranscription::run_retranscription has cyclomatic complexity 22 (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.
meetily::summary::llm_client::generate_summary (cyclomatic 22) frontend/src-tauri/src/summary/llm_client.rs:259— meetily::summary::llm_client::generate_summary has cyclomatic complexity 22 (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.
meetily::audio::transcription::engine::get_or_init_whisper (cyclomatic 21) frontend/src-tauri/src/audio/transcription/engine.rs:225— meetily::audio::transcription::engine::get_or_init_whisper has cyclomatic complexity 21 (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.
meetily::summary::processor::generate_meeting_summary (cyclomatic 21) frontend/src-tauri/src/summary/processor.rs:364— meetily::summary::processor::generate_meeting_summary has cyclomatic complexity 21 (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: meetily::summary::processor::language_name_from_code (cyclomatic 32) 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.
meetily::audio::core-old::configure_windows_audio (cyclomatic 20) frontend/src-tauri/src/audio/core-old.rs:118— meetily::audio::core-old::configure_windows_audio 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.
meetily::audio::devices::platform::windows::configure_windows_audio (cyclomatic 20) frontend/src-tauri/src/audio/devices/platform/windows.rs:8— meetily::audio::devices::platform::windows::configure_windows_audio 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.
meetily::audio::ffmpeg::find_ffmpeg_path_internal (cyclomatic 20) frontend/src-tauri/src/audio/ffmpeg.rs:24— meetily::audio::ffmpeg::find_ffmpeg_path_internal 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.
meetily::run (cyclomatic 19) frontend/src-tauri/src/lib.rs:447— meetily::run 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.
meetily::audio::recording_commands::trigger_mic_fallback_to_default (cyclomatic 19) frontend/src-tauri/src/audio/recording_commands.rs:1483— meetily::audio::recording_commands::trigger_mic_fallback_to_default 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.
meetily::audio::decoder::decode_audio_file_with_progress (cyclomatic 17) frontend/src-tauri/src/audio/decoder.rs:397— meetily::audio::decoder::decode_audio_file_with_progress 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.
meetily::lib_old_complex::start_recording (cyclomatic 17) frontend/src-tauri/src/lib_old_complex.rs:1307— meetily::lib_old_complex::start_recording 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.
meetily::summary::templates::loader::list_template_ids (cyclomatic 16) frontend/src-tauri/src/summary/templates/loader.rs:142— meetily::summary::templates::loader::list_template_ids 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.
Hotspot: frontend/src-tauri/src/audio/recording_commands.rs frontend/src-tauri/src/audio/recording_commands.rs:676— frontend/src-tauri/src/audio/recording_commands.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in meetily::audio::recording_commands::stop_recording at line 676. 14 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/recording_commands.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: frontend/src/components/RecordingControls.tsx frontend/src/components/RecordingControls.tsx:32— frontend/src/components/RecordingControls.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 84 in RecordingControls.RecordingControls at line 32. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/components/RecordingControls.tsx`: 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: frontend/src/hooks/meeting-details/useSummaryGeneration.ts frontend/src/hooks/meeting-details/useSummaryGeneration.ts:170— frontend/src/hooks/meeting-details/useSummaryGeneration.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in useSummaryGeneration.useSummaryGeneration.handlePollingResult at line 170. 7 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/hooks/meeting-details/useSummaryGeneration.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.
Hotspot: frontend/src/components/ParakeetModelManager.tsx frontend/src/components/ParakeetModelManager.tsx:23— frontend/src/components/ParakeetModelManager.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in ParakeetModelManager.ParakeetModelManager at line 23. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/components/ParakeetModelManager.tsx`: 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: frontend/src-tauri/src/summary/llm_client.rs frontend/src-tauri/src/summary/llm_client.rs:259— frontend/src-tauri/src/summary/llm_client.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in meetily::summary::llm_client::generate_summary at line 259. 7 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src-tauri/src/summary/llm_client.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: frontend/src-tauri/src/summary/processor.rs frontend/src-tauri/src/summary/processor.rs:364— frontend/src-tauri/src/summary/processor.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in meetily::summary::processor::generate_meeting_summary at line 364. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src-tauri/src/summary/processor.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: frontend/src/app/meeting-details/page.tsx frontend/src/app/meeting-details/page.tsx:23— frontend/src/app/meeting-details/page.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in page.MeetingDetailsContent at line 23. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/app/meeting-details/page.tsx`: 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: frontend/src-tauri/src/whisper_engine/whisper_engine.rs frontend/src-tauri/src/whisper_engine/whisper_engine.rs:948— frontend/src-tauri/src/whisper_engine/whisper_engine.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in WhisperEngine::finish_download at line 948. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src-tauri/src/whisper_engine/whisper_engine.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: frontend/src/components/MeetingDetails/SummaryPanel.tsx frontend/src/components/MeetingDetails/SummaryPanel.tsx:59— frontend/src/components/MeetingDetails/SummaryPanel.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in SummaryPanel.SummaryPanel at line 59. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/components/MeetingDetails/SummaryPanel.tsx`: 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: frontend/src/components/WhisperModelManager.tsx frontend/src/components/WhisperModelManager.tsx:25— frontend/src/components/WhisperModelManager.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in WhisperModelManager.ModelManager at line 25. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/components/WhisperModelManager.tsx`: 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: frontend/src/hooks/useRecordingStart.ts frontend/src/hooks/useRecordingStart.ts:43— frontend/src/hooks/useRecordingStart.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in useRecordingStart.useRecordingStart at line 43. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/hooks/useRecordingStart.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.
Hotspot: frontend/src/components/Sidebar/SidebarProvider.tsx frontend/src/components/Sidebar/SidebarProvider.tsx:78— frontend/src/components/Sidebar/SidebarProvider.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in SidebarProvider.SidebarProvider at line 78. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/components/Sidebar/SidebarProvider.tsx`: 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: frontend/src-tauri/src/summary/service.rs frontend/src-tauri/src/summary/service.rs:334— frontend/src-tauri/src/summary/service.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in SummaryService::process_transcript_background at line 334. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src-tauri/src/summary/service.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: frontend/src/contexts/RecordingStateContext.tsx frontend/src/contexts/RecordingStateContext.tsx:61— frontend/src/contexts/RecordingStateContext.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in RecordingStateContext.RecordingStateProvider at line 61. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/contexts/RecordingStateContext.tsx`: 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: frontend/src-tauri/src/audio/transcription/worker.rs frontend/src-tauri/src/audio/transcription/worker.rs:51— frontend/src-tauri/src/audio/transcription/worker.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in meetily::audio::transcription::worker::start_transcription_task at line 51. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/transcription/worker.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: frontend/src-tauri/src/lib.rs frontend/src-tauri/src/lib.rs:447— frontend/src-tauri/src/lib.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in meetily::run at line 447. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src-tauri/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: frontend/src-tauri/src/audio/device_monitor.rs frontend/src-tauri/src/audio/device_monitor.rs:272— frontend/src-tauri/src/audio/device_monitor.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in AudioDeviceMonitor::monitor_loop at line 272. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/device_monitor.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: frontend/src/hooks/meeting-details/useCopyOperations.ts frontend/src/hooks/meeting-details/useCopyOperations.ts:109— frontend/src/hooks/meeting-details/useCopyOperations.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in useCopyOperations.useCopyOperations.handleCopySummary at line 109. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/hooks/meeting-details/useCopyOperations.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.
Hotspot: frontend/src/components/RecordingSettings.tsx frontend/src/components/RecordingSettings.tsx:23— frontend/src/components/RecordingSettings.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in RecordingSettings.RecordingSettings at line 23. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/components/RecordingSettings.tsx`: 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.
FileTooLong: src/lib_old_complex.rs frontend/src-tauri/src/lib_old_complex.rs— FileTooLong — 1458 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 48 free functions. The bar is 500 significant lines; this is 958 over it, 2.92× 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: components/ModelSettingsModal.tsx frontend/src/components/ModelSettingsModal.tsx— FileTooLong — 1052 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: ModelSettingsModal (112-1408). The bar is 500 significant lines; this is 552 over it, 2.10× 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: api/api.rs frontend/src-tauri/src/api/api.rs— FileTooLong — 953 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 453 over it, 1.91× 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: audio/recording_commands.rs frontend/src-tauri/src/audio/recording_commands.rs— FileTooLong — 916 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 416 over it, 1.83× 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: parakeet_engine/parakeet_engine.rs frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs— FileTooLong — 812 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 79% of them inside a single declaration: ParakeetEngine (263-1230). The bar is 500 significant lines; this is 312 over it, 1.62× 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: whisper_engine/whisper_engine.rs frontend/src-tauri/src/whisper_engine/whisper_engine.rs— FileTooLong — 734 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 234 over it, 1.47× 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: Sidebar/index.tsx frontend/src/components/Sidebar/index.tsx— FileTooLong — 638 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: Sidebar (42-880). The bar is 500 significant lines; this is 138 over it, 1.28× 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: audio/import.rs frontend/src-tauri/src/audio/import.rs— FileTooLong — 630 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 130 over it, 1.26× 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: audio/pipeline.rs frontend/src-tauri/src/audio/pipeline.rs— FileTooLong — 603 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 103 over it, 1.21× 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: components/WhisperModelManager.tsx frontend/src/components/WhisperModelManager.tsx— FileTooLong — 597 significant lines (blank, comment-only and punctuation-only lines excluded), about 60% of them inside a single declaration: ModelManager (25-561). The bar is 500 significant lines; this is 97 over it, 1.19× 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 frontend/src-tauri/src/lib.rs— FileTooLong — 590 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 90 over it, 1.18× 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: AISummary/index.tsx frontend/src/components/AISummary/index.tsx— FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: AISummary (22-821). The bar is 500 significant lines; this is 74 over it, 1.15× 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: audio/core-old.rs frontend/src-tauri/src/audio/core-old.rs— FileTooLong — 563 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 63 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: lib/analytics.ts frontend/src/lib/analytics.ts— FileTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: Analytics (21-855). The bar is 500 significant lines; this is 58 over it, 1.12× 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: audio/retranscription.rs frontend/src-tauri/src/audio/retranscription.rs— FileTooLong — 520 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 20 over it, 1.04× 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: components/ParakeetModelManager.tsx frontend/src/components/ParakeetModelManager.tsx— FileTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 17 over it, 1.03× 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.
Duplicated block (11 lines × 2) frontend/src-tauri/src/api/api.rs:872— frontend/src-tauri/src/api/api.rs:872-882 | frontend/src-tauri/src/database/repositories/meeting.rs:86-96 — 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) frontend/src-tauri/src/audio/core-old.rs:131— frontend/src-tauri/src/audio/core-old.rs:131-141 | frontend/src-tauri/src/audio/devices/platform/windows.rs:21-31 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/platform/windows.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 115 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) frontend/src-tauri/src/audio/core-old.rs:161— frontend/src-tauri/src/audio/core-old.rs:161-171 | frontend/src-tauri/src/audio/devices/platform/windows.rs:51-61 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/platform/windows.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 115 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) frontend/src-tauri/src/audio/core-old.rs:285— frontend/src-tauri/src/audio/core-old.rs:285-295 | frontend/src-tauri/src/audio/devices/discovery.rs:32-42 — 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) frontend/src-tauri/src/audio/core-old.rs:780— frontend/src-tauri/src/audio/core-old.rs:780-790 | frontend/src-tauri/src/audio/devices/platform/windows.rs:178-188 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/platform/windows.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 115 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) frontend/src-tauri/src/audio/pipeline.rs:867— frontend/src-tauri/src/audio/pipeline.rs:867-877 | frontend/src-tauri/src/audio/pipeline.rs:937-947 — 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 (11 lines × 2) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:890— frontend/src-tauri/src/whisper_engine/whisper_engine.rs:890-900 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:912-922 — 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 (11 lines × 2) frontend/src-tauri/src/audio/core-old.rs:99— frontend/src-tauri/src/audio/core-old.rs:99-109 | frontend/src-tauri/src/audio/devices/configuration.rs:92-102 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/configuration.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 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) frontend/src-tauri/src/database/repositories/meeting.rs:211— frontend/src-tauri/src/database/repositories/meeting.rs:211-223 | frontend/src-tauri/src/database/repositories/summary.rs:52-62 — 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) frontend/src-tauri/src/parakeet_engine/commands.rs:78— frontend/src-tauri/src/parakeet_engine/commands.rs:78-88 | frontend/src-tauri/src/whisper_engine/commands.rs:133-143 — `frontend/src-tauri/src/parakeet_engine/commands.rs` and `frontend/src-tauri/src/whisper_engine/commands.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 7 separate duplicated blocks between them, totalling at least 93 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) frontend/src-tauri/src/audio/import.rs:767— frontend/src-tauri/src/audio/import.rs:767-777 | frontend/src-tauri/src/audio/import.rs:813-823 — 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 (11 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:853— frontend/src-tauri/src/audio/recording_commands.rs:853-863 | frontend/src-tauri/src/audio/recording_commands.rs:879-889 — 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 (11 lines × 2) frontend/src-tauri/src/lib_old_complex.rs:1097— frontend/src-tauri/src/lib_old_complex.rs:1097-1107 | frontend/src-tauri/src/lib_old_complex.rs:1291-1301 — 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 (11 lines × 2) backend/app/db.py:569— backend/app/db.py:569-579 | backend/app/db.py:689-699 — 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 (11 lines × 2) backend/app/db.py:633— backend/app/db.py:633-643 | backend/app/db.py:757-767 — 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×13
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×12
Animation without a prefers-reduced-motion guard frontend/src/app/_components/StatusOverlays.tsx:30— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/components/AISummary/index.tsx:622— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/components/ChunkProgressDisplay.tsx:224— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/components/MeetingDetails/SummaryPanel.tsx:285— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/components/ModelDownloadProgress.tsx:23— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/components/RecordingControls.tsx:340— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/components/RecordingControls.tsx:396— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/components/VirtualizedTranscriptView.tsx:310— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/components/VirtualizedTranscriptView.tsx:366— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/app/globals.css:32— `.animate-vibrate` moves (`animation: vibrate 0.3s linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/app/globals.css:48— `.animate-fade-in` moves (`animation: fade-in 0.4s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/app/globals.css:64— `.animate-fade-in-up` moves (`animation: fade-in-up 0.5s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D30 · Dependency Vulnerabilities· Medium CVE · ×12
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×11
Duplicated block (9 lines × 2) frontend/src-tauri/src/audio_v2/stream.rs:389— frontend/src-tauri/src/audio_v2/stream.rs:389-397 | frontend/src-tauri/src/audio_v2/stream.rs:401-409 — 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) frontend/src-tauri/src/lib.rs:226— frontend/src-tauri/src/lib.rs:226-234 | frontend/src-tauri/src/lib_old_complex.rs:1700-1708 — 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) frontend/src-tauri/src/lib_old_complex.rs:217— frontend/src-tauri/src/lib_old_complex.rs:217-225 | frontend/src-tauri/src/lib_old_complex.rs:251-259 — 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) frontend/src-tauri/src/lib_old_complex.rs:2305— frontend/src-tauri/src/lib_old_complex.rs:2305-2313 | frontend/src-tauri/src/whisper_engine/commands.rs:449-461 — 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) frontend/src-tauri/src/parakeet_engine/commands.rs:180— frontend/src-tauri/src/parakeet_engine/commands.rs:180-188 | frontend/src-tauri/src/parakeet_engine/commands.rs:233-241 — 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) frontend/src-tauri/src/whisper_engine/commands.rs:235— frontend/src-tauri/src/whisper_engine/commands.rs:235-243 | frontend/src-tauri/src/whisper_engine/commands.rs:283-291 — 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) frontend/src-tauri/src/ollama/ollama.rs:299— frontend/src-tauri/src/ollama/ollama.rs:299-307 | frontend/src-tauri/src/ollama/ollama.rs:459-467 — 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) frontend/src-tauri/src/audio/stream.rs:436— frontend/src-tauri/src/audio/stream.rs:436-444 | frontend/src-tauri/src/audio_v2/stream.rs:315-323 — `frontend/src-tauri/src/audio/stream.rs` and `frontend/src-tauri/src/audio_v2/stream.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 90 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) frontend/src-tauri/src/audio/devices/platform/windows.rs:133— frontend/src-tauri/src/audio/devices/platform/windows.rs:133-141 | frontend/src-tauri/src/audio/devices/platform/windows.rs:198-206 — 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) frontend/src-tauri/src/audio/recording_commands.rs:1298— frontend/src-tauri/src/audio/recording_commands.rs:1298-1306 | frontend/src-tauri/src/audio/recording_commands.rs:1313-1321 — 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.
MethodTooLong: ModelManager.download_model_detailed frontend/src-tauri/src/summary/summary_engine/model_manager.rs:351— MethodTooLong — download_model_detailed runs 233 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 133 over it, 2.33× 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: ParakeetEngine.download_artifacts frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:849— MethodTooLong — download_artifacts runs 222 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 122 over it, 2.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.
MethodTooLong: SummaryService.process_transcript_background frontend/src-tauri/src/summary/service.rs:334— MethodTooLong — process_transcript_background runs 218 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 118 over it, 2.18× 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: AudioStream.from_device frontend/src-tauri/src/audio/core-old.rs:396— MethodTooLong — from_device 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: MacOSSystemAudioDetector.start frontend/src-tauri/src/audio/system_detector.rs:130— MethodTooLong — start 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.
MethodTooLong: ModelState.generate llama-helper/src/main.rs:348— MethodTooLong — generate runs 135 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 35 over it, 1.35× 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: AudioCapture.process_audio_data frontend/src-tauri/src/audio/pipeline.rs:399— MethodTooLong — process_audio_data 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.
MethodTooLong: AudioCapture.new frontend/src-tauri/src/audio/pipeline.rs:230— MethodTooLong — new runs 114 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 14 over it, 1.14× 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: SidecarManager.resolve_helper_binary frontend/src-tauri/src/summary/summary_engine/sidecar.rs:108— MethodTooLong — resolve_helper_binary runs 101 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 1 over it, 1.01× 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 (5 lines × 2) frontend/src-tauri/src/analytics/analytics.rs:256— frontend/src-tauri/src/analytics/analytics.rs:256-260 | frontend/src-tauri/src/analytics/analytics.rs:314-318 — 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) frontend/src-tauri/src/audio/pipeline.rs:422— frontend/src-tauri/src/audio/pipeline.rs:422-426 | frontend/src-tauri/src/audio/pipeline.rs:492-496 — 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) frontend/src-tauri/src/audio/pipeline.rs:492— frontend/src-tauri/src/audio/pipeline.rs:492-496 | frontend/src-tauri/src/audio_v2/mixer.rs:155-159 — 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) frontend/src-tauri/src/audio_v2/mixer.rs:74— frontend/src-tauri/src/audio_v2/mixer.rs:74-78 | frontend/src-tauri/src/audio_v2/mixer.rs:87-91 — 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) frontend/src-tauri/src/summary/summary_engine/sidecar.rs:127— frontend/src-tauri/src/summary/summary_engine/sidecar.rs:127-131 | frontend/src-tauri/src/summary/summary_engine/sidecar.rs:183-188 — 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) frontend/src-tauri/src/summary/summary_engine/sidecar.rs:422— frontend/src-tauri/src/summary/summary_engine/sidecar.rs:422-426 | frontend/src-tauri/src/summary/summary_engine/sidecar.rs:488-492 — 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) frontend/src-tauri/src/whisper_engine/commands.rs:91— frontend/src-tauri/src/whisper_engine/commands.rs:91-95 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:216-221 — 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 (5 lines × 2) frontend/src-tauri/src/audio/recording_manager.rs:248— frontend/src-tauri/src/audio/recording_manager.rs:248-252 | frontend/src-tauri/src/audio/recording_manager.rs:255-259 — 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) REDACTED:315— REDACTED:315-319 | REDACTED:323-327 — 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.
AC2 · Forms & labels· <Select> field component without a label · ×7
<Select> field component without a label frontend/src/components/ImportAudio/ImportAudioDialog.tsx:352— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label frontend/src/components/ImportAudio/ImportAudioDialog.tsx:384— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:310— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:345— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label frontend/src/components/ModelSettingsModal.tsx:814— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label frontend/src/components/TranscriptSettings.tsx:110— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label frontend/src/components/TranscriptSettings.tsx:134— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
Repeated repair: frontend/src-tauri/src/audio/vad.rs frontend/src-tauri/src/audio/vad.rs:240— frontend/src-tauri/src/audio/vad.rs changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is ContinuousVadProcessor::process_chunk at line 240), 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(windows): recover from ONNX runtime failures [skip ci]”; “fix(vad): align forced flush payload with timestamps”; “fix(vad): bound flushed segment timestamps”; “fix(vad): use 500ms live redemption, keep 2000ms for batch paths”. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/vad.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: frontend/src-tauri/src/audio/recording_manager.rs frontend/src-tauri/src/audio/recording_manager.rs:228— frontend/src-tauri/src/audio/recording_manager.rs changed 7 times in last 90 days and 5 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 RecordingManager::start_recording at line 228), 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: harden ONNX runtime and recording startup [skip ci]”; “fix(windows): load compatible ONNX Runtime dynamically”; “fix(audio): tear down the dead mic outside RECORDING_MANAGER so a hung BT teardown can't freeze Stop”; “fix(audio): resolve default output lock-free during mic hot-swap”. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/recording_manager.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: frontend/src/services/recordingService.ts frontend/src/services/recordingService.ts:55— frontend/src/services/recordingService.ts changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is RecordingService.isRecording at line 55), 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(audio): resolve default system audio on custom start path + silence false mic-fallback toast on stop”; “fix(audio): re-arm mic-disconnect detection after a failed hot-swap”; “fix(audio): unify mic resolution across both start paths + notify on no mic”; “fix(recording): harden start/stop lifecycle and surface mic device changes”. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/services/recordingService.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: frontend/src/app/meeting-details/page-content.tsx frontend/src/app/meeting-details/page-content.tsx:22— frontend/src/app/meeting-details/page-content.tsx changed 5 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is page-content.PageContent at line 22), 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(summary): restore generation progress after navigation”; “fix(summary): preserve truthful generation state [skip ci]”; “fix(summary): enforce safe generation lifecycle [skip ci]”; “fix(summary): harden Ollama summaries and editor state [skip ci]”. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/app/meeting-details/page-content.tsx`: 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: frontend/src/components/MeetingDetails/MeetingDetailsSplitView.tsx frontend/src/components/MeetingDetails/MeetingDetailsSplitView.tsx:44— frontend/src/components/MeetingDetails/MeetingDetailsSplitView.tsx changed 5 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 MeetingDetailsSplitView.MeetingDetailsSplitView at line 44), 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(ui): center the transcript summary tab on small window sizes”; “fix(summary): enforce safe generation lifecycle [skip ci]”; “fix(summary): harden Ollama summaries and editor state [skip ci]”; “fix(meeting-details): prevent transcript toolbar clipping [skip ci]”. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/components/MeetingDetails/MeetingDetailsSplitView.tsx`: 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: frontend/src/components/Logo.tsx frontend/src/components/Logo.tsx:12— frontend/src/components/Logo.tsx changed 4 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 2 (its worst body is Logo.Logo at line 12), 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: “hotfix(logo): fix the shrinked logo on expanded sidebar”; “fix: restore About access and Ollama cancellation [skip ci]”; “fix(ui): restore compact expanded sidebar logo [skip ci]”; “fix(ui): meeting-details split layout, toolbars, and container queries”. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/components/Logo.tsx`: 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: frontend/src/components/MeetingDetails/SummaryGeneratorButtonGroup.tsx frontend/src/components/MeetingDetails/SummaryGeneratorButtonGroup.tsx:41— frontend/src/components/MeetingDetails/SummaryGeneratorButtonGroup.tsx changed 3 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 12 (its worst body is SummaryGeneratorButtonGroup.SummaryGeneratorButtonGroup at line 41), 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(summary): show primary action labels sooner [skip ci]”; “fix(summary): enforce safe generation lifecycle [skip ci]”; “fix(ui): meeting-details split layout, toolbars, and container queries”. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 23:58:42 +05:30' --until='2026-09-10 23:58:42 +05:30' --full-history --no-merges -- frontend/src/components/MeetingDetails/SummaryGeneratorButtonGroup.tsx`: 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.
Duplicated block (12 lines × 2) frontend/src-tauri/src/audio/core-old.rs:806— frontend/src-tauri/src/audio/core-old.rs:806-817 | frontend/src-tauri/src/audio/devices/platform/windows.rs:204-215 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/platform/windows.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 115 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 (12 lines × 2) frontend/src-tauri/src/audio/devices/microphone.rs:45— frontend/src-tauri/src/audio/devices/microphone.rs:45-56 | frontend/src-tauri/src/audio/devices/speakers.rs:84-95 — 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) frontend/src-tauri/src/audio/recording_commands.rs:944— frontend/src-tauri/src/audio/recording_commands.rs:944-955 | frontend/src-tauri/src/audio/recording_commands.rs:959-970 — 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) frontend/src-tauri/src/audio/recording_saver.rs:121— frontend/src-tauri/src/audio/recording_saver.rs:121-132 | frontend/src-tauri/src/audio/recording_saver_old.rs:100-111 — 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) frontend/src-tauri/src/parakeet_engine/commands.rs:16— frontend/src-tauri/src/parakeet_engine/commands.rs:16-27 | frontend/src-tauri/src/whisper_engine/commands.rs:16-27 — `frontend/src-tauri/src/parakeet_engine/commands.rs` and `frontend/src-tauri/src/whisper_engine/commands.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 7 separate duplicated blocks between them, totalling at least 93 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) frontend/src-tauri/src/database/repositories/setting.rs:127— frontend/src-tauri/src/database/repositories/setting.rs:127-138 | frontend/src-tauri/src/database/repositories/setting.rs:219-230 — 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) frontend/src-tauri/src/audio/core-old.rs:745— frontend/src-tauri/src/audio/core-old.rs:745-756 | frontend/src-tauri/src/audio/core-old.rs:810-821 — 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.
Swallowed exception (empty catch) scripts/generate-update-manifest-github.js:45— 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.
Swallowed exception (empty catch) frontend/src/lib/summary-language-preferences.ts:47— 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.
Swallowed exception (empty catch) frontend/src/hooks/useRecentLanguages.ts:46— 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.
Swallowed exception (empty catch) frontend/src/hooks/meeting-details/useSummaryGeneration.ts:378— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) frontend/src/contexts/TranscriptContext.tsx:137— 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.
Swallowed exception (empty catch) frontend/src/components/MeetingDetails/MeetingDetailsSplitView.tsx:30— 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.
Swallowed exception (empty catch) frontend/scripts/tauri-auto.js:32— 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.
Change coupling: import.rs ↔ retranscription.rs frontend/src-tauri/src/audio/import.rs:1— `frontend/src-tauri/src/audio/import.rs` and `frontend/src-tauri/src/audio/retranscription.rs` change together 86% of the time (12 of the 14 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 12 shared commits counted here, the most recent 3 are `0ceee520` fix(vad): use 500ms live redemption, keep 2000ms for batch paths; `9ebafeca` feat(summary): add default summary output language preference; `0fbeb6ec` fix: replace unstable floor_char_boundary with stable equivalent — run `git show` on any of them.
Change coupling: retranscription.rs ↔ ImportAudioDialog.tsx frontend/src-tauri/src/audio/retranscription.rs:1— `frontend/src-tauri/src/audio/retranscription.rs` and `frontend/src/components/ImportAudio/ImportAudioDialog.tsx` change together 60% of the time (6 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `eadd3efc` fix(import): prevent dialog re-init on config changes using prevOpenRef; `5760dec8` refactor(beta): strengthen import/retranscribe feature gating; `a5e0e7b3` fix(import/retranscribe): code quality improvements + DRY violations … — run `git show` on any of them.
Change coupling: AnalyticsProvider.tsx ↔ index.tsx frontend/src/components/AnalyticsProvider.tsx:1— `frontend/src/components/AnalyticsProvider.tsx` and `frontend/src/components/Sidebar/index.tsx` change together 58% of the time (7 of the 12 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 `419cc083` chore: version bump to v0.4.1; `f6afb882` chore: version bump to v0.4.0; `c37431f2` chore(bump): version bump to v0.3.0 — run `git show` on any of them.
Change coupling: pipeline.rs ↔ recording_saver.rs frontend/src-tauri/src/audio/pipeline.rs:1— `frontend/src-tauri/src/audio/pipeline.rs` and `frontend/src-tauri/src/audio/recording_saver.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 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 7 shared commits counted here, the most recent 3 are `b650235c` Bluetooth device fix: Added advanced resampling; `983f3f8e` Meeting transcript chunk time saving: Tauri; `c7167c07` Better recording — run `git show` on any of them.
Change coupling: service.rs ↔ useSummaryGeneration.ts frontend/src-tauri/src/summary/service.rs:1— `frontend/src-tauri/src/summary/service.rs` and `frontend/src/hooks/meeting-details/useSummaryGeneration.ts` change together 50% of the time (8 of the 16 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `03dfb7b2` fix(summary): enforce safe generation lifecycle [skip ci]; `2f28bb8b` fix(summary): keep Ollama reasoning enabled and strip it for notes; `fd38fe99` fix(summary): address PR 455 language persistence follow-up [skip ci] — run `git show` on any of them.
Change coupling: setting.rs ↔ ModelSettingsModal.tsx frontend/src-tauri/src/database/repositories/setting.rs:1— `frontend/src-tauri/src/database/repositories/setting.rs` and `frontend/src/components/ModelSettingsModal.tsx` 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `f61c1033` migrations changed and removed gemini for compatibility; `ec176d63` custom endpoint model settings data loading fix, test endpoint fix; `6dd4f720` custom-openai endpoint added — run `git show` on any of them.
Duplicated block (18 lines × 2) frontend/src-tauri/src/audio/core-old.rs:842— frontend/src-tauri/src/audio/core-old.rs:842-859 | frontend/src-tauri/src/audio/devices/platform/windows.rs:240-257 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/platform/windows.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 115 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 (18 lines × 2) frontend/src-tauri/src/audio/core-old.rs:871— frontend/src-tauri/src/audio/core-old.rs:871-888 | frontend/src-tauri/src/audio/devices/configuration.rs:123-140 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/configuration.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 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 (18 lines × 2) frontend/src-tauri/src/audio/transcription/worker.rs:463— frontend/src-tauri/src/audio/transcription/worker.rs:463-480 | frontend/src-tauri/src/audio/transcription/worker.rs:500-517 — 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 (18 lines × 2) frontend/src-tauri/src/lib_old_complex.rs:963— frontend/src-tauri/src/lib_old_complex.rs:963-980 | frontend/src-tauri/src/lib_old_complex.rs:1214-1231 — 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 (18 lines × 2) frontend/src-tauri/src/notifications/commands.rs:341— frontend/src-tauri/src/notifications/commands.rs:341-358 | frontend/src-tauri/src/notifications/commands.rs:388-405 — 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 (18 lines × 2) frontend/src-tauri/src/parakeet_engine/commands.rs:243— frontend/src-tauri/src/parakeet_engine/commands.rs:243-260 | frontend/src-tauri/src/whisper_engine/commands.rs:293-310 — `frontend/src-tauri/src/parakeet_engine/commands.rs` and `frontend/src-tauri/src/whisper_engine/commands.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 7 separate duplicated blocks between them, totalling at least 93 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 (15 lines × 2) frontend/src-tauri/src/audio/core-old.rs:219— frontend/src-tauri/src/audio/core-old.rs:219-233 | frontend/src-tauri/src/audio/devices/platform/linux.rs:19-33 — 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) frontend/src-tauri/src/audio/devices/platform/windows.rs:143— frontend/src-tauri/src/audio/devices/platform/windows.rs:143-157 | frontend/src-tauri/src/audio/devices/platform/windows.rs:208-222 — 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 lines × 2) frontend/src-tauri/src/audio/level_monitor.rs:240— frontend/src-tauri/src/audio/level_monitor.rs:240-254 | frontend/src-tauri/src/audio/level_monitor.rs:264-278 — 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 lines × 2) frontend/src-tauri/src/audio/playback_monitor.rs:104— frontend/src-tauri/src/audio/playback_monitor.rs:104-118 | frontend/src-tauri/src/audio/playback_monitor.rs:143-157 — 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 lines × 2) frontend/src-tauri/src/parakeet_engine/commands.rs:182— frontend/src-tauri/src/parakeet_engine/commands.rs:182-196 | frontend/src-tauri/src/whisper_engine/commands.rs:237-251 — `frontend/src-tauri/src/parakeet_engine/commands.rs` and `frontend/src-tauri/src/whisper_engine/commands.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 7 separate duplicated blocks between them, totalling at least 93 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 (14 lines × 2) frontend/src-tauri/src/audio/core-old.rs:146— frontend/src-tauri/src/audio/core-old.rs:146-159 | frontend/src-tauri/src/audio/devices/platform/windows.rs:36-49 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/platform/windows.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 115 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 (14 lines × 2) frontend/src-tauri/src/audio/import.rs:779— frontend/src-tauri/src/audio/import.rs:779-792 | frontend/src-tauri/src/audio/import.rs:825-838 — 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) frontend/src-tauri/src/parakeet_engine/commands.rs:196— frontend/src-tauri/src/parakeet_engine/commands.rs:196-209 | frontend/src-tauri/src/parakeet_engine/commands.rs:288-301 — 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) frontend/src-tauri/src/whisper_engine/commands.rs:251— frontend/src-tauri/src/whisper_engine/commands.rs:251-264 | frontend/src-tauri/src/whisper_engine/commands.rs:338-351 — 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) backend/app/db.py:702— backend/app/db.py:702-715 | backend/app/db.py:750-763 — 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 × 2) frontend/src-tauri/src/analytics/analytics.rs:129— frontend/src-tauri/src/analytics/analytics.rs:129-136 | frontend/src-tauri/src/analytics/analytics.rs:427-434 — 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 × 2) frontend/src-tauri/src/audio/core-old.rs:34— frontend/src-tauri/src/audio/core-old.rs:34-41 | frontend/src-tauri/src/audio/devices/configuration.rs:27-34 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/configuration.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 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 (8 lines × 2) frontend/src-tauri/src/audio/core-old.rs:208— frontend/src-tauri/src/audio/core-old.rs:208-215 | frontend/src-tauri/src/audio/devices/platform/linux.rs:8-15 — 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) frontend/src-tauri/src/database/manager.rs:46— frontend/src-tauri/src/database/manager.rs:46-56 | frontend/src-tauri/src/database/manager.rs:137-144 — 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 × 2) frontend/src-tauri/src/lib_old_complex.rs:508— frontend/src-tauri/src/lib_old_complex.rs:508-515 | frontend/src-tauri/src/lib_old_complex.rs:542-549 — 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) frontend/src-tauri/src/analytics/analytics.rs:115— frontend/src-tauri/src/analytics/analytics.rs:115-121 | frontend/src-tauri/src/analytics/analytics.rs:444-450 — 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) frontend/src-tauri/src/audio/import.rs:760— frontend/src-tauri/src/audio/import.rs:760-766 | frontend/src-tauri/src/audio/import.rs:806-812 — 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) frontend/src-tauri/src/lib_old_complex.rs:204— frontend/src-tauri/src/lib_old_complex.rs:204-210 | frontend/src-tauri/src/lib_old_complex.rs:238-244 — 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) frontend/src-tauri/src/audio/core-old.rs:297— frontend/src-tauri/src/audio/core-old.rs:297-303 | frontend/src-tauri/src/audio/devices/microphone.rs:8-14 — 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) frontend/src-tauri/src/summary/summary_engine/sidecar.rs:168— frontend/src-tauri/src/summary/summary_engine/sidecar.rs:168-175 | frontend/src-tauri/src/summary/summary_engine/sidecar.rs:223-229 — 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 lines × 2 locations) frontend/src/app/settings/page.tsx:38— frontend/src/app/settings/page.tsx:38 · frontend/src/contexts/ConfigContext.tsx:201 — 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 (15 lines × 2 locations) frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx:66— frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx:66 · frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx:88 — 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 (15 lines × 2 locations) frontend/src/components/ImportAudio/ImportAudioDialog.tsx:162— frontend/src/components/ImportAudio/ImportAudioDialog.tsx:162 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:84 — 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 (15 lines × 2 locations) frontend/src/lib/parakeet.ts:96— frontend/src/lib/parakeet.ts:96 · frontend/src/lib/whisper.ts:127 — 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 (15 lines × 2 locations) frontend/src/lib/parakeet.ts:122— frontend/src/lib/parakeet.ts:122 · frontend/src/lib/whisper.ts:142 — 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.
WhisperEngine::finish_download (cognitive 44) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:948— WhisperEngine::finish_download has cognitive complexity 44 (threshold 15). Drivers by points: if/else 19 (32 pts), match/switch 4 (10 pts), boolean chains 2 (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.
WhisperEngine::transcribe_audio (cognitive 36) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:668— WhisperEngine::transcribe_audio has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 7, match/switch 2 (3 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.
WhisperEngine::download_model_with_owner (cognitive 28) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:1118— WhisperEngine::download_model_with_owner has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), match/switch 2 (3 pts), boolean chains 1, 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.
WhisperEngine::discover_models (cognitive 27) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:210— WhisperEngine::discover_models has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 3 (11 pts), loops 3, boolean chains 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.
RecordingSaver::start_accumulation (cognitive 32) frontend/src-tauri/src/audio/recording_saver.rs:138— RecordingSaver::start_accumulation has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (25 pts), match/switch 2 (6 pts), loops 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.
RecordingSaver::start_accumulation (cognitive 22) frontend/src-tauri/src/audio/recording_saver_old.rs:114— RecordingSaver::start_accumulation has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 1 (3 pts), loops 1 (2 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.
RecordingSaver::stop_and_save (cognitive 19) frontend/src-tauri/src/audio/recording_saver.rs:352— RecordingSaver::stop_and_save has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (17 pts), match/switch 1 (2 pts) (nesting depth added 5). 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.
RecordingSaver::stop_and_save (cognitive 18) frontend/src-tauri/src/audio/recording_saver_old.rs:258— RecordingSaver::stop_and_save has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (14 pts), match/switch 2 (4 pts) (nesting depth added 3). 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.
ClassTooLong: ModelSettingsModal frontend/src/components/ModelSettingsModal.tsx:1— ClassTooLong — 964 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 564 over it, 2.41× 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: ParakeetEngine frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:263— ClassTooLong — 638 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 27 methods. The bar is 400 significant lines; this is 238 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.
ClassTooLong: Analytics frontend/src/lib/analytics.ts:21— ClassTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 144 over it, 1.36× 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: ModelManager frontend/src-tauri/src/summary/summary_engine/model_manager.rs:110— ClassTooLong — 416 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 2 blocks, lines 110-851. The bar is 400 significant lines; this is 16 over it, 1.04× 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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×4
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (5 members, 50+ identical tokens) frontend/src-tauri/src/api/api.rs:1012— frontend/src-tauri/src/api/api.rs:1012-1075 | frontend/src-tauri/src/audio/recording_preferences.rs:207-244 | frontend/src-tauri/src/database/commands.rs:238-278 | frontend/src-tauri/src/parakeet_engine/commands.rs:538-577 | frontend/src-tauri/src/whisper_engine/commands.rs:530-568 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) frontend/src-tauri/src/summary/summary_engine/commands.rs:75— frontend/src-tauri/src/summary/summary_engine/commands.rs:75-97 | frontend/src-tauri/src/summary/summary_engine/commands.rs:105-127 | frontend/src-tauri/src/summary/summary_engine/commands.rs:135-214 | frontend/src-tauri/src/summary/summary_engine/commands.rs:275-306 | frontend/src-tauri/src/summary/summary_engine/commands.rs:314-352 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) backend/app/db.py:171— backend/app/db.py:171-209 | backend/app/db.py:214-281 | backend/app/db.py:285-327 | backend/app/db.py:583-625 | backend/app/db.py:702-746 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) backend/app/db.py:583— backend/app/db.py:583-625 | backend/app/db.py:628-643 | backend/app/db.py:702-746 | backend/app/db.py:750-767 | backend/app/db.py:864-878 — These 5 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 5 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 5 times.
Duplicated block (17 lines × 2) frontend/src-tauri/src/audio/core-old.rs:759— frontend/src-tauri/src/audio/core-old.rs:759-775 | frontend/src-tauri/src/audio/devices/platform/windows.rs:157-173 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/platform/windows.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 115 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 (17 lines × 2) frontend/src-tauri/src/audio/core-old.rs:908— frontend/src-tauri/src/audio/core-old.rs:908-924 | frontend/src-tauri/src/audio/devices/configuration.rs:160-176 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/configuration.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 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 (17 lines × 2) frontend/src-tauri/src/audio/decoder.rs:427— frontend/src-tauri/src/audio/decoder.rs:427-443 | frontend/src-tauri/src/audio/import.rs:205-221 — 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 (17 lines × 2) frontend/src-tauri/src/audio/import.rs:450— frontend/src-tauri/src/audio/import.rs:450-466 | frontend/src-tauri/src/audio/retranscription.rs:259-275 — before extracting anything, compare `frontend/src-tauri/src/audio/import.rs` and `frontend/src-tauri/src/audio/retranscription.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 174 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 (16 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:453— frontend/src-tauri/src/audio/recording_commands.rs:453-468 | frontend/src-tauri/src/audio/recording_commands.rs:640-655 — 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) frontend/src-tauri/src/lib.rs:172— frontend/src-tauri/src/lib.rs:172-187 | frontend/src-tauri/src/lib.rs:405-421 — 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) frontend/src-tauri/src/audio/recording_saver_old.rs:156— frontend/src-tauri/src/audio/recording_saver_old.rs:156-171 | frontend/src-tauri/src/audio/recording_saver_old.rs:221-236 — 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) backend/app/db.py:542— backend/app/db.py:542-557 | backend/app/db.py:662-677 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `backend/app/db.py:542` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:369— frontend/src-tauri/src/audio/recording_commands.rs:369-378 | frontend/src-tauri/src/audio/recording_commands.rs:545-554 — 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) frontend/src-tauri/src/lib.rs:292— frontend/src-tauri/src/lib.rs:292-301 | frontend/src-tauri/src/lib_old_complex.rs:1799-1808 — 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 (10 lines × 2) frontend/src-tauri/src/audio/decoder.rs:336— frontend/src-tauri/src/audio/decoder.rs:336-345 | frontend/src-tauri/src/audio/encode.rs:64-73 — 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 (10 lines × 2) frontend/src-tauri/src/parakeet_engine/commands.rs:367— frontend/src-tauri/src/parakeet_engine/commands.rs:367-376 | frontend/src-tauri/src/whisper_engine/commands.rs:410-419 — `frontend/src-tauri/src/parakeet_engine/commands.rs` and `frontend/src-tauri/src/whisper_engine/commands.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 7 separate duplicated blocks between them, totalling at least 93 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 (19 lines × 2 locations) frontend/src/components/ImportAudio/ImportAudioDialog.tsx:346— frontend/src/components/ImportAudio/ImportAudioDialog.tsx:346 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:304 — 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 (19 lines × 2 locations) frontend/src/components/ImportAudio/ImportAudioDialog.tsx:378— frontend/src/components/ImportAudio/ImportAudioDialog.tsx:378 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:339 — 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 (19 lines × 2 locations) frontend/src/components/Sidebar/index.tsx:457— frontend/src/components/Sidebar/index.tsx:457 · frontend/src/components/Sidebar/index.tsx:516 — 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 (19 lines × 2 locations) frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:252— frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:252 · frontend/src/components/shared/DownloadProgressToast.tsx:286 — 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×4
Untrusted text written into markup unescaped REDACTED:174— `note.content.split('\n').map(line=>{if(line.startsWith('# ')){return`<h1>${line.slice(2)}</h1>`;}else if(line.startsW…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:176— `line.slice(2)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:178— `line.slice(3)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:180— `line.slice(2)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
WhisperEngine::transcribe_audio (cyclomatic 25) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:668— WhisperEngine::transcribe_audio 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.
WhisperEngine::finish_download (cyclomatic 23) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:948— WhisperEngine::finish_download 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.
WhisperEngine::download_model_with_owner (cyclomatic 19) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:1118— WhisperEngine::download_model_with_owner 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.
MacOSSystemAudioDetector::start::system_listener (cognitive 55) frontend/src-tauri/src/audio/system_detector.rs:199— MacOSSystemAudioDetector::start::system_listener has cognitive complexity 55 (threshold 15). Drivers by points: if/else 11 (54 pts), loops 1 (nesting depth added 43). 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 (MacOSSystemAudioDetector::start, MacOSSystemAudioDetector::start::device_listener) 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.
MacOSSystemAudioDetector::start::device_listener (cognitive 45) frontend/src-tauri/src/audio/system_detector.rs:144— MacOSSystemAudioDetector::start::device_listener has cognitive complexity 45 (threshold 15). Drivers by points: if/else 9 (44 pts), loops 1 (nesting depth added 35). 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 (MacOSSystemAudioDetector::start, MacOSSystemAudioDetector::start::system_listener) 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.
MacOSSystemAudioDetector::start (cognitive 23) frontend/src-tauri/src/audio/system_detector.rs:130— MacOSSystemAudioDetector::start has cognitive complexity 23 (threshold 15). Drivers by points: if/else 31 (117 pts), loops 4, match/switch 1 (2 pts) (nesting depth added 87). 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 (MacOSSystemAudioDetector::start::device_listener, MacOSSystemAudioDetector::start::system_listener) 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.
Duplicated block (9–10 lines × 3) frontend/src-tauri/src/anthropic/anthropic.rs:80— frontend/src-tauri/src/anthropic/anthropic.rs:80-89 | frontend/src-tauri/src/groq/groq.rs:78-86 | frontend/src-tauri/src/openai/openai.rs:110-118 — `frontend/src-tauri/src/anthropic/anthropic.rs` and `frontend/src-tauri/src/groq/groq.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 30 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–10 lines × 3) frontend/src-tauri/src/parakeet_engine/commands.rs:161— frontend/src-tauri/src/parakeet_engine/commands.rs:161-170 | frontend/src-tauri/src/parakeet_engine/commands.rs:194-202 | frontend/src-tauri/src/parakeet_engine/commands.rs:286-294 — 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 (9–10 lines × 3) frontend/src-tauri/src/whisper_engine/commands.rs:216— frontend/src-tauri/src/whisper_engine/commands.rs:216-225 | frontend/src-tauri/src/whisper_engine/commands.rs:249-257 | frontend/src-tauri/src/whisper_engine/commands.rs:336-344 — 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.
Outbound HTTP without resilience backend/debug_cors.py:30— `requests.post(` 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 frontend/src-tauri/src/openrouter/openrouter.rs:43— `Client::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.
Outbound HTTP without resilience frontend/src-tauri/src/summary/service.rs:546— `reqwest::Client::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.
Duplicated block (26 lines × 2 locations) frontend/src/app/_components/SettingsModal.tsx:159— frontend/src/app/_components/SettingsModal.tsx:159 · frontend/src/app/_components/SettingsModal.tsx:200 — 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 (26 lines × 2 locations) frontend/src/components/Sidebar/index.tsx:161— frontend/src/components/Sidebar/index.tsx:161 · frontend/src/components/SummaryModelSettings.tsx:79 — 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 (26 lines × 2 locations) frontend/src/components/TranscriptView.tsx:351— frontend/src/components/TranscriptView.tsx:351 · frontend/src/components/VirtualizedTranscriptView.tsx:239 — 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 (16 lines × 2 locations) frontend/src/components/BuiltInModelManager.tsx:350— frontend/src/components/BuiltInModelManager.tsx:350 · frontend/src/components/BuiltInModelManager.tsx:379 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (16 lines × 2 locations) frontend/src/components/ui/select.tsx:35— frontend/src/components/ui/select.tsx:35 · frontend/src/components/ui/select.tsx:52 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (16 lines × 2 locations) frontend/src/contexts/OllamaDownloadContext.tsx:82— frontend/src/contexts/OllamaDownloadContext.tsx:82 · frontend/src/contexts/OllamaDownloadContext.tsx:110 — 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.
AC3 · Page structure· Page without a main landmark · ×2
Page without a main landmark backend/whisper-custom/server/public/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark frontend/src/app/layout.tsx:234— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Focus outline removed inline frontend/src/components/AISummary/Block.tsx:235— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline frontend/src/components/LanguagePickerPopover.tsx:90— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
AudioCapture::process_audio_data (cyclomatic 36) frontend/src-tauri/src/audio/pipeline.rs:399— AudioCapture::process_audio_data has cyclomatic complexity 36 (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.
AudioCapture::new (cyclomatic 16) frontend/src-tauri/src/audio/pipeline.rs:230— AudioCapture::new has cyclomatic complexity 16 (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.
AudioCapture::process_audio_data (cognitive 105) frontend/src-tauri/src/audio/pipeline.rs:399— AudioCapture::process_audio_data has cognitive complexity 105 (threshold 15). Drivers by points: if/else 40 (92 pts), match/switch 1 (6 pts), loops 1 (5 pts), boolean chains 2 (nesting depth added 61). 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.
AudioCapture::new (cognitive 28) frontend/src-tauri/src/audio/pipeline.rs:230— AudioCapture::new has cognitive complexity 28 (threshold 15). Drivers by points: if/else 18 (21 pts), match/switch 3 (7 pts) (nesting depth added 7). 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.
ModelManager::download_model_detailed (cognitive 96) frontend/src-tauri/src/summary/summary_engine/model_manager.rs:351— ModelManager::download_model_detailed has cognitive complexity 96 (threshold 15). Drivers by points: if/else 49 (88 pts), match/switch 2 (5 pts), boolean chains 2, loops 1 (nesting depth added 42). 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.
ModelManager::scan_models (cognitive 18) frontend/src-tauri/src/summary/summary_engine/model_manager.rs:182— ModelManager::scan_models has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 1 (3 pts), boolean chains 1, 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.
ParakeetEngine::download_artifacts (cognitive 63) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:849— ParakeetEngine::download_artifacts has cognitive complexity 63 (threshold 15). Drivers by points: if/else 19 (42 pts), match/switch 6 (16 pts), loops 2 (3 pts), boolean chains 2 (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.
ParakeetEngine::discover_models_from_specs (cognitive 24) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:336— ParakeetEngine::discover_models_from_specs has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 5 (9 pts), match/switch 1 (4 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.
PostProcessor::clean_repetitive_text (cognitive 26) frontend/src-tauri/src/audio/post_processor.rs:145— PostProcessor::clean_repetitive_text has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 12). 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.
PostProcessor::new (cognitive 16) frontend/src-tauri/src/audio/post_processor.rs:35— PostProcessor::new has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 1 (2 pts), 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.
TooManyMethods: Analytics frontend/src/lib/analytics.ts:21— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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: RecordingManager frontend/src-tauri/src/audio/recording_manager.rs:187— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× 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 (35 lines × 2) frontend/src-tauri/src/audio/import.rs:518— frontend/src-tauri/src/audio/import.rs:518-552 | frontend/src-tauri/src/audio/retranscription.rs:309-343 — before extracting anything, compare `frontend/src-tauri/src/audio/import.rs` and `frontend/src-tauri/src/audio/retranscription.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 174 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 (35 lines × 2) frontend/src-tauri/src/lib_old_complex.rs:1062— frontend/src-tauri/src/lib_old_complex.rs:1062-1096 | frontend/src-tauri/src/lib_old_complex.rs:1256-1290 — 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 (24 lines × 2) frontend/src-tauri/src/audio/transcription/engine.rs:67— frontend/src-tauri/src/audio/transcription/engine.rs:67-90 | frontend/src-tauri/src/audio/transcription/engine.rs:163-186 — 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 (24 lines × 2) backend/app/db.py:588— backend/app/db.py:588-611 | backend/app/db.py:709-732 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `backend/app/db.py:588` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (22 lines × 2) frontend/src-tauri/src/audio/core-old.rs:74— frontend/src-tauri/src/audio/core-old.rs:74-95 | frontend/src-tauri/src/audio/devices/configuration.rs:67-88 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/configuration.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 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 (22 lines × 2) frontend/src-tauri/src/lib_old_complex.rs:940— frontend/src-tauri/src/lib_old_complex.rs:940-961 | frontend/src-tauri/src/lib_old_complex.rs:1191-1212 — 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 (21 lines × 2) frontend/src-tauri/src/audio/core-old.rs:700— frontend/src-tauri/src/audio/core-old.rs:700-720 | frontend/src-tauri/src/audio/devices/platform/windows.rs:98-118 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/platform/windows.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 115 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 (21 lines × 2) frontend/src-tauri/src/audio/import.rs:467— frontend/src-tauri/src/audio/import.rs:467-487 | frontend/src-tauri/src/audio/retranscription.rs:276-296 — before extracting anything, compare `frontend/src-tauri/src/audio/import.rs` and `frontend/src-tauri/src/audio/retranscription.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 174 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 (14–15 lines × 2) frontend/src-tauri/src/audio/vad.rs:145— frontend/src-tauri/src/audio/vad.rs:145-159 | frontend/src-tauri/src/audio_v2/resampler.rs:37-50 — 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 (14–15 lines × 2) frontend/src-tauri/src/summary/summary_engine/sidecar.rs:143— frontend/src-tauri/src/summary/summary_engine/sidecar.rs:143-157 | frontend/src-tauri/src/summary/summary_engine/sidecar.rs:200-213 — 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 (13 lines × 2) frontend/src-tauri/src/audio/retranscription.rs:594— frontend/src-tauri/src/audio/retranscription.rs:594-606 | frontend/src-tauri/src/audio/retranscription.rs:694-706 — 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 (13 lines × 2) frontend/src-tauri/src/summary/templates/loader.rs:153— frontend/src-tauri/src/summary/templates/loader.rs:153-165 | frontend/src-tauri/src/summary/templates/loader.rs:177-189 — 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 × 3) frontend/src-tauri/src/audio/core-old.rs:890— frontend/src-tauri/src/audio/core-old.rs:890-901 | frontend/src-tauri/src/audio/core-old.rs:907-918 | frontend/src-tauri/src/audio/devices/configuration.rs:159-170 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/configuration.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 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 (12 lines × 3) backend/app/db.py:583— backend/app/db.py:583-594 | backend/app/db.py:628-639 | backend/app/db.py:864-875 — 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–12 lines × 2) frontend/src-tauri/src/audio/import.rs:756— frontend/src-tauri/src/audio/import.rs:756-766 | frontend/src-tauri/src/audio/retranscription.rs:527-538 — before extracting anything, compare `frontend/src-tauri/src/audio/import.rs` and `frontend/src-tauri/src/audio/retranscription.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 174 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 (11–12 lines × 2) frontend/src-tauri/src/audio/import.rs:802— frontend/src-tauri/src/audio/import.rs:802-812 | frontend/src-tauri/src/audio/retranscription.rs:629-640 — before extracting anything, compare `frontend/src-tauri/src/audio/import.rs` and `frontend/src-tauri/src/audio/retranscription.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 174 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 × 3) frontend/src-tauri/src/anthropic/anthropic.rs:155— frontend/src-tauri/src/anthropic/anthropic.rs:155-163 | frontend/src-tauri/src/groq/groq.rs:149-157 | frontend/src-tauri/src/openai/openai.rs:178-186 — `frontend/src-tauri/src/anthropic/anthropic.rs` and `frontend/src-tauri/src/groq/groq.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 30 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 × 3) backend/app/db.py:195— backend/app/db.py:195-205 | backend/app/db.py:615-623 | backend/app/db.py:736-744 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `backend/app/db.py:195` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–8 lines × 2) frontend/src-tauri/src/audio/level_monitor.rs:304— frontend/src-tauri/src/audio/level_monitor.rs:304-311 | frontend/src-tauri/src/audio_v2/mixer.rs:155-161 — 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–8 lines × 2) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:902— frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:902-908 | frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:926-933 — 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 (11 lines × 3) frontend/src-tauri/src/anthropic/anthropic.rs:107— frontend/src-tauri/src/anthropic/anthropic.rs:107-117 | frontend/src-tauri/src/groq/groq.rs:101-111 | frontend/src-tauri/src/openai/openai.rs:133-143 — `frontend/src-tauri/src/anthropic/anthropic.rs` and `frontend/src-tauri/src/groq/groq.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 30 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 × 3) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:593— frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:593-603 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:890-900 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:912-922 — 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 (33 lines × 2 locations) frontend/src/components/ImportAudio/ImportAudioDialog.tsx:412— frontend/src/components/ImportAudio/ImportAudioDialog.tsx:412 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:361 — 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 (33 lines × 2 locations) frontend/src/components/VirtualizedTranscriptView.tsx:300— frontend/src/components/VirtualizedTranscriptView.tsx:300 · frontend/src/components/VirtualizedTranscriptView.tsx:356 — 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 (24 lines × 2 locations) frontend/src/components/molecules/form-components/form-input-item.tsx:59— frontend/src/components/molecules/form-components/form-input-item.tsx:59 · frontend/src/components/molecules/form-components/form-select-item.tsx:33 — 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 (24 lines × 2 locations) frontend/src/components/ui/dropdown-menu.tsx:74— frontend/src/components/ui/dropdown-menu.tsx:74 · frontend/src/components/ui/dropdown-menu.tsx:138 — 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 (17 lines × 2 locations) frontend/src/components/LanguagePickerPopover.tsx:106— frontend/src/components/LanguagePickerPopover.tsx:106 · frontend/src/components/LanguagePickerPopover.tsx:152 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (17 lines × 2 locations) frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:85— frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:85 · frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:134 — 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 (17 matched lines × 2 locations) · ×2
Duplicated block with local edits (17 matched lines × 2 locations) frontend/src/contexts/OnboardingContext.tsx:112— frontend/src/contexts/OnboardingContext.tsx:112 · frontend/src/contexts/OnboardingContext.tsx:400 — the two spans are one implementation copied and then locally edited — 69 tokens are still identical, in the same order in both spans, 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 with local edits (17 matched lines × 2 locations) frontend/src/contexts/TranscriptContext.tsx:290— frontend/src/contexts/TranscriptContext.tsx:290 · frontend/src/contexts/TranscriptContext.tsx:409 — the two spans are one implementation copied and then locally edited — 99 tokens are still identical, in the same order in both spans, 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.
Dead file (~19 LoC) frontend/src/components/MainNav/index.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~19 LoC) frontend/src/hooks/useNavigation.ts— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~6 LoC) frontend/src/app/metadata.ts— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~6 LoC) frontend/src/app/metadata.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~0 LoC) frontend/src/components/AudioPlayer.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~0 LoC) frontend/src/config/api.ts— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×2
Recursive walk over a caller-supplied document has no depth cap frontend/src/lib/summary-content.ts:14— `hasVisibleSummaryContent` is exported, takes a document from its caller (line 49) and hands it to `containsReasoningMarker`, which calls itself at line 14 (`containsReasoningMarker`) with a piece of `value` (and at line 26) — and nowhere in `containsReasoningMarker` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `containsReasoningMarker` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap frontend/src/lib/summary-content.ts:35— `hasVisibleSummaryContent` is exported, takes a document from its caller (line 49) and hands it to `hasBlockText`, which calls itself at line 35 (`hasBlockText`) with a piece of `value` (and at line 38) — and nowhere in `hasBlockText` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `hasBlockText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×1
Modal dialog does not manage focus frontend/src/components/LanguagePickerPopover.tsx:82— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Low contrast colour pair in CSS (4.0:1) backend/whisper-custom/server/public/index.html:5— `button` sets color: white on background-color: #007bff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast Tailwind colour pair (4.4:1) frontend/src/components/AudioBackendSelector.tsx:165— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (1.5:1) frontend/src/components/RecordingControls.tsx:373— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (2.1:1) frontend/src/components/RecordingControls.tsx:411— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
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-jsx-a11y) 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 115 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.
index.AISummary (cyclomatic 93) frontend/src/components/AISummary/index.tsx:22— index.AISummary has cyclomatic complexity 93 (threshold 15). Most of this is not in the body itself: 12 of the 93 points are its own statements and the rest belongs to 32 function items inside it that branch (a function literal at line 406, handleCreateNewBlock, handleBlockDelete, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
RecordingControls.RecordingControls (cyclomatic 84) frontend/src/components/RecordingControls.tsx:32— RecordingControls.RecordingControls has cyclomatic complexity 84 (threshold 15). Of this number, 35 points are the body's own statements and 49 belong to 13 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.
ModelSettingsModal.ModelSettingsModal (cyclomatic 83) frontend/src/components/ModelSettingsModal.tsx:112— ModelSettingsModal.ModelSettingsModal has cyclomatic complexity 83 (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. This shape REPEATS in the file: one other method here (ModelSettingsModal.ModelSettingsModal::handleSave) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both 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.
OnboardingContext.OnboardingProvider (cyclomatic 62) frontend/src/contexts/OnboardingContext.tsx:77— OnboardingContext.OnboardingProvider has cyclomatic complexity 62 (threshold 15). Most of this is not in the body itself: 1 of the 62 points is its own statement and the rest belongs to 19 function items inside it that branch (startBackgroundDownloads, performAutoDetection, loadOnboardingStatus, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TranscriptContext.TranscriptProvider (cyclomatic 58) frontend/src/contexts/TranscriptContext.tsx:27— TranscriptContext.TranscriptProvider has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 1 of the 58 points is its own statement and the rest belongs to 24 function literals inside it that branch (lines 188, 232, 267, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
WhisperModelManager.ModelManager (cyclomatic 57) frontend/src/components/WhisperModelManager.tsx:25— WhisperModelManager.ModelManager has cyclomatic complexity 57 (threshold 15). Most of this is not in the body itself: 5 of the 57 points are its own statements and the rest belongs to 25 function items inside it that branch (reconcileCancellation::reconcile, a function literal at line 149, a function literal at line 308, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ParakeetModelManager.ParakeetModelManager (cyclomatic 54) frontend/src/components/ParakeetModelManager.tsx:23— ParakeetModelManager.ParakeetModelManager has cyclomatic complexity 54 (threshold 15). Most of this is not in the body itself: 6 of the 54 points are its own statements and the rest belongs to 20 function items inside it that branch (a function literal at line 92, a function literal at line 98, downloadModel, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
RetranscribeDialog.RetranscribeDialog (cyclomatic 54) frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:54— RetranscribeDialog.RetranscribeDialog has cyclomatic complexity 54 (threshold 15). Of this number, 21 points are the body's own statements and 33 belong to 14 function items inside it that branch. 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.
BuiltInModelManager.BuiltInModelManager (cyclomatic 53) frontend/src/components/BuiltInModelManager.tsx:38— BuiltInModelManager.BuiltInModelManager has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 6 of the 53 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 290, fetchModels, a function literal at line 81, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
VirtualizedTranscriptView.VirtualizedTranscriptView (cyclomatic 53) frontend/src/components/VirtualizedTranscriptView.tsx:113— VirtualizedTranscriptView.VirtualizedTranscriptView has cyclomatic complexity 53 (threshold 15). Of this number, 33 points are the body's own statements and 20 belong to 5 function literals inside it that branch. 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.
ImportAudioDialog.ImportAudioDialog (cyclomatic 50) frontend/src/components/ImportAudio/ImportAudioDialog.tsx:67— ImportAudioDialog.ImportAudioDialog has cyclomatic complexity 50 (threshold 15). Of this number, 25 points are the body's own statements and 25 belong to 12 function items inside it that branch. 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.
ConfigContext.ConfigProvider (cyclomatic 47) frontend/src/contexts/ConfigContext.tsx:100— ConfigContext.ConfigProvider has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 1 of the 47 points is its own statement and the rest belongs to 17 function literals inside it that branch (lines 232, 199, 352, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ModelManager::download_model_detailed (cyclomatic 45) frontend/src-tauri/src/summary/summary_engine/model_manager.rs:351— ModelManager::download_model_detailed has cyclomatic complexity 45 (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.
DeviceSelection.DeviceSelection (cyclomatic 43) frontend/src/components/DeviceSelection.tsx:40— DeviceSelection.DeviceSelection has cyclomatic complexity 43 (threshold 15). Of this number, 17 points are the body's own statements and 26 belong to 10 function items inside it that branch. 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.
UpdateDialog.UpdateDialog (cyclomatic 41) frontend/src/components/UpdateDialog.tsx:23— UpdateDialog.UpdateDialog has cyclomatic complexity 41 (threshold 15). Of this number, 17 points are the body's own statements and 24 belong to 9 function items inside it that branch. 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.
TranscriptView.TranscriptView (cyclomatic 41) frontend/src/components/TranscriptView.tsx:107— TranscriptView.TranscriptView has cyclomatic complexity 41 (threshold 15). Of this number, 16 points are the body's own statements and 25 belong to 8 function literals inside it that branch. 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.
useRecordingStop.useRecordingStop.handleRecordingStop (cyclomatic 41) frontend/src/hooks/useRecordingStop.ts:121— useRecordingStop.useRecordingStop.handleRecordingStop 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.
AudioStream::from_device (cyclomatic 37) frontend/src-tauri/src/audio/core-old.rs:396— AudioStream::from_device has cyclomatic complexity 37 (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.
page.MeetingDetailsContent (cyclomatic 36) frontend/src/app/meeting-details/page.tsx:23— page.MeetingDetailsContent has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 6 of the 36 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 67, 227, 122, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Block.BlockComponent::handleKeyDown (cyclomatic 35) frontend/src/components/AISummary/Block.tsx:107— Block.BlockComponent::handleKeyDown 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.
ParakeetEngine::download_artifacts (cyclomatic 33) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:849— ParakeetEngine::download_artifacts has cyclomatic complexity 33 (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.
ParakeetModelManager.ModelCard (cyclomatic 33) frontend/src/components/ParakeetModelManager.tsx:478— ParakeetModelManager.ModelCard has cyclomatic complexity 33 (threshold 15). Of this number, 32 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
SummaryPanel.SummaryPanel (cyclomatic 33) frontend/src/components/MeetingDetails/SummaryPanel.tsx:59— SummaryPanel.SummaryPanel has cyclomatic complexity 33 (threshold 15). Of this number, 16 points are the body's own statements and 17 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.
TranscriptRecovery.TranscriptRecovery (cyclomatic 33) frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:34— TranscriptRecovery.TranscriptRecovery has cyclomatic complexity 33 (threshold 15). Of this number, 16 points are the body's own statements and 17 belong to 7 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.
SummaryService::process_transcript_background (cyclomatic 32) frontend/src-tauri/src/summary/service.rs:334— SummaryService::process_transcript_background has cyclomatic complexity 32 (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.
BlockNoteSummaryView.BlockNoteSummaryView (cyclomatic 32) frontend/src/components/AISummary/BlockNoteSummaryView.tsx:68— BlockNoteSummaryView.BlockNoteSummaryView has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 6 of the 32 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 170, 136, 90, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SidebarProvider.SidebarProvider (cyclomatic 32) frontend/src/components/Sidebar/SidebarProvider.tsx:78— SidebarProvider.SidebarProvider has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 1 of the 32 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 216, a function literal at line 97, a function literal at line 199, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MacOSSystemAudioDetector::start (cyclomatic 31) frontend/src-tauri/src/audio/system_detector.rs:130— MacOSSystemAudioDetector::start has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 11 of the 31 points are its own statements and the rest belongs to 2 function items inside it that branch (system_listener, device_listener). 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.
generate-update-manifest-github.bundleFiles.forEach() (cyclomatic 31) scripts/generate-update-manifest-github.js:91— generate-update-manifest-github.bundleFiles.forEach() has cyclomatic complexity 31 (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.
main.process_transcript_background (cyclomatic 30) REDACTED:219— main.process_transcript_background 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.
TranscriptSettings.TranscriptSettings (cyclomatic 29) frontend/src/components/TranscriptSettings.tsx:24— TranscriptSettings.TranscriptSettings has cyclomatic complexity 29 (threshold 15). Of this number, 20 points are the body's own statements and 9 belong to 6 function items inside it that branch. 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.
useSummaryGeneration.useSummaryGeneration.handlePollingResult (cyclomatic 29) frontend/src/hooks/meeting-details/useSummaryGeneration.ts:170— useSummaryGeneration.useSummaryGeneration.handlePollingResult 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.
main.get_summary (cyclomatic 28) REDACTED:369— main.get_summary 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.
ModelSettingsModal.ModelSettingsModal::handleSave (cyclomatic 28) frontend/src/components/ModelSettingsModal.tsx:617— ModelSettingsModal.ModelSettingsModal::handleSave has cyclomatic complexity 28 (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. This shape REPEATS in the file: one other method here (ModelSettingsModal.ModelSettingsModal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both 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.
WhisperModelManager.ModelCard (cyclomatic 27) frontend/src/components/WhisperModelManager.tsx:577— WhisperModelManager.ModelCard has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
page.Home (cyclomatic 26) frontend/src/app/page.tsx:24— page.Home has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 71, handleRecovery, a function literal at line 109, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ChunkProgressDisplay.ChunkProgressDisplay (cyclomatic 25) frontend/src/components/ChunkProgressDisplay.tsx:31— ChunkProgressDisplay.ChunkProgressDisplay has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 9 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (getChunkStatusIcon, getChunkStatusColor, a function literal at line 204, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
LanguagePickerPopover.LanguagePickerPopover (cyclomatic 25) frontend/src/components/LanguagePickerPopover.tsx:15— LanguagePickerPopover.LanguagePickerPopover has cyclomatic complexity 25 (threshold 15). Of this number, 15 points are the body's own statements and 10 belong to 7 function literals inside it that branch. 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.
PreferenceSettings.PreferenceSettings (cyclomatic 25) frontend/src/components/PreferenceSettings.tsx:11— PreferenceSettings.PreferenceSettings has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 56, a function literal at line 77, handleOpenFolder, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.Sidebar::renderItem (cyclomatic 25) frontend/src/components/Sidebar/index.tsx:554— index.Sidebar::renderItem 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.
useRecordingStart.useRecordingStart (cyclomatic 25) frontend/src/hooks/useRecordingStart.ts:43— useRecordingStart.useRecordingStart has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 212, 310). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SidecarManager::resolve_helper_binary (cyclomatic 24) frontend/src-tauri/src/summary/summary_engine/sidecar.rs:108— SidecarManager::resolve_helper_binary 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.
PermissionWarning.PermissionWarning (cyclomatic 24) frontend/src/components/PermissionWarning.tsx:14— PermissionWarning.PermissionWarning has cyclomatic complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 belong to 2 function items inside it that branch. 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.
DownloadProgressToast.useDownloadProgressToast (cyclomatic 23) frontend/src/components/shared/DownloadProgressToast.tsx:127— DownloadProgressToast.useDownloadProgressToast has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 306, 200, 164, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
useAutoScroll.useAutoScroll (cyclomatic 23) frontend/src/hooks/useAutoScroll.ts:38— useAutoScroll.useAutoScroll has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 132, 180, 94, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SummaryModelSettings.SummaryModelSettings (cyclomatic 22) frontend/src/components/SummaryModelSettings.tsx:15— SummaryModelSettings.SummaryModelSettings has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 27, a function literal at line 75, handleSaveModelConfig). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
auto-detect-gpu.detectGPU (cyclomatic 20) REDACTED:19— auto-detect-gpu.detectGPU 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.
useModelConfiguration.useModelConfiguration (cyclomatic 20) frontend/src/hooks/meeting-details/useModelConfiguration.ts:11— useModelConfiguration.useModelConfiguration has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
TranscriptProcessor.process_transcript (cyclomatic 19) backend/app/transcript_processor.py:87— TranscriptProcessor.process_transcript 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.
useCopyOperations.useCopyOperations.handleCopySummary (cyclomatic 18) frontend/src/hooks/meeting-details/useCopyOperations.ts:109— useCopyOperations.useCopyOperations.handleCopySummary has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 2 function literals inside it that branch. 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.
AudioDeviceMonitor::monitor_loop (cyclomatic 17) frontend/src-tauri/src/audio/device_monitor.rs:272— AudioDeviceMonitor::monitor_loop 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.
AnalyticsConsentSwitch.AnalyticsConsentSwitch (cyclomatic 17) frontend/src/components/AnalyticsConsentSwitch.tsx:13— AnalyticsConsentSwitch.AnalyticsConsentSwitch has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (performToggle, a function literal at line 23, handleCopyUserId, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
LegacyDatabaseImport.LegacyDatabaseImport (cyclomatic 17) frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx:17— LegacyDatabaseImport.LegacyDatabaseImport has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 3 function items inside it that branch. 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.
RecordingSettings.RecordingSettings (cyclomatic 16) frontend/src/components/RecordingSettings.tsx:23— RecordingSettings.RecordingSettings has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (savePreferences, a function literal at line 39, a function literal at line 62, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
LanguageSelection.LanguageSelection (cyclomatic 16) frontend/src/components/LanguageSelection.tsx:124— LanguageSelection.LanguageSelection has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 3 function items inside it that branch. 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.
DownloadProgressStep.DownloadProgressStep::renderDownloadCard (cyclomatic 16) frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:402— DownloadProgressStep.DownloadProgressStep::renderDownloadCard has cyclomatic complexity 16 (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.
RecordingStateContext.RecordingStateProvider (cyclomatic 16) frontend/src/contexts/RecordingStateContext.tsx:61— RecordingStateContext.RecordingStateProvider has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 10 function items inside it that branch (a function literal at line 260, a function literal at line 167, a function literal at line 75, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
useSummaryGeneration.useSummaryGeneration.processSummary (cyclomatic 16) frontend/src/hooks/meeting-details/useSummaryGeneration.ts:307— useSummaryGeneration.useSummaryGeneration.processSummary has cyclomatic complexity 16 (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.
index.AISummary (cognitive 104) frontend/src/components/AISummary/index.tsx:22— index.AISummary has cognitive complexity 104 (threshold 15). Drivers by points: if/else 50 (64 pts), boolean chains 25, loops 6 (8 pts), ternaries 5, match/switch 1 (2 pts) (nesting depth added 17). Most of this is not in the body itself: 7 of the 104 points are its own statements and the rest belongs to 32 function items inside it that branch (a function literal at line 406, handleBlockDelete, handleCreateNewBlock, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
RecordingControls.RecordingControls (cognitive 104) frontend/src/components/RecordingControls.tsx:32— RecordingControls.RecordingControls has cognitive complexity 104 (threshold 15). Drivers by points: ternaries 16 (47 pts), if/else 18 (27 pts), boolean chains 24, error handling 6 (nesting depth added 40). Of this number, 43 points are the body's own statements and 61 belong to 13 function literals inside it that branch. 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.
DownloadProgressStep.DownloadProgressStep (cognitive 83) frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:26— DownloadProgressStep.DownloadProgressStep has cognitive complexity 83 (threshold 15). Drivers by points: boolean chains 28, ternaries 16 (24 pts), if/else 22 (23 pts), error handling 6 (8 pts) (nesting depth added 11). Most of this is not in the body itself: 10 of the 83 points are its own statements and the rest belongs to 20 function items inside it that branch (renderDownloadCard, handleContinue, a function literal at line 304, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
main.process_transcript_background (cognitive 74) REDACTED:219— main.process_transcript_background has cognitive complexity 74 (threshold 15). Drivers by points: if/else 14 (41 pts), loops 4 (13 pts), error handling 6 (10 pts), ternaries 1 (6 pts), boolean chains 4 (nesting depth added 45). 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.
AudioStream::from_device (cognitive 70) frontend/src-tauri/src/audio/core-old.rs:396— AudioStream::from_device has cognitive complexity 70 (threshold 15). Drivers by points: if/else 29 (54 pts), match/switch 8 (15 pts), boolean chains 1 (nesting depth added 32). 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.
OnboardingContext.OnboardingProvider (cognitive 67) frontend/src/contexts/OnboardingContext.tsx:77— OnboardingContext.OnboardingProvider has cognitive complexity 67 (threshold 15). Drivers by points: if/else 30 (37 pts), boolean chains 14, error handling 13 (14 pts), ternaries 2 (nesting depth added 8). None of this is in the body itself: all 67 points belong to 19 function items inside it that branch (startBackgroundDownloads, loadOnboardingStatus, performAutoDetection, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ParakeetModelManager.ParakeetModelManager (cognitive 65) frontend/src/components/ParakeetModelManager.tsx:23— ParakeetModelManager.ParakeetModelManager has cognitive complexity 65 (threshold 15). Drivers by points: ternaries 15 (28 pts), boolean chains 16, if/else 14 (16 pts), error handling 5 (nesting depth added 15). Most of this is not in the body itself: 5 of the 65 points are its own statements and the rest belongs to 20 function items inside it that branch (a function literal at line 92, downloadModel, deleteModel, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SidecarManager::resolve_helper_binary (cognitive 63) frontend/src-tauri/src/summary/summary_engine/sidecar.rs:108— SidecarManager::resolve_helper_binary has cognitive complexity 63 (threshold 15). Drivers by points: if/else 21 (52 pts), loops 3 (9 pts), boolean chains 2 (nesting depth added 37). 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.
useRecordingStop.useRecordingStop.handleRecordingStop (cognitive 62) frontend/src/hooks/useRecordingStop.ts:121— useRecordingStop.useRecordingStop.handleRecordingStop has cognitive complexity 62 (threshold 15). Drivers by points: if/else 14 (22 pts), error handling 7 (14 pts), ternaries 6 (14 pts), boolean chains 11, loops 1 (nesting depth added 23). 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.
WhisperModelManager.ModelManager (cognitive 57) frontend/src/components/WhisperModelManager.tsx:25— WhisperModelManager.ModelManager has cognitive complexity 57 (threshold 15). Drivers by points: if/else 22 (23 pts), ternaries 9 (16 pts), boolean chains 10, error handling 7, loops 1 (nesting depth added 8). Most of this is not in the body itself: 4 of the 57 points are its own statements and the rest belongs to 25 function items inside it that branch (reconcileCancellation::reconcile, a function literal at line 149, a function literal at line 141, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ConfigContext.ConfigProvider (cognitive 57) frontend/src/contexts/ConfigContext.tsx:100— ConfigContext.ConfigProvider has cognitive complexity 57 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 16, error handling 9 (11 pts), ternaries 3 (6 pts) (nesting depth added 12). None of this is in the body itself: all 57 points belong to 17 function literals inside it that branch (lines 232, 199, 183, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TranscriptContext.TranscriptProvider (cognitive 57) frontend/src/contexts/TranscriptContext.tsx:27— TranscriptContext.TranscriptProvider has cognitive complexity 57 (threshold 15). Drivers by points: if/else 22 (29 pts), boolean chains 18, error handling 4 (5 pts), ternaries 2 (3 pts), loops 2 (nesting depth added 9). None of this is in the body itself: all 57 points belong to 24 function literals inside it that branch (lines 188, 364, 232, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
useRecordingStart.useRecordingStart (cognitive 56) frontend/src/hooks/useRecordingStart.ts:43— useRecordingStart.useRecordingStart has cognitive complexity 56 (threshold 15). Drivers by points: if/else 15 (32 pts), ternaries 4 (14 pts), boolean chains 6, error handling 2 (4 pts) (nesting depth added 29). None of this is in the body itself: all 56 points belong to 2 function literals inside it that branch (lines 212, 310). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
main.get_summary (cognitive 55) REDACTED:369— main.get_summary has cognitive complexity 55 (threshold 15). Drivers by points: if/else 15 (37 pts), loops 2 (6 pts), error handling 3 (5 pts), boolean chains 4, ternaries 3 (nesting depth added 28). 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.
ModelSettingsModal.ModelSettingsModal (cognitive 55) frontend/src/components/ModelSettingsModal.tsx:112— ModelSettingsModal.ModelSettingsModal has cognitive complexity 55 (threshold 15). Drivers by points: boolean chains 108, if/else 53 (67 pts), ternaries 25 (33 pts), error handling 16 (21 pts), loops 1 (nesting depth added 27). 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. This shape REPEATS in the file: one other method here (ModelSettingsModal.ModelSettingsModal::handleSave) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both 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.
AudioPipeline::run (cognitive 53) frontend/src-tauri/src/audio/pipeline.rs:792— AudioPipeline::run has cognitive complexity 53 (threshold 15). Drivers by points: if/else 9 (35 pts), loops 3 (10 pts), match/switch 2 (7 pts), boolean chains 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.
RetranscribeDialog.RetranscribeDialog (cognitive 52) frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:54— RetranscribeDialog.RetranscribeDialog has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 19, if/else 16, ternaries 9 (14 pts), error handling 2 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 15 of the 52 points are its own statements and the rest belongs to 14 function items inside it that branch (handleStartRetranscription, a function literal at line 105, a function literal at line 128, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Block.BlockComponent::handleKeyDown (cognitive 49) frontend/src/components/AISummary/Block.tsx:107— Block.BlockComponent::handleKeyDown has cognitive complexity 49 (threshold 15). Drivers by points: if/else 18 (30 pts), boolean chains 16, ternaries 1 (3 pts) (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.
ImportAudioDialog.ImportAudioDialog (cognitive 48) frontend/src/components/ImportAudio/ImportAudioDialog.tsx:67— ImportAudioDialog.ImportAudioDialog has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 20, if/else 13 (16 pts), ternaries 7 (12 pts) (nesting depth added 8). Of this number, 20 points are the body's own statements and 28 belong to 12 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.
AudioDeviceMonitor::monitor_loop (cognitive 46) frontend/src-tauri/src/audio/device_monitor.rs:272— AudioDeviceMonitor::monitor_loop has cognitive complexity 46 (threshold 15). Drivers by points: if/else 11 (30 pts), match/switch 3 (9 pts), loops 3 (7 pts) (nesting depth added 29). 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.
TranscriptRecovery.TranscriptRecovery (cognitive 45) frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:34— TranscriptRecovery.TranscriptRecovery has cognitive complexity 45 (threshold 15). Drivers by points: if/else 8 (18 pts), ternaries 11 (15 pts), error handling 4 (7 pts), boolean chains 5 (nesting depth added 17). Of this number, 16 points are the body's own statements and 29 belong to 7 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.
UpdateDialog.UpdateDialog (cognitive 44) frontend/src/components/UpdateDialog.tsx:23— UpdateDialog.UpdateDialog has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 16, if/else 13 (15 pts), ternaries 5 (8 pts), error handling 3 (4 pts), match/switch 1 (nesting depth added 6). Most of this is not in the body itself: 15 of the 44 points are its own statements and the rest belongs to 9 function items inside it that branch (handleDownloadAndInstall, a function literal at line 89, a function literal at line 29, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SummaryService::process_transcript_background (cognitive 43) frontend/src-tauri/src/summary/service.rs:334— SummaryService::process_transcript_background has cognitive complexity 43 (threshold 15). Drivers by points: match/switch 13 (22 pts), if/else 15 (20 pts), boolean chains 1 (nesting depth added 14). 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.
useSummaryGeneration.useSummaryGeneration.handlePollingResult (cognitive 42) frontend/src/hooks/meeting-details/useSummaryGeneration.ts:170— useSummaryGeneration.useSummaryGeneration.handlePollingResult has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 7, ternaries 3 (7 pts), error handling 2 (5 pts) (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.
auto-detect-gpu.detectGPU (cognitive 40) REDACTED:19— auto-detect-gpu.detectGPU has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (33 pts), boolean chains 7 (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.
BuiltInModelManager.BuiltInModelManager (cognitive 37) frontend/src/components/BuiltInModelManager.tsx:38— BuiltInModelManager.BuiltInModelManager has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 22, if/else 7 (9 pts), error handling 4, ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 5 of the 37 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 290, fetchModels, downloadModel, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SidebarProvider.SidebarProvider (cognitive 37) frontend/src/components/Sidebar/SidebarProvider.tsx:78— SidebarProvider.SidebarProvider has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 6, error handling 4 (6 pts), ternaries 2 (5 pts) (nesting depth added 9). None of this is in the body itself: all 37 points belong to 6 function items inside it that branch (a function literal at line 216, a function literal at line 97, handleRecordingToggle, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DeviceSelection.DeviceSelection (cognitive 36) frontend/src/components/DeviceSelection.tsx:40— DeviceSelection.DeviceSelection has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 16, if/else 13, error handling 4, ternaries 3. Most of this is not in the body itself: 14 of the 36 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 93, getDeviceMetadata, a function literal at line 152, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
VirtualizedTranscriptView.VirtualizedTranscriptView (cognitive 36) frontend/src/components/VirtualizedTranscriptView.tsx:113— VirtualizedTranscriptView.VirtualizedTranscriptView has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 7 (15 pts), boolean chains 14, if/else 7 (nesting depth added 8). Of this number, 24 points are the body's own statements and 12 belong to 5 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.
BlockNoteSummaryView.BlockNoteSummaryView (cognitive 35) frontend/src/components/AISummary/BlockNoteSummaryView.tsx:68— BlockNoteSummaryView.BlockNoteSummaryView has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 12, error handling 3 (4 pts), ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 5 of the 35 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 170, 136, 90, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AudioMixer::mix (cognitive 34) frontend/src-tauri/src/audio_v2/mixer.rs:66— AudioMixer::mix has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 4 (7 pts), match/switch 1 (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.
ModelSettingsModal.ModelSettingsModal::handleSave (cognitive 30) frontend/src/components/ModelSettingsModal.tsx:617— ModelSettingsModal.ModelSettingsModal::handleSave has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 12 (15 pts), boolean chains 10, if/else 3, error handling 1 (2 pts) (nesting depth added 4). 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. This shape REPEATS in the file: one other method here (ModelSettingsModal.ModelSettingsModal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both 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.
page.MeetingDetailsContent (cognitive 29) frontend/src/app/meeting-details/page.tsx:23— page.MeetingDetailsContent has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 7, error handling 3, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 67, 197, 122, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
index.Sidebar::renderItem (cognitive 29) frontend/src/components/Sidebar/index.tsx:554— index.Sidebar::renderItem has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 11 (20 pts), boolean chains 8, if/else 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.
TranscriptView.TranscriptView (cognitive 29) frontend/src/components/TranscriptView.tsx:107— TranscriptView.TranscriptView has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 10, ternaries 6 (7 pts) (nesting depth added 3). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 263, 175, 130, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
generate-update-manifest-github.bundleFiles.forEach() (cognitive 29) scripts/generate-update-manifest-github.js:91— generate-update-manifest-github.bundleFiles.forEach() has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 9, error handling 1 (3 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.
TranscriptProcessor.process_transcript (cognitive 28) backend/app/transcript_processor.py:87— TranscriptProcessor.process_transcript has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (22 pts), error handling 2 (3 pts), boolean chains 2, 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.
SummaryModelSettings.SummaryModelSettings (cognitive 28) frontend/src/components/SummaryModelSettings.tsx:15— SummaryModelSettings.SummaryModelSettings has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (9 pts), error handling 4 (8 pts) (nesting depth added 8). None of this is in the body itself: all 28 points belong to 3 function items inside it that branch (a function literal at line 27, a function literal at line 75, handleSaveModelConfig). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
useAutoScroll.useAutoScroll (cognitive 28) frontend/src/hooks/useAutoScroll.ts:38— useAutoScroll.useAutoScroll has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 4 (nesting depth added 9). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 180, 132, 94, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
useModelConfiguration.useModelConfiguration (cognitive 27) frontend/src/hooks/meeting-details/useModelConfiguration.ts:11— useModelConfiguration.useModelConfiguration has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (9 pts), error handling 3 (7 pts) (nesting depth added 8). None of this is in the body itself: all 27 points belong to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
page.Home (cognitive 26) frontend/src/app/page.tsx:24— page.Home has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3 (6 pts), boolean chains 5, error handling 4 (nesting depth added 6). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (handleRecovery, a function literal at line 71, a function literal at line 109, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ParallelProcessor::create_worker (cognitive 24) frontend/src-tauri/src/whisper_engine/parallel_processor.rs:199— ParallelProcessor::create_worker has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 2 (5 pts), loops 2 (3 pts), boolean chains 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.
llama_helper::main (cognitive 24) llama-helper/src/main.rs:548— llama_helper::main has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (14 pts), match/switch 3 (9 pts), loops 1 (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.
SummaryPanel.SummaryPanel::persistLatestLanguageSelection (cognitive 24) frontend/src/components/MeetingDetails/SummaryPanel.tsx:141— SummaryPanel.SummaryPanel::persistLatestLanguageSelection has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 12). 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.
DownloadProgressToast.useDownloadProgressToast (cognitive 24) frontend/src/components/shared/DownloadProgressToast.tsx:127— DownloadProgressToast.useDownloadProgressToast has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 6 (10 pts), if/else 7 (8 pts), boolean chains 5, match/switch 1 (nesting depth added 5). None of this is in the body itself: all 24 points belong to 5 function literals inside it that branch (lines 306, 200, 227, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DatabaseManager::new_from_app_handle (cognitive 23) frontend/src-tauri/src/database/manager.rs:44— DatabaseManager::new_from_app_handle has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 5 (10 pts), boolean chains 1 (nesting depth added 13). 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.
ModelState::generate (cognitive 23) llama-helper/src/main.rs:348— ModelState::generate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 3 (4 pts), match/switch 1 (2 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.
ParakeetModelManager.ModelCard (cognitive 23) frontend/src/components/ParakeetModelManager.tsx:478— ParakeetModelManager.ModelCard has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 17, ternaries 4 (5 pts), if/else 1 (nesting depth added 1). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
PreferenceSettings.PreferenceSettings (cognitive 23) frontend/src/components/PreferenceSettings.tsx:11— PreferenceSettings.PreferenceSettings has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5, error handling 2, ternaries 1 (2 pts), match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 56, a function literal at line 36, a function literal at line 77, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ParakeetModel::decode_sequence (cognitive 22) frontend/src-tauri/src/parakeet_engine/model.rs:349— ParakeetModel::decode_sequence has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, 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.
AudioLevelMonitor::find_device_by_name (cognitive 20) frontend/src-tauri/src/audio/level_monitor.rs:140— AudioLevelMonitor::find_device_by_name has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (4 pts) (nesting depth added 12). 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.
AnalyticsConsentSwitch.AnalyticsConsentSwitch (cognitive 20) frontend/src/components/AnalyticsConsentSwitch.tsx:13— AnalyticsConsentSwitch.AnalyticsConsentSwitch has cognitive complexity 20 (threshold 15). Drivers by points: error handling 7 (11 pts), if/else 6, boolean chains 2, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (performToggle, a function literal at line 23, handleToggle, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
WhisperModelManager.ModelCard (cognitive 20) frontend/src/components/WhisperModelManager.tsx:577— WhisperModelManager.ModelCard has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 14, ternaries 4 (5 pts), if/else 1 (nesting depth added 1). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
DownloadProgressToast.DownloadToastContent (cognitive 20) frontend/src/components/shared/DownloadProgressToast.tsx:52— DownloadProgressToast.DownloadToastContent has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9 (18 pts), boolean chains 2 (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.
ContinuousVadProcessor::process_chunk (cognitive 19) frontend/src-tauri/src/audio/vad.rs:240— ContinuousVadProcessor::process_chunk has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (2 pts), 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.
LanguagePickerPopover.LanguagePickerPopover (cognitive 19) frontend/src/components/LanguagePickerPopover.tsx:15— LanguagePickerPopover.LanguagePickerPopover has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, if/else 3, ternaries 2. Of this number, 11 points are the body's own statements and 8 belong to 7 function literals inside it that branch. 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.
PermissionWarning.PermissionWarning (cognitive 19) frontend/src/components/PermissionWarning.tsx:14— PermissionWarning.PermissionWarning has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, error handling 2 (4 pts), if/else 4 (nesting depth added 2). Of this number, 13 points are the body's own statements and 6 belong to 2 function items inside it that branch. 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.
LoudnessNormalizer::normalize_loudness (cognitive 18) frontend/src-tauri/src/audio/audio_processing.rs:186— LoudnessNormalizer::normalize_loudness has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 1, loops 1 (nesting depth added 10). 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.
LegacyDatabaseImport.LegacyDatabaseImport (cognitive 18) frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx:17— LegacyDatabaseImport.LegacyDatabaseImport has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (6 pts), boolean chains 5, if/else 4, error handling 3 (nesting depth added 2). Of this number, 11 points are the body's own statements and 7 belong to 3 function items inside it that branch. 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.
useRecordingStart.useRecordingStart.handleRecordingStart (cognitive 18) frontend/src/hooks/useRecordingStart.ts:119— useRecordingStart.useRecordingStart.handleRecordingStart has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (4 pts), boolean chains 2, error handling 1 (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.
HardwareProfile::calculate_performance_tier (cognitive 17) frontend/src-tauri/src/audio/hardware_detector.rs:121— HardwareProfile::calculate_performance_tier has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, match/switch 1 (nesting depth added 4). 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.
ChunkProgressDisplay.ChunkProgressDisplay (cognitive 17) frontend/src/components/ChunkProgressDisplay.tsx:31— ChunkProgressDisplay.ChunkProgressDisplay has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 4, match/switch 2, ternaries 2. Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 204, formatDuration, formatTimeRemaining, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TranscriptSettings.TranscriptSettings (cognitive 17) frontend/src/components/TranscriptSettings.tsx:24— TranscriptSettings.TranscriptSettings has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 5, error handling 1. Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 36, fetchApiKey, a function literal at line 112, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
RecordingSettings.RecordingSettings (cognitive 17) frontend/src/components/RecordingSettings.tsx:23— RecordingSettings.RecordingSettings has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, error handling 6 (7 pts), ternaries 1 (2 pts), if/else 1 (nesting depth added 2). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (savePreferences, a function literal at line 39, a function literal at line 62, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TranscriptView.cleanRepetitions (cognitive 17) frontend/src/components/TranscriptView.tsx:35— TranscriptView.cleanRepetitions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (3 pts), boolean chains 2 (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.
PermissionRow.PermissionRow (cognitive 17) frontend/src/components/onboarding/shared/PermissionRow.tsx:7— PermissionRow.PermissionRow has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (12 pts), boolean chains 3, if/else 2 (nesting depth added 4). Of this number, 15 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.
useTranscriptRecovery.useTranscriptRecovery.recoverMeeting (cognitive 17) frontend/src/hooks/useTranscriptRecovery.ts:110— useTranscriptRecovery.useTranscriptRecovery.recoverMeeting has cognitive complexity 17 (threshold 15). Drivers by points: error handling 5 (8 pts), if/else 6, boolean chains 3 (nesting depth added 3). Of this number, 14 points are the body's own statements and 3 belong to one function literal 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.
layout.RootLayout (cognitive 16) frontend/src/app/layout.tsx:66— layout.RootLayout has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 1, ternaries 1. Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 131, 166, 82, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MeetingDetailsSplitView.MeetingDetailsSplitView (cognitive 16) frontend/src/components/MeetingDetails/MeetingDetailsSplitView.tsx:44— MeetingDetailsSplitView.MeetingDetailsSplitView has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 3, boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 89, 74, 80). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SummaryGeneratorButtonGroup.SummaryGeneratorButtonGroup (cognitive 16) frontend/src/components/MeetingDetails/SummaryGeneratorButtonGroup.tsx:41— SummaryGeneratorButtonGroup.SummaryGeneratorButtonGroup has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (11 pts), boolean chains 3, if/else 2 (nesting depth added 6). Of this number, 15 points are the body's own statements and 1 belongs to one function literal 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.
Change-coupling hub: REDACTED → tray.rs, REDACTED, TranscriptView.tsx frontend/src/app/page.tsx— `frontend/src/app/page.tsx` changes together with 3 other files — `frontend/src-tauri/src/tray.rs`, `frontend/src/app/settings/page.tsx`, `frontend/src/components/TranscriptView.tsx` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Near-duplicate member family (3 members, 29 shared lines) · ×1
Near-duplicate member family (3 members, 29 shared lines) frontend/src-tauri/src/anthropic/anthropic.rs:74— frontend/src-tauri/src/anthropic/anthropic.rs:74-163 | frontend/src-tauri/src/groq/groq.rs:72-157 | frontend/src-tauri/src/openai/openai.rs:104-186 — These 3 members are variants of one another: a block of 29 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
Near-duplicate member pair (133 shared lines) frontend/src-tauri/src/audio/import.rs:319— frontend/src-tauri/src/audio/import.rs:319-675 | frontend/src-tauri/src/audio/retranscription.rs:180-500 — These two members are variants of one another: 133 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 (125 shared lines) frontend/src-tauri/src/audio/recording_commands.rs:310— frontend/src-tauri/src/audio/recording_commands.rs:310-483 | frontend/src-tauri/src/audio/recording_commands.rs:500-673 — These two members are variants of one another: 125 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 (86 shared lines) frontend/src-tauri/src/lib_old_complex.rs:864— frontend/src-tauri/src/lib_old_complex.rs:864-1110 | frontend/src-tauri/src/lib_old_complex.rs:1115-1304 — These two members are variants of one another: 86 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 (79 shared lines) frontend/src-tauri/src/audio/core-old.rs:699— frontend/src-tauri/src/audio/core-old.rs:699-859 | frontend/src-tauri/src/audio/devices/platform/windows.rs:97-257 — These two members are variants of one another: 79 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 (36 shared lines) frontend/src-tauri/src/audio/core-old.rs:118— frontend/src-tauri/src/audio/core-old.rs:118-204 | frontend/src-tauri/src/audio/devices/platform/windows.rs:8-94 — These two members are variants of one another: 36 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.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) frontend/src-tauri/src/audio/core-old.rs:305— frontend/src-tauri/src/audio/core-old.rs:305-349 | frontend/src-tauri/src/audio/devices/speakers.rs:8-46 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) backend/app/db.py:538— backend/app/db.py:538-579 | backend/app/db.py:660-699 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) frontend/src-tauri/src/audio/import.rs:755— frontend/src-tauri/src/audio/import.rs:755-795 | frontend/src-tauri/src/audio/import.rs:801-841 | frontend/src-tauri/src/audio/retranscription.rs:526-578 | frontend/src-tauri/src/audio/retranscription.rs:628-680 — 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 (71 lines × 2) frontend/src-tauri/src/audio/stream.rs:242— frontend/src-tauri/src/audio/stream.rs:242-312 | frontend/src-tauri/src/audio_v2/stream.rs:90-160 — `frontend/src-tauri/src/audio/stream.rs` and `frontend/src-tauri/src/audio_v2/stream.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 90 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 (60–63 lines × 2) frontend/src-tauri/src/audio/import.rs:561— frontend/src-tauri/src/audio/import.rs:561-623 | frontend/src-tauri/src/audio/retranscription.rs:354-413 — before extracting anything, compare `frontend/src-tauri/src/audio/import.rs` and `frontend/src-tauri/src/audio/retranscription.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 174 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 (59–60 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:387— frontend/src-tauri/src/audio/recording_commands.rs:387-446 | frontend/src-tauri/src/audio/recording_commands.rs:575-633 — 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 (40–42 lines × 2) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:552— frontend/src-tauri/src/whisper_engine/whisper_engine.rs:552-593 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:669-708 — 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 (40–41 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:313— frontend/src-tauri/src/audio/recording_commands.rs:313-353 | frontend/src-tauri/src/audio/recording_commands.rs:504-543 — 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 (34 lines × 2) frontend/src-tauri/src/audio/core-old.rs:316— frontend/src-tauri/src/audio/core-old.rs:316-349 | frontend/src-tauri/src/audio/devices/speakers.rs:13-46 — 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 lines × 2) frontend/src-tauri/src/summary/summary_engine/sidecar.rs:558— frontend/src-tauri/src/summary/summary_engine/sidecar.rs:558-576 | frontend/src-tauri/src/summary/summary_engine/sidecar.rs:606-624 — 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 (18 lines × 5) frontend/src-tauri/src/summary/summary_engine/commands.rs:76— frontend/src-tauri/src/summary/summary_engine/commands.rs:76-93 | frontend/src-tauri/src/summary/summary_engine/commands.rs:106-123 | frontend/src-tauri/src/summary/summary_engine/commands.rs:136-153 | frontend/src-tauri/src/summary/summary_engine/commands.rs:276-293 | frontend/src-tauri/src/summary/summary_engine/commands.rs:315-332 — all 5 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 (14–16 lines × 3) frontend/src-tauri/src/audio/playback_monitor.rs:36— frontend/src-tauri/src/audio/playback_monitor.rs:36-51 | frontend/src-tauri/src/audio/playback_monitor.rs:83-96 | frontend/src-tauri/src/audio/playback_monitor.rs:122-135 — 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 (15 lines × 4) frontend/src-tauri/src/audio/recording_preferences.rs:218— frontend/src-tauri/src/audio/recording_preferences.rs:218-232 | frontend/src-tauri/src/database/commands.rs:252-266 | frontend/src-tauri/src/parakeet_engine/commands.rs:551-565 | frontend/src-tauri/src/whisper_engine/commands.rs:542-556 — `frontend/src-tauri/src/parakeet_engine/commands.rs` and `frontend/src-tauri/src/whisper_engine/commands.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 7 separate duplicated blocks between them, totalling at least 93 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–15 lines × 3) frontend/src-tauri/src/audio/audio_processing.rs:632— frontend/src-tauri/src/audio/audio_processing.rs:632-646 | frontend/src-tauri/src/audio/audio_processing.rs:673-685 | frontend/src-tauri/src/audio/audio_processing.rs:708-719 — 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 (13–14 lines × 2) frontend/src-tauri/src/audio/import.rs:729— frontend/src-tauri/src/audio/import.rs:729-742 | frontend/src-tauri/src/audio/retranscription.rs:451-463 — before extracting anything, compare `frontend/src-tauri/src/audio/import.rs` and `frontend/src-tauri/src/audio/retranscription.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 174 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 (12–13 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:1554— frontend/src-tauri/src/audio/recording_commands.rs:1554-1565 | frontend/src-tauri/src/audio/recording_commands.rs:1607-1619 — 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 (11–13 lines × 2) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:647— frontend/src-tauri/src/whisper_engine/whisper_engine.rs:647-657 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:805-817 — 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 × 4) frontend/src-tauri/src/api/api.rs:1050— frontend/src-tauri/src/api/api.rs:1050-1061 | frontend/src-tauri/src/database/commands.rs:263-274 | frontend/src-tauri/src/parakeet_engine/commands.rs:562-573 | frontend/src-tauri/src/whisper_engine/commands.rs:553-564 — `frontend/src-tauri/src/parakeet_engine/commands.rs` and `frontend/src-tauri/src/whisper_engine/commands.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 7 separate duplicated blocks between them, totalling at least 93 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–12 lines × 2) frontend/src-tauri/src/audio/recording_saver.rs:98— frontend/src-tauri/src/audio/recording_saver.rs:98-109 | frontend/src-tauri/src/audio/recording_saver_old.rs:85-94 — 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 × 5) frontend/src-tauri/src/audio/core-old.rs:875— frontend/src-tauri/src/audio/core-old.rs:875-885 | frontend/src-tauri/src/audio/core-old.rs:890-900 | frontend/src-tauri/src/audio/core-old.rs:907-917 | frontend/src-tauri/src/audio/devices/configuration.rs:127-137 | frontend/src-tauri/src/audio/devices/configuration.rs:159-169 — before extracting anything, compare `frontend/src-tauri/src/audio/core-old.rs` and `frontend/src-tauri/src/audio/devices/configuration.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 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 (8–11 lines × 2) frontend/src-tauri/src/audio/core-old.rs:253— frontend/src-tauri/src/audio/core-old.rs:253-260 | frontend/src-tauri/src/audio/devices/platform/macos.rs:11-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 (10 lines × 3) frontend/src-tauri/src/audio/stream.rs:472— frontend/src-tauri/src/audio/stream.rs:472-481 | frontend/src-tauri/src/audio/system_audio_stream.rs:189-198 | frontend/src-tauri/src/audio_v2/stream.rs:355-364 — `frontend/src-tauri/src/audio/stream.rs` and `frontend/src-tauri/src/audio_v2/stream.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 90 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) frontend/src-tauri/src/audio/import.rs:377— frontend/src-tauri/src/audio/import.rs:377-382 | frontend/src-tauri/src/audio/import.rs:406-411 — 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 (20–23 lines × 2) backend/app/db.py:810— backend/app/db.py:810-829 | backend/app/db.py:833-855 — 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 × 5) backend/app/db.py:200— backend/app/db.py:200-207 | backend/app/db.py:274-281 | backend/app/db.py:320-327 | backend/app/db.py:618-625 | backend/app/db.py:739-746 — all 5 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.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `REDACTED`, `REDACTED`, `REDACTED`, `REDACTED`, `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Duplication concentrated across 6 sibling directories (19 clone groups) frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:75— 19 duplicated blocks under frontend/src/ have copies in at least two of the sibling directories app, components, constants, contexts, hooks, services — 11 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 19 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (7 clone groups) frontend/src/components/ImportAudio/ImportAudioDialog.tsx:203— 7 duplicated blocks under frontend/src/components/ have copies in at least two of the sibling directories DatabaseImport, ImportAudio, MeetingDetails, Sidebar, onboarding, shared — 6 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (508 matched lines × 2 locations) · ×1
Duplicated block with local edits (508 matched lines × 2 locations) frontend/src/components/ParakeetModelManager.tsx:16— frontend/src/components/ParakeetModelManager.tsx:16 · frontend/src/components/WhisperModelManager.tsx:18 — the two spans are one implementation copied and then locally edited — 2778 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.
R10 · Code Duplication· Duplicated block with local edits (86 matched lines × 2 locations) · ×1
Duplicated block with local edits (86 matched lines × 2 locations) frontend/src/components/ui/dialog.tsx:9— frontend/src/components/ui/dialog.tsx:9 · frontend/src/components/ui/sheet.tsx:10 — the two spans are one implementation copied and then locally edited — 446 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.
R10 · Code Duplication· Duplicated block with local edits (83 matched lines × 2 locations) · ×1
Duplicated block with local edits (83 matched lines × 2 locations) frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:267— frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:267 · frontend/src/components/UpdateDialog.tsx:181 — the two spans are one implementation copied and then locally edited — 409 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 (48 lines × 2 locations) frontend/src/hooks/useRecordingStart.ts:229— frontend/src/hooks/useRecordingStart.ts:229 · frontend/src/hooks/useRecordingStart.ts:328 — 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 (44 lines × 2 locations) frontend/src/lib/parakeet.ts:162— frontend/src/lib/parakeet.ts:162 · frontend/src/lib/whisper.ts:278 — 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.
R10 · Code Duplication· Duplicated block with local edits (43 matched lines × 2 locations) · ×1
Duplicated block with local edits (43 matched lines × 2 locations) frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:75— frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:75 · frontend/src/hooks/useImportAudio.ts:67 — the two spans are one implementation copied and then locally edited — 261 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 (37 lines × 2 locations) frontend/src/components/ImportAudio/ImportAudioDialog.tsx:203— frontend/src/components/ImportAudio/ImportAudioDialog.tsx:203 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:243 — 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 (31 lines × 2 locations) frontend/src/components/DeviceSelection.tsx:316— frontend/src/components/DeviceSelection.tsx:316 · frontend/src/components/DeviceSelection.tsx:384 — 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 (27 lines × 2 locations) frontend/src/hooks/meeting-details/useCopyOperations.ts:26— frontend/src/hooks/meeting-details/useCopyOperations.ts:26 · frontend/src/hooks/meeting-details/useSummaryGeneration.ts:402 — 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 (22 lines × 2 locations) frontend/src/components/SummaryModelSettings.tsx:32— frontend/src/components/SummaryModelSettings.tsx:32 · frontend/src/hooks/meeting-details/useModelConfiguration.ts:37 — 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 (21 lines × 2 locations) frontend/src/services/indexedDBService.ts:343— frontend/src/services/indexedDBService.ts:343 · frontend/src/services/indexedDBService.ts:393 — 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 (19 lines × 3 locations) frontend/src/hooks/useRecordingStart.ts:126— frontend/src/hooks/useRecordingStart.ts:126 · frontend/src/hooks/useRecordingStart.ts:218 · frontend/src/hooks/useRecordingStart.ts:317 — 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 (16 lines × 3 locations) frontend/src/components/BuiltInModelManager.tsx:109— frontend/src/components/BuiltInModelManager.tsx:109 · frontend/src/components/BuiltInModelManager.tsx:130 · frontend/src/components/BuiltInModelManager.tsx:150 — all 3 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 (14 lines × 3 locations) frontend/src/app/layout.tsx:194— frontend/src/app/layout.tsx:194 · frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:181 · frontend/src/hooks/useImportAudio.ts:142 — 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 (14 lines × 2 locations) frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:277— frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:277 · frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:293 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Complex function ModelSettingsModal (cyclomatic 81, cognitive 72) frontend/src/components/ModelSettingsModal.tsx:112— ModelSettingsModal has cyclomatic complexity 81 and cognitive complexity 72; 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.
Complex function (anonymous) (cyclomatic 41, cognitive 62) frontend/src/hooks/useRecordingStop.ts:121— (anonymous) has cyclomatic complexity 41 and cognitive complexity 62; 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 handleKeyDown (cyclomatic 35, cognitive 49) frontend/src/components/AISummary/Block.tsx:107— handleKeyDown has cyclomatic complexity 35 and cognitive complexity 49; 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 RecordingControls (cyclomatic 35, cognitive 23) frontend/src/components/RecordingControls.tsx:32— RecordingControls has cyclomatic complexity 35 and cognitive complexity 23; 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.
Complex function ModelCard (cyclomatic 33, cognitive 25) frontend/src/components/ParakeetModelManager.tsx:478— ModelCard has cyclomatic complexity 33 and cognitive complexity 25; 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.
Complex function VirtualizedTranscriptView (cyclomatic 33, cognitive 20) frontend/src/components/VirtualizedTranscriptView.tsx:113— VirtualizedTranscriptView has cyclomatic complexity 33 and cognitive complexity 20; 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.
Complex function (anonymous) (cyclomatic 31, cognitive 29) scripts/generate-update-manifest-github.js:91— (anonymous) has cyclomatic complexity 31 and cognitive complexity 29; 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.
Complex function (anonymous) (cyclomatic 31, cognitive 23) frontend/src/components/BuiltInModelManager.tsx:290— (anonymous) has cyclomatic complexity 31 and cognitive complexity 23; 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.
Complex function (anonymous) (cyclomatic 29, cognitive 44) frontend/src/hooks/meeting-details/useSummaryGeneration.ts:170— (anonymous) has cyclomatic complexity 29 and cognitive complexity 44; 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 handleSave (cyclomatic 28, cognitive 30) frontend/src/components/ModelSettingsModal.tsx:617— handleSave has cyclomatic complexity 28 and cognitive complexity 30; 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 ModelCard (cyclomatic 26, cognitive 23) frontend/src/components/WhisperModelManager.tsx:577— ModelCard has cyclomatic complexity 26 and cognitive complexity 23; 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.
Complex function ImportAudioDialog (cyclomatic 25, cognitive 21) frontend/src/components/ImportAudio/ImportAudioDialog.tsx:67— ImportAudioDialog has cyclomatic complexity 25 and cognitive complexity 21; 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.
Complex function renderItem (cyclomatic 25, cognitive 20) frontend/src/components/Sidebar/index.tsx:554— renderItem has cyclomatic complexity 25 and cognitive complexity 20; 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.
Complex function poll (cyclomatic 21, cognitive 21) frontend/src/components/Sidebar/SidebarProvider.tsx:216— poll has cyclomatic complexity 21 and cognitive complexity 21; 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 RetranscribeDialog (cyclomatic 21, cognitive 15) frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:54— RetranscribeDialog has cyclomatic complexity 21 and cognitive complexity 15; 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.
Complex function detectGPU (cyclomatic 20, cognitive 40) REDACTED:19— detectGPU has cyclomatic complexity 20 and cognitive complexity 40; 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 fetchModelConfig (cyclomatic 20, cognitive 27) frontend/src/hooks/meeting-details/useModelConfiguration.ts:23— fetchModelConfig has cyclomatic complexity 20 and cognitive complexity 27; 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 PermissionWarning (cyclomatic 20, cognitive 17) frontend/src/components/PermissionWarning.tsx:14— PermissionWarning has cyclomatic complexity 20 and cognitive complexity 17; 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.
Complex function TranscriptSettings (cyclomatic 20, cognitive 16) frontend/src/components/TranscriptSettings.tsx:24— TranscriptSettings has cyclomatic complexity 20 and cognitive complexity 16; 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.
Complex function (anonymous) (cyclomatic 19, cognitive 25) frontend/src/components/SummaryModelSettings.tsx:27— (anonymous) has cyclomatic complexity 19 and cognitive complexity 25; 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.
R3 · Large Files· frontend/src/components/ModelSettingsModal.tsx · ×1
frontend/src/components/ModelSettingsModal.tsx: 1287 lines of code frontend/src/components/ModelSettingsModal.tsx:1— frontend/src/components/ModelSettingsModal.tsx has 1287 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· frontend/src/components/Sidebar/index.tsx · ×1
frontend/src/components/Sidebar/index.tsx: 783 lines of code frontend/src/components/Sidebar/index.tsx:1— frontend/src/components/Sidebar/index.tsx has 783 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· frontend/src/lib/analytics.ts · ×1
frontend/src/lib/analytics.ts: 738 lines of code frontend/src/lib/analytics.ts:1— frontend/src/lib/analytics.ts has 738 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· frontend/src/components/WhisperModelManager.tsx · ×1
frontend/src/components/WhisperModelManager.tsx: 729 lines of code frontend/src/components/WhisperModelManager.tsx:1— frontend/src/components/WhisperModelManager.tsx has 729 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· frontend/src/components/AISummary/index.tsx · ×1
frontend/src/components/AISummary/index.tsx: 725 lines of code frontend/src/components/AISummary/index.tsx:1— frontend/src/components/AISummary/index.tsx has 725 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· frontend/src/components/ParakeetModelManager.tsx · ×1
frontend/src/components/ParakeetModelManager.tsx: 629 lines of code frontend/src/components/ParakeetModelManager.tsx:1— frontend/src/components/ParakeetModelManager.tsx has 629 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· frontend/src/contexts/OnboardingContext.tsx · ×1
frontend/src/contexts/OnboardingContext.tsx: 577 lines of code frontend/src/contexts/OnboardingContext.tsx:1— frontend/src/contexts/OnboardingContext.tsx has 577 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· frontend/src/hooks/meeting-details/useSummaryGeneration.ts · ×1
frontend/src/hooks/meeting-details/useSummaryGeneration.ts: 552 lines of code frontend/src/hooks/meeting-details/useSummaryGeneration.ts:1— frontend/src/hooks/meeting-details/useSummaryGeneration.ts has 552 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· frontend/src/components/onboarding/steps/DownloadProgressStep.tsx · ×1
frontend/src/components/onboarding/steps/DownloadProgressStep.tsx: 505 lines of code frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:1— frontend/src/components/onboarding/steps/DownloadProgressStep.tsx has 505 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· frontend/src/contexts/ConfigContext.tsx · ×1
frontend/src/contexts/ConfigContext.tsx: 493 lines of code frontend/src/contexts/ConfigContext.tsx:1— frontend/src/contexts/ConfigContext.tsx has 493 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· frontend/src/components/RecordingControls.tsx · ×1
frontend/src/components/RecordingControls.tsx: 475 lines of code frontend/src/components/RecordingControls.tsx:1— frontend/src/components/RecordingControls.tsx has 475 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· frontend/src/contexts/TranscriptContext.tsx · ×1
frontend/src/contexts/TranscriptContext.tsx: 464 lines of code frontend/src/contexts/TranscriptContext.tsx:1— frontend/src/contexts/TranscriptContext.tsx has 464 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· frontend/src/components/BuiltInModelManager.tsx · ×1
frontend/src/components/BuiltInModelManager.tsx: 458 lines of code frontend/src/components/BuiltInModelManager.tsx:1— frontend/src/components/BuiltInModelManager.tsx has 458 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· frontend/src/components/ImportAudio/ImportAudioDialog.tsx · ×1
frontend/src/components/ImportAudio/ImportAudioDialog.tsx: 438 lines of code frontend/src/components/ImportAudio/ImportAudioDialog.tsx:1— frontend/src/components/ImportAudio/ImportAudioDialog.tsx has 438 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· frontend/src/hooks/useRecordingStop.ts · ×1
frontend/src/hooks/useRecordingStop.ts: 406 lines of code frontend/src/hooks/useRecordingStop.ts:1— frontend/src/hooks/useRecordingStop.ts has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No test script — test ✗ · lint ✓ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~294 LoC) frontend/src/components/ChunkProgressDisplay.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/hooks/useProcessingProgress.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~275 LoC) frontend/src/hooks/useAudioPlayer.ts— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~264 LoC) frontend/src/hooks/useProcessingProgress.ts— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~231 LoC) frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~178 LoC) frontend/src/components/ui/form.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (frontend/src/components/molecules/form-components/form-input-item.tsx, frontend/src/components/molecules/form-components/form-input-switch.tsx, frontend/src/components/molecules/form-components/form-select-item.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~169 LoC) frontend/src/hooks/meeting-details/useModelConfiguration.ts— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~150 LoC) frontend/src/components/DatabaseImport/HomebrewDatabaseDetector.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~140 LoC) frontend/src/components/ui/sheet.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~132 LoC) frontend/src/components/molecules/form-components/form-input-item.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~130 LoC) frontend/src/components/ModelDownloadProgress.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~105 LoC) frontend/src/components/BluetoothPlaybackWarning.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~98 LoC) frontend/src/lib/builtin-ai.ts— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~92 LoC) frontend/src/components/ConsoleToggle.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~90 LoC) frontend/src/components/molecules/form-components/form-select-item.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~59 LoC) frontend/src/components/molecules/form-components/form-input-switch.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~35 LoC) frontend/src/components/CustomDialog.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~28 LoC) frontend/src/components/ui/progress.tsx— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~27 LoC) frontend/src-tauri/src/audio/system_audio_types.ts— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~25 LoC) frontend/src/constants/modelDefaults.ts— no import path from any entry point (9 application, 8 tooling, 11 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
X1 · Async correctness· Task from `asyncio.create_task` is not kept · ×1
Task from `asyncio.create_task` is not kept backend/app/transcript_processor.py:305— The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
Interpolated log message defeats structured logging backend/app/db.py:40— `error` at line 40 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:198— `info` at line 198 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:202— `error` at line 202 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:206— `error` at line 206 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:233— `error` at line 233 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:257— `error` at line 257 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:269— `warning` at line 269 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:272— `debug` at line 272 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:276— `error` at line 276 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:280— `error` at line 280 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:318— `info` at line 318 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:322— `error` at line 322 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:326— `error` at line 326 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:379— `info` at line 379 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:386— `error` at line 386 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:409— `error` at line 409 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:451— `error` at line 451 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:495— `warning` at line 495 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:513— `error` at line 513 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:518— `info` at line 518 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:523— `error` at line 523 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:527— `error` at line 527 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:570— `info` at line 570 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:574— `error` at line 574 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging backend/app/db.py:578— `error` at line 578 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Duplicated predicate frontend/src/components/ParakeetModelManager.tsx:129— `!throttleData || now - throttleData.timestamp > 300 || Math.abs(progress - throttleData.progress) >= 5` appears character-identically in 2 files — frontend/src/components/ParakeetModelManager.tsx, frontend/src/components/WhisperModelManager.tsx. 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 frontend/src/components/ModelSettingsModal.tsx:271— `data.provider !== 'ollama' && !data.apiKey` appears character-identically in 2 files — frontend/src/components/ModelSettingsModal.tsx, frontend/src/components/Sidebar/index.tsx. 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 frontend/src/components/ImportAudio/ImportAudioDialog.tsx:175— `isParakeetModel && selectedLang !== 'auto'` appears character-identically in 2 files — frontend/src/components/ImportAudio/ImportAudioDialog.tsx, frontend/src/components/MeetingDetails/RetranscribeDialog.tsx. 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 frontend/src/components/ModelSettingsModal.tsx:610— `localStorage.getItem('providerModelMap') || '{}'` appears character-identically in 2 files — frontend/src/components/ModelSettingsModal.tsx, frontend/src/contexts/ConfigContext.tsx. 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 frontend/src/components/ImportAudio/ImportAudioDialog.tsx:170— `m.provider === provider && m.name === name` appears character-identically in 2 files — frontend/src/components/ImportAudio/ImportAudioDialog.tsx, frontend/src/components/MeetingDetails/RetranscribeDialog.tsx. 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 frontend/src/components/ImportAudio/ImportAudioDialog.tsx:260— `progress?.message || 'Processing audio...'` appears character-identically in 2 files — frontend/src/components/ImportAudio/ImportAudioDialog.tsx, frontend/src/components/MeetingDetails/RetranscribeDialog.tsx. 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 frontend/src/components/ParakeetModelManager.tsx:367— `selectedModel === modelName && onModelSelect` appears character-identically in 2 files — frontend/src/components/ParakeetModelManager.tsx, frontend/src/components/WhisperModelManager.tsx. 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 frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:274— `selectedSummaryModel && model === selectedSummaryModel` appears character-identically in 2 files — frontend/src/components/onboarding/steps/DownloadProgressStep.tsx, frontend/src/contexts/OnboardingContext.tsx. 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 frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:289— `status === 'completed' || progress >= 100` appears character-identically in 3 files — frontend/src/components/onboarding/steps/DownloadProgressStep.tsx, frontend/src/components/shared/DownloadProgressToast.tsx, frontend/src/contexts/OnboardingContext.tsx. 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 frontend/src/components/MeetingDetails/SummaryGeneratorButtonGroup.tsx:81— `summaryStatus === 'processing' || summaryStatus === 'summarizing' || summaryStatus === 'regenerating'` appears character-identically in 2 files — frontend/src/components/MeetingDetails/SummaryGeneratorButtonGroup.tsx, frontend/src/components/MeetingDetails/SummaryPanel.tsx. 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 frontend/src/components/ParakeetModelManager.tsx:498— `typeof model.status === 'object' && 'Corrupted' in model.status` appears character-identically in 2 files — frontend/src/components/ParakeetModelManager.tsx, frontend/src/components/WhisperModelManager.tsx. 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 frontend/src/components/ParakeetModelManager.tsx:500— `typeof model.status === 'object' && 'Downloading' in model.status` appears character-identically in 2 files — frontend/src/components/ParakeetModelManager.tsx, frontend/src/components/WhisperModelManager.tsx. 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 frontend/src/components/ParakeetModelManager.tsx:497— `typeof model.status === 'object' && 'Error' in model.status` appears character-identically in 2 files — frontend/src/components/ParakeetModelManager.tsx, frontend/src/components/WhisperModelManager.tsx. 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 frontend/src/lib/parakeet.ts:127— `typeof status === 'object' && 'Downloading' in status` appears character-identically in 2 files — frontend/src/lib/parakeet.ts, frontend/src/lib/whisper.ts. 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 frontend/src/lib/parakeet.ts:128— `typeof status === 'object' && 'Error' in status` appears character-identically in 2 files — frontend/src/lib/parakeet.ts, frontend/src/lib/whisper.ts. 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 frontend/src-tauri/src/audio/transcription/engine.rs:257— `config.provider == "localWhisper" && !config.model.is_empty()` appears character-identically in 2 files — frontend/src-tauri/src/audio/transcription/engine.rs, frontend/src-tauri/src/whisper_engine/commands.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 frontend/src-tauri/src/audio/core-old.rs:742— `config.sample_format() == cpal::SampleFormat::F32 && config.channels() == 2` appears character-identically in 2 files — frontend/src-tauri/src/audio/core-old.rs, frontend/src-tauri/src/audio/devices/platform/windows.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 frontend/src-tauri/src/audio/core-old.rs:720— `name == base_name || name.contains(base_name)` appears character-identically in 2 files — frontend/src-tauri/src/audio/core-old.rs, frontend/src-tauri/src/audio/devices/platform/windows.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 frontend/src-tauri/src/audio/device_detection.rs:357— `name_lower.contains(".hfp") || name_lower.contains(".hsp")` appears character-identically in 2 files — frontend/src-tauri/src/audio/device_detection.rs, frontend/src-tauri/src/audio/diagnostics.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 frontend/src-tauri/src/audio/devices/microphone.rs:52— `name_lower.contains("bluetooth") || name_lower.contains("airpods") || name_lower.contains("wireless")` appears character-identically in 2 files — frontend/src-tauri/src/audio/devices/microphone.rs, frontend/src-tauri/src/audio/devices/speakers.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 frontend/src-tauri/src/audio/device_detection.rs:318— `name_lower.contains("realtek") || name_lower.contains("conexant")` appears character-identically in 2 files — frontend/src-tauri/src/audio/device_detection.rs, frontend/src-tauri/src/audio/diagnostics.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 frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:1142— `result.is_ok() && !active_download.cancellation.is_cancelled()` appears character-identically in 2 files — frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs, frontend/src-tauri/src/whisper_engine/whisper_engine.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 frontend/src-tauri/src/audio/stream.rs:422— `self.microphone_stream.is_none() && self.system_stream.is_none()` appears character-identically in 2 files — frontend/src-tauri/src/audio/stream.rs, frontend/src-tauri/src/audio_v2/stream.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 frontend/src-tauri/src/audio/stream.rs:485— `self.microphone_stream.is_some() || self.system_stream.is_some()` appears character-identically in 2 files — frontend/src-tauri/src/audio/stream.rs, frontend/src-tauri/src/audio_v2/stream.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.
Orphaned file frontend/src-tauri/src/audio/stt.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 frontend/src/components/AISummary/Block.tsx: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 frontend/src/hooks/useAudioPlayer.ts: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 REDACTED: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 frontend/src/components/AISummary/Section.tsx: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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 32 significant file(s) lose their only recent owner: llama-helper/src/main.rs, frontend/src/contexts/OnboardingContext.tsx, frontend/src/contexts/TranscriptContext.tsx, frontend/src-tauri/src/summary/summary_engine/models.rs, frontend/src/components/onboarding/steps/DownloadProgressStep.tsx, frontend/src/hooks/useRecordingStop.ts, frontend/src/contexts/ConfigContext.tsx, frontend/src/components/BuiltInModelManager.tsx (+24 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 10 significant file(s) lose their only recent owner: frontend/src-tauri/src/audio/ffmpeg_mixer.rs, frontend/src-tauri/src/audio/capture/core_audio.rs, frontend/src-tauri/src/audio/recording_state.rs, frontend/src-tauri/src/audio/devices/platform/windows.rs, frontend/src/components/AudioBackendSelector.tsx, frontend/src-tauri/src/audio/permissions.rs, frontend/src-tauri/src/audio/playback_monitor.rs, frontend/src-tauri/src/audio/capture/system.rs (+2 more). Pair on, review, or document these before any departure.
Silent fallback default on Err frontend/src-tauri/src/audio/recording_saver.rs:464— `get_transcript_segments` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err frontend/src-tauri/src/audio/system_detector.rs:377— `list_system_audio_using_apps` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (44 single-owned of 215 analysed files in total, 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; 215 of the 323 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: frontend/src/services/recordingService.ts, frontend/src/components/DatabaseImport/HomebrewDatabaseDetector.tsx.
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 — 2 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 2.0/10. The most over is `frontend/src-tauri` (42246 LoC, 333 module-visible types across 25 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.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 5 of 215 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; 215 of the 323 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: frontend/src-tauri/src/audio/stt.rs, frontend/src/components/AISummary/Block.tsx, frontend/src/hooks/useAudioPlayer.ts, REDACTED, frontend/src/components/AISummary/Section.tsx. 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 2/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `frontend`, `llama-helper`.
No SAST — No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 128238 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
R7 · Dead Code· Unused export 'useUpdateCheckContext' · ×1
Unused export 'useUpdateCheckContext' frontend/src/components/UpdateCheckProvider.tsx:72— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'StatusIndicator' · ×1
Unused export 'StatusIndicator' frontend/src/components/onboarding/shared/StatusIndicator.tsx:5— Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/src/components/onboarding/shared/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/src/components/onboarding/shared/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'ParakeetEngineState' · ×1
Unused export 'ParakeetEngineState' frontend/src/lib/parakeet.ts:38— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'PARAKEET_MODEL_CONFIGS' · ×1
Unused export 'PARAKEET_MODEL_CONFIGS' frontend/src/lib/parakeet.ts:79— Nothing imports this binding — it is safe to review for removal.
Unused export 'getModelIcon' frontend/src/lib/parakeet.ts:104— Nothing imports THIS copy of 'getModelIcon' — but frontend/src/lib/whisper.ts:135 in the same directory exports that same name, and it is the copy every import site resolves to. Grepping the name therefore finds live callers that do not reach this binding: it is the dead half of a duplicated pair, left behind when the API moved. Delete it here and keep frontend/src/lib/whisper.ts's, or, if this one is meant to be the survivor, repoint the importers before removing the other.
R7 · Dead Code· Unused export 'getStatusColor' · ×1
Unused export 'getStatusColor' frontend/src/lib/parakeet.ts:124— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'isQuantizedModel' · ×1
Unused export 'isQuantizedModel' frontend/src/lib/parakeet.ts:140— Nothing imports THIS copy of 'isQuantizedModel' — but frontend/src/lib/whisper.ts:173 in the same directory exports that same name, and it is the copy every import site resolves to. Grepping the name therefore finds live callers that do not reach this binding: it is the dead half of a duplicated pair, left behind when the API moved. Delete it here and keep frontend/src/lib/whisper.ts's, or, if this one is meant to be the survivor, repoint the importers before removing the other.
R7 · Dead Code· Unused export 'getModelPerformanceBadge' · ×1
Unused export 'getModelPerformanceBadge' frontend/src/lib/parakeet.ts:145— Nothing imports THIS copy of 'getModelPerformanceBadge' — but frontend/src/lib/whisper.ts:178 in the same directory exports that same name, and it is the copy every import site resolves to. Grepping the name therefore finds live callers that do not reach this binding: it is the dead half of a duplicated pair, left behind when the API moved. Delete it here and keep frontend/src/lib/whisper.ts's, or, if this one is meant to be the survivor, repoint the importers before removing the other.
R7 · Dead Code· Unused export 'getRecommendedModel' · ×1
Unused export 'getRecommendedModel' frontend/src/lib/parakeet.ts:156— Nothing imports this binding — it is safe to review for removal.
Null assertions (`!`) reduce the strict null checking score — ~0.5 `!` null assertions per 1k TypeScript source lines — 15 assertion(s) across the 31152 source line(s) of the 171 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: frontend/src/services/indexedDBService.ts (10), frontend/src/components/ModelSettingsModal.tsx (1), frontend/src/components/Sidebar/index.tsx (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Silent fallback default in catch frontend/src/hooks/useRecentLanguages.ts:37— `readFromStorage` swallows every exception into `return []` — 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.
Outdated: anyhow — `anyhow` is locked at 1.0.102 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in llama-helper/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
Outdated: async-trait — `async-trait` is locked at 0.1.89 but 0.1.92 is the current stable release on crates.io, and it already satisfies the `"0.1"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p async-trait` and commit the updated REDACTED.
Outdated: bytemuck — `bytemuck` is locked at 1.25.0 but 1.25.2 is the current stable release on crates.io, and it already satisfies the `"1.16.1"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytemuck` and commit the updated REDACTED.
Outdated: bytes — `bytes` is locked at 1.11.1 but 1.12.1 is the current stable release on crates.io, and it already satisfies the `"1.9.0"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytes` and commit the updated REDACTED.
Outdated: chrono — `chrono` is locked at 0.4.44 but 0.4.45 is the current stable release on crates.io, and it already satisfies the `"0.4.31"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p chrono` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.6.1 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4.3"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: crossbeam — `crossbeam` is locked at 0.8.4 but 0.8.5 is the current stable release on crates.io, and it already satisfies the `"0.8.4"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam` and commit the updated REDACTED.
Outdated: dashmap — `dashmap` is locked at 6.1.0 but 6.2.1 is the current stable release on crates.io, and it already satisfies the `"6.1.0"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p dashmap` and commit the updated REDACTED.
Outdated: encoding_rs — `encoding_rs` is locked at 0.8.35 but 0.8.42 is the current stable release on crates.io, and it already satisfies the `"0.8"` requirement declared in llama-helper/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p encoding_rs` and commit the updated REDACTED.
Outdated: env_logger — `env_logger` is locked at 0.11.10 but 0.11.11 is the current stable release on crates.io, and it already satisfies the `"0.11"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p env_logger` and commit the updated REDACTED.
Outdated: futures-channel — `futures-channel` is locked at 0.3.32 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3.31"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures-channel` and commit the updated REDACTED.
Outdated: futures-util — `futures-util` is locked at 0.3.32 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures-util` and commit the updated REDACTED.
Outdated: lazy_static — `lazy_static` is locked at 1.5.0 but 1.5.1 is the current stable release on crates.io, and it already satisfies the `"1.4.0"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p lazy_static` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.29 but 0.4.34 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: regex — `regex` is locked at 1.12.3 but 1.13.1 is the current stable release on crates.io, and it already satisfies the `"1.11.0"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p regex` and commit the updated REDACTED.
Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in llama-helper/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.149 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in llama-helper/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: tar — `tar` is locked at 0.4.45 but 0.4.46 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tar` and commit the updated REDACTED.
Outdated: tauri — `tauri` is locked at 2.11.1 but 2.12.5 is the current stable release on crates.io, and it already satisfies the `"2.6.2"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tauri` and commit the updated REDACTED.
Outdated: tauri-build — `tauri-build` is locked at 2.6.1 but 2.7.4 is the current stable release on crates.io, and it already satisfies the `"2.3.0"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tauri-build` and commit the updated REDACTED.
Outdated: tauri-plugin-dialog — `tauri-plugin-dialog` is locked at 2.7.1 but 2.8.3 is the current stable release on crates.io, and it already satisfies the `"2.3.0"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tauri-plugin-dialog` and commit the updated REDACTED.
Outdated: tauri-plugin-fs — `tauri-plugin-fs` is locked at 2.5.1 but 2.7.1 is the current stable release on crates.io, and it already satisfies the `"2.4.0"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tauri-plugin-fs` and commit the updated REDACTED.
Outdated: tauri-plugin-log — `tauri-plugin-log` is locked at 2.8.0 but 2.10.1 is the current stable release on crates.io, and it already satisfies the `"2.6.0"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tauri-plugin-log` and commit the updated REDACTED.
Outdated: tauri-plugin-notification — `tauri-plugin-notification` is locked at 2.3.3 but 2.7.0 is the current stable release on crates.io, and it already satisfies the `"2.3.1"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tauri-plugin-notification` and commit the updated REDACTED.
Outdated: tauri-plugin-process — `tauri-plugin-process` is locked at 2.3.1 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3.0"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tauri-plugin-process` and commit the updated REDACTED.
+ 7 more in this group — see findings.md.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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 01a17616-5d20-7247-9aba-688cded519cb · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 206 · Warnings: 759 · Recommendations: 101 · Info: 32 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 02:42 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.