Public report of Lake1059/FFmpegFreeUI, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 26 October 2026, 16:51 UTC · Survey ID cd_47df299a99dd43339f1d224fba7e836f
Lake1059/FFmpegFreeUI
Measured 26 October 2026, 16:49 UTC, at code version becda5b
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Test distribution is not measured: No automated tests.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreProvisionalNo change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 34,975 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 34
Findings by how serious they are
131 critical271 serious16 minor
40 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 16:49 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The code didn't build, so the score is provisional
Watchdog couldn't build the code: the build stopped with 2018 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: BC30002: Type 'ModernComboBox' is not defined.; BC30002: Type 'ModernListBox.ItemForeColorEventArgs' is not defined.; BC30002: Type 'LakeUI.ModernPanel' is not defined.; BC30002: Type 'AgentRoom.LinkClickedEventArgs' is not defined.; BC30002: Type 'LakeUI.AgentRoom.ChatItem' is not defined.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
40of 40 dimensions measured by tools.
397of 418 findings point to an exact file and line, so you can open each one in the code. The other 21 concern the repository as a whole, such as missing documentation.
40dimensions across 6 lenses, read from 34,975 lines of product code in 2 projects.
Lake1059/FFmpegFreeUI has a provisional result, because the code didn't build. Its score is held back in part because the project has no automated tests. It scores 43 out of 100, and the ratings may change once the code builds. 20 of its 131 critical findings are security problems in the build pipeline.
Production Readiness, at 34, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 8 points. Recording design decisions is another step, worth about 2 points. Raising Production Readiness to 70 would lift the score to about 51.
Eight secrets can leak from the build pipeline. Four pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline, and 109 errors are caught and ignored, so failures can go unnoticed. Limiting each secret to its own step, passing outside input through environment variables and handling or logging the ignored errors would close these risks. Pinning each tool to an exact version would fix the four pipeline tools referenced by a changeable name, and correcting the flagged pipeline settings would deal with the four weaknesses in the build pipeline's configuration. The analysis rule switched off in the settings needs switching back on in the settings file.
The product code is 34,975 lines, about €32,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 3 findings
These 3 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one.
Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb
Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €32,000 · Estimate
Cost to rebuild
€11,000 to €53,000, for 176 to 559 hours of work, about 0.2 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 43. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 34,975 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 8 points · Low effort · Code Coverage
2
Resolve the 1 No tests found finding(s) in Test Distribution.
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 2 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: BC30002: Type 'ModernComboBox' is not defined.; BC30002: Type 'ModernListBox.ItemForeColorEventArgs' is not defined.; BC30002: Type 'LakeUI.ModernPanel' is not defined.; BC30002: Type 'AgentRoom.LinkClickedEventArgs' is not defined.; BC30002: Type 'LakeUI.AgentRoom.ChatItem' is not defined.
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €32,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 34 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.4 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 30,055 lines over the last 90 days, which is about 121,890 lines a year. At that pace, the extra work comes to an estimated 6.1 to 40.6 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
At a glance — Code Health · 47% · Weak · gated by D18 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
20
High / Critical
A03:2025 — Software Supply Chain Failures
7
Medium
Roadmap
Begin by addressing the critical gaps in testing by resolving the single code coverage and test distribution issues to ensure foundational quality. Simultaneously, tackle the significant backlog of empty catch blocks, prioritizing the Form_v6_集成工具_质量评测.vb, Agent本地工具_进程_v6.vb, and 界面主题_v6.vb files to reduce explicit technical debt. Finally, establish basic release hygiene by maintaining a changelog and document key architectural decisions through an Architectural Decision Record to improve transparency and traceability.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No automated tests finding(s) in Code Coverage.
Per-file score 0–10 — a quality signature. Of 79 files carrying findings, judged against the Production bar: 19% slop · 63% mixed · 18% near-clean.
File
Score
Band
Worst signal
FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb
2.2
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb
2.3
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb
2.3
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/功能/界面主题_v6.vb
2.3
Slop
Explicit Debt: EmptyCatchBlock
Updater/Program.vb
2.3
Slop
Explicit Debt: EmptyCatchBlock
REDACTED
2.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
2.3
Slop
Static Analysis (SAST): High: REDACTED
FFmpegFreeUI/功能/Module1.vb
2.3
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/功能/设置_v6.vb
2.6
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/界面 v6 主页面/Form_v6_编码队列_任务日志.vb
2.7
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/功能/编码任务_v6.vb
2.8
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/功能/Agent 智能体/Agent工具封装_v6.vb
3.2
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/界面 v6 主页面/Form_v6_调试播放器.vb
3.3
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/功能/编码队列_v6.vb
3.4
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_预设管理.vb
3.8
Slop
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_文件网络_v6.vb
4.8
Mixed
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/集成工具/比特率可视化数据核心.vb
4.8
Mixed
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/功能/启动参数响应_v6.vb
4.8
Mixed
Explicit Debt: EmptyCatchBlock
FFmpegFreeUI/功能/Agent 智能体/Agent能力缓存_v6.vb
4.9
Mixed
Explicit Debt: EmptyCatchBlock
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 131
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 271
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 16
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 40
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 40 of 40 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 40 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, 397 of 418 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (34,975 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
PF3 Async & latency hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No function of a language this check models was read, so there was no async code to examine. That is a limit of the analyzer on this repository, not a finding about it.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X10 Duplicated predicate — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
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.
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.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
54 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was 预设管理_v6.显示参数总览 at 121. A further 20 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 Form_v6_参数面板_视频编码器.是质量相关参数 at 70 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_视频编码器.vb (Form_v6_参数面板_视频编码器.是质量相关参数 at 70), FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_画面区域选择窗口.vb (Form_v6_参数面板_画面区域选择窗口.是图片扩展 at 34), FFmpegFreeUI/功能/视频编码器数据库_v6.vb (视频编码器数据库_v6.获取默认无损模式说明 at 20), FFmpegFreeUI/功能/Agent 智能体/Agent技能资料库_v6.vb (Agent技能资料库_v6.读取资料 at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 49 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with 预设管理_v6.显示参数总览 (cyclomatic 121), 预设管理_v6.生成滤镜图 (cyclomatic 114), AgentLocalTools.ExecuteAsync (cyclomatic 79). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 82 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with 预设管理_v6.显示参数总览 (cognitive 178), 预设管理_v6.生成滤镜图 (cognitive 150), AgentLocalTools.ExecuteAsync (cognitive 77). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 4.5 to about 6.0/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes4.7 / 10Weak✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 25 TooManyMethods finding(s) in God Classes — start with 预设区段_剪辑自定义_v6.vb, Agent页面控制器_v6.vb, Form_v6_集成工具_质量评测.vb. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 20 FileTooLong finding(s) in God Classes — start with Form_v6_集成工具_质量评测.vb, Agent端点客户端_v6.vb, 编码队列_v6.vb. — One of this dimension's main actionable groups (20 warning-level).
Resolve the 13 MethodTooLong finding(s) in God Classes — start with 预设面板总览_参数文本_v6.vb (2), Agent本地工具_v6.vb (2), 预设区段_画面帧_v6.vb (2). — One of this dimension's main actionable groups (13 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
48 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 26 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Form_v6_集成工具_抽流.vb, 预设区段_质量色彩音频_v6.vb, Form_v6_编码队列_任务日志.vb. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Agent端点客户端_v6.vb, Agent会话Json升级器_v6.vb, Form_v6_媒体流选择器.vb. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with 视频编码器数据库_v6.vb, Form_v6_参数面板_烧录字幕.vb, Agent能力缓存_v6.vb. — One of this dimension's main actionable groups (4 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
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.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
No automated tests — no test code was found in this repository.
No automated tests
What to do
Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution0.0 / 10Critical✓ 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.
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.
0 of 159 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 7 direct `PackageReference`(s), and 152 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with Agent本地工具_v6.vb, 预设面板总览_参数文本_v6.vb, 界面主题_v6.vb. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor3.2 / 10Weak✓ 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.
78 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is FFmpegFreeUI/功能/视频编码器数据库_v6.vb. Counted over 115 of the 146 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
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).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D17 · Explicit Debt4.1 / 10Weak✓ Tool-verified
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
Resolve the 109 EmptyCatchBlock finding(s) in Explicit Debt — start with Form_v6_集成工具_质量评测.vb (18), Agent本地工具_进程_v6.vb (10), 界面主题_v6.vb (9). — One of this dimension's main actionable groups (109 issue-level).
Resolve the 1 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig. — One of this dimension's main actionable groups (1 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape3.0 / 10Weak✓ Tool-verified
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.
2 projects, 146 source files, 34975 hand-written lines of code (34975 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 31130 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 0 inter-project edges (build failed).
Build failed
What to do
Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
1 of 2 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
61 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
20 finding(s): 0 critical, 20 high, 0 medium, 0 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 115 of the 146 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with Agent本地工具_v6.vb, Agent技能资料库_v6.vb. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether 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.
~35k production LoC (292 types) across 2 project(s) / 6 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
What to do
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Other · 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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 2 of 2 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
What to do
Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
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.
Do you agree with this assessment?
P1 · CI/CD gates6.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean as a CI step. What was searched, so you can tell an absence from a miss: the 6250 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 13 use(s) across 39,708 production line(s) (~0.3/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Visual Basic: on hot paths, work through Span(Of T)/Memory(Of T) (AsSpan/AsMemory) instead of copies, rent buffers from ArrayPool(Of T), return ValueTask from completions that are usually synchronous, write through IBufferWriter(Of T), and presize List/StringBuilder/Dictionary.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 1 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 5 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 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
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
D21 Naming Consistency — Naming consistency is measured on C# only; Visual Basic not measured.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D24 Comment Value — 122 of 147 comment blocks were not judged (119 in a non-Latin script, 3 in a language other than English): redundancy is judged by word overlap with the code's identifiers, which cannot be measured across languages.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — 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
X10 Duplicated predicate — 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
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — 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
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
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
X5 Nullable reference types — 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 — 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
X7 Silent fallback defaults — 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
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 FFmpegFreeUI/功能/Agent 智能体/Agent会话存储_v6.vb:340— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent工具封装_v6.vb:472— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent工具封装_v6.vb:486— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent工具封装_v6.vb:504— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_文件网络_v6.vb:157— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:231— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:235— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:239— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:386— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:394— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:405— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:409— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:594— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:600— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:616— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:941— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent能力缓存_v6.vb:200— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent能力缓存_v6.vb:208— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Agent 智能体/Agent通用工具_v6.vb:17— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Module1.vb:120— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Module1.vb:336— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Module1.vb:341— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Module1.vb:359— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Module1.vb:370— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock FFmpegFreeUI/功能/Module1.vb:430— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
AnalyzerSeverityNone .editorconfig:4— CA1806 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
TooManyMethods: 预设管理_v6 FFmpegFreeUI/功能/预设系统/预设区段_剪辑自定义_v6.vb— TooManyMethods — 4189 significant lines (blank, comment-only and punctuation-only lines excluded), 267 methods. The bar is 30 methods; this is 237 over it, 8.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Agent页面控制器_v6 FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_v6.vb— TooManyMethods — 2538 significant lines (blank, comment-only and punctuation-only lines excluded), 165 methods. The bar is 30 methods; this is 135 over it, 5.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Form_v6_集成工具_质量评测 FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb— TooManyMethods — 2139 significant lines (blank, comment-only and punctuation-only lines excluded), 154 methods. The bar is 30 methods; this is 124 over it, 5.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AgentLocalTools FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb— TooManyMethods — 2399 significant lines (blank, comment-only and punctuation-only lines excluded), 92 methods. The bar is 30 methods; this is 62 over it, 3.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: 编码队列_v6 FFmpegFreeUI/功能/编码队列_v6.vb— TooManyMethods — 941 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 30 methods; this is 54 over it, 2.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AgentEndpointClient FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb— TooManyMethods — 968 significant lines (blank, comment-only and punctuation-only lines excluded), 68 methods. The bar is 30 methods; this is 38 over it, 2.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Form_v6_集成工具_混流 FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb— TooManyMethods — 719 significant lines (blank, comment-only and punctuation-only lines excluded), 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Form_v6_编码队列 FFmpegFreeUI/界面 v6 主页面/Form_v6_编码队列.vb— TooManyMethods — 503 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Form_v6_集成工具_抽流 FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb— TooManyMethods — 835 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Form_v6_参数面板_预设管理 FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_预设管理.vb— TooManyMethods — 588 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: 设置_v6 FFmpegFreeUI/功能/设置_v6.vb— TooManyMethods — 623 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Module1 FFmpegFreeUI/功能/Module1.vb— TooManyMethods — 571 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Program Updater/Program.vb— TooManyMethods — 725 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Agent工具封装_v6 FFmpegFreeUI/功能/Agent 智能体/Agent工具封装_v6.vb— TooManyMethods — 486 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: 编码任务_v6 FFmpegFreeUI/功能/编码任务_v6.vb— TooManyMethods — 738 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Form_v6_集成工具_Whisper生成字幕 FFmpegFreeUI/集成工具/Form_v6_集成工具_Whisper生成字幕.vb— TooManyMethods — 444 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. 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: Form_v6_参数面板_画面区域选择窗口 FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_画面区域选择窗口.vb— TooManyMethods — 392 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. 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: Form_v6_调试播放器 FFmpegFreeUI/界面 v6 主页面/Form_v6_调试播放器.vb— TooManyMethods — 374 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. 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: Form_v6_集成工具_合并 FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb— TooManyMethods — 294 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. 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: Form_v6_参数面板_烧录字幕 FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_烧录字幕.vb— TooManyMethods — 292 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. 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: Form_v6_准备文件 FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb— TooManyMethods — 364 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Form_v6_集成工具_比特率可视化 FFmpegFreeUI/集成工具/Form_v6_集成工具_比特率可视化.vb— TooManyMethods — 500 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: 视频编码器数据库_v6 FFmpegFreeUI/功能/视频编码器数据库_v6.vb— TooManyMethods — 697 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Form_v6_编码队列_任务日志 FFmpegFreeUI/界面 v6 主页面/Form_v6_编码队列_任务日志.vb— TooManyMethods — 478 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Form_v6_Agent FFmpegFreeUI/界面 v6 主页面/Form_v6_Agent.vb— TooManyMethods — 103 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: 集成工具/Form_v6_集成工具_质量评测.vb FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb— FileTooLong — 2146 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1646 over it, 4.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Agent 智能体/Agent端点客户端_v6.vb FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb— FileTooLong — 974 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 474 over it, 1.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 功能/编码队列_v6.vb FFmpegFreeUI/功能/编码队列_v6.vb— FileTooLong — 945 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 445 over it, 1.89× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 集成工具/Form_v6_集成工具_抽流.vb FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb— FileTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 341 over it, 1.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 功能/编码任务_v6.vb FFmpegFreeUI/功能/编码任务_v6.vb— FileTooLong — 799 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 299 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Updater/Program.vb Updater/Program.vb— FileTooLong — 728 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 228 over it, 1.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 集成工具/Form_v6_集成工具_混流.vb FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb— FileTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 223 over it, 1.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 功能/视频编码器数据库_v6.vb FFmpegFreeUI/功能/视频编码器数据库_v6.vb— FileTooLong — 697 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 197 over it, 1.39× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Agent 智能体/Agent页面控制器_呈现_v6.vb FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_呈现_v6.vb— FileTooLong — 683 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 183 over it, 1.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 功能/设置_v6.vb FFmpegFreeUI/功能/设置_v6.vb— FileTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 127 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Agent 智能体/Agent页面控制器_v6.vb FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_v6.vb— FileTooLong — 620 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 120 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 界面 v6 参数面板/Form_v6_参数面板_预设管理.vb FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_预设管理.vb— FileTooLong — 591 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 91 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 功能/Module1.vb FFmpegFreeUI/功能/Module1.vb— FileTooLong — 580 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 80 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Agent 智能体/Agent本地工具_进程_v6.vb FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb— FileTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 70 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 预设系统/预设面板总览_参数文本_v6.vb FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb— FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 53 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Agent 智能体/Agent本地工具_队列_v6.vb FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_队列_v6.vb— FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 40 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 预设系统/预设区段_画面帧_v6.vb FFmpegFreeUI/功能/预设系统/预设区段_画面帧_v6.vb— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Agent 智能体/Agent本地工具_参数_v6.vb FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_参数_v6.vb— FileTooLong — 529 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 29 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 集成工具/Form_v6_集成工具_比特率可视化.vb FFmpegFreeUI/集成工具/Form_v6_集成工具_比特率可视化.vb— FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 界面 v6 主页面/Form_v6_编码队列.vb FFmpegFreeUI/界面 v6 主页面/Form_v6_编码队列.vb— FileTooLong — 505 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 5 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
MethodTooLong: 预设管理_v6.显示参数总览 FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb:63— MethodTooLong — 显示参数总览 runs 278 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 178 over it, 2.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 视频编码器数据库_v6.初始化编码器 FFmpegFreeUI/功能/视频编码器数据库_v6.vb:115— MethodTooLong — 初始化编码器 runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 预设管理_v6.生成滤镜图 FFmpegFreeUI/功能/预设系统/预设命令行滤镜图_v6.vb:9— MethodTooLong — 生成滤镜图 runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AgentLocalTools.BuildToolDefinitions FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb:10— MethodTooLong — BuildToolDefinitions runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AgentLocalTools.ExecuteAsync FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb:233— MethodTooLong — ExecuteAsync runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 预设管理_v6.重置滤镜对应页面 FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb:462— MethodTooLong — 重置滤镜对应页面 runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 开发者内置预设_v6.获取全部 FFmpegFreeUI/功能/预设系统/开发者内置预设_v6.vb:14— MethodTooLong — 获取全部 runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 预设管理_v6.储存滤镜子窗口 FFmpegFreeUI/功能/预设系统/预设区段_画面帧_v6.vb:54— MethodTooLong — 储存滤镜子窗口 runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 预设管理_v6.重置滤镜对应预设字段 FFmpegFreeUI/功能/预设系统/预设滤镜排序_v6.vb:253— MethodTooLong — 重置滤镜对应预设字段 runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 音频编码器数据库_v6.初始化编码器 FFmpegFreeUI/功能/音频编码器数据库_v6.vb:98— MethodTooLong — 初始化编码器 runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Agent页面控制器_v6.RefreshModelsAsync FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_模型_v6.vb:108— MethodTooLong — RefreshModelsAsync runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 预设管理_v6.显示滤镜子窗口 FFmpegFreeUI/功能/预设系统/预设区段_画面帧_v6.vb:197— MethodTooLong — 显示滤镜子窗口 runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 设置_v6.启动时加载设置 FFmpegFreeUI/功能/设置_v6.vb:425— MethodTooLong — 启动时加载设置 runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Hotspot: FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb:233— FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 79 in AgentLocalTools.ExecuteAsync at line 233. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:08:39 +08:00' --until='2026-10-26 10:08:39 +08:00' --full-history --no-merges -- FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb:63— FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 121 in 预设管理_v6.显示参数总览 at line 63. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:08:39 +08:00' --until='2026-10-26 10:08:39 +08:00' --full-history --no-merges -- FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: FFmpegFreeUI/功能/界面主题_v6.vb FFmpegFreeUI/功能/界面主题_v6.vb:377— FFmpegFreeUI/功能/界面主题_v6.vb changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 68 in 界面主题_v6.转换为浅色 at line 377. 2 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:08:39 +08:00' --until='2026-10-26 10:08:39 +08:00' --full-history --no-merges -- FFmpegFreeUI/功能/界面主题_v6.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:925— FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in Form_v6_集成工具_质量评测.开始评测Async at line 925. 3 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:08:39 +08:00' --until='2026-10-26 10:08:39 +08:00' --full-history --no-merges -- FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: FFmpegFreeUI/功能/Agent 智能体/Agent技能资料库_v6.vb FFmpegFreeUI/功能/Agent 智能体/Agent技能资料库_v6.vb:24— FFmpegFreeUI/功能/Agent 智能体/Agent技能资料库_v6.vb changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in Agent技能资料库_v6.读取资料 at line 24. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:08:39 +08:00' --until='2026-10-26 10:08:39 +08:00' --full-history --no-merges -- FFmpegFreeUI/功能/Agent 智能体/Agent技能资料库_v6.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:137— FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in AgentEndpointClient.TryCreateChatCompletionStreamingAsync at line 137. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:08:39 +08:00' --until='2026-10-26 10:08:39 +08:00' --full-history --no-merges -- FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: FFmpegFreeUI/功能/编码队列_v6.vb FFmpegFreeUI/功能/编码队列_v6.vb:713— FFmpegFreeUI/功能/编码队列_v6.vb changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in 编码队列_v6.检查全部完成提示 at line 713. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:08:39 +08:00' --until='2026-10-26 10:08:39 +08:00' --full-history --no-merges -- FFmpegFreeUI/功能/编码队列_v6.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: FFmpegFreeUI/功能/设置_v6.vb FFmpegFreeUI/功能/设置_v6.vb:425— FFmpegFreeUI/功能/设置_v6.vb changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in 设置_v6.启动时加载设置 at line 425. 1 of those changes was a fix/bug commit, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:08:39 +08:00' --until='2026-10-26 10:08:39 +08:00' --full-history --no-merges -- FFmpegFreeUI/功能/设置_v6.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: FFmpegFreeUI/功能/预设系统/预设滤镜排序_v6.vb FFmpegFreeUI/功能/预设系统/预设滤镜排序_v6.vb:253— FFmpegFreeUI/功能/预设系统/预设滤镜排序_v6.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in 预设管理_v6.重置滤镜对应预设字段 at line 253. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:08:39 +08:00' --until='2026-10-26 10:08:39 +08:00' --full-history --no-merges -- FFmpegFreeUI/功能/预设系统/预设滤镜排序_v6.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb:103— FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Form_v6_媒体流选择器.开始读取 at line 103. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:08:39 +08:00' --until='2026-10-26 10:08:39 +08:00' --full-history --no-merges -- FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (8 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:700— FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:700-707 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:432-439 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) FFmpegFreeUI/功能/预设系统/预设区段_质量色彩音频_v6.vb:297— FFmpegFreeUI/功能/预设系统/预设区段_质量色彩音频_v6.vb:297-304 | FFmpegFreeUI/功能/预设系统/预设面板总览_兼容性_v6.vb:378-385 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) FFmpegFreeUI/界面 v6 主页面/Form_v6_编码队列_任务日志.vb:77— FFmpegFreeUI/界面 v6 主页面/Form_v6_编码队列_任务日志.vb:77-84 | FFmpegFreeUI/界面 v6 主页面/Form_v6_编码队列_查看参数.vb:39-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:809— FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:809-817 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:2309-2316 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:2309` 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) FFmpegFreeUI/功能/Module1.vb:287— FFmpegFreeUI/功能/Module1.vb:287-294 | FFmpegFreeUI/功能/编码任务_v6.vb:851-858 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:119— FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:119-123 | FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:247-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) FFmpegFreeUI/功能/Agent 智能体/Agent会话Json升级器_v6.vb:241— FFmpegFreeUI/功能/Agent 智能体/Agent会话Json升级器_v6.vb:241-245 | FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_v6.vb:572-576 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb:207— FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb:207-211 | FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:427-431 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) FFmpegFreeUI/功能/Agent 智能体/Agent上下文能力表_v6.vb:77— FFmpegFreeUI/功能/Agent 智能体/Agent上下文能力表_v6.vb:77-81 | FFmpegFreeUI/功能/Agent 智能体/Agent推理级别能力表_v6.vb:48-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) FFmpegFreeUI/功能/视频编码器数据库_v6.vb:460— FFmpegFreeUI/功能/视频编码器数据库_v6.vb:460-465 | FFmpegFreeUI/功能/视频编码器数据库_v6.vb:466-471 — 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 `FFmpegFreeUI/功能/视频编码器数据库_v6.vb:460` 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 (6 lines × 2) FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_烧录字幕.vb:94— FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_烧录字幕.vb:94-99 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_烧录字幕.vb:109-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) FFmpegFreeUI/功能/Agent 智能体/Agent能力缓存_v6.vb:220— FFmpegFreeUI/功能/Agent 智能体/Agent能力缓存_v6.vb:220-225 | FFmpegFreeUI/功能/Agent 智能体/Agent自定义模型配置_v6.vb:100-105 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:41— FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:41-46 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:79-84 — before extracting anything, compare `FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb` and `FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
ClassTooLong: 界面主题_v6 FFmpegFreeUI/功能/界面主题_v6.vb— ClassTooLong — 478 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 78 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: 预设数据_v6 FFmpegFreeUI/功能/预设系统/预设数据_v6.vb— ClassTooLong — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 40 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Form_v6_媒体流选择器 FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb— ClassTooLong — 416 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 16 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (13 lines × 2) FFmpegFreeUI/ApplicationEvents.vb:99— FFmpegFreeUI/ApplicationEvents.vb:99-111 | Updater/Program.vb:767-779 — before extracting anything, compare `FFmpegFreeUI/ApplicationEvents.vb` and `Updater/Program.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) FFmpegFreeUI/ApplicationEvents.vb:115— FFmpegFreeUI/ApplicationEvents.vb:115-127 | Updater/Program.vb:783-795 — before extracting anything, compare `FFmpegFreeUI/ApplicationEvents.vb` and `Updater/Program.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:264— FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:264-276 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:714-726 — before extracting anything, compare `FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb` and `FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) Updater/Program.vb:172— Updater/Program.vb:172-182 | Updater/Program.vb:537-547 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) FFmpegFreeUI/ApplicationEvents.vb:141— FFmpegFreeUI/ApplicationEvents.vb:141-151 | Updater/Program.vb:809-819 — before extracting anything, compare `FFmpegFreeUI/ApplicationEvents.vb` and `Updater/Program.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:298— FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:298-308 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:783-793 — before extracting anything, compare `FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb` and `FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) FFmpegFreeUI/ApplicationEvents.vb:62— FFmpegFreeUI/ApplicationEvents.vb:62-73 | Updater/Program.vb:730-741 — before extracting anything, compare `FFmpegFreeUI/ApplicationEvents.vb` and `Updater/Program.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) FFmpegFreeUI/功能/Module1.vb:617— FFmpegFreeUI/功能/Module1.vb:617-628 | FFmpegFreeUI/界面 v6 主页面/Form_v6_媒体信息.vb:57-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:100— FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:100-111 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:138-149 — before extracting anything, compare `FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb` and `FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) FFmpegFreeUI/功能/预设系统/预设区段_质量色彩音频_v6.vb:285— FFmpegFreeUI/功能/预设系统/预设区段_质量色彩音频_v6.vb:285-293 | FFmpegFreeUI/功能/预设系统/预设面板总览_兼容性_v6.vb:366-374 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `FFmpegFreeUI/功能/预设系统/预设区段_质量色彩音频_v6.vb:282` calls `IsNullOrWhiteSpace` and `FFmpegFreeUI/功能/预设系统/预设面板总览_兼容性_v6.vb:365` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) FFmpegFreeUI/界面 v6 主页面/Form_v6_支持者.vb:34— FFmpegFreeUI/界面 v6 主页面/Form_v6_支持者.vb:34-42 | FFmpegFreeUI/界面 v6 主页面/Form_v6_支持者.vb:47-55 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:54— FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:54-62 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:92-100 — before extracting anything, compare `FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb` and `FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Change coupling: Agent本地工具_v6.vb ↔ Form_v6_Agent.vb FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb:1— `FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb` and `FFmpegFreeUI/界面 v6 主页面/Form_v6_Agent.vb` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `becda5bb` 2026/10/26-1; `add8f0d0` 2026/9/30-1; `103979fa` 2026/9/21-1 — run `git show` on any of them.
Change coupling: Agent技能资料库_v6.vb ↔ Form_v6_Agent.vb FFmpegFreeUI/功能/Agent 智能体/Agent技能资料库_v6.vb:1— `FFmpegFreeUI/功能/Agent 智能体/Agent技能资料库_v6.vb` and `FFmpegFreeUI/界面 v6 主页面/Form_v6_Agent.vb` 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `becda5bb` 2026/10/26-1; `add8f0d0` 2026/9/30-1; `103979fa` 2026/9/21-1 — run `git show` on any of them.
Duplicated block (9 lines × 3) FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:700— FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:700-708 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:432-441 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1301-1310 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:700` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 3) FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb:60— FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb:60-68 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_胶片颗粒.vb:54-62 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_锐化.vb:46-54 — before extracting anything, compare `FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb` and `FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_胶片颗粒.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb:328— FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb:328-334 | FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb:341-347 — 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 `FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb:328` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) FFmpegFreeUI/ApplicationEvents.vb:131— FFmpegFreeUI/ApplicationEvents.vb:131-137 | Updater/Program.vb:799-805 — before extracting anything, compare `FFmpegFreeUI/ApplicationEvents.vb` and `Updater/Program.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Appears unstructured (no recognised architecture) — ~35k production LoC (292 types) across 2 project(s) / 6 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
预设管理_v6.显示参数总览 (cyclomatic 121) FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb:63— 预设管理_v6.显示参数总览 has cyclomatic complexity 121 (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.
预设管理_v6.生成滤镜图 (cyclomatic 114) FFmpegFreeUI/功能/预设系统/预设命令行滤镜图_v6.vb:9— 预设管理_v6.生成滤镜图 has cyclomatic complexity 114 (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.
AgentLocalTools.ExecuteAsync (cyclomatic 79) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb:233— AgentLocalTools.ExecuteAsync has cyclomatic complexity 79 (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.
界面主题_v6.转换为浅色 (cyclomatic 68) FFmpegFreeUI/功能/界面主题_v6.vb:377— 界面主题_v6.转换为浅色 has cyclomatic complexity 68 (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.
AgentLocalTools.FetchUrlAsync (cyclomatic 54) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_文件网络_v6.vb:87— AgentLocalTools.FetchUrlAsync has cyclomatic complexity 54 (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.
Form_v6_集成工具_质量评测.获取视频流信息Async (cyclomatic 42) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1255— Form_v6_集成工具_质量评测.获取视频流信息Async has cyclomatic complexity 42 (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.
界面主题_v6.应用对象颜色 (cyclomatic 33) FFmpegFreeUI/功能/界面主题_v6.vb:290— 界面主题_v6.应用对象颜色 has cyclomatic complexity 33 (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.
编码任务_v6.开始Async (cyclomatic 32) FFmpegFreeUI/功能/编码任务_v6.vb:370— 编码任务_v6.开始Async has cyclomatic complexity 32 (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.
AgentConversationJsonUpgrader.UpgradeTurns (cyclomatic 31) FFmpegFreeUI/功能/Agent 智能体/Agent会话Json升级器_v6.vb:89— AgentConversationJsonUpgrader.UpgradeTurns has cyclomatic complexity 31 (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.
AgentLocalTools.ResolveQueueTarget (cyclomatic 31) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_队列_v6.vb:143— AgentLocalTools.ResolveQueueTarget has cyclomatic complexity 31 (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.
AgentEndpointClient.TryCreateChatCompletionStreamingAsync (cyclomatic 30) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:137— AgentEndpointClient.TryCreateChatCompletionStreamingAsync has cyclomatic complexity 30 (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. This is NOT this file's highest cyclomatic complexity: AgentEndpointClient.IsReasoningEffortToken (cyclomatic 36) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
预设管理_v6.获取预设启用的内置滤镜标识符 (cyclomatic 30) FFmpegFreeUI/功能/预设系统/预设滤镜排序_v6.vb:220— 预设管理_v6.获取预设启用的内置滤镜标识符 has cyclomatic complexity 30 (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.
Agent页面控制器_v6.GetToolExecutionStatus (cyclomatic 28) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_呈现_v6.vb:153— Agent页面控制器_v6.GetToolExecutionStatus has cyclomatic complexity 28 (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. This is NOT this file's highest cyclomatic complexity: Agent页面控制器_v6.GetToolDisplayName (cyclomatic 38) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
预设管理_v6.构造烧字幕滤镜 (cyclomatic 28) FFmpegFreeUI/功能/预设系统/预设区段_画面效果字幕_v6.vb:84— 预设管理_v6.构造烧字幕滤镜 has cyclomatic complexity 28 (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.
预设管理_v6.生成元数据章节附件片段 (cyclomatic 28) FFmpegFreeUI/功能/预设系统/预设区段_高级流控制_v6.vb:210— 预设管理_v6.生成元数据章节附件片段 has cyclomatic complexity 28 (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. This is NOT this file's highest cyclomatic complexity: 预设管理_v6.附加片段默认映射主视频 (cyclomatic 29) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
预设管理_v6.生成命令行 (cyclomatic 28) FFmpegFreeUI/功能/预设系统/预设命令行核心_v6.vb:116— 预设管理_v6.生成命令行 has cyclomatic complexity 28 (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.
比特率可视化数据核心.构造序列 (cyclomatic 27) FFmpegFreeUI/集成工具/比特率可视化数据核心.vb:163— 比特率可视化数据核心.构造序列 has cyclomatic complexity 27 (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.
AgentLocalTools.DeserializeJsonElement (cyclomatic 26) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_参数_v6.vb:449— AgentLocalTools.DeserializeJsonElement has cyclomatic complexity 26 (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.
ConsoleRunSession.ExecuteAsync (cyclomatic 26) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:50— ConsoleRunSession.ExecuteAsync has cyclomatic complexity 26 (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.
AgentEndpointClient.ParseChatResult (cyclomatic 26) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:813— AgentEndpointClient.ParseChatResult has cyclomatic complexity 26 (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. This is NOT this file's highest cyclomatic complexity: AgentEndpointClient.IsReasoningEffortToken (cyclomatic 36) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
Agent页面控制器_v6.RefreshModelsAsync (cyclomatic 26) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_模型_v6.vb:108— Agent页面控制器_v6.RefreshModelsAsync has cyclomatic complexity 26 (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.
预设管理_v6.构造色彩转换滤镜 (cyclomatic 24) FFmpegFreeUI/功能/预设系统/预设区段_质量色彩音频_v6.vb:307— 预设管理_v6.构造色彩转换滤镜 has cyclomatic complexity 24 (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.
编码进度_v6.解析Progress键值 (cyclomatic 23) FFmpegFreeUI/功能/编码进度_v6.vb:90— 编码进度_v6.解析Progress键值 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.
Form_v6_集成工具_质量评测.解析AutoVmaf模型 (cyclomatic 23) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:370— Form_v6_集成工具_质量评测.解析AutoVmaf模型 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.
编码进度_v6.解析FFmpeg输出 (cyclomatic 22) FFmpegFreeUI/功能/编码进度_v6.vb:26— 编码进度_v6.解析FFmpeg输出 has cyclomatic complexity 22 (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.
Form_v6_集成工具_质量评测.开始评测Async (cyclomatic 22) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:925— Form_v6_集成工具_质量评测.开始评测Async has cyclomatic complexity 22 (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.
Form_v6_集成工具_质量评测.运行单项指标Async (cyclomatic 22) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1011— Form_v6_集成工具_质量评测.运行单项指标Async has cyclomatic complexity 22 (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.
AgentLocalTools.MoveLocalPath (cyclomatic 21) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_文件网络_v6.vb:289— AgentLocalTools.MoveLocalPath has cyclomatic complexity 21 (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.
AgentLocalTools.RunWindowsExecutableAsync (cyclomatic 21) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:543— AgentLocalTools.RunWindowsExecutableAsync has cyclomatic complexity 21 (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.
编码队列_v6.生成自动命名后缀 (cyclomatic 21) FFmpegFreeUI/功能/编码队列_v6.vb:958— 编码队列_v6.生成自动命名后缀 has cyclomatic complexity 21 (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.
Form_v6_性能监控_LHM.ReadGpuSensors (cyclomatic 20) FFmpegFreeUI/界面 v6 主页面/Form_v6_性能监控_LHM.vb:122— Form_v6_性能监控_LHM.ReadGpuSensors has cyclomatic complexity 20 (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.
媒体信息解析器.解析 (cyclomatic 20) FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb:323— 媒体信息解析器.解析 has cyclomatic complexity 20 (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.
Form_v6_集成工具_比特率可视化.分析点击 (cyclomatic 20) FFmpegFreeUI/集成工具/Form_v6_集成工具_比特率可视化.vb:181— Form_v6_集成工具_比特率可视化.分析点击 has cyclomatic complexity 20 (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.
启动参数响应_v6.处理接收的参数 (cyclomatic 19) FFmpegFreeUI/功能/启动参数响应_v6.vb:31— 启动参数响应_v6.处理接收的参数 has cyclomatic complexity 19 (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.
编码任务_v6.计算当前总时长 (cyclomatic 19) FFmpegFreeUI/功能/编码任务_v6.vb:593— 编码任务_v6.计算当前总时长 has cyclomatic complexity 19 (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.
设置_v6.迁移旧设置字段 (cyclomatic 19) FFmpegFreeUI/功能/设置_v6.vb:571— 设置_v6.迁移旧设置字段 has cyclomatic complexity 19 (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.
Form_v6_集成工具_Whisper生成字幕.验证任务参数 (cyclomatic 19) FFmpegFreeUI/集成工具/Form_v6_集成工具_Whisper生成字幕.vb:302— Form_v6_集成工具_Whisper生成字幕.验证任务参数 has cyclomatic complexity 19 (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.
Form_v6_集成工具_质量评测.解析VMAFJson (cyclomatic 19) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1701— Form_v6_集成工具_质量评测.解析VMAFJson has cyclomatic complexity 19 (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.
AgentEndpointClient.ParseResponsesResult (cyclomatic 18) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:844— AgentEndpointClient.ParseResponsesResult has cyclomatic complexity 18 (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. This is NOT this file's highest cyclomatic complexity: AgentEndpointClient.IsReasoningEffortToken (cyclomatic 36) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
编码队列_v6.移动任务 (cyclomatic 18) FFmpegFreeUI/功能/编码队列_v6.vb:555— 编码队列_v6.移动任务 has cyclomatic complexity 18 (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.
预设管理_v6.储存滤镜子窗口 (cyclomatic 18) FFmpegFreeUI/功能/预设系统/预设区段_画面帧_v6.vb:54— 预设管理_v6.储存滤镜子窗口 has cyclomatic complexity 18 (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.
Agent工具封装_v6.扫描控件递归 (cyclomatic 17) FFmpegFreeUI/功能/Agent 智能体/Agent工具封装_v6.vb:324— Agent工具封装_v6.扫描控件递归 has cyclomatic complexity 17 (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. This is NOT this file's highest cyclomatic complexity: Agent工具封装_v6.是参数面板可读控件 (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
AgentEndpointClient.AccumulateChatMessageDelta (cyclomatic 17) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:771— AgentEndpointClient.AccumulateChatMessageDelta has cyclomatic complexity 17 (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. This is NOT this file's highest cyclomatic complexity: AgentEndpointClient.IsReasoningEffortToken (cyclomatic 36) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
编码队列_v6.调度待启动任务 (cyclomatic 17) FFmpegFreeUI/功能/编码队列_v6.vb:618— 编码队列_v6.调度待启动任务 has cyclomatic complexity 17 (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.
Form_v6_媒体流选择器.开始读取 (cyclomatic 17) FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb:103— Form_v6_媒体流选择器.开始读取 has cyclomatic complexity 17 (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.
Form_v6_集成工具_混流.Agent配置 (cyclomatic 17) FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:181— Form_v6_集成工具_混流.Agent配置 has cyclomatic complexity 17 (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.
AgentEndpointClient.ExtractErrorMessage (cyclomatic 16) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:916— AgentEndpointClient.ExtractErrorMessage 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. This is NOT this file's highest cyclomatic complexity: AgentEndpointClient.IsReasoningEffortToken (cyclomatic 36) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
Agent页面控制器_v6.EnsureContextSummaryAsync (cyclomatic 16) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_上下文_v6.vb:130— Agent页面控制器_v6.EnsureContextSummaryAsync 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.
Agent页面控制器_v6.CompleteInterruptedToolBatch (cyclomatic 16) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_运行_v6.vb:403— Agent页面控制器_v6.CompleteInterruptedToolBatch 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.
启动参数响应_v6.拆分命令行 (cyclomatic 16) FFmpegFreeUI/功能/启动参数响应_v6.vb:204— 启动参数响应_v6.拆分命令行 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.
编码任务_v6.追加日志 (cyclomatic 16) FFmpegFreeUI/功能/编码任务_v6.vb:271— 编码任务_v6.追加日志 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.
编码队列_v6.检查全部完成提示 (cyclomatic 16) FFmpegFreeUI/功能/编码队列_v6.vb:713— 编码队列_v6.检查全部完成提示 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.
预设管理_v6.添加字幕容器兼容性总览 (cyclomatic 16) FFmpegFreeUI/功能/预设系统/预设面板总览_兼容性_v6.vb:256— 预设管理_v6.添加字幕容器兼容性总览 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. This is NOT this file's highest cyclomatic complexity: 预设管理_v6.视频滤镜参数已设置 (cyclomatic 28) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
比特率可视化数据核心.解析包 (cyclomatic 16) FFmpegFreeUI/集成工具/比特率可视化数据核心.vb:128— 比特率可视化数据核心.解析包 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.
Build failed — The target solution did not build cleanly (errors: 2018), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: BC30002: Type 'ModernComboBox' is not defined.; BC30002: Type 'ModernListBox.ItemForeColorEventArgs' is not defined.; BC30002: Type 'LakeUI.ModernPanel' is not defined.; BC30002: Type 'AgentRoom.LinkClickedEventArgs' is not defined.; BC30002: Type 'LakeUI.AgentRoom.ChatItem' is not defined..
预设管理_v6.显示参数总览 (cognitive 178) FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb:63— 预设管理_v6.显示参数总览 has cognitive complexity 178 (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.
预设管理_v6.生成滤镜图 (cognitive 150) FFmpegFreeUI/功能/预设系统/预设命令行滤镜图_v6.vb:9— 预设管理_v6.生成滤镜图 has cognitive complexity 150 (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.
AgentLocalTools.ExecuteAsync (cognitive 77) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb:233— AgentLocalTools.ExecuteAsync has cognitive complexity 77 (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.
界面主题_v6.转换为浅色 (cognitive 76) FFmpegFreeUI/功能/界面主题_v6.vb:377— 界面主题_v6.转换为浅色 has cognitive complexity 76 (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.
AgentConversationJsonUpgrader.UpgradeTurns (cognitive 61) FFmpegFreeUI/功能/Agent 智能体/Agent会话Json升级器_v6.vb:89— AgentConversationJsonUpgrader.UpgradeTurns 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.
AgentLocalTools.FetchUrlAsync (cognitive 51) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_文件网络_v6.vb:87— AgentLocalTools.FetchUrlAsync has cognitive complexity 51 (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.
AgentLocalTools.DeserializeJsonElement (cognitive 44) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_参数_v6.vb:449— AgentLocalTools.DeserializeJsonElement has cognitive complexity 44 (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.
Form_v6_集成工具_质量评测.开始评测Async (cognitive 44) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:925— Form_v6_集成工具_质量评测.开始评测Async has cognitive complexity 44 (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.
AgentEndpointClient.TryCreateChatCompletionStreamingAsync (cognitive 43) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:137— AgentEndpointClient.TryCreateChatCompletionStreamingAsync 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.
比特率可视化数据核心.构造序列 (cognitive 43) FFmpegFreeUI/集成工具/比特率可视化数据核心.vb:163— 比特率可视化数据核心.构造序列 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.
预设管理_v6.生成命令行 (cognitive 41) FFmpegFreeUI/功能/预设系统/预设命令行核心_v6.vb:116— 预设管理_v6.生成命令行 has cognitive complexity 41 (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.
编码任务_v6.开始Async (cognitive 40) FFmpegFreeUI/功能/编码任务_v6.vb:370— 编码任务_v6.开始Async has cognitive complexity 40 (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.
媒体信息解析器.解析 (cognitive 40) FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb:323— 媒体信息解析器.解析 has cognitive complexity 40 (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.
Form_v6_集成工具_质量评测.获取视频流信息Async (cognitive 40) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1255— Form_v6_集成工具_质量评测.获取视频流信息Async has cognitive complexity 40 (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.
AgentLocalTools.ResolveQueueTarget (cognitive 39) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_队列_v6.vb:143— AgentLocalTools.ResolveQueueTarget 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.
AgentEndpointClient.ParseChatResult (cognitive 38) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:813— AgentEndpointClient.ParseChatResult has cognitive complexity 38 (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.
预设管理_v6.构造色彩转换滤镜 (cognitive 38) FFmpegFreeUI/功能/预设系统/预设区段_质量色彩音频_v6.vb:307— 预设管理_v6.构造色彩转换滤镜 has cognitive complexity 38 (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.
界面主题_v6.应用对象颜色 (cognitive 36) FFmpegFreeUI/功能/界面主题_v6.vb:290— 界面主题_v6.应用对象颜色 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.
Agent页面控制器_v6.RefreshModelsAsync (cognitive 35) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_模型_v6.vb:108— Agent页面控制器_v6.RefreshModelsAsync has cognitive complexity 35 (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.
启动参数响应_v6.拆分命令行 (cognitive 35) FFmpegFreeUI/功能/启动参数响应_v6.vb:204— 启动参数响应_v6.拆分命令行 has cognitive complexity 35 (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.
预设管理_v6.生成元数据章节附件片段 (cognitive 33) FFmpegFreeUI/功能/预设系统/预设区段_高级流控制_v6.vb:210— 预设管理_v6.生成元数据章节附件片段 has cognitive complexity 33 (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.
Form_v6_集成工具_质量评测.解析VMAFJson (cognitive 32) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1701— Form_v6_集成工具_质量评测.解析VMAFJson has cognitive complexity 32 (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.
AgentLocalTools.MoveLocalPath (cognitive 30) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_文件网络_v6.vb:289— AgentLocalTools.MoveLocalPath 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.
ConsoleRunSession.ExecuteAsync (cognitive 30) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:50— ConsoleRunSession.ExecuteAsync 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.
Agent页面控制器_v6.ReplaceLatestUserTurnAsync (cognitive 30) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_v6.vb:323— Agent页面控制器_v6.ReplaceLatestUserTurnAsync 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.
AgentEndpointClient.AccumulateChatMessageDelta (cognitive 29) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:771— AgentEndpointClient.AccumulateChatMessageDelta has cognitive complexity 29 (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.
AgentConversationStore.RecoverInterruptedRuns (cognitive 28) FFmpegFreeUI/功能/Agent 智能体/Agent会话存储_v6.vb:251— AgentConversationStore.RecoverInterruptedRuns 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.
编码进度_v6.解析FFmpeg输出 (cognitive 28) FFmpegFreeUI/功能/编码进度_v6.vb:26— 编码进度_v6.解析FFmpeg输出 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.
AgentEndpointClient.ParseResponsesResult (cognitive 27) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:844— AgentEndpointClient.ParseResponsesResult has cognitive complexity 27 (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.
Agent页面控制器_v6.GetToolExecutionStatus (cognitive 27) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_呈现_v6.vb:153— Agent页面控制器_v6.GetToolExecutionStatus has cognitive complexity 27 (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.
预设管理_v6.构造烧字幕滤镜 (cognitive 27) FFmpegFreeUI/功能/预设系统/预设区段_画面效果字幕_v6.vb:84— 预设管理_v6.构造烧字幕滤镜 has cognitive complexity 27 (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.
Form_v6_集成工具_质量评测.恢复页面状态 (cognitive 26) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:892— Form_v6_集成工具_质量评测.恢复页面状态 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.
Form_v6_集成工具_质量评测.运行单项指标Async (cognitive 26) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1011— Form_v6_集成工具_质量评测.运行单项指标Async 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.
Agent页面控制器_v6.RunAgentLoopAsync (cognitive 25) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_运行_v6.vb:202— Agent页面控制器_v6.RunAgentLoopAsync 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.
预设管理_v6.获取预设启用的内置滤镜标识符 (cognitive 25) FFmpegFreeUI/功能/预设系统/预设滤镜排序_v6.vb:220— 预设管理_v6.获取预设启用的内置滤镜标识符 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.
Form_v6_媒体流选择器.开始读取 (cognitive 25) FFmpegFreeUI/界面 v6 参数面板/Form_v6_媒体流选择器.vb:103— Form_v6_媒体流选择器.开始读取 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.
Agent工具封装_v6.扫描控件递归 (cognitive 24) FFmpegFreeUI/功能/Agent 智能体/Agent工具封装_v6.vb:324— Agent工具封装_v6.扫描控件递归 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.
AgentEndpointClient.AddReasoningEffortsFromParameterDefinitions (cognitive 24) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:531— AgentEndpointClient.AddReasoningEffortsFromParameterDefinitions 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.
Form_v6_集成工具_比特率可视化.分析点击 (cognitive 24) FFmpegFreeUI/集成工具/Form_v6_集成工具_比特率可视化.vb:181— Form_v6_集成工具_比特率可视化.分析点击 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.
Form_v6_集成工具_质量评测.生成当前列表导出记录 (cognitive 24) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:2094— Form_v6_集成工具_质量评测.生成当前列表导出记录 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.
AgentLocalTools.RunWindowsExecutableAsync (cognitive 23) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:543— AgentLocalTools.RunWindowsExecutableAsync 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.
Agent页面控制器_v6.RemoveConversationMessagesFrom (cognitive 23) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_v6.vb:420— Agent页面控制器_v6.RemoveConversationMessagesFrom 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.
启动参数响应_v6.处理接收的参数 (cognitive 23) FFmpegFreeUI/功能/启动参数响应_v6.vb:31— 启动参数响应_v6.处理接收的参数 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.
编码进度_v6.解析Progress键值 (cognitive 23) FFmpegFreeUI/功能/编码进度_v6.vb:90— 编码进度_v6.解析Progress键值 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.
Form_v6_集成工具_比特率可视化.刷新呈现 (cognitive 23) FFmpegFreeUI/集成工具/Form_v6_集成工具_比特率可视化.vb:324— Form_v6_集成工具_比特率可视化.刷新呈现 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.
Program.等待主程序退出 (cognitive 23) Updater/Program.vb:206— Program.等待主程序退出 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.
编码任务_v6.计算当前总时长 (cognitive 22) FFmpegFreeUI/功能/编码任务_v6.vb:593— 编码任务_v6.计算当前总时长 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.
Form_v6_参数面板_预设管理.刷新预设列表 (cognitive 22) FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_预设管理.vb:40— Form_v6_参数面板_预设管理.刷新预设列表 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.
Form_v6_集成工具_混流.Agent配置 (cognitive 22) FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:181— Form_v6_集成工具_混流.Agent配置 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.
比特率可视化数据核心.读取文件信息Async (cognitive 22) FFmpegFreeUI/集成工具/比特率可视化数据核心.vb:60— 比特率可视化数据核心.读取文件信息Async 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.
ConsoleRunSession.EnsureProcessStarted (cognitive 21) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_进程_v6.vb:200— ConsoleRunSession.EnsureProcessStarted 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.
Agent页面控制器_v6.RenderCurrentConversation (cognitive 21) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_呈现_v6.vb:31— Agent页面控制器_v6.RenderCurrentConversation 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.
预设管理_v6.获取未引用滤镜标签 (cognitive 21) FFmpegFreeUI/功能/预设系统/预设命令行滤镜图_v6.vb:330— 预设管理_v6.获取未引用滤镜标签 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.
Form_v6_集成工具_抽流.构建主文本 (cognitive 21) FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:324— Form_v6_集成工具_抽流.构建主文本 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.
Form_v6_集成工具_质量评测.解析AutoVmaf模型 (cognitive 21) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:370— Form_v6_集成工具_质量评测.解析AutoVmaf模型 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.
AgentEndpointClient.AddReasoningEffortsFromContainer (cognitive 20) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:503— AgentEndpointClient.AddReasoningEffortsFromContainer 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.
编码队列_v6.添加来自参数面板的文件 (cognitive 20) FFmpegFreeUI/功能/编码队列_v6.vb:318— 编码队列_v6.添加来自参数面板的文件 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.
编码队列_v6.移动任务 (cognitive 20) FFmpegFreeUI/功能/编码队列_v6.vb:555— 编码队列_v6.移动任务 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.
设置_v6.迁移旧设置字段 (cognitive 20) FFmpegFreeUI/功能/设置_v6.vb:571— 设置_v6.迁移旧设置字段 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.
预设管理_v6.储存滤镜子窗口 (cognitive 20) FFmpegFreeUI/功能/预设系统/预设区段_画面帧_v6.vb:54— 预设管理_v6.储存滤镜子窗口 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.
预设管理_v6.构造超分滤镜 (cognitive 20) FFmpegFreeUI/功能/预设系统/预设区段_画面帧_v6.vb:393— 预设管理_v6.构造超分滤镜 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.
AgentConversationStore.NormalizeConversations (cognitive 19) FFmpegFreeUI/功能/Agent 智能体/Agent会话存储_v6.vb:212— AgentConversationStore.NormalizeConversations 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.
AgentEndpointClient.BuildChatMessages (cognitive 19) FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb:391— AgentEndpointClient.BuildChatMessages 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.
设置_v6.启动时加载设置 (cognitive 19) FFmpegFreeUI/功能/设置_v6.vb:425— 设置_v6.启动时加载设置 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.
预设管理_v6.规范化Agent排序项 (cognitive 19) FFmpegFreeUI/功能/预设系统/预设滤镜排序_v6.vb:186— 预设管理_v6.规范化Agent排序项 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.
Form_v6_性能监控_LHM.ReadGpuSensors (cognitive 19) FFmpegFreeUI/界面 v6 主页面/Form_v6_性能监控_LHM.vb:122— Form_v6_性能监控_LHM.ReadGpuSensors 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.
Form_v6_集成工具_质量评测.标记未完成项为已取消 (cognitive 19) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1920— Form_v6_集成工具_质量评测.标记未完成项为已取消 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.
Program.主流程 (cognitive 19) Updater/Program.vb:46— Program.主流程 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.
Agent页面控制器_v6.RenderTurnRecord (cognitive 18) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_呈现_v6.vb:70— Agent页面控制器_v6.RenderTurnRecord 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.
编码队列_v6.生成自动命名后缀 (cognitive 18) FFmpegFreeUI/功能/编码队列_v6.vb:958— 编码队列_v6.生成自动命名后缀 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.
Form_v6_准备文件.获取文件夹中的所有文件 (cognitive 18) FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb:94— Form_v6_准备文件.获取文件夹中的所有文件 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.
Form_v6_集成工具_质量评测.从FFmpeg运行库提取Vmaf模型列表 (cognitive 18) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:393— Form_v6_集成工具_质量评测.从FFmpeg运行库提取Vmaf模型列表 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.
Form_v6_集成工具_质量评测.刷新评分颜色 (cognitive 18) FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1968— Form_v6_集成工具_质量评测.刷新评分颜色 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.
Agent页面控制器_v6.StartAgentRunAsync (cognitive 17) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_运行_v6.vb:93— Agent页面控制器_v6.StartAgentRunAsync 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.
Agent页面控制器_v6.CompleteInterruptedToolBatch (cognitive 17) FFmpegFreeUI/功能/Agent 智能体/Agent页面控制器_运行_v6.vb:403— Agent页面控制器_v6.CompleteInterruptedToolBatch 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.
Module1.LoadImageFromFile (cognitive 17) FFmpegFreeUI/功能/Module1.vb:317— Module1.LoadImageFromFile 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.
编码任务_v6.追加日志 (cognitive 17) FFmpegFreeUI/功能/编码任务_v6.vb:271— 编码任务_v6.追加日志 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.
编码队列_v6.修改预设任务核心 (cognitive 17) FFmpegFreeUI/功能/编码队列_v6.vb:355— 编码队列_v6.修改预设任务核心 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.
Form_v6_性能监控.Timer1_Tick (cognitive 17) FFmpegFreeUI/界面 v6 主页面/Form_v6_性能监控.vb:86— Form_v6_性能监控.Timer1_Tick 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.
Form_v6_参数面板_滤镜排序.移动选中项 (cognitive 17) FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_滤镜排序.vb:205— Form_v6_参数面板_滤镜排序.移动选中项 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.
Form_v6_集成工具_Whisper生成字幕.验证任务参数 (cognitive 17) FFmpegFreeUI/集成工具/Form_v6_集成工具_Whisper生成字幕.vb:302— Form_v6_集成工具_Whisper生成字幕.验证任务参数 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.
编码队列_v6.调度待启动任务 (cognitive 16) FFmpegFreeUI/功能/编码队列_v6.vb:618— 编码队列_v6.调度待启动任务 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.
预设管理_v6.构造缩放滤镜 (cognitive 16) FFmpegFreeUI/功能/预设系统/预设区段_画面帧_v6.vb:317— 预设管理_v6.构造缩放滤镜 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.
预设管理_v6.添加字幕容器兼容性总览 (cognitive 16) FFmpegFreeUI/功能/预设系统/预设面板总览_兼容性_v6.vb:256— 预设管理_v6.添加字幕容器兼容性总览 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.
Form_v6_调试播放器.播放 (cognitive 16) FFmpegFreeUI/界面 v6 主页面/Form_v6_调试播放器.vb:97— Form_v6_调试播放器.播放 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.
Form_v6_集成工具_合并.移动选中项 (cognitive 16) FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:173— Form_v6_集成工具_合并.移动选中项 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.
Form_v6_集成工具_混流.移动选中项 (cognitive 16) FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:465— Form_v6_集成工具_混流.移动选中项 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.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb:68— FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb:68-71 | FFmpegFreeUI/集成工具/Form_v6_集成工具_Whisper生成字幕.vb:134-150 | FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:66-69 | FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:73-76 | FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:107-123 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:104-107 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:111-114 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:564-567 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:698— FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:698-722 | FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:726-799 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:430-455 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1299-1324 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1573-1644 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb:3— FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb:3-10 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_胶片颗粒.vb:3-10 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_锐化.vb:3-10 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_降噪.vb:3-10 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (45 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:755— FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:755-799 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1600-1644 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (26–28 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:726— FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:726-753 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1573-1598 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (26 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:174— FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:174-199 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:466-491 — before extracting anything, compare `FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb` and `FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (23–24 lines × 2) FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:700— FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:700-722 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1301-1324 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19 lines × 2) FFmpegFreeUI/ApplicationEvents.vb:77— FFmpegFreeUI/ApplicationEvents.vb:77-95 | Updater/Program.vb:745-763 — before extracting anything, compare `FFmpegFreeUI/ApplicationEvents.vb` and `Updater/Program.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) FFmpegFreeUI/界面 v6 主页面/Form_v6_编码队列_任务日志.vb:491— FFmpegFreeUI/界面 v6 主页面/Form_v6_编码队列_任务日志.vb:491-508 | FFmpegFreeUI/界面 v6 主页面/Form_v6_编码队列_查看参数.vb:64-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (3–17 lines × 8) FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb:68— FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb:68-70 | FFmpegFreeUI/集成工具/Form_v6_集成工具_Whisper生成字幕.vb:134-150 | FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:66-68 | FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:73-75 | FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:107-123 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:104-106 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:111-113 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:564-566 — there are 8 copies across 6 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 8 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–14 lines × 2) FFmpegFreeUI/功能/预设系统/预设区段_输出解码编码_v6.vb:13— FFmpegFreeUI/功能/预设系统/预设区段_输出解码编码_v6.vb:13-24 | FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb:389-402 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 3) FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb:92— FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb:92-104 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_胶片颗粒.vb:86-98 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_锐化.vb:74-86 — before extracting anything, compare `FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb` and `FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_胶片颗粒.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) FFmpegFreeUI/ApplicationEvents.vb:155— FFmpegFreeUI/ApplicationEvents.vb:155-164 | Updater/Program.vb:823-832 — before extracting anything, compare `FFmpegFreeUI/ApplicationEvents.vb` and `Updater/Program.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:733— FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:733-740 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1301-1308 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1579-1586 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (8 lines × 5) FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:700— FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:700-707 | FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:733-740 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:432-439 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1301-1308 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:1579-1586 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (8 lines × 4) FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb:3— FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb:3-10 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_胶片颗粒.vb:3-10 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_锐化.vb:3-10 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_降噪.vb:3-10 — before extracting anything, compare `FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_平滑断层.vb` and `FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_胶片颗粒.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:341— FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:341-345 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:834-838 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:2329-2333 — before extracting anything, compare `FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb` and `FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb:389— FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb:389-395 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:809-815 | FFmpegFreeUI/集成工具/Form_v6_集成工具_质量评测.vb:2309-2314 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (4–6 lines × 3) FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_队列_v6.vb:412— FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_队列_v6.vb:412-417 | FFmpegFreeUI/功能/编码队列_v6.vb:808-813 | FFmpegFreeUI/功能/预设系统/预设命令行核心_v6.vb:81-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `FFmpegFreeUI/功能/预设系统/预设命令行核心_v6.vb:84` calls `Q` and `FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_队列_v6.vb:417` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_元数据.vb:143— FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_元数据.vb:143-156 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_附件.vb:176-189 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 5) FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_动态模糊.vb:4— FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_动态模糊.vb:4-15 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_扫描方式.vb:4-21 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_插帧_NV_FRUC.vb:5-26 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_插帧_简易.vb:3-14 | FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_画面翻转.vb:4-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_动态模糊.vb:15` calls `Hide` and `FFmpegFreeUI/界面 v6 参数面板/Form_v6_参数面板_扫描方式.vb:21` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 5) FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb:51— FFmpegFreeUI/界面 v6 主页面/Form_v6_准备文件.vb:51-56 | FFmpegFreeUI/集成工具/Form_v6_集成工具_Whisper生成字幕.vb:114-119 | FFmpegFreeUI/集成工具/Form_v6_集成工具_合并.vb:24-29 | FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb:88-93 | FFmpegFreeUI/集成工具/Form_v6_集成工具_混流.vb:62-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 77 significant file(s) lose their only recent owner: FFmpegFreeUI/功能/视频编码器数据库_v6.vb, FFmpegFreeUI/功能/Agent 智能体/Agent端点客户端_v6.vb, FFmpegFreeUI/功能/Agent 智能体/Agent技能资料库_v6.vb, FFmpegFreeUI/功能/编码队列_v6.vb, FFmpegFreeUI/功能/Agent 智能体/Agent本地工具_v6.vb, FFmpegFreeUI/功能/预设系统/预设面板总览_参数文本_v6.vb, FFmpegFreeUI/集成工具/Form_v6_集成工具_抽流.vb, FFmpegFreeUI/功能/编码任务_v6.vb (+69 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (78 single-owned of 115 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 115 of the 146 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: FFmpegFreeUI/集成工具/VmafModelComboBox.vb.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `FFmpegFreeUI` (34209 LoC, 140 public types across 1 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P1 · CI/CD gates· CI build step not evidenced · ×1
CI build step not evidenced — A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
No SAST — No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean as a CI step. What was searched, so you can tell an absence from a miss: the 6250 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Outdated: Microsoft.Agents.AI.OpenAI — Microsoft.Agents.AI.OpenAI 1.24.0 → 1.26.0 available (referenced by FFmpegFreeUI).
Outdated: System.Management — System.Management 10.0.12 → 10.0.14 available (referenced by FFmpegFreeUI).
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.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a1791d-b37d-7aec-b557-26e9b4d98318 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 131 · Warnings: 271 · Recommendations: 14 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 16:49 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.