Public report — NAudio, published 5 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
376findings with an exact file:lineof 401 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
53/97dimensions across the health lenses106022 LoC · 30 projects — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
naudio/NAudio is sound in substance but carries real gaps (57%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Architecture (95%) — the structure is clean and changes stay contained.
The area that most needs attention is Code Health (51%) — changes there are slower and more error-prone. Security (57%) is the next concern — exposure to security and compliance incidents is elevated.
Leadership focus, highest impact first: Sync-over-async (deadlock risk) (Async correctness); Thread a CancellationToken through async methods so work stops… (Cancellation propagation); Enable <Nullable>enable</Nullable> across all projects… (Nullable reference types).
For scale: Large (~106,022 production lines); rebuilding it from scratch would take roughly ~1.7 person-years (~1–4 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (95%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
This codebase represents roughly ~1.7 person-years of build effort (about ~€250,000 to rebuild). Its weakest lens is Code Health at 51% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.1) — desktop/game × a 0.8× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with NAudioWpfDemo.csproj, NAudioDemo.csproj, MixDiff.csproj.
Value concentrated against a weak lens · Medium · Value at risk
This is a Large asset (~1.7 person-years to rebuild), and its weakest lens is Code Health at 51%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Code Health first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Sync-over-async (deadlock risk) The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Sync-over-async (deadlock risk)
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 — module dependency matrix
34 modules, 55 dependencies — 1 dependency cycle, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
At a glance — Code Health · 51% · Adequate · gated by X5
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
A03:2021 — Injection
18
High / Critical
A04:2021 — Insecure Design
1
High / Critical
Roadmap
First, eliminate the deadlock risks caused by synchronous calls within asynchronous contexts. Next, ensure that cancellation tokens are properly propagated through all asynchronous methods to allow for timely operation termination. Then, enable nullable reference types across all projects and resolve the resulting warnings instead of suppressing them. Finally, address the 16 instances of swallowed exceptions, starting with DiagnosticsCollector.cs, VolumePanel.cs, and Vst3RealtimeInstrumentEngine.cs.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with NAudioWpfDemo.csproj, NAudioDemo.csproj, MixDiff.csproj.
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. 49 of 53 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.7 — 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 — 53 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, 376 of 401 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
A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.
When something does degrade — a missing scanner, a shallow clone, an LLM hiccup — it is named here explicitly and its exact cause recorded in diagnostics.md, never absorbed silently into the score.
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 (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
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 the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
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.
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 (5): D19, D20, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These 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.
45 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MidiConverter.ConvertMidi at 54. A further 9 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.
+ 40 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 MidiConverter.ConvertMidi (cyclomatic 54) finding(s) in Cyclomatic Complexity — start with MidiConverter.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 WdlResampler.ResampleOut (cyclomatic 51) finding(s) in Cyclomatic Complexity — start with WdlResampler.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Vst3Plugin.Initialise (cyclomatic 35) finding(s) in Cyclomatic Complexity — start with Vst3Plugin.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 98 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 WdlResampler.ResampleOut (cognitive 128) finding(s) in Cognitive Complexity — start with WdlResampler.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 MidiConverter.ConvertMidi (cognitive 113) finding(s) in Cognitive Complexity — start with MidiConverter.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 DahdsrEnvelope.Advance (cognitive 95) finding(s) in Cognitive Complexity — start with DahdsrEnvelope.cs. — One of this dimension's main actionable groups (1 warning-level).
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.7 / 10Exemplary✓ 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.
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.
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.5 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
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.
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.
1807 test methods: 1807 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.9 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
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.
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.
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.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.5 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
53 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/NAudio.Asio/AsioDevice.cs.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
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.
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.
NAudio's documentation is comprehensive and well-structured across READMEs, architecture markdowns, and XML docs. The main README gives a clear overview of the library (Mark Heath authorship, NAudio 3 pre-release status, features), links to GitHub and NuGet, and an outline naming Features, Getting Started, Tutorials, and more sections. A dedicated cross-platform SoundFile README covers P/Invoke libsndfile with supported formats, codec availability via capabilities, and a concrete read/write example, plus a clip-out that the outline promises (Read any file; Write FLAC / Ogg / Opus). The VST3 README is excellent at describing plug-in discovery, hosting, integration, and editor UI. Despite being clipped in several places, each outlined section exists and is not flagged as missing. The NAudio documentation is comprehensive and well-structured: a README for each major package (Midi, Extras, Dmo, Core, Asio, ALSA) explains what it includes and when to use, plus an architecture/Docs markdown collection covering the cross-platform core, Windows-only APIs, and the separate WASAPI/DMO/DirectSound backends. The XML-doc coverage is low for most packages (e.g. 7% for NAudio.Midi), but the READMEs alone are clear and complete for a reader who can navigate the package docs on GitHub. The NAudio documentation is exemplary in its breadth and depth for a C# audio library. It includes 19 README files plus architecture/design docs (59) covering WASAPI playback, capture, loopback, and the older WasapiOut API, with each major feature documented thoroughly. The XML-doc coverage is strong: 32/429 NAudio.Alsa to 1195/1271 Wasapi.WasapiWASAPI (94%) plus 100% for NAudio.Midi and NAudio.Sampler, reflecting the high quality of the documentation. The two clipped WASAPI docs are the only visible sections in a long outline; they do not appear missing but are trimmed mid-sentence, so no section is flagged as unexplained.
Improve Documentation Quality — currently 8.6/10. — NAudio's documentation is comprehensive and well-structured across READMEs, architecture markdowns, and XML docs. The main README gives a clear overview of the library (Mark Heath authorship, NAudio 3 pre-release status, features), links to GitHub and NuGet, and an outline naming Features, Getting Started, Tutorials, and more sections. A dedicated cross-platform SoundFile README covers P/Invoke libsndfile with supported formats, codec availability via capabilities, and a concrete read/write example, plus a clip-out that the outline promises (Read any file; Write FLAC / Ogg / Opus). The VST3 README is excellent at describing plug-in discovery, hosting, integration, and editor UI. Despite being clipped in several places, each outlined section exists and is not flagged as missing. The NAudio documentation is comprehensive and well-structured: a README for each major package (Midi, Extras, Dmo, Core, Asio, ALSA) explains what it includes and when to use, plus an architecture/Docs markdown collection covering the cross-platform core, Windows-only APIs, and the separate WASAPI/DMO/DirectSound backends. The XML-doc coverage is low for most packages (e.g. 7% for NAudio.Midi), but the READMEs alone are clear and complete for a reader who can navigate the package docs on GitHub. The NAudio documentation is exemplary in its breadth and depth for a C# audio library. It includes 19 README files plus architecture/design docs (59) covering WASAPI playback, capture, loopback, and the older WasapiOut API, with each major feature documented thoroughly. The XML-doc coverage is strong: 32/429 NAudio.Alsa to 1195/1271 Wasapi.WasapiWASAPI (94%) plus 100% for NAudio.Midi and NAudio.Sampler, reflecting the high quality of the documentation. The two clipped WASAPI docs are the only visible sections in a long outline; they do not appear missing but are trimmed mid-sentence, so no section is flagged as unexplained.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D24 · Comment Value / 10Exemplary◐ 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 27 projects flagged as possibly oversized/incoherent.
Split NAudio.Core
What to do
Resolve the 1 Split NAudio.Core 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.6 / 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.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
85 % of calls cross a namespace and 2 % go through an interface, but 60 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.
Scattered collaborators
What to do
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: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
High: github-actions-mutable-action-tag · ×10.github/workflows/build.yml:19detected by semgrep finding
Low: plaintext-http-link · ×8samples/AudioFileInspector/audio_file_inspector.html:39detected by semgrep finding
What to do
Resolve the 10 High finding(s) in Static Analysis (SAST) — start with docs.yml (4), release.yml (4), build.yml (2). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 8 Low finding(s) in Static Analysis (SAST) — start with midi_file_converter.html (5), audio_file_inspector.html (3). — One of this dimension's main actionable groups (8 recommendation-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
No known-vulnerable NuGet packages (direct or transitive).
✓ On the Gold path — maintain.
Detailed fixes: d30_recommendation.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)7.1 / 10Strong✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR pattern scan via semgrep across the repo, using Watchdog's own ruleset (personal data reaching log/console sinks, URLs and query strings, or unprotected browser storage); matches map to severity and a 0-10 wide normalizer. NotApplicable when the scan runs and detects no PII/GDPR surface (no unearned 10); reported LOUDLY as a measurement gap, never as not-applicable, if the ruleset is missing from the analyzer image. Exhaustive, advisory-leaning; degrades on parse failure.
High: watchdog-sensitive-personal-data-in-logsrc/NAudio.Core/Wave/WaveOutputs/AiffFileWriter.cs:90detected by semgrep finding
What to do
Resolve the 1 High finding(s) in Data Compliance (PII/GDPR) — start with AiffFileWriter.cs. — 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.
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; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PR-triggered workflow without a permissions block finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No build provenance 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.9 / 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.
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.
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 — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether 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 member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · 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.
A placeholder string ("Replacement") is still in shipped code — typical of generated boilerplate that was never filled in. — NamingRule.cs:54
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — AsioAudioAvailableEventArgs.cs:109, AudioPlaybackEngine.cs:47, PropVariant.cs:273
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
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.
`Callback` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — MidiOut.cs:126
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×22) — AsioAudioAvailableEventArgs.cs:91, SmbPitchShifter.cs:239, WdlResampler.cs:81, …
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.
1548 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.
Add a 'Testing' section to the root README — 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 11 of 27 project(s) that lack one — worth up to 0.8 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 `NNNN-title.md` documents 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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
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.
Only 5/19 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 19, 6 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.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
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.
Readiness · Performance — Whether the library 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 — 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.
Raise allocation-aware density on the hot paths — currently 377 use(s) across 113,450 production line(s) (~3.3/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code keeps its host responsive — a library awaits with ConfigureAwait(false) (so it never captures and stalls the host's context) and avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a 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 in a consumer with a synchronization context.
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code.
Do you agree with this assessment?
X1 · Async correctness4.3 / 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. (×6) — Vst3LiveSynthTest.cs:64, Vst3LiveSynthTest.cs:88, WasapiPlayFileTest.cs:61, …
`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. (×5) — LiveSamplerDemoViewModel.cs:159, SamplerDemoViewModel.cs:141, SamplerDemoViewModel.cs:235, …
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.
Only 2/32 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. (×25) — MidiInPanel.cs:32, MidiInPanel.cs:48, MidiInPanel.cs:104, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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. (×16) — AsioDuplexPassthroughTest.cs:127, AsioLegacyDuplexPassthroughTest.cs:136, AsioPlayAudioFileTest.cs:116, …
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.
2/19 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.6 `!` suppressions per 1k syntax nodes — 46 suppression(s) across the 80983 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
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.
Not included — 44 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
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.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in 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
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies 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.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this check looks for (4 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check 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 check looks for
P12 CI test-gate honesty — 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
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) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, 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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
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/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs:127— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:136— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock samples/NAudioDemo/VolumeMixerDemo/VolumePanel.cs:213— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock samples/NAudioDemo/VolumeMixerDemo/VolumePanel.cs:228— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentEngine.cs:114— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentEngine.cs:130— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs:195— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/NAudio.Wasapi/MediaFoundation/FileFormatDiscovery/AudioFileFormatFinder.cs:177— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/NAudio.Wasapi/MediaFoundation/FileFormatDiscovery/AudioFileFormatFinder.cs:183— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/NAudio.Wasapi/MediaFoundation/MFByteStreamFromStream.cs:506— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
High: github-actions-mutable-action-tag .github/workflows/build.yml:19— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:43— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/docs.yml:35— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/docs.yml:42— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/docs.yml:55— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-pages-artifact@<40-character SHA>`. This step references `actions/upload-pages-artifact@v3`; resolve the SHA it points at today with `gh api repos/actions/upload-pages-artifact/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/docs.yml:73— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/deploy-pages@<40-character SHA>`. This step references `actions/deploy-pages@v4`; resolve the SHA it points at today with `gh api repos/actions/deploy-pages/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release.yml:29— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: run-shell-injection .github/workflows/release.yml:47— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/workflows/release.yml:182— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release.yml:196— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: NuGet/login@<40-character SHA>`. This step references `NuGet/login@v1`; resolve the SHA it points at today with `gh api repos/NuGet/login/commits/v1 --jq .sha`.
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.
High: watchdog-sensitive-personal-data-in-log src/NAudio.Core/Wave/WaveOutputs/AiffFileWriter.cs:90— Special-category or directly-identifying personal data appears to be written to a log or console sink. Logs are copied, shipped to third parties and retained far longer than the data itself is lawfully needed. Log a stable pseudonymous reference instead of the value.
Dead code: FindBeatsPerMeasure samples/AudioFileInspector/FileInspectors/MidiFileInspector.cs:61— Method FindBeatsPerMeasure — no references found in solution.
Dead code: AudioFileSelector samples/NAudioConsoleTest/Shared/AudioFileSelector.cs:5— NamedType AudioFileSelector — no references found in solution.
Dead code: DeviceSelector samples/NAudioConsoleTest/Shared/DeviceSelector.cs:6— NamedType DeviceSelector — no references found in solution.
Dead code: AsioDevicePlugin samples/NAudioDemo/AudioPlaybackDemo/AsioDevicePlugin.cs:10— NamedType AsioDevicePlugin — no references found in solution.
Dead code: AsioOutPlugin samples/NAudioDemo/AudioPlaybackDemo/AsioOutPlugin.cs:6— NamedType AsioOutPlugin — no references found in solution.
Dead code: DirectSoundOutPlugin samples/NAudioDemo/AudioPlaybackDemo/DirectSoundOutPlugin.cs:7— NamedType DirectSoundOutPlugin — no references found in solution.
Dead code: WaveOutPlugin samples/NAudioDemo/AudioPlaybackDemo/WaveOutPlugin.cs:6— NamedType WaveOutPlugin — no references found in solution.
Dead code: WaveOutWindowPlugin samples/NAudioDemo/AudioPlaybackDemo/WaveOutWindowPlugin.cs:6— NamedType WaveOutWindowPlugin — no references found in solution.
Dead code: Tb_ValueChanged samples/NAudioDemo/DeviceTopology/DeviceTopologyPanel.cs:136— Method Tb_ValueChanged — no references found in solution.
Dead code: DeviceTopologyPlugin samples/NAudioDemo/DeviceTopology/DeviceTopologyPlugin.cs:3— NamedType DeviceTopologyPlugin — no references found in solution.
Dead code: FadeInOutPlugin samples/NAudioDemo/FadeInOutDemo/FadeInOutPlugin.cs:3— NamedType FadeInOutPlugin — no references found in solution.
Dead code: AcmALawChatCodec samples/NAudioDemo/NetworkChatDemo/ALawChatCodec.cs:7— NamedType AcmALawChatCodec — no references found in solution.
Dead code: ALawChatCodec samples/NAudioDemo/NetworkChatDemo/ALawChatCodec.cs:18— NamedType ALawChatCodec — no references found in solution.
Dead code: G722ChatCodec samples/NAudioDemo/NetworkChatDemo/G722ChatCodec.cs:9— NamedType G722ChatCodec — no references found in solution.
Dead code: Gsm610ChatCodec samples/NAudioDemo/NetworkChatDemo/Gsm610ChatCodec.cs:5— NamedType Gsm610ChatCodec — no references found in solution.
Dead code: MicrosoftAdpcmChatCodec samples/NAudioDemo/NetworkChatDemo/MicrosoftAdpcmChatCodec.cs:5— NamedType MicrosoftAdpcmChatCodec — no references found in solution.
Dead code: AcmMuLawChatCodec samples/NAudioDemo/NetworkChatDemo/MuLawChatCodec.cs:7— NamedType AcmMuLawChatCodec — no references found in solution.
Dead code: MuLawChatCodec samples/NAudioDemo/NetworkChatDemo/MuLawChatCodec.cs:18— NamedType MuLawChatCodec — no references found in solution.
Dead code: TrueSpeechChatCodec samples/NAudioDemo/NetworkChatDemo/TrueSpeechChatCodec.cs:10— NamedType TrueSpeechChatCodec — no references found in solution.
Dead code: UncompressedPcmChatCodec samples/NAudioDemo/NetworkChatDemo/UncompressedPcmChatCodec.cs:6— NamedType UncompressedPcmChatCodec — no references found in solution.
Dead code: GeneratorPlugin samples/NAudioDemo/SignalGeneratorDemo/GeneratorPlugIn.cs:5— NamedType GeneratorPlugin — no references found in solution.
Dead code: VolumeMixerPlugin samples/NAudioDemo/VolumeMixerDemo/VolumeMixerPlugin.cs:8— NamedType VolumeMixerPlugin — no references found in solution.
Dead code: LiveWaveformVisualization samples/NAudioWpfDemo/AudioPlaybackDemo/LiveWaveformVisualization.cs:13— NamedType LiveWaveformVisualization — no references found in solution.
Dead code: SpectrumAnalyzerVisualization samples/NAudioWpfDemo/AudioPlaybackDemo/SpectrumAnalyzerVisualization.cs:3— NamedType SpectrumAnalyzerVisualization — no references found in solution.
Dead code: ConvolutionReverbDemoPlugin samples/NAudioWpfDemo/ConvolutionReverbDemo/ConvolutionReverbDemoPlugin.cs:5— NamedType ConvolutionReverbDemoPlugin — no references found in solution.
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:208— // 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:187— // 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:51— // 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:36— // 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:525— // 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.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.
TodoComment src/NAudio.WinForms/Gui/Fader.cs:104— // TODO: are we over the fader — 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.
Hotspot: src/NAudio.Wasapi/WasapiPlayer.cs src/NAudio.Wasapi/WasapiPlayer.cs— src/NAudio.Wasapi/WasapiPlayer.cs changed 10 times in last 90 days, max complexity 22. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: src/NAudio.Core/Dsp/WdlResampler.cs src/NAudio.Core/Dsp/WdlResampler.cs— src/NAudio.Core/Dsp/WdlResampler.cs changed 4 times in last 90 days, max complexity 51. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: samples/MidiFileConverter/MidiConverter.cs samples/MidiFileConverter/MidiConverter.cs— samples/MidiFileConverter/MidiConverter.cs changed 3 times in last 90 days, max complexity 54. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: samples/NAudioConsoleTest/Wasapi/Tests/WasapiPlayFileTest.cs samples/NAudioConsoleTest/Wasapi/Tests/WasapiPlayFileTest.cs— samples/NAudioConsoleTest/Wasapi/Tests/WasapiPlayFileTest.cs changed 5 times in last 90 days, max complexity 27. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: src/NAudio.Wasapi/WasapiOut.cs src/NAudio.Wasapi/WasapiOut.cs— src/NAudio.Wasapi/WasapiOut.cs changed 7 times in last 90 days, max complexity 18. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecordToWavFileTest.cs samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecordToWavFileTest.cs— samples/NAudioConsoleTest/Wasapi/Tests/WasapiRecordToWavFileTest.cs changed 6 times in last 90 days, max complexity 20. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs— samples/NAudioConsoleTest/Asio/Tests/AsioDuplexPassthroughTest.cs changed 3 times in last 90 days, max complexity 31. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs— samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs changed 3 times in last 90 days, max complexity 30. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/NAudio.Asio/AsioSampleConvertor.cs src/NAudio.Asio/AsioSampleConvertor.cs— src/NAudio.Asio/AsioSampleConvertor.cs changed 3 times in last 90 days, max complexity 28. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/NAudio.Midi/Midi/MidiFile.cs src/NAudio.Midi/Midi/MidiFile.cs— src/NAudio.Midi/Midi/MidiFile.cs changed 3 times in last 90 days, max complexity 25. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
No assertions: HasConnectInputToOutputMethod tests/NAudio.Core.Tests/WaveStreams/MultiplexingSampleProviderTests.cs:129— Test method exercises code but verifies nothing — add an assertion.
No assertions: HasFindByShortNameMethod tests/NAudio.Windows.Tests/Acm/AcmDriverTests.cs:38— Test method exercises code but verifies nothing — add an assertion.
No assertions: CanConvertALawToSuggestedPcm tests/NAudio.Windows.Tests/Acm/WaveFormatConversionStreamTests.cs:88— Test method exercises code but verifies nothing — add an assertion.
No assertions: CanConvertMuLawToSuggestedPcm tests/NAudio.Windows.Tests/Acm/WaveFormatConversionStreamTests.cs:97— Test method exercises code but verifies nothing — add an assertion.
No assertions: CanCreateResamplerMediaObject tests/NAudio.Windows.Tests/Dmo/ResamplerDmoTests.cs:22— Test method exercises code but verifies nothing — add an assertion.
No assertions: ResamplerCanCallProcessInput tests/NAudio.Windows.Tests/Dmo/ResamplerDmoTests.cs:133— Test method exercises code but verifies nothing — add an assertion.
No assertions: CanFindDefaultWaveIn tests/NAudio.Windows.Tests/Mixer/MixerApiTests.cs:30— Test method exercises code but verifies nothing — add an assertion.
TooManyMethods: Vst3Plugin src/NAudio.Vst3/Vst3Plugin.cs:0— TooManyMethods — 1025 significant lines (blank, comment-only and punctuation-only lines excluded), 74 methods. 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:0— TooManyMethods — 237 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. 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:0— TooManyMethods — 459 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. 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:0— TooManyMethods — 112 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. 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:0— TooManyMethods — 278 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. 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 (10 lines × 2) src/NAudio.Asio/AsioAudioCapturedEventArgs.cs:72— src/NAudio.Asio/AsioAudioCapturedEventArgs.cs:72-81 | src/NAudio.Asio/AsioProcessBuffers.cs:86-95 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 (10 lines × 2) src/NAudio.Asio/AsioSampleConvertor.cs:471— src/NAudio.Asio/AsioSampleConvertor.cs:471-480 | src/NAudio.Asio/AsioSampleConvertor.cs:525-535 — 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 (10 lines × 2) src/NAudio.Core/Codecs/G722Codec.cs:235— src/NAudio.Core/Codecs/G722Codec.cs:235-244 | src/NAudio.Core/Codecs/G722Codec.cs:268-277 — 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.Core/Effects/ChorusEffect.cs:79— src/NAudio.Core/Effects/ChorusEffect.cs:79-88 | src/NAudio.Core/Effects/FlangerEffect.cs:80-89 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/NAudio.Core/Effects/ChorusEffect.cs:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/NAudio.Core/Effects/GateEffect.cs:95— src/NAudio.Core/Effects/GateEffect.cs:95-104 | src/NAudio.Core/Effects/TransientShaperEffect.cs:57-67 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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:95` 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 (8 lines × 2) src/NAudio.Core/Codecs/G722Codec.cs:411— src/NAudio.Core/Codecs/G722Codec.cs:411-418 | src/NAudio.Core/Codecs/G722Codec.cs:448-455 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/NAudio.Core/Dsp/BiQuadFilter.cs:156— src/NAudio.Core/Dsp/BiQuadFilter.cs:156-164 | src/NAudio.Core/Dsp/BiQuadFilter.cs:185-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:84— src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:84-91 | src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:92-99 — 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/Mp3/XingHeader.cs:92` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/NAudio.Core/Wave/SampleProviders/Pcm24BitToSampleProvider.cs:27— src/NAudio.Core/Wave/SampleProviders/Pcm24BitToSampleProvider.cs:27-34 | src/NAudio.Core/Wave/SampleProviders/Pcm32BitToSampleProvider.cs:27-34 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) src/NAudio.WinForms/WaveOutWindow.cs:251— src/NAudio.WinForms/WaveOutWindow.cs:251-258 | src/NAudio.WinMM/WaveOut.cs:293-300 — 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 `src/NAudio.WinForms/WaveOutWindow.cs:251` 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.
Low cohesion: SamplerRegion (LCOM4 8) src/NAudio.Sampler/SamplerRegion.cs:34— SamplerRegion's methods form 8 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: AsioRecordingPanel (LCOM4 7) samples/NAudioDemo/AsioRecordingDemo/AsioRecordingPanel.cs:10— AsioRecordingPanel's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: AudioFileInspectorForm (LCOM4 5) samples/AudioFileInspector/AudioFileInspectorForm.cs:11— AudioFileInspectorForm's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: MainForm (LCOM4 5) samples/MidiFileConverter/MainForm.cs:12— MainForm's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: MixDiffForm (LCOM4 5) samples/MixDiff/MixDiffForm.cs:11— MixDiffForm's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
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 begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) samples/NAudioWpfDemo/Vst3HostDemo/Vst3HostDemoViewModel.cs:341— samples/NAudioWpfDemo/Vst3HostDemo/Vst3HostDemoViewModel.cs:341-352 | samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeEffectViewModel.cs:398-409 — 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/Vst3HostDemo/Vst3HostDemoViewModel.cs:341` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/NAudio.Asio/AsioDevice.cs:687— src/NAudio.Asio/AsioDevice.cs:687-698 | src/NAudio.Asio/AsioDevice.cs:733-745 — 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/AsioDevice.cs:687` 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.Vst3/Vst3InstrumentSampleProvider.cs:116— src/NAudio.Vst3/Vst3InstrumentSampleProvider.cs:116-127 | src/NAudio.Vst3/Vst3MidiInstrument.cs:199-210 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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 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.
Change coupling: AudioClient.cs ↔ WasapiRecorderBuilder.cs src/NAudio.Wasapi/CoreAudioApi/AudioClient.cs— `src/NAudio.Wasapi/CoreAudioApi/AudioClient.cs` and `src/NAudio.Wasapi/WasapiRecorderBuilder.cs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: WasapiPlayer.cs ↔ WasapiRecorderBuilder.cs src/NAudio.Wasapi/WasapiPlayer.cs— `src/NAudio.Wasapi/WasapiPlayer.cs` and `src/NAudio.Wasapi/WasapiRecorderBuilder.cs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
Duplicated block (13 lines × 2) samples/AudioFileInspector/FileInspectors/SoundFontInspector.cs:31— samples/AudioFileInspector/FileInspectors/SoundFontInspector.cs:31-43 | samples/AudioFileInspector/FileInspectors/SoundFontInspector.cs:49-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 `samples/AudioFileInspector/FileInspectors/SoundFontInspector.cs:31` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/NAudio.Dmo/Dmo/MediaObject.cs:71— src/NAudio.Dmo/Dmo/MediaObject.cs:71-83 | src/NAudio.Dmo/Dmo/MediaObject.cs:94-106 — 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:71` 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 (11 lines × 2) samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:148— samples/NAudioWpfDemo/Vst3MidiFileDemo/Vst3MidiFileDemoViewModel.cs:148-158 | samples/NAudioWpfDemo/Vst3RealtimeInstrumentDemo/Vst3RealtimeInstrumentViewModel.cs:239-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:148` 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 lines × 2) src/NAudio.WinForms/WaveInWindow.cs:136— src/NAudio.WinForms/WaveInWindow.cs:136-146 | src/NAudio.WinMM/WaveIn.cs:82-92 — 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 `src/NAudio.WinForms/WaveInWindow.cs:136` 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:187— src/NAudio.Asio/AsioSampleConvertor.cs:187-196 | src/NAudio.Asio/AsioSampleConvertor.cs:231-240 | src/NAudio.Asio/AsioSampleConvertor.cs:418-427 — 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:187` 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:299— src/NAudio.Asio/AsioSampleConvertor.cs:299-309 | src/NAudio.Asio/AsioSampleConvertor.cs:498-508 | src/NAudio.Asio/AsioSampleConvertor.cs:553-562 — 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.
Off the main sequence: NAudio.Core — NAudio.Core: abstractness 0.10, instability 0.00, distance 0.90 — 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) — NAudio.Midi(net9.0): abstractness 0.09, instability 0.14, distance 0.76 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
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 51) src/NAudio.Core/Dsp/WdlResampler.cs:229— WdlResampler.ResampleOut has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
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.
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:36— 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.
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.
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.
MidiFile.MidiFile.ctor (cyclomatic 25) src/NAudio.Midi/Midi/MidiFile.cs:54— MidiFile.MidiFile.ctor 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.
SamplerVoice.RenderSpan (cyclomatic 25) src/NAudio.Sampler/SamplerVoice.cs:530— SamplerVoice.RenderSpan 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:163— 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.
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.
WasapiPlayer.GetSupportedExclusiveFormat (cyclomatic 22) src/NAudio.Wasapi/WasapiPlayer.cs:388— 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.
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.
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:503— 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:159— 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.
Mp3Frame.IsValidHeader (cyclomatic 19) src/NAudio.Core/FileFormats/Mp3/Mp3Frame.cs:183— Mp3Frame.IsValidHeader 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.
WaveFileChunkReader.ReadWaveHeader (cyclomatic 18) src/NAudio.Core/Wave/WaveStreams/WaveFileChunkReader.cs:35— WaveFileChunkReader.ReadWaveHeader 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.
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.
WasapiOut.PlayThread (cyclomatic 18) src/NAudio.Wasapi/WasapiOut.cs:95— WasapiOut.PlayThread 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.
XingHeader.LoadXingHeader (cyclomatic 17) src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:58— XingHeader.LoadXingHeader has cyclomatic complexity 17 (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.
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.
WasapiPlayer.PlayThread (cyclomatic 17) src/NAudio.Wasapi/WasapiPlayer.cs:742— WasapiPlayer.PlayThread 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:274— 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.
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.
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.
D11 · Test Reliability· Test reliability not measured · ×1
Test reliability not measured — no test run produced results — 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.
BarePragmaDisable src/NAudio.Dmo/Dmo/MediaParamInfo.cs:11— #pragma warning disable 0649 — the disable has no matching restore, 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. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
WdlResampler.ResampleOut (cognitive 128) src/NAudio.Core/Dsp/WdlResampler.cs:229— WdlResampler.ResampleOut has cognitive complexity 128 (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.
MidiConverter.ConvertMidi (cognitive 113) samples/MidiFileConverter/MidiConverter.cs:157— MidiConverter.ConvertMidi has cognitive complexity 113 (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.
DahdsrEnvelope.Advance (cognitive 95) src/NAudio.Core/Dsp/DahdsrEnvelope.cs:319— DahdsrEnvelope.Advance has cognitive complexity 95 (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.
MidiFile.MidiFile.ctor (cognitive 61) src/NAudio.Midi/Midi/MidiFile.cs:54— MidiFile.MidiFile.ctor has cognitive complexity 61 (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 60) src/NAudio.Sampler/SamplerVoice.cs:530— SamplerVoice.RenderSpan has cognitive complexity 60 (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.
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, 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.
AsioSampleConvertor.SelectSampleConvertor (cognitive 48) src/NAudio.Asio/AsioSampleConvertor.cs:19— AsioSampleConvertor.SelectSampleConvertor has cognitive complexity 48 (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.
AsioLegacyDuplexPassthroughTest.NativePassthroughChannel (cognitive 45) samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:163— 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.
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, 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.
AsioLegacyDuplexPassthroughTest.Run (cognitive 42) samples/NAudioConsoleTest/Asio/Tests/AsioLegacyDuplexPassthroughTest.cs:36— 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, 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.
DirectSoundOut.PlaybackThreadFunc (cognitive 42) src/NAudio.Dmo/DirectSound/DirectSoundOut.cs:480— 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.
WaveFileChunkReader.ReadWaveHeader (cognitive 39) src/NAudio.Core/Wave/WaveStreams/WaveFileChunkReader.cs:35— WaveFileChunkReader.ReadWaveHeader has cognitive complexity 39 (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.
WasapiPlayFileTest.Run (cognitive 36) samples/NAudioConsoleTest/Wasapi/Tests/WasapiPlayFileTest.cs:32— WasapiPlayFileTest.Run has cognitive complexity 36 (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.PlayThread (cognitive 36) src/NAudio.Wasapi/WasapiOut.cs:95— WasapiOut.PlayThread has cognitive complexity 36 (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.
Mp3Frame.IsValidHeader (cognitive 35) src/NAudio.Core/FileFormats/Mp3/Mp3Frame.cs:183— Mp3Frame.IsValidHeader has cognitive complexity 35 (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:503— 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:388— 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.
WasapiPlayer.PlayThread (cognitive 31) src/NAudio.Wasapi/WasapiPlayer.cs:742— WasapiPlayer.PlayThread has cognitive complexity 31 (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.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.
BatchRunner.RenderMarkdown (cognitive 28) samples/NAudioConsoleTest/Shared/Testing/BatchRunner.cs:229— BatchRunner.RenderMarkdown has cognitive complexity 28 (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.
WasapiExclusiveDetailedScanTest.Run (cognitive 28) samples/NAudioConsoleTest/Wasapi/Tests/WasapiExclusiveDetailedScanTest.cs:21— WasapiExclusiveDetailedScanTest.Run has cognitive complexity 28 (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.
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, 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.
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.
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, 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.
WinMmPlayFileTest.Run (cognitive 26) samples/NAudioConsoleTest/WinMM/Tests/WinMmPlayFileTest.cs:29— WinMmPlayFileTest.Run has cognitive complexity 26 (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.
AsioAudioAvailableEventArgs.GetAsInterleavedSamples (cognitive 26) src/NAudio.Asio/AsioAudioAvailableEventArgs.cs:56— 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:20— DiagnosticsRenderer.ToMarkdown 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.
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, 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.
MultibandCompressorEffect.ProcessBlock (cognitive 25) src/NAudio.Core/Effects/MultibandCompressorEffect.cs:79— 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.
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.
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.
WasapiOut.Init (cognitive 24) src/NAudio.Wasapi/WasapiOut.cs:362— WasapiOut.Init has cognitive complexity 24 (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.
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:238— AlsaOut.PlaybackLoop has cognitive complexity 23 (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.
CompressorEffect.ProcessBlock (cognitive 23) src/NAudio.Core/Effects/CompressorEffect.cs:113— CompressorEffect.ProcessBlock has cognitive complexity 23 (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.
AiffFileReader.ReadAiffHeader (cognitive 23) src/NAudio.Core/Wave/WaveStreams/AiffFileReader.cs:60— AiffFileReader.ReadAiffHeader has cognitive complexity 23 (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.
Mp3FileReaderBase.Read (cognitive 23) src/NAudio.Core/Wave/WaveStreams/Mp3FileReaderBase.cs:475— Mp3FileReaderBase.Read 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.
WaveIn.DoRecording (cognitive 23) src/NAudio.WinMM/WaveIn.cs:143— WaveIn.DoRecording has cognitive complexity 23 (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.
FdnReverbEffect.ProcessBlock (cognitive 22) src/NAudio.Core/Effects/FdnReverbEffect.cs:91— 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:496— 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.
CueList.CueList.ctor (cognitive 22) src/NAudio.Core/Wave/WaveStreams/CueList.cs:188— CueList.CueList.ctor has cognitive complexity 22 (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.
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, 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.
BitCrusherEffect.ProcessBlock (cognitive 21) src/NAudio.Core/Effects/BitCrusherEffect.cs:83— BitCrusherEffect.ProcessBlock has cognitive complexity 21 (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.
MultiplexingSampleProvider.Read (cognitive 21) src/NAudio.Core/Wave/SampleProviders/MultiplexingSampleProvider.cs:80— 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:101— 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.
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:48— 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.
MidiEventCollection.PrepareForExport (cognitive 20) src/NAudio.Midi/Midi/MidiEventCollection.cs:226— MidiEventCollection.PrepareForExport has cognitive complexity 20 (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.
MediaFoundationReader.ReadNextDecoderBuffer (cognitive 20) src/NAudio.Wasapi/MediaFoundationReader.cs:302— 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.
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.
WdlResampler.SetMode (cognitive 19) src/NAudio.Core/Dsp/WdlResampler.cs:73— 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:528— WdlResampler.BuildLowPass has cognitive complexity 19 (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.
MultiplexingWaveProvider.MultiplexingWaveProvider.ctor (cognitive 19) src/NAudio.Core/Wave/WaveProviders/MultiplexingWaveProvider.cs:38— MultiplexingWaveProvider.MultiplexingWaveProvider.ctor 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.
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:419— MediaFoundationReader.Reposition has cognitive complexity 19 (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.
WaveOut.DoPlayback (cognitive 19) src/NAudio.WinMM/WaveOut.cs:163— WaveOut.DoPlayback has cognitive complexity 19 (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.
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, 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.
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.
AsioOut.driver_BufferUpdate (cognitive 18) src/NAudio.Asio/AsioOut.cs:280— AsioOut.driver_BufferUpdate has cognitive complexity 18 (threshold 15). Of this number, 14 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.
InterpolatingSampleReader.ReadContiguous (cognitive 18) src/NAudio.Core/Dsp/InterpolatingSampleReader.cs:274— 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:159— 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.
XingHeader.LoadXingHeader (cognitive 18) src/NAudio.Core/FileFormats/Mp3/XingHeader.cs:58— XingHeader.LoadXingHeader 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.
MidiFileSequence.FromMidiFile (cognitive 18) src/NAudio.Midi/Sequencing/MidiFileSequence.cs:50— MidiFileSequence.FromMidiFile 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.
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.
SfzParser.Flatten (cognitive 17) src/NAudio.Core/FileFormats/Sfz/SfzParser.cs:235— 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.
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.
WaveViewer.OnPaint (cognitive 17) src/NAudio.WinForms/Gui/WaveViewer.cs:109— WaveViewer.OnPaint has cognitive complexity 17 (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.
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.
MultiplexingSampleProvider.MultiplexingSampleProvider.ctor (cognitive 16) src/NAudio.Core/Wave/SampleProviders/MultiplexingSampleProvider.cs:26— MultiplexingSampleProvider.MultiplexingSampleProvider.ctor 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.
WaveChannel32.Read (cognitive 16) src/NAudio.Core/Wave/WaveStreams/WaveChannel32.cs:139— 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.
MidiFile.SeekToRmidMidiData (cognitive 16) src/NAudio.Midi/Midi/MidiFile.cs:233— MidiFile.SeekToRmidMidiData has cognitive complexity 16 (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.
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.
FileTooLong: NAudio.Vst3/Vst3Plugin.cs src/NAudio.Vst3/Vst3Plugin.cs:0— FileTooLong — 1039 significant lines (blank, comment-only and punctuation-only lines excluded). 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.
ClassTooLong: SamplerVoice src/NAudio.Sampler/SamplerVoice.cs:0— ClassTooLong — 429 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. 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.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 9 floating ref(s) across 3 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.
D36 · Supply-chain Provenance & Signing· PR-triggered workflow without a permissions block · ×1
PR-triggered workflow without a permissions block — 1 workflow(s) triggered by pull_request declare no `permissions:` block (build.yml) and so run with the repository's default GITHUB_TOKEN scope, while 2 sibling workflows in the same repository are already scoped. Pull-request runs build the least-trusted code in the repository; give each of these workflows its own least-privilege block — `permissions: {contents: read}` at the top of the workflow, widened per job only where a job genuinely writes.
Duplicated block (20 lines × 2) samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:211— samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:211-230 | samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeAudioEngine.cs:231-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:211` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) samples/AudioFileInspector/AudioFileInspectorForm.cs:164— samples/AudioFileInspector/AudioFileInspectorForm.cs:164-181 | samples/MidiFileConverter/MainForm.cs:349-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:164` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:128— samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:128-143 | samples/NAudioWpfDemo/Vst3RealtimeEffectDemo/Vst3RealtimeAudioEngine.cs:128-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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/NAudioWpfDemo/RealtimeEffectsDemo/RealtimeAudioEngine.cs:128` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/NAudio.Vst3/Hosting/Vst3HostMessage.cs:65— src/NAudio.Vst3/Hosting/Vst3HostMessage.cs:65-79 | src/NAudio.Vst3/Hosting/Vst3MemoryStream.cs:161-175 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/NAudio.Vst3/Hosting/Vst3HostMessage.cs:65` 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 (10 lines × 4) src/NAudio.Asio/AsioSampleConvertor.cs:275— src/NAudio.Asio/AsioSampleConvertor.cs:275-284 | src/NAudio.Asio/AsioSampleConvertor.cs:347-357 | src/NAudio.Asio/AsioSampleConvertor.cs:393-403 | src/NAudio.Asio/AsioSampleConvertor.cs:445-454 — 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.
Duplicated block (8 lines × 3) src/NAudio.Core/Dsp/BiQuadFilter.cs:361— src/NAudio.Core/Dsp/BiQuadFilter.cs:361-368 | src/NAudio.Core/Dsp/BiQuadFilter.cs:386-393 | src/NAudio.Core/Dsp/BiQuadFilter.cs:436-443 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
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 (7 lines × 2) src/NAudio.Core/FileFormats/Sfz/SfzMappedRegion.cs:439— src/NAudio.Core/FileFormats/Sfz/SfzMappedRegion.cs:439-445 | src/NAudio.Core/FileFormats/Sfz/SfzMappedRegion.cs:525-531 — 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 (6 lines × 2) src/NAudio.Core/Dsp/BiQuadFilter.cs:478— src/NAudio.Core/Dsp/BiQuadFilter.cs:478-483 | src/NAudio.Core/Dsp/BiQuadFilter.cs:505-510 — 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/Dsp/BiQuadFilter.cs:478` 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/ChorusEffect.cs:56— src/NAudio.Core/Effects/ChorusEffect.cs:56-60 | src/NAudio.Core/Effects/FlangerEffect.cs:57-61 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/NAudio.Core/Effects/ChorusEffect.cs:56` 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.
Coverage not measured — The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. No coverage collector was found in your CI either, so there is no existing report to hand us: add a coverage collector to your test run and commit (or publish) its Cobertura/OpenCover/lcov output anywhere in the repo, or make the suite runnable in-image, and real coverage will be measured.
Low: plaintext-http-link samples/AudioFileInspector/audio_file_inspector.html:39— This link points to a plaintext HTTP URL. Prefer an encrypted HTTPS URL if possible.
Low: plaintext-http-link samples/AudioFileInspector/audio_file_inspector.html:45— This link points to a plaintext HTTP URL. Prefer an encrypted HTTPS URL if possible.
Low: plaintext-http-link samples/AudioFileInspector/audio_file_inspector.html:72— This link points to a plaintext HTTP URL. Prefer an encrypted HTTPS URL if possible.
Low: plaintext-http-link samples/MidiFileConverter/midi_file_converter.html:9— This link points to a plaintext HTTP URL. Prefer an encrypted HTTPS URL if possible.
Low: plaintext-http-link samples/MidiFileConverter/midi_file_converter.html:11— This link points to a plaintext HTTP URL. Prefer an encrypted HTTPS URL if possible.
Low: plaintext-http-link samples/MidiFileConverter/midi_file_converter.html:26— This link points to a plaintext HTTP URL. Prefer an encrypted HTTPS URL if possible.
Low: plaintext-http-link samples/MidiFileConverter/midi_file_converter.html:32— This link points to a plaintext HTTP URL. Prefer an encrypted HTTPS URL if possible.
Low: plaintext-http-link samples/MidiFileConverter/midi_file_converter.html:270— This link points to a plaintext HTTP URL. Prefer an encrypted HTTPS URL if possible.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 53 significant file(s) lose their only recent owner: src/NAudio.Asio/AsioDevice.cs, src/NAudio.Wasapi/WasapiPlayer.cs, src/NAudio.Wasapi/WasapiRecorder.cs, src/NAudio.Dmo/DirectSound/DirectSoundOut.cs, src/NAudio.Wasapi/CoreAudioApi/AudioClient.cs, src/NAudio.Core/Dsp/WdlResampler.cs, src/NAudio.Core/Wave/WaveOutputs/WaveFileWriter.cs, src/NAudio.Wasapi/MediaFoundationEncoder.cs (+45 more). Pair on, review, or document these before any departure.
No ADRs found — No ADRs found at common paths; consider documenting architectural decisions in Docs/ADL/ or similar.
D23 · Boundary Type-Coupling· Bounded contexts not declared · ×1
Bounded contexts not declared — At 100k LoC across 30 projects the codebase is large and multi-module, so explicit bounded contexts are needed. 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"]`.
Scattered collaborators — 85 % 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.
No build provenance — No SLSA provenance generation or build attestation found in CI — nothing binds a released artifact to the build that produced it, so a consumer cannot tell your artifact from a substituted one. On GitHub Actions, `actions/attest-build-provenance` (or slsa-github-generator) emits one from the job's own OIDC identity; elsewhere, run `cosign attest` over the released artifact from the release pipeline and publish the attestation beside it.
No artifact signing — No artifact signing found in CI — sign your released artifacts with whatever your ecosystem ships (a GPG/minisign detached signature — or `cosign sign-blob` — over the release archives, or over a checksum file published alongside them, Authenticode via signtool, or `dotnet nuget sign` for packages) so consumers can verify what you built.
D36 · Supply-chain Provenance & Signing· No SBOM · ×1
No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (`sbom-tool generate` (install it with `dotnet tool install --global Microsoft.Sbom.DotNetTool`) or `dotnet CycloneDX` over the solution, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Publish it as a release asset (`*.spdx.json` / `*.cdx.json`) so consumers can see what they are installing.
IL efficiency: 29 authored method(s) exceed the IL budget src/NAudio.Core/Dsp/WdlResampler.cs:231— 29 of 4791 first-party methods compile to oversized IL bodies (> 250 instructions); worst: NAudio.Dsp.WdlResampler.ResampleOut @ src/NAudio.Core/Dsp/WdlResampler.cs:231, 870 IL instructions; large bodies don't JIT-inline, which pulled this dimension to 9.9/10; splitting the hottest bodies recovers the most.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies 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.
0
—
Run 019fd317-f7e6-7a83-87a5-72702bf38904 · 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 — 6 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 with a deliberately specific classifier (the same one the GDPR dimensions use, so CardDefinition or FileName don't trip); informational — it feeds no score.
Issues: 30 · Warnings: 313 · Recommendations: 28 · Info: 30 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 05-08-2026 @ 18:03 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.