Public report of Zackriya-Solutions/meetily, published 14 November 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 report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert 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, 14 November 2026, 05:24 UTC · Survey ID cd_1409ec69ee7645e6b3a54edbaba92a75

Zackriya-Solutions/meetily

Measured 14 November 2026, 05:23 UTC, at code version 9e50dc2

CAI score 45out of 100 At risk Up 2 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: 77,658 lines of product code in 5 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Production Readiness, 34

Findings by how serious they are

207 critical 893 serious 202 minor

16 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 05:23 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 the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer 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. We work 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 ▸

72of 72 dimensions measured by tools.
1250of 1302 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.
72dimensions across 10 lenses, read from 77,658 lines of product code in 5 projects.
Chapters

Executive summary

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 45 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.

Production Readiness, at 34, is the weakest lens and counts most in the score. The best first steps are adding automated security scanning and planning backups and recovery, each worth about 5 points. Raising Production Readiness to 62 would lift the score to about 53.

Sixty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fifty-four secrets can leak from the build pipeline, and twenty-one 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 77,658 lines, about €70,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 for The 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.
Production Readiness 34 · counts for 45%Accessibility 48 · counts for 25%Code Health 48 · counts for 14%Security and Compliance 57 · counts for 8%Performance 79 · counts for 4%Event-Driven 80 · counts for 2%Maturity 80 · counts for 1%Architecture 92 · counts for 1%Domain Modelling 100 · counts for 0%Event Sourcing 100 · counts for 0%

If Production Readiness rose from 34 to 62, the lowest score rated Strong, the score would rise from 45 to about 53.

Code composition: what the lines of code are
Product code 98%Tests 2%
New since the last survey: 243 findings

These 243 critical or serious findings weren't in the previous survey, on 26 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · AudioCapture::process_audio_data_with_timestamp (cyclomatic 38) frontend/src-tauri/src/audio/pipeline.rs
  • Cyclomatic Complexity · meetily::audio::recording_commands::stop_recording_for_session (cyclomatic 32) frontend/src-tauri/src/audio/recording_commands.rs
  • Cyclomatic Complexity · PulseCapture::run_timed_ready (cyclomatic 29) frontend/src-tauri/src/audio/capture/pulse_linux.rs
  • Cyclomatic Complexity · meetily::audio::recording_commands::swap_linux_stream (cyclomatic 21) frontend/src-tauri/src/audio/recording_commands.rs
  • Cyclomatic Complexity · meetily::audio::recording_commands::repair_linux_stream (cyclomatic 19) frontend/src-tauri/src/audio/recording_commands.rs
  • Cyclomatic Complexity · meetily::audio::recording_commands::spawn_device_event_processor (cyclomatic 17) frontend/src-tauri/src/audio/recording_commands.rs
  • Cyclomatic Complexity · meetily::audio::recording_commands::start_recording_with_meeting_name (cyclomatic 16) frontend/src-tauri/src/audio/recording_commands.rs
  • Cyclomatic Complexity · meetily::audio::recording_commands::follow_linux_default (cyclomatic 16) frontend/src-tauri/src/audio/recording_commands.rs
  • Cognitive Complexity · AudioCapture::process_audio_data_with_timestamp (cognitive 107) frontend/src-tauri/src/audio/pipeline.rs
  • Cognitive Complexity · PulseCapture::run_timed_ready (cognitive 54) frontend/src-tauri/src/audio/capture/pulse_linux.rs
  • Cognitive Complexity · meetily::audio::recording_commands::stop_recording_for_session (cognitive 50) frontend/src-tauri/src/audio/recording_commands.rs
  • Cognitive Complexity · meetily::audio::recording_commands::spawn_device_event_processor (cognitive 40) frontend/src-tauri/src/audio/recording_commands.rs
  • Cognitive Complexity · meetily::audio::recording_commands::swap_linux_stream (cognitive 30) frontend/src-tauri/src/audio/recording_commands.rs
  • Cognitive Complexity · RecordingStateContext.RecordingStateProvider (cognitive 27) frontend/src/contexts/RecordingStateContext.tsx
  • Cognitive Complexity · meetily::audio::recording_preferences::resolve_start_devices (cognitive 22) frontend/src-tauri/src/audio/recording_preferences.rs
  • Cognitive Complexity · meetily::audio::recording_commands::repair_linux_stream (cognitive 21) frontend/src-tauri/src/audio/recording_commands.rs
  • Cognitive Complexity · meetily::audio::recording_commands::start_recording_with_meeting_name (cognitive 20) frontend/src-tauri/src/audio/recording_commands.rs
  • Cognitive Complexity · meetily::audio::recording_commands::start_recording_with_devices_and_meeting (cognitive 19) frontend/src-tauri/src/audio/recording_commands.rs
  • Cognitive Complexity · meetily::audio::recording_commands::follow_linux_default (cognitive 19) frontend/src-tauri/src/audio/recording_commands.rs
  • Cognitive Complexity · meetily::audio::recording_preferences::save_recording_preferences (cognitive 18) frontend/src-tauri/src/audio/recording_preferences.rs
  • Cognitive Complexity · meetily::audio::capture::pulse_enumerator::enumerator_thread (cognitive 17) frontend/src-tauri/src/audio/capture/pulse_enumerator.rs
  • God Classes · FunctionTooLong: meetily::audio::recording_commands::stop_recording_for_session frontend/src-tauri/src/audio/recording_commands.rs
  • God Classes · MethodTooLong: AudioCapture.process_audio_data_with_timestamp frontend/src-tauri/src/audio/pipeline.rs
  • God Classes · FunctionTooLong: meetily::audio::recording_commands::start_recording_with_meeting_name frontend/src-tauri/src/audio/recording_commands.rs
  • God Classes · FunctionTooLong: meetily::audio::recording_commands::start_recording_with_devices_and_meeting frontend/src-tauri/src/audio/recording_commands.rs
  • God Classes · FileTooLong: audio/stream.rs frontend/src-tauri/src/audio/stream.rs
  • God Classes · ClassTooLong: AudioStream frontend/src-tauri/src/audio/stream.rs
  • Code Duplication · Near-duplicate member family (3 members, 29 shared lines) frontend/src-tauri/src/anthropic/anthropic.rs
  • Code Duplication · Near-duplicate member pair (167 shared lines) frontend/src-tauri/src/audio/recording_commands.rs
  • Code Duplication · Near-duplicate member pair (133 shared lines) frontend/src-tauri/src/audio/import.rs
  • Code Duplication · Near-duplicate member pair (88 shared lines) frontend/src-tauri/src/lib_old_complex.rs
  • Code Duplication · Near-duplicate member pair (80 shared lines) frontend/src-tauri/src/audio/core-old.rs
  • 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) frontend/src-tauri/src/api/api.rs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) backend/app/db.py
  • Code Duplication · Edited copy of a member (85 corresponding lines) frontend/src-tauri/src/audio/stream.rs
  • Code Duplication · Edited copy of a member (104 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs
  • Code Duplication · Edited copy of a member (56 corresponding lines) frontend/src-tauri/src/whisper_engine/whisper_engine.rs
  • Code Duplication · Edited copy of a member (62 corresponding lines) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Edited copy of a member (52 corresponding lines) frontend/src-tauri/src/tray.rs
  • Code Duplication · Edited copy of a member (45 corresponding lines) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Edited copy of a member (59 corresponding lines) frontend/src-tauri/src/audio/recording_saver_old.rs
  • Code Duplication · Edited copy of a member (46 corresponding lines) frontend/src-tauri/src/summary/summary_engine/sidecar.rs
  • Code Duplication · Edited copy of a member (49 corresponding lines) frontend/src-tauri/src/lib_old_complex.rs
  • Code Duplication · Edited copy of a member (49 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs
  • Code Duplication · Edited copy of a member (44 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs
  • Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) frontend/src-tauri/src/audio/playback_monitor.rs
  • Code Duplication · Edited copy of a member (35 corresponding lines) frontend/src-tauri/src/audio/capture/pulse_enumerator.rs
  • Code Duplication · Edited copy of a member (41 corresponding lines) frontend/src-tauri/src/audio_v2/compatibility.rs
  • Code Duplication · Edited copy of a member (20 corresponding lines) frontend/src-tauri/src/audio/recording_state.rs
  • Code Duplication · Edited copy of a member (44 corresponding lines) frontend/src-tauri/src/api/api.rs
  • Code Duplication · Edited copy of a member (40 corresponding lines) frontend/src-tauri/src/audio/retranscription.rs
  • Code Duplication · Edited copy of a member (41 corresponding lines) frontend/src-tauri/src/audio/import.rs
  • Code Duplication · Edited copy of a member (29 corresponding lines) frontend/src-tauri/src/api/api.rs
  • Code Duplication · Edited copy of a member (43 corresponding lines) frontend/src-tauri/src/audio/devices/microphone.rs
  • Code Duplication · Edited copy of a member (26 corresponding lines) frontend/src-tauri/src/analytics/analytics.rs
  • Code Duplication · Edited copy of a member (31 corresponding lines) frontend/src-tauri/src/audio/recording_commands.rs
  • Code Duplication · Edited copy of a member (39 corresponding lines) frontend/src-tauri/src/console_utils/console_utils.rs
  • Code Duplication · Edited copy of a member (38 corresponding lines) frontend/src-tauri/src/audio/device_detection.rs
  • Code Duplication · Edited copy of a member (28 corresponding lines) frontend/src-tauri/src/audio/recording_manager.rs
  • Code Duplication · Edited copy of a member (24 corresponding lines) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) frontend/src-tauri/src/audio/recording_saver.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) frontend/src-tauri/src/parakeet_engine/model.rs
  • Code Duplication · Edited copy of a member (16 corresponding lines) frontend/src-tauri/src/audio/devices/platform/linux.rs
  • Code Duplication · Edited copy of a member (23 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs
  • Code Duplication · Edited copy of a member (28 corresponding lines) frontend/src-tauri/src/database/repositories/setting.rs
  • Code Duplication · Edited copy of a member (27 corresponding lines) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Edited copy of a member (19 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) frontend/src-tauri/src/summary/summary_engine/commands.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) frontend/src-tauri/src/lib.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) frontend/src-tauri/src/summary/commands.rs
  • Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) frontend/src-tauri/src/api/api.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs
  • Code Duplication · Edited copy of a member (22 corresponding lines) frontend/src-tauri/src/database/repositories/setting.rs
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) backend/app/db.py
  • Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) frontend/src-tauri/src/audio/capture/pulse_enumerator.rs
  • Code Duplication · Edited copy of a member (16 corresponding lines) frontend/src-tauri/src/tray.rs
  • Code Duplication · Edited copy of a member (8 corresponding lines) frontend/src-tauri/src/analytics/analytics.rs
  • Code Duplication · Edited copy of a member (17 corresponding lines) frontend/src-tauri/src/summary/templates/loader.rs
  • Code Duplication · Edited copy of a member (19 corresponding lines) frontend/src-tauri/src/api/api.rs
  • Code Duplication · Edited copy of a member (12 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) frontend/src-tauri/src/summary/commands.rs
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) frontend/src-tauri/src/api/api.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs
  • Code Duplication · Edited copy of a member (9 corresponding lines) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) frontend/src-tauri/src/audio/recording_saver.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs
  • Code Duplication · Edited copy of a member (7 corresponding lines) frontend/src-tauri/src/analytics/analytics.rs
  • Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs
  • Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) frontend/src-tauri/src/analytics/commands.rs
  • Code Duplication · Edited copies of one member (7 members, 11+ corresponding lines) frontend/src-tauri/src/notifications/commands.rs
  • Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) frontend/src-tauri/src/analytics/commands.rs
  • Code Duplication · Edited copy of a member (14 corresponding lines) frontend/src-tauri/src/analytics/commands.rs
  • Code Duplication · Edited copy of a member (14 corresponding lines) frontend/src-tauri/src/audio/transcription/parakeet_provider.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) frontend/src-tauri/src/database/repositories/summary.rs
  • Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) backend/app/db.py
  • Code Duplication · Edited copy of a member (7 corresponding lines) frontend/src-tauri/src/summary/summary_engine/model_manager.rs
  • Code Duplication · Edited copy of a member (22 corresponding lines) frontend/src-tauri/src/database/repositories/setting.rs

We compare 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: 193 findings

These 193 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one. The first 100 are listed here.

  • Cyclomatic Complexity · AudioCapture::process_audio_data (cyclomatic 36) frontend/src-tauri/src/audio/pipeline.rs
  • Cyclomatic Complexity · generate-update-manifest-github.bundleFiles.forEach() (cyclomatic 31) scripts/generate-update-manifest-github.js
  • Cyclomatic Complexity · meetily::audio::recording_commands::stop_recording (cyclomatic 28) frontend/src-tauri/src/audio/recording_commands.rs
  • Cyclomatic Complexity · WhisperEngine::transcribe_audio (cyclomatic 25) frontend/src-tauri/src/whisper_engine/whisper_engine.rs
  • Cognitive Complexity · AudioCapture::process_audio_data (cognitive 105) frontend/src-tauri/src/audio/pipeline.rs
  • Cognitive Complexity · AudioPipeline::run (cognitive 53) frontend/src-tauri/src/audio/pipeline.rs
  • Cognitive Complexity · meetily::audio::recording_commands::stop_recording (cognitive 45) frontend/src-tauri/src/audio/recording_commands.rs
  • Cognitive Complexity · meetily::api::api::api_test_custom_openai_connection (cognitive 44) frontend/src-tauri/src/api/api.rs
  • Cognitive Complexity · WhisperEngine::transcribe_audio (cognitive 36) frontend/src-tauri/src/whisper_engine/whisper_engine.rs
  • Cognitive Complexity · generate-update-manifest-github.bundleFiles.forEach() (cognitive 29) scripts/generate-update-manifest-github.js
  • Cognitive Complexity · meetily::audio::transcription::worker::transcribe_chunk_with_provider (cognitive 22) frontend/src-tauri/src/audio/transcription/worker.rs
  • God Classes · FunctionTooLong: meetily::audio::recording_commands::stop_recording frontend/src-tauri/src/audio/recording_commands.rs
  • God Classes · MethodTooLong: AudioCapture.process_audio_data frontend/src-tauri/src/audio/pipeline.rs
  • God Classes · FunctionTooLong: meetily::audio::transcription::worker::transcribe_chunk_with_provider frontend/src-tauri/src/audio/transcription/worker.rs
  • Code Duplication · Near-duplicate member family (3 members, 29 shared lines) frontend/src-tauri/src/anthropic/anthropic.rs
  • Code Duplication · Near-duplicate member pair (133 shared lines) frontend/src-tauri/src/audio/import.rs
  • Code Duplication · Near-duplicate member pair (125 shared lines) frontend/src-tauri/src/audio/recording_commands.rs
  • Code Duplication · Near-duplicate member pair (86 shared lines) frontend/src-tauri/src/lib_old_complex.rs
  • Code Duplication · Near-duplicate member pair (79 shared lines) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Edited copy of a member (34 corresponding lines) frontend/src-tauri/src/audio/core-old.rs
  • 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) frontend/src-tauri/src/api/api.rs
  • 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
  • Code Duplication · Duplicated block (59–60 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs
  • Code Duplication · Duplicated block (40–42 lines × 2) frontend/src-tauri/src/whisper_engine/whisper_engine.rs
  • Code Duplication · Duplicated block (40–41 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs
  • Code Duplication · Duplicated block (34 lines × 2) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (22 lines × 2) frontend/src-tauri/src/lib_old_complex.rs
  • Code Duplication · Duplicated block (21 lines × 2) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (21 lines × 2) frontend/src-tauri/src/audio/import.rs
  • Code Duplication · Duplicated block (18 lines × 2) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (18 lines × 2) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (18 lines × 2) frontend/src-tauri/src/lib_old_complex.rs
  • Code Duplication · Duplicated block (18 lines × 2) frontend/src-tauri/src/notifications/commands.rs
  • Code Duplication · Duplicated block (17 lines × 2) frontend/src-tauri/src/audio/decoder.rs
  • Code Duplication · Duplicated block (16 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs
  • Code Duplication · Duplicated block (15 lines × 2) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (14–15 lines × 2) frontend/src-tauri/src/summary/summary_engine/sidecar.rs
  • Code Duplication · Duplicated block (12–13 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs
  • Code Duplication · Duplicated block (11–13 lines × 2) frontend/src-tauri/src/whisper_engine/whisper_engine.rs
  • Code Duplication · Duplicated block (12 lines × 3) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (12 lines × 2) frontend/src-tauri/src/audio/devices/microphone.rs
  • Code Duplication · Duplicated block (12 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs
  • Code Duplication · Duplicated block (11 lines × 5) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (8–11 lines × 2) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (11 lines × 2) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (11 lines × 2) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (11 lines × 2) frontend/src-tauri/src/audio/pipeline.rs
  • Code Duplication · Duplicated block (10 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs
  • Code Duplication · Duplicated block (9 lines × 2) frontend/src-tauri/src/audio_v2/stream.rs
  • Code Duplication · Duplicated block (8 lines × 2) frontend/src-tauri/src/analytics/analytics.rs
  • Code Duplication · Duplicated block (8 lines × 2) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (7 lines × 2) frontend/src-tauri/src/audio/core-old.rs
  • Code Duplication · Duplicated block (16 lines × 2) frontend/src-tauri/src/audio/recording_saver_old.rs
  • Code Duplication · Duplicated block (11 lines × 2) frontend/src-tauri/src/audio/import.rs
  • Code Duplication · Duplicated block (11 lines × 3) frontend/src-tauri/src/anthropic/anthropic.rs
  • Code Duplication · Duplicated block (8 lines × 2) frontend/src-tauri/src/database/manager.rs
  • Code Duplication · Duplicated block (11 lines × 2) frontend/src-tauri/src/lib_old_complex.rs
  • Code Duplication · Duplicated block (10 lines × 2) frontend/src-tauri/src/audio/decoder.rs
  • Code Duplication · Duplicated block (9 lines × 2) frontend/src-tauri/src/audio/stream.rs
  • Code Duplication · Duplicated block (9 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs
  • Code Duplication · Duplicated block (24 lines × 2) backend/app/db.py
  • Code Duplication · Duplicated block (11 lines × 2) backend/app/db.py
  • Code Duplication · Duplicated block (11 lines × 2) backend/app/db.py
  • Churn × Complexity Hotspots · Repeated repair: frontend/src/components/MeetingDetails/SummaryGeneratorButtonGroup.tsx frontend/src/components/MeetingDetails/SummaryGeneratorButtonGroup.tsx
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: watchdog-unverified-download-in-run REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: watchdog-unverified-download-in-run REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: watchdog-unverified-download-in-run REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0346 REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0367 REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0367 REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Change Coupling · Change-coupling hub: REDACTED → tray.rs, REDACTED, TranscriptView.tsx frontend/src/app/page.tsx
  • Change Coupling · Change coupling: AnalyticsProvider.tsx ↔ index.tsx frontend/src/components/AnalyticsProvider.tsx
  • Change Coupling · Change coupling: service.rs ↔ useSummaryGeneration.ts frontend/src-tauri/src/summary/service.rs
  • Supply-chain Provenance & Signing · CI installs an unverified third-party binary REDACTED
  • Code Duplication · Duplicated block (31 lines × 2 locations) frontend/src/components/DeviceSelection.tsx
  • Code Duplication · Duplicated block (19 lines × 2 locations) frontend/src/components/Sidebar/index.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) frontend/src/components/ui/dropdown-menu.tsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) frontend/src/components/DeviceSelection.tsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) frontend/src/components/ModelSettingsModal.tsx
  • Code Duplication · Duplicated block (13 lines × 3 locations) frontend/src/components/TranscriptView.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) frontend/src/components/AISummary/index.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) frontend/src/components/onboarding/steps/DownloadProgressStep.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) frontend/src/hooks/useProcessingProgress.ts
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) frontend/src/components/About.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) frontend/src/components/AnalyticsDataModal.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) frontend/src/components/ChunkProgressDisplay.tsx
Rebuild cost: about €70,000 · Estimate
Cost to rebuild€23,000 to €120,000, for 388 to 1,230 hours of work, about 0.5 person-years for one engineer
Difficulty of the problemStandard, 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 45. 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.
SizeMedium: 77,658 lines of product code
What it is notNot 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: We price 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.
Raises the score by about 5 points · Medium effort · Security & performance tooling
2
Resolve the 1 finding(s) in DR & Backup.
Raises the score by about 5 points · Medium effort · DR & Backup
3
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.
Raises the score by about 3 points · Medium effort · Outbound HTTP resilience

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €70,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 34 (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 5 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 5.8 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 12% on every change. The history of the code shows how much it changes: about 28,158 lines over the last 90 days, which is about 114,196 lines a year. At that pace, the extra work comes to an estimated 15.6 to 93.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 our 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.

267 modules, with 198 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; 227 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 frontend.src.app._components2 frontend.src.components.ModelSettingsModal3 frontend.src.components.TranscriptSettings4 frontend.src.lib.audioDevices5 frontend.src.lib.whisper6 frontend.src.types7 frontend.src.types.onboarding8 meetily.api.api9 meetily.audio.core-old10 meetily.audio.device_detection11 meetily.audio.vad12 meetily.notifications.types13 meetily.parakeet_engine.parakeet_engine14 frontend.src.components.MeetingDetails.SummaryPanel15 frontend.src.components.SettingTabs16 frontend.src.contexts.ConfigContext17 frontend.src.hooks18 frontend.src.hooks.meeting-details.useSummaryGeneration19 frontend.src.lib.parakeet20 frontend.src.services.configService21 meetily.audio.recording_saver22 meetily.audio.recording_state23 meetily.audio.stt24 meetily.audio_v2.recorder25 meetily.notifications.manager26 meetily.whisper_engine.whisper_engine27 frontend.src.components28 frontend.src.components.MeetingDetails29 frontend.src.hooks.meeting-details30 frontend.src.lib31 meetily.audio.pipeline32 meetily.audio.system_audio_stream33 meetily.audio.transcription.worker34 meetily.audio_v235 meetily.whisper_engine.parallel_processor36 meetily.audio.stream37 meetily.audio_v2.compatibility38 meetily.audio.recording_manager39 meetily.audio.recording_commands40 meetily.lib_old_complex
1 frontend.src.app._components
2 frontend.src.components.ModelSettingsModal
3 frontend.src.components.TranscriptSettings
4 frontend.src.lib.audioDevices
5 frontend.src.lib.whisper
6 frontend.src.types
7 frontend.src.types.onboarding
8 meetily.api.api
9 meetily.audio.core-old
10 meetily.audio.device_detection
11 meetily.audio.vad
12 meetily.notifications.types
13 meetily.parakeet_engine.parakeet_engine
14 frontend.src.components.MeetingDetails.SummaryPanel1
15 frontend.src.components.SettingTabs11
16 frontend.src.contexts.ConfigContext111
17 frontend.src.hooks11
18 frontend.src.hooks.meeting-details.useSummaryGeneration1
19 frontend.src.lib.parakeet4
20 frontend.src.services.configService11
21 meetily.audio.recording_saver2
22 meetily.audio.recording_state3
23 meetily.audio.stt31
24 meetily.audio_v2.recorder11
25 meetily.notifications.manager1
26 meetily.whisper_engine.whisper_engine1
27 frontend.src.components111
28 frontend.src.components.MeetingDetails1
29 frontend.src.hooks.meeting-details132
30 frontend.src.lib151
31 meetily.audio.pipeline3213
32 meetily.audio.system_audio_stream42
33 meetily.audio.transcription.worker1
34 meetily.audio_v211
35 meetily.whisper_engine.parallel_processor22
36 meetily.audio.stream421
37 meetily.audio_v2.compatibility11
38 meetily.audio.recording_manager121212
39 meetily.audio.recording_commands1111
40 meetily.lib_old_complex2212
Uses a module listed above itPart of a loopThe module itself
1 frontend.src.app._components2 frontend.src.components.ModelSettingsModal3 frontend.src.components.TranscriptSettings4 frontend.src.lib.audioDevices5 frontend.src.lib.whisper6 frontend.src.types7 frontend.src.types.onboarding8 meetily.api.api9 meetily.audio.core-old10 meetily.audio.device_detection11 meetily.audio.vad12 meetily.notifications.types13 meetily.parakeet_engine.parakeet_engine14 frontend.src.components.MeetingDetails.SummaryPanel15 frontend.src.components.SettingTabs16 frontend.src.contexts.ConfigContext17 frontend.src.hooks18 frontend.src.hooks.meeting-details.useSummaryGeneration19 frontend.src.lib.parakeet20 frontend.src.services.configService21 meetily.audio.recording_saver22 meetily.audio.recording_state23 meetily.audio.stt24 meetily.audio_v2.recorder25 meetily.notifications.manager26 meetily.whisper_engine.whisper_engine27 frontend.src.components28 frontend.src.components.MeetingDetails29 frontend.src.hooks.meeting-details30 frontend.src.lib31 meetily.audio.pipeline32 meetily.audio.system_audio_stream33 meetily.audio.transcription.worker34 meetily.audio_v235 meetily.whisper_engine.parallel_processor36 meetily.audio.stream37 meetily.audio_v2.compatibility38 meetily.audio.recording_manager39 meetily.audio.recording_commands40 meetily.lib_old_complexfrontend.src.app._components1frontend.src.components.ModelSettingsModal2frontend.src.components.TranscriptSettings3frontend.src.lib.audioDevices4frontend.src.lib.whisper5frontend.src.types6frontend.src.types.onboarding7meetily.api.api8meetily.audio.core-old9meetily.audio.device_detection10meetily.audio.vad11meetily.notifications.types12meetily.parakeet_engine.parakeet_engine13frontend.src.components.MeetingDetails.SummaryPanel14frontend.src.components.SettingTabs15frontend.src.contexts.ConfigContext16frontend.src.hooks17frontend.src.hooks.meeting-details.useSummaryGeneration18frontend.src.lib.parakeet19frontend.src.services.configService20meetily.audio.recording_saver21meetily.audio.recording_state22meetily.audio.stt23meetily.audio_v2.recorder24meetily.notifications.manager25meetily.whisper_engine.whisper_engine26frontend.src.components27frontend.src.components.MeetingDetails28frontend.src.hooks.meeting-details29frontend.src.lib30meetily.audio.pipeline31meetily.audio.system_audio_stream32meetily.audio.transcription.worker33meetily.audio_v234meetily.whisper_engine.parallel_processor35meetily.audio.stream36meetily.audio_v2.compatibility37meetily.audio.recording_manager38meetily.audio.recording_commands39meetily.lib_old_complex40111111111411233111111111132151321342111224211112121211112212+227 more modules (most-connected shown)

At a glance — Code Health · 48% · Adequate · gated by D2, X4 ·

At a glance — Architecture · 92% · Adequate · gated by D26 ·

At a glance — Maturity · 80% · Strong ·

At a glance — Readiness · 34% · Weak · gated by P3, P5, P7 ·

At a glance — Security · 57% · Adequate · gated by D29, D36 ·

At a glance — Domain Modelling · 100% · Exemplary ·

At a glance — Event-Driven · 80% · Strong ·

At a glance — Event Sourcing · 100% · Exemplary ·

At a glance — Accessibility · 48% · Adequate · gated by AC4 ·

At a glance — Performance · 79% · Strong ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A05:2025 — Injection143High / Critical
A03:2025 — Software Supply Chain Failures84High / Critical
A02:2025 — Security Misconfiguration18High / Critical

Roadmap

Top priorities: 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; Resolve the 1 finding(s) in DR & Backup; 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.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
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.+5.3 ptsMediumSecurity & performance tooling
Resolve the 1 finding(s) in DR & Backup.+5.3 ptsMediumDR & Backup
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.+2.7 ptsMediumOutbound HTTP resilience
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+1.9 ptsMediumKeyboard semantics
Interpolated log message defeats structured logging+1.4 ptsMediumStructured logging
Add tests that import the unreached modules (directly or through their public entry).+1.4 ptsMediumTest Coverage
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.+1.3 ptsMediumObservability
Resolve the 69 FunctionTooLong finding(s) in God Classes — start with recording_commands.rs (4), REDACTED (3), index.tsx (2).+1.1 ptsHighGod Classes

File quality

Per-file score 0–10 — a quality signature. Of 166 files carrying findings, judged against the Preview bar: 6% slop · 21% mixed · 73% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical vulnerability: REDACTED
REDACTED0.9SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.0MixedIaC & Container Security: High IaC: REDACTED
REDACTED3.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED3.7MixedDependency Vulnerabilities: High CVE: REDACTED
frontend/src/app/page.tsx4.6MixedCyclomatic Complexity: page.Home (cyclomatic 26)
frontend/src/components/Sidebar/index.tsx4.8MixedCyclomatic Complexity: index.Sidebar::renderItem (cyclomatic 25)
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.0MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedIaC & Container Security: High IaC: REDACTED
frontend/src/components/MeetingDetails/SummaryPanel.tsx5.4MixedChange Coupling: Boundary-crossing change coupling: SummaryPanel.tsx ↔ useSummaryGeneration.ts

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 207

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 — 893

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 — 202

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 16

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

This survey 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. All 72 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 72 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D16D17D19D20D24D26D28D29D30D31D34D35D36D43D44AC1AC2AC3AC4AC5AC6AX10AX3AX4AX9DM4DM5DM6ED4ES2M1M2M3M4P1P10P2P3P4P5P6P7P8PF1PF3R1R10R2R3R4R6R7R8R9X1X21X27X28X29X4X5

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
  1. 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, 1250 of 1302 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1d882-fa7c-728e-bf50-88ff3c98687c.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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 — We 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: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 58 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 2 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 — We 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, 60 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 — We measured this, but not all of it. What we 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 — We measured this, but not all of it. What we 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 — We measured this, but not all of it. What we 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 — We 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 naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — not measured this run — We 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D27 Navigability — not measured this run — We 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.
  • AX6 Interface segregation — not measured this run — We 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • AXR1 Runtime accessibility — not measured this run — We 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-11-14T05:24:06Z" level=warning msg="The \"MODEL_NAME\" variable is not set. Defaulting to a blank string." time="2026-11-14T05:24:06Z" level=warning msg="The \"MODEL_NAME\" variable is not set. Defaulting to a blank string." time="2026-11-14T05:24:06Z" 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 — We 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 — We 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 — We measured this, but not all of it. What we 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), and artefact counts an order of magnitude off. 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 — We measured this, but not all of it. What we 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.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 16 further occurrence(s) are not listed individually; the score already reflects all 56.
  • R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 41 further occurrence(s) are not listed individually; the score already reflects all 81.
  • R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
  • S1 Web-Security Posture — not measured this run — We 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.
  • X12 Unreachable branch — not measured this run — We 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — not measured this run — We 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — We 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X2 Cancellation propagation — not measured this run — We 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, got, undici, node:http; 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.
  • X23 Unguarded diagnostic materialisation — not measured this run — We 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X24 Document value interpolated into markup unescaped — not measured this run — We 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X3 Exception handling — not measured this run — We 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 57 further occurrence(s) are not listed individually; the score already reflects all 97.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do 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.
  • 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • 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.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • 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.
  • 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • 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.

Dimensions

D1 · Cyclomatic Complexity4.5 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 4.5 / 10 · rule-coverage 100% · ceiling Prevented

88 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.

meetily::lib_old_complex::audio_collection_task (cyclomatic 68) · ×26frontend/src-tauri/src/lib_old_complex.rs:270
AudioCapture::process_audio_data_with_timestamp (cyclomatic 38) · ×2frontend/src-tauri/src/audio/pipeline.rs:624
WhisperEngine::finish_download (cyclomatic 23) · ×2frontend/src-tauri/src/whisper_engine/whisper_engine.rs:830
index.AISummary (cyclomatic 93)frontend/src/components/AISummary/index.tsx:22
RecordingControls.RecordingControls (cyclomatic 89)frontend/src/components/RecordingControls.tsx:34

+ 56 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 5 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with index.AISummary (cyclomatic 93), RecordingControls.RecordingControls (cyclomatic 89), 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.5 to about 5.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Prevented

133 method(s) exceeded the cognitive complexity threshold of 15; the worst was meetily::lib_old_complex::audio_collection_task at 193.

meetily::lib_old_complex::audio_collection_task (cognitive 193) · ×45frontend/src-tauri/src/lib_old_complex.rs:270
RecordingSaver::start_accumulation (cognitive 32) · ×4frontend/src-tauri/src/audio/recording_saver.rs:138
MacOSSystemAudioDetector::start::system_listener (cognitive 55) · ×3frontend/src-tauri/src/audio/system_detector.rs:196
WhisperEngine::finish_download (cognitive 44) · ×3frontend/src-tauri/src/whisper_engine/whisper_engine.rs:830
AudioCapture::process_audio_data_with_timestamp (cognitive 107) · ×2frontend/src-tauri/src/audio/pipeline.rs:624

+ 73 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 21 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 21 together lifts Cognitive Complexity from 2.0 to about 4.0/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes5.2 / 10Adequate✓ 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.

Maturity: Documented → Verified → Prevented · effective 5.2 / 10 · rule-coverage 100% · ceiling Prevented

102 god class(es) detected.

FunctionTooLong: ModelSettingsModal.ModelSettingsModal · ×69frontend/src/components/ModelSettingsModal.tsx:121
FileTooLong: src/lib_old_complex.rs · ×17frontend/src-tauri/src/lib_old_complex.rs
MethodTooLong: ModelManager.download_model_detailed · ×9frontend/src-tauri/src/summary/summary_engine/model_manager.rs:351
ClassTooLong: ModelSettingsModal · ×5frontend/src/components/ModelSettingsModal.tsx:1
TooManyMethods: Analytics · ×2frontend/src/lib/analytics.ts:21

What to do

  1. Resolve the 69 FunctionTooLong finding(s) in God Classes — start with recording_commands.rs (4), REDACTED (3), index.tsx (2). — One of this dimension's main actionable groups (69 warning-level).
  2. Resolve the 17 FileTooLong finding(s) in God Classes — start with index.tsx (2), lib_old_complex.rs, recording_commands.rs. — One of this dimension's main actionable groups (17 warning-level).
  3. 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).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication6.8 / 10Adequate✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.8 / 10 · rule-coverage 100% · ceiling Verified

136 duplicated block group(s) detected. 8.1 % of the production lines (6,289 of 77,658) are in a reported copy. A further 80 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .tsx (24% 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.

Duplicated block (12 lines × 2) · ×11frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:356
Duplicated block (11 lines × 2) · ×9frontend/src-tauri/src/api/api.rs:898
Duplicated block (9 lines × 2) · ×9frontend/src-tauri/src/audio/recording_manager.rs:84
Duplicated block (14 lines × 2) · ×7frontend/src-tauri/src/audio/core-old.rs:146
Edited copy of a member (15 corresponding lines) · ×6frontend/src-tauri/src/audio/recording_saver.rs:94

+ 106 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 11 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with core-old.rs (3), pulse_enumerator.rs (2), microphone.rs. — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 9 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with core-old.rs (3), api.rs, recording_manager.rs. — One of this dimension's main actionable groups (9 warning-level).
  3. Resolve the 9 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with lib_old_complex.rs (2), commands.rs (2), recording_manager.rs. — One of this dimension's main actionable groups (9 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

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.

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 60 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 58 tests. Measured on the JavaScript/TypeScript suite only — at least 2 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

D12 · Dependency Hygiene8.3 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 8.3 / 10 · rule-coverage 100% · ceiling Verified

34 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 · ×34

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 832 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.0 / 10Stronggated by 37 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: frontend/src-tauri/src/audio/recording_commands.rs (30×32=960); frontend/src/components/RecordingControls.tsx (5×89=445); frontend/src/components/Sidebar/index.tsx (4×99=396) Repeated repair below the complexity floor: frontend/src-tauri/src/audio/stream.rs (9 of 12 changes were fixes); frontend/src-tauri/src/audio/recording_manager.rs (8 of 10 changes were fixes); frontend/src/services/recordingService.ts (7 of 8 changes were fixes)

Hotspot: frontend/src-tauri/src/audio/recording_commands.rs · ×24frontend/src-tauri/src/audio/recording_commands.rs:869
Repeated repair: frontend/src-tauri/src/audio/stream.rs · ×13frontend/src-tauri/src/audio/stream.rs:302

What to do

  1. Resolve the 24 Hotspot finding(s) in Churn × Complexity Hotspots — start with recording_commands.rs, RecordingControls.tsx, index.tsx. — One of this dimension's main actionable groups (24 warning-level).
  2. Resolve the 13 Repeated repair finding(s) in Churn × Complexity Hotspots — start with stream.rs, recording_manager.rs, recordingService.ts. — One of this dimension's main actionable groups (13 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D16 · Bus Factor8.1 / 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.

Maturity: Documented → Verified → Prevented · effective 8.1 / 10 · rule-coverage 100% · ceiling Documented

43 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is backend/app/db.py. Counted over 222 of the 326 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

  1. Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
  2. 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.

D17 · Explicit Debt9.9 / 10Stronggated by 24 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

24 deducted task-comment markers across 77658 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

  1. 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).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 10 document(s) read across 2 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundllama-helper/src/main.rs:1

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D24 · Comment Value5.5 5.4 / 10Adequate✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 5.4 / 10 · rule-coverage 98% · ceiling Documented

55 of 1220 judged comments only repeat the code they sit on (4.5 %). 27 comment(s) in another language or script were not judged.

redundant comment · ×55frontend/src-tauri/src/audio/system_audio_types.ts:7
doc comments repeat the namesfrontend/src/components/VirtualizedTranscriptView.tsx:22

What to do

  1. Resolve the 55 redundant comment finding(s) in Comment Value — start with index.tsx (6), DeviceSelection.tsx (4), TranscriptContext.tsx (4). — One of this dimension's main actionable groups (55 recommendation-level).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion2.0 / 10Critical✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 5 build units (Cargo, Python, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. 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.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.0 / 10Critical✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

143 finding(s): 0 critical, 131 high, 11 medium, 1 low. 60 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

+ 7 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. 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).
  3. No action in Static Analysis (SAST) — all 60 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 (60 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

77 finding(s): 4 critical, 17 high, 54 medium, 2 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 3 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 1 Critical vulnerability 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.

D31 · IaC & Container Security5.9 / 10Adequate✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 5.9 / 10 · rule-coverage 100% · ceiling Documented

18 finding(s): 0 critical, 10 high, 8 medium, 0 low.

REDACTED
REDACTED

What to do

  1. 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).
  2. 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.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 222 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is frontend/src/components/SummaryLanguageSettings.tsx. Counted over 222 of the 326 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge
Orphaned filefrontend/src/components/SummaryLanguageSettings.tsx:1

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling9.4 / 10Adequategated by 1 critical finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: import.rs↔retranscription.rs 86%; About.tsx↔AnalyticsProvider.tsx 80%; About.tsx↔index.tsx 80%

Boundary-crossing change coupling: SummaryPanel.tsx ↔ useSummaryGeneration.tsfrontend/src/components/MeetingDetails/SummaryPanel.tsx:1
Change coupling: import.rs ↔ retranscription.rs · ×7frontend/src-tauri/src/audio/import.rs:1
Change-coupling hub: index.tsx → About.tsx, AnalyticsConsentSwitch.tsx, AnalyticsProvider.tsxfrontend/src/components/Sidebar/index.tsx

What to do

  1. 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).
  2. Resolve the 7 Change coupling finding(s) in Change Coupling — start with REDACTED (2), import.rs, About.tsx. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with index.tsx. — 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.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 2 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. 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.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

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:70, frontend/src/app/_components/SettingsModal.tsx:175, frontend/src/app/_components/SettingsModal.tsx:216, …
  • 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:91, 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:95, frontend/src/app/_components/SettingsModal.tsx:115, 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 select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it. (×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:1095, 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.
AC3 · Page structure6.3 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — 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.
AC4 · Keyboard semantics1.4 / 10Critical✓ Tool-verified

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:138, frontend/src/components/BuiltInModelManager.tsx:300, frontend/src/components/ModelSettingsModal.tsx:1001, …
  • 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:570, frontend/src/components/Sidebar/index.tsx:728
  • 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.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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.

AC6 · Visual & motion safety4.7 / 10Adequate✓ Tool-verified

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:31
  • <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, …
  • 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. (×14) — frontend/src/app/meeting-details/page.tsx:255, frontend/src/components/AudioBackendSelector.tsx:160, frontend/src/components/AudioBackendSelector.tsx:165, …
  • <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
  • <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.
AX10 · Code composition9.7 / 10Exemplary✓ Tool-verified

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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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.

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.

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

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.

ED4 · Outbox / dual-write8.0 / 10Strong✓ Tool-verified

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`, :598) 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:335

What to do

  • Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

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.

M1 · Documentation (README)9.3 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

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's code 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.

P2 · Observability5.2 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • 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.
  • Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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 8 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.
  • `frontend/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — frontend/package.json:30

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.
P4 · Deployment & Rollback10.0 / 10Exemplary✓ Tool-verified

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.

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.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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:550

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.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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.

PF1 · Benchmark discipline7.5 / 10Strong✓ Tool-verified

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.

PF3 · Async & latency hygiene8.5 / 10Exemplary✓ Tool-verified

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 each language's code 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.

  • `stop` is async and calls thread::sleep — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — frontend/src-tauri/src/audio/stream.rs:630

What to do

  • Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
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.

R10 · Code Duplication4.2 / 10Weak✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): 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. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 18 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 7 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 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 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 18 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/components/DeviceSelection.tsx:279 · frontend/src/components/DeviceSelection.tsx:367 — 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:279
  • 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/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:160 · frontend/src/app/_components/SettingsModal.tsx:201 — 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:160
  • frontend/src/components/Sidebar/index.tsx:163 · 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:163
  • 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/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:202 — 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/DeviceSelection.tsx:143 · frontend/src/components/DeviceSelection.tsx:162 — 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/DeviceSelection.tsx:143
  • 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/Sidebar/index.tsx:465 · frontend/src/components/Sidebar/index.tsx:518 — 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:465

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.
R2 · Cyclomatic Complexity7.5 / 10Strong✓ Tool-verified

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: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. — frontend/src/hooks/useRecordingStop.ts:121
  • RecordingControls has cyclomatic complexity 36 and cognitive complexity 24; 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:34
  • 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
  • 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:626
  • 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:556
  • 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:233
  • 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
  • fetchModelConfig has cyclomatic complexity 18 and cognitive complexity 26; 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:267
  • (anonymous) has cyclomatic complexity 18 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 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/RecordingControls.tsx:91
  • (anonymous) has cyclomatic complexity 17 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 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:307
  • UpdateDialog has cyclomatic complexity 17 and cognitive complexity 13; 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/UpdateDialog.tsx:23
  • renderDownloadCard has cyclomatic complexity 16 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/onboarding/steps/DownloadProgressStep.tsx:402
  • SummaryPanel has cyclomatic complexity 16 and cognitive complexity 13; 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/SummaryPanel.tsx:59
  • TranscriptRecovery has cyclomatic complexity 16 and cognitive complexity 13; 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/TranscriptRecovery/TranscriptRecovery.tsx:34
  • getModelTagline has cyclomatic complexity 15 and cognitive complexity 13; 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/lib/whisper.ts:195
  • checkAutoStartRecording has cyclomatic complexity 14 and cognitive complexity 36; 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/useRecordingStart.ts:212
  • getMarkdown has cyclomatic complexity 14 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 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/BlockNoteSummaryView.tsx:170
  • startBackgroundDownloads has cyclomatic complexity 14 and cognitive complexity 13; 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/contexts/OnboardingContext.tsx:514
  • DeviceSelection has cyclomatic complexity 14 and cognitive complexity 12; 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/DeviceSelection.tsx:43
  • LanguagePickerPopover has cyclomatic complexity 14 and cognitive complexity 12; 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/LanguagePickerPopover.tsx:15
  • persistLatestLanguageSelection has cyclomatic complexity 13 and cognitive complexity 24; 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/MeetingDetails/SummaryPanel.tsx:141
  • fetchModelConfig has cyclomatic complexity 13 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 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/contexts/ConfigContext.tsx:233
  • (anonymous) has cyclomatic complexity 13 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/hooks/useTranscriptRecovery.ts:110
  • handleStartRetranscription has cyclomatic complexity 13 and cognitive complexity 13; 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/MeetingDetails/RetranscribeDialog.tsx:199
  • (anonymous) has cyclomatic complexity 13 and cognitive complexity 12; 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/TranscriptView.tsx:263
  • PermissionRow has cyclomatic complexity 13 and cognitive complexity 12; 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/onboarding/shared/PermissionRow.tsx:7
  • DownloadToastContent has cyclomatic complexity 13 and cognitive complexity 12; 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/shared/DownloadProgressToast.tsx:52
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 1295 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 785 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 495 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 480 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.
R4 · Test Coverage5.0 / 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).
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.
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 10 application, 8 tooling and 16 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 (10 application, 8 tooling, 16 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 (10 application, 8 tooling, 16 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 (10 application, 8 tooling, 16 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 (10 application, 8 tooling, 16 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/audioDevices.ts:42, frontend/src/lib/parakeet.ts:38, …
  • 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.
R8 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

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.

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

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.

X1 · Async correctness8.0 / 10Strong✓ Tool-verified

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.

  • This `async` body is polled on an executor's worker thread, and `std::thread::sleep` blocks that thread: for the whole delay no other task scheduled on it makes progress — the Rust form of blocking on a task. Use `tokio::time::sleep(…).await` (or the runtime's own timer), which suspends only this task. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the executor with `tokio::task::spawn_blocking(…).await`. — frontend/src-tauri/src/audio/stream.rs:654
  • 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

What to do

  • Blocking `thread::sleep` inside an `async` body
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

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.

X4 · Structured logging1.7 / 10Critical✓ Tool-verified

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

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types9.8 / 10Exemplary✓ Tool-verified

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 31423 source line(s) of the 173 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. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

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 `?`).

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 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).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

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.

LensScoreRatingImpact
Code Health48%Adequate — gated by D2, X4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture92%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity80%StrongSolid.
Readiness34%Weak — gated by P3, P5, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security57%Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling100%ExemplaryStrongest area.
Event-Driven80%StrongSolid.
Event Sourcing100%ExemplarySolid.
Accessibility48%Adequate — gated by AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance79%StrongSolid.
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 — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 63 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.

  • 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
  • AX6 Interface segregation — AX6 reached only 33% of this repository's production lines — rust (47,402 lines), c (7,790 lines), python (2,219 lines), cpp (1,007 lines), swift (20 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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-11-14T05:24:06Z" level=warning msg="The \"MODEL_NAME\" variable is not set. Defaulting to a blank string." time="2026-11-14T05:24:06Z" level=warning msg="The \"MODEL_NAME\" variable is not set. Defaulting to a blank string." time="2026-11-14T05:24:06Z" 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 does not read html yet; 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+ sibling projects each declaring an entity of their own or taking another project's integration events. 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"]`.
  • 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.
  • 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 — Rust 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
  • 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
  • ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
  • 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • 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.
  • X12 Unreachable branch — X12 reached only 35% of this repository's production lines — rust (47,402 lines), c (7,790 lines), cpp (1,007 lines), swift (20 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — X16 reached only 33% of this repository's production lines — rust (47,402 lines), c (7,790 lines), python (2,219 lines), cpp (1,007 lines), swift (20 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X17 Uncapped recursion over a caller-supplied document — X17 reached only 35% of this repository's production lines — rust (47,402 lines), c (7,790 lines), cpp (1,007 lines), swift (20 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — X23 reached only 35% of this repository's production lines — rust (47,402 lines), c (7,790 lines), cpp (1,007 lines), swift (20 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X24 Document value interpolated into markup unescaped — X24 reached only 35% of this repository's production lines — rust (47,402 lines), c (7,790 lines), cpp (1,007 lines), swift (20 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X3 Exception handling — X3 reached only 35% of this repository's production lines — rust (47,402 lines), c (7,790 lines), cpp (1,007 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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.

Critical — 207 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 35 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 23 more in this group — see findings.md.
AC2 · Forms & labels · <button> with no accessible text · ×17
  • <button> with no accessible text frontend/src/app/_components/SettingsModal.tsx:70 — 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:175 — 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:216 — 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:254 — 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:255 — 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:352 — 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:378 — 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:463 — 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:498 — 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:513 — 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:531 — 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).
D30 · Dependency Vulnerabilities · High CVE · ×17
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×9
  • Click handler on a non-interactive <div> frontend/src/app/_components/SettingsModal.tsx:138 — 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:1001 — 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:1095 — 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:1128 — 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:1324 — 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:570 — 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:728 — 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:91 — 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:95 — 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:115 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
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:1095 — 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.
AC3 · Page structure · <html> without a lang · ×1
  • <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}.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • 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.
ED4 · Outbox / dual-write · Dual write (no outbox) · ×1
  • Dual write (no outbox): SummaryService.process_transcript_background frontend/src-tauri/src/summary/service.rs:335 — `SummaryService.process_transcript_background` performs two independent DURABLE writes — a durable state write (`SummaryProcessesRepository.update_process_completed`, :598) 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).
Serious — 893 finding(s)
D3 · God Classes · FunctionTooLong · ×69
  • FunctionTooLong: ModelSettingsModal.ModelSettingsModal frontend/src/components/ModelSettingsModal.tsx:121 — 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 604 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 504 over it, 6.04× 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: RecordingControls.RecordingControls frontend/src/components/RecordingControls.tsx:34 — FunctionTooLong — RecordingControls runs 375 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 275 over it, 3.75× 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: 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: meetily::run frontend/src-tauri/src/lib.rs:553 — FunctionTooLong — meetily::run runs 329 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 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: 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: 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: DeviceSelection.DeviceSelection frontend/src/components/DeviceSelection.tsx:43 — FunctionTooLong — DeviceSelection runs 295 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 195 over it, 2.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ConfigContext.ConfigProvider frontend/src/contexts/ConfigContext.tsx:101 — FunctionTooLong — ConfigProvider runs 291 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 191 over it, 2.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: 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: meetily::audio::recording_commands::stop_recording_for_session frontend/src-tauri/src/audio/recording_commands.rs:869 — FunctionTooLong — meetily::audio::recording_commands::stop_recording_for_session runs 273 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 173 over it, 2.73× 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:38 — 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: 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.
  • + 44 more in this group — see findings.md.
D2 · Cognitive Complexity · meetily · ×45
  • 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::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::audio::transcription::worker::start_transcription_task (cognitive 63) frontend/src-tauri/src/audio/transcription/worker.rs:181 — meetily::audio::transcription::worker::start_transcription_task has cognitive complexity 63 (threshold 15). Drivers by points: if/else 16 (49 pts), match/switch 3 (7 pts), loops 5 (6 pts), boolean chains 1 (nesting depth added 38). 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_for_session (cognitive 50) frontend/src-tauri/src/audio/recording_commands.rs:869 — meetily::audio::recording_commands::stop_recording_for_session has cognitive complexity 50 (threshold 15). Drivers by points: if/else 22 (30 pts), match/switch 10 (15 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 14). Of this number, 46 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::summary::processor::generate_meeting_summary (cognitive 42) frontend/src-tauri/src/summary/processor.rs:363 — 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::recording_commands::spawn_device_event_processor (cognitive 40) frontend/src-tauri/src/audio/recording_commands.rs:1656 — meetily::audio::recording_commands::spawn_device_event_processor has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (29 pts), loops 2 (4 pts), match/switch 2 (4 pts), boolean chains 3 (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::run (cognitive 37) frontend/src-tauri/src/lib.rs:553 — meetily::run has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (27 pts), match/switch 6 (7 pts), boolean chains 3 (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.
  • 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::recording_commands::trigger_mic_fallback_to_default (cognitive 35) frontend/src-tauri/src/audio/recording_commands.rs:1997 — meetily::audio::recording_commands::trigger_mic_fallback_to_default has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (27 pts), match/switch 4 (6 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.
  • 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::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::audio::recording_commands::swap_linux_stream (cognitive 30) frontend/src-tauri/src/audio/recording_commands.rs:1781 — meetily::audio::recording_commands::swap_linux_stream has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (21 pts), match/switch 3 (5 pts), boolean chains 3, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • 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.
  • + 20 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/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/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/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/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/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/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.
  • No test reaches this file frontend/src/hooks/useModalState.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file frontend/src/components/ui/form.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.
  • + 15 more in this group — see findings.md.
D1 · Cyclomatic Complexity · meetily · ×26
  • 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::recording_commands::stop_recording_for_session (cyclomatic 32) frontend/src-tauri/src/audio/recording_commands.rs:869 — meetily::audio::recording_commands::stop_recording_for_session has cyclomatic complexity 32 (threshold 15). Of this number, 30 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::recording_commands::trigger_mic_fallback_to_default (cyclomatic 27) frontend/src-tauri/src/audio/recording_commands.rs:1997 — meetily::audio::recording_commands::trigger_mic_fallback_to_default has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • 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::audio::transcription::worker::start_transcription_task (cyclomatic 26) frontend/src-tauri/src/audio/transcription/worker.rs:181 — meetily::audio::transcription::worker::start_transcription_task has cyclomatic complexity 26 (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::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::run (cyclomatic 24) frontend/src-tauri/src/lib.rs:553 — meetily::run 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.
  • 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::recording_commands::swap_linux_stream (cyclomatic 21) frontend/src-tauri/src/audio/recording_commands.rs:1781 — meetily::audio::recording_commands::swap_linux_stream 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::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:363 — 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::audio::recording_commands::repair_linux_stream (cyclomatic 19) frontend/src-tauri/src/audio/recording_commands.rs:1926 — meetily::audio::recording_commands::repair_linux_stream has cyclomatic complexity 19 (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::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::audio::recording_commands::spawn_device_event_processor (cyclomatic 17) frontend/src-tauri/src/audio/recording_commands.rs:1656 — meetily::audio::recording_commands::spawn_device_event_processor 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::audio::recording_commands::start_recording_with_meeting_name (cyclomatic 16) frontend/src-tauri/src/audio/recording_commands.rs:430 — meetily::audio::recording_commands::start_recording_with_meeting_name 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.
  • meetily::audio::recording_commands::follow_linux_default (cyclomatic 16) frontend/src-tauri/src/audio/recording_commands.rs:1845 — meetily::audio::recording_commands::follow_linux_default 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.
  • + 1 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×24
  • Hotspot: frontend/src-tauri/src/audio/recording_commands.rs frontend/src-tauri/src/audio/recording_commands.rs:869 — frontend/src-tauri/src/audio/recording_commands.rs changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in meetily::audio::recording_commands::stop_recording_for_session at line 869. 25 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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:34 — frontend/src/components/RecordingControls.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 89 in RecordingControls.RecordingControls at line 34. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/components/Sidebar/index.tsx frontend/src/components/Sidebar/index.tsx:42 — frontend/src/components/Sidebar/index.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 99 in index.Sidebar at line 42. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src/components/Sidebar/index.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/capture/pulse_linux.rs frontend/src-tauri/src/audio/capture/pulse_linux.rs:167 — frontend/src-tauri/src/audio/capture/pulse_linux.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in PulseCapture::run_timed_ready at line 167. 8 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/capture/pulse_linux.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/parakeet_engine/parakeet_engine.rs frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:841 — frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in ParakeetEngine::download_artifacts at line 841. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src-tauri/src/parakeet_engine/parakeet_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/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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/contexts/RecordingStateContext.tsx frontend/src/contexts/RecordingStateContext.tsx:63 — frontend/src/contexts/RecordingStateContext.tsx changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in RecordingStateContext.RecordingStateProvider at line 63. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/hooks/meeting-details/useSummaryGeneration.ts frontend/src/hooks/meeting-details/useSummaryGeneration.ts:170 — frontend/src/hooks/meeting-details/useSummaryGeneration.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in useSummaryGeneration.useSummaryGeneration.handlePollingResult at line 170. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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-tauri/src/lib.rs frontend/src-tauri/src/lib.rs:553 — frontend/src-tauri/src/lib.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in meetily::run at line 553. 5 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/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. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/whisper_engine/whisper_engine.rs frontend/src-tauri/src/whisper_engine/whisper_engine.rs:830 — frontend/src-tauri/src/whisper_engine/whisper_engine.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in WhisperEngine::finish_download at line 830. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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-tauri/src/summary/processor.rs frontend/src-tauri/src/summary/processor.rs:363 — 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 363. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/components/DeviceSelection.tsx frontend/src/components/DeviceSelection.tsx:43 — frontend/src/components/DeviceSelection.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in DeviceSelection.DeviceSelection 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src/components/DeviceSelection.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/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. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/components/Sidebar/SidebarProvider.tsx frontend/src/components/Sidebar/SidebarProvider.tsx:80 — frontend/src/components/Sidebar/SidebarProvider.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in SidebarProvider.SidebarProvider at line 80. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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:335 — frontend/src-tauri/src/summary/service.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in SummaryService::process_transcript_background at line 335. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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-tauri/src/audio/device_monitor.rs frontend/src-tauri/src/audio/device_monitor.rs:280 — frontend/src-tauri/src/audio/device_monitor.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in AudioDeviceMonitor::monitor_loop at line 280. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/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. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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-tauri/src/audio/transcription/worker.rs frontend/src-tauri/src/audio/transcription/worker.rs:181 — frontend/src-tauri/src/audio/transcription/worker.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in meetily::audio::transcription::worker::start_transcription_task at line 181. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/components/MeetingDetails/SummaryPanel.tsx frontend/src/components/MeetingDetails/SummaryPanel.tsx:59 — frontend/src/components/MeetingDetails/SummaryPanel.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in SummaryPanel.SummaryPanel at line 59. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/contexts/ConfigContext.tsx frontend/src/contexts/ConfigContext.tsx:101 — frontend/src/contexts/ConfigContext.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in ConfigContext.ConfigProvider at line 101. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src/contexts/ConfigContext.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 3 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/RecordingSettings.tsx frontend/src/components/RecordingSettings.tsx:25 — frontend/src/components/RecordingSettings.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in RecordingSettings.RecordingSettings at line 25. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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.
  • 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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.
D17 · Explicit Debt · TodoComment · ×24
  • 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.
D3 · God Classes · FileTooLong · ×17
  • 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: audio/recording_commands.rs frontend/src-tauri/src/audio/recording_commands.rs — FileTooLong — 1343 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 40 free functions. The bar is 500 significant lines; this is 843 over it, 2.69× 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 — 1058 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: ModelSettingsModal (121-1417). The bar is 500 significant lines; this is 558 over it, 2.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: api/api.rs frontend/src-tauri/src/api/api.rs — FileTooLong — 997 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 497 over it, 1.99× 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 — 807 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 78% of them inside a single declaration: ParakeetEngine (263-1223). The bar is 500 significant lines; this is 307 over it, 1.61× 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/pipeline.rs frontend/src-tauri/src/audio/pipeline.rs — FileTooLong — 736 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 236 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: whisper_engine/whisper_engine.rs frontend/src-tauri/src/whisper_engine/whisper_engine.rs — FileTooLong — 691 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 191 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/lib.rs frontend/src-tauri/src/lib.rs — FileTooLong — 672 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 172 over it, 1.34× 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 — 640 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: Sidebar (42-882). The bar is 500 significant lines; this is 140 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: 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: audio/stream.rs frontend/src-tauri/src/audio/stream.rs — FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 70% of them inside a single declaration: AudioStream (2 blocks, 56-677). The bar is 500 significant lines; this is 87 over it, 1.17× 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: 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×16
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×15
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D15 · Churn × Complexity Hotspots · Repeated repair · ×13
  • Repeated repair: frontend/src-tauri/src/audio/stream.rs frontend/src-tauri/src/audio/stream.rs:302 — frontend/src-tauri/src/audio/stream.rs changed 12 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is AudioStream::create_pulse_stream at line 302), AT OR 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(linux): notify when system audio fails to start”; “fix(linux): reject failed Pulse inventories and declare audio deps”; “fix(audio): address Linux device and shutdown review feedback”; “fix(audio): reject startup when the resolved microphone fails”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/stream.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 10 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is RecordingManager::start_recording at line 228), AT OR 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): preserve Linux capture through recovery and shutdown”; “fix(audio): harden Linux capture and recording device switching”; “fix(linux): TECH-01 complete ALSA lock + reliable Pulse thread shutdown”; “fix: harden ONNX runtime and recording startup [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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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:57 — frontend/src/services/recordingService.ts changed 8 times in last 90 days and 7 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 57), AT OR 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): prevent concurrent shutdown and gate Linux stress example”; “fix(linux): show the label carried by microphone events”; “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”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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-tauri/src/audio/devices/discovery.rs frontend/src-tauri/src/audio/devices/discovery.rs:9 — frontend/src-tauri/src/audio/devices/discovery.rs changed 8 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 5 (its worst body is meetily::audio::devices::discovery::list_audio_devices at line 9), AT OR 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): address Linux device and shutdown review feedback”; “fix(linux): close remaining ALSA lock gaps + stale-chunk risk found in TECH-01 review”; “fix(linux): TECH-01 complete ALSA lock + reliable Pulse thread shutdown”; “fix(linux): serialize alsa-lib device enumeration to stop heap corruption”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/devices/discovery.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/vad.rs frontend/src-tauri/src/audio/vad.rs:237 — frontend/src-tauri/src/audio/vad.rs changed 7 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 237), AT OR 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(logging): harden retained diagnostics [skip ci]”; “fix(windows): recover from ONNX runtime failures [skip ci]”; “fix(vad): align forced flush payload with timestamps”; “fix(vad): bound flushed segment timestamps”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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/devices/platform/linux.rs frontend/src-tauri/src/audio/devices/platform/linux.rs:160 — frontend/src-tauri/src/audio/devices/platform/linux.rs changed 8 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 9 (its worst body is meetily::audio::devices::platform::linux::configure_linux_audio at line 160), AT OR 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(linux): reject failed Pulse inventories and declare audio deps”; “fix(audio): address Linux device and shutdown review feedback”; “fix(linux): give identical device captions distinct readable numbers”; “fix(linux): TECH-01 complete ALSA lock + reliable Pulse thread shutdown”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/devices/platform/linux.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/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), AT OR 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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-tauri/src/audio/recording_preferences.rs frontend/src-tauri/src/audio/recording_preferences.rs:169 — frontend/src-tauri/src/audio/recording_preferences.rs 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 12 (its worst body is meetily::audio::recording_preferences::resolve_start_devices at line 169), AT OR 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: don't block Start on unresolved legacy devices or failed migration write”; “fix(audio): fall back to default mic for unresolved legacy selection”; “fix(audio): preserve Linux capture through recovery and shutdown”; “fix(audio): finalize automatic stops and migrate legacy device preferences”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/recording_preferences.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/app/meeting-details/page-content.tsx frontend/src/app/meeting-details/page-content.tsx:22 — frontend/src/app/meeting-details/page-content.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 14 (its worst body is page-content.PageContent at line 22), AT OR 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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-tauri/src/audio/devices/microphone.rs frontend/src-tauri/src/audio/devices/microphone.rs:78 — frontend/src-tauri/src/audio/devices/microphone.rs changed 5 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 7 (its worst body is meetily::audio::devices::microphone::find_builtin_input_device at line 78), AT OR 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(linux): reject failed Pulse inventories and declare audio deps”; “fix(audio): harden Linux capture and recording device switching”; “fix(linux): apply microphone eligibility to the default source”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/devices/microphone.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/components/Logo.tsx frontend/src/components/Logo.tsx:15 — frontend/src/components/Logo.tsx changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is Logo.Logo at line 15), AT OR 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]”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +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-tauri/src/summary/commands.rs frontend/src-tauri/src/summary/commands.rs:356 — frontend/src-tauri/src/summary/commands.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is meetily::summary::commands::api_get_summary at line 356), AT OR 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(logging): harden retained diagnostics [skip ci]”; “fix(summary): preserve truthful generation state [skip ci]”; “fix(summary): enforce safe generation lifecycle [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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src-tauri/src/summary/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.
  • Repeated repair: frontend/src-tauri/src/audio/capture/pulse_enumerator.rs frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:162 — frontend/src-tauri/src/audio/capture/pulse_enumerator.rs 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 11 (its worst body is meetily::audio::capture::pulse_enumerator::enumerator_thread at line 162), AT OR 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(linux): reject failed Pulse inventories and declare audio deps”; “fix(audio): harden Linux capture and recording device switching”; “fix(linux): résout le sink par défaut réel du serveur pour l'audio système”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 19:46:54 +05:30' --until='2026-11-13 19:46:54 +05:30' --full-history --no-merges -- frontend/src-tauri/src/audio/capture/pulse_enumerator.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.
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:345 — <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:401 — <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 vulnerability · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×11
  • Duplicated block (12 lines × 2) frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:356 — frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:356-367 | frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:417-428 — 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 `frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:356` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:355` calls `as_deref`, `unwrap_or_default`, `to_string` and `frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:416` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • 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 116 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:806` 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 (12 lines × 2) frontend/src-tauri/src/audio/devices/microphone.rs:98 — frontend/src-tauri/src/audio/devices/microphone.rs:98-109 | frontend/src-tauri/src/audio/devices/speakers.rs:108-119 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/devices/microphone.rs:98` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:1145 — frontend/src-tauri/src/audio/recording_commands.rs:1145-1156 | frontend/src-tauri/src/audio/recording_commands.rs:1160-1171 — 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 `frontend/src-tauri/src/audio/recording_commands.rs:1145` 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 (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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • 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/audio/core-old.rs:779 — frontend/src-tauri/src/audio/core-old.rs:779-790 | frontend/src-tauri/src/audio/devices/platform/windows.rs:177-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 116 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:779` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 2) frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:267 — frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:267-283 | frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:310-321 — 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 `frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:267` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/database/repositories/setting.rs:127` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `frontend/src-tauri/src/database/repositories/setting.rs:126` calls `Ok` and `frontend/src-tauri/src/database/repositories/setting.rs:218` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) frontend/src-tauri/src/ollama/metadata.rs:146 — frontend/src-tauri/src/ollama/metadata.rs:146-157 | frontend/src-tauri/src/ollama/ollama.rs:285-296 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/ollama/metadata.rs:146` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:745` 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.
D3 · God Classes · MethodTooLong · ×9
  • 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:841 — MethodTooLong — download_artifacts runs 223 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 123 over it, 2.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: SummaryService.process_transcript_background frontend/src-tauri/src/summary/service.rs:335 — MethodTooLong — process_transcript_background runs 220 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 120 over it, 2.20× 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 138 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 38 over it, 1.38× 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_with_timestamp frontend/src-tauri/src/audio/pipeline.rs:624 — MethodTooLong — process_audio_data_with_timestamp runs 132 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AudioCapture.new frontend/src-tauri/src/audio/pipeline.rs:444 — MethodTooLong — new runs 116 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 16 over it, 1.16× 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×9
  • Duplicated block (11 lines × 2) frontend/src-tauri/src/api/api.rs:898 — frontend/src-tauri/src/api/api.rs:898-908 | 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 116 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:131` 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 (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 116 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:161` 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 (11 lines × 2) frontend/src-tauri/src/audio/recording_manager.rs:327 — frontend/src-tauri/src/audio/recording_manager.rs:327-337 | frontend/src-tauri/src/audio/recording_manager.rs:359-369 — 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 `frontend/src-tauri/src/audio/recording_manager.rs:327` 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 (11 lines × 2) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:772 — frontend/src-tauri/src/whisper_engine/whisper_engine.rs:772-782 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:794-804 — 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 `frontend/src-tauri/src/whisper_engine/whisper_engine.rs:772` 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 (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:128-138 — 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 94 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/database/repositories/meeting.rs:211` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/parakeet_engine/commands.rs:78` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:1054 — frontend/src-tauri/src/audio/recording_commands.rs:1054-1064 | frontend/src-tauri/src/audio/recording_commands.rs:1080-1090 — 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 `frontend/src-tauri/src/audio/recording_commands.rs:1054` 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×9
  • Duplicated block (9 lines × 2) frontend/src-tauri/src/audio/recording_manager.rs:84 — frontend/src-tauri/src/audio/recording_manager.rs:84-94 | frontend/src-tauri/src/audio/recording_manager.rs:161-169 — 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 `frontend/src-tauri/src/audio/recording_manager.rs:84` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/lib_old_complex.rs:217` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/lib_old_complex.rs:2305` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/parakeet_engine/commands.rs:180` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/whisper_engine/commands.rs:235` 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 (9 lines × 2) frontend/src-tauri/src/audio/core-old.rs:284 — frontend/src-tauri/src/audio/core-old.rs:284-292 | frontend/src-tauri/src/audio/devices/discovery.rs:48-56 — 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/audio/recording_commands.rs:1501 — frontend/src-tauri/src/audio/recording_commands.rs:1501-1509 | frontend/src-tauri/src/audio/recording_commands.rs:1518-1526 — 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 `frontend/src-tauri/src/audio/recording_commands.rs:1501` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/ollama/ollama.rs:299` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/devices/platform/windows.rs:133` 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.
D31 · IaC & Container Security · Medium IaC · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <Select> field component without a label · ×7
  • <Select> field component without a label frontend/src/components/ImportAudio/ImportAudioDialog.tsx:352 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label frontend/src/components/ImportAudio/ImportAudioDialog.tsx:384 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:310 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:345 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label frontend/src/components/ModelSettingsModal.tsx:823 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label frontend/src/components/TranscriptSettings.tsx:110 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
  • <Select> field component without a label frontend/src/components/TranscriptSettings.tsx:134 — This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it.
D35 · Change Coupling · Change coupling · ×7
  • 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: About.tsx ↔ AnalyticsProvider.tsx frontend/src/components/About.tsx:1 — `frontend/src/components/About.tsx` and `frontend/src/components/AnalyticsProvider.tsx` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `df0f9e3a` chore: bump application version to 0.5.0; `419cc083` chore: version bump to v0.4.1; `f6afb882` chore: version bump to v0.4.0 — run `git show` on any of them.
  • Change coupling: REDACTED ↔ TranscriptView.tsx frontend/src/app/page.tsx:1 — `frontend/src/app/page.tsx` and `frontend/src/components/TranscriptView.tsx` change together 71% of the time (12 of the 17 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 12 shared commits counted here, the most recent 3 are `0225df97` UI fixes; `3894ec3c` UI changes; version update; `92b978c8` UX improvements — 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: REDACTED ↔ REDACTED frontend/src/app/page.tsx:1 — `frontend/src/app/page.tsx` and `frontend/src/app/settings/page.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 `6a6a5199` Bugfix/sidebar start and modal fix (#242); `8470e274` Fixes for Smooth UX; `81cb3f77` Removed the onSave — 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 57% of the time (8 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 8 shared commits counted here, the most recent 3 are `defefece` fix(logging): harden retained diagnostics [skip ci]; `b650235c` Bluetooth device fix: Added advanced resampling; `983f3f8e` Meeting transcript chunk time saving: Tauri — 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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×7
  • 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 116 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:146` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/import.rs:779` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (14 lines × 2) frontend/src-tauri/src/audio/recording_manager.rs:332 — frontend/src-tauri/src/audio/recording_manager.rs:332-345 | frontend/src-tauri/src/audio/recording_manager.rs:427-440 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/parakeet_engine/commands.rs:196` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/whisper_engine/commands.rs:251` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) frontend/src-tauri/src/lib_old_complex.rs:1020 — frontend/src-tauri/src/lib_old_complex.rs:1020-1033 | frontend/src-tauri/src/lib_old_complex.rs:1585-1598 — 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 `frontend/src-tauri/src/lib_old_complex.rs:1020` 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 (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.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×6
  • Edited copy of a member (15 corresponding lines) frontend/src-tauri/src/audio/recording_saver.rs:94 — frontend/src-tauri/src/audio/recording_saver.rs:94-117 | frontend/src-tauri/src/audio/recording_saver_old.rs:81-95 — These two members are one piece of code written twice and then edited apart: 15 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.
  • Edited copy of a member (15 corresponding lines) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:648 — frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:648-664 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:814-828 — These two members are one piece of code written twice and then edited apart: 15 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.
  • Edited copy of a member (15 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs:520 — frontend/src-tauri/src/parakeet_engine/commands.rs:520-534 | frontend/src-tauri/src/whisper_engine/commands.rs:512-526 — These two members are one piece of code written twice and then edited apart: 15 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.
  • Edited copy of a member (15 corresponding lines) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:55 — frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:55-69 | frontend/src-tauri/src/summary/summary_engine/model_manager.rs:41-55 — These two members are one piece of code written twice and then edited apart: 15 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.
  • Edited copy of a member (15 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs:55 — frontend/src-tauri/src/parakeet_engine/commands.rs:55-69 | frontend/src-tauri/src/whisper_engine/commands.rs:55-71 — These two members are one piece of code written twice and then edited apart: 15 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.
  • Edited copy of a member (15 corresponding lines) backend/app/db.py:392 — backend/app/db.py:392-410 | backend/app/schema_validator.py:14-28 — These two members are one piece of code written twice and then edited apart: 15 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 · Duplicated block (10 lines × 2) · ×6
  • Duplicated block (10 lines × 2) frontend/src-tauri/src/audio/decoder.rs:332 — frontend/src-tauri/src/audio/decoder.rs:332-341 | frontend/src-tauri/src/audio/encode.rs:60-69 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/decoder.rs:332` 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 (10 lines × 2) frontend/src-tauri/src/audio/level_monitor.rs:99 — frontend/src-tauri/src/audio/level_monitor.rs:99-108 | frontend/src-tauri/src/audio/simple_level_monitor.rs:62-71 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/level_monitor.rs:99` 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/lib.rs:411 — frontend/src-tauri/src/lib.rs:411-420 | 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/system_detector.rs:145 — frontend/src-tauri/src/audio/system_detector.rs:145-154 | frontend/src-tauri/src/audio/system_detector.rs:197-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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/system_detector.rs:145` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `frontend/src-tauri/src/audio/system_detector.rs:207` calls `mut` and `frontend/src-tauri/src/audio/system_detector.rs:155` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) frontend/src-tauri/src/lib.rs:343 — frontend/src-tauri/src/lib.rs:343-352 | frontend/src-tauri/src/lib_old_complex.rs:1699-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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/parakeet_engine/commands.rs:367` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×6
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/analytics/analytics.rs:115` 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 first that the copies are not typed on the same thing: the declarations holding them bind `properties` to `Option<HashMap<String, String>>` in one and `HashMap<String, String>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) frontend/src-tauri/src/audio/recording_manager.rs:76 — frontend/src-tauri/src/audio/recording_manager.rs:76-82 | frontend/src-tauri/src/audio/recording_manager.rs:153-159 — 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 `frontend/src-tauri/src/audio/recording_manager.rs:76` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/lib_old_complex.rs:204` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/summary/summary_engine/sidecar.rs:168` 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 lines × 2) frontend/src-tauri/src/tray.rs:95 — frontend/src-tauri/src/tray.rs:95-101 | frontend/src-tauri/src/tray.rs:193-199 — 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 `frontend/src-tauri/src/tray.rs:95` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 2) frontend/src-tauri/src/audio/core-old.rs:343 — frontend/src-tauri/src/audio/core-old.rs:343-349 | frontend/src-tauri/src/audio/devices/speakers.rs:64-70 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:343` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×6
  • 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `frontend/src-tauri/src/analytics/analytics.rs:320` calls `Some`, `insert`, `to_string` and `frontend/src-tauri/src/analytics/analytics.rs:262` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) frontend/src-tauri/src/audio/pipeline.rs:717 — frontend/src-tauri/src/audio/pipeline.rs:717-721 | 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/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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/summary/summary_engine/sidecar.rs:422` 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 (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:206-211 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/whisper_engine/commands.rs:91` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/recording_manager.rs:248` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (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.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×6
  • 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:202 — 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/DeviceSelection.tsx:143 — frontend/src/components/DeviceSelection.tsx:143 · frontend/src/components/DeviceSelection.tsx:162 — 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.
D29 · Static Analysis (SAST) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · ClassTooLong · ×5
  • ClassTooLong: ModelSettingsModal frontend/src/components/ModelSettingsModal.tsx:1 — ClassTooLong — 964 significant lines (blank, comment-only and punctuation-only lines excluded), 2 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 — 633 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 233 over it, 1.58× 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.
  • ClassTooLong: AudioStream frontend/src-tauri/src/audio/stream.rs:56 — ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods, 2 blocks, lines 56-677. The bar is 400 significant lines; this is 10 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×5
  • Duplicated block (13 lines × 2) frontend/src-tauri/src/audio/core-old.rs:876 — frontend/src-tauri/src/audio/core-old.rs:876-888 | frontend/src-tauri/src/audio/devices/configuration.rs:179-191 — 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 94 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:876` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) frontend/src-tauri/src/audio/pipeline.rs:1151 — frontend/src-tauri/src/audio/pipeline.rs:1151-1163 | frontend/src-tauri/src/audio/pipeline.rs:1193-1205 — 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 `frontend/src-tauri/src/audio/pipeline.rs:1151` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/retranscription.rs:594` 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/summary/templates/loader.rs:153` 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 (13 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:500 — frontend/src-tauri/src/audio/recording_commands.rs:500-512 | frontend/src-tauri/src/audio/recording_commands.rs:715-727 — 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.
D2 · Cognitive Complexity · RecordingSaver · ×4
  • 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:351 — 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.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×4
  • 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 116 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:842` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/lib_old_complex.rs:963` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/parakeet_engine/commands.rs:243` 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 (18 lines × 2) frontend/src-tauri/src/audio/import.rs:760 — frontend/src-tauri/src/audio/import.rs:760-777 | frontend/src-tauri/src/audio/import.rs:806-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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/import.rs:760` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×4
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/devices/platform/windows.rs:143` 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 (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:152-166 — 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 `frontend/src-tauri/src/audio/playback_monitor.rs:104` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (15 lines × 2) frontend/src-tauri/src/audio/transcription/worker.rs:433 — frontend/src-tauri/src/audio/transcription/worker.rs:433-447 | frontend/src-tauri/src/audio/transcription/worker.rs:451-465 — 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 `frontend/src-tauri/src/audio/transcription/worker.rs:433` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/parakeet_engine/commands.rs:182` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×4
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/analytics/analytics.rs:129` 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 (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 94 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • 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. 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 (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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/lib_old_complex.rs:508` 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.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (3.8 · ×3
  • Low contrast Tailwind colour pair (3.8:1) frontend/src/app/meeting-details/page.tsx:255 — 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 (3.8:1) frontend/src/components/ChunkProgressDisplay.tsx:123 — 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 (3.8:1) frontend/src/components/RecordingControls.tsx:352 — 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.
D2 · Cognitive Complexity · MacOSSystemAudioDetector · ×3
  • MacOSSystemAudioDetector::start::system_listener (cognitive 55) frontend/src-tauri/src/audio/system_detector.rs:196 — 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.
D2 · Cognitive Complexity · WhisperEngine · ×3
  • WhisperEngine::finish_download (cognitive 44) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:830 — 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::download_model_with_owner (cognitive 28) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:1000 — 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:200 — 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.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (5 members, 50+ identical tokens) frontend/src-tauri/src/api/api.rs:1017 — frontend/src-tauri/src/api/api.rs:1017-1080 | frontend/src-tauri/src/audio/recording_preferences.rs:438-475 | 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.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×3
  • Edited copy of a member (18 corresponding lines) frontend/src-tauri/src/parakeet_engine/model.rs:187 — frontend/src-tauri/src/parakeet_engine/model.rs:187-204 | frontend/src-tauri/src/parakeet_engine/model.rs:210-229 — These two members are one piece of code written twice and then edited apart: 18 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.
  • Edited copy of a member (18 corresponding lines) frontend/src-tauri/src/lib.rs:407 — frontend/src-tauri/src/lib.rs:407-424 | frontend/src-tauri/src/lib_old_complex.rs:1795-1812 — These two members are one piece of code written twice and then edited apart: 18 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.
  • Edited copy of a member (18 corresponding lines) frontend/src-tauri/src/summary/commands.rs:160 — frontend/src-tauri/src/summary/commands.rs:160-177 | frontend/src-tauri/src/summary/commands.rs:206-223 — These two members are one piece of code written twice and then edited apart: 18 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 (13 corresponding lines) · ×3
  • Edited copy of a member (13 corresponding lines) frontend/src-tauri/src/summary/summary_engine/commands.rs:52 — frontend/src-tauri/src/summary/summary_engine/commands.rs:52-64 | frontend/src-tauri/src/summary/summary_engine/commands.rs:360-382 — These two members are one piece of code written twice and then edited apart: 13 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.
  • Edited copy of a member (13 corresponding lines) frontend/src-tauri/src/summary/commands.rs:139 — frontend/src-tauri/src/summary/commands.rs:139-151 | frontend/src-tauri/src/summary/commands.rs:185-197 — These two members are one piece of code written twice and then edited apart: 13 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.
  • Edited copy of a member (13 corresponding lines) frontend/src-tauri/src/audio/recording_saver.rs:120 — frontend/src-tauri/src/audio/recording_saver.rs:120-132 | frontend/src-tauri/src/audio/recording_saver_old.rs:98-111 — These two members are one piece of code written twice and then edited apart: 13 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 · Duplicated block (21 lines × 2) · ×3
  • Duplicated block (21 lines × 2) frontend/src-tauri/src/audio/core-old.rs:316 — frontend/src-tauri/src/audio/core-old.rs:316-336 | frontend/src-tauri/src/audio/devices/speakers.rs:13-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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:316` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (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 116 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:700` 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 (21 lines × 2) frontend/src-tauri/src/summary/summary_engine/sidecar.rs:558 — frontend/src-tauri/src/summary/summary_engine/sidecar.rs:558-578 | frontend/src-tauri/src/summary/summary_engine/sidecar.rs:606-626 — 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 `frontend/src-tauri/src/summary/summary_engine/sidecar.rs:558` 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×3
  • 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 116 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:759` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (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:216-232 — 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 94 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:908` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×3
  • Duplicated block (16 lines × 2) frontend/src-tauri/src/audio/level_monitor.rs:239 — frontend/src-tauri/src/audio/level_monitor.rs:239-254 | frontend/src-tauri/src/audio/level_monitor.rs:263-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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/level_monitor.rs:239` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (16 lines × 2) frontend/src-tauri/src/lib.rs:296 — frontend/src-tauri/src/lib.rs:296-311 | frontend/src-tauri/src/lib.rs:511-527 — 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 `frontend/src-tauri/src/lib.rs:296` 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 (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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×3
  • 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 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/import.rs:756` 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 (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 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/import.rs:802` 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 (11–12 lines × 2) frontend/src-tauri/src/database/repositories/meeting.rs:184 — frontend/src-tauri/src/database/repositories/meeting.rs:184-194 | frontend/src-tauri/src/database/repositories/meeting.rs:208-219 — 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 matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9–10 lines × 3) · ×3
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/anthropic/anthropic.rs:80` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) frontend/src-tauri/src/audio/pipeline.rs:646 — frontend/src-tauri/src/audio/pipeline.rs:646-651 | frontend/src-tauri/src/audio/pipeline.rs:716-721 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) frontend/src-tauri/src/audio_v2/mixer.rs:73 — frontend/src-tauri/src/audio_v2/mixer.rs:73-78 | frontend/src-tauri/src/audio_v2/mixer.rs:86-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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio_v2/mixer.rs:86` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `frontend/src-tauri/src/audio/import.rs:374` calls `emit_progress` and `frontend/src-tauri/src/audio/import.rs:403` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×3
  • 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:550 — `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.
R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×3
  • Duplicated block (26 lines × 2 locations) frontend/src/app/_components/SettingsModal.tsx:160 — frontend/src/app/_components/SettingsModal.tsx:160 · frontend/src/app/_components/SettingsModal.tsx:201 — 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:163 — frontend/src/components/Sidebar/index.tsx:163 · 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.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×3
  • 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/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.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×3
  • 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>.
AC6 · Visual & motion safety · Focus outline removed inline · ×2
  • 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).
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (3.3 · ×2
  • Low contrast Tailwind colour pair (3.3:1) frontend/src/components/DatabaseImport/HomebrewDatabaseDetector.tsx:120 — 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 (3.3:1) frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx:187 — 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.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (3.6 · ×2
  • Low contrast Tailwind colour pair (3.6:1) frontend/src/components/ParakeetModelManager.tsx:612 — 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 (3.6:1) frontend/src/components/WhisperModelManager.tsx:732 — 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.
D1 · Cyclomatic Complexity · AudioCapture · ×2
  • AudioCapture::process_audio_data_with_timestamp (cyclomatic 38) frontend/src-tauri/src/audio/pipeline.rs:624 — AudioCapture::process_audio_data_with_timestamp 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.
  • AudioCapture::new (cyclomatic 16) frontend/src-tauri/src/audio/pipeline.rs:444 — 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.
D1 · Cyclomatic Complexity · WhisperEngine · ×2
  • WhisperEngine::finish_download (cyclomatic 23) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:830 — 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:1000 — 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.
D2 · Cognitive Complexity · AudioCapture · ×2
  • AudioCapture::process_audio_data_with_timestamp (cognitive 107) frontend/src-tauri/src/audio/pipeline.rs:624 — AudioCapture::process_audio_data_with_timestamp has cognitive complexity 107 (threshold 15). Drivers by points: if/else 40 (92 pts), match/switch 1 (6 pts), loops 1 (5 pts), boolean chains 4 (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:444 — 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.
D2 · Cognitive Complexity · ModelManager · ×2
  • 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.
D2 · Cognitive Complexity · ParakeetEngine · ×2
  • ParakeetEngine::download_artifacts (cognitive 63) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:841 — 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.
D2 · Cognitive Complexity · PostProcessor · ×2
  • 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.
D3 · God Classes · TooManyMethods · ×2
  • 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 — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×2
  • 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.
  • Edited copy of a member (40 corresponding lines) frontend/src-tauri/src/audio/retranscription.rs:581 — frontend/src-tauri/src/audio/retranscription.rs:581-622 | frontend/src-tauri/src/audio/retranscription.rs:683-722 — 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 · Edited copy of a member (49 corresponding lines) · ×2
  • Edited copy of a member (49 corresponding lines) frontend/src-tauri/src/lib_old_complex.rs:2286 — frontend/src-tauri/src/lib_old_complex.rs:2286-2334 | frontend/src-tauri/src/whisper_engine/commands.rs:425-492 — These two members are one piece of code written twice and then edited apart: 49 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.
  • Edited copy of a member (49 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs:75 — frontend/src-tauri/src/parakeet_engine/commands.rs:75-123 | frontend/src-tauri/src/whisper_engine/commands.rs:130-178 — These two members are one piece of code written twice and then edited apart: 49 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 (44 corresponding lines) · ×2
  • Edited copy of a member (44 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs:179 — frontend/src-tauri/src/parakeet_engine/commands.rs:179-226 | frontend/src-tauri/src/whisper_engine/commands.rs:234-277 — These two members are one piece of code written twice and then edited apart: 44 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.
  • Edited copy of a member (44 corresponding lines) frontend/src-tauri/src/api/api.rs:496 — frontend/src-tauri/src/api/api.rs:496-539 | frontend/src-tauri/src/api/api.rs:629-672 — These two members are one piece of code written twice and then edited apart: 44 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 (41 corresponding lines) · ×2
  • Edited copy of a member (41 corresponding lines) frontend/src-tauri/src/audio_v2/compatibility.rs:72 — frontend/src-tauri/src/audio_v2/compatibility.rs:72-113 | frontend/src-tauri/src/audio_v2/compatibility.rs:119-159 — These two members are one piece of code written twice and then edited apart: 41 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.
  • Edited copy of a member (41 corresponding lines) frontend/src-tauri/src/audio/import.rs:262 — frontend/src-tauri/src/audio/import.rs:262-309 | frontend/src-tauri/src/audio/retranscription.rs:98-138 — These two members are one piece of code written twice and then edited apart: 41 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 (28 corresponding lines) · ×2
  • Edited copy of a member (28 corresponding lines) frontend/src-tauri/src/audio/recording_manager.rs:322 — frontend/src-tauri/src/audio/recording_manager.rs:322-349 | frontend/src-tauri/src/audio/recording_manager.rs:352-389 — These two members are one piece of code written twice and then edited apart: 28 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.
  • Edited copy of a member (28 corresponding lines) frontend/src-tauri/src/database/repositories/setting.rs:113 — frontend/src-tauri/src/database/repositories/setting.rs:113-140 | frontend/src-tauri/src/database/repositories/setting.rs:237-267 — These two members are one piece of code written twice and then edited apart: 28 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 (16 corresponding lines) · ×2
  • Edited copy of a member (16 corresponding lines) frontend/src-tauri/src/audio/devices/platform/linux.rs:114 — frontend/src-tauri/src/audio/devices/platform/linux.rs:114-129 | frontend/src-tauri/src/audio/devices/platform/linux.rs:131-146 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) frontend/src-tauri/src/tray.rs:120 — frontend/src-tauri/src/tray.rs:120-135 | frontend/src-tauri/src/tray.rs:137-153 — These two members are one piece of code written twice and then edited apart: 16 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 (19 corresponding lines) · ×2
  • Edited copy of a member (19 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs:15 — frontend/src-tauri/src/parakeet_engine/commands.rs:15-33 | frontend/src-tauri/src/whisper_engine/commands.rs:15-33 — These two members are one piece of code written twice and then edited apart: 19 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.
  • Edited copy of a member (19 corresponding lines) frontend/src-tauri/src/api/api.rs:604 — frontend/src-tauri/src/api/api.rs:604-622 | frontend/src-tauri/src/api/api.rs:718-740 — These two members are one piece of code written twice and then edited apart: 19 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 (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) frontend/src-tauri/src/database/repositories/setting.rs:179 — frontend/src-tauri/src/database/repositories/setting.rs:179-206 | frontend/src-tauri/src/database/repositories/setting.rs:211-232 — These two members are one piece of code written twice and then edited apart: 22 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.
  • Edited copy of a member (22 corresponding lines) frontend/src-tauri/src/database/repositories/setting.rs:47 — frontend/src-tauri/src/database/repositories/setting.rs:47-68 | frontend/src-tauri/src/database/repositories/summary.rs:92-122 — These two members are one piece of code written twice and then edited apart: 22 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 (9 corresponding lines) · ×2
  • Edited copy of a member (9 corresponding lines) frontend/src-tauri/src/audio/core-old.rs:33 — frontend/src-tauri/src/audio/core-old.rs:33-41 | frontend/src-tauri/src/audio/devices/configuration.rs:26-34 — These two members are one piece of code written twice and then edited apart: 9 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.
  • Edited copy of a member (9 corresponding lines) frontend/src-tauri/src/audio/import.rs:37 — frontend/src-tauri/src/audio/import.rs:37-45 | frontend/src-tauri/src/audio/retranscription.rs:31-39 — These two members are one piece of code written twice and then edited apart: 9 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 (7 corresponding lines) · ×2
  • Edited copy of a member (7 corresponding lines) frontend/src-tauri/src/analytics/analytics.rs:245 — frontend/src-tauri/src/analytics/analytics.rs:245-251 | frontend/src-tauri/src/analytics/analytics.rs:265-271 — These two members are one piece of code written twice and then edited apart: 7 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.
  • Edited copy of a member (7 corresponding lines) frontend/src-tauri/src/summary/summary_engine/model_manager.rs:341 — frontend/src-tauri/src/summary/summary_engine/model_manager.rs:341-348 | frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:614-620 — These two members are one piece of code written twice and then edited apart: 7 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 copies of one member (3 members, 12+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 12+ corresponding lines) frontend/src-tauri/src/analytics/commands.rs:117 — frontend/src-tauri/src/analytics/commands.rs:117-128 | frontend/src-tauri/src/analytics/commands.rs:237-248 | frontend/src-tauri/src/analytics/commands.rs:251-262 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) frontend/src-tauri/src/analytics/commands.rs:33 — frontend/src-tauri/src/analytics/commands.rs:33-44 | frontend/src-tauri/src/analytics/commands.rs:89-100 | frontend/src-tauri/src/analytics/commands.rs:209-220 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×2
  • Edited copy of a member (14 corresponding lines) frontend/src-tauri/src/analytics/commands.rs:10 — frontend/src-tauri/src/analytics/commands.rs:10-23 | frontend/src-tauri/src/lib_old_complex.rs:1816-1830 — These two members are one piece of code written twice and then edited apart: 14 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.
  • Edited copy of a member (14 corresponding lines) frontend/src-tauri/src/audio/transcription/parakeet_provider.rs:27 — frontend/src-tauri/src/audio/transcription/parakeet_provider.rs:27-44 | frontend/src-tauri/src/audio/transcription/whisper_provider.rs:26-39 — These two members are one piece of code written twice and then edited apart: 14 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 · Duplicated block (35 lines × 2) · ×2
  • 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 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/import.rs:518` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `frontend/src-tauri/src/audio/import.rs:554` calls `remove_dir_all` and `frontend/src-tauri/src/audio/retranscription.rs:346` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (35 lines × 2) frontend/src-tauri/src/audio/recording_saver_old.rs:134 — frontend/src-tauri/src/audio/recording_saver_old.rs:134-168 | frontend/src-tauri/src/audio/recording_saver_old.rs:199-233 — 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.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×2
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/transcription/engine.rs:67` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (24 lines × 2) frontend/src-tauri/src/tray.rs:67 — frontend/src-tauri/src/tray.rs:67-90 | frontend/src-tauri/src/tray.rs:165-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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/tray.rs:67` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `frontend/src-tauri/src/tray.rs:60` calls `is_recording`, `set_tray_state` and `frontend/src-tauri/src/tray.rs:161` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2
  • 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:103-124 — 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 94 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/lib_old_complex.rs:940` 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.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×2
  • Duplicated block (15 lines × 4) frontend/src-tauri/src/audio/core-old.rs:518 — frontend/src-tauri/src/audio/core-old.rs:518-532 | frontend/src-tauri/src/audio/core-old.rs:548-562 | frontend/src-tauri/src/audio/core-old.rs:578-592 | frontend/src-tauri/src/audio/core-old.rs:608-622 — all 4 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 `frontend/src-tauri/src/audio/core-old.rs:518` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (15 lines × 4) frontend/src-tauri/src/audio/recording_preferences.rs:449 — frontend/src-tauri/src/audio/recording_preferences.rs:449-463 | 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.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×2
  • 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:215-226 — 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 94 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:890` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (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.
D4 · Code Duplication · Duplicated block (8–12 lines × 2) · ×2
  • Duplicated block (8–12 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:2077 — frontend/src-tauri/src/audio/recording_commands.rs:2077-2088 | frontend/src-tauri/src/audio/recording_commands.rs:2120-2127 — 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 `frontend/src-tauri/src/audio/recording_commands.rs:2077` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8–12 lines × 2) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:546 — frontend/src-tauri/src/whisper_engine/whisper_engine.rs:546-557 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:667-674 — 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 `frontend/src-tauri/src/whisper_engine/whisper_engine.rs:546` 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×2
  • Duplicated block (10 lines × 3) frontend/src-tauri/src/audio/recording_manager.rs:331 — frontend/src-tauri/src/audio/recording_manager.rs:331-340 | frontend/src-tauri/src/audio/recording_manager.rs:363-372 | frontend/src-tauri/src/audio/recording_manager.rs:426-435 — 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 (10 lines × 3) frontend/src-tauri/src/audio/stream.rs:876 — frontend/src-tauri/src/audio/stream.rs:876-885 | frontend/src-tauri/src/audio/system_audio_stream.rs:189-198 | frontend/src-tauri/src/audio_v2/stream.rs:355-364 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `frontend/src-tauri/src/audio/stream.rs:888` calls `has_active_streams`, `is_some` and `frontend/src-tauri/src/audio_v2/stream.rs:365` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×2
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/anthropic/anthropic.rs:155` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (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.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×2
  • 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:895 — frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:895-901 | frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:919-926 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/anthropic/anthropic.rs:107` 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 (11 lines × 3) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:585 — frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:585-595 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:772-782 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:794-804 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:585` 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.
R10 · Code Duplication · Duplicated block (33 lines × 2 locations) · ×2
  • 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.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×2
  • 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.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×2
  • 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.
R7 · Dead Code · Dead file (~19 LoC) · ×2
  • Dead file (~19 LoC) frontend/src/components/MainNav/index.tsx — no import path from any entry point (10 application, 8 tooling, 16 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 (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~6 LoC) · ×2
  • Dead file (~6 LoC) frontend/src/app/metadata.ts — no import path from any entry point (10 application, 8 tooling, 16 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 (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~0 LoC) · ×2
  • Dead file (~0 LoC) frontend/src/components/AudioPlayer.tsx — no import path from any entry point (10 application, 8 tooling, 16 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 (10 application, 8 tooling, 16 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
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.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.0 · ×1
  • Low contrast colour pair in CSS (4.0:1) backend/whisper-custom/server/public/index.html:31 — `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.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (4.3 · ×1
  • Low contrast Tailwind colour pair (4.3:1) frontend/src/components/AudioBackendSelector.tsx:160 — 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.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (4.4 · ×1
  • 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.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (1.9 · ×1
  • Low contrast Tailwind colour pair (1.9:1) frontend/src/components/ChunkProgressDisplay.tsx:107 — 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.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (2.3 · ×1
  • Low contrast Tailwind colour pair (2.3:1) frontend/src/components/ChunkProgressDisplay.tsx:115 — 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.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (3.2 · ×1
  • Low contrast Tailwind colour pair (3.2:1) frontend/src/components/PermissionWarning.tsx:70 — 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.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (1.5 · ×1
  • Low contrast Tailwind colour pair (1.5:1) frontend/src/components/RecordingControls.tsx:378 — 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.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (2.1 · ×1
  • Low contrast Tailwind colour pair (2.1:1) frontend/src/components/RecordingControls.tsx:416 — 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.
D1 · Cyclomatic Complexity · index.AISummary (cyclomatic 93) · ×1
  • 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.
D1 · Cyclomatic Complexity · RecordingControls.RecordingControls (cyclomatic 89) · ×1
  • RecordingControls.RecordingControls (cyclomatic 89) frontend/src/components/RecordingControls.tsx:34 — RecordingControls.RecordingControls has cyclomatic complexity 89 (threshold 15). Of this number, 36 points are the body's own statements and 53 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.
D1 · Cyclomatic Complexity · ModelSettingsModal.ModelSettingsModal (cyclomatic 83) · ×1
  • ModelSettingsModal.ModelSettingsModal (cyclomatic 83) frontend/src/components/ModelSettingsModal.tsx:121 — 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.
D1 · Cyclomatic Complexity · OnboardingContext.OnboardingProvider (cyclomatic 62) · ×1
  • 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.
D1 · Cyclomatic Complexity · TranscriptContext.TranscriptProvider (cyclomatic 58) · ×1
  • 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.
D1 · Cyclomatic Complexity · WhisperModelManager.ModelManager (cyclomatic 57) · ×1
  • 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.
D1 · Cyclomatic Complexity · ParakeetModelManager.ParakeetModelManager (cyclomatic 54) · ×1
  • 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.
D1 · Cyclomatic Complexity · RetranscribeDialog.RetranscribeDialog (cyclomatic 54) · ×1
  • 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.
D1 · Cyclomatic Complexity · BuiltInModelManager.BuiltInModelManager (cyclomatic 53) · ×1
  • 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.
D1 · Cyclomatic Complexity · VirtualizedTranscriptView.VirtualizedTranscriptView (cyclomatic 53) · ×1
  • 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.
D1 · Cyclomatic Complexity · ImportAudioDialog.ImportAudioDialog (cyclomatic 50) · ×1
  • 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.
D1 · Cyclomatic Complexity · ConfigContext.ConfigProvider (cyclomatic 47) · ×1
  • ConfigContext.ConfigProvider (cyclomatic 47) frontend/src/contexts/ConfigContext.tsx:101 — 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 233, 200, 353, …). 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.
D1 · Cyclomatic Complexity · ModelManager · ×1
  • 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.
D1 · Cyclomatic Complexity · UpdateDialog.UpdateDialog (cyclomatic 41) · ×1
  • 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.
D1 · Cyclomatic Complexity · TranscriptView.TranscriptView (cyclomatic 41) · ×1
  • 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.
D1 · Cyclomatic Complexity · useRecordingStop.useRecordingStop.handleRecordingStop (cyclomatic 41) · ×1
  • 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.
D1 · Cyclomatic Complexity · AudioStream · ×1
  • 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.
D1 · Cyclomatic Complexity · page.MeetingDetailsContent (cyclomatic 36) · ×1
  • 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.
D1 · Cyclomatic Complexity · DeviceSelection.DeviceSelection (cyclomatic 36) · ×1
  • DeviceSelection.DeviceSelection (cyclomatic 36) frontend/src/components/DeviceSelection.tsx:43 — DeviceSelection.DeviceSelection has cyclomatic complexity 36 (threshold 15). Of this number, 16 points are the body's own statements and 20 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.
D1 · Cyclomatic Complexity · Block.BlockComponent · ×1
  • 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.
D1 · Cyclomatic Complexity · ParakeetEngine · ×1
  • ParakeetEngine::download_artifacts (cyclomatic 33) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:841 — 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.
D1 · Cyclomatic Complexity · SidebarProvider.SidebarProvider (cyclomatic 33) · ×1
  • SidebarProvider.SidebarProvider (cyclomatic 33) frontend/src/components/Sidebar/SidebarProvider.tsx:80 — SidebarProvider.SidebarProvider has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 7 function items inside it that branch (a function literal at line 233, a function literal at line 114, a function literal at line 216, …). 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.
D1 · Cyclomatic Complexity · ParakeetModelManager.ModelCard (cyclomatic 33) · ×1
  • 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.
D1 · Cyclomatic Complexity · SummaryPanel.SummaryPanel (cyclomatic 33) · ×1
  • 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.
D1 · Cyclomatic Complexity · TranscriptRecovery.TranscriptRecovery (cyclomatic 33) · ×1
  • 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.
D1 · Cyclomatic Complexity · SummaryService · ×1
  • SummaryService::process_transcript_background (cyclomatic 32) frontend/src-tauri/src/summary/service.rs:335 — 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.
D1 · Cyclomatic Complexity · BlockNoteSummaryView.BlockNoteSummaryView (cyclomatic 32) · ×1
  • 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.
D1 · Cyclomatic Complexity · MacOSSystemAudioDetector · ×1
  • 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.
D1 · Cyclomatic Complexity · main.process_transcript_background (cyclomatic 30) · ×1
  • 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.
D1 · Cyclomatic Complexity · PulseCapture · ×1
  • PulseCapture::run_timed_ready (cyclomatic 29) frontend/src-tauri/src/audio/capture/pulse_linux.rs:167 — PulseCapture::run_timed_ready 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.
D1 · Cyclomatic Complexity · TranscriptSettings.TranscriptSettings (cyclomatic 29) · ×1
  • 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.
D1 · Cyclomatic Complexity · useSummaryGeneration.useSummaryGeneration.handlePollingResult (cyclomatic 29) · ×1
  • 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.
D1 · Cyclomatic Complexity · main.get_summary (cyclomatic 28) · ×1
  • 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.
D1 · Cyclomatic Complexity · ModelSettingsModal.ModelSettingsModal · ×1
  • ModelSettingsModal.ModelSettingsModal::handleSave (cyclomatic 28) frontend/src/components/ModelSettingsModal.tsx:626 — 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.
D1 · Cyclomatic Complexity · WhisperModelManager.ModelCard (cyclomatic 27) · ×1
  • 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.
D1 · Cyclomatic Complexity · page.Home (cyclomatic 26) · ×1
  • 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.
D1 · Cyclomatic Complexity · RecordingStateContext.RecordingStateProvider (cyclomatic 26) · ×1
  • RecordingStateContext.RecordingStateProvider (cyclomatic 26) frontend/src/contexts/RecordingStateContext.tsx:63 — RecordingStateContext.RecordingStateProvider has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 15 function items inside it that branch (a function literal at line 282, a function literal at line 168, a function literal at line 178, …). 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.
D1 · Cyclomatic Complexity · ChunkProgressDisplay.ChunkProgressDisplay (cyclomatic 25) · ×1
  • 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.
D1 · Cyclomatic Complexity · LanguagePickerPopover.LanguagePickerPopover (cyclomatic 25) · ×1
  • 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.
D1 · Cyclomatic Complexity · PreferenceSettings.PreferenceSettings (cyclomatic 25) · ×1
  • 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.
D1 · Cyclomatic Complexity · index.Sidebar · ×1
  • index.Sidebar::renderItem (cyclomatic 25) frontend/src/components/Sidebar/index.tsx:556 — 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.
D1 · Cyclomatic Complexity · useRecordingStart.useRecordingStart (cyclomatic 25) · ×1
  • 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.
D1 · Cyclomatic Complexity · AudioDeviceMonitor · ×1
  • AudioDeviceMonitor::monitor_loop (cyclomatic 24) frontend/src-tauri/src/audio/device_monitor.rs:280 — AudioDeviceMonitor::monitor_loop 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.
D1 · Cyclomatic Complexity · SidecarManager · ×1
  • 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.
D1 · Cyclomatic Complexity · PermissionWarning.PermissionWarning (cyclomatic 24) · ×1
  • 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.
D1 · Cyclomatic Complexity · DownloadProgressToast.useDownloadProgressToast (cyclomatic 23) · ×1
  • 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.
D1 · Cyclomatic Complexity · useAutoScroll.useAutoScroll (cyclomatic 23) · ×1
  • 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.
D1 · Cyclomatic Complexity · SummaryModelSettings.SummaryModelSettings (cyclomatic 22) · ×1
  • 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.
D1 · Cyclomatic Complexity · auto-detect-gpu.detectGPU (cyclomatic 20) · ×1
  • 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.
D1 · Cyclomatic Complexity · useModelConfiguration.useModelConfiguration (cyclomatic 20) · ×1
  • 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.
D1 · Cyclomatic Complexity · TranscriptProcessor.process_transcript (cyclomatic 19) · ×1
  • 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.
D1 · Cyclomatic Complexity · RecordingSettings.RecordingSettings (cyclomatic 18) · ×1
  • RecordingSettings.RecordingSettings (cyclomatic 18) frontend/src/components/RecordingSettings.tsx:25 — RecordingSettings.RecordingSettings has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (savePreferences, a function literal at line 42, handleDeviceChange, …). 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.
D1 · Cyclomatic Complexity · useCopyOperations.useCopyOperations.handleCopySummary (cyclomatic 18) · ×1
  • 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.
D1 · Cyclomatic Complexity · AnalyticsConsentSwitch.AnalyticsConsentSwitch (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · LegacyDatabaseImport.LegacyDatabaseImport (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · LanguageSelection.LanguageSelection (cyclomatic 16) · ×1
  • 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.
D1 · Cyclomatic Complexity · DownloadProgressStep.DownloadProgressStep · ×1
  • 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.
D1 · Cyclomatic Complexity · useSummaryGeneration.useSummaryGeneration.processSummary (cyclomatic 16) · ×1
  • 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.
D2 · Cognitive Complexity · RecordingControls.RecordingControls (cognitive 108) · ×1
  • RecordingControls.RecordingControls (cognitive 108) frontend/src/components/RecordingControls.tsx:34 — RecordingControls.RecordingControls has cognitive complexity 108 (threshold 15). Drivers by points: ternaries 16 (47 pts), if/else 20 (29 pts), boolean chains 26, error handling 6 (nesting depth added 40). Of this number, 44 points are the body's own statements and 64 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.
D2 · Cognitive Complexity · index.AISummary (cognitive 104) · ×1
  • 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.
D2 · Cognitive Complexity · DownloadProgressStep.DownloadProgressStep (cognitive 83) · ×1
  • 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.
D2 · Cognitive Complexity · main.process_transcript_background (cognitive 74) · ×1
  • 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.
D2 · Cognitive Complexity · AudioStream · ×1
  • 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.
D2 · Cognitive Complexity · AudioDeviceMonitor · ×1
  • AudioDeviceMonitor::monitor_loop (cognitive 70) frontend/src-tauri/src/audio/device_monitor.rs:280 — AudioDeviceMonitor::monitor_loop has cognitive complexity 70 (threshold 15). Drivers by points: if/else 15 (49 pts), match/switch 4 (12 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 46). 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.
D2 · Cognitive Complexity · OnboardingContext.OnboardingProvider (cognitive 67) · ×1
  • 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.
D2 · Cognitive Complexity · ParakeetModelManager.ParakeetModelManager (cognitive 65) · ×1
  • 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.
D2 · Cognitive Complexity · SidecarManager · ×1
  • 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.
D2 · Cognitive Complexity · useRecordingStop.useRecordingStop.handleRecordingStop (cognitive 62) · ×1
  • 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.
D2 · Cognitive Complexity · WhisperModelManager.ModelManager (cognitive 57) · ×1
  • 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.
D2 · Cognitive Complexity · ConfigContext.ConfigProvider (cognitive 57) · ×1
  • ConfigContext.ConfigProvider (cognitive 57) frontend/src/contexts/ConfigContext.tsx:101 — 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 233, 200, 184, …). 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.
D2 · Cognitive Complexity · TranscriptContext.TranscriptProvider (cognitive 57) · ×1
  • 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.
D2 · Cognitive Complexity · useRecordingStart.useRecordingStart (cognitive 56) · ×1
  • 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.
D2 · Cognitive Complexity · main.get_summary (cognitive 55) · ×1
  • 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.
D2 · Cognitive Complexity · ModelSettingsModal.ModelSettingsModal (cognitive 55) · ×1
  • ModelSettingsModal.ModelSettingsModal (cognitive 55) frontend/src/components/ModelSettingsModal.tsx:121 — 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.
D2 · Cognitive Complexity · PulseCapture · ×1
  • PulseCapture::run_timed_ready (cognitive 54) frontend/src-tauri/src/audio/capture/pulse_linux.rs:167 — PulseCapture::run_timed_ready has cognitive complexity 54 (threshold 15). Drivers by points: if/else 18 (39 pts), match/switch 2 (8 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 28). 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.
D2 · Cognitive Complexity · RetranscribeDialog.RetranscribeDialog (cognitive 52) · ×1
  • 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.
D2 · Cognitive Complexity · Block.BlockComponent · ×1
  • 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.
D2 · Cognitive Complexity · ImportAudioDialog.ImportAudioDialog (cognitive 48) · ×1
  • 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.
D2 · Cognitive Complexity · TranscriptRecovery.TranscriptRecovery (cognitive 45) · ×1
  • 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.
D2 · Cognitive Complexity · UpdateDialog.UpdateDialog (cognitive 44) · ×1
  • 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.
D2 · Cognitive Complexity · SummaryService · ×1
  • SummaryService::process_transcript_background (cognitive 43) frontend/src-tauri/src/summary/service.rs:335 — 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.
D2 · Cognitive Complexity · useSummaryGeneration.useSummaryGeneration.handlePollingResult (cognitive 42) · ×1
  • 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.
D2 · Cognitive Complexity · auto-detect-gpu.detectGPU (cognitive 40) · ×1
  • 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.
D2 · Cognitive Complexity · SidebarProvider.SidebarProvider (cognitive 38) · ×1
  • SidebarProvider.SidebarProvider (cognitive 38) frontend/src/components/Sidebar/SidebarProvider.tsx:80 — SidebarProvider.SidebarProvider has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (21 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 38 points belong to 7 function items inside it that branch (a function literal at line 233, a function literal at line 114, 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.
D2 · Cognitive Complexity · BuiltInModelManager.BuiltInModelManager (cognitive 37) · ×1
  • 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.
D2 · Cognitive Complexity · VirtualizedTranscriptView.VirtualizedTranscriptView (cognitive 36) · ×1
  • 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.
D2 · Cognitive Complexity · BlockNoteSummaryView.BlockNoteSummaryView (cognitive 35) · ×1
  • 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.
D2 · Cognitive Complexity · AudioMixer · ×1
  • 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.
D2 · Cognitive Complexity · ModelSettingsModal.ModelSettingsModal · ×1
  • ModelSettingsModal.ModelSettingsModal::handleSave (cognitive 30) frontend/src/components/ModelSettingsModal.tsx:626 — 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.
D2 · Cognitive Complexity · DeviceSelection.DeviceSelection (cognitive 30) · ×1
  • DeviceSelection.DeviceSelection (cognitive 30) frontend/src/components/DeviceSelection.tsx:43 — DeviceSelection.DeviceSelection has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 11, if/else 11, error handling 4, ternaries 4. Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 10 function items inside it that branch (getDeviceMetadata, a function literal at line 101, handleMicDeviceChange, …). 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.
D2 · Cognitive Complexity · page.MeetingDetailsContent (cognitive 29) · ×1
  • 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.
D2 · Cognitive Complexity · index.Sidebar · ×1
  • index.Sidebar::renderItem (cognitive 29) frontend/src/components/Sidebar/index.tsx:556 — 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.
D2 · Cognitive Complexity · TranscriptView.TranscriptView (cognitive 29) · ×1
  • 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.
D2 · Cognitive Complexity · TranscriptProcessor.process_transcript (cognitive 28) · ×1
  • 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.
D2 · Cognitive Complexity · SummaryModelSettings.SummaryModelSettings (cognitive 28) · ×1
  • 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.
D2 · Cognitive Complexity · useAutoScroll.useAutoScroll (cognitive 28) · ×1
  • 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.
D2 · Cognitive Complexity · RecordingStateContext.RecordingStateProvider (cognitive 27) · ×1
  • RecordingStateContext.RecordingStateProvider (cognitive 27) frontend/src/contexts/RecordingStateContext.tsx:63 — RecordingStateContext.RecordingStateProvider has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14, boolean chains 6, ternaries 4, error handling 3. None of this is in the body itself: all 27 points belong to 15 function items inside it that branch (a function literal at line 282, a function literal at line 168, a function literal at line 244, …). 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.
D2 · Cognitive Complexity · useModelConfiguration.useModelConfiguration (cognitive 27) · ×1
  • 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.
D2 · Cognitive Complexity · page.Home (cognitive 26) · ×1
  • 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.
D2 · Cognitive Complexity · ParallelProcessor · ×1
  • 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.
D2 · Cognitive Complexity · llama_helper · ×1
  • 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.
D2 · Cognitive Complexity · SummaryPanel.SummaryPanel · ×1
  • 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.
D2 · Cognitive Complexity · DownloadProgressToast.useDownloadProgressToast (cognitive 24) · ×1
  • 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.
D2 · Cognitive Complexity · DatabaseManager · ×1
  • 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.
D2 · Cognitive Complexity · ModelState · ×1
  • 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.
D2 · Cognitive Complexity · ParakeetModelManager.ModelCard (cognitive 23) · ×1
  • 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.
D2 · Cognitive Complexity · PreferenceSettings.PreferenceSettings (cognitive 23) · ×1
  • 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.
D2 · Cognitive Complexity · ParakeetModel · ×1
  • ParakeetModel::decode_sequence (cognitive 21) frontend/src-tauri/src/parakeet_engine/model.rs:341 — ParakeetModel::decode_sequence has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 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.
D2 · Cognitive Complexity · AudioLevelMonitor · ×1
  • 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.
D2 · Cognitive Complexity · AnalyticsConsentSwitch.AnalyticsConsentSwitch (cognitive 20) · ×1
  • 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.
D2 · Cognitive Complexity · WhisperModelManager.ModelCard (cognitive 20) · ×1
  • 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.
D2 · Cognitive Complexity · DownloadProgressToast.DownloadToastContent (cognitive 20) · ×1
  • 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.
D2 · Cognitive Complexity · ContinuousVadProcessor · ×1
  • ContinuousVadProcessor::process_chunk (cognitive 19) frontend/src-tauri/src/audio/vad.rs:237 — ContinuousVadProcessor::process_chunk has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (2 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.
D2 · Cognitive Complexity · RecordingSettings.RecordingSettings (cognitive 19) · ×1
  • RecordingSettings.RecordingSettings (cognitive 19) frontend/src/components/RecordingSettings.tsx:25 — RecordingSettings.RecordingSettings has cognitive complexity 19 (threshold 15). Drivers by points: error handling 6 (7 pts), ternaries 5 (6 pts), boolean chains 5, if/else 1 (nesting depth added 2). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 6 function items inside it that branch (savePreferences, a function literal at line 42, handleDeviceChange, …). 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.
D2 · Cognitive Complexity · LanguagePickerPopover.LanguagePickerPopover (cognitive 19) · ×1
  • 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.
D2 · Cognitive Complexity · PermissionWarning.PermissionWarning (cognitive 19) · ×1
  • 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.
D2 · Cognitive Complexity · LoudnessNormalizer · ×1
  • 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.
D2 · Cognitive Complexity · LegacyDatabaseImport.LegacyDatabaseImport (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · useRecordingStart.useRecordingStart.handleRecordingStart (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · HardwareProfile · ×1
  • 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.
D2 · Cognitive Complexity · ChunkProgressDisplay.ChunkProgressDisplay (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · TranscriptSettings.TranscriptSettings (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · TranscriptView.cleanRepetitions (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · PermissionRow.PermissionRow (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · useTranscriptRecovery.useTranscriptRecovery.recoverMeeting (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · layout.RootLayout (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · MeetingDetailsSplitView.MeetingDetailsSplitView (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · SummaryGeneratorButtonGroup.SummaryGeneratorButtonGroup (cognitive 16) · ×1
  • 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: index.tsx → About.tsx, AnalyticsConsentSwitch.tsx, AnalyticsProvider.tsx frontend/src/components/Sidebar/index.tsx — `frontend/src/components/Sidebar/index.tsx` changes together with 3 other files — `frontend/src/components/About.tsx`, `frontend/src/components/AnalyticsConsentSwitch.tsx`, `frontend/src/components/AnalyticsProvider.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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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.
D4 · Code Duplication · Near-duplicate member pair (167 shared lines) · ×1
  • Near-duplicate member pair (167 shared lines) frontend/src-tauri/src/audio/recording_commands.rs:433 — frontend/src-tauri/src/audio/recording_commands.rs:433-642 | frontend/src-tauri/src/audio/recording_commands.rs:659-859 — These two members are variants of one another: 167 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 · Near-duplicate member pair (133 shared lines) · ×1
  • 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.
D4 · Code Duplication · Near-duplicate member pair (88 shared lines) · ×1
  • Near-duplicate member pair (88 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: 88 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 · Near-duplicate member pair (80 shared lines) · ×1
  • Near-duplicate member pair (80 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: 80 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 · Near-duplicate member pair (36 shared lines) · ×1
  • 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 · 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.
D4 · Code Duplication · Edited copy of a member (85 corresponding lines) · ×1
  • Edited copy of a member (85 corresponding lines) frontend/src-tauri/src/audio/stream.rs:308 — frontend/src-tauri/src/audio/stream.rs:308-392 | frontend/src-tauri/src/audio/stream.rs:402-498 — These two members are one piece of code written twice and then edited apart: 85 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 (104 corresponding lines) · ×1
  • Edited copy of a member (104 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs:232 — frontend/src-tauri/src/parakeet_engine/commands.rs:232-344 | frontend/src-tauri/src/whisper_engine/commands.rs:282-385 — These two members are one piece of code written twice and then edited apart: 104 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 (56 corresponding lines) · ×1
  • Edited copy of a member (56 corresponding lines) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:545 — frontend/src-tauri/src/whisper_engine/whisper_engine.rs:545-660 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:666-721 — These two members are one piece of code written twice and then edited apart: 56 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 (62 corresponding lines) · ×1
  • Edited copy of a member (62 corresponding lines) frontend/src-tauri/src/audio/core-old.rs:863 — frontend/src-tauri/src/audio/core-old.rs:863-924 | frontend/src-tauri/src/audio/devices/configuration.rs:159-232 — These two members are one piece of code written twice and then edited apart: 62 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 (52 corresponding lines) · ×1
  • Edited copy of a member (52 corresponding lines) frontend/src-tauri/src/tray.rs:56 — frontend/src-tauri/src/tray.rs:56-118 | frontend/src-tauri/src/tray.rs:155-206 — These two members are one piece of code written twice and then edited apart: 52 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 (45 corresponding lines) · ×1
  • Edited copy of a member (45 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-70 — These two members are one piece of code written twice and then edited apart: 45 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 (59 corresponding lines) · ×1
  • Edited copy of a member (59 corresponding lines) frontend/src-tauri/src/audio/recording_saver_old.rs:114 — frontend/src-tauri/src/audio/recording_saver_old.rs:114-180 | frontend/src-tauri/src/audio/recording_saver_old.rs:184-242 — These two members are one piece of code written twice and then edited apart: 59 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 (46 corresponding lines) · ×1
  • Edited copy of a member (46 corresponding lines) frontend/src-tauri/src/summary/summary_engine/sidecar.rs:557 — frontend/src-tauri/src/summary/summary_engine/sidecar.rs:557-602 | frontend/src-tauri/src/summary/summary_engine/sidecar.rs:605-658 — These two members are one piece of code written twice and then edited apart: 46 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 copies of one member (3 members, 37+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 37+ corresponding lines) frontend/src-tauri/src/audio/playback_monitor.rs:35 — frontend/src-tauri/src/audio/playback_monitor.rs:35-79 | frontend/src-tauri/src/audio/playback_monitor.rs:82-118 | frontend/src-tauri/src/audio/playback_monitor.rs:121-166 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:337 — frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:337-371 | frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:390-432 — These two members are one piece of code written twice and then edited apart: 35 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 (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) frontend/src-tauri/src/audio/recording_state.rs:135 — frontend/src-tauri/src/audio/recording_state.rs:135-154 | frontend/src-tauri/src/audio/recording_state.rs:411-430 — These two members are one piece of code written twice and then edited apart: 20 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 (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) frontend/src-tauri/src/api/api.rs:551 — frontend/src-tauri/src/api/api.rs:551-596 | frontend/src-tauri/src/api/api.rs:682-710 — These two members are one piece of code written twice and then edited apart: 29 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 (43 corresponding lines) · ×1
  • Edited copy of a member (43 corresponding lines) frontend/src-tauri/src/audio/devices/microphone.rs:78 — frontend/src-tauri/src/audio/devices/microphone.rs:78-120 | frontend/src-tauri/src/audio/devices/speakers.rs:85-139 — These two members are one piece of code written twice and then edited apart: 43 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 (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) frontend/src-tauri/src/analytics/analytics.rs:101 — frontend/src-tauri/src/analytics/analytics.rs:101-126 | frontend/src-tauri/src/analytics/analytics.rs:426-455 — These two members are one piece of code written twice and then edited apart: 26 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 (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) frontend/src-tauri/src/audio/recording_commands.rs:1316 — frontend/src-tauri/src/audio/recording_commands.rs:1316-1346 | frontend/src-tauri/src/audio/recording_commands.rs:1350-1380 — These two members are one piece of code written twice and then edited apart: 31 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 (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) frontend/src-tauri/src/console_utils/console_utils.rs:22 — frontend/src-tauri/src/console_utils/console_utils.rs:22-61 | frontend/src-tauri/src/console_utils/console_utils.rs:64-102 — These two members are one piece of code written twice and then edited apart: 39 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 (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) frontend/src-tauri/src/audio/device_detection.rs:287 — frontend/src-tauri/src/audio/device_detection.rs:287-324 | frontend/src-tauri/src/audio/device_detection.rs:334-375 — These two members are one piece of code written twice and then edited apart: 38 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 (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:1198 — frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:1198-1222 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:1130-1153 — These two members are one piece of code written twice and then edited apart: 24 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 (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs:154 — frontend/src-tauri/src/parakeet_engine/commands.rs:154-176 | frontend/src-tauri/src/whisper_engine/commands.rs:209-231 — These two members are one piece of code written twice and then edited apart: 23 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 (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) frontend/src-tauri/src/audio/core-old.rs:207 — frontend/src-tauri/src/audio/core-old.rs:207-233 | frontend/src-tauri/src/audio/devices/platform/macos.rs:7-35 — These two members are one piece of code written twice and then edited apart: 27 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 copies of one member (3 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 22+ corresponding lines) frontend/src-tauri/src/api/api.rs:775 — frontend/src-tauri/src/api/api.rs:775-804 | frontend/src-tauri/src/api/api.rs:812-835 | frontend/src-tauri/src/api/api.rs:932-953 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) backend/app/db.py:628 — backend/app/db.py:628-643 | backend/app/db.py:750-767 | backend/app/db.py:864-878 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:458 — frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:458-478 | frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:480-503 | frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:507-524 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) frontend/src-tauri/src/analytics/analytics.rs:299 — frontend/src-tauri/src/analytics/analytics.rs:299-307 | frontend/src-tauri/src/analytics/analytics.rs:327-334 — These two members are one piece of code written twice and then edited apart: 8 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 (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) frontend/src-tauri/src/summary/templates/loader.rs:39 — frontend/src-tauri/src/summary/templates/loader.rs:39-55 | frontend/src-tauri/src/summary/templates/loader.rs:64-80 — These two members are one piece of code written twice and then edited apart: 17 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 (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs:41 — frontend/src-tauri/src/parakeet_engine/commands.rs:41-52 | frontend/src-tauri/src/whisper_engine/commands.rs:41-52 — These two members are one piece of code written twice and then edited apart: 12 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 copies of one member (3 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) frontend/src-tauri/src/api/api.rs:428 — frontend/src-tauri/src/api/api.rs:428-436 | frontend/src-tauri/src/api/api.rs:444-459 | frontend/src-tauri/src/api/api.rs:469-489 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs:364 — frontend/src-tauri/src/parakeet_engine/commands.rs:364-376 | frontend/src-tauri/src/whisper_engine/commands.rs:388-404 | frontend/src-tauri/src/whisper_engine/commands.rs:407-419 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 11+ corresponding lines) frontend/src-tauri/src/notifications/commands.rs:50 — frontend/src-tauri/src/notifications/commands.rs:50-60 | frontend/src-tauri/src/notifications/commands.rs:66-76 | frontend/src-tauri/src/notifications/commands.rs:83-96 | frontend/src-tauri/src/notifications/commands.rs:102-112 | frontend/src-tauri/src/notifications/commands.rs:145-155 | frontend/src-tauri/src/notifications/commands.rs:162-172 | frontend/src-tauri/src/notifications/commands.rs:178-188 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) frontend/src-tauri/src/database/repositories/summary.rs:160 — frontend/src-tauri/src/database/repositories/summary.rs:160-185 | frontend/src-tauri/src/database/repositories/summary.rs:191-215 — These two members are one piece of code written twice and then edited apart: 25 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 copies of one member (4 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) frontend/src-tauri/src/parakeet_engine/commands.rs:126 — frontend/src-tauri/src/parakeet_engine/commands.rs:126-137 | frontend/src-tauri/src/parakeet_engine/commands.rs:140-151 | frontend/src-tauri/src/whisper_engine/commands.rs:181-192 | frontend/src-tauri/src/whisper_engine/commands.rs:195-206 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) frontend/src-tauri/src/lib.rs:399 — frontend/src-tauri/src/lib.rs:399-404 | frontend/src-tauri/src/lib_old_complex.rs:1787-1792 — These two members are one piece of code written twice and then edited apart: 6 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 (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) frontend/src-tauri/src/audio/import.rs:678 — frontend/src-tauri/src/audio/import.rs:678-687 | frontend/src-tauri/src/audio/retranscription.rs:509-519 — These two members are one piece of code written twice and then edited apart: 10 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 copies of one member (3 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 6+ corresponding lines) frontend/src-tauri/src/anthropic/anthropic.rs:166 — frontend/src-tauri/src/anthropic/anthropic.rs:166-171 | frontend/src-tauri/src/groq/groq.rs:160-165 | frontend/src-tauri/src/openai/openai.rs:189-194 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (71 lines × 2) · ×1
  • Duplicated block (71 lines × 2) frontend/src-tauri/src/audio/stream.rs:506 — frontend/src-tauri/src/audio/stream.rs:506-576 | frontend/src-tauri/src/audio_v2/stream.rs:90-160 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (109–110 lines × 2) · ×1
  • Duplicated block (109–110 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:518 — frontend/src-tauri/src/audio/recording_commands.rs:518-627 | frontend/src-tauri/src/audio/recording_commands.rs:733-841 — 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.
D4 · Code Duplication · Duplicated block (60–63 lines × 2) · ×1
  • 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 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/import.rs:561` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `frontend/src-tauri/src/audio/import.rs:627` calls `remove_dir_all` and `frontend/src-tauri/src/audio/retranscription.rs:417` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (45 lines × 2) · ×1
  • Duplicated block (45 lines × 2) frontend/src-tauri/src/audio/recording_commands.rs:436 — frontend/src-tauri/src/audio/recording_commands.rs:436-480 | frontend/src-tauri/src/audio/recording_commands.rs:664-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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/recording_commands.rs:436` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `frontend/src-tauri/src/audio/recording_commands.rs:662` calls `is_some` and `frontend/src-tauri/src/audio/recording_commands.rs:435` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (48 lines × 2) · ×1
  • Duplicated block (48 lines × 2) frontend/src-tauri/src/lib_old_complex.rs:1060 — frontend/src-tauri/src/lib_old_complex.rs:1060-1107 | frontend/src-tauri/src/lib_old_complex.rs:1254-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.
D4 · Code Duplication · Duplicated block (17–30 lines × 2) · ×1
  • Duplicated block (17–30 lines × 2) frontend/src-tauri/src/whisper_engine/whisper_engine.rs:558 — frontend/src-tauri/src/whisper_engine/whisper_engine.rs:558-587 | frontend/src-tauri/src/whisper_engine/whisper_engine.rs:676-692 — 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 `frontend/src-tauri/src/whisper_engine/whisper_engine.rs:558` 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.
D4 · Code Duplication · Duplicated block (38 lines × 2) · ×1
  • Duplicated block (38 lines × 2) frontend/src-tauri/src/audio/import.rs:450 — frontend/src-tauri/src/audio/import.rs:450-487 | frontend/src-tauri/src/audio/retranscription.rs:259-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 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/import.rs:450` 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.
D4 · Code Duplication · Duplicated block (45–51 lines × 2) · ×1
  • Duplicated block (45–51 lines × 2) frontend/src-tauri/src/audio/stream.rs:315 — frontend/src-tauri/src/audio/stream.rs:315-359 | frontend/src-tauri/src/audio/stream.rs:412-462 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/stream.rs:315` 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.
D4 · Code Duplication · Duplicated block (19–21 lines × 2) · ×1
  • Duplicated block (19–21 lines × 2) frontend/src-tauri/src/audio/stream.rs:361 — frontend/src-tauri/src/audio/stream.rs:361-379 | frontend/src-tauri/src/audio/stream.rs:467-487 — 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 `frontend/src-tauri/src/audio/stream.rs:467` 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.
D4 · Code Duplication · Duplicated block (18 lines × 5) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (15–18 lines × 2) · ×1
  • Duplicated block (15–18 lines × 2) frontend/src-tauri/src/audio/system_detector.rs:224 — frontend/src-tauri/src/audio/system_detector.rs:224-241 | frontend/src-tauri/src/audio/system_detector.rs:292-306 — 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 `frontend/src-tauri/src/audio/system_detector.rs:224` 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) frontend/src-tauri/src/audio/transcription/worker.rs:123 — frontend/src-tauri/src/audio/transcription/worker.rs:123-139 | frontend/src-tauri/src/audio/transcription/worker.rs:142-159 — 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 `frontend/src-tauri/src/audio/transcription/worker.rs:123` 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. 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.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) frontend/src-tauri/src/summary/summary_engine/sidecar.rs:127 — frontend/src-tauri/src/summary/summary_engine/sidecar.rs:127-157 | frontend/src-tauri/src/summary/summary_engine/sidecar.rs:183-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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/summary/summary_engine/sidecar.rs:127` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) frontend/src-tauri/src/audio/transcription/worker.rs:92 — frontend/src-tauri/src/audio/transcription/worker.rs:92-107 | frontend/src-tauri/src/audio/transcription/worker.rs:124-139 | frontend/src-tauri/src/audio/transcription/worker.rs:143-158 — 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 `frontend/src-tauri/src/audio/transcription/worker.rs:92` 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.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×1
  • Duplicated block (14–16 lines × 2) 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 — 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.
D4 · Code Duplication · Duplicated block (12–15 lines × 3) · ×1
  • 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `frontend/src-tauri/src/audio/audio_processing.rs:629` calls `replace` and `frontend/src-tauri/src/audio/audio_processing.rs:670` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13–15 lines × 2) · ×1
  • Duplicated block (13–15 lines × 2) frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:462 — frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:462-474 | frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:484-498 — 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 `frontend/src-tauri/src/audio/capture/pulse_enumerator.rs:462` 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. 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • 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 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/import.rs:729` 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.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) frontend/src-tauri/src/audio/recording_commands.rs:2097 — frontend/src-tauri/src/audio/recording_commands.rs:2097-2109 | frontend/src-tauri/src/audio/recording_commands.rs:2139-2151 | frontend/src-tauri/src/audio/recording_commands.rs:2158-2170 — 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 `frontend/src-tauri/src/audio/recording_commands.rs:2097` 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. 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.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) frontend/src-tauri/src/api/api.rs:1055 — frontend/src-tauri/src/api/api.rs:1055-1066 | 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/api/api.rs:1055` 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.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/recording_saver.rs:98` 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.
D4 · Code Duplication · Duplicated block (11 lines × 5) · ×1
  • 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:178-188 | frontend/src-tauri/src/audio/devices/configuration.rs:215-225 — 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 94 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:890` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `frontend/src-tauri/src/audio/devices/configuration.rs:176` calls `unwrap_or_else`, `into_inner` and `frontend/src-tauri/src/audio/core-old.rs:874` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–11 lines × 2) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `frontend/src-tauri/src/audio/core-old.rs:253` 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.
D4 · Code Duplication · Duplicated block (7–9 lines × 3) · ×1
  • Duplicated block (7–9 lines × 3) frontend/src-tauri/src/audio/playback_monitor.rs:39 — frontend/src-tauri/src/audio/playback_monitor.rs:39-47 | frontend/src-tauri/src/audio/playback_monitor.rs:85-92 | frontend/src-tauri/src/audio/playback_monitor.rs:132-138 — 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.
D4 · Code Duplication · Duplicated block (20–23 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×1
  • 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.
P5 · DR & Backup · No DR/backup evidence · ×1
  • 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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×1
  • Sync-over-async blocking frontend/src-tauri/src/audio/stream.rs:630 — `stop` is async and calls thread::sleep — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (18 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (18 clone groups) frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:75 — 18 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 7 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 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 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 18 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 · Duplication concentrated across 6 sibling directories (7 clone groups) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (48 lines × 2 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (45 lines × 2 locations) · ×1
  • Duplicated block (45 lines × 2 locations) frontend/src/components/DeviceSelection.tsx:279 — frontend/src/components/DeviceSelection.tsx:279 · frontend/src/components/DeviceSelection.tsx:367 — 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.
R10 · Code Duplication · Duplicated block (44 lines × 2 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (37 lines × 2 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (19 lines × 3 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (16 lines × 3 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (14 lines × 3 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) frontend/src/components/Sidebar/index.tsx:465 — frontend/src/components/Sidebar/index.tsx:465 · frontend/src/components/Sidebar/index.tsx:518 — 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.
R2 · Cyclomatic Complexity · Complex function ModelSettingsModal (cyclomatic 81, cognitive 72) · ×1
  • Complex function ModelSettingsModal (cyclomatic 81, cognitive 72) frontend/src/components/ModelSettingsModal.tsx:121 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 41, cognitive 62) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function RecordingControls (cyclomatic 36, cognitive 24) · ×1
  • Complex function RecordingControls (cyclomatic 36, cognitive 24) frontend/src/components/RecordingControls.tsx:34 — RecordingControls has cyclomatic complexity 36 and cognitive complexity 24; 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.
R2 · Cyclomatic Complexity · Complex function handleKeyDown (cyclomatic 35, cognitive 49) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function ModelCard (cyclomatic 33, cognitive 25) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function VirtualizedTranscriptView (cyclomatic 33, cognitive 20) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 31, cognitive 29) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 31, cognitive 23) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 29, cognitive 44) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function handleSave (cyclomatic 28, cognitive 30) · ×1
  • Complex function handleSave (cyclomatic 28, cognitive 30) frontend/src/components/ModelSettingsModal.tsx:626 — 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.
R2 · Cyclomatic Complexity · Complex function ModelCard (cyclomatic 26, cognitive 23) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function ImportAudioDialog (cyclomatic 25, cognitive 21) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function renderItem (cyclomatic 25, cognitive 20) · ×1
  • Complex function renderItem (cyclomatic 25, cognitive 20) frontend/src/components/Sidebar/index.tsx:556 — 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.
R2 · Cyclomatic Complexity · Complex function poll (cyclomatic 21, cognitive 21) · ×1
  • Complex function poll (cyclomatic 21, cognitive 21) frontend/src/components/Sidebar/SidebarProvider.tsx:233 — 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.
R2 · Cyclomatic Complexity · Complex function RetranscribeDialog (cyclomatic 21, cognitive 15) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function detectGPU (cyclomatic 20, cognitive 40) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function fetchModelConfig (cyclomatic 20, cognitive 27) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function PermissionWarning (cyclomatic 20, cognitive 17) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function TranscriptSettings (cyclomatic 20, cognitive 16) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 19, cognitive 25) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function fetchModelConfig (cyclomatic 18, cognitive 26) · ×1
  • Complex function fetchModelConfig (cyclomatic 18, cognitive 26) frontend/src/components/ModelSettingsModal.tsx:267 — fetchModelConfig has cyclomatic complexity 18 and cognitive complexity 26; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 18, cognitive 20) · ×1
  • Complex function (anonymous) (cyclomatic 18, cognitive 20) frontend/src/components/RecordingControls.tsx:91 — (anonymous) has cyclomatic complexity 18 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 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 17) · ×1
  • Complex function (anonymous) (cyclomatic 17, cognitive 17) frontend/src/hooks/meeting-details/useSummaryGeneration.ts:307 — (anonymous) has cyclomatic complexity 17 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 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.
R2 · Cyclomatic Complexity · Complex function UpdateDialog (cyclomatic 17, cognitive 13) · ×1
  • Complex function UpdateDialog (cyclomatic 17, cognitive 13) frontend/src/components/UpdateDialog.tsx:23 — UpdateDialog has cyclomatic complexity 17 and cognitive complexity 13; 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.
R2 · Cyclomatic Complexity · Complex function renderDownloadCard (cyclomatic 16, cognitive 15) · ×1
  • Complex function renderDownloadCard (cyclomatic 16, cognitive 15) frontend/src/components/onboarding/steps/DownloadProgressStep.tsx:402 — renderDownloadCard has cyclomatic complexity 16 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.
R2 · Cyclomatic Complexity · Complex function SummaryPanel (cyclomatic 16, cognitive 13) · ×1
  • Complex function SummaryPanel (cyclomatic 16, cognitive 13) frontend/src/components/MeetingDetails/SummaryPanel.tsx:59 — SummaryPanel has cyclomatic complexity 16 and cognitive complexity 13; 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.
R2 · Cyclomatic Complexity · Complex function TranscriptRecovery (cyclomatic 16, cognitive 13) · ×1
  • Complex function TranscriptRecovery (cyclomatic 16, cognitive 13) frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:34 — TranscriptRecovery has cyclomatic complexity 16 and cognitive complexity 13; 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.
R2 · Cyclomatic Complexity · Complex function getModelTagline (cyclomatic 15, cognitive 13) · ×1
  • Complex function getModelTagline (cyclomatic 15, cognitive 13) frontend/src/lib/whisper.ts:195 — getModelTagline has cyclomatic complexity 15 and cognitive complexity 13; 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.
R2 · Cyclomatic Complexity · Complex function checkAutoStartRecording (cyclomatic 14, cognitive 36) · ×1
  • Complex function checkAutoStartRecording (cyclomatic 14, cognitive 36) frontend/src/hooks/useRecordingStart.ts:212 — checkAutoStartRecording has cyclomatic complexity 14 and cognitive complexity 36; 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.
R2 · Cyclomatic Complexity · Complex function getMarkdown (cyclomatic 14, cognitive 16) · ×1
  • Complex function getMarkdown (cyclomatic 14, cognitive 16) frontend/src/components/AISummary/BlockNoteSummaryView.tsx:170 — getMarkdown has cyclomatic complexity 14 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 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.
R2 · Cyclomatic Complexity · Complex function startBackgroundDownloads (cyclomatic 14, cognitive 13) · ×1
  • Complex function startBackgroundDownloads (cyclomatic 14, cognitive 13) frontend/src/contexts/OnboardingContext.tsx:514 — startBackgroundDownloads has cyclomatic complexity 14 and cognitive complexity 13; 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.
R2 · Cyclomatic Complexity · Complex function DeviceSelection (cyclomatic 14, cognitive 12) · ×1
  • Complex function DeviceSelection (cyclomatic 14, cognitive 12) frontend/src/components/DeviceSelection.tsx:43 — DeviceSelection has cyclomatic complexity 14 and cognitive complexity 12; 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.
R2 · Cyclomatic Complexity · Complex function LanguagePickerPopover (cyclomatic 14, cognitive 12) · ×1
  • Complex function LanguagePickerPopover (cyclomatic 14, cognitive 12) frontend/src/components/LanguagePickerPopover.tsx:15 — LanguagePickerPopover has cyclomatic complexity 14 and cognitive complexity 12; 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.
R2 · Cyclomatic Complexity · Complex function persistLatestLanguageSelection (cyclomatic 13, cognitive 24) · ×1
  • Complex function persistLatestLanguageSelection (cyclomatic 13, cognitive 24) frontend/src/components/MeetingDetails/SummaryPanel.tsx:141 — persistLatestLanguageSelection has cyclomatic complexity 13 and cognitive complexity 24; 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.
R2 · Cyclomatic Complexity · Complex function fetchModelConfig (cyclomatic 13, cognitive 20) · ×1
  • Complex function fetchModelConfig (cyclomatic 13, cognitive 20) frontend/src/contexts/ConfigContext.tsx:233 — fetchModelConfig has cyclomatic complexity 13 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 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 18) · ×1
  • Complex function (anonymous) (cyclomatic 13, cognitive 18) frontend/src/hooks/useTranscriptRecovery.ts:110 — (anonymous) has cyclomatic complexity 13 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleStartRetranscription (cyclomatic 13, cognitive 13) · ×1
  • Complex function handleStartRetranscription (cyclomatic 13, cognitive 13) frontend/src/components/MeetingDetails/RetranscribeDialog.tsx:199 — handleStartRetranscription has cyclomatic complexity 13 and cognitive complexity 13; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 12) · ×1
  • Complex function (anonymous) (cyclomatic 13, cognitive 12) frontend/src/components/TranscriptView.tsx:263 — (anonymous) has cyclomatic complexity 13 and cognitive complexity 12; 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.
R2 · Cyclomatic Complexity · Complex function PermissionRow (cyclomatic 13, cognitive 12) · ×1
  • Complex function PermissionRow (cyclomatic 13, cognitive 12) frontend/src/components/onboarding/shared/PermissionRow.tsx:7 — PermissionRow has cyclomatic complexity 13 and cognitive complexity 12; 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.
R2 · Cyclomatic Complexity · Complex function DownloadToastContent (cyclomatic 13, cognitive 12) · ×1
  • Complex function DownloadToastContent (cyclomatic 13, cognitive 12) frontend/src/components/shared/DownloadProgressToast.tsx:52 — DownloadToastContent has cyclomatic complexity 13 and cognitive complexity 12; 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.
R3 · Large Files · frontend/src/components/ModelSettingsModal.tsx · ×1
  • frontend/src/components/ModelSettingsModal.tsx: 1295 lines of code frontend/src/components/ModelSettingsModal.tsx:1 — frontend/src/components/ModelSettingsModal.tsx has 1295 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: 785 lines of code frontend/src/components/Sidebar/index.tsx:1 — frontend/src/components/Sidebar/index.tsx has 785 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: 495 lines of code frontend/src/contexts/ConfigContext.tsx:1 — frontend/src/contexts/ConfigContext.tsx has 495 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: 480 lines of code frontend/src/components/RecordingControls.tsx:1 — frontend/src/components/RecordingControls.tsx has 480 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.
R6 · Tooling · No test script · ×1
  • 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.
R7 · Dead Code · Dead file (~294 LoC) · ×1
  • Dead file (~294 LoC) frontend/src/components/ChunkProgressDisplay.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~275 LoC) · ×1
  • Dead file (~275 LoC) frontend/src/hooks/useAudioPlayer.ts — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~264 LoC) · ×1
  • Dead file (~264 LoC) frontend/src/hooks/useProcessingProgress.ts — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~231 LoC) · ×1
  • Dead file (~231 LoC) frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~178 LoC) · ×1
  • Dead file (~178 LoC) frontend/src/components/ui/form.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~169 LoC) · ×1
  • Dead file (~169 LoC) frontend/src/hooks/meeting-details/useModelConfiguration.ts — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~150 LoC) · ×1
  • Dead file (~150 LoC) frontend/src/components/DatabaseImport/HomebrewDatabaseDetector.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~140 LoC) · ×1
  • Dead file (~140 LoC) frontend/src/components/ui/sheet.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~132 LoC) · ×1
  • Dead file (~132 LoC) frontend/src/components/molecules/form-components/form-input-item.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~130 LoC) · ×1
  • Dead file (~130 LoC) frontend/src/components/ModelDownloadProgress.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~105 LoC) · ×1
  • Dead file (~105 LoC) frontend/src/components/BluetoothPlaybackWarning.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~98 LoC) · ×1
  • Dead file (~98 LoC) frontend/src/lib/builtin-ai.ts — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~92 LoC) · ×1
  • Dead file (~92 LoC) frontend/src/components/ConsoleToggle.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~90 LoC) · ×1
  • Dead file (~90 LoC) frontend/src/components/molecules/form-components/form-select-item.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~59 LoC) · ×1
  • Dead file (~59 LoC) frontend/src/components/molecules/form-components/form-input-switch.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~35 LoC) · ×1
  • Dead file (~35 LoC) frontend/src/components/CustomDialog.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~28 LoC) · ×1
  • Dead file (~28 LoC) frontend/src/components/ui/progress.tsx — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~27 LoC) · ×1
  • Dead file (~27 LoC) frontend/src-tauri/src/audio/system_audio_types.ts — no import path from any entry point (10 application, 8 tooling, 16 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
R7 · Dead Code · Dead file (~25 LoC) · ×1
  • Dead file (~25 LoC) frontend/src/constants/modelDefaults.ts — no import path from any entry point (10 application, 8 tooling, 16 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 · Blocking `thread · ×1
  • Blocking `thread::sleep` inside an `async` body frontend/src-tauri/src/audio/stream.rs:654 — This `async` body is polled on an executor's worker thread, and `std::thread::sleep` blocks that thread: for the whole delay no other task scheduled on it makes progress — the Rust form of blocking on a task. Use `tokio::time::sleep(…).await` (or the runtime's own timer), which suspends only this task. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the executor with `tokio::task::spawn_blocking(…).await`.
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.
Minor — 167 finding(s)
D24 · Comment Value · redundant comment · ×55
  • redundant comment frontend/src-tauri/src/audio/system_audio_types.ts:7 — "List available system audio devices" repeats the code it sits on: 4 of its 5 words (list, system, audio, devices) are already in `listSystemAudioDevicesCommand(): Promise<string[]>;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src-tauri/src/audio/system_audio_types.ts:16 — "Stop monitoring system audio usage" repeats the code it sits on: 4 of its 5 words (stop, monitoring, system, audio) are already in `stopSystemAudioMonitoring(): Promise<void>;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src-tauri/src/audio/system_audio_types.ts:19 — "Get the current status of system audio monitoring" repeats the code it sits on: 5 of its 6 words (get, status, system, audio, monitoring) are already in `getSystemAudioMonitoringStatus(): Promise<boolean>;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/app/layout.tsx:110 — "Listen for tray recording toggle request" repeats the code it sits on: 4 of its 5 words (listen, recording, toggle, request) are already in `const unlisten = listen('request-recording-toggle', () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/app/layout.tsx:211 — "Handle import dialog close" repeats the code it sits on: 4 of its 4 words (handle, import, dialog, close) are already in `const handleImportDialogClose = useCallback((open: boolean) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/app/page.tsx:65 — "Track page view" repeats the code it sits on: 3 of its 3 words (track, page, view) are already in `Analytics.trackPageView('home');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/AISummary/index.tsx:469 — "Context menu state" repeats the code it sits on: 3 of its 3 words (context, menu, state) are already in `const [contextMenu, setContextMenu] = useState<{`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/AISummary/index.tsx:555 — "Select the new block" repeats the code it sits on: 3 of its 3 words (select, new, block) are already in `setSelectedBlocks([newBlockId]);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/AnalyticsConsentSwitch.tsx:46 — "Track that user copied their ID" repeats the code it sits on: 4 of its 4 words (track, user, copied, id) are already in `await Analytics.track('user_id_copied', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/AnalyticsConsentSwitch.tsx:103 — "Start analytics session with the same user ID" repeats the code it sits on: 5 of its 5 words (start, analytics, session, user, id) are already in `await Analytics.startSession(userId);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/AnalyticsProvider.tsx:109 — "Check and track first launch (after analytics is initialized)" repeats the code it sits on: 5 of its 6 words (check, track, first, launch, analytics) are already in `await Analytics.checkAndTrackFirstLaunch();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/AnalyticsProvider.tsx:112 — "Track app started" repeats the code it sits on: 3 of its 3 words (track, app, started) are already in `await Analytics.trackAppStarted();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/AnalyticsProvider.tsx:115 — "Check and track daily usage" repeats the code it sits on: 4 of its 4 words (check, track, daily, usage) are already in `await Analytics.checkAndTrackDailyUsage();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/DatabaseImport/LegacyDatabaseImport.tsx:36 — "Detect database from selected path" repeats the code it sits on: 4 of its 4 words (detect, database, selected, path) are already in `const dbPath = await invoke<string | null>('detect_legacy_database', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/DeviceSelection.tsx:52 — "Filter devices by type" repeats the code it sits on: 3 of its 3 words (filter, devices, type) are already in `const inputDevices = devices.filter(device => device.device_type === 'Input');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/DeviceSelection.tsx:184 — "Start audio level monitoring" repeats the code it sits on: 4 of its 4 words (start, audio, level, monitoring) are already in `const startAudioLevelMonitoring = async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/DeviceSelection.tsx:204 — "Stop audio level monitoring" repeats the code it sits on: 4 of its 4 words (stop, audio, level, monitoring) are already in `const stopAudioLevelMonitoring = async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/DeviceSelection.tsx:216 — "Toggle audio level monitoring" repeats the code it sits on: 4 of its 4 words (toggle, audio, level, monitoring) are already in `const toggleAudioLevelMonitoring = async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/LanguageSelection.tsx:171 — "Find the selected language name for display" repeats the code it sits on: 4 of its 5 words (find, selected, language, name) are already in `const selectedLanguageName = LANGUAGES.find(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/ModelSettingsModal.tsx:157 — "Custom OpenAI state" repeats the code it sits on: 4 of its 4 words (custom, open, ai, state) are already in `const [customOpenAIEndpoint, setCustomOpenAIEndpoint] = useState<string>(modelConfig.customOpenAIEndpoint || '');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/ModelSettingsModal.tsx:680 — "Test custom OpenAI connection" repeats the code it sits on: 5 of its 5 words (test, custom, open, ai, connection) are already in `const testCustomOpenAIConnection = async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/ModelSettingsModal.tsx:787 — "Download completed, refresh models list" repeats the code it sits on: 5 of its 5 words (download, completed, refresh, models, list) are already in `console.log(`[ModelSettingsModal] Download completed for ${modelName}, refreshing list`);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/PreferenceSettings.tsx:58 — "Notification enabled means both started and stopped notifications are enabled" repeats the code it sits on: 5 of its 6 words (notification, enabled, started, stopped, notifications) are already in `const enabled =`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/Sidebar/index.tsx:82 — "State for edit modal" repeats the code it sits on: 3 of its 3 words (state, edit, modal) are already in `const [editModalState, setEditModalState] = useState<{ isOpen: boolean; meetingId: string | null; currentTitle: string } …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment frontend/src/components/Sidebar/index.tsx:187 — "Handle model config save" repeats the code it sits on: 4 of its 4 words (handle, model, config, save) are already in `const handleSaveModelConfig = async (config: ModelConfig) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • + 30 more in this group — see findings.md.
X4 · Structured logging · Interpolated log message defeats structured logging · ×40
  • 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.
  • + 15 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×24
  • 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:280 — `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:619 — `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:105 — `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:1135 — `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:777 — `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:889 — `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.
X7 · Silent fallback defaults · Pending state with no failure state · ×12
  • Pending state with no failure state frontend/src/components/About.tsx:77 — The view draws `Checking...` under `isChecking`, but `isChecking` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/AnalyticsConsentSwitch.tsx:175 — The view draws `<Loader2 class="w-4 h-4 animate-spin text-gray-500"/>` under `isProcessing`, but `isProcessing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/PreferenceSettings.tsx:138 — The view draws `Loading Preferences...` under `isLoadingPreferences && ! notificationSettings && ! storageLocations`, but `isLoadingPreferences` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/PreferenceSettings.tsx:143 — The view draws `Loading Preferences...` under `notificationsEnabled === null && ! isLoadingPreferences`, but `notificationsEnabled` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/TranscriptView.tsx:339 — The view draws `Listening...` under `! isStopping && isRecording && ! isPaused && ! isProcessing && transcripts . length > 0`, but `isPaused` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:206 — The view draws `Loading preview...` under `isLoadingPreview`, but `isLoadingPreview` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:281 — The view draws `Deleting...` under `isDeleting`, but `isDeleting` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/TranscriptRecovery/TranscriptRecovery.tsx:297 — The view draws `Recovering...` under `isRecovering`, but `isRecovering` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/Sidebar/index.tsx:605 — The view draws `Searching...` under `searchQuery && item . id === 'meetings' && isSearching`, but `isSearching` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/Sidebar/index.tsx:752 — The view draws `Searching...` under `searchQuery && item . id === 'meetings' && isSearching`, but `isSearching` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/Sidebar/index.tsx:785 — The view draws `Recording in progress...` under `isRecording`, but `isRecording` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state frontend/src/components/DatabaseImport/HomebrewDatabaseDetector.tsx:126 — The view draws `Importing...` under `isImporting`, but `isImporting` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
X7 · Silent fallback defaults · Silent fallback default on Err · ×3
  • Silent fallback default on Err frontend/src-tauri/src/audio/recording_saver.rs:463 — `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:373 — `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.
  • Silent fallback default on Err frontend/src-tauri/src/utils.rs:65 — `url_origin_for_log` turns every `Err` into `"<invalid-url>".to_string()` — 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 · Off-boarding risk · ×2
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 33 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 (+25 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 8 significant file(s) lose their only recent owner: backend/app/db.py, REDACTED, frontend/src-tauri/src/audio/ffmpeg_mixer.rs, frontend/src-tauri/src/audio/capture/core_audio.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/notifications/system.rs. Pair on, review, or document these before any departure.
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 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 (43 single-owned of 222 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; 222 of the 326 production source files in this repository met that bar). They are anonymized user #3 (1 file(s)), anonymized user #4 (1 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/components/DatabaseImport/HomebrewDatabaseDetector.tsx, frontend/src-tauri/src/audio/devices/configuration.rs.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found llama-helper/src/main.rs:1 — 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/`. ADRs are expected here because `llama-helper/src/main.rs` makes this repository a deployable product (line 1).
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` (46800 LoC, 336 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 1 of 222 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; 222 of the 326 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/components/SummaryLanguageSettings.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.
D34 · Knowledge Freshness · Orphaned file · ×1
  • Orphaned file frontend/src/components/SummaryLanguageSettings.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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • 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.
P2 · Observability · Logging is not universal · ×1
  • 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`.
P3 · Security & performance tooling · No SAST · ×1
  • 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 8 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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation frontend/package.json:30 — `frontend/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
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 'labelForId' · ×1
  • Unused export 'labelForId' frontend/src/lib/audioDevices.ts:42 — Nothing imports this binding — it is safe to review for removal.
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.
R7 · Dead Code · Unused export 'getModelIcon' · ×1
  • 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.
R7 · Dead Code · Unused export 'AUTO_VALUE' · ×1
  • Unused export 'AUTO_VALUE' frontend/src/lib/summary-languages.ts:44 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'WhisperEngineState' · ×1
  • Unused export 'WhisperEngineState' frontend/src/lib/whisper.ts:32 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'DownloadModelRequest' · ×1
  • Unused export 'DownloadModelRequest' frontend/src/lib/whisper.ts:40 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'SwitchModelRequest' · ×1
  • Unused export 'SwitchModelRequest' frontend/src/lib/whisper.ts:44 — Nothing imports this binding — it is safe to review for removal.
X5 · Nullable reference types · Null assertions (`!`) override strict null checking · ×1
  • Null assertions (`!`) override strict null checking — ~0.5 `!` null assertions per 1k TypeScript source lines — 15 assertion(s) across the 31423 source line(s) of the 173 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. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • 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.
Minor — 35 finding(s)
D12 · Dependency Hygiene · Outdated · ×34
  • 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: ebur128 — `ebur128` is locked at 0.1.10 but 0.1.11 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 ebur128` and commit the updated REDACTED.
  • Outdated: encoding_rs — `encoding_rs` is locked at 0.8.35 but 0.8.44 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: 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.35 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: open — `open` is locked at 5.3.3 but 5.4.5 is the current stable release on crates.io, and it already satisfies the `"5.3.3"` requirement declared in frontend/src-tauri/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p open` and commit the updated REDACTED.
  • Outdated: realfft — `realfft` is locked at 3.5.0 but 3.5.1 is the current stable release on crates.io, and it already satisfies the `"3.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 realfft` 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.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-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.2 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.
  • + 9 more in this group — see findings.md.
D24 · Comment Value · doc comments repeat the names · ×1
  • doc comments repeat the names frontend/src/components/VirtualizedTranscriptView.tsx:22 — 1 of 41 documented parameters and 4 of 116 summaries in `meetily` only repeat the member or parameter name (e.g. "Whether stopping" for `isStopping`). Delete the restating tags, or add what the name does not say.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8bc8dea606ad426eb2df8ad8440986ca/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8bc8dea606ad426eb2df8ad8440986ca/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .143artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .77artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .18artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—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.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1d882-fa7c-728e-bf50-88ff3c98687c · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md