Public report of naudio/NAudio, published 23 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 23 October 2026, 12:22 UTC · Survey ID cd_702040a519fc4484a117dc8a5eeb706c
naudio/NAudio
Measured 23 October 2026, 12:14 UTC, at code version 54cb818
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Code coverage is not measured: No coverage collector is wired up.
Test reliability is not measured: No test run produced results.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 3 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 117,239 lines of product code in 31 projects, tests not counted · Estimated rebuild effort: about 2.1 person-years · Weakest lens: Code Health, 54
Findings by how serious they are
122 critical633 serious152 minor
2 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 12:14 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
70of 74 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
873of 907 findings point to an exact file and line, so you can open each one in the code. The other 34 concern the repository as a whole, such as missing documentation.
74dimensions across 6 lenses, read from 117,239 lines of product code in 31 projects.
naudio/NAudio scores 60 out of 100 and is rated Adequate, while five of its six lenses score higher still: Architecture at 95, rated Exemplary, Performance at 75, rated Strong, and Security and Compliance at 65 and Maturity and Production Readiness at 62, all rated Adequate.
The score is lower than those five because the weakest lens counts most, and here that is Code Health, which scores 54 and is rated Adequate. Its Async correctness dimension scores 3.9 out of 10, and until that reaches 4, Code Health can't be rated higher than Adequate. The first actions are to resolve the 7 AnalyzerSeverityNone finding(s) in Explicit Debt and to resolve the 9 WriteOnlyPrivateField finding(s) in Explicit Debt, and if Code Health rose to 70, the score would rise from 60 to about 64.
122 findings are critical: 103 in Explicit Debt, 12 in Static Analysis (SAST), two in Secrets (history), two in Test Quality, one in Data Compliance (PII/GDPR), one in Project dependency cycles and one in Secret Scanning.
Watchdog couldn't measure Runtime evidence locked — no reproducible boot in this code, so that dimension is left out of the score. The product code is 117,239 lines, which would take an estimated 2.1 person-years, around €300,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Code Health rose from 54 to 70, the lowest score rated Strong, the score would rise from 60 to about 64.
Code composition: what the lines of code are
Business logic 27%Supporting code 36%Tests 33%Generated by tools 5%
New since the last survey: 171 findings
These 171 critical or serious findings weren't in the previous survey, on 9 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Explicit Debt · Dead code: NotAutomatable samples/NAudioConsoleTest/Shared/Testing/TestResult.cs
Explicit Debt · Dead code: cBias src/NAudio.Core/Codecs/ALawEncoder.cs
Explicit Debt · Dead code: BandPassFilterConstantSkirtGain src/NAudio.Core/Dsp/BiQuadFilter.cs
Explicit Debt · Dead code: ComplexInverse src/NAudio.Core/Dsp/FftProcessor.cs
Explicit Debt · Dead code: IsEntirelyNull src/NAudio.Core/Utils/ByteArrayExtensions.cs
Explicit Debt · Dead code: MAKE_HRESULT src/NAudio.Core/Utils/HResult.cs
Explicit Debt · Dead code: GetPositionTimeSpan src/NAudio.Core/Utils/WavePositionExtensions.cs
Explicit Debt · Dead code: RemoveMixerInput src/NAudio.Core/Wave/SampleProviders/MixingSampleProvider.cs
Explicit Debt · Dead code: RemoveAllMixerInputs src/NAudio.Core/Wave/SampleProviders/MixingSampleProvider.cs
Explicit Debt · Dead code: NotifyingSampleProvider src/NAudio.Core/Wave/SampleProviders/NotifyingSampleProvider.cs
Explicit Debt · Dead code: PanningSampleProvider src/NAudio.Core/Wave/SampleProviders/PanningSampleProvider.cs
Explicit Debt · Dead code: StereoBalanceStrategy src/NAudio.Core/Wave/SampleProviders/PanningSampleProvider.cs
Explicit Debt · Dead code: SquareRootPanStrategy src/NAudio.Core/Wave/SampleProviders/PanningSampleProvider.cs
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 46 findings
These 46 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one.
€98,000 to €500,000, for 1,640 to 5,311 hours of work, about 2.1 person-years for 1 to 4 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 117,239 lines of product code
Comment lines
The estimate prices 85,744 lines. Comment lines count towards the size of 117,239 lines but aren't priced as work.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 7 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .globalconfig (7).
Raises the score by about 5 points · Low effort · Explicit Debt
2
Resolve the 9 WriteOnlyPrivateField finding(s) in Explicit Debt — start with XingHeader.cs (3), Vst3Plugin.cs (3), AsioDriverExt.cs (2).
Raises the score by about 5 points · Low effort · Explicit Debt
3
Resolve the 78 EmptyCatchBlock finding(s) in Explicit Debt — start with Vst3Plugin.cs (5), DiagnosticsCollector.cs (4), MixingCapturePanel.cs (4).
Raises the score by about 5 points · Medium effort · Explicit Debt
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 €300,000 to build again, about 2.1 person-years of work. Its weakest lens is Code Health, at 54 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 7 AnalyzerSeverityNone finding(s) in Explicit Debt. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 7 Explicit Debt findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
41 modules, with 74 dependencies between them. One loop runs through 16 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 1 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.
NAudio.CoreAudioApi.Interfaces uses NAudio.CoreAudioApi, so a change to NAudio.CoreAudioApi can break NAudio.CoreAudioApi.Interfaces, while a change to NAudio.CoreAudioApi.Interfaces can't break NAudio.CoreAudioApi.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
NAudio.Dmo uses NAudio.Dmo.Interfaces, so a change to NAudio.Dmo.Interfaces can break NAudio.Dmo, while a change to NAudio.Dmo can't break NAudio.Dmo.Interfaces.
Position
Below the diagonal: NAudio.Dmo uses a module listed above it, which is the healthy direction.
NAudio.MacOS.CoreAudio uses NAudio.MacOS.CoreAudioTypes, so a change to NAudio.MacOS.CoreAudioTypes can break NAudio.MacOS.CoreAudio, while a change to NAudio.MacOS.CoreAudio can't break NAudio.MacOS.CoreAudioTypes.
Position
Below the diagonal: NAudio.MacOS.CoreAudio uses a module listed above it, which is the healthy direction.
15→24 NAudio.MacOS.CoreAudio uses NAudio.MacOS.CoreAudio.Interoppart of a loop✕
Connections
17 pairs of types, where a type in NAudio.MacOS.CoreAudio uses a type in NAudio.MacOS.CoreAudio.Interop.
NAudio.MacOS.CoreAudio uses NAudio.MacOS.CoreAudio.Interop, so a change to NAudio.MacOS.CoreAudio.Interop can break NAudio.MacOS.CoreAudio, while a change to NAudio.MacOS.CoreAudio can't break NAudio.MacOS.CoreAudio.Interop.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→26 NAudio.MacOS.CoreAudio uses NAudio.MacOSpart of a loop✕
Connections
2 pairs of types, where a type in NAudio.MacOS.CoreAudio uses a type in NAudio.MacOS.
NAudio.MacOS.CoreAudio uses NAudio.MacOS, so a change to NAudio.MacOS can break NAudio.MacOS.CoreAudio, while a change to NAudio.MacOS.CoreAudio can't break NAudio.MacOS.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→30 NAudio.MacOS.CoreAudio uses NAudio.Wavepart of a loop✕
Connections
3 pairs of types, where a type in NAudio.MacOS.CoreAudio uses a type in NAudio.Wave.
NAudio.MacOS.CoreAudio uses NAudio.Wave, so a change to NAudio.Wave can break NAudio.MacOS.CoreAudio, while a change to NAudio.MacOS.CoreAudio can't break NAudio.Wave.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→25 NAudio.MediaFoundation.Interfaces uses NAudio.MediaFoundationpart of a loop✕
Connections
2 pairs of types, where a type in NAudio.MediaFoundation.Interfaces uses a type in NAudio.MediaFoundation.
NAudio.MediaFoundation.Interfaces uses NAudio.MediaFoundation, so a change to NAudio.MediaFoundation can break NAudio.MediaFoundation.Interfaces, while a change to NAudio.MediaFoundation.Interfaces can't break NAudio.MediaFoundation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
NAudio.Utils uses NAudio.MacOS.CoreAudioTypes, so a change to NAudio.MacOS.CoreAudioTypes can break NAudio.Utils, while a change to NAudio.Utils can't break NAudio.MacOS.CoreAudioTypes.
Position
Below the diagonal: NAudio.Utils uses a module listed above it, which is the healthy direction.
18→30 NAudio.Utils uses NAudio.Wavepart of a loop✕
Connections
5 pairs of types, where a type in NAudio.Utils uses a type in NAudio.Wave.
NAudio.Vst3.Hosting uses NAudio.Vst3.Interop, so a change to NAudio.Vst3.Interop can break NAudio.Vst3.Hosting, while a change to NAudio.Vst3.Hosting can't break NAudio.Vst3.Interop.
Position
Below the diagonal: NAudio.Vst3.Hosting uses a module listed above it, which is the healthy direction.
20→30 NAudio.Wave.Asio uses NAudio.Wavepart of a loop✕
Connections
2 pairs of types, where a type in NAudio.Wave.Asio uses a type in NAudio.Wave.
NAudio.Wave.Compression uses NAudio, so a change to NAudio can break NAudio.Wave.Compression, while a change to NAudio.Wave.Compression can't break NAudio.
Position
Below the diagonal: NAudio.Wave.Compression uses a module listed above it, which is the healthy direction.
21→30 NAudio.Wave.Compression uses NAudio.Wavepart of a loop✕
Connections
7 pairs of types, where a type in NAudio.Wave.Compression uses a type in NAudio.Wave.
NAudio.Wave.Compression uses NAudio.Wave, so a change to NAudio.Wave can break NAudio.Wave.Compression, while a change to NAudio.Wave.Compression can't break NAudio.Wave.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
NAudio.Wave.SampleProviders uses NAudio.Dsp, so a change to NAudio.Dsp can break NAudio.Wave.SampleProviders, while a change to NAudio.Wave.SampleProviders can't break NAudio.Dsp.
Position
Below the diagonal: NAudio.Wave.SampleProviders uses a module listed above it, which is the healthy direction.
22→30 NAudio.Wave.SampleProviders uses NAudio.Wavepart of a loop✕
Connections
79 pairs of types, where a type in NAudio.Wave.SampleProviders uses a type in NAudio.Wave. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
NAudio.Wave.SampleProviders uses NAudio.Wave, so a change to NAudio.Wave can break NAudio.Wave.SampleProviders, while a change to NAudio.Wave.SampleProviders can't break NAudio.Wave.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
NAudio.MacOS.CoreAudio.Interop uses NAudio.MacOS.CoreAudioTypes, so a change to NAudio.MacOS.CoreAudioTypes can break NAudio.MacOS.CoreAudio.Interop, while a change to NAudio.MacOS.CoreAudio.Interop can't break NAudio.MacOS.CoreAudioTypes.
Position
Below the diagonal: NAudio.MacOS.CoreAudio.Interop uses a module listed above it, which is the healthy direction.
NAudio.MacOS.CoreAudio.Interop uses NAudio.MacOS.CoreAudio, so a change to NAudio.MacOS.CoreAudio can break NAudio.MacOS.CoreAudio.Interop, while a change to NAudio.MacOS.CoreAudio.Interop can't break NAudio.MacOS.CoreAudio.
Position
Below the diagonal: NAudio.MacOS.CoreAudio.Interop uses a module listed above it, which is the healthy direction.
24→26 NAudio.MacOS.CoreAudio.Interop uses NAudio.MacOSpart of a loop✕
Connections
1 pair of types, where a type in NAudio.MacOS.CoreAudio.Interop uses a type in NAudio.MacOS.
NAudio.MacOS.CoreAudio.Interop uses NAudio.MacOS, so a change to NAudio.MacOS can break NAudio.MacOS.CoreAudio.Interop, while a change to NAudio.MacOS.CoreAudio.Interop can't break NAudio.MacOS.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
NAudio.MediaFoundation uses NAudio.MediaFoundation.Interfaces, so a change to NAudio.MediaFoundation.Interfaces can break NAudio.MediaFoundation, while a change to NAudio.MediaFoundation can't break NAudio.MediaFoundation.Interfaces.
Position
Below the diagonal: NAudio.MediaFoundation uses a module listed above it, which is the healthy direction.
25→30 NAudio.MediaFoundation uses NAudio.Wavepart of a loop✕
Connections
4 pairs of types, where a type in NAudio.MediaFoundation uses a type in NAudio.Wave.
NAudio.MediaFoundation uses NAudio.Wave, so a change to NAudio.Wave can break NAudio.MediaFoundation, while a change to NAudio.MediaFoundation can't break NAudio.Wave.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
NAudio.MacOS uses NAudio.MacOS.CoreAudio.Interop, so a change to NAudio.MacOS.CoreAudio.Interop can break NAudio.MacOS, while a change to NAudio.MacOS can't break NAudio.MacOS.CoreAudio.Interop.
Position
Below the diagonal: NAudio.MacOS uses a module listed above it, which is the healthy direction.
26→30 NAudio.MacOS uses NAudio.Wavepart of a loop✕
Connections
1 pair of types, where a type in NAudio.MacOS uses a type in NAudio.Wave.
NAudio.MacOS.AudioToolbox.Interop uses NAudio.MacOS.CoreAudioTypes, so a change to NAudio.MacOS.CoreAudioTypes can break NAudio.MacOS.AudioToolbox.Interop, while a change to NAudio.MacOS.AudioToolbox.Interop can't break NAudio.MacOS.CoreAudioTypes.
Position
Below the diagonal: NAudio.MacOS.AudioToolbox.Interop uses a module listed above it, which is the healthy direction.
NAudio.MacOS.AudioToolbox.Interop uses NAudio.MacOS, so a change to NAudio.MacOS can break NAudio.MacOS.AudioToolbox.Interop, while a change to NAudio.MacOS.AudioToolbox.Interop can't break NAudio.MacOS.
Position
Below the diagonal: NAudio.MacOS.AudioToolbox.Interop uses a module listed above it, which is the healthy direction.
NAudio.MacOS.CoreFoundationApi uses NAudio.MacOS, so a change to NAudio.MacOS can break NAudio.MacOS.CoreFoundationApi, while a change to NAudio.MacOS.CoreFoundationApi can't break NAudio.MacOS.
Position
Below the diagonal: NAudio.MacOS.CoreFoundationApi uses a module listed above it, which is the healthy direction.
NAudio.MacOS.AudioToolbox uses NAudio.MacOS.CoreAudioTypes, so a change to NAudio.MacOS.CoreAudioTypes can break NAudio.MacOS.AudioToolbox, while a change to NAudio.MacOS.AudioToolbox can't break NAudio.MacOS.CoreAudioTypes.
Position
Below the diagonal: NAudio.MacOS.AudioToolbox uses a module listed above it, which is the healthy direction.
NAudio.MacOS.AudioToolbox uses NAudio.MacOS, so a change to NAudio.MacOS can break NAudio.MacOS.AudioToolbox, while a change to NAudio.MacOS.AudioToolbox can't break NAudio.MacOS.
Position
Below the diagonal: NAudio.MacOS.AudioToolbox uses a module listed above it, which is the healthy direction.
NAudio.MacOS.AudioToolbox uses NAudio.MacOS.AudioToolbox.Interop, so a change to NAudio.MacOS.AudioToolbox.Interop can break NAudio.MacOS.AudioToolbox, while a change to NAudio.MacOS.AudioToolbox can't break NAudio.MacOS.AudioToolbox.Interop.
Position
Below the diagonal: NAudio.MacOS.AudioToolbox uses a module listed above it, which is the healthy direction.
29→30 NAudio.MacOS.AudioToolbox uses NAudio.Wavepart of a loop✕
Connections
6 pairs of types, where a type in NAudio.MacOS.AudioToolbox uses a type in NAudio.Wave.
NAudio.MacOS.AudioToolbox uses NAudio.Wave, so a change to NAudio.Wave can break NAudio.MacOS.AudioToolbox, while a change to NAudio.MacOS.AudioToolbox can't break NAudio.Wave.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
NAudio.Wave uses NAudio.MacOS.CoreAudioTypes, so a change to NAudio.MacOS.CoreAudioTypes can break NAudio.Wave, while a change to NAudio.Wave can't break NAudio.MacOS.CoreAudioTypes.
Position
Below the diagonal: NAudio.Wave uses a module listed above it, which is the healthy direction.
NAudio.Wave uses NAudio.Wave.DirectSoundInterop, so a change to NAudio.Wave.DirectSoundInterop can break NAudio.Wave, while a change to NAudio.Wave can't break NAudio.Wave.DirectSoundInterop.
Position
Below the diagonal: NAudio.Wave uses a module listed above it, which is the healthy direction.
NAudio.Wave uses NAudio.MacOS.CoreAudio, so a change to NAudio.MacOS.CoreAudio can break NAudio.Wave, while a change to NAudio.Wave can't break NAudio.MacOS.CoreAudio.
Position
Below the diagonal: NAudio.Wave uses a module listed above it, which is the healthy direction.
NAudio.Wave uses NAudio.MediaFoundation.Interfaces, so a change to NAudio.MediaFoundation.Interfaces can break NAudio.Wave, while a change to NAudio.Wave can't break NAudio.MediaFoundation.Interfaces.
Position
Below the diagonal: NAudio.Wave uses a module listed above it, which is the healthy direction.
NAudio.Wave uses NAudio.Wave.Compression, so a change to NAudio.Wave.Compression can break NAudio.Wave, while a change to NAudio.Wave can't break NAudio.Wave.Compression.
Position
Below the diagonal: NAudio.Wave uses a module listed above it, which is the healthy direction.
NAudio.Wave uses NAudio.Wave.SampleProviders, so a change to NAudio.Wave.SampleProviders can break NAudio.Wave, while a change to NAudio.Wave can't break NAudio.Wave.SampleProviders.
Position
Below the diagonal: NAudio.Wave uses a module listed above it, which is the healthy direction.
NAudio.Wave uses NAudio.Dmo.Effect, so a change to NAudio.Dmo.Effect can break NAudio.Wave, while a change to NAudio.Wave can't break NAudio.Dmo.Effect.
Position
Below the diagonal: NAudio.Wave uses a module listed above it, which is the healthy direction.
NAudio.Wave uses NAudio.MediaFoundation, so a change to NAudio.MediaFoundation can break NAudio.Wave, while a change to NAudio.Wave can't break NAudio.MediaFoundation.
Position
Below the diagonal: NAudio.Wave uses a module listed above it, which is the healthy direction.
NAudio.Wave uses NAudio.MacOS.AudioToolbox, so a change to NAudio.MacOS.AudioToolbox can break NAudio.Wave, while a change to NAudio.Wave can't break NAudio.MacOS.AudioToolbox.
Position
Below the diagonal: NAudio.Wave uses a module listed above it, which is the healthy direction.
30→31 NAudio.Wave uses NAudio.CoreAudioApipart of a loop✕
Connections
33 pairs of types, where a type in NAudio.Wave uses a type in NAudio.CoreAudioApi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
NAudio.Wave uses NAudio.CoreAudioApi, so a change to NAudio.CoreAudioApi can break NAudio.Wave, while a change to NAudio.Wave can't break NAudio.CoreAudioApi.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
52 pairs of types, where a type in NAudio.CoreAudioApi uses a type in NAudio.CoreAudioApi.Interfaces. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
NAudio.CoreAudioApi uses NAudio.CoreAudioApi.Interfaces, so a change to NAudio.CoreAudioApi.Interfaces can break NAudio.CoreAudioApi, while a change to NAudio.CoreAudioApi can't break NAudio.CoreAudioApi.Interfaces.
Position
Below the diagonal: NAudio.CoreAudioApi uses a module listed above it, which is the healthy direction.
NAudio.CoreAudioApi uses NAudio.Wave, so a change to NAudio.Wave can break NAudio.CoreAudioApi, while a change to NAudio.CoreAudioApi can't break NAudio.Wave.
Position
Below the diagonal: NAudio.CoreAudioApi uses a module listed above it, which is the healthy direction.
38 pairs of types, where a type in NAudio.Effects uses a type in NAudio.Dsp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
33 pairs of types, where a type in NAudio.Effects uses a type in NAudio.Wave. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
NAudio.Extras uses NAudio.Wave.SampleProviders, so a change to NAudio.Wave.SampleProviders can break NAudio.Extras, while a change to NAudio.Extras can't break NAudio.Wave.SampleProviders.
Position
Below the diagonal: NAudio.Extras uses a module listed above it, which is the healthy direction.
NAudio.Sequencing uses NAudio.Wave.SampleProviders, so a change to NAudio.Wave.SampleProviders can break NAudio.Sequencing, while a change to NAudio.Sequencing can't break NAudio.Wave.SampleProviders.
Position
Below the diagonal: NAudio.Sequencing uses a module listed above it, which is the healthy direction.
NAudio.Sequencing uses NAudio.Wave, so a change to NAudio.Wave can break NAudio.Sequencing, while a change to NAudio.Sequencing can't break NAudio.Wave.
Position
Below the diagonal: NAudio.Sequencing uses a module listed above it, which is the healthy direction.
NAudio.Wave.Alsa uses NAudio.Wave.SampleProviders, so a change to NAudio.Wave.SampleProviders can break NAudio.Wave.Alsa, while a change to NAudio.Wave.Alsa can't break NAudio.Wave.SampleProviders.
Position
Below the diagonal: NAudio.Wave.Alsa uses a module listed above it, which is the healthy direction.
NAudio.Midi uses NAudio.Sequencing, so a change to NAudio.Sequencing can break NAudio.Midi, while a change to NAudio.Midi can't break NAudio.Sequencing.
Position
Below the diagonal: NAudio.Midi uses a module listed above it, which is the healthy direction.
NAudio.Sampler uses NAudio.SoundFont, so a change to NAudio.SoundFont can break NAudio.Sampler, while a change to NAudio.Sampler can't break NAudio.SoundFont.
Position
Below the diagonal: NAudio.Sampler uses a module listed above it, which is the healthy direction.
NAudio.Sampler uses NAudio.Effects, so a change to NAudio.Effects can break NAudio.Sampler, while a change to NAudio.Sampler can't break NAudio.Effects.
Position
Below the diagonal: NAudio.Sampler uses a module listed above it, which is the healthy direction.
NAudio.Vst3 uses NAudio.Vst3.Interop, so a change to NAudio.Vst3.Interop can break NAudio.Vst3, while a change to NAudio.Vst3 can't break NAudio.Vst3.Interop.
Position
Below the diagonal: NAudio.Vst3 uses a module listed above it, which is the healthy direction.
NAudio.Vst3 uses NAudio.Vst3.Hosting, so a change to NAudio.Vst3.Hosting can break NAudio.Vst3, while a change to NAudio.Vst3 can't break NAudio.Vst3.Hosting.
Position
Below the diagonal: NAudio.Vst3 uses a module listed above it, which is the healthy direction.
NAudio.Vst3 uses NAudio.Sequencing, so a change to NAudio.Sequencing can break NAudio.Vst3, while a change to NAudio.Vst3 can't break NAudio.Sequencing.
Position
Below the diagonal: NAudio.Vst3 uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
19
High / Critical
A03:2025 — Software Supply Chain Failures
7
Medium
A07:2025 — Authentication Failures
4
High / Critical
A01:2025 — Broken Access Control
1
High / Critical
Roadmap
Begin by resolving explicit code debt, starting with the global configuration file to address severity issues, followed by fixing empty catch blocks in key plugin and diagnostic files, and finally correcting write-only private fields in header and driver extensions. Next, eliminate the risk of deadlocks by addressing synchronous calls made within asynchronous contexts. Finally, ensure robust cancellation handling by threading cancellation tokens through all asynchronous methods to allow work to stop promptly when requested.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 7 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .globalconfig (7).
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 — 122
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 — 633
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 — 152
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 2
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 70 of 74 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 74 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 873 of 907 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (103 contributor(s) across 1531 commit(s) sampled, automation and bot accounts excluded). One of them holds 84% of the history; the other 102 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (116,945 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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"]`.
D32 Data Compliance (PII/GDPR) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `src/NAudio.Alsa/AlsaOut.cs`, `src/NAudio.MacOS/GlobalUsings.cs`, `src/NAudio.Vst3/Vst3Plugin.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (samples/NAudioWpfDemo/SpectrumAnalyser.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 17 further occurrence(s) are not listed individually; the score already reflects all 57.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X18 Disposal-pattern correctness — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 42 further occurrence(s) are not listed individually; the score already reflects all 82.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
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.
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.
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.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
54 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MacUtils.ConstructSpeakersValue at 99. A further 12 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 MediaFoundationException.GetMessageForHResult at 37 — they are counted neither in the figure above nor in this dimension's score. 10 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/NAudio.Wasapi/MediaFoundation/MediaFoundationException.cs (MediaFoundationException.GetMessageForHResult at 37), src/NAudio.Wasapi/CoreAudioApi/CoreAudioException.cs (CoreAudioException.GetMessageForHResult at 32), src/NAudio.Core/FileFormats/SoundFont/SoundFontInstrumentResolver.cs (SoundFontInstrumentResolver.IsAllowedAtPresetLevel at 27), src/NAudio.Core/FileFormats/SoundFont/PresetsChunk.cs (PresetsChunk.PresetsChunk.ctor at 21), src/NAudio.WinMM/Mixer/MixerLine.cs (MixerLine.TypeDescription.get at 21), and 5 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 49 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with MacUtils.ConstructSpeakersValue (cyclomatic 99). — Refactoring it lifts Cyclomatic Complexity from 6.0 to about 6.5/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 113 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with WdlResampler.ResampleOut (cognitive 132), MidiConverter.ConvertMidi (cognitive 113), DahdsrEnvelope.Advance (cognitive 95). — 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 6 together lifts Cognitive Complexity from 5.7 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.4 / 10Stronggated by 17 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 7 TooManyMethods finding(s) in God Classes — start with Vst3Plugin.cs, MFByteStreamFromStream.cs, AsioDevice.cs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 MethodTooLong finding(s) in God Classes — start with MacUtils.ChannelTranslations.cs, WdlResampler.cs, Vst3Plugin.cs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 ClassTooLong finding(s) in God Classes — start with MacUtils.cs, SamplerVoice.cs, WasapiPlayer.cs. — One of this dimension's main actionable groups (3 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
80 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 19 of the 82 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 32 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with OfflineMidiRenderer.cs, InstrumentBuilder.cs, Pcm24BitToSampleProvider.cs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 7 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with IPluginFactory.cs, SfzMappedRegion.cs, AsioDriverExt.cs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 7 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with WasapiOut.cs (2), Vst3InstrumentSampleProvider.cs, MediaFoundationEncoder.cs. — One of this dimension's main actionable groups (7 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.5 / 10Stronggated by 2 serious findings✓ 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.
Off the main sequence: NAudio.Core · ×2src/NAudio.Core/NAudio.Core.csproj:1
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling — start with NAudio.Core.csproj, NAudio.Midi.csproj. — One of this dimension's main actionable groups (2 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with SamplerRegion.cs, AsioRecordingPanel.cs, AudioFileInspectorForm.cs. — One of this dimension's main actionable groups (3 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
2018 test methods: 2018 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.7 / 10Adequategated by 2 critical findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 Assertions commented out finding(s) in Test Quality — start with ResamplerDmoTests.cs, MixerApiTests.cs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 31 No assertions finding(s) in Test Quality — start with CanEnumerateDevices.cs (4), ResamplerDmoStreamTests.cs (4), MMDeviceEnumeratorTests.cs (4). — One of this dimension's main actionable groups (31 warning-level).
Resolve the 3 Test cannot fail finding(s) in Test Quality — start with WaveFileChunkReaderTests.cs (2), CueListInterpreterTests.cs. — One of this dimension's main actionable groups (3 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 156 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 10 direct `PackageReference`(s), and 124 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
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.
Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with WdlResampler.cs, MidiFile.cs, WaveFileChunkReader.cs. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 78 EmptyCatchBlock finding(s) in Explicit Debt — start with Vst3Plugin.cs (5), DiagnosticsCollector.cs (4), MixingCapturePanel.cs (4). — One of this dimension's main actionable groups (78 issue-level).
Resolve the 9 WriteOnlyPrivateField finding(s) in Explicit Debt — start with XingHeader.cs (3), Vst3Plugin.cs (3), AsioDriverExt.cs (2). — One of this dimension's main actionable groups (9 issue-level).
Resolve the 7 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .globalconfig (7). — One of this dimension's main actionable groups (7 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
31 projects, 1407 source files, 161953 hand-written lines of code (116945 production / 45008 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 6840 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 85 inter-project edges.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
This project is exceptionally well documented: 21 README files plus 65 architecture/Docs markdown files cover the codebase (XML-doc coverage ranges from 2% for [NAudio.Midi(net9.0)] to 100% for [NAudio.Midi(net9.0)], with most in the middle band), and each document is clearly scoped, well-structured, and navigable — a full outline appears under every heading (e.g. ASIO Channel Mapping; The mental model; Discovering the device; Common patterns; Stereo to the first two outputs; ...). (21 of 25 sampled documents could not be assessed: 2 of 3 evaluation groups failed.)
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
1 naming inconsistencies across 200 sampled symbols.
Inconsistent test naming convention for the same test class `WaveOffsetStreamTests`. One test uses a descriptive sentence format (`ChangingSourceLengthUpdatesLength`), while another uses a technical assertion format with underscores (`WaveOffsetStream_SpanAndByteArrayRead_Agree`).
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
2 of 30 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability4.5 / 10Weak✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
87 % of calls cross a namespace and 1 % go through an interface, but 60 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.
Resolve the 2 Pass-through layer finding(s) in Navigability — start with IgnoreDisposeStream.cs, MMDeviceNotificationClient.cs. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
19 finding(s): 0 critical, 12 high, 5 medium, 2 low. 10 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 15 file(s) — `Docs/toc.yml`, `samples/NAudioConsoleTest/Asio/Tests/AsioDisposeFromStoppedHandlerTest.cs` (line 23), `samples/NAudioConsoleTest/Asio/Tests/AsioShowCapabilitiesTest.cs` (line 15), `samples/NAudioConsoleTest/Asio/Tests/AsioStopFromCallbackGuardTest.cs` (line 22), `samples/NAudioConsoleTest/MediaFoundation/Tests/MediaFoundationReadAudioFileTest.cs` (line 21), … (+10 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 1 of those file(s) — `src/NAudio.Vst3/Vst3Plugin.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 2 of those file(s) — `src/NAudio.Alsa/AlsaOut.cs`, `src/NAudio.MacOS/GlobalUsings.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 2 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
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
No known-vulnerable dependencies in any ecosystem this repository declares.
✓ On the Gold path — maintain.
Detailed fixes: d30_recommendation.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)7.1 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. semgrep could not parse 3 file(s) — `src/NAudio.Alsa/AlsaOut.cs`, `src/NAudio.MacOS/GlobalUsings.cs`, `src/NAudio.Vst3/Vst3Plugin.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 395 of the 716 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D39 · IL Efficiency9.8 / 10Exemplary✓ Tool-verified
Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 30 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with NAudioAsioFakeDriverTest.csproj. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
The namespaces NAudio.CoreAudioApi ↔ NAudio.CoreAudioApi.Interfaces ↔ NAudio.Dmo ↔ NAudio.Dmo.Effect ↔ NAudio.MacOS ↔ NAudio.MacOS.AudioToolbox ↔ NAudio.MacOS.AudioToolbox.Interop ↔ NAudio.MacOS.CoreAudio ↔ NAudio.MacOS.CoreAudio.Interop ↔ NAudio.MediaFoundation ↔ NAudio.MediaFoundation.Interfaces ↔ NAudio.Utils ↔ NAudio.Wave ↔ NAudio.Wave.Asio ↔ NAudio.Wave.Compression ↔ NAudio.Wave.SampleProviders depend on each other. The lightest dependency in the cycle is NAudio.MacOS → NAudio.MacOS.CoreAudio.Interop (NAudio.MacOS.RangedWaveFormat → NAudio.MacOS.CoreAudio.Interop.AudioStreamRangedDescription, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/NAudio.MacOS/MacOS/RangedWaveFormat.cs:7
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by imperative guard methods that throw on violation) — this is NOT a claim that the code is unprotected. What's missing is a NAMED rule set: the guards encode the access rules inline, so the rules can't be listed, reviewed or tested apart from the call sites that apply them. Recommendation, not a defect.
What to do
Name the access rules — give each one a named predicate/policy object your guards consult, so the rule set can be reviewed and unit-tested independently of the call sites that enforce it.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`DummyEventHandler` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/NAudio.MacOS/MacOS/CoreAudio/PropertyListenerHandle.cs:77
`Callback` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/NAudio.WinMM/Midi/MidiOut.cs:144
The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — src/NAudio.WinMM/Mixer/MixerControl.cs:169
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×30) — src/NAudio.Asio/AsioAudioAvailableEventArgs.cs:92, src/NAudio.Core/Dsp/SmbPitchShifter.cs:239, src/NAudio.Core/Dsp/WdlResampler.cs:82, …
4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). (×2) — src/NAudio.Core/Wave/WaveOutputs/WaveBuffer.cs:71, src/NAudio.Wasapi/WasapiOut.cs:255
13 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/NAudio.MacOS/MacOS/CoreFoundationApi/AbstractCoreFoundationObject.cs:107
20 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/NAudio.MacOS/MacOS/CoreFoundationApi/AbstractCoreFoundationObject.cs:124
7 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:183
47 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/NAudio.Wasapi/CoreAudioApi/PropVariant.cs:132
5 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/NAudio.WinForms/Gui/Fader.cs:64
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
882 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 13 of 30 project(s) that lack one — worth up to 0.9 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Docs/CrossPlatformAudioFilesWithSoundFile.md installs the package `NAudio.SoundFile` (`dotnet add package NAudio.SoundFile`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/CrossPlatformAudioFilesWithSoundFile.md:12
Docs/PlayAudioFileLinuxAlsa.md installs the package `NAudio.Alsa` (`dotnet add package NAudio.Alsa`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/PlayAudioFileLinuxAlsa.md:9
Docs/PlayAudioFileMacOS.md installs the package `NAudio.MacOS` (`dotnet add package NAudio.MacOS --prerelease`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/PlayAudioFileMacOS.md:10
Docs/RecordAudioFileLinuxAlsa.md installs the package `NAudio.Alsa` (`dotnet add package NAudio.Alsa`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/RecordAudioFileLinuxAlsa.md:8
Docs/RecordAudioFileMacOS.md installs the package `NAudio.MacOS` (`dotnet add package NAudio.MacOS --prerelease`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/RecordAudioFileMacOS.md:8
Docs/ValidatingAlsaOnLinux.md runs `dotnet build NAudio.Alsa/NAudio.Alsa.csproj -c Release`, but `NAudio.Alsa/NAudio.Alsa.csproj` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/ValidatingAlsaOnLinux.md:48
Docs/ValidatingAlsaOnLinux.md runs `dotnet test --project NAudio.Alsa.Tests/NAudio.Alsa.Tests.csproj -c Release`, but `NAudio.Alsa.Tests/NAudio.Alsa.Tests.csproj` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/ValidatingAlsaOnLinux.md:49
Docs/Architecture/DirectSoundActivationModernization.md names `NAudio.Core/Utils/NativeMethods.cs`, but no file or folder `NAudio.Core/Utils/NativeMethods.cs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/Architecture/DirectSoundActivationModernization.md:3
Docs/Architecture/DirectSoundActivationModernization.md runs `dotnet publish NAudioAotSmokeTest -c Release -p:PublishAot=false -p:PublishTrimmed=true -p:BuiltInComInteropSupport=false` from `Docs/Architecture/` or the repository root, but `NAudioAotSmokeTest` is not there: the project is `tests/NAudioAotSmokeTest`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/Architecture/DirectSoundActivationModernization.md:96
Docs/Architecture/MODERNIZATION.md names .NET 6, but the projects target .NET 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/Architecture/MODERNIZATION.md:11
Docs/Architecture/MODERNIZATION.md runs `dotnet publish NAudioAotSmokeTest -c Release -p:PublishTrimmed=true -p:BuiltInComInteropSupport=false` from `Docs/Architecture/` or the repository root, but `NAudioAotSmokeTest` is not there: the project is `tests/NAudioAotSmokeTest`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/Architecture/MODERNIZATION.md:254
Docs/Architecture/MODERNIZATION.md names `NAudioTests/Utils/CountingStream.cs`, but no file or folder `NAudioTests/Utils/CountingStream.cs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/Architecture/MODERNIZATION.md:324
Docs/Architecture/MediaFoundationActivationModernization.md runs `dotnet publish NAudioAotSmokeTest -c Release -p:PublishAot=false -p:PublishTrimmed=true` from `Docs/Architecture/` or the repository root, but `NAudioAotSmokeTest` is not there: the project is `tests/NAudioAotSmokeTest`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/Architecture/MediaFoundationActivationModernization.md:241
Docs/Architecture/Vst3Hosting.md names the project `NAudio.Vst3Host`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/Architecture/Vst3Hosting.md:28
Docs/Architecture/Vst3Hosting.md names the project `NAudio.PluginHost`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/Architecture/Vst3Hosting.md:28
Docs/Architecture/Vst3Hosting.md names the project `NAudio.AudioUnit`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/Architecture/Vst3Hosting.md:143
Docs/Architecture/Vst3Hosting.md names the project `NAudio.Clap`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/Architecture/Vst3Hosting.md:143
src/NAudio.Alsa/README.md installs the package `NAudio.Alsa` (`dotnet add package NAudio.Alsa`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/NAudio.Alsa/README.md:32
src/NAudio.Alsa/README.md installs the package `NAudio.SoundFile` (`dotnet add package NAudio.SoundFile`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/NAudio.Alsa/README.md:75
src/NAudio.SoundFile/README.md installs the package `NAudio.SoundFile` (`dotnet add package NAudio.SoundFile`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/NAudio.SoundFile/README.md:35
src/NAudio.Vst3/README.md installs the package `NAudio.Vst3` (`dotnet add package NAudio.Vst3`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/NAudio.Vst3/README.md:20
tests/MfStressTest/README.md runs `dotnet run -c Release --project MfStressTest` from `tests/MfStressTest/` or the repository root, but `MfStressTest` is not there: the project is `tests/MfStressTest`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tests/MfStressTest/README.md:141
tests/NAudioAotSmokeTest/README.md runs `dotnet publish NAudioAotSmokeTest/NAudioAotSmokeTest.csproj -c Release -p:PublishAot=false -p:PublishTrimmed=true`, but `NAudioAotSmokeTest/NAudioAotSmokeTest.csproj` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tests/NAudioAotSmokeTest/README.md:88
What to do
Reconcile the README with reality: Docs/CrossPlatformAudioFilesWithSoundFile.md installs the package `NAudio.SoundFile` (`dotnet add package NAudio.SoundFile`), but no project or props file references it; Docs/PlayAudioFileLinuxAlsa.md installs the package `NAudio.Alsa` (`dotnet add package NAudio.Alsa`), but no project or props file references it; Docs/PlayAudioFileMacOS.md installs the package `NAudio.MacOS` (`dotnet add package NAudio.MacOS --prerelease`), but no project or props file references it; Docs/RecordAudioFileLinuxAlsa.md installs the package `NAudio.Alsa` (`dotnet add package NAudio.Alsa`), but no project or props file references it; Docs/RecordAudioFileMacOS.md installs the package `NAudio.MacOS` (`dotnet add package NAudio.MacOS --prerelease`), but no project or props file references it.
Only 5/11 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 11, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 502 use(s) across 131,255 production line(s) (~3.8/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
6 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×6) — samples/NAudioConsoleTest/Vst3/Tests/Vst3LiveSynthTest.cs:64, samples/NAudioConsoleTest/Vst3/Tests/Vst3LiveSynthTest.cs:88, samples/NAudioConsoleTest/Wasapi/Tests/WasapiPlayFileTest.cs:65, …
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Do you agree with this assessment?
X1 · Async correctness3.9 / 10Weak✓ 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.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. — samples/NAudioDemo/AudioPlaybackDemo/WasapiPlayerPlugin.cs:29
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×11) — samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:52, samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:130, samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:280, …
Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — samples/NAudioDemo/Mp3StreamingDemo/MP3StreamingPanel.cs:66
`SingleLinkedCaptureBufferQueue.Dequeue` is a synchronous helper that blocks (`SemaphoreSlim.Wait`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll). (×2) — src/NAudio.MacOS/Wave/CoreAudioRecorder.BaseAPI.cs:383, src/NAudio.MacOS/Wave/CoreAudioRecorder.BaseAPI.cs:401
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`ofd` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `openToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var ofd = …;`), which releases it at the end of the scope on every path including a throw. — samples/AudioFileInspector/AudioFileInspectorForm.cs:83
`aboutForm` is a `AboutForm`, which implements `IDisposable`, and it is created here (line 104). Every use of it in `aboutToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var aboutForm = …;`), which releases it at the end of the scope on every path including a throw. — samples/AudioFileInspector/AudioFileInspectorForm.cs:104
`optionsForm` is a `OptionsForm`, which implements `IDisposable`, and it is created here (line 119). Every use of it in `optionsToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var optionsForm = …;`), which releases it at the end of the scope on every path including a throw. — samples/AudioFileInspector/AudioFileInspectorForm.cs:119
`saveFileDialog` is a `SaveFileDialog`, which implements `IDisposable`, and it is created here (line 148). Every use of it in `saveLogToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var saveFileDialog = …;`), which releases it at the end of the scope on every path including a throw. — samples/AudioFileInspector/AudioFileInspectorForm.cs:148
`container` is a `CompositionContainer`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var container = …;`), which releases it at the end of the scope on every path including a throw. — samples/AudioFileInspector/Program.cs:21
`folderBrowser` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 261). Every use of it in `buttonBrowseEZDrummer_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var folderBrowser = …;`), which releases it at the end of the scope on every path including a throw. — samples/MidiFileConverter/MainForm.cs:261
`folderBrowser` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 272). Every use of it in `buttonBrowseOutputFolder_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var folderBrowser = …;`), which releases it at the end of the scope on every path including a throw. — samples/MidiFileConverter/MainForm.cs:272
`aboutForm` is a `AboutForm`, which implements `IDisposable`, and it is created here (line 305). Every use of it in `aboutToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var aboutForm = …;`), which releases it at the end of the scope on every path including a throw. — samples/MidiFileConverter/MainForm.cs:305
`optionsForm` is a `AdvancedOptionsForm`, which implements `IDisposable`, and it is created here (line 323). Every use of it in `optionsToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var optionsForm = …;`), which releases it at the end of the scope on every path including a throw. — samples/MidiFileConverter/MainForm.cs:323
`saveFileDialog` is a `SaveFileDialog`, which implements `IDisposable`, and it is created here (line 336). Every use of it in `saveLogToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var saveFileDialog = …;`), which releases it at the end of the scope on every path including a throw. — samples/MidiFileConverter/MainForm.cs:336
`openFileDialog` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 42). Every use of it in `LoadFile` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var openFileDialog = …;`), which releases it at the end of the scope on every path including a throw. — samples/MixDiff/MixDiffForm.cs:42
`propertiesForm` is a `PropertiesForm`, which implements `IDisposable`, and it is created here (line 352). Every use of it in `propertiesToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var propertiesForm = …;`), which releases it at the end of the scope on every path including a throw. — samples/MixDiff/MixDiffForm.cs:352
`saveFileDialog` is a `SaveFileDialog`, which implements `IDisposable`, and it is created here (line 362). Every use of it in `saveComparisonToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var saveFileDialog = …;`), which releases it at the end of the scope on every path including a throw. — samples/MixDiff/MixDiffForm.cs:362
`openFileDialog` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 426). Every use of it in `openSavedComparisonToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var openFileDialog = …;`), which releases it at the end of the scope on every path including a throw. — samples/MixDiff/MixDiffForm.cs:426
`aboutForm` is a `AboutForm`, which implements `IDisposable`, and it is created here (line 455). Every use of it in `aboutToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var aboutForm = …;`), which releases it at the end of the scope on every path including a throw. — samples/MixDiff/MixDiffForm.cs:455
`settingsForm` is a `SettingsForm`, which implements `IDisposable`, and it is created here (line 461). Every use of it in `settingsToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var settingsForm = …;`), which releases it at the end of the scope on every path including a throw. — samples/MixDiff/MixDiffForm.cs:461
`MixDiffStream` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `offsetStream` itself (line 8), which makes that instance its own. But `offsetStream` is named in none of the methods the disposal search covered: `Dispose` (line 111) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`offsetStream?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — samples/MixDiff/MixDiffStream.cs:8
`completed` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 50). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var completed = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioConsoleTest/Asio/Tests/AsioDisposeFromStoppedHandlerTest.cs:50
`completed` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 92). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var completed = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs:92
`stopped` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 114). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var stopped = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:114
`completed` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 94). Every use of it in `RunDevicePlayback` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var completed = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioConsoleTest/Asio/Tests/AsioPlayAudioFileTest.cs:94
`completed` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 88). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var completed = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioConsoleTest/Asio/Tests/AsioRecordToWavTest.cs:88
`fired` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 41). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var fired = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioConsoleTest/Asio/Tests/AsioStopFromCallbackGuardTest.cs:41
`captured` is a `MemoryStream`, which implements `IDisposable`, and it is created here (line 54). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var captured = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecordAndPlaybackTest.cs:54
`openFileDialog` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 129). Every use of it in `SelectFileToOpen` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var openFileDialog = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioDemo/AcmDemo/AcmPanel.cs:129
`saveFileDialog` is a `SaveFileDialog`, which implements `IDisposable`, and it is created here (line 146). Every use of it in `GetOutputFileName` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var saveFileDialog = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioDemo/AcmDemo/AcmPanel.cs:146
`ofd` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 42). Every use of it in `OnButtonSelectFileClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var ofd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:42
`openFileDialog` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 260). Every use of it in `OnOpenFileClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var openFileDialog = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioDemo/AudioPlaybackDemo/AudioPlaybackPanel.cs:260
`ofd` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 56). Every use of it in `SelectInputFile` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var ofd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:56
`sfd` is a `SaveFileDialog`, which implements `IDisposable`, and it is created here (line 343). Every use of it in `OnButtonSaveClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var sfd = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioDemo/SignalGeneratorDemo/GeneratorPanel.cs:343
`process` is a `Process`, which implements `IDisposable`, and it is created here (line 9). Every use of it in `ShellExecute` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var process = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioDemo/Utils/ProcessHelper.cs:9
`deviceEnumerator` is a `MMDeviceEnumerator`, which implements `IDisposable`, and it is created here (line 35). Every use of it in `VolumePanel` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var deviceEnumerator = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioDemo/VolumeMixerDemo/VolumePanel.cs:35
`deviceEnumerator` is a `MMDeviceEnumerator`, which implements `IDisposable`, and it is created here (line 86). Every use of it in `VolumePanel_Load` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var deviceEnumerator = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioDemo/VolumeMixerDemo/VolumePanel.cs:86
`p` is a `Process`, which implements `IDisposable`, and it is created here (line 300). Every use of it in `ShellExecute` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var p = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioWpfDemo/ConvolutionReverbDemo/ConvolutionReverbDemoViewModel.cs:300
`process` is a `Process`, which implements `IDisposable`, and it is created here (line 45). Every use of it in `ShellExecute` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var process = …;`), which releases it at the end of the scope on every path including a throw. — samples/NAudioWpfDemo/WasapiRecorderDemo/RecordingsViewModel.cs:45
`DirectSoundOut` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `frameEventWaitHandle1` itself (line 37), which makes that instance its own. But `frameEventWaitHandle1` is named in none of the methods the disposal search covered: `Dispose` (line 461), `Stop` (line 175) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`frameEventWaitHandle1?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:37
`DirectSoundOut` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `frameEventWaitHandle2` itself (line 38), which makes that instance its own. But `frameEventWaitHandle2` is named in none of the methods the disposal search covered: `Dispose` (line 461), `Stop` (line 175) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`frameEventWaitHandle2?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:38
`DirectSoundOut` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `endEventWaitHandle` itself (line 39), which makes that instance its own. But `endEventWaitHandle` is named in none of the methods the disposal search covered: `Dispose` (line 461), `Stop` (line 175) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`endEventWaitHandle?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:39
`AudioSessionControl` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `audioMeterInformation` itself (line 27), which makes that instance its own. But `audioMeterInformation` is named in none of the methods the disposal search covered: `Dispose` (line 95), `QueryEventsInterface` (line 37) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`audioMeterInformation?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/NAudio.Wasapi/CoreAudioApi/AudioSessionControl.cs:27
`AudioSessionControl` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `simpleAudioVolume` itself (line 28), which makes that instance its own. But `simpleAudioVolume` is named in none of the methods the disposal search covered: `Dispose` (line 95), `QueryEventsInterface` (line 37) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`simpleAudioVolume?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/NAudio.Wasapi/CoreAudioApi/AudioSessionControl.cs:28
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 3/31 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×28) — samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:52, samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:74, samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:130, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
The guard on line 67 rejects `key` and line 69 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(key)` is true of a value that is NOT null: it is satisfied by an EMPTY `key`, and on that path `key` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/NAudio.Core/FileFormats/Mp3/Id3v2Tag.cs:69
The guard on line 72 rejects `value` and line 74 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(value)` is true of a value that is NOT null: it is satisfied by an EMPTY `value`, and on that path `value` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/NAudio.Core/FileFormats/Mp3/Id3v2Tag.cs:74
What to do
Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element6.0 / 10Adequate✓ Tool-verified
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.
This loop runs once per element of `selected`, and the statement it guards acts on the element it is on — `selected[i]`. The test deciding whether that statement runs does not: `other != format` reads `selected[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 878, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out. — src/NAudio.Asio/AsioDevice.cs:882
What to do
Each finding names the test and the statement it guards, which index the same collection at two different subscripts — one fixed, one the loop variable. Confirm from the two, then decide which subscript the test meant. If it was meant to be per-element, give it the loop variable so each element is judged on itself. If it really is one answer for the whole collection, hoist the test OUT of the loop, where a reader can see it is asked once and where it is not re-evaluated on every pass — leaving it inside, reading a fixed element, is the one arrangement that cannot be right under either reading.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×35) — samples/MidiFileConverter/MainForm.cs:57, samples/NAudioConsoleTest/Program.cs:17, samples/NAudioConsoleTest/Shared/Testing/DiagnosticsCollector.cs:55, …
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×4) — samples/NAudioConsoleTest/Shared/Testing/RecentFilesStore.cs:48, samples/NAudioDemo/NetworkChatDemo/NetworkChatPanel.cs:93, samples/NAudioDemo/RecordingDemo/RecordingPanel.cs:186, …
`catch (MmException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — samples/NAudioDemo/NetworkChatDemo/AcmChatCodec.cs:87
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This method contradicts itself about `buttonInfo`: line 71 assigns it with `as MixdownInfo`, which hands back null rather than throwing when the value is not a `MixdownInfo`, but line 72 then dereferences it directly as `buttonInfo.Stream` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `buttonInfo` once before the first use and handle the null case, or cast with `(MixdownInfo)` so the failure is reported where it happens — rather than leaving the two readings side by side. — samples/MixDiff/MixDiffForm.cs:72
This method contradicts itself about `button`: line 107 assigns it with `as Button`, which hands back null rather than throwing when the value is not a `Button`, but line 108 then dereferences it directly as `button.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `button` once before the first use and handle the null case, or cast with `(Button)` so the failure is reported where it happens — rather than leaving the two readings side by side. — samples/MixDiff/MixDiffForm.cs:108
14/20 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~0.2 `!` suppressions per 1k syntax nodes — 73 suppression(s) across the 319583 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
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.
Unscored — 4 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 — 2 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.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 12 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 41 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D11 Test Reliability — Test reliability not measured — no test run produced results
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: this repository runs its tests on Microsoft.Testing.Platform (its global.json opts in), where coverage comes from a coverage extension the test project references — and none is wired up: no build file names `Microsoft.Testing.Extensions.CodeCoverage` or `coverlet.MTP`. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment. Add one of those PackageReferences to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (6 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message — its own wrapper, log4net, Console or Debug — so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
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.
EmptyCatchBlock samples/MidiFileConverter/MainForm.cs:57— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs:127— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:139— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Asio/Tests/AsioPlayAudioFileTest.cs:116— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Asio/Tests/AsioRecordToWavTest.cs:106— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Asio/Tests/AsioShowChannelLevelsTest.cs:103— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Program.cs:17— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Shared/Testing/DiagnosticsCollector.cs:55— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Shared/Testing/DiagnosticsCollector.cs:56— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Shared/Testing/DiagnosticsCollector.cs:74— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Shared/Testing/DiagnosticsCollector.cs:80— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Shared/Testing/RecentFilesStore.cs:74— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Shared/Testing/RecentFilesStore.cs:88— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/SoundFile/Tests/SoundFileRoundTripTest.cs:102— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Wasapi/Tests/WasapiListDevicesTest.cs:33— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Wasapi/Tests/WasapiVolumeCallbackStressTest.cs:167— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioConsoleTest/Wasapi/Tests/WasapiVolumeSafety.cs:27— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioDemo/AudioPlaybackDemo/WasapiOutSettingsPanel.cs:43— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:186— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioDemo/MixingCaptureDemo/MixingCapturePanel.cs:431— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioDemo/MixingCaptureDemo/MixingCapturePanel.cs:572— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioDemo/MixingCaptureDemo/MixingCapturePanel.cs:573— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioDemo/MixingCaptureDemo/MixingCapturePanel.cs:579— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioDemo/RecordingDemo/RecordingPanel.cs:219— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock samples/NAudioDemo/RecordingDemo/RecordingPanel.cs:248— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
WriteOnlyPrivateField src/NAudio.Asio/AsioDriverExt.cs:54— private int outputChannelOffset — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/NAudio.Asio/AsioDriverExt.cs:55— private int inputChannelOffset — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:21— private int startOffset — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:22— private int endOffset — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:24— private int tocOffset — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/NAudio.Vst3/Vst3Plugin.cs:65— private ulong _inputArrangement — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/NAudio.Vst3/Vst3Plugin.cs:66— private ulong _outputArrangement — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/NAudio.Vst3/Vst3Plugin.cs:90— private bool _eventInputActive — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/NAudio.Wasapi/CoreAudioApi/Part.cs:18— private Guid IID_IAudioEndpointVolume — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
AnalyzerSeverityNone .globalconfig:14— CA1707 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .globalconfig:24— CA1051 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .globalconfig:27— CA1069 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .globalconfig:30— CA1708 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .globalconfig:33— CA1711 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .globalconfig:36— CA1712 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .globalconfig:39— CA1852 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
NoWarnInCsproj tests/NAudioAsioFakeDriverTest/NAudioAsioFakeDriverTest.csproj:22— CA1416 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/NAudioWpfDemo/NAudioWpfDemo.csproj:8— CA1001 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/NAudioDemo/NAudioDemo.csproj:10— CA1001 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj samples/MixDiff/MixDiff.csproj:8— CA1001 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
FileScopedPragmaDisable src/NAudio.MacOS/MacOS/AudioToolbox/Interop/AudioConverterProperties.cs:10— #pragma warning disable IDE0055 // We want the properties to have a consistent view. — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable src/NAudio.MacOS/MacOS/AudioToolbox/Interop/ExtendedAudioFileProperties.cs:10— #pragma warning disable IDE0055 // We want the properties to have a consistent view. — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable src/NAudio.MacOS/MacOS/AudioToolbox/Interop/GlobalAudioFileProperties.cs:8— #pragma warning disable IDE0055 // We want the properties to have a consistent view. — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
Assertions commented out: ResamplerCanCallProcessOutput tests/NAudio.Windows.Tests/Dmo/ResamplerDmoTests.cs:141— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: CanFindDefaultWaveIn tests/NAudio.Windows.Tests/Mixer/MixerApiTests.cs:30— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Namespace dependency cycle src/NAudio.MacOS/MacOS/RangedWaveFormat.cs:7— The namespaces NAudio.CoreAudioApi ↔ NAudio.CoreAudioApi.Interfaces ↔ NAudio.Dmo ↔ NAudio.Dmo.Effect ↔ NAudio.MacOS ↔ NAudio.MacOS.AudioToolbox ↔ NAudio.MacOS.AudioToolbox.Interop ↔ NAudio.MacOS.CoreAudio ↔ NAudio.MacOS.CoreAudio.Interop ↔ NAudio.MediaFoundation ↔ NAudio.MediaFoundation.Interfaces ↔ NAudio.Utils ↔ NAudio.Wave ↔ NAudio.Wave.Asio ↔ NAudio.Wave.Compression ↔ NAudio.Wave.SampleProviders depend on each other. The lightest dependency in the cycle is NAudio.MacOS → NAudio.MacOS.CoreAudio.Interop (NAudio.MacOS.RangedWaveFormat → NAudio.MacOS.CoreAudio.Interop.AudioStreamRangedDescription, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
FileScopedPragmaDisable repeated across 13 files samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:7— The identical FileScopedPragmaDisable (`#pragma warning disable CS0618`) appears in 13 files (13 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 13 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
DisabledAnalyzers Directory.Build.props:71— AnalysisLevel — this does not switch a rule off, it stops the analyzers running for the whole project: every rule they ship is silenced at once, including every rule added by a future upgrade, and nothing at the sites they would have reported records that anything was switched off. There is no code here to look up and nothing to weigh, which is what makes it the one suppression that is never revisited. Turn the analyzers back on and deal with what they report — suppressing the handful of rules that are genuinely unwanted, each on its own line with its reason, keeps the rest protecting the project and leaves a record a reader can audit.
Dead code: FindBeatsPerMeasure samples/AudioFileInspector/FileInspectors/MidiFileInspector.cs:61— Method FindBeatsPerMeasure — Roslyn's SymbolFinder walked every project the solution loads, including AudioFileInspector, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AudioFileSelector samples/NAudioConsoleTest/Shared/AudioFileSelector.cs:5— NamedType AudioFileSelector — Roslyn's SymbolFinder walked every project the solution loads, including NAudioConsoleTest, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: DeviceSelector samples/NAudioConsoleTest/Shared/DeviceSelector.cs:6— NamedType DeviceSelector — Roslyn's SymbolFinder walked every project the solution loads, including NAudioConsoleTest, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: NotAutomatable samples/NAudioConsoleTest/Shared/Testing/TestResult.cs:31— Method NotAutomatable — Roslyn's SymbolFinder walked every project the solution loads, including NAudioConsoleTest, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AcmPanelPlugin samples/NAudioDemo/AcmDemo/AcmPanel.cs:263— NamedType AcmPanelPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AsioDirectPanelPlugin REDACTED:121— NamedType AsioDirectPanelPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AsioRecordingPanelPlugin samples/NAudioDemo/AsioRecordingDemo/AsioRecordingPanel.cs:255— NamedType AsioRecordingPanelPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AsioDevicePlugin samples/NAudioDemo/AudioPlaybackDemo/AsioDevicePlugin.cs:10— NamedType AsioDevicePlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AsioOutPlugin samples/NAudioDemo/AudioPlaybackDemo/AsioOutPlugin.cs:6— NamedType AsioOutPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AudioPlaybackPanelPlugin samples/NAudioDemo/AudioPlaybackDemo/AudioPlaybackPanelPlugin.cs:5— NamedType AudioPlaybackPanelPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: DirectSoundOutPlugin samples/NAudioDemo/AudioPlaybackDemo/DirectSoundOutPlugin.cs:7— NamedType DirectSoundOutPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: WaveOutPlugin samples/NAudioDemo/AudioPlaybackDemo/WaveOutPlugin.cs:6— NamedType WaveOutPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: WaveOutWindowPlugin samples/NAudioDemo/AudioPlaybackDemo/WaveOutWindowPlugin.cs:6— NamedType WaveOutWindowPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: DeviceNotificationsPanelPlugin samples/NAudioDemo/DeviceNotificationsDemo/DeviceNotificationsPanel.cs:58— NamedType DeviceNotificationsPanelPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: Tb_ValueChanged samples/NAudioDemo/DeviceTopology/DeviceTopologyPanel.cs:136— Method Tb_ValueChanged — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: DeviceTopologyPlugin samples/NAudioDemo/DeviceTopology/DeviceTopologyPlugin.cs:3— NamedType DeviceTopologyPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: FadeInOutPlugin samples/NAudioDemo/FadeInOutDemo/FadeInOutPlugin.cs:3— NamedType FadeInOutPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: MidiInPanelPlugin samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:478— NamedType MidiInPanelPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: MixingCaptureDemoPlugin samples/NAudioDemo/MixingCaptureDemo/MixingCaptureDemoPlugin.cs:9— NamedType MixingCaptureDemoPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: Mp3StreamingPanelPlugin samples/NAudioDemo/Mp3StreamingDemo/MP3StreamingPanel.cs:282— NamedType Mp3StreamingPanelPlugin — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AcmALawChatCodec samples/NAudioDemo/NetworkChatDemo/ALawChatCodec.cs:7— NamedType AcmALawChatCodec — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ALawChatCodec samples/NAudioDemo/NetworkChatDemo/ALawChatCodec.cs:18— NamedType ALawChatCodec — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: G722ChatCodec samples/NAudioDemo/NetworkChatDemo/G722ChatCodec.cs:9— NamedType G722ChatCodec — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: Gsm610ChatCodec samples/NAudioDemo/NetworkChatDemo/Gsm610ChatCodec.cs:5— NamedType Gsm610ChatCodec — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: MicrosoftAdpcmChatCodec samples/NAudioDemo/NetworkChatDemo/MicrosoftAdpcmChatCodec.cs:5— NamedType MicrosoftAdpcmChatCodec — Roslyn's SymbolFinder walked every project the solution loads, including NAudioDemo, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
TodoComment samples/AudioFileInspector/FileAssociations.cs:117— // TODO: add ourselves as an "Open With" application — 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 samples/AudioFileInspector/FileAssociations.cs:118— // TODO: better error handling — 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 samples/AudioFileInspector/FileAssociations.cs:119— // TODO: unregistering stuff — 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 samples/AudioFileInspector/FileAssociations.cs:120— // TODO: set default action — 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 samples/MixDiff/MixDiffForm.cs:47— // TODO: sort this out - post shuffle — 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 samples/MixDiff/MixDiffForm.cs:464— // TODO: reopen WaveOut device — 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 samples/NAudioDemo/AudioPlaybackDemo/AudioPlaybackPanel.cs:80— // TODO: only re-initialise if necessary — 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 samples/NAudioWpfDemo/MediaFoundationEncode/MediaFoundationEncodeViewModel.cs:36— // TODO: fill this by asking the encoders what they can do — 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 src/NAudio.Asio/AsioSampleConvertor.cs:24— // TODO : IMPLEMENTS OTHER CONVERTOR TYPES — 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 src/NAudio.Core/Dsp/WdlResampler.cs:209— // todo: notify of error? — 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 src/NAudio.Core/FileFormats/Mp3/Mp3Frame.cs:100— // TODO: could have an option to suppress this, although it does indicate a corrupt file — 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 src/NAudio.Core/FileFormats/Mp3/Mp3Frame.cs:192— // TODO: could do with a bitstream class here — 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 src/NAudio.Core/FileFormats/SoundFont/SoundFont.cs:154— // TODO: save / save as function — 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 src/NAudio.Core/Wave/WaveFormats/AdpcmWaveFormat.cs:76— // TODO: validate sampleRate, bitsPerSample — 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 src/NAudio.Core/Wave/WaveStreams/WaveOffsetStream.cs:38— // TODO: add support for IEEE float + perhaps some others - — 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 src/NAudio.Dmo/Dmo/MediaObject.cs:529— // TODO: there are still several IMediaObject functions to be wrapped — 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 src/NAudio.Extras/CachedSound.cs:50— // TODO: could add resampling in here if required — 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 src/NAudio.MacOS/MacOS/AudioToolbox/LowLevelAudioConverter.cs:17— // mdcdi1315: TODO: This work is primitive but for now it works. — 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 src/NAudio.Midi/Midi/ChannelAfterTouchEvent.cs:22— // TODO: might be a follow-on — 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 src/NAudio.Midi/Midi/ControlChangeEvent.cs:24— // TODO: might be a follow-on — 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 src/NAudio.Midi/Midi/PatchChangeEvent.cs:51— // TODO: might be a follow-on — 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 src/NAudio.Midi/Midi/PitchWheelChangeEvent.cs:23— // TODO: might be a follow-on — 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 src/NAudio.Midi/Midi/PatchChangeEvent.cs:21— // TODO: localize — 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 src/NAudio.Midi/Midi/TrackSequenceNumberEvent.cs:28— // TODO: there is a form of the TrackSequenceNumberEvent that — 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 src/NAudio.Wasapi/MediaFoundation/AudioSubtypes.cs:174— // TODO: find out what these are, and add them: — 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.
Swallowed exception (empty catch) samples/MidiFileConverter/MainForm.cs:57— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioConsoleTest/Program.cs:17— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioConsoleTest/Shared/Testing/DiagnosticsCollector.cs:55— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioConsoleTest/Shared/Testing/DiagnosticsCollector.cs:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioConsoleTest/Shared/Testing/DiagnosticsCollector.cs:74— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioConsoleTest/Shared/Testing/DiagnosticsCollector.cs:80— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioConsoleTest/Shared/Testing/RecentFilesStore.cs:74— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioConsoleTest/Shared/Testing/RecentFilesStore.cs:88— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioDemo/AudioPlaybackDemo/WasapiOutSettingsPanel.cs:43— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:186— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioDemo/MixingCaptureDemo/MixingCapturePanel.cs:431— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioDemo/MixingCaptureDemo/MixingCapturePanel.cs:572— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioDemo/MixingCaptureDemo/MixingCapturePanel.cs:573— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioDemo/MixingCaptureDemo/MixingCapturePanel.cs:579— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioDemo/RecordingDemo/RecordingPanel.cs:219— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioDemo/RecordingDemo/RecordingPanel.cs:248— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioDemo/VolumeMixerDemo/VolumePanel.cs:213— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioDemo/VolumeMixerDemo/VolumePanel.cs:228— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioWpfDemo/DemoSettings.cs:60— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioWpfDemo/DemoSettings.cs:72— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:158— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:339— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3PluginSlotViewModel.cs:80— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3PluginSlotViewModel.cs:98— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3PluginSlotViewModel.cs:129— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
+ 10 more in this group — see findings.md.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×34
Disposable created and abandoned in the method that made it samples/AudioFileInspector/AudioFileInspectorForm.cs:83— `ofd` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `openToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var ofd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/AudioFileInspector/AudioFileInspectorForm.cs:104— `aboutForm` is a `AboutForm`, which implements `IDisposable`, and it is created here (line 104). Every use of it in `aboutToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var aboutForm = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/AudioFileInspector/AudioFileInspectorForm.cs:119— `optionsForm` is a `OptionsForm`, which implements `IDisposable`, and it is created here (line 119). Every use of it in `optionsToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var optionsForm = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/AudioFileInspector/AudioFileInspectorForm.cs:148— `saveFileDialog` is a `SaveFileDialog`, which implements `IDisposable`, and it is created here (line 148). Every use of it in `saveLogToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var saveFileDialog = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/AudioFileInspector/Program.cs:21— `container` is a `CompositionContainer`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var container = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MidiFileConverter/MainForm.cs:261— `folderBrowser` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 261). Every use of it in `buttonBrowseEZDrummer_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var folderBrowser = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MidiFileConverter/MainForm.cs:272— `folderBrowser` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 272). Every use of it in `buttonBrowseOutputFolder_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var folderBrowser = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MidiFileConverter/MainForm.cs:305— `aboutForm` is a `AboutForm`, which implements `IDisposable`, and it is created here (line 305). Every use of it in `aboutToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var aboutForm = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MidiFileConverter/MainForm.cs:323— `optionsForm` is a `AdvancedOptionsForm`, which implements `IDisposable`, and it is created here (line 323). Every use of it in `optionsToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var optionsForm = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MidiFileConverter/MainForm.cs:336— `saveFileDialog` is a `SaveFileDialog`, which implements `IDisposable`, and it is created here (line 336). Every use of it in `saveLogToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var saveFileDialog = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MixDiff/MixDiffForm.cs:42— `openFileDialog` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 42). Every use of it in `LoadFile` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var openFileDialog = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MixDiff/MixDiffForm.cs:352— `propertiesForm` is a `PropertiesForm`, which implements `IDisposable`, and it is created here (line 352). Every use of it in `propertiesToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var propertiesForm = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MixDiff/MixDiffForm.cs:362— `saveFileDialog` is a `SaveFileDialog`, which implements `IDisposable`, and it is created here (line 362). Every use of it in `saveComparisonToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var saveFileDialog = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MixDiff/MixDiffForm.cs:426— `openFileDialog` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 426). Every use of it in `openSavedComparisonToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var openFileDialog = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MixDiff/MixDiffForm.cs:455— `aboutForm` is a `AboutForm`, which implements `IDisposable`, and it is created here (line 455). Every use of it in `aboutToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var aboutForm = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/MixDiff/MixDiffForm.cs:461— `settingsForm` is a `SettingsForm`, which implements `IDisposable`, and it is created here (line 461). Every use of it in `settingsToolStripMenuItem_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var settingsForm = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/NAudioConsoleTest/Asio/Tests/AsioDisposeFromStoppedHandlerTest.cs:50— `completed` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 50). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var completed = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs:92— `completed` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 92). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var completed = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:114— `stopped` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 114). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var stopped = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/NAudioConsoleTest/Asio/Tests/AsioPlayAudioFileTest.cs:94— `completed` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 94). Every use of it in `RunDevicePlayback` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var completed = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/NAudioConsoleTest/Asio/Tests/AsioRecordToWavTest.cs:88— `completed` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 88). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var completed = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/NAudioConsoleTest/Asio/Tests/AsioStopFromCallbackGuardTest.cs:41— `fired` is a `ManualResetEventSlim`, which implements `IDisposable`, and it is created here (line 41). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var fired = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecordAndPlaybackTest.cs:54— `captured` is a `MemoryStream`, which implements `IDisposable`, and it is created here (line 54). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var captured = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/NAudioDemo/AcmDemo/AcmPanel.cs:129— `openFileDialog` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 129). Every use of it in `SelectFileToOpen` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var openFileDialog = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/NAudioDemo/AcmDemo/AcmPanel.cs:146— `saveFileDialog` is a `SaveFileDialog`, which implements `IDisposable`, and it is created here (line 146). Every use of it in `GetOutputFileName` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var saveFileDialog = …;`), which releases it at the end of the scope on every path including a throw.
No assertions: HasConnectInputToOutputMethod tests/NAudio.Core.Tests/WaveStreams/MultiplexingSampleProviderTests.cs:129— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: HasConnectInputToOutputMethod tests/NAudio.Core.Tests/WaveStreams/MultiplexingWaveProviderTests.cs:154— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanUseWriteSampleToA16BitFile tests/NAudio.Core.Tests/WaveStreams/WaveFileWriterTests.cs:143— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: LoopThroughDevices tests/NAudio.MacOS.Tests/AudioHALTests/CanEnumerateDevices.cs:16— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: QueryDefaultInDevice tests/NAudio.MacOS.Tests/AudioHALTests/CanEnumerateDevices.cs:26— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: QueryDefaultOutDevice tests/NAudio.MacOS.Tests/AudioHALTests/CanEnumerateDevices.cs:32— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: QueryDefaultSystemOutDevice tests/NAudio.MacOS.Tests/AudioHALTests/CanEnumerateDevices.cs:38— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: HasFindByShortNameMethod tests/NAudio.Windows.Tests/Acm/AcmDriverTests.cs:38— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanConvertAdpcmToSuggestedPcm tests/NAudio.Windows.Tests/Acm/WaveFormatConversionStreamTests.cs:79— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanConvertALawToSuggestedPcm tests/NAudio.Windows.Tests/Acm/WaveFormatConversionStreamTests.cs:88— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanConvertMuLawToSuggestedPcm tests/NAudio.Windows.Tests/Acm/WaveFormatConversionStreamTests.cs:97— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanEnumerateDevices tests/NAudio.Windows.Tests/DirectSound/DirectSoundTests.cs:13— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanDecompressAnMp3 tests/NAudio.Windows.Tests/Dmo/DmoMp3FrameDecompressorTests.cs:23— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanEnumerateAudioEffects tests/NAudio.Windows.Tests/Dmo/DmoTests.cs:11— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanEnumerateAudioEncoders tests/NAudio.Windows.Tests/Dmo/DmoTests.cs:23— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanEnumerateAudioDecoders tests/NAudio.Windows.Tests/Dmo/DmoTests.cs:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanResampleAWholeStreamToIEEE tests/NAudio.Windows.Tests/Dmo/ResamplerDmoStreamTests.cs:40— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanResampleAWholeStreamTo48000PCM tests/NAudio.Windows.Tests/Dmo/ResamplerDmoStreamTests.cs:49— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanResampleAWholeStreamTo44100IEEE tests/NAudio.Windows.Tests/Dmo/ResamplerDmoStreamTests.cs:59— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanResampleAWholeStreamTo44100PCM tests/NAudio.Windows.Tests/Dmo/ResamplerDmoStreamTests.cs:68— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanCreateResamplerMediaObject tests/NAudio.Windows.Tests/Dmo/ResamplerDmoTests.cs:18— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ResamplerCanCallProcessInput tests/NAudio.Windows.Tests/Dmo/ResamplerDmoTests.cs:129— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanGetWaveInMixerLine tests/NAudio.Windows.Tests/Mixer/MixerApiTests.cs:71— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanCaptureDefaultDeviceInDefaultFormatUsingWasapiCapture tests/NAudio.Windows.Tests/Wasapi/AudioClientTests.cs:178— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanReuseWasapiCapture tests/NAudio.Windows.Tests/Wasapi/AudioClientTests.cs:187— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 6 more in this group — see findings.md.
X2 · Cancellation propagation· Async method without CancellationToken · ×28
Async method without CancellationToken: MidiInForm_Load samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:52— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PopulateDeviceListsAsync samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:74— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnButtonMonitorClick samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:130— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StartMonitoringAsync samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:142— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnButtonRefreshDevicesClick samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:280— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnComboBoxBackendSelectedIndexChanged samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:285— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnCheckBoxMidiOutMessagesCheckedChanged samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:293— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StartSendingMidiOutAsync samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:305— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: EnsureMidiOutOpenAsync samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:321— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnButtonSendSysexClick samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:355— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ProcessAsync samples/NAudioWpfDemo/ConvolutionReverbDemo/ConvolutionReverbDemoViewModel.cs:116— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RefreshDevicesAsync samples/NAudioWpfDemo/LiveSamplerDemo/LiveSamplerDemoViewModel.cs:143— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Start samples/NAudioWpfDemo/LiveSamplerDemo/LiveSamplerDemoViewModel.cs:159— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Play samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:141— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RenderToWav samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:235— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RenderToWav samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:279— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConnectMidiAsync samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentEngine.cs:101— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Start samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs:157— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RefreshMidi samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs:264— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadMidiDevicesAsync samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs:271— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAsync samples/NAudioWpfDemo/Vst3Shared/Vst3InstalledPlugins.cs:64— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RescanAsync samples/NAudioWpfDemo/Vst3Shared/Vst3InstalledPlugins.cs:82— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Start samples/NAudioWpfDemo/WasapiRecorderDemo/WasapiRecorderViewModel.cs:378— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitializeRecordingAsync src/NAudio.MacOS/Wave/CoreAudioRecorder.BaseAPI.cs:258— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ActivateProcessLoopbackAsync src/NAudio.Wasapi/CoreAudioApi/AudioClient.cs:116— No CancellationToken parameter — this work can't be stopped early once started.
Hotspot: src/NAudio.Core/Dsp/WdlResampler.cs src/NAudio.Core/Dsp/WdlResampler.cs:251— src/NAudio.Core/Dsp/WdlResampler.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in WdlResampler.ResampleOut at line 251. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.Core/Dsp/WdlResampler.cs`: 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: src/NAudio.Midi/Midi/MidiFile.cs src/NAudio.Midi/Midi/MidiFile.cs:55— src/NAudio.Midi/Midi/MidiFile.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in MidiFile.MidiFile.ctor at line 55. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.Midi/Midi/MidiFile.cs`: 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: src/NAudio.Core/Wave/WaveStreams/WaveFileChunkReader.cs src/NAudio.Core/Wave/WaveStreams/WaveFileChunkReader.cs:42— src/NAudio.Core/Wave/WaveStreams/WaveFileChunkReader.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in WaveFileChunkReader.ReadWaveHeader 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-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.Core/Wave/WaveStreams/WaveFileChunkReader.cs`: 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: src/NAudio.Wasapi/WasapiPlayer.cs src/NAudio.Wasapi/WasapiPlayer.cs:752— src/NAudio.Wasapi/WasapiPlayer.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in WasapiPlayer.PlayThread at line 752. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.Wasapi/WasapiPlayer.cs`: 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: src/NAudio.Wasapi/WasapiOut.cs src/NAudio.Wasapi/WasapiOut.cs:97— src/NAudio.Wasapi/WasapiOut.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in WasapiOut.PlayThread at line 97. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.Wasapi/WasapiOut.cs`: 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: src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:130— src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in CoreAudioPlayer.Initialize at line 130. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs`: 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: src/NAudio.Core/Wave/WaveStreams/AiffFileReader.cs src/NAudio.Core/Wave/WaveStreams/AiffFileReader.cs:66— src/NAudio.Core/Wave/WaveStreams/AiffFileReader.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AiffFileReader.ReadAiffHeader at line 66. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.Core/Wave/WaveStreams/AiffFileReader.cs`: 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: src/NAudio.Core/Wave/WaveStreams/CueList.cs src/NAudio.Core/Wave/WaveStreams/CueList.cs:188— src/NAudio.Core/Wave/WaveStreams/CueList.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in CueList.CueList.ctor at line 188. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.Core/Wave/WaveStreams/CueList.cs`: 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: src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesReader.cs src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesReader.cs:44— src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesReader.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in ExtendedAudioFileServicesReader.InitReaderInternal at line 44. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesReader.cs`: 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: src/NAudio.Core/Wave/WaveStreams/Mp3FileReaderBase.cs src/NAudio.Core/Wave/WaveStreams/Mp3FileReaderBase.cs:516— src/NAudio.Core/Wave/WaveStreams/Mp3FileReaderBase.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in Mp3FileReaderBase.Read at line 516. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.Core/Wave/WaveStreams/Mp3FileReaderBase.cs`: 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: src/NAudio.MacOS/Wave/CoreAudioRecorder.InitAPI.cs src/NAudio.MacOS/Wave/CoreAudioRecorder.InitAPI.cs:99— src/NAudio.MacOS/Wave/CoreAudioRecorder.InitAPI.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in CoreAudioRecorder.Initialize at line 99. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 07:11:59 +01:00' --until='2026-10-22 07:11:59 +01:00' --full-history --no-merges -- src/NAudio.MacOS/Wave/CoreAudioRecorder.InitAPI.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (5 lines × 2) src/NAudio.Midi/Sequencing/OfflineMidiRenderer.cs:27— src/NAudio.Midi/Sequencing/OfflineMidiRenderer.cs:27-31 | src/NAudio.Midi/Sequencing/OfflineMidiRenderer.cs:55-59 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/NAudio.Core/FileFormats/SoundFont/InstrumentBuilder.cs:17— src/NAudio.Core/FileFormats/SoundFont/InstrumentBuilder.cs:17-21 | src/NAudio.Core/FileFormats/SoundFont/PresetBuilder.cs:14-18 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/NAudio.Core/Wave/SampleProviders/Pcm24BitToSampleProvider.cs:29— src/NAudio.Core/Wave/SampleProviders/Pcm24BitToSampleProvider.cs:29-33 | src/NAudio.Core/Wave/SampleProviders/Pcm32BitToSampleProvider.cs:29-33 — 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 `src/NAudio.Core/Wave/SampleProviders/Pcm24BitToSampleProvider.cs:29` 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) src/NAudio.Core/Effects/AutomaticGainControlEffect.cs:56— src/NAudio.Core/Effects/AutomaticGainControlEffect.cs:56-60 | src/NAudio.Core/Effects/CompressorEffect.cs:70-74 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/NAudio.WinForms/WaveInWindow.cs:129— src/NAudio.WinForms/WaveInWindow.cs:129-133 | src/NAudio.WinMM/WaveIn.cs:274-278 — 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.
Duplicated block (5 lines × 2) src/NAudio.WinForms/WaveOutWindow.cs:45— src/NAudio.WinForms/WaveOutWindow.cs:45-49 | src/NAudio.WinMM/WaveOut.cs:40-44 — 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.
Duplicated block (5 lines × 2) samples/NAudioDemo/Utils/ReflectionHelper.cs:11— samples/NAudioDemo/Utils/ReflectionHelper.cs:11-15 | samples/NAudioWpfDemo/Utils/ReflectionHelper.cs:11-15 — before extracting anything, compare `samples/NAudioDemo/Utils/ReflectionHelper.cs` and `samples/NAudioWpfDemo/Utils/ReflectionHelper.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (5 lines × 2) samples/NAudioWpfDemo/LiveSamplerDemo/LiveSamplerDemoViewModel.cs:273— samples/NAudioWpfDemo/LiveSamplerDemo/LiveSamplerDemoViewModel.cs:273-277 | samples/NAudioWpfDemo/Utils/SamplerPlayback.cs:42-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeEffectsViewModel.cs:74— samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeEffectsViewModel.cs:74-78 | samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeEffectViewModel.cs:84-88 — 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) samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:110— samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:110-114 | samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:128-132 — 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.
Duplicated block (5 lines × 2) samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeEffectViewModel.cs:155— samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeEffectViewModel.cs:155-159 | samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs:118-122 — 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.
async void method: MidiInForm_Load samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:52— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnButtonMonitorClick samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:130— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnButtonRefreshDevicesClick samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:280— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnComboBoxBackendSelectedIndexChanged samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:285— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnCheckBoxMidiOutMessagesCheckedChanged samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:293— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnButtonSendSysexClick samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:355— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Start samples/NAudioWpfDemo/LiveSamplerDemo/LiveSamplerDemoViewModel.cs:159— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Play samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:141— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: RenderToWav samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:235— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: RenderToWav samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:279— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: RefreshMidi samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs:264— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
TooManyMethods: Vst3Plugin src/NAudio.Vst3/Vst3Plugin.cs— TooManyMethods — 1025 significant lines (blank, comment-only and punctuation-only lines excluded), 74 methods. The bar is 30 methods; this is 44 over it, 2.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MfByteStreamFromStream src/NAudio.Wasapi/MediaFoundation/MFByteStreamFromStream.cs— TooManyMethods — 238 significant lines (blank, comment-only and punctuation-only lines excluded), 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: AsioDevice src/NAudio.Asio/AsioDevice.cs— TooManyMethods — 473 significant lines (blank, comment-only and punctuation-only lines excluded), 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.
TooManyMethods: AcmInterop src/NAudio.WinMM/Compression/AcmInterop.cs— TooManyMethods — 112 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: WaveFileWriter src/NAudio.Core/Wave/WaveOutputs/WaveFileWriter.cs— TooManyMethods — 273 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AudioObject src/NAudio.MacOS/MacOS/CoreAudio/AudioObject.cs— TooManyMethods — 217 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AsioDriver src/NAudio.Asio/AsioDriver.cs— TooManyMethods — 149 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (16 lines × 2) src/NAudio.Vst3/Interop/Factory/IPluginFactory.cs:56— src/NAudio.Vst3/Interop/Factory/IPluginFactory.cs:56-71 | src/NAudio.Vst3/Interop/Factory/IPluginFactory.cs:86-101 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) src/NAudio.Core/FileFormats/Sfz/SfzMappedRegion.cs:439— src/NAudio.Core/FileFormats/Sfz/SfzMappedRegion.cs:439-454 | src/NAudio.Core/FileFormats/Sfz/SfzMappedRegion.cs:525-540 — 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 `src/NAudio.Core/FileFormats/Sfz/SfzMappedRegion.cs:439` 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. 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 (16 lines × 2) src/NAudio.Asio/AsioDriverExt.cs:486— src/NAudio.Asio/AsioDriverExt.cs:486-501 | src/NAudio.Asio/AsioDriverExt.cs:587-602 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) src/NAudio.Vst3/Vst3InstrumentSampleProvider.cs:116— src/NAudio.Vst3/Vst3InstrumentSampleProvider.cs:116-131 | src/NAudio.Vst3/Vst3MidiInstrument.cs:199-214 — 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 `src/NAudio.Vst3/Vst3InstrumentSampleProvider.cs:116` 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. 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.
Duplicated block (16 lines × 2) src/NAudio.Wasapi/WasapiRecorder.cs:294— src/NAudio.Wasapi/WasapiRecorder.cs:294-309 | src/NAudio.Wasapi/WasapiRecorder.cs:600-615 — 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, `src/NAudio.Wasapi/WasapiRecorder.cs:292` calls `InitializeAudioClient` and `src/NAudio.Wasapi/WasapiRecorder.cs:599` 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 (16 lines × 2) src/NAudio.WinMM/Mixer/CustomMixerControl.cs:12— src/NAudio.WinMM/Mixer/CustomMixerControl.cs:12-27 | src/NAudio.WinMM/Mixer/ListTextMixerControl.cs:12-29 — 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 (16 lines × 2) samples/AudioFileInspector/FileInspectors/SoundFontInspector.cs:28— samples/AudioFileInspector/FileInspectors/SoundFontInspector.cs:28-43 | samples/AudioFileInspector/FileInspectors/SoundFontInspector.cs:46-61 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/NAudio.Vst3/Vst3InstrumentSampleProvider.cs:47— src/NAudio.Vst3/Vst3InstrumentSampleProvider.cs:47-59 | src/NAudio.Vst3/Vst3MidiInstrument.cs:92-104 — 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 (13 lines × 2) src/NAudio.Wasapi/MediaFoundationEncoder.cs:294— src/NAudio.Wasapi/MediaFoundationEncoder.cs:294-306 | src/NAudio.Wasapi/MediaFoundationEncoder.cs:325-337 — 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 `src/NAudio.Wasapi/MediaFoundationEncoder.cs:294` 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) src/NAudio.WinForms/WaveInWindow.cs:139— src/NAudio.WinForms/WaveInWindow.cs:139-151 | src/NAudio.WinMM/WaveIn.cs:83-95 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/NAudio.WinForms/WaveInWindow.cs:153` calls `MemberNotNull`, `nameof` and `src/NAudio.WinMM/WaveIn.cs:97` 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 (13 lines × 2) src/NAudio.Asio/AsioAudioCapturedEventArgs.cs:71— src/NAudio.Asio/AsioAudioCapturedEventArgs.cs:71-83 | src/NAudio.Asio/AsioProcessBuffers.cs:85-97 — 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 `src/NAudio.Asio/AsioAudioCapturedEventArgs.cs:71` 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. 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 (13 lines × 2) src/NAudio.Core/Codecs/G722Codec.cs:411— src/NAudio.Core/Codecs/G722Codec.cs:411-423 | src/NAudio.Core/Codecs/G722Codec.cs:448-460 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/NAudio.Wasapi/WasapiOut.cs:207— src/NAudio.Wasapi/WasapiOut.cs:207-219 | src/NAudio.WinMM/WaveOut.cs:401-413 — 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.
Duplicated block (13 lines × 2) src/NAudio.Wasapi/WasapiOut.cs:310— src/NAudio.Wasapi/WasapiOut.cs:310-322 | src/NAudio.Wasapi/WasapiPlayer.cs:276-288 — 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.
Sync-over-async blocking — 6 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking samples/NAudioConsoleTest/Vst3/Tests/Vst3LiveSynthTest.cs:64— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking samples/NAudioConsoleTest/Vst3/Tests/Vst3LiveSynthTest.cs:88— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking samples/NAudioConsoleTest/Wasapi/Tests/WasapiPlayFileTest.cs:65— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking samples/NAudioConsoleTest/Wasapi/Tests/WasapiProcessLoopbackTest.cs:69— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecordToWavFileTest.cs:72— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking samples/NAudioDemo/AudioPlaybackDemo/WasapiPlayerPlugin.cs:29— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
MethodTooLong: MacUtils.ConstructSpeakersValue src/NAudio.MacOS/Utils/MacUtils.ChannelTranslations.cs:233— MethodTooLong — ConstructSpeakersValue runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WdlResampler.ResampleOut src/NAudio.Core/Dsp/WdlResampler.cs:251— MethodTooLong — ResampleOut runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× 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: Vst3Plugin.Initialise src/NAudio.Vst3/Vst3Plugin.cs:289— MethodTooLong — Initialise runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× 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: G722Codec.Decode src/NAudio.Core/Codecs/G722Codec.cs:156— MethodTooLong — Decode runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CoreAudioPlayer.Initialize src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:130— MethodTooLong — Initialize runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: DahdsrEnvelope.Advance src/NAudio.Core/Dsp/DahdsrEnvelope.cs:319— MethodTooLong — Advance runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×6
Owned disposable field is never released samples/MixDiff/MixDiffStream.cs:8— `MixDiffStream` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `offsetStream` itself (line 8), which makes that instance its own. But `offsetStream` is named in none of the methods the disposal search covered: `Dispose` (line 111) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`offsetStream?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:37— `DirectSoundOut` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `frameEventWaitHandle1` itself (line 37), which makes that instance its own. But `frameEventWaitHandle1` is named in none of the methods the disposal search covered: `Dispose` (line 461), `Stop` (line 175) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`frameEventWaitHandle1?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:38— `DirectSoundOut` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `frameEventWaitHandle2` itself (line 38), which makes that instance its own. But `frameEventWaitHandle2` is named in none of the methods the disposal search covered: `Dispose` (line 461), `Stop` (line 175) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`frameEventWaitHandle2?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:39— `DirectSoundOut` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `endEventWaitHandle` itself (line 39), which makes that instance its own. But `endEventWaitHandle` is named in none of the methods the disposal search covered: `Dispose` (line 461), `Stop` (line 175) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`endEventWaitHandle?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released src/NAudio.Wasapi/CoreAudioApi/AudioSessionControl.cs:27— `AudioSessionControl` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `audioMeterInformation` itself (line 27), which makes that instance its own. But `audioMeterInformation` is named in none of the methods the disposal search covered: `Dispose` (line 95), `QueryEventsInterface` (line 37) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`audioMeterInformation?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released src/NAudio.Wasapi/CoreAudioApi/AudioSessionControl.cs:28— `AudioSessionControl` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `simpleAudioVolume` itself (line 28), which makes that instance its own. But `simpleAudioVolume` is named in none of the methods the disposal search covered: `Dispose` (line 95), `QueryEventsInterface` (line 37) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`simpleAudioVolume?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Duplicated block (10 lines × 2) src/NAudio.Core/Codecs/G722Codec.cs:236— src/NAudio.Core/Codecs/G722Codec.cs:236-245 | src/NAudio.Core/Codecs/G722Codec.cs:269-278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) src/NAudio.MacOS/MacOS/CoreAudio/AudioClockDevice.cs:78— src/NAudio.MacOS/MacOS/CoreAudio/AudioClockDevice.cs:78-87 | src/NAudio.MacOS/MacOS/CoreAudio/AudioDevice.cs:272-281 — 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 `src/NAudio.MacOS/MacOS/CoreAudio/AudioClockDevice.cs:78` 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.
Duplicated block (10 lines × 2) src/NAudio.Core/Wave/SampleProviders/SampleToWaveProvider16.cs:24— src/NAudio.Core/Wave/SampleProviders/SampleToWaveProvider16.cs:24-33 | src/NAudio.Core/Wave/SampleProviders/SampleToWaveProvider24.cs:23-32 — 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 (10 lines × 2) samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:149— samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:149-158 | samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs:240-249 — 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 `samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:149` 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) samples/NAudioDemo/AsioRecordingDemo/AsioRecordingPanel.cs:243— samples/NAudioDemo/AsioRecordingDemo/AsioRecordingPanel.cs:243-252 | samples/NAudioDemo/AudioPlaybackDemo/AsioDeviceSettingsPanel.cs:31-40 — 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.
Swallowed exception (caught, then discarded) samples/NAudioConsoleTest/Shared/Testing/RecentFilesStore.cs:48— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) samples/NAudioDemo/NetworkChatDemo/AcmChatCodec.cs:87— `catch (MmException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) samples/NAudioDemo/NetworkChatDemo/NetworkChatPanel.cs:93— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) samples/NAudioDemo/RecordingDemo/RecordingPanel.cs:186— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) samples/NAudioDemo/VolumeMixerDemo/VolumeMixerPanel.cs:84— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Duplicated block (14 lines × 2) src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:692— src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:692-705 | src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:752-765 — 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 `src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:692` 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 (14 lines × 2) src/NAudio.Core/Effects/ChorusEffect.cs:26— src/NAudio.Core/Effects/ChorusEffect.cs:26-39 | src/NAudio.Core/Effects/FlangerEffect.cs:27-40 — before extracting anything, compare `src/NAudio.Core/Effects/ChorusEffect.cs` and `src/NAudio.Core/Effects/FlangerEffect.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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. 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 (14 lines × 2) src/NAudio.WinForms/WaveOutWindow.cs:199— src/NAudio.WinForms/WaveOutWindow.cs:199-212 | src/NAudio.WinMM/WaveOut.cs:239-252 — 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.
Duplicated block (14 lines × 2) samples/NAudioWpfDemo/Vst3HostDemo/Vst3HostDemoViewModel.cs:338— samples/NAudioWpfDemo/Vst3HostDemo/Vst3HostDemoViewModel.cs:338-351 | samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeEffectViewModel.cs:395-408 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) src/NAudio.Dmo/Dmo/MediaObject.cs:74— src/NAudio.Dmo/Dmo/MediaObject.cs:74-85 | src/NAudio.Dmo/Dmo/MediaObject.cs:97-108 — 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 `src/NAudio.Dmo/Dmo/MediaObject.cs:74` 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. 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) src/NAudio.Vst3/Vst3Plugin.cs:730— src/NAudio.Vst3/Vst3Plugin.cs:730-741 | src/NAudio.Vst3/Vst3Plugin.cs:1188-1199 — 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 `src/NAudio.Vst3/Vst3Plugin.cs:730` 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) src/NAudio.Dmo/Interop/ComActivation.cs:49— src/NAudio.Dmo/Interop/ComActivation.cs:49-60 | src/NAudio.Wasapi/CoreAudioApi/ComActivation.cs:60-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:262— samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:262-273 | samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:312-323 — 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 `samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:262` 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 × 3) src/NAudio.Core/Dsp/BiQuadFilter.cs:361— src/NAudio.Core/Dsp/BiQuadFilter.cs:361-366 | src/NAudio.Core/Dsp/BiQuadFilter.cs:386-391 | src/NAudio.Core/Dsp/BiQuadFilter.cs:436-441 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) src/NAudio.Core/Wave/SampleChunkConverters/Mono24SampleChunkConverter.cs:20— src/NAudio.Core/Wave/SampleChunkConverters/Mono24SampleChunkConverter.cs:20-25 | src/NAudio.Core/Wave/SampleChunkConverters/Stereo24SampleChunkConverter.cs:21-26 | src/NAudio.Core/Wave/SampleChunkConverters/Stereo8SampleChunkConverter.cs:20-25 — 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 all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) src/NAudio.Core/Wave/SampleChunkConverters/MonoFloatSampleChunkConverter.cs:20— src/NAudio.Core/Wave/SampleChunkConverters/MonoFloatSampleChunkConverter.cs:20-25 | src/NAudio.Core/Wave/SampleChunkConverters/Stereo16SampleChunkConverter.cs:21-26 | src/NAudio.Core/Wave/SampleChunkConverters/StereoFloatSampleChunkConverter.cs:20-25 — 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 all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:335— samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:335-340 | samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3PluginSlotViewModel.cs:124-130 | samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs:217-222 — 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. 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.
Test cannot fail: MalformedAdtlSubChunkSizeDoesNotLoop tests/NAudio.Core.Tests/WaveStreams/CueListInterpreterTests.cs:261— This test's act runs inside `Run` at tests/NAudioAsioFakeDriverTest/FakeAsioDriverChecks.cs:211, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 5 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: Rf64WithNegativeDataChunkLengthThrowsInsteadOfLooping tests/NAudio.Core.Tests/WaveStreams/WaveFileChunkReaderTests.cs:210— This test's act runs inside `Run` at tests/NAudioAsioFakeDriverTest/FakeAsioDriverChecks.cs:211, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 4 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: Rf64WithNegativeRiffSizeThrows tests/NAudio.Core.Tests/WaveStreams/WaveFileChunkReaderTests.cs:222— This test's act runs inside `Run` at tests/NAudioAsioFakeDriverTest/FakeAsioDriverChecks.cs:211, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 4 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
ClassTooLong: MacUtils src/NAudio.MacOS/Utils/MacUtils.cs— ClassTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods, declared across 3 files: Utils/MacUtils.cs (10), Utils/MacUtils.ChannelTranslations.cs (6), Utils/MacUtils.ASBDTranslations.cs (2). The bar is 400 significant lines; this is 118 over it, 1.30× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: SamplerVoice src/NAudio.Sampler/SamplerVoice.cs— ClassTooLong — 431 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 31 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WasapiPlayer src/NAudio.Wasapi/WasapiPlayer.cs— ClassTooLong — 408 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 8 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (7 lines × 2) src/NAudio.Core/Dsp/BiQuadFilter.cs:479— src/NAudio.Core/Dsp/BiQuadFilter.cs:479-485 | src/NAudio.Core/Dsp/BiQuadFilter.cs:506-512 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/NAudio.MacOS/MacOS/AudioToolbox/AudioFileLibraryInformation.cs:27— src/NAudio.MacOS/MacOS/AudioToolbox/AudioFileLibraryInformation.cs:27-33 | src/NAudio.MacOS/MacOS/AudioToolbox/AudioFileLibraryInformation.cs:55-61 — 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 `src/NAudio.MacOS/MacOS/AudioToolbox/AudioFileLibraryInformation.cs:27` 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) samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:227— samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:227-233 | samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:271-277 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) src/NAudio.Core/Wave/WaveStreams/AiffFileReader.cs:217— src/NAudio.Core/Wave/WaveStreams/AiffFileReader.cs:217-224 | src/NAudio.Core/Wave/WaveStreams/WaveFileReader.cs:150-157 — 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 (8 lines × 2) src/NAudio.Vst3/Vst3Module.cs:247— src/NAudio.Vst3/Vst3Module.cs:247-254 | src/NAudio.Vst3/Vst3Plugin.cs:829-836 — 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 (8 lines × 2) samples/NAudioWpfDemo/Vst3HostDemo/Vst3HostDemoViewModel.cs:382— samples/NAudioWpfDemo/Vst3HostDemo/Vst3HostDemoViewModel.cs:382-389 | samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeEffectViewModel.cs:422-429 — 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.
Low cohesion: SamplerRegion (LCOM4 8) src/NAudio.Sampler/SamplerRegion.cs:35— SamplerRegion's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AsioRecordingPanel (LCOM4 7) samples/NAudioDemo/AsioRecordingDemo/AsioRecordingPanel.cs:10— AsioRecordingPanel's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AudioFileInspectorForm (LCOM4 5) samples/AudioFileInspector/AudioFileInspectorForm.cs:11— AudioFileInspectorForm's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplicated block (22 lines × 2) src/NAudio.Vst3/Hosting/Vst3HostMessage.cs:58— src/NAudio.Vst3/Hosting/Vst3HostMessage.cs:58-79 | src/NAudio.Vst3/Hosting/Vst3MemoryStream.cs:154-175 — 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 (22 lines × 2) samples/MidiFileConverter/LogBox.cs:17— samples/MidiFileConverter/LogBox.cs:17-38 | samples/NAudioDemo/MidiInDemo/LogBox.cs:17-38 — before extracting anything, compare `samples/MidiFileConverter/LogBox.cs` and `samples/NAudioDemo/MidiInDemo/LogBox.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11–12 lines × 2) src/NAudio.Asio/AsioSampleConvertor.cs:471— src/NAudio.Asio/AsioSampleConvertor.cs:471-481 | src/NAudio.Asio/AsioSampleConvertor.cs:525-536 — 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 `src/NAudio.Asio/AsioSampleConvertor.cs:471` 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) src/NAudio.Core/Dsp/BiQuadFilter.cs:156— src/NAudio.Core/Dsp/BiQuadFilter.cs:156-167 | src/NAudio.Core/Dsp/BiQuadFilter.cs:185-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/NAudio.WinForms/WaveOutWindow.cs:264— src/NAudio.WinForms/WaveOutWindow.cs:264-274 | src/NAudio.WinMM/WaveOut.cs:307-317 — 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.
Duplicated block (11 lines × 2) src/NAudio.Wasapi/WasapiCapture.cs:366— src/NAudio.Wasapi/WasapiCapture.cs:366-376 | src/NAudio.WinForms/WaveInWindow.cs:291-301 — 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.
Duplicated block (9 lines × 2) src/NAudio.Vst3/Vst3Plugin.cs:729— src/NAudio.Vst3/Vst3Plugin.cs:729-737 | src/NAudio.Vst3/Vst3Plugin.cs:1153-1161 — 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 `src/NAudio.Vst3/Vst3Plugin.cs:729` 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) src/NAudio.MacOS/MacOS/CoreAudio/AudioObject.cs:421— src/NAudio.MacOS/MacOS/CoreAudio/AudioObject.cs:421-429 | src/NAudio.MacOS/MacOS/CoreAudio/AudioObjectsConstructors.cs:32-40 — 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 (7 lines × 3) src/NAudio.Core/Dsp/BiQuadFilter.cs:155— src/NAudio.Core/Dsp/BiQuadFilter.cs:155-162 | src/NAudio.Core/Dsp/BiQuadFilter.cs:184-190 | src/NAudio.Core/Dsp/BiQuadFilter.cs:306-313 — 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 `src/NAudio.Core/Dsp/BiQuadFilter.cs:155` 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 (7 lines × 3) src/NAudio.Core/Dsp/BiQuadFilter.cs:213— src/NAudio.Core/Dsp/BiQuadFilter.cs:213-219 | src/NAudio.Core/Dsp/BiQuadFilter.cs:231-237 | src/NAudio.Core/Dsp/BiQuadFilter.cs:248-254 — 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 `src/NAudio.Core/Dsp/BiQuadFilter.cs:213` 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 (6 lines × 2) src/NAudio.Core/Effects/ChorusEffect.cs:58— src/NAudio.Core/Effects/ChorusEffect.cs:58-63 | src/NAudio.Core/Effects/FlangerEffect.cs:59-64 — before extracting anything, compare `src/NAudio.Core/Effects/ChorusEffect.cs` and `src/NAudio.Core/Effects/FlangerEffect.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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. 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 (6 lines × 2) src/NAudio.WinForms/WaveInWindow.cs:84— src/NAudio.WinForms/WaveInWindow.cs:84-89 | src/NAudio.WinMM/WaveIn.cs:59-64 — 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. 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.
Off the main sequence: NAudio.Core src/NAudio.Core/NAudio.Core.csproj:1— NAudio.Core: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: NAudio.Midi(net9.0) src/NAudio.Midi/NAudio.Midi.csproj:1— NAudio.Midi(net9.0): abstractness 0.09, instability 0.20, distance 0.71 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
IC1 · Incompleteness & stubs· Empty method body · ×2
Empty method body — does nothing with its inputs src/NAudio.MacOS/MacOS/CoreAudio/PropertyListenerHandle.cs:77— `DummyEventHandler` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs src/NAudio.WinMM/Midi/MidiOut.cs:144— `Callback` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Blocking `SingleLinkedCaptureBufferQueue.Dequeue` inside an `async` method src/NAudio.MacOS/Wave/CoreAudioRecorder.BaseAPI.cs:383— `SingleLinkedCaptureBufferQueue.Dequeue` is a synchronous helper that blocks (`SemaphoreSlim.Wait`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll).
Blocking `SingleLinkedCaptureBufferQueue.Dequeue` inside an `async` method src/NAudio.MacOS/Wave/CoreAudioRecorder.BaseAPI.cs:401— `SingleLinkedCaptureBufferQueue.Dequeue` is a synchronous helper that blocks (`SemaphoreSlim.Wait`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll).
X20 · Mistyped argument guard· Argument guard throws the exception its own condition disproves · ×2
Argument guard throws the exception its own condition disproves src/NAudio.Core/FileFormats/Mp3/Id3v2Tag.cs:69— The guard on line 67 rejects `key` and line 69 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(key)` is true of a value that is NOT null: it is satisfied by an EMPTY `key`, and on that path `key` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/NAudio.Core/FileFormats/Mp3/Id3v2Tag.cs:74— The guard on line 72 rejects `value` and line 74 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(value)` is true of a value that is NOT null: it is satisfied by an EMPTY `value`, and on that path `value` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×2
Symbol treated as nullable, then dereferenced unguarded samples/MixDiff/MixDiffForm.cs:72— This method contradicts itself about `buttonInfo`: line 71 assigns it with `as MixdownInfo`, which hands back null rather than throwing when the value is not a `MixdownInfo`, but line 72 then dereferences it directly as `buttonInfo.Stream` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `buttonInfo` once before the first use and handle the null case, or cast with `(MixdownInfo)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded samples/MixDiff/MixDiffForm.cs:108— This method contradicts itself about `button`: line 107 assigns it with `as Button`, which hands back null rather than throwing when the value is not a `Button`, but line 108 then dereferences it directly as `button.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `button` once before the first use and handle the null case, or cast with `(Button)` so the failure is reported where it happens — rather than leaving the two readings side by side.
MacUtils.ConstructSpeakersValue (cyclomatic 99) src/NAudio.MacOS/Utils/MacUtils.ChannelTranslations.cs:233— MacUtils.ConstructSpeakersValue has cyclomatic complexity 99 (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.
MidiConverter.ConvertMidi (cyclomatic 54) samples/MidiFileConverter/MidiConverter.cs:157— MidiConverter.ConvertMidi has cyclomatic complexity 54 (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.
WdlResampler.ResampleOut (cyclomatic 53) src/NAudio.Core/Dsp/WdlResampler.cs:251— WdlResampler.ResampleOut has cyclomatic complexity 53 (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.
Vst3Plugin.Initialise (cyclomatic 35) src/NAudio.Vst3/Vst3Plugin.cs:289— Vst3Plugin.Initialise has cyclomatic complexity 35 (threshold 15). Of this number, 33 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
CoreAudioPlayer.Initialize (cyclomatic 33) src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:130— CoreAudioPlayer.Initialize 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.
AsioDuplexPassthroughTest.Run (cyclomatic 31) samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs:33— AsioDuplexPassthroughTest.Run has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 belong to one function literal 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.
DahdsrEnvelope.Advance (cyclomatic 31) src/NAudio.Core/Dsp/DahdsrEnvelope.cs:319— DahdsrEnvelope.Advance has cyclomatic complexity 31 (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.
AsioLegacyDuplexPassthroughTest.Run (cyclomatic 30) samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:39— AsioLegacyDuplexPassthroughTest.Run has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to one function literal 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.
AsioSampleConvertor.SelectSampleConvertor (cyclomatic 28) src/NAudio.Asio/AsioSampleConvertor.cs:19— AsioSampleConvertor.SelectSampleConvertor 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.
MidiFile.MidiFile.ctor (cyclomatic 28) src/NAudio.Midi/Midi/MidiFile.cs:55— MidiFile.MidiFile.ctor 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.
WasapiPlayFileTest.Run (cyclomatic 27) samples/NAudioConsoleTest/Wasapi/Tests/WasapiPlayFileTest.cs:32— WasapiPlayFileTest.Run 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.
SamplerVoice.RenderSpan (cyclomatic 26) src/NAudio.Sampler/SamplerVoice.cs:532— SamplerVoice.RenderSpan 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.
Vst3Plugin.DisposeCore (cyclomatic 26) src/NAudio.Vst3/Vst3Plugin.cs:2153— Vst3Plugin.DisposeCore 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.
AsioValidateSamplePositionTest.Run (cyclomatic 25) samples/NAudioConsoleTest/Asio/Tests/AsioValidateSamplePositionTest.cs:29— AsioValidateSamplePositionTest.Run 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.
Vst3LiveSynthTest.Run (cyclomatic 24) samples/NAudioConsoleTest/Vst3/Tests/Vst3LiveSynthTest.cs:38— Vst3LiveSynthTest.Run has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 belong to one function literal 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.
SfzMappedRegion.Map (cyclomatic 24) src/NAudio.Core/FileFormats/Sfz/SfzMappedRegion.cs:291— SfzMappedRegion.Map has cyclomatic complexity 24 (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.
AsioLegacyDuplexPassthroughTest.NativePassthroughChannel (cyclomatic 23) samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:166— AsioLegacyDuplexPassthroughTest.NativePassthroughChannel 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.
Vst3ListPluginsTest.Run (cyclomatic 23) samples/NAudioConsoleTest/Vst3/Tests/Vst3ListPluginsTest.cs:26— Vst3ListPluginsTest.Run 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.
WasapiVolumeCallbackStressTest.Run (cyclomatic 23) samples/NAudioConsoleTest/Wasapi/Tests/WasapiVolumeCallbackStressTest.cs:40— WasapiVolumeCallbackStressTest.Run 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.
ExtendedAudioFileServicesWriter.SelectBestIDForFileType (cyclomatic 23) src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesWriter.cs:50— ExtendedAudioFileServicesWriter.SelectBestIDForFileType has cyclomatic complexity 23 (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.
AudioControl.ComputeKind (cyclomatic 23) src/NAudio.MacOS/MacOS/CoreAudio/AudioControl.cs:19— AudioControl.ComputeKind has cyclomatic complexity 23 (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.
Vst3Plugin.Process (cyclomatic 23) src/NAudio.Vst3/Vst3Plugin.cs:1275— Vst3Plugin.Process has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AsioRecordToWavTest.Run (cyclomatic 22) samples/NAudioConsoleTest/Asio/Tests/AsioRecordToWavTest.cs:26— AsioRecordToWavTest.Run has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
G722Codec.Decode (cyclomatic 22) src/NAudio.Core/Codecs/G722Codec.cs:156— G722Codec.Decode has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
G722Codec.Encode (cyclomatic 22) src/NAudio.Core/Codecs/G722Codec.cs:326— G722Codec.Encode has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AudioObjectsConstructors.ConstructAudioControlInternal (cyclomatic 22) src/NAudio.MacOS/MacOS/CoreAudio/AudioObjectsConstructors.cs:58— AudioObjectsConstructors.ConstructAudioControlInternal has cyclomatic complexity 22 (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.
WasapiPlayer.GetSupportedExclusiveFormat (cyclomatic 22) src/NAudio.Wasapi/WasapiPlayer.cs:390— WasapiPlayer.GetSupportedExclusiveFormat 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.
CoreAudioRecorder.Initialize (cyclomatic 21) src/NAudio.MacOS/Wave/CoreAudioRecorder.InitAPI.cs:99— CoreAudioRecorder.Initialize 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.
AsioShowChannelLevelsTest.Run (cyclomatic 20) samples/NAudioConsoleTest/Asio/Tests/AsioShowChannelLevelsTest.cs:33— AsioShowChannelLevelsTest.Run has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal 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.
WasapiRecordToWavFileTest.Run (cyclomatic 20) samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecordToWavFileTest.cs:27— WasapiRecordToWavFileTest.Run has cyclomatic complexity 20 (threshold 15). 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, 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.
DahdsrEnvelope.Process (cyclomatic 20) src/NAudio.Core/Dsp/DahdsrEnvelope.cs:210— DahdsrEnvelope.Process 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.
Mp3Frame.IsValidHeader (cyclomatic 20) src/NAudio.Core/FileFormats/Mp3/Mp3Frame.cs:182— Mp3Frame.IsValidHeader 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.
WaveFileChunkReader.ReadWaveHeader (cyclomatic 20) src/NAudio.Core/Wave/WaveStreams/WaveFileChunkReader.cs:42— WaveFileChunkReader.ReadWaveHeader 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.
WasapiProcessLoopbackTest.Run (cyclomatic 19) samples/NAudioConsoleTest/Wasapi/Tests/WasapiProcessLoopbackTest.cs:39— WasapiProcessLoopbackTest.Run has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
WasapiRecorderViewModel.PeakOf (cyclomatic 19) samples/NAudioWpfDemo/WasapiRecorderDemo/WasapiRecorderViewModel.cs:504— WasapiRecorderViewModel.PeakOf 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.
WdlResampler.ResamplePrepare (cyclomatic 19) src/NAudio.Core/Dsp/WdlResampler.cs:160— WdlResampler.ResamplePrepare 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.
AudioFileException.ThrowIfError (cyclomatic 19) src/NAudio.MacOS/MacOS/AudioToolbox/AudioFileException.cs:30— AudioFileException.ThrowIfError 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.
WasapiOut.PlayThread (cyclomatic 19) src/NAudio.Wasapi/WasapiOut.cs:97— WasapiOut.PlayThread 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.
WasapiRecordAndPlaybackTest.Run (cyclomatic 18) samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecordAndPlaybackTest.cs:31— WasapiRecordAndPlaybackTest.Run has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal 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.
Vst3RealtimeAudioEngine.OnBuffer (cyclomatic 18) samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeAudioEngine.cs:170— Vst3RealtimeAudioEngine.OnBuffer has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XingHeader.LoadXingHeader (cyclomatic 18) src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:46— XingHeader.LoadXingHeader has cyclomatic complexity 18 (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.
SamplerEngine.NoteOn (cyclomatic 18) src/NAudio.Sampler/SamplerEngine.cs:202— SamplerEngine.NoteOn has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LimiterEffect.ProcessBlock (cyclomatic 17) src/NAudio.Core/Effects/LimiterEffect.cs:147— LimiterEffect.ProcessBlock 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.
OffsetSampleProvider.Read (cyclomatic 17) src/NAudio.Core/Wave/SampleProviders/OffsetSampleProvider.cs:172— OffsetSampleProvider.Read 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.
SoundFilePlayFileTest.Run (cyclomatic 16) samples/NAudioConsoleTest/SoundFile/Tests/SoundFilePlayFileTest.cs:29— SoundFilePlayFileTest.Run 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.
WinMmPlayFileTest.Run (cyclomatic 16) samples/NAudioConsoleTest/WinMM/Tests/WinMmPlayFileTest.cs:29— WinMmPlayFileTest.Run 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.
G722Codec.Block4 (cyclomatic 16) src/NAudio.Core/Codecs/G722Codec.cs:43— G722Codec.Block4 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.
InterpolatingSampleReader.ReadContiguous (cyclomatic 16) src/NAudio.Core/Dsp/InterpolatingSampleReader.cs:276— InterpolatingSampleReader.ReadContiguous has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
SmbPitchShifter.PitchShift (cyclomatic 16) src/NAudio.Core/Dsp/SmbPitchShifter.cs:92— SmbPitchShifter.PitchShift has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AiffFileReader.ReadAiffHeader (cyclomatic 16) src/NAudio.Core/Wave/WaveStreams/AiffFileReader.cs:66— AiffFileReader.ReadAiffHeader 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.
CueList.CueList.ctor (cyclomatic 16) src/NAudio.Core/Wave/WaveStreams/CueList.cs:188— CueList.CueList.ctor 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.
CoreAudioPlayer.TryConstructingExclusiveModeStream (cyclomatic 16) src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:381— CoreAudioPlayer.TryConstructingExclusiveModeStream has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
SfzRegionProjector.Project (cyclomatic 16) src/NAudio.Sampler/SfzRegionProjector.cs:34— SfzRegionProjector.Project 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.
WasapiPlayer.PlayThread (cyclomatic 16) src/NAudio.Wasapi/WasapiPlayer.cs:752— WasapiPlayer.PlayThread 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.
D10 · Test Quality· Fixed-sleep synchronisation · ×1
Fixed-sleep synchronisation: ConcurrentControlAndDisposeIsSafe tests/NAudio.Alsa.Tests/AlsaPlaybackTests.cs:74— This test starts a background task and then orders itself against it with `Thread.Sleep(150)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
BarePragmaDisable src/NAudio.Dmo/Dmo/MediaParamInfo.cs:11— #pragma warning disable 0649 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
WdlResampler.ResampleOut (cognitive 132) src/NAudio.Core/Dsp/WdlResampler.cs:251— WdlResampler.ResampleOut has cognitive complexity 132 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MidiConverter.ConvertMidi (cognitive 113) samples/MidiFileConverter/MidiConverter.cs:157— MidiConverter.ConvertMidi has cognitive complexity 113 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DahdsrEnvelope.Advance (cognitive 95) src/NAudio.Core/Dsp/DahdsrEnvelope.cs:319— DahdsrEnvelope.Advance has cognitive complexity 95 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MacUtils.ConstructSpeakersValue (cognitive 82) src/NAudio.MacOS/Utils/MacUtils.ChannelTranslations.cs:233— MacUtils.ConstructSpeakersValue has cognitive complexity 82 (threshold 15). 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.
MidiFile.MidiFile.ctor (cognitive 65) src/NAudio.Midi/Midi/MidiFile.cs:55— MidiFile.MidiFile.ctor has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SamplerVoice.RenderSpan (cognitive 61) src/NAudio.Sampler/SamplerVoice.cs:532— SamplerVoice.RenderSpan has cognitive complexity 61 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
G722Codec.Encode (cognitive 55) src/NAudio.Core/Codecs/G722Codec.cs:326— G722Codec.Encode has cognitive complexity 55 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsioDuplexPassthroughTest.Run (cognitive 49) samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs:33— AsioDuplexPassthroughTest.Run has cognitive complexity 49 (threshold 15). Of this number, 38 points are the body's own statements and 11 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.
Vst3ListPluginsTest.Run (cognitive 48) samples/NAudioConsoleTest/Vst3/Tests/Vst3ListPluginsTest.cs:26— Vst3ListPluginsTest.Run has cognitive complexity 48 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsioSampleConvertor.SelectSampleConvertor (cognitive 48) src/NAudio.Asio/AsioSampleConvertor.cs:19— AsioSampleConvertor.SelectSampleConvertor has cognitive complexity 48 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsioLegacyDuplexPassthroughTest.NativePassthroughChannel (cognitive 45) samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:166— AsioLegacyDuplexPassthroughTest.NativePassthroughChannel has cognitive complexity 45 (threshold 15). 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.
G722Codec.Decode (cognitive 45) src/NAudio.Core/Codecs/G722Codec.cs:156— G722Codec.Decode has cognitive complexity 45 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CoreAudioPlayer.TryConstructingExclusiveModeStream (cognitive 45) src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:381— CoreAudioPlayer.TryConstructingExclusiveModeStream has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
WaveFileChunkReader.ReadWaveHeader (cognitive 44) src/NAudio.Core/Wave/WaveStreams/WaveFileChunkReader.cs:42— WaveFileChunkReader.ReadWaveHeader has cognitive complexity 44 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CoreAudioPlayer.Initialize (cognitive 44) src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:130— CoreAudioPlayer.Initialize has cognitive complexity 44 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SmbPitchShifter.PitchShift (cognitive 43) src/NAudio.Core/Dsp/SmbPitchShifter.cs:92— SmbPitchShifter.PitchShift has cognitive complexity 43 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
LimiterEffect.ProcessBlock (cognitive 43) src/NAudio.Core/Effects/LimiterEffect.cs:147— LimiterEffect.ProcessBlock has cognitive complexity 43 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsioLegacyDuplexPassthroughTest.Run (cognitive 42) samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:39— AsioLegacyDuplexPassthroughTest.Run has cognitive complexity 42 (threshold 15). Of this number, 39 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.
DahdsrEnvelope.Process (cognitive 42) src/NAudio.Core/Dsp/DahdsrEnvelope.cs:210— DahdsrEnvelope.Process has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DirectSoundOut.PlaybackThreadFunc (cognitive 42) src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:495— DirectSoundOut.PlaybackThreadFunc has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Vst3Plugin.Initialise (cognitive 37) src/NAudio.Vst3/Vst3Plugin.cs:289— Vst3Plugin.Initialise has cognitive complexity 37 (threshold 15). Of this number, 34 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
WasapiOut.PlayThread (cognitive 37) src/NAudio.Wasapi/WasapiOut.cs:97— WasapiOut.PlayThread has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasapiPlayFileTest.Run (cognitive 36) samples/NAudioConsoleTest/Wasapi/Tests/WasapiPlayFileTest.cs:32— WasapiPlayFileTest.Run has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Mp3Frame.IsValidHeader (cognitive 36) src/NAudio.Core/FileFormats/Mp3/Mp3Frame.cs:182— Mp3Frame.IsValidHeader has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsioValidateSamplePositionTest.Run (cognitive 33) samples/NAudioConsoleTest/Asio/Tests/AsioValidateSamplePositionTest.cs:29— AsioValidateSamplePositionTest.Run has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasapiVolumeCallbackStressTest.Run (cognitive 32) samples/NAudioConsoleTest/Wasapi/Tests/WasapiVolumeCallbackStressTest.cs:40— WasapiVolumeCallbackStressTest.Run has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasapiRecorderViewModel.PeakOf (cognitive 32) samples/NAudioWpfDemo/WasapiRecorderDemo/WasapiRecorderViewModel.cs:504— WasapiRecorderViewModel.PeakOf has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Vst3Plugin.DisposeCore (cognitive 32) src/NAudio.Vst3/Vst3Plugin.cs:2153— Vst3Plugin.DisposeCore has cognitive complexity 32 (threshold 15). 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.
AsioShowChannelLevelsTest.Run (cognitive 31) samples/NAudioConsoleTest/Asio/Tests/AsioShowChannelLevelsTest.cs:33— AsioShowChannelLevelsTest.Run has cognitive complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 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.
WasapiPlayer.GetSupportedExclusiveFormat (cognitive 31) src/NAudio.Wasapi/WasapiPlayer.cs:390— WasapiPlayer.GetSupportedExclusiveFormat has cognitive complexity 31 (threshold 15). 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.
Vst3Plugin.Process (cognitive 30) src/NAudio.Vst3/Vst3Plugin.cs:1275— Vst3Plugin.Process has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
WasapiPlayer.PlayThread (cognitive 30) src/NAudio.Wasapi/WasapiPlayer.cs:752— WasapiPlayer.PlayThread has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AiffFileReader.ReadAiffHeader (cognitive 29) src/NAudio.Core/Wave/WaveStreams/AiffFileReader.cs:66— AiffFileReader.ReadAiffHeader has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchRunner.RenderMarkdown (cognitive 28) samples/NAudioConsoleTest/Shared/Testing/BatchRunner.cs:229— BatchRunner.RenderMarkdown has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasapiExclusiveDetailedScanTest.Run (cognitive 28) samples/NAudioConsoleTest/Wasapi/Tests/WasapiExclusiveDetailedScanTest.cs:21— WasapiExclusiveDetailedScanTest.Run has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Vst3RealtimeAudioEngine.OnBuffer (cognitive 28) samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeAudioEngine.cs:170— Vst3RealtimeAudioEngine.OnBuffer has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OffsetSampleProvider.Read (cognitive 28) src/NAudio.Core/Wave/SampleProviders/OffsetSampleProvider.cs:172— OffsetSampleProvider.Read has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SamplerEngine.NoteOn (cognitive 28) src/NAudio.Sampler/SamplerEngine.cs:202— SamplerEngine.NoteOn has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtendedAudioFileServicesReader.InitReaderInternal (cognitive 27) src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesReader.cs:44— ExtendedAudioFileServicesReader.InitReaderInternal has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CoreAudioRecorder.Initialize (cognitive 27) src/NAudio.MacOS/Wave/CoreAudioRecorder.InitAPI.cs:99— CoreAudioRecorder.Initialize has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsioRecordToWavTest.Run (cognitive 26) samples/NAudioConsoleTest/Asio/Tests/AsioRecordToWavTest.cs:26— AsioRecordToWavTest.Run has cognitive complexity 26 (threshold 15). Of this number, 22 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SoundFilePlayFileTest.Run (cognitive 26) samples/NAudioConsoleTest/SoundFile/Tests/SoundFilePlayFileTest.cs:29— SoundFilePlayFileTest.Run has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WinMmPlayFileTest.Run (cognitive 26) samples/NAudioConsoleTest/WinMM/Tests/WinMmPlayFileTest.cs:29— WinMmPlayFileTest.Run has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsioAudioAvailableEventArgs.GetAsInterleavedSamples (cognitive 26) src/NAudio.Asio/AsioAudioAvailableEventArgs.cs:57— AsioAudioAvailableEventArgs.GetAsInterleavedSamples has cognitive complexity 26 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
SfzMappedRegion.Map (cognitive 26) src/NAudio.Core/FileFormats/Sfz/SfzMappedRegion.cs:291— SfzMappedRegion.Map has cognitive complexity 26 (threshold 15). 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.
DiagnosticsRenderer.ToMarkdown (cognitive 25) samples/NAudioConsoleTest/Shared/Testing/DiagnosticsRenderer.cs:21— DiagnosticsRenderer.ToMarkdown has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Vst3LiveSynthTest.Run (cognitive 25) samples/NAudioConsoleTest/Vst3/Tests/Vst3LiveSynthTest.cs:38— Vst3LiveSynthTest.Run has cognitive complexity 25 (threshold 15). Of this number, 24 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.
WaveformControl.Redraw (cognitive 25) samples/NAudioWpfDemo/SampleEditorDemo/WaveformControl.xaml.cs:112— WaveformControl.Redraw has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultibandCompressorEffect.ProcessBlock (cognitive 25) src/NAudio.Core/Effects/MultibandCompressorEffect.cs:80— MultibandCompressorEffect.ProcessBlock has cognitive complexity 25 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CueList.CueList.ctor (cognitive 25) src/NAudio.Core/Wave/WaveStreams/CueList.cs:188— CueList.CueList.ctor has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Mp3FileReaderBase.Read (cognitive 25) src/NAudio.Core/Wave/WaveStreams/Mp3FileReaderBase.cs:516— Mp3FileReaderBase.Read has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AudioFileFormatFinder.FindFormat (cognitive 25) src/NAudio.Wasapi/MediaFoundation/FileFormatDiscovery/AudioFileFormatFinder.cs:135— AudioFileFormatFinder.FindFormat has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
WasapiOut.Init (cognitive 25) src/NAudio.Wasapi/WasapiOut.cs:381— WasapiOut.Init has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasapiRecordToWavFileTest.Run (cognitive 24) samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecordToWavFileTest.cs:27— WasapiRecordToWavFileTest.Run has cognitive complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WaveIn.DoRecording (cognitive 24) src/NAudio.WinMM/WaveIn.cs:156— WaveIn.DoRecording has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealtimeAudioEngine.OnBuffer (cognitive 23) samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:166— RealtimeAudioEngine.OnBuffer has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AlsaOut.PlaybackLoop (cognitive 23) src/NAudio.Alsa/AlsaOut.cs:241— AlsaOut.PlaybackLoop has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CompressorEffect.ProcessBlock (cognitive 23) src/NAudio.Core/Effects/CompressorEffect.cs:114— CompressorEffect.ProcessBlock has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AudioControl.ComputeKind (cognitive 23) src/NAudio.MacOS/MacOS/CoreAudio/AudioControl.cs:19— AudioControl.ComputeKind has cognitive complexity 23 (threshold 15). 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.
FdnReverbEffect.ProcessBlock (cognitive 22) src/NAudio.Core/Effects/FdnReverbEffect.cs:92— FdnReverbEffect.ProcessBlock has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GateEffect.ProcessBlock (cognitive 22) src/NAudio.Core/Effects/GateEffect.cs:87— GateEffect.ProcessBlock has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WaveFileWriter.WriteSamples (cognitive 22) src/NAudio.Core/Wave/WaveOutputs/WaveFileWriter.cs:489— WaveFileWriter.WriteSamples has cognitive complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
InfoListInterpreter.Interpret (cognitive 22) src/NAudio.Core/Wave/WaveStreams/InfoMetadata.cs:155— InfoListInterpreter.Interpret has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasapiProcessLoopbackTest.Run (cognitive 21) samples/NAudioConsoleTest/Wasapi/Tests/WasapiProcessLoopbackTest.cs:39— WasapiProcessLoopbackTest.Run has cognitive complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RecordingPanel.OnDevicesChanged (cognitive 21) samples/NAudioDemo/RecordingDemo/RecordingPanel.cs:381— RecordingPanel.OnDevicesChanged has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BitCrusherEffect.ProcessBlock (cognitive 21) src/NAudio.Core/Effects/BitCrusherEffect.cs:83— BitCrusherEffect.ProcessBlock has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiplexingSampleProvider.Read (cognitive 21) src/NAudio.Core/Wave/SampleProviders/MultiplexingSampleProvider.cs:84— MultiplexingSampleProvider.Read has cognitive complexity 21 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
SignalGenerator.Read (cognitive 21) src/NAudio.Core/Wave/SampleProviders/SignalGenerator.cs:116— SignalGenerator.Read has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiplexingWaveProvider.Read (cognitive 21) src/NAudio.Core/Wave/WaveProviders/MultiplexingWaveProvider.cs:105— MultiplexingWaveProvider.Read has cognitive complexity 21 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
WaveOut.DoPlayback (cognitive 21) src/NAudio.WinMM/WaveOut.cs:174— WaveOut.DoPlayback has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsioShowCapabilitiesTest.Run (cognitive 20) samples/NAudioConsoleTest/Asio/Tests/AsioShowCapabilitiesTest.cs:18— AsioShowCapabilitiesTest.Run has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MidiInPanel.PopulateDeviceListsAsync (cognitive 20) samples/NAudioDemo/MidiInDemo/MidiInPanel.cs:74— MidiInPanel.PopulateDeviceListsAsync has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiplexingWaveProvider.MultiplexingWaveProvider.ctor (cognitive 20) src/NAudio.Core/Wave/WaveProviders/MultiplexingWaveProvider.cs:38— MultiplexingWaveProvider.MultiplexingWaveProvider.ctor has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MediaFoundationReader.ReadNextDecoderBuffer (cognitive 20) src/NAudio.Wasapi/MediaFoundationReader.cs:309— MediaFoundationReader.ReadNextDecoderBuffer has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CliDispatcher.Describe (cognitive 19) samples/NAudioConsoleTest/Shared/Testing/CliDispatcher.cs:82— CliDispatcher.Describe has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasapiRecordAndPlaybackTest.Run (cognitive 19) samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecordAndPlaybackTest.cs:31— WasapiRecordAndPlaybackTest.Run has cognitive complexity 19 (threshold 15). Of this number, 18 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.
WinMmMidiOutSysexTest.Run (cognitive 19) samples/NAudioConsoleTest/WinMM/Tests/WinMmMidiOutSysexTest.cs:33— WinMmMidiOutSysexTest.Run has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConvolutionReverbDemoViewModel.LoadAndPrepareIr (cognitive 19) samples/NAudioWpfDemo/ConvolutionReverbDemo/ConvolutionReverbDemoViewModel.cs:228— ConvolutionReverbDemoViewModel.LoadAndPrepareIr has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AsioOut.driver_BufferUpdate (cognitive 19) src/NAudio.Asio/AsioOut.cs:296— AsioOut.driver_BufferUpdate has cognitive complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 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.
WdlResampler.SetMode (cognitive 19) src/NAudio.Core/Dsp/WdlResampler.cs:74— WdlResampler.SetMode has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WdlResampler.BuildLowPass (cognitive 19) src/NAudio.Core/Dsp/WdlResampler.cs:563— WdlResampler.BuildLowPass has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XingHeader.LoadXingHeader (cognitive 19) src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:46— XingHeader.LoadXingHeader has cognitive complexity 19 (threshold 15). 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.
AudioFileException.ThrowIfError (cognitive 19) src/NAudio.MacOS/MacOS/AudioToolbox/AudioFileException.cs:30— AudioFileException.ThrowIfError has cognitive complexity 19 (threshold 15). 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.
Vst3Plugin.BuildUnitModel (cognitive 19) src/NAudio.Vst3/Vst3Plugin.cs:1931— Vst3Plugin.BuildUnitModel has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MediaFoundationReader.Reposition (cognitive 19) src/NAudio.Wasapi/MediaFoundationReader.cs:428— MediaFoundationReader.Reposition has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SoundFontInspector.Describe (cognitive 18) samples/AudioFileInspector/FileInspectors/SoundFontInspector.cs:22— SoundFontInspector.Describe has cognitive complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CliDispatcher.TryParseParameters (cognitive 18) samples/NAudioConsoleTest/Shared/Testing/CliDispatcher.cs:165— CliDispatcher.TryParseParameters has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Mp3StreamingPanel.StreamMp3 (cognitive 18) samples/NAudioDemo/Mp3StreamingDemo/MP3StreamingPanel.cs:58— Mp3StreamingPanel.StreamMp3 has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FilterEffect.ProcessBlock (cognitive 18) samples/NAudioWpfDemo/RealtimeEffectsDemo/CustomEffects/FilterEffect.cs:61— FilterEffect.ProcessBlock has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealtimeAudioEngine.SetEffects (cognitive 18) samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:55— RealtimeAudioEngine.SetEffects has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InterpolatingSampleReader.ReadContiguous (cognitive 18) src/NAudio.Core/Dsp/InterpolatingSampleReader.cs:276— InterpolatingSampleReader.ReadContiguous has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
WdlResampler.ResamplePrepare (cognitive 18) src/NAudio.Core/Dsp/WdlResampler.cs:160— WdlResampler.ResamplePrepare has cognitive complexity 18 (threshold 15). 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.
ExtendedAudioFileServicesWriter.FindBestFormat (cognitive 18) src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesWriter.cs:191— ExtendedAudioFileServicesWriter.FindBestFormat has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MacUtils.DecodeSpeakersFromChannelDescriptions (cognitive 18) src/NAudio.MacOS/Utils/MacUtils.ChannelTranslations.cs:114— MacUtils.DecodeSpeakersFromChannelDescriptions has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WaveViewer.OnPaint (cognitive 18) src/NAudio.WinForms/Gui/WaveViewer.cs:109— WaveViewer.OnPaint has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WaveFormatConversionProvider.Read (cognitive 18) src/NAudio.WinMM/WaveFormatConversionProvider.cs:58— WaveFormatConversionProvider.Read has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MixDiffForm.Shuffle (cognitive 17) samples/MixDiff/MixDiffForm.cs:483— MixDiffForm.Shuffle has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchRunner.Run (cognitive 17) samples/NAudioConsoleTest/Shared/Testing/BatchRunner.cs:16— BatchRunner.Run has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchRunner.TryBuildValues (cognitive 17) samples/NAudioConsoleTest/Shared/Testing/BatchRunner.cs:183— BatchRunner.TryBuildValues has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasapiRecorderRestartTest.Run (cognitive 17) samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecorderRestartTest.cs:33— WasapiRecorderRestartTest.Run has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SfzParser.Flatten (cognitive 17) src/NAudio.Core/FileFormats/Sfz/SfzParser.cs:240— SfzParser.Flatten has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiplexingSampleProvider.MultiplexingSampleProvider.ctor (cognitive 17) src/NAudio.Core/Wave/SampleProviders/MultiplexingSampleProvider.cs:26— MultiplexingSampleProvider.MultiplexingSampleProvider.ctor has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtendedAudioFileReaderFromStream.InitializeReader (cognitive 17) src/NAudio.MacOS/Wave/ExtendedAudioFileReaderFromStream.cs:79— ExtendedAudioFileReaderFromStream.InitializeReader has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MidiFile.SeekToRmidMidiData (cognitive 17) src/NAudio.Midi/Midi/MidiFile.cs:248— MidiFile.SeekToRmidMidiData has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MidiFileSequence.FromMidiFile (cognitive 17) src/NAudio.Midi/Sequencing/MidiFileSequence.cs:50— MidiFileSequence.FromMidiFile has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SfzRegionProjector.ApplyModulation (cognitive 17) src/NAudio.Sampler/SfzRegionProjector.cs:226— SfzRegionProjector.ApplyModulation has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Vst3Plugin.NegotiateBusArrangement (cognitive 17) src/NAudio.Vst3/Vst3Plugin.cs:594— Vst3Plugin.NegotiateBusArrangement has cognitive complexity 17 (threshold 15). 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.
WasapiRecorderBuilder.BuildAsync (cognitive 17) src/NAudio.Wasapi/WasapiRecorderBuilder.cs:288— WasapiRecorderBuilder.BuildAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsioPlayAudioFileTest.RunDevicePlayback (cognitive 16) samples/NAudioConsoleTest/Asio/Tests/AsioPlayAudioFileTest.cs:91— AsioPlayAudioFileTest.RunDevicePlayback has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasapiLoopbackCaptureTest.Run (cognitive 16) samples/NAudioConsoleTest/Wasapi/Tests/WasapiLoopbackCaptureTest.cs:35— WasapiLoopbackCaptureTest.Run has cognitive complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
G722Codec.Block4 (cognitive 16) src/NAudio.Core/Codecs/G722Codec.cs:43— G722Codec.Block4 has cognitive complexity 16 (threshold 15). 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.
FastFourierTransform.FFT (cognitive 16) src/NAudio.Core/Dsp/FastFourierTransform.cs:20— FastFourierTransform.FFT has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
WaveChannel32.Read (cognitive 16) src/NAudio.Core/Wave/WaveStreams/WaveChannel32.cs:141— WaveChannel32.Read has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtendedAudioFileServicesWriter.SelectBestIDForFileType (cognitive 16) src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesWriter.cs:50— ExtendedAudioFileServicesWriter.SelectBestIDForFileType has cognitive complexity 16 (threshold 15). 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.
MidiEventCollection.PrepareForExport (cognitive 16) src/NAudio.Midi/Midi/MidiEventCollection.cs:227— MidiEventCollection.PrepareForExport has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MidiEventComparer.Compare (cognitive 16) src/NAudio.Midi/Midi/MidiEventComparer.cs:18— MidiEventComparer.Compare has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SfzRegionProjector.Project (cognitive 16) src/NAudio.Sampler/SfzRegionProjector.cs:34— SfzRegionProjector.Project has cognitive complexity 16 (threshold 15). 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.
WasapiRecorder.CaptureAsync (cognitive 16) src/NAudio.Wasapi/WasapiRecorder.cs:279— WasapiRecorder.CaptureAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileTooLong: NAudio.Vst3/Vst3Plugin.cs src/NAudio.Vst3/Vst3Plugin.cs— FileTooLong — 1039 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 539 over it, 2.08× 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) src/NAudio.Core/Dsp/BiQuadFilter.cs:277— src/NAudio.Core/Dsp/BiQuadFilter.cs:277-293 | src/NAudio.Core/Dsp/BiQuadFilter.cs:360-375 | src/NAudio.Core/Dsp/BiQuadFilter.cs:385-400 | src/NAudio.Core/Dsp/BiQuadFilter.cs:410-425 | src/NAudio.Core/Dsp/BiQuadFilter.cs:435-450 — 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· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) src/NAudio.Asio/AsioSampleConvertor.cs:272— src/NAudio.Asio/AsioSampleConvertor.cs:272-290 | src/NAudio.Asio/AsioSampleConvertor.cs:344-363 | src/NAudio.Asio/AsioSampleConvertor.cs:390-409 | src/NAudio.Asio/AsioSampleConvertor.cs:442-462 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (90–92 lines × 5) src/NAudio.Wasapi/MediaFoundation/Interfaces/IMFActivate.cs:18— src/NAudio.Wasapi/MediaFoundation/Interfaces/IMFActivate.cs:18-109 | src/NAudio.Wasapi/MediaFoundation/Interfaces/IMFAttributes.cs:18-107 | src/NAudio.Wasapi/MediaFoundation/Interfaces/IMFMediaEvent.cs:18-109 | src/NAudio.Wasapi/MediaFoundation/Interfaces/IMFMediaType.cs:18-109 | src/NAudio.Wasapi/MediaFoundation/Interfaces/IMFSample.cs:18-109 — before extracting anything, compare `src/NAudio.Wasapi/MediaFoundation/Interfaces/IMFActivate.cs` and `src/NAudio.Wasapi/MediaFoundation/Interfaces/IMFAttributes.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `src/NAudio.Wasapi/MediaFoundation/Interfaces/IMFActivate.cs:18` 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 (78 lines × 2) src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioSessionControl.cs:37— src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioSessionControl.cs:37-114 | src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioSessionControl.cs:127-204 — 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 (44–46 lines × 3) src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioClient.cs:15— src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioClient.cs:15-58 | src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioClient2.cs:15-60 | src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioClient3.cs:16-61 — before extracting anything, compare `src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioClient.cs` and `src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioClient2.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioClient.cs:15` 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 (39 lines × 2) src/NAudio.Dmo/Dmo/Effect/DmoChorus.cs:44— src/NAudio.Dmo/Dmo/Effect/DmoChorus.cs:44-82 | src/NAudio.Dmo/Dmo/Effect/DmoFlanger.cs:44-82 — 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 `src/NAudio.Dmo/Dmo/Effect/DmoChorus.cs:44` 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 (24 lines × 2) src/NAudio.MacOS/MacOS/AudioToolbox/Interop/AudioFileCallbacks.cs:77— src/NAudio.MacOS/MacOS/AudioToolbox/Interop/AudioFileCallbacks.cs:77-100 | src/NAudio.MacOS/MacOS/AudioToolbox/Interop/AudioFileCallbacks.cs:130-153 — 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 `src/NAudio.MacOS/MacOS/AudioToolbox/Interop/AudioFileCallbacks.cs:77` 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 (16–22 lines × 2) src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:141— src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:141-162 | src/NAudio.MacOS/Wave/CoreAudioRecorder.InitAPI.cs:105-120 — 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 `src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:141` 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 (19 lines × 2) src/NAudio.Core/Effects/ChorusEffect.cs:73— src/NAudio.Core/Effects/ChorusEffect.cs:73-91 | src/NAudio.Core/Effects/FlangerEffect.cs:74-92 — before extracting anything, compare `src/NAudio.Core/Effects/ChorusEffect.cs` and `src/NAudio.Core/Effects/FlangerEffect.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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 `src/NAudio.Core/Effects/ChorusEffect.cs:73` 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–15 lines × 2) src/NAudio.Asio/AsioDevice.cs:694— src/NAudio.Asio/AsioDevice.cs:694-707 | src/NAudio.Asio/AsioDevice.cs:745-759 — 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.
Duplicated block (13–14 lines × 2) src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioVolumeLevel.cs:11— src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioVolumeLevel.cs:11-24 | src/NAudio.Wasapi/CoreAudioApi/Interfaces/IPerChannelDbLevel.cs:11-23 — before extracting anything, compare `src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioVolumeLevel.cs` and `src/NAudio.Wasapi/CoreAudioApi/Interfaces/IPerChannelDbLevel.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `src/NAudio.Wasapi/CoreAudioApi/Interfaces/IAudioVolumeLevel.cs:11` 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–13 lines × 4) src/NAudio.Asio/AsioSampleConvertor.cs:275— src/NAudio.Asio/AsioSampleConvertor.cs:275-286 | src/NAudio.Asio/AsioSampleConvertor.cs:347-359 | src/NAudio.Asio/AsioSampleConvertor.cs:393-405 | src/NAudio.Asio/AsioSampleConvertor.cs:445-457 — 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 `src/NAudio.Asio/AsioSampleConvertor.cs:275` 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 (11–12 lines × 3) src/NAudio.Asio/AsioSampleConvertor.cs:299— src/NAudio.Asio/AsioSampleConvertor.cs:299-310 | src/NAudio.Asio/AsioSampleConvertor.cs:498-509 | src/NAudio.Asio/AsioSampleConvertor.cs:553-563 — 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 `src/NAudio.Asio/AsioSampleConvertor.cs:299` 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 × 3) src/NAudio.Asio/AsioSampleConvertor.cs:188— src/NAudio.Asio/AsioSampleConvertor.cs:188-197 | src/NAudio.Asio/AsioSampleConvertor.cs:232-241 | src/NAudio.Asio/AsioSampleConvertor.cs:419-428 — 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 `src/NAudio.Asio/AsioSampleConvertor.cs:188` 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–10 lines × 3) src/NAudio.Core/Effects/GateEffect.cs:93— src/NAudio.Core/Effects/GateEffect.cs:93-102 | src/NAudio.Core/Effects/LimiterEffect.cs:152-160 | src/NAudio.Core/Effects/TransientShaperEffect.cs:58-67 — 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 all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/NAudio.Core/Effects/GateEffect.cs:93` 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 (6 lines × 5) src/NAudio.Core/Dsp/BiQuadFilter.cs:278— src/NAudio.Core/Dsp/BiQuadFilter.cs:278-283 | src/NAudio.Core/Dsp/BiQuadFilter.cs:361-366 | src/NAudio.Core/Dsp/BiQuadFilter.cs:386-391 | src/NAudio.Core/Dsp/BiQuadFilter.cs:411-416 | src/NAudio.Core/Dsp/BiQuadFilter.cs:436-441 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15 lines × 2) src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesReader.cs:449— src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesReader.cs:449-463 | src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesWriter.cs:450-464 — 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 (26 lines × 2) samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:205— samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:205-230 | samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeAudioEngine.cs:225-250 — 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 `samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:205` 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 (27 lines × 2) samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:117— samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:117-143 | samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeAudioEngine.cs:117-143 — 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 (18–19 lines × 2) samples/AudioFileInspector/AudioFileInspectorForm.cs:163— samples/AudioFileInspector/AudioFileInspectorForm.cs:163-181 | samples/MidiFileConverter/MainForm.cs:348-365 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/AudioFileInspector/AudioFileInspectorForm.cs:163` 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–10 lines × 2) samples/NAudioConsoleTest/Shared/Testing/FilePathPrompter.cs:43— samples/NAudioConsoleTest/Shared/Testing/FilePathPrompter.cs:43-52 | samples/NAudioConsoleTest/Shared/Testing/ParameterPrompter.cs:73-81 — 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 `samples/NAudioConsoleTest/Shared/Testing/FilePathPrompter.cs:43` 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 (42 lines × 3) samples/AudioFileInspector/AboutForm.cs:22— samples/AudioFileInspector/AboutForm.cs:22-63 | samples/MidiFileConverter/AboutForm.cs:22-63 | samples/MixDiff/AboutForm.cs:22-63 — `samples/AudioFileInspector/AboutForm.cs` and `samples/MidiFileConverter/AboutForm.cs` 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 1 separate duplicated blocks between them, totalling at least 42 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 `samples/AudioFileInspector/AboutForm.cs:22` 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.
End-of-life runtime: .NET net9.0 tests/NAudioAsioFakeDriverTest/NAudioAsioFakeDriverTest.csproj:12— tests/NAudioAsioFakeDriverTest/NAudioAsioFakeDriverTest.csproj declares .NET net9.0 as this project's target framework, and .NET 9 STS, support ended 2026-05-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-05-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: this repository runs its tests on Microsoft.Testing.Platform (its global.json opts in), where coverage comes from a coverage extension the test project references — and none is wired up: no build file names `Microsoft.Testing.Extensions.CodeCoverage` or `coverlet.MTP`. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment. Add one of those PackageReferences to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
IC1 · Incompleteness & stubs· Both branches are identical · ×1
Both branches are identical — the condition decides nothing src/NAudio.WinMM/Mixer/MixerControl.cs:169— The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 882 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
P12 · CI test-gate honesty· CI test gate excludes suites by filter · ×1
CI test gate excludes suites by filter REDACTED:34— `dotnet test --solution NAudio.slnx --configuration Release --no-build --filter "TestCategory!=IntegrationTest" --report-trx --results-dir…` filters with `TestCategory!=IntegrationTest` — 157 test(s) it drops — run by no other gate before merge (categories IntegrationTest; e.g. AlsaHardwareTests.PlaysAToneToARealDevice, AlsaHardwareTests.PlaysAWavFileToARealDevice). Run what it drops in another job before merge (a complementary filter), or remove the filter.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Sync-over-async (deadlock risk) samples/NAudioDemo/AudioPlaybackDemo/WasapiPlayerPlugin.cs:29— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) through `.Result` samples/NAudioDemo/Mp3StreamingDemo/MP3StreamingPanel.cs:66— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
X29 · Per-element action decided by a fixed element· Per-element action decided by a fixed element · ×1
Per-element action decided by a fixed element src/NAudio.Asio/AsioDevice.cs:882— This loop runs once per element of `selected`, and the statement it guards acts on the element it is on — `selected[i]`. The test deciding whether that statement runs does not: `other != format` reads `selected[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 878, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out.
Commented-out code src/NAudio.Asio/AsioAudioAvailableEventArgs.cs:92— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/Dsp/SmbPitchShifter.cs:239— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/Dsp/WdlResampler.cs:82— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/Dsp/WdlResampler.cs:578— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/FileFormats/Mp3/Mp3Frame.cs:186— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/FileFormats/Mp3/Mp3Frame.cs:196— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:72— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/FileFormats/SoundFont/GeneratorBuilder.cs:18— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/FileFormats/SoundFont/InfoChunk.cs:18— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/FileFormats/SoundFont/ModulatorBuilder.cs:21— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/FileFormats/SoundFont/RiffChunk.cs:81— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/FileFormats/SoundFont/SoundFont.cs:43— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/Wave/SampleProviders/PanningSampleProvider.cs:147— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/Wave/SampleProviders/PanningSampleProvider.cs:169— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/Wave/SampleProviders/PanningSampleProvider.cs:192— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/Wave/WaveFormats/WaveFormatExtensible.cs:168— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Core/Wave/WaveOutputs/WaveBuffer.cs:71— 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.MacOS/MacOS/CoreFoundationApi/AbstractCoreFoundationObject.cs:107— 13 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.MacOS/MacOS/CoreFoundationApi/AbstractCoreFoundationObject.cs:124— 20 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:183— 7 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:444— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:477— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:495— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:513— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/NAudio.Midi/Midi/MetaEvent.cs:99— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Duplicated predicate samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs:110— `!completed.IsSet && DateTime.UtcNow - start < duration` appears character-identically in 2 files — samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs, samples/NAudioConsoleTest/Asio/Tests/AsioRecordToWavTest.cs. 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 samples/NAudioConsoleTest/Dmo/Tests/DmoDecodeMp3Test.cs:50— `!ctx.Cancellation.IsCancellationRequested && (bytesRead = reader.Read(buffer, 0, buffer.Length)) > 0` appears character-identically in 2 files — samples/NAudioConsoleTest/Dmo/Tests/DmoDecodeMp3Test.cs, samples/NAudioConsoleTest/WinMM/Tests/WinMmDecodeMp3Test.cs. 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 samples/NAudioConsoleTest/Asio/Tests/AsioPlayAudioFileTest.cs:112— `!ctx.Interactive && DateTime.UtcNow - start >= maxDuration` appears character-identically in 4 files — samples/NAudioConsoleTest/Asio/Tests/AsioPlayAudioFileTest.cs, samples/NAudioConsoleTest/SoundFile/Tests/SoundFilePlayFileTest.cs, samples/NAudioConsoleTest/Wasapi/Tests/WasapiPlayFileTest.cs, samples/NAudioConsoleTest/WinMM/Tests/WinMmPlayFileTest.cs. 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 samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeEffectsViewModel.cs:34— `!string.IsNullOrEmpty(remembered) && Drivers.Contains(remembered)` appears character-identically in 3 files — samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeEffectsViewModel.cs, samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeEffectViewModel.cs, samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs. 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 src/NAudio.Alsa/AlsaIn.cs:71— `AlsaInterop.PcmDelay(pcm.Pcm, out nint delayFrames) < 0 || delayFrames < 0` appears character-identically in 2 files — src/NAudio.Alsa/AlsaIn.cs, src/NAudio.Alsa/AlsaOut.cs. 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 samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs:112— `Console.KeyAvailable && Console.ReadKey(intercept: true).Key == ConsoleKey.Escape` appears character-identically in 3 files — samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs, samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs, samples/NAudioConsoleTest/Asio/Tests/AsioShowChannelLevelsTest.cs. 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 REDACTED:284— `WaveFormat.BitsPerSample == 32 && WaveFormat.Encoding == WaveFormatEncoding.IeeeFloat` appears character-identically in 2 files — REDACTED, src/NAudio.Core/Wave/WaveOutputs/WaveFileWriter.cs. 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 samples/NAudioConsoleTest/Asio/Tests/AsioPlayAudioFileTest.cs:108— `ctx.Interactive && Console.KeyAvailable && Console.ReadKey(intercept: true).Key == ConsoleKey.Escape` appears character-identically in 9 files — samples/NAudioConsoleTest/Asio/Tests/AsioPlayAudioFileTest.cs, samples/NAudioConsoleTest/Asio/Tests/AsioRecordToWavTest.cs, samples/NAudioConsoleTest/Asio/Tests/AsioValidateSamplePositionTest.cs, samples/NAudioConsoleTest/DirectSound/Tests/DirectSoundPlayToneTest.cs. 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 samples/NAudioDemo/AsioRecordingDemo/AsioRecordingPanel.cs:177— `device != null && device.State == AsioDeviceState.Running` appears character-identically in 4 files — samples/NAudioDemo/AsioRecordingDemo/AsioRecordingPanel.cs, samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs, samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeAudioEngine.cs, samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentEngine.cs. 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 samples/NAudioConsoleTest/WinMM/Tests/WinMmMidiOutSysexTest.cs:40— `deviceNumber < 0 || deviceNumber >= deviceCount` appears character-identically in 2 files — samples/NAudioConsoleTest/WinMM/Tests/WinMmMidiOutSysexTest.cs, samples/NAudioConsoleTest/WinMM/Tests/WinMmRecordToFileTest.cs. 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 samples/NAudioWpfDemo/LiveSamplerDemo/LiveSamplerDemoViewModel.cs:275— `dispatcher == null || dispatcher.CheckAccess()` appears character-identically in 2 files — samples/NAudioWpfDemo/LiveSamplerDemo/LiveSamplerDemoViewModel.cs, samples/NAudioWpfDemo/Utils/SamplerPlayback.cs. 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 src/NAudio.Asio/AsioDevice.cs:86— `driverIndex < 0 || driverIndex >= names.Length` appears character-identically in 2 files — src/NAudio.Asio/AsioDevice.cs, src/NAudio.Asio/AsioOut.cs. 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 samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs:232— `durationSeconds > 0 && pos >= durationSeconds` appears character-identically in 2 files — samples/NAudioWpfDemo/SamplerDemo/SamplerDemoViewModel.cs, samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs. 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 src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesWriter.cs:327— `extensible.SubFormat != AudioMediaSubtypes.MEDIASUBTYPE_PCM && extensible.SubFormat != AudioMediaSubtypes.MEDIASUBTYPE_IEEE_FLOAT` appears character-identically in 2 files — src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesWriter.cs, src/NAudio.MacOS/Wave/MacAudioConverter.cs. 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 src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesWriter.cs:334— `fmt.Encoding != WaveFormatEncoding.Pcm && fmt.Encoding != WaveFormatEncoding.IeeeFloat` appears character-identically in 2 files — src/NAudio.MacOS/MacOS/AudioToolbox/ExtendedAudioFileServicesWriter.cs, src/NAudio.MacOS/Wave/MacAudioConverter.cs. 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 samples/NAudioWpfDemo/WasapiRecorderDemo/WasapiRecorderViewModel.cs:507— `format.Encoding == WaveFormatEncoding.IeeeFloat && format.BitsPerSample == 32` appears character-identically in 2 files — samples/NAudioWpfDemo/WasapiRecorderDemo/WasapiRecorderViewModel.cs, src/NAudio.SoundFile/SoundFileWriter.cs. 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 samples/NAudioWpfDemo/WasapiRecorderDemo/WasapiRecorderViewModel.cs:515— `format.Encoding == WaveFormatEncoding.Pcm && format.BitsPerSample == 16` appears character-identically in 2 files — samples/NAudioWpfDemo/WasapiRecorderDemo/WasapiRecorderViewModel.cs, src/NAudio.SoundFile/SoundFileWriter.cs. 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 src/NAudio.Vst3/Hosting/Vst3HostMessage.cs:67— `hr != 0 || _attributesPtr == IntPtr.Zero` appears character-identically in 2 files — src/NAudio.Vst3/Hosting/Vst3HostMessage.cs, src/NAudio.Vst3/Hosting/Vst3MemoryStream.cs. 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 src/NAudio.Core/Wave/SampleProviders/MultiplexingSampleProvider.cs:143— `inputChannel < 0 || inputChannel >= InputChannelCount` appears character-identically in 2 files — src/NAudio.Core/Wave/SampleProviders/MultiplexingSampleProvider.cs, src/NAudio.Core/Wave/WaveProviders/MultiplexingWaveProvider.cs. 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 samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:175— `inputChannels == 2 && buffers.InputChannelCount > 1` appears character-identically in 2 files — samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs, samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeAudioEngine.cs. 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 src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:27— `ioProcedure is not null && ioProcedure.IsRunning` appears character-identically in 2 files — src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs, src/NAudio.MacOS/Wave/CoreAudioRecorder.InitAPI.cs. 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 src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:312— `isInit || ioProcedure is InterleavedProcedure` appears character-identically in 2 files — src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs, src/NAudio.MacOS/Wave/CoreAudioRecorder.InitAPI.cs. 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 src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs:330— `isInit || ioProcedure is NonInterleavedProcedure` appears character-identically in 2 files — src/NAudio.MacOS/Wave/CoreAudioPlayer.InitAPI.cs, src/NAudio.MacOS/Wave/CoreAudioRecorder.InitAPI.cs. 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 src/NAudio.Core/Wave/SampleProviders/MultiplexingSampleProvider.cs:147— `outputChannel < 0 || outputChannel >= OutputChannelCount` appears character-identically in 2 files — src/NAudio.Core/Wave/SampleProviders/MultiplexingSampleProvider.cs, src/NAudio.Core/Wave/WaveProviders/MultiplexingWaveProvider.cs. 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 src/NAudio.Wasapi/WasapiOut.cs:310— `playbackState == PlaybackState.Stopped || OutputWaveFormat == null` appears character-identically in 2 files — src/NAudio.Wasapi/WasapiOut.cs, src/NAudio.Wasapi/WasapiPlayer.cs. 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.
README/code drift Docs/CrossPlatformAudioFilesWithSoundFile.md:12— Docs/CrossPlatformAudioFilesWithSoundFile.md installs the package `NAudio.SoundFile` (`dotnet add package NAudio.SoundFile`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/PlayAudioFileLinuxAlsa.md:9— Docs/PlayAudioFileLinuxAlsa.md installs the package `NAudio.Alsa` (`dotnet add package NAudio.Alsa`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/PlayAudioFileMacOS.md:10— Docs/PlayAudioFileMacOS.md installs the package `NAudio.MacOS` (`dotnet add package NAudio.MacOS --prerelease`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/RecordAudioFileLinuxAlsa.md:8— Docs/RecordAudioFileLinuxAlsa.md installs the package `NAudio.Alsa` (`dotnet add package NAudio.Alsa`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/RecordAudioFileMacOS.md:8— Docs/RecordAudioFileMacOS.md installs the package `NAudio.MacOS` (`dotnet add package NAudio.MacOS --prerelease`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/ValidatingAlsaOnLinux.md:48— Docs/ValidatingAlsaOnLinux.md runs `dotnet build NAudio.Alsa/NAudio.Alsa.csproj -c Release`, but `NAudio.Alsa/NAudio.Alsa.csproj` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/ValidatingAlsaOnLinux.md:49— Docs/ValidatingAlsaOnLinux.md runs `dotnet test --project NAudio.Alsa.Tests/NAudio.Alsa.Tests.csproj -c Release`, but `NAudio.Alsa.Tests/NAudio.Alsa.Tests.csproj` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/Architecture/DirectSoundActivationModernization.md:3— Docs/Architecture/DirectSoundActivationModernization.md names `NAudio.Core/Utils/NativeMethods.cs`, but no file or folder `NAudio.Core/Utils/NativeMethods.cs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/Architecture/DirectSoundActivationModernization.md:96— Docs/Architecture/DirectSoundActivationModernization.md runs `dotnet publish NAudioAotSmokeTest -c Release -p:PublishAot=false -p:PublishTrimmed=true -p:BuiltInComInteropSupport=false` from `Docs/Architecture/` or the repository root, but `NAudioAotSmokeTest` is not there: the project is `tests/NAudioAotSmokeTest`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/Architecture/MODERNIZATION.md:11— Docs/Architecture/MODERNIZATION.md names .NET 6, but the projects target .NET 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/Architecture/MODERNIZATION.md:254— Docs/Architecture/MODERNIZATION.md runs `dotnet publish NAudioAotSmokeTest -c Release -p:PublishTrimmed=true -p:BuiltInComInteropSupport=false` from `Docs/Architecture/` or the repository root, but `NAudioAotSmokeTest` is not there: the project is `tests/NAudioAotSmokeTest`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/Architecture/MODERNIZATION.md:324— Docs/Architecture/MODERNIZATION.md names `NAudioTests/Utils/CountingStream.cs`, but no file or folder `NAudioTests/Utils/CountingStream.cs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/Architecture/MediaFoundationActivationModernization.md:241— Docs/Architecture/MediaFoundationActivationModernization.md runs `dotnet publish NAudioAotSmokeTest -c Release -p:PublishAot=false -p:PublishTrimmed=true` from `Docs/Architecture/` or the repository root, but `NAudioAotSmokeTest` is not there: the project is `tests/NAudioAotSmokeTest`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/Architecture/Vst3Hosting.md:28— Docs/Architecture/Vst3Hosting.md names the project `NAudio.Vst3Host`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/Architecture/Vst3Hosting.md:28— Docs/Architecture/Vst3Hosting.md names the project `NAudio.PluginHost`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/Architecture/Vst3Hosting.md:143— Docs/Architecture/Vst3Hosting.md names the project `NAudio.AudioUnit`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/Architecture/Vst3Hosting.md:143— Docs/Architecture/Vst3Hosting.md names the project `NAudio.Clap`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/NAudio.Alsa/README.md:32— src/NAudio.Alsa/README.md installs the package `NAudio.Alsa` (`dotnet add package NAudio.Alsa`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/NAudio.Alsa/README.md:75— src/NAudio.Alsa/README.md installs the package `NAudio.SoundFile` (`dotnet add package NAudio.SoundFile`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/NAudio.SoundFile/README.md:35— src/NAudio.SoundFile/README.md installs the package `NAudio.SoundFile` (`dotnet add package NAudio.SoundFile`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/NAudio.Vst3/README.md:20— src/NAudio.Vst3/README.md installs the package `NAudio.Vst3` (`dotnet add package NAudio.Vst3`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift tests/MfStressTest/README.md:141— tests/MfStressTest/README.md runs `dotnet run -c Release --project MfStressTest` from `tests/MfStressTest/` or the repository root, but `MfStressTest` is not there: the project is `tests/MfStressTest`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift tests/NAudioAotSmokeTest/README.md:88— tests/NAudioAotSmokeTest/README.md runs `dotnet publish NAudioAotSmokeTest/NAudioAotSmokeTest.csproj -c Release -p:PublishAot=false -p:PublishTrimmed=true`, but `NAudioAotSmokeTest/NAudioAotSmokeTest.csproj` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Silent fallback default in catch samples/NAudioConsoleTest/MediaFoundation/Tests/MediaFoundationEnumerateTransformsTest.cs:74— `GetTransformName` swallows every exception into `return "(unknown)";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch samples/NAudioConsoleTest/MediaFoundation/Tests/MediaFoundationEnumerateTransformsTest.cs:92— `GetTypeDescriptions` swallows every exception into `return "-";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch samples/NAudioDemo/VolumeMixerDemo/IconExtractor.cs:20— `Extract` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch samples/NAudioDemo/VolumeMixerDemo/VolumeMixerPanel.cs:84— `OnSessionCreated` swallows every exception and sets `display = "<unknown>";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch samples/NAudioDemo/VolumeMixerDemo/VolumeMixerPanel.cs:114— `ProcessExists` swallows `ArgumentException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeEffectViewModel.cs:380— `SafeListDrivers` swallows every exception into `return Array.Empty<string>();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs:300— `SafeListDrivers` swallows every exception into `return Array.Empty<string>();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/NAudio.MacOS/MacOS/CoreAudio/AudioObject.cs:101— `GetStringPropertyValueOrEmptyIfNotExisting` swallows `CoreAudioPropertyNotFoundException` into `return string.Empty;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/NAudio.Vst3/Hosting/Vst3MemoryStream.cs:135— `SetStreamSize` swallows every exception into `return TResultCodes.InternalError;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/NAudio.Wasapi/MediaFoundation/MFByteStreamFromStream.cs:211— `SetCurrentPosition` swallows `IOException` into `return HResult.STG_E_SEEKERROR;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/NAudio.Wasapi/MediaFoundation/MFByteStreamFromStream.cs:228— `SetLength` swallows `NotSupportedException` into `return HResult.STG_E_UNIMPLEMENTEDFUNCTION;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Pass-through layer src/NAudio.Core/Utils/IgnoreDisposeStream.cs:11— IgnoreDisposeStream: all 7 public methods forward their arguments unchanged to SourceStream and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call SourceStream directly, or give the layer a job.
Pass-through layer src/NAudio.Wasapi/CoreAudioApi/MMDeviceNotificationClient.cs:112— NotificationCallback: all 5 public methods forward their arguments unchanged to owner and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call owner directly, or give the layer a job.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by imperative guard methods that throw on violation) — this is NOT a claim that the code is unprotected. What's missing is a NAMED rule set: the guards encode the access rules inline, so the rules can't be listed, reviewed or tested apart from the call sites that apply them. Recommendation, not a defect.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D21 · Naming Consistency· Inconsistent test naming convention for the same test class `WaveOffsetStreamTests`. One test uses a descriptive sentence format (`ChangingSourceLengthUpdatesLength`), while another uses a technical assertion format with underscores (`WaveOffsetStream_SpanAndByteArrayRead_Agree`). · ×1
Inconsistent test naming convention for the same test class `WaveOffsetStreamTests`. One test uses a descriptive sentence format (`ChangingSourceLengthUpdatesLength`), while another uses a technical assertion format with underscores (`WaveOffsetStream_SpanAndByteArrayRead_Agree`). — Standardize on a single test naming style for the class, either all descriptive sentences (e.g., `ChangingSourceLengthUpdatesLength`) or all technical assertions (e.g., `SpanAndByteArrayRead_Agree`). Given the other tests in the list use descriptive sentences, the underscored name is the outlier. (symbols: NAudio.Core.Tests.WaveStreams.WaveOffsetStreamTests.ChangingSourceLengthUpdatesLength, NAudio.Core.Tests.WaveStreams.WaveOffsetStream_SpanAndByteArrayRead_Agree)
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 30 project(s) overshoot their size bounds, lowering Project Cohesion to 8.7/10. The most over is `NAudio.Core` (26278 LoC, 261 public types across 9 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
Scattered collaborators — 87 % of calls cross a namespace and only 60 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
IL efficiency: 50 authored method(s) exceed the IL budget src/NAudio.Core/Dsp/WdlResampler.cs:252— 50 of 5564 first-party methods compile to oversized IL bodies (> 250 instructions); worst: NAudio.Dsp.WdlResampler.ResampleOut @ src/NAudio.Core/Dsp/WdlResampler.cs:252, 1167 IL instructions; that pulled this dimension to 9.8/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.
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.
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 20 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
Logging is not universal — Only 5/11 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 11, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 3/31 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Nullable reference types not enabled everywhere — 14/20 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.2 `!` suppressions per 1k syntax nodes — 73 suppression(s) across the 319583 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Silent fallback default on parse failure samples/NAudioDemo/AudioPlaybackDemo/AsioDeviceSettingsPanel.cs:26— `OutputChannelOffset` falls back to `0` when `int.TryParse(textBoxChannelOffset.Text, out int offset)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a168ae-ba64-7d5c-b9d7-d321f0e02e50 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 5 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 122 · Warnings: 633 · Recommendations: 120 · Info: 32 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 12:14 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.