Public report — npoi, published 5 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
2386findings with an exact file:lineof 2408 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
50/98dimensions across the health lenses485061 LoC · 33 projects — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
nissl-lab/npoi is sound in substance but carries real gaps (51%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Architecture (94%) — the structure is clean and changes stay contained. Performance (81%) is solid too.
The area that most needs attention is Security (41%) — exposure to security and compliance incidents is elevated. Code Health (54%) is the next concern — changes there are slower and more error-prone.
Leadership focus, highest impact first: Strengthen data-at-rest protection (Data Protection); Store passwords with a salted KDF (Cryptographic Hygiene); 18 High finding(s) (Static Analysis (SAST)).
For scale: Large (~485,061 production lines); rebuilding it from scratch would take roughly ~7.0 person-years (~4–14 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (94%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
This codebase represents roughly ~7.0 person-years of build effort (about ~€1,000,000 to rebuild). Its weakest lens is Security at 41% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Low (×0.9) — library/CLI × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `main/HSSF/Record/Aggregates/WorksheetProtectionBlock.cs:278`.
Value concentrated against a weak lens · High · Value at risk
This is a Large asset (~7.0 person-years to rebuild), and its weakest lens is Security at 41%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Security first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
Architecture — module dependency matrix
119 modules, 445 dependencies — 7 dependency cycles, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
At a glance — Code Health · 54% · Adequate · gated by X5, IC1
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
19
High / Critical
A02:2021 — Cryptographic Failures
1
High / Critical
Roadmap
First, strengthen data protection by vaulting keys and encrypting sensitive columns to close current coverage gaps. Next, implement proper password storage using a salted KDF and constant-time comparison to ensure cryptographic hygiene. Then, resolve the 18 high-priority static analysis findings, particularly in the CI and PR pipelines. After that, finish or remove all unfinished code stubs to eliminate dead surfaces. Finally, enable nullable reference types across all projects and resolve warnings instead of suppressing them.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `main/HSSF/Record/Aggregates/WorksheetProtectionBlock.cs:278`.
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. 47 of 50 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — 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 — 50 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, 2386 of 2408 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.
D24 Comment Value — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D20, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
235 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CT_Settings.Write at 102. A further 23 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 LocaleUtil.GetLocaleFromLCID at 457 — they are counted neither in the figure above nor in this dimension's score.
+ 228 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 CT_ShapeProperties.Parse (cyclomatic 19) finding(s) in Cyclomatic Complexity — start with ShapeProperties.cs, SpreadsheetDrawing.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 CT_ShapeProperties.Write (cyclomatic 17) finding(s) in Cyclomatic Complexity — start with ShapeProperties.cs, SpreadsheetDrawing.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 CT_Settings.Write (cyclomatic 102) finding(s) in Cyclomatic Complexity — start with Settings.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 385 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 CT_ShapeProperties.Parse (cognitive 19) finding(s) in Cognitive Complexity — start with ShapeProperties.cs, SpreadsheetDrawing.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 CT_ShapeProperties.Write (cognitive 16) finding(s) in Cognitive Complexity — start with ShapeProperties.cs, SpreadsheetDrawing.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 CT_ParaRPrOriginal.Write (cognitive 121) finding(s) in Cognitive Complexity — start with Paragraph.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.0 / 10Exemplary✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
+ 21 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.8 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with FileSharingRecord.cs. — One of this dimension's main actionable groups (1 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
53 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is OpenXmlFormats/Wordprocessing/Paragraph.cs.
Off-boarding risk: anonymized user #1 · ×3
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D17 · Explicit Debt8.6 / 10Strong✓ 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.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 75 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (73), NPOI.Core.csproj, NPOI.Benchmarks.csproj. — One of this dimension's main actionable groups (75 issue-level).
Resolve the 5 EmptyCatchBlock finding(s) in Explicit Debt — start with FontCharset.cs, StandardDecryptor.cs, StandardEncryptor.cs. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 649 CommentedOutCode finding(s) in Explicit Debt — start with TestSignatureInfo.cs (27), TestXSSFRichTextString.cs (22), ShapeEffects.cs (18). — One of this dimension's main actionable groups (649 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
NPOI's documentation is mostly a single README plus an untrusted YouTube tutorial link and a one-line README for a unrelated project; the main repository has no architecture or design docs and only 12% XML-doc coverage across its packages. The EULA/fee section is present but not well integrated into the README, leaving the reader with little guidance on how to get started.
The README links only to YouTube tutorials ('How NPOI library succeeds') and an untrusted GitHub wiki, with no real documentation.README.md
Resolve the 1 The README links only to YouTube tutorials ('How NPOI library succeeds')… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
3 of 10 projects flagged as possibly oversized/incoherent.
Split NPOI.Core
Split NPOI.OOXML.Core
Split NPOI.OpenXmlFormats.Core
What to do
Resolve the 1 Split NPOI.Core finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Split NPOI.OOXML.Core finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Split NPOI.OpenXmlFormats.Core finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability6.7 / 10Adequate✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
68 % of calls cross a namespace and 2 % go through an interface, but 71 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.
What to do
Improve Navigability — currently 6.7/10. — 68 % of calls cross a namespace and 2 % go through an interface, but 71 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
High: github-actions-mutable-action-tag · ×18.github/workflows/CI.yml:34detected by semgrep finding
Medium: regular-expression-dosopenxml4Net/Util/XmlHelper.cs:289detected by semgrep finding
What to do
Resolve the 18 High finding(s) in Static Analysis (SAST) — start with CI.yml (6), PR.yml (6), static.yml (4). — One of this dimension's main actionable groups (18 issue-level).
Resolve the 1 Medium finding(s) in Static Analysis (SAST) — start with XmlHelper.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
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.
350 of 1403 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotCacheDefinition.cs.
Resolve the 37 Orphaned knowledge finding(s) in Knowledge Freshness — start with CT_PivotCacheDefinition.cs, Sdt.cs, OfficeDrawing.cs. — One of this dimension's main actionable groups (37 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PR-triggered workflow without a permissions block finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
`IEvaluationWorkbook` declares 16 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — EvaluationWorkbook.cs:84
`IBorderFormatting` declares 21 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — BorderFormatting.cs:26
`ICell` declares 36 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cell.cs:53
`ICellStyle` declares 34 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — CellStyle.cs:24
`IColumn` declares 22 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Column.cs:25
`IConditionalFormattingRule` declares 19 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — ConditionalFormattingRule.cs:27
`IPrintSetup` declares 20 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — PrintSetup.cs:33
`IRow` declares 23 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Row.cs:37
`ISheet` declares 115 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Sheet.cs:88
`IWorkbook` declares 59 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Workbook.cs:35
`ICell` declares 39 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cell.cs:53
`IPackageProperties` declares 35 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — PackageProperties.cs:14
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
C1 · Data Protection3.5 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×25) — EscherArrayProperty.cs:283, EscherArrayProperty.cs:299, DocumentSummaryInformation.cs:737, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
`CT_Property` has 36 unfinished members out of 39 — a scaffolded type that was never implemented. — DocumentPropertiesCustom.cs:78
`IsSetFiletime` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — DocumentPropertiesCustom.cs:146
`IsSetBool` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — DocumentPropertiesCustom.cs:151
`GetBool` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — DocumentPropertiesCustom.cs:156
`IsSetI1` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — DocumentPropertiesCustom.cs:161
`GetI1` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — DocumentPropertiesCustom.cs:166
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 9 of 10 project(s) that lack one — worth up to 1.8 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 `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Maturity · Maturity — Whether the 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.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries. Exhaustive, deterministic.
18874/20526 types (92%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
What to do
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · 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 library protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Raise allocation-aware density on the hot paths — currently 48 use(s) across 485,713 production line(s) (~0.1/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code keeps its host responsive — a library awaits with ConfigureAwait(false) (so it never captures and stalls the host's context) and avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a library with ≥5 awaits — the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Cryptographic hygiene (weak hash/cipher, password key-derivation). This codebase has no web surface, so transport/header/cookie/CSRF controls are N/A and only crypto is scored.
Identifier 'PasswordHash' looks like a password-hash field/property, but no KDF (PBKDF2 / Argon2 / BCrypt / PasswordHasher) was found anywhere in the source — so passwords aren't protected by a salted key-derivation function (whether a fast/plain hash, or a client-hashed value stored and compared verbatim). Password storage needs a salted KDF and a constant-time compare. — WorksheetProtectionBlock.cs:278
MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — Biff8EncryptionKey.cs:94
What to do
Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `main/HSSF/Record/Aggregates/WorksheetProtectionBlock.cs:278`.
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — FontCharset.cs:178, StandardEncryptor.cs:167, POILogFactory.cs:89
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch. (×2) — StandardDecryptor.cs:327, SheetDataWriter.cs:126
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Not included — 48 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
D10 Test Quality — Test Quality not included (time budget)
D11 Test Reliability — Test reliability not included
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D24 Comment Value — LLM evaluation failed
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this check looks for (a Domain/Aggregates/ValueObjects layer)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, 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'.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — no async methods found
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
NoWarnInCsproj main/NPOI.Core.csproj:9— CS8002 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj benchmarks/NPOI.Benchmarks/NPOI.Benchmarks.csproj:7— SYSLIB0014 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj testcases/Directory.Build.props:15— SYSLIB0014 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:36— CS0419 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:37— CS1570 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:38— CS1572 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:39— CS1573 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:40— CS1574 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:41— CS1584 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:42— CS1587 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:43— CS1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:44— CS1734 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:50— CS0108 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:51— CS0114 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:52— CS0162 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj testcases/Directory.Build.props:13— CS0162 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:53— CS0168 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:54— CS0169 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:55— CS0414 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:56— CS0628 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:57— CS0649 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:58— CS0659 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:59— NU1900 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:61— CS0612 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj testcases/Directory.Build.props:11— CS0612 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
Orphaned knowledge OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotCacheDefinition.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge OpenXmlFormats/Wordprocessing/Sdt.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge OpenXmlFormats/Vml/OfficeDrawing.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge OpenXmlFormats/Wordprocessing/CustomXml.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge OpenXmlFormats/Wordprocessing/HdrFtr.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge OpenXmlFormats/Wordprocessing/Markup.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge OpenXmlFormats/Drawing/ShapeGeometry.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge ooxml/XSSF/UserModel/XSSFTextParagraph.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge main/SS/Util/PropertyTemplate.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge ooxml/POIFS/Crypt/Dsig/SignatureConfig.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge OpenXmlFormats/Spreadsheet/ExternalConnections.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge ooxml/XDDF/UserModel/PresetGeometry.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge ooxml/XSSF/UserModel/XSSFSimpleShape.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge main/POIFS/Crypt/CryptoFunctions.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge OpenXmlFormats/Drawing/Chart/PieChart.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge main/SS/Formula/DataValidationEvaluator.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge ooxml/XDDF/UserModel/Text/XDDFTextParagraph.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge ooxml/POIFS/Crypt/Dsig/SignatureInfo.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge ooxml/XDDF/UserModel/PresetColor.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge ooxml/XDDF/UserModel/Text/XDDFTextRun.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge main/Util/LocaleUtil.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge OpenXmlFormats/Spreadsheet/Styles/CT_Font.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge ooxml/XSSF/UserModel/XSSFPivotTable.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge OpenXmlFormats/Vml/SpreadsheetDrawing.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge openxml4Net/OPC/PackagePartName.cs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
High: github-actions-mutable-action-tag .github/workflows/CI.yml:34— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/CI.yml:38— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/CI.yml:42— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/CI.yml:52— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/CI.yml:56— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/CI.yml:60— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/PR.yml:32— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/PR.yml:36— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/PR.yml:40— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/PR.yml:50— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/PR.yml:54— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/PR.yml:58— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/opencode.yml:24— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v6`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/opencode.yml:29— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: anomalyco/opencode/github@<40-character SHA>`. This step references `anomalyco/opencode/github@latest`; resolve the SHA it points at today with `gh api repos/anomalyco/opencode/commits/latest --jq .sha`. `anomalyco/opencode/github` is hosted INSIDE the `anomalyco/opencode` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `anomalyco/opencode/github` path in `uses:` and query only `anomalyco/opencode`.
High: github-actions-mutable-action-tag .github/workflows/static.yml:33— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/static.yml:37— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/configure-pages@<40-character SHA>`. This step references `actions/configure-pages@v5`; resolve the SHA it points at today with `gh api repos/actions/configure-pages/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/static.yml:39— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-pages-artifact@<40-character SHA>`. This step references `actions/upload-pages-artifact@v3`; resolve the SHA it points at today with `gh api repos/actions/upload-pages-artifact/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/static.yml:45— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/deploy-pages@<40-character SHA>`. This step references `actions/deploy-pages@v4`; resolve the SHA it points at today with `gh api repos/actions/deploy-pages/commits/v4 --jq .sha`.
EmptyCatchBlock main/Common/UserModel/Fonts/FontCharset.cs:178— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock main/POIFS/Crypt/Standard/StandardDecryptor.cs:327— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock main/POIFS/Crypt/Standard/StandardEncryptor.cs:167— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock main/Util/POILogFactory.cs:89— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock ooxml/XSSF/Streaming/SheetDataWriter.cs:126— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
Leaked secret: hardcoded-credential main/HSSF/Record/FileSharingRecord.cs:167— hardcoded-credential detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
TodoComment OpenXmlFormats/Spreadsheet/CustomXmlMappings.cs:20— // TODO the initial elements of schemaField and mapField must be ensured somewhere else - or is there a save default!? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment OpenXmlFormats/Spreadsheet/CustomXmlMappings.cs:108— // TODO ensure initialization = new XmlElement(); // 1..1 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotCacheDefinition.cs:144— //TODO add namespaceUri — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotCacheRecords.cs:64— //TODO add namespaceUri — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment OpenXmlFormats/Spreadsheet/SharedString/CT_Rst.cs:43— //TODO: diff has-space case and no-space case — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment OpenXmlFormats/Spreadsheet/Sheet/CT_Comment.cs:96— // 0..1 TODO: Type is ST_Guid — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment OpenXmlFormats/Spreadsheet/Styles/CT_Colors.cs:183— // TODO change all the uses theme to use uint instead of signed integer variants — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment OpenXmlFormats/Spreadsheet/Styles/CT_Colors.cs:405— // TODO change all the uses theme to use uint instead of signed integer variants — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment OpenXmlFormats/Spreadsheet/Styles/CT_Fill.cs:116— //TODO: NPOI duplication code, fix it. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment OpenXmlFormats/Vml/Main.cs:1326— // TODO remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/DDF/EscherArrayProperty.cs:201— // TODO: this part is strange - it doesn't make sense to compare — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/DDF/EscherContainerRecord.cs:289— // TODO - keep looping? Do we expect multiple matches? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/GlobalSuppressions.cs:12— // TODO fix warnings: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/GlobalSuppressions.cs:42— // TODO fix warnings: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/GlobalSuppressions.cs:78— // TODO: apply fix that is proposed in the code: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/GlobalSuppressions.cs:91— // TODO: fix needs some minutes, because the constructor adds itself to the given parameter BlockList. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/HPSF/CodePageString.cs:53— // TODO Some files, such as TestVisioWithCodepage.vsd, are currently
TodoComment main/HSSF/Extractor/EventBasedExcelExtractor.cs:262— // TODO: Find object to match nrec.GetShapeId() — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/HSSF/Extractor/OldExcelExtractor.cs:243— // TODO track the XFs and Format Strings — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/HSSF/Extractor/OldExcelExtractor.cs:328— // TODO Need to fetch / use format strings — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/HSSF/Model/InternalChart.cs:874— // TODO: Add Pattern constants to record — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/HSSF/UserModel/HSSFChart.cs:886— // TODO: Add Pattern constants to record — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/HSSF/Model/InternalSheet.cs:56— // TODO - Is it legal for dims record to be missing? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/HSSF/Model/InternalSheet.cs:212— // TODO - take chart streams off into separate java objects — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/HPSF/PropertySet.cs:420— /* FIXME (3): Ensure that at most "length" bytes are read. */ — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/HPSF/PropertySet.cs:466— /* FIXME (3): Ensure that at most "length" bytes are read. */ — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/HPSF/SummaryInformation.cs:438— /* FIXME: */ — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/HPSF/TypeWriter.cs:52— // FIXME: unsigned — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/HSSF/UserModel/HSSFDataValidation.cs:58— //FIXME: This cast can be avoided. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/HSSF/UserModel/HSSFSheet.cs:739— // FIXME: this may be faster if it looped over array formulas directly rather than looping over each cell in — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/SS/Util/CellAddress.cs:84— // FIXME: breaks if Address Contains a sheet name or dollar signs from an absolute CellReference — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/SS/Util/CellReference.cs:72— // FIXME: _sheetName may be null, depending on the entry point. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/SS/Util/CellUtil.cs:143— // FIXME: Cached value may be stale — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/Streaming/AutoSizeColumnTracker.cs:326— // FIXME: if cell belongs to a merged region, some of the merged region may have fallen outside of the random access window — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/Streaming/AutoSizeColumnTracker.cs:346— // FIXME: if cell belongs to a merged region, some of the merged region may have fallen outside of the random access window — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/Streaming/AutoSizeColumnTracker.cs:329— // FIXME: Most cells are not merged, so calling getCellWidth twice re-computes the same value twice. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/Streaming/AutoSizeColumnTracker.cs:349— // FIXME: Most cells are not merged, so calling getCellWidth twice re-computes the same value twice. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/BaseXSSFEvaluationWorkbook.cs:397— // FIXME: use org.apache.commons.collections.map.CaseInsensitiveMap — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFColor.cs:412— // FIXME: this method would be more useful if it could convert any Color to an XSSFColor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFDataValidationConstraint.cs:99— //FIXME: Need to confirm if this is not a formula. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFHyperlink.cs:116— //FIXME: change to protected if/when SXSSFHyperlink class is created — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFRow.cs:475— // FIXME: remove type casting when copyCellFrom(Cell, CellCopyPolicy) is added to Cell interface — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFRow.cs:522— // FIXME: is this something that rowShifter could be doing? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFSheet.cs:3302— // FIXME: is this something that rowShifter could be doing? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFSheet.cs:3265— // FIXME: is special behavior needed if srcRows and destRows belong to the same sheets and the regions overlap? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFSheet.cs:3274— // FIXME: if srcRows contains gaps or null values, clear out those rows that will be overwritten — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFSheet.cs:4987— // FIXME: this may be faster if it looped over array formulas — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFSheet.cs:5524— // FIXME: (performance optimization) this should be moved outside the for-loop so that comments only needs to be iterated over once. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment ooxml/XSSF/UserModel/XSSFSheet.cs:5550— // FIXME: (performance optimization) this should be moved outside the for-loop so that hyperlinks only needs to be iterated over once. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FileTooLong: PivotTable/CT_PivotCacheDefinition.cs OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotCacheDefinition.cs:0— FileTooLong — 4778 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Wordprocessing/Paragraph.cs OpenXmlFormats/Wordprocessing/Paragraph.cs:0— FileTooLong — 4663 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: PivotTable/CT_PivotTableDefinition.cs OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotTableDefinition.cs:0— FileTooLong — 4124 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Wordprocessing/Settings.cs OpenXmlFormats/Wordprocessing/Settings.cs:0— FileTooLong — 3973 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Wordprocessing/Table.cs OpenXmlFormats/Wordprocessing/Table.cs:0— FileTooLong — 3582 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Vml/Main.cs OpenXmlFormats/Vml/Main.cs:0— FileTooLong — 3570 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UserModel/XSSFSheet.cs ooxml/XSSF/UserModel/XSSFSheet.cs:0— FileTooLong — 2926 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Drawing/ShapeEffects.cs OpenXmlFormats/Drawing/ShapeEffects.cs:0— FileTooLong — 2547 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Vml/OfficeDrawing.cs OpenXmlFormats/Vml/OfficeDrawing.cs:0— FileTooLong — 2241 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Wordprocessing/Sdt.cs OpenXmlFormats/Wordprocessing/Sdt.cs:0— FileTooLong — 1946 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Wordprocessing/Run.cs OpenXmlFormats/Wordprocessing/Run.cs:0— FileTooLong — 1672 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Wordprocessing/CustomXml.cs OpenXmlFormats/Wordprocessing/CustomXml.cs:0— FileTooLong — 1540 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Util/BigInteger.cs main/Util/BigInteger.cs:0— FileTooLong — 1513 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Wordprocessing/Styles.cs OpenXmlFormats/Wordprocessing/Styles.cs:0— FileTooLong — 1403 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Drawing/ShapeProperties.cs OpenXmlFormats/Drawing/ShapeProperties.cs:0— FileTooLong — 1376 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Model/InternalWorkbook.cs main/HSSF/Model/InternalWorkbook.cs:0— FileTooLong — 1327 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Drawing/ShapeGeometry.cs OpenXmlFormats/Drawing/ShapeGeometry.cs:0— FileTooLong — 1323 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UserModel/HSSFSheet.cs main/HSSF/UserModel/HSSFSheet.cs:0— FileTooLong — 1262 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Drawing/SpreadsheetDrawing.cs OpenXmlFormats/Drawing/SpreadsheetDrawing.cs:0— FileTooLong — 1221 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Formula/FormulaParser.cs main/SS/Formula/FormulaParser.cs:0— FileTooLong — 1158 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Wordprocessing/HdrFtr.cs OpenXmlFormats/Wordprocessing/HdrFtr.cs:0— FileTooLong — 1082 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Wordprocessing/Numbering.cs OpenXmlFormats/Wordprocessing/Numbering.cs:0— FileTooLong — 1075 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UserModel/XSSFWorkbook.cs ooxml/XSSF/UserModel/XSSFWorkbook.cs:0— FileTooLong — 971 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Spreadsheet/ExternalConnections.cs OpenXmlFormats/Spreadsheet/ExternalConnections.cs:0— FileTooLong — 963 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UserModel/HSSFWorkbook.cs main/HSSF/UserModel/HSSFWorkbook.cs:0— FileTooLong — 934 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
TooManyMethods: CT_P OpenXmlFormats/Wordprocessing/Paragraph.cs:0— TooManyMethods — 609 significant lines (blank, comment-only and punctuation-only lines excluded), 240 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CT_R OpenXmlFormats/Wordprocessing/Run.cs:0— TooManyMethods — 577 significant lines (blank, comment-only and punctuation-only lines excluded), 240 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CT_Comment OpenXmlFormats/Wordprocessing/Markup.cs:0— TooManyMethods — 499 significant lines (blank, comment-only and punctuation-only lines excluded), 221 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XSSFSheet ooxml/XSSF/UserModel/XSSFSheet.cs:0— TooManyMethods — 2862 significant lines (blank, comment-only and punctuation-only lines excluded), 209 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HSSFSheet main/HSSF/UserModel/HSSFSheet.cs:0— TooManyMethods — 1212 significant lines (blank, comment-only and punctuation-only lines excluded), 126 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XSSFWorkbook ooxml/XSSF/UserModel/XSSFWorkbook.cs:0— TooManyMethods — 947 significant lines (blank, comment-only and punctuation-only lines excluded), 125 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SXSSFSheet ooxml/XSSF/Streaming/SXSSFSheet.cs:0— TooManyMethods — 580 significant lines (blank, comment-only and punctuation-only lines excluded), 118 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HSSFWorkbook main/HSSF/UserModel/HSSFWorkbook.cs:0— TooManyMethods — 893 significant lines (blank, comment-only and punctuation-only lines excluded), 110 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InternalWorkbook main/HSSF/Model/InternalWorkbook.cs:0— TooManyMethods — 1313 significant lines (blank, comment-only and punctuation-only lines excluded), 107 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XWPFDocument ooxml/XWPF/Usermodel/XWPFDocument.cs:0— TooManyMethods — 698 significant lines (blank, comment-only and punctuation-only lines excluded), 100 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CT_TrPrBase OpenXmlFormats/Wordprocessing/Table.cs:0— TooManyMethods — 264 significant lines (blank, comment-only and punctuation-only lines excluded), 95 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InternalSheet main/HSSF/Model/InternalSheet.cs:0— TooManyMethods — 846 significant lines (blank, comment-only and punctuation-only lines excluded), 81 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OPCPackage openxml4Net/OPC/OPCPackage.cs:0— TooManyMethods — 622 significant lines (blank, comment-only and punctuation-only lines excluded), 72 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BigInteger main/Util/BigInteger.cs:0— TooManyMethods — 753 significant lines (blank, comment-only and punctuation-only lines excluded), 70 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FormulaParser main/SS/Formula/FormulaParser.cs:0— TooManyMethods — 1098 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SignatureConfig ooxml/POIFS/Crypt/Dsig/SignatureConfig.cs:0— TooManyMethods — 253 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CT_Font OpenXmlFormats/Spreadsheet/Styles/CT_Font.cs:0— TooManyMethods — 447 significant lines (blank, comment-only and punctuation-only lines excluded), 68 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SXSSFWorkbook ooxml/XSSF/Streaming/SXSSFWorkbook.cs:0— TooManyMethods — 370 significant lines (blank, comment-only and punctuation-only lines excluded), 67 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XDDFChart ooxml/XDDF/UserModel/Chart/XDDFChart.cs:0— TooManyMethods — 414 significant lines (blank, comment-only and punctuation-only lines excluded), 66 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MutableBigInteger main/Util/BigInteger.cs:0— TooManyMethods — 755 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CT_Worksheet OpenXmlFormats/Spreadsheet/Sheet/CT_Worksheet.cs:0— TooManyMethods — 595 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InternalChart main/HSSF/Model/InternalChart.cs:0— TooManyMethods — 568 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XSSFDialogsheet ooxml/XSSF/UserModel/XSSFDialogsheet.cs:0— TooManyMethods — 275 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HSSFChart main/HSSF/UserModel/HSSFChart.cs:0— TooManyMethods — 753 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CT_RPrElt OpenXmlFormats/Spreadsheet/SharedString/CT_RPrElt.cs:0— TooManyMethods — 329 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Low cohesion: CT_RPr (LCOM4 26) OpenXmlFormats/Wordprocessing/Paragraph.cs:3975— CT_RPr's methods form 26 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: SignatureConfig (LCOM4 24) ooxml/POIFS/Crypt/Dsig/SignatureConfig.cs:37— SignatureConfig's methods form 24 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_Worksheet (LCOM4 23) OpenXmlFormats/Spreadsheet/Sheet/CT_Worksheet.cs:10— CT_Worksheet's methods form 23 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_RPrElt (LCOM4 16) OpenXmlFormats/Spreadsheet/SharedString/CT_RPrElt.cs:14— CT_RPrElt's methods form 16 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: InternalSheet (LCOM4 12) main/HSSF/Model/InternalSheet.cs:49— InternalSheet's methods form 12 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_TextListStyle (LCOM4 11) OpenXmlFormats/Drawing/Text.cs:108— CT_TextListStyle's methods form 11 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_PPrBase (LCOM4 11) OpenXmlFormats/Wordprocessing/Paragraph.cs:6117— CT_PPrBase's methods form 11 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_LineSer (LCOM4 10) OpenXmlFormats/Drawing/Chart/LineChart.cs:12— CT_LineSer's methods form 10 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_ScatterSer (LCOM4 10) OpenXmlFormats/Drawing/Chart/ScatterChart.cs:15— CT_ScatterSer's methods form 10 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_PieSer (LCOM4 9) OpenXmlFormats/Drawing/Chart/PieChart.cs:306— CT_PieSer's methods form 9 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_TextBodyProperties (LCOM4 9) OpenXmlFormats/Drawing/Text.cs:513— CT_TextBodyProperties's methods form 9 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_AreaSer (LCOM4 8) OpenXmlFormats/Drawing/Chart/AreaChart.cs:220— CT_AreaSer's methods form 8 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_BarSer (LCOM4 8) OpenXmlFormats/Drawing/Chart/BarChart.cs:470— CT_BarSer's methods form 8 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_RadarSer (LCOM4 8) OpenXmlFormats/Drawing/Chart/RadarChart.cs:14— CT_RadarSer's methods form 8 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_ShapeProperties (LCOM4 8) OpenXmlFormats/Drawing/SpreadsheetDrawing.cs:583— CT_ShapeProperties's methods form 8 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_PivotTableDefinition (LCOM4 8) OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotTableDefinition.cs:14— CT_PivotTableDefinition's methods form 8 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_ClientData (LCOM4 8) OpenXmlFormats/Vml/SpreadsheetDrawing.cs:12— CT_ClientData's methods form 8 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_BarChart (LCOM4 7) OpenXmlFormats/Drawing/Chart/BarChart.cs:14— CT_BarChart's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_SolidColorFillProperties (LCOM4 7) OpenXmlFormats/Drawing/ShapeEffects.cs:1983— CT_SolidColorFillProperties's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_Workbook (LCOM4 7) OpenXmlFormats/Spreadsheet/Workbook/CT_Workbook.cs:12— CT_Workbook's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_Shape (LCOM4 7) OpenXmlFormats/Vml/Main.cs:615— CT_Shape's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_Shapetype (LCOM4 7) OpenXmlFormats/Vml/Main.cs:3701— CT_Shapetype's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_PPr (LCOM4 7) OpenXmlFormats/Wordprocessing/Paragraph.cs:951— CT_PPr's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_TblPrBase (LCOM4 7) OpenXmlFormats/Wordprocessing/Table.cs:1144— CT_TblPrBase's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: CT_TblBorders (LCOM4 7) OpenXmlFormats/Wordprocessing/Table.cs:2348— CT_TblBorders's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
ClassTooLong: CT_Settings OpenXmlFormats/Wordprocessing/Settings.cs:0— ClassTooLong — 1161 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CT_PivotTableDefinition OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotTableDefinition.cs:0— ClassTooLong — 1052 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CT_Compat OpenXmlFormats/Wordprocessing/Settings.cs:0— ClassTooLong — 737 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CT_PivotField OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotTableDefinition.cs:0— ClassTooLong — 642 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EscherDump main/DDF/EscherDump.cs:0— ClassTooLong — 620 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: EscherProperties main/DDF/EscherProperties.cs:0— ClassTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: PresetGeometryExtensions ooxml/XDDF/UserModel/PresetGeometry.cs:0— ClassTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: ExtendedFormatRecord main/HSSF/Record/ExtendedFormatRecord.cs:0— ClassTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FormulaShifter main/SS/Formula/FormulaShifter.cs:0— ClassTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CT_ParaRPr OpenXmlFormats/Wordprocessing/Paragraph.cs:0— ClassTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LocaleUtil main/Util/LocaleUtil.cs:0— ClassTooLong — 494 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: CellNumberFormatter main/SS/Format/CellNumberFormatter.cs:0— ClassTooLong — 491 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CT_PPrBase OpenXmlFormats/Wordprocessing/Paragraph.cs:0— ClassTooLong — 482 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ExcelToHtmlConverter ooxml/SS/Converter/ExcelToHtmlConverter.cs:0— ClassTooLong — 479 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EscherAggregate main/HSSF/Record/EscherAggregate.cs:0— ClassTooLong — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: XSSFSimpleShape ooxml/XSSF/UserModel/XSSFSimpleShape.cs:0— ClassTooLong — 461 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: XWPFTable ooxml/XWPF/Usermodel/XWPFTable.cs:0— ClassTooLong — 443 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CT_Tbl OpenXmlFormats/Wordprocessing/Table.cs:0— ClassTooLong — 428 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PresetColorExtensions ooxml/XDDF/UserModel/PresetColor.cs:0— ClassTooLong — 424 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: DataFormatter main/SS/UserModel/DataFormatter.cs:0— ClassTooLong — 421 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CT_Stroke OpenXmlFormats/Vml/Main.cs:0— ClassTooLong — 406 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FunctionEval main/SS/Formula/Eval/FunctionEval.cs:0— ClassTooLong — 404 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Duplicated block (8 lines × 2) main/Common/UserModel/Fonts/FontCharset.cs:149— main/Common/UserModel/Fonts/FontCharset.cs:149-156 | main/SS/UserModel/FontCharset.cs:83-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) main/DDF/AbstractEscherOptRecord.cs:232— main/DDF/AbstractEscherOptRecord.cs:232-239 | main/DDF/EscherOptRecord.cs:93-100 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/DDF/AbstractEscherOptRecord.cs:232` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) main/DDF/EscherClientAnchorRecord.cs:174— main/DDF/EscherClientAnchorRecord.cs:174-181 | main/DDF/EscherClientDataRecord.cs:112-119 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/DDF/EscherClientAnchorRecord.cs:174` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) main/DDF/EscherMetafileBlip.cs:344— main/DDF/EscherMetafileBlip.cs:344-351 | main/DDF/EscherPictBlip.cs:278-285 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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) main/HSSF/Model/InternalChart.cs:431— main/HSSF/Model/InternalChart.cs:431-438 | main/HSSF/UserModel/HSSFChart.cs:637-644 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) main/HSSF/Model/InternalChart.cs:474— main/HSSF/Model/InternalChart.cs:474-481 | main/HSSF/UserModel/HSSFChart.cs:680-687 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:474` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) main/HSSF/Model/InternalChart.cs:659— main/HSSF/Model/InternalChart.cs:659-666 | main/HSSF/UserModel/HSSFChart.cs:867-874 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:659` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) main/HSSF/Model/InternalChart.cs:762— main/HSSF/Model/InternalChart.cs:762-769 | main/HSSF/UserModel/HSSFChart.cs:417-424 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:762` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) main/HSSF/Model/InternalChart.cs:806— main/HSSF/Model/InternalChart.cs:806-813 | main/HSSF/UserModel/HSSFChart.cs:400-407 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:806` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) main/HSSF/Model/InternalChart.cs:870— main/HSSF/Model/InternalChart.cs:870-877 | main/HSSF/UserModel/HSSFChart.cs:882-889 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:870` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) main/HSSF/Model/InternalChart.cs:883— main/HSSF/Model/InternalChart.cs:883-890 | main/HSSF/UserModel/HSSFChart.cs:895-902 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:883` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) main/HSSF/Model/InternalChart.cs:896— main/HSSF/Model/InternalChart.cs:896-903 | main/HSSF/UserModel/HSSFChart.cs:908-915 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:896` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) main/HSSF/UserModel/HSSFChart.cs:735— main/HSSF/UserModel/HSSFChart.cs:735-742 | main/HSSF/UserModel/HSSFChart.cs:765-772 — 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 `main/HSSF/UserModel/HSSFChart.cs:735` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) main/POIFS/Storage/DataInputBlock.cs:130— main/POIFS/Storage/DataInputBlock.cs:130-137 | main/Util/LittleEndianByteArrayInputStream.cs:115-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) main/SS/Formula/Atp/FinancialAtpFunctions.cs:560— main/SS/Formula/Atp/FinancialAtpFunctions.cs:560-571 | main/SS/Formula/Atp/FinancialAtpFunctions.cs:613-620 — 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 `main/SS/Formula/Atp/FinancialAtpFunctions.cs:560` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) main/SS/Formula/Atp/FinancialAtpFunctions.cs:851— main/SS/Formula/Atp/FinancialAtpFunctions.cs:851-858 | main/SS/Formula/Atp/FinancialAtpFunctions.cs:881-888 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) main/SS/Util/SheetUtil.cs:542— main/SS/Util/SheetUtil.cs:542-549 | main/SS/Util/SheetUtil.cs:563-570 — 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 `main/SS/Util/SheetUtil.cs:542` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) main/HSSF/Model/InternalChart.cs:406— main/HSSF/Model/InternalChart.cs:406-414 | main/HSSF/UserModel/HSSFChart.cs:612-620 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) main/HSSF/Model/InternalChart.cs:493— main/HSSF/Model/InternalChart.cs:493-501 | main/HSSF/UserModel/HSSFChart.cs:564-572 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) main/HSSF/Model/InternalChart.cs:506— main/HSSF/Model/InternalChart.cs:506-514 | main/HSSF/UserModel/HSSFChart.cs:577-585 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:506` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) main/HSSF/Record/CFRule12Record.cs:413— main/HSSF/Record/CFRule12Record.cs:413-421 | main/HSSF/Record/CFRuleRecord.cs:141-149 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/CFRule12Record.cs:413` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) main/HSSF/Record/Chart/AlRunsRecord.cs:127— main/HSSF/Record/Chart/AlRunsRecord.cs:127-135 | main/HSSF/Record/Chart/ChartTitleFormatRecord.cs:121-129 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/Chart/AlRunsRecord.cs:127` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) main/HSSF/Record/Chart/AlRunsRecord.cs:147— main/HSSF/Record/Chart/AlRunsRecord.cs:147-155 | main/HSSF/Record/Chart/ChartTitleFormatRecord.cs:141-149 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/Chart/AlRunsRecord.cs:147` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) main/HSSF/Record/Chart/CrtLayout12ARecord.cs:61— main/HSSF/Record/Chart/CrtLayout12ARecord.cs:61-69 | main/HSSF/Record/Chart/CrtLayout12Record.cs:153-161 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
Duplicated block (9 lines × 2) main/HSSF/Record/Chart/CrtLayout12ARecord.cs:112— main/HSSF/Record/Chart/CrtLayout12ARecord.cs:112-120 | main/HSSF/Record/Chart/CrtLayout12Record.cs:102-110 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) main/HSSF/UserModel/HSSFCombobox.cs:47— main/HSSF/UserModel/HSSFCombobox.cs:47-55 | main/HSSF/UserModel/HSSFPolygon.cs:60-68 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/UserModel/HSSFCombobox.cs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) main/POIFS/FileSystem/DocumentFactoryHelper.cs:199— main/POIFS/FileSystem/DocumentFactoryHelper.cs:199-209 | main/POIFS/FileSystem/DocumentFactoryHelper.cs:227-235 — 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 `main/POIFS/FileSystem/DocumentFactoryHelper.cs:199` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) main/POIFS/FileSystem/NPOIFSStream.cs:237— main/POIFS/FileSystem/NPOIFSStream.cs:237-245 | main/Util/OutputStream.cs:22-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/Util/OutputStream.cs:22` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) main/SS/Formula/Functions/Text/Mid.cs:32— main/SS/Formula/Functions/Text/Mid.cs:32-40 | main/SS/Formula/Functions/Text/Replace.cs:44-52 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Functions/Text/Mid.cs:32` 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) main/DDF/EscherMetafileBlip.cs:94— main/DDF/EscherMetafileBlip.cs:94-100 | main/DDF/EscherPictBlip.cs:76-82 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) main/DDF/EscherMetafileBlip.cs:148— main/DDF/EscherMetafileBlip.cs:148-154 | main/DDF/EscherPictBlip.cs:121-127 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) main/DDF/EscherSpgrRecord.cs:73— main/DDF/EscherSpgrRecord.cs:73-79 | main/DDF/EscherSpRecord.cs:83-90 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/DDF/EscherSpgrRecord.cs:73` 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) main/HSSF/Record/Chart/AxisOptionsRecord.cs:108— main/HSSF/Record/Chart/AxisOptionsRecord.cs:108-114 | main/HSSF/Record/Chart/CategorySeriesAxisRecord.cs:72-78 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/Chart/AxisOptionsRecord.cs:108` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) main/HSSF/Record/Chart/ChartStartBlockRecord.cs:83— main/HSSF/Record/Chart/ChartStartBlockRecord.cs:83-89 | main/HSSF/Record/Chart/StartBlockRecord.cs:100-106 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/Chart/ChartStartBlockRecord.cs:83` 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) main/HSSF/Record/Chart/DataLabelExtensionRecord.cs:78— main/HSSF/Record/Chart/DataLabelExtensionRecord.cs:78-84 | main/HSSF/Record/Chart/DataLabExtRecord.cs:77-83 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/Chart/DataLabelExtensionRecord.cs:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) main/HSSF/UserModel/EscherGraphics.cs:245— main/HSSF/UserModel/EscherGraphics.cs:245-251 | main/HSSF/UserModel/EscherGraphics.cs:398-404 — 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 `main/HSSF/UserModel/EscherGraphics.cs:245` 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) main/POIFS/Crypt/BinaryRC4/BinaryRC4Encryptor.cs:88— main/POIFS/Crypt/BinaryRC4/BinaryRC4Encryptor.cs:88-94 | main/POIFS/Crypt/CryptoAPI/CryptoAPIEncryptor.cs:42-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/POIFS/Crypt/BinaryRC4/BinaryRC4Encryptor.cs:88` 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) main/SS/Formula/Atp/FinancialAtpFunctions.cs:32— main/SS/Formula/Atp/FinancialAtpFunctions.cs:32-38 | main/SS/Formula/Atp/FinancialAtpFunctions.cs:53-59 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Atp/FinancialAtpFunctions.cs:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) main/SS/Formula/Atp/FinancialAtpFunctions.cs:74— main/SS/Formula/Atp/FinancialAtpFunctions.cs:74-80 | main/SS/Formula/Atp/FinancialAtpFunctions.cs:99-105 — 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 `main/SS/Formula/Atp/FinancialAtpFunctions.cs:74` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) main/SS/UserModel/IndexedColors.cs:229— main/SS/UserModel/IndexedColors.cs:229-235 | main/SS/UserModel/IndexedColors.cs:237-243 — 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.
HackComment main/HSSF/Record/FeatHdrRecord.cs:125— //HACK: do a "cheat" Clone, see Record.java for more information — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment main/HSSF/Record/FeatRecord.cs:217— //HACK: do a "cheat" Clone, see Record.java for more information — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment main/HSSF/Record/HeaderFooterRecord.cs:117— //HACK: do a "cheat" Clone, see Record.java for more information — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment main/HSSF/Record/UserSViewBegin.cs:102— //HACK: do a "cheat" Clone, see Record.java for more information — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment main/HSSF/Record/UserSViewEnd.cs:86— //HACK: do a "cheat" Clone, see Record.java for more information — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment testcases/main/HSSF/EventModel/TestEventRecordFactory.cs:69— // hack to pass boolean by ref into inner class — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment testcases/main/POIFS/FileSystem/TestNPOIFSStream.cs:234— // Hack the FAT so that it goes 0->1->2->0 — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment testcases/main/POIFS/FileSystem/TestNPOIFSStream.cs:894— // Hack the FAT so that it goes 0->1->2->0 — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment testcases/main/SS/Formula/TestEvaluationCache.cs:161— // hack to tell the difference between formula and plain value — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
Duplicated block (10 lines × 2) main/DDF/EscherBlipWMFRecord.cs:288— main/DDF/EscherBlipWMFRecord.cs:288-297 | main/DDF/EscherBSERecord.cs:353-362 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/DDF/EscherBlipWMFRecord.cs:288` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) main/DDF/EscherDggRecord.cs:111— main/DDF/EscherDggRecord.cs:111-120 | main/DDF/EscherSplitMenuColorsRecord.cs:72-81 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/DDF/EscherDggRecord.cs:111` 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 (10 lines × 2) main/HSSF/Record/Aggregates/Chart/DropBarAggregate.cs:36— main/HSSF/Record/Aggregates/Chart/DropBarAggregate.cs:36-45 | main/HSSF/Record/Aggregates/Chart/FrameAggregate.cs:37-46 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) main/HSSF/Record/Chart/CrtLayout12ARecord.cs:139— main/HSSF/Record/Chart/CrtLayout12ARecord.cs:139-148 | main/HSSF/Record/Chart/CrtLayout12Record.cs:133-142 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 (10 lines × 2) main/HSSF/UserModel/HeaderFooter.cs:61— main/HSSF/UserModel/HeaderFooter.cs:61-70 | main/HSSF/UserModel/HeaderFooter.cs:73-82 — 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 `main/HSSF/UserModel/HeaderFooter.cs:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) main/HSSF/UserModel/HSSFPolygon.cs:140— main/HSSF/UserModel/HSSFPolygon.cs:140-149 | main/HSSF/UserModel/HSSFPolygon.cs:163-172 — 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 `main/HSSF/UserModel/HSSFPolygon.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) main/SS/Formula/Functions/Dec2Bin.cs:139— main/SS/Formula/Functions/Dec2Bin.cs:139-149 | main/SS/Formula/Functions/Dec2Hex.cs:147-156 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Functions/Dec2Bin.cs:139` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) main/SS/Formula/PTG/Deleted3DPxg.cs:49— main/SS/Formula/PTG/Deleted3DPxg.cs:49-58 | main/SS/Formula/PTG/NameXPxg.cs:55-64 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) main/Util/BigInteger.cs:1537— main/Util/BigInteger.cs:1537-1546 | main/Util/BigInteger.cs:1608-1617 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) main/DDF/EscherClientAnchorRecord.cs:195— main/DDF/EscherClientAnchorRecord.cs:195-200 | main/DDF/EscherClientDataRecord.cs:124-129 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/DDF/EscherClientAnchorRecord.cs:195` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) main/HPSF/ClassID.cs:238— main/HPSF/ClassID.cs:238-243 | main/HPSF/ClassID.cs:244-249 — 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) main/HSSF/Record/Chart/ChartEndBlockRecord.cs:90— main/HSSF/Record/Chart/ChartEndBlockRecord.cs:90-95 | main/HSSF/Record/Chart/EndBlockRecord.cs:95-100 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/Chart/ChartEndBlockRecord.cs:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) main/HSSF/Record/EscherAggregate.cs:619— main/HSSF/Record/EscherAggregate.cs:619-624 | main/HSSF/Record/EscherAggregate.cs:639-644 — 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 `main/HSSF/Record/EscherAggregate.cs:619` 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) main/HSSF/UserModel/HSSFPolygon.cs:87— main/HSSF/UserModel/HSSFPolygon.cs:87-92 | main/HSSF/UserModel/HSSFTextbox.cs:95-100 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (6 lines × 2) main/SS/Formula/Atp/FinancialAtpFunctions.cs:683— main/SS/Formula/Atp/FinancialAtpFunctions.cs:683-688 | main/SS/Formula/Atp/FinancialAtpFunctions.cs:709-714 — 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 `main/SS/Formula/Atp/FinancialAtpFunctions.cs:683` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) main/SS/Formula/Atp/FinancialAtpFunctions.cs:748— main/SS/Formula/Atp/FinancialAtpFunctions.cs:748-753 | main/SS/Formula/Atp/FinancialAtpFunctions.cs:776-781 — 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 `main/SS/Formula/Atp/FinancialAtpFunctions.cs:748` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) main/SS/Formula/Functions/Index.cs:151— main/SS/Formula/Functions/Index.cs:151-156 | main/SS/Formula/Functions/Var3or4ArgFunction.cs:35-40 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Functions/Index.cs:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
XxxComment main/SS/Formula/Functions/DateFunc.cs:105— // XXX fix 1900/1904 problem — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment main/SS/Formula/Functions/WeekdayFunc.cs:90— // (XXX 1904-windowing not respected) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ooxml/POIFS/Crypt/Dsig/Facets/XAdESSignatureFacet.cs:213— // * XXX: not correct according to RFC 4514. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ooxml/SS/Converter/ExcelToHtmlConverter.cs:479— // XXX: enrich — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ooxml/SS/Converter/ExcelToHtmlConverter.cs:540— // XXX: enrich — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ooxml/SS/Converter/ExcelToHtmlUtils.cs:44— // XXX: shall we support fill? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (17 lines × 2) main/HSSF/Model/InternalWorkbook.cs:2725— main/HSSF/Model/InternalWorkbook.cs:2725-2741 | main/HSSF/Model/InternalWorkbook.cs:2765-2781 — 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 `main/HSSF/Model/InternalWorkbook.cs:2725` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) main/SS/Formula/CellCacheEntry.cs:60— main/SS/Formula/CellCacheEntry.cs:60-76 | main/SS/Formula/EvaluationCache.cs:198-214 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/CellCacheEntry.cs:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) main/SS/Formula/Eval/RelationalOperationEval/RelationalOperationEval.cs:142— main/SS/Formula/Eval/RelationalOperationEval/RelationalOperationEval.cs:142-158 | main/SS/Formula/Eval/RelationalOperationEval/RelationalOperationEval.cs:162-178 — 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 `main/SS/Formula/Eval/RelationalOperationEval/RelationalOperationEval.cs:142` 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 (17 lines × 2) main/SS/Formula/Functions/ArrayFunction.cs:75— main/SS/Formula/Functions/ArrayFunction.cs:75-91 | main/SS/Formula/Functions/ArrayFunction.cs:97-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. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Functions/ArrayFunction.cs:75` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) main/SS/Formula/Functions/Dec2Bin.cs:94— main/SS/Formula/Functions/Dec2Bin.cs:94-110 | main/SS/Formula/Functions/Dec2Hex.cs:99-115 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Functions/Dec2Bin.cs:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) main/SS/Formula/Functions/DollarDe.cs:27— main/SS/Formula/Functions/DollarDe.cs:27-43 | main/SS/Formula/Functions/DollarFr.cs:21-37 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (11 lines × 2) main/HSSF/Record/Chart/AlRunsRecord.cs:87— main/HSSF/Record/Chart/AlRunsRecord.cs:87-97 | main/HSSF/Record/Chart/ChartTitleFormatRecord.cs:81-91 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/Chart/AlRunsRecord.cs:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) main/POIFS/Crypt/BinaryRC4/BinaryRC4Decryptor.cs:69— main/POIFS/Crypt/BinaryRC4/BinaryRC4Decryptor.cs:69-82 | main/POIFS/Crypt/CryptoAPI/CryptoAPIDecryptor.cs:110-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/POIFS/Crypt/BinaryRC4/BinaryRC4Decryptor.cs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) main/SS/Formula/Atp/MRound.cs:49— main/SS/Formula/Atp/MRound.cs:49-59 | main/SS/Formula/Atp/RandBetween.cs:59-69 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Atp/MRound.cs:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) main/SS/Formula/PTG/Area3DPxg.cs:81— main/SS/Formula/PTG/Area3DPxg.cs:81-91 | main/SS/Formula/PTG/Ref3DPxg.cs:82-92 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/PTG/Area3DPxg.cs:81` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) main/SS/Util/PropertyTemplate.cs:911— main/SS/Util/PropertyTemplate.cs:911-921 | main/SS/Util/PropertyTemplate.cs:948-958 — 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 `main/SS/Util/PropertyTemplate.cs:911` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) main/Util/Arrays.cs:198— main/Util/Arrays.cs:198-210 | main/Util/Arrays.cs:673-683 — 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 `main/Util/Arrays.cs:198` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) main/DDF/EscherBlipWMFRecord.cs:326— main/DDF/EscherBlipWMFRecord.cs:326-330 | main/DDF/EscherTextboxRecord.cs:202-206 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/DDF/EscherBlipWMFRecord.cs:326` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) main/DDF/EscherMetafileBlip.cs:357— main/DDF/EscherMetafileBlip.cs:357-361 | main/DDF/EscherPictBlip.cs:289-293 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/DDF/EscherMetafileBlip.cs:357` 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 (5 lines × 2) main/HSSF/Record/CellRecord.cs:117— main/HSSF/Record/CellRecord.cs:117-121 | main/HSSF/Record/OldCellRecord.cs:116-120 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (5 lines × 2) main/HSSF/UserModel/HSSFComment.cs:285— main/HSSF/UserModel/HSSFComment.cs:285-289 | main/HSSF/UserModel/HSSFTextbox.cs:132-136 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (5 lines × 2) main/SS/Formula/Atp/WorkdayCalculator.cs:42— main/SS/Formula/Atp/WorkdayCalculator.cs:42-46 | main/SS/Formula/Atp/WorkdayCalculator.cs:47-51 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) main/Util/LittleEndian.cs:541— main/Util/LittleEndian.cs:541-545 | main/Util/LittleEndian.cs:589-593 — 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 `main/Util/LittleEndian.cs:541` 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 (15 lines × 2) main/HSSF/Record/Aggregates/Chart/ChartSheetAggregate.cs:93— main/HSSF/Record/Aggregates/Chart/ChartSheetAggregate.cs:93-108 | main/HSSF/Record/Aggregates/ChartSubstreamRecordAggregate.cs:79-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/Aggregates/Chart/ChartSheetAggregate.cs:93` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) main/SS/Formula/Atp/XLookupFunction.cs:78— main/SS/Formula/Atp/XLookupFunction.cs:78-92 | main/SS/Formula/Atp/XMatchFunction.cs:53-67 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Atp/XLookupFunction.cs:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) main/SS/Formula/Functions/LinearRegressionFunction.cs:142— main/SS/Formula/Functions/LinearRegressionFunction.cs:142-156 | main/SS/Formula/Functions/XYNumericFunction.cs:144-158 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Functions/LinearRegressionFunction.cs:142` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) main/SS/Formula/Functions/LookupUtils.cs:467— main/SS/Formula/Functions/LookupUtils.cs:467-481 | main/SS/Formula/Functions/LookupUtils.cs:526-545 — 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 `main/SS/Formula/Functions/LookupUtils.cs:467` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) main/Util/BigInteger.cs:3311— main/Util/BigInteger.cs:3311-3326 | main/Util/BigInteger.cs:3331-3345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) main/POIFS/FileSystem/POIFSDocumentReader.cs:275— main/POIFS/FileSystem/POIFSDocumentReader.cs:275-287 | main/Util/ByteArrayInputStream.cs:142-154 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (13 lines × 2) main/SS/Formula/Atp/XLookupFunction.cs:60— main/SS/Formula/Atp/XLookupFunction.cs:60-72 | main/SS/Formula/Atp/XMatchFunction.cs:35-47 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Atp/XLookupFunction.cs:60` 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 (13 lines × 2) main/SS/Formula/Functions/Mode.cs:54— main/SS/Formula/Functions/Mode.cs:54-66 | main/SS/Formula/Functions/StatsLib.cs:118-130 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Functions/Mode.cs:54` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) main/SS/UserModel/TableStyleType.cs:139— main/SS/UserModel/TableStyleType.cs:139-151 | main/SS/UserModel/TableStyleType.cs:165-177 — 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 `main/SS/UserModel/TableStyleType.cs:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (13 lines × 2) main/SS/UserModel/TableStyleType.cs:191— main/SS/UserModel/TableStyleType.cs:191-203 | main/SS/UserModel/TableStyleType.cs:219-233 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/UserModel/TableStyleType.cs:191` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) main/HSSF/Record/Aggregates/Chart/AttachedLabelAggregate.cs:91— main/HSSF/Record/Aggregates/Chart/AttachedLabelAggregate.cs:91-102 | main/HSSF/Record/Aggregates/Chart/LDAggregate.cs:50-61 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/Aggregates/Chart/AttachedLabelAggregate.cs:91` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) main/SS/Formula/Functions/Npv.cs:30— main/SS/Formula/Functions/Npv.cs:30-41 | main/SS/Formula/Functions/Numeric/NumericFunction.cs:66-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Functions/Npv.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) main/SS/Util/ImageUtils.cs:250— main/SS/Util/ImageUtils.cs:250-261 | main/SS/Util/ImageUtils.cs:286-298 — 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 `main/SS/Util/ImageUtils.cs:250` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) main/SS/Util/PropertyTemplate.cs:367— main/SS/Util/PropertyTemplate.cs:367-378 | main/SS/Util/PropertyTemplate.cs:416-427 — 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 `main/SS/Util/PropertyTemplate.cs:367` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) main/SS/Util/PropertyTemplate.cs:743— main/SS/Util/PropertyTemplate.cs:743-754 | main/SS/Util/PropertyTemplate.cs:793-804 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Util/PropertyTemplate.cs:743` 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 (20 lines × 2) main/HSSF/Model/InternalChart.cs:190— main/HSSF/Model/InternalChart.cs:190-209 | main/HSSF/Record/Aggregates/PageSettingsBlock.cs:408-427 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:190` 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 (20 lines × 2) main/HSSF/UserModel/HSSFOptimiser.cs:96— main/HSSF/UserModel/HSSFOptimiser.cs:96-116 | main/HSSF/UserModel/HSSFOptimiser.cs:308-327 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/UserModel/HSSFOptimiser.cs:96` 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 (20 lines × 2) main/SS/Formula/Functions/ArrayFunction.cs:127— main/SS/Formula/Functions/ArrayFunction.cs:127-146 | main/SS/Formula/Functions/ArrayFunction.cs:151-170 — 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 `main/SS/Formula/Functions/ArrayFunction.cs:127` 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 (20 lines × 2) main/SS/Formula/Functions/Count.cs:53— main/SS/Formula/Functions/Count.cs:53-72 | main/SS/Formula/Functions/Counta.cs:49-71 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
BarePragmaDisable OpenXmlFormats/Wordprocessing/Markup.cs:726— #pragma warning disable format — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable OpenXmlFormats/Wordprocessing/Paragraph.cs:614— #pragma warning disable format — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable OpenXmlFormats/Wordprocessing/Run.cs:298— #pragma warning disable format — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
Duplicated block (18 lines × 2) main/HSSF/Record/BlankRecord.cs:155— main/HSSF/Record/BlankRecord.cs:155-172 | main/HSSF/Record/CellRecord.cs:95-112 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/BlankRecord.cs:155` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) main/SS/Formula/Functions/Complex.cs:52— main/SS/Formula/Functions/Complex.cs:52-69 | main/SS/Formula/Functions/Complex.cs:71-88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) main/SS/Formula/Functions/Dec2Bin.cs:67— main/SS/Formula/Functions/Dec2Bin.cs:67-84 | main/SS/Formula/Functions/Dec2Hex.cs:72-89 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Functions/Dec2Bin.cs:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) main/HSSF/Model/InternalChart.cs:219— main/HSSF/Model/InternalChart.cs:219-234 | main/HSSF/Record/Aggregates/PageSettingsBlock.cs:437-452 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Model/InternalChart.cs:219` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) main/HSSF/Model/RecordOrderer.cs:160— main/HSSF/Model/RecordOrderer.cs:160-175 | main/HSSF/Model/RecordOrderer.cs:382-397 — 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 `main/HSSF/Model/RecordOrderer.cs:160` 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 (16 lines × 2) main/SS/Formula/Eval/PercentEval.cs:34— main/SS/Formula/Eval/PercentEval.cs:34-49 | main/SS/Formula/Eval/UnaryMinusEval.cs:37-52 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Eval/PercentEval.cs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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.
CT_ShapeProperties.Parse (cyclomatic 19) OpenXmlFormats/Drawing/ShapeProperties.cs:2086— CT_ShapeProperties.Parse has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_ShapeProperties.Parse (cyclomatic 19) OpenXmlFormats/Drawing/SpreadsheetDrawing.cs:887— CT_ShapeProperties.Parse has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_ShapeProperties.Write (cyclomatic 17) OpenXmlFormats/Drawing/ShapeProperties.cs:2131— CT_ShapeProperties.Write has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_ShapeProperties.Write (cyclomatic 17) OpenXmlFormats/Drawing/SpreadsheetDrawing.cs:932— CT_ShapeProperties.Write has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_ShapeProperties.Parse (cognitive 19) OpenXmlFormats/Drawing/ShapeProperties.cs:2086— CT_ShapeProperties.Parse has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_ShapeProperties.Parse (cognitive 19) OpenXmlFormats/Drawing/SpreadsheetDrawing.cs:887— CT_ShapeProperties.Parse has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_ShapeProperties.Write (cognitive 16) OpenXmlFormats/Drawing/ShapeProperties.cs:2131— CT_ShapeProperties.Write has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_ShapeProperties.Write (cognitive 16) OpenXmlFormats/Drawing/SpreadsheetDrawing.cs:932— CT_ShapeProperties.Write has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Duplicated block (26 lines × 2) main/SS/Formula/FormulaShifter.cs:597— main/SS/Formula/FormulaShifter.cs:597-622 | main/SS/Formula/FormulaShifter.cs:634-659 — 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 `main/SS/Formula/FormulaShifter.cs:597` 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 (26 lines × 2) main/SS/Formula/FormulaShifter.cs:783— main/SS/Formula/FormulaShifter.cs:783-808 | main/SS/Formula/FormulaShifter.cs:949-974 — 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 `main/SS/Formula/FormulaShifter.cs:783` 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 (21 lines × 2) main/SS/Formula/Functions/LinearRegressionFunction.cs:173— main/SS/Formula/Functions/LinearRegressionFunction.cs:173-193 | main/SS/Formula/Functions/XYNumericFunction.cs:180-200 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/SS/Formula/Functions/LinearRegressionFunction.cs:173` 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 (21 lines × 2) main/SS/Formula/Functions/LookupUtils.cs:709— main/SS/Formula/Functions/LookupUtils.cs:709-729 | main/SS/Formula/Functions/LookupUtils.cs:777-797 — 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 `main/SS/Formula/Functions/LookupUtils.cs:709` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) main/SS/Formula/FormulaParser.cs:745— main/SS/Formula/FormulaParser.cs:745-763 | main/SS/Formula/FormulaParser.cs:830-848 — 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 `main/SS/Formula/FormulaParser.cs:745` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) main/SS/Formula/Functions/Matrix/MatrixFunction.cs:184— main/SS/Formula/Functions/Matrix/MatrixFunction.cs:184-202 | main/SS/Formula/Functions/Matrix/MatrixFunction.cs:209-227 — 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 `main/SS/Formula/Functions/Matrix/MatrixFunction.cs:184` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) main/HSSF/Record/Aggregates/CFRecordsAggregate.cs:338— main/HSSF/Record/Aggregates/CFRecordsAggregate.cs:338-351 | main/SS/UserModel/Helpers/BaseRowColShifter.cs:55-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 (14 lines × 2) main/SS/Formula/Functions/NormInv.cs:29— main/SS/Formula/Functions/NormInv.cs:29-42 | main/SS/Formula/Functions/Standardize.cs:20-33 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) main/HSSF/Record/Cont/ContinuableRecordInput.cs:107— main/HSSF/Record/Cont/ContinuableRecordInput.cs:107-115 | main/POIFS/Storage/DataInputBlock.cs:141-149 | main/Util/LittleEndianByteArrayInputStream.cs:126-134 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `main/HSSF/Record/Cont/ContinuableRecordInput.cs:107` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) main/HSSF/UserModel/HSSFChart.cs:517— main/HSSF/UserModel/HSSFChart.cs:517-525 | main/HSSF/UserModel/HSSFChart.cs:717-725 | main/HSSF/UserModel/HSSFChart.cs:854-862 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
CT_Settings.Write (cyclomatic 102) OpenXmlFormats/Wordprocessing/Settings.cs:234— CT_Settings.Write has cyclomatic complexity 102 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_Settings.Parse (cyclomatic 100) OpenXmlFormats/Wordprocessing/Settings.cs:19— CT_Settings.Parse has cyclomatic complexity 100 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_ParaRPrOriginal.Write (cyclomatic 83) OpenXmlFormats/Wordprocessing/Paragraph.cs:5643— CT_ParaRPrOriginal.Write has cyclomatic complexity 83 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CT_RPrOriginal.Write (cyclomatic 79) OpenXmlFormats/Wordprocessing/Paragraph.cs:7424— CT_RPrOriginal.Write has cyclomatic complexity 79 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CT_PivotTableDefinition.Parse (cyclomatic 77) OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotTableDefinition.cs:18— CT_PivotTableDefinition.Parse has cyclomatic complexity 77 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_Compat.Parse (cyclomatic 68) OpenXmlFormats/Wordprocessing/Settings.cs:4891— CT_Compat.Parse has cyclomatic complexity 68 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_Compat.Write (cyclomatic 66) OpenXmlFormats/Wordprocessing/Settings.cs:5034— CT_Compat.Write has cyclomatic complexity 66 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EscherDump.DumpOld (cyclomatic 65) main/DDF/EscherDump.cs:67— EscherDump.DumpOld has cyclomatic complexity 65 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FormulaParser.ParseStructuredReference (cyclomatic 61) main/SS/Formula/FormulaParser.cs:701— FormulaParser.ParseStructuredReference has cyclomatic complexity 61 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CT_R.Write (cyclomatic 61) OpenXmlFormats/Wordprocessing/Run.cs:724— CT_R.Write has cyclomatic complexity 61 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SharedStringsTable.ReadFromStreamViaXmlReader (cyclomatic 57) ooxml/XSSF/Model/SharedStringsTable.cs:249— SharedStringsTable.ReadFromStreamViaXmlReader has cyclomatic complexity 57 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CT_P.Write (cyclomatic 56) OpenXmlFormats/Wordprocessing/Paragraph.cs:289— CT_P.Write has cyclomatic complexity 56 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_Body.Write (cyclomatic 53) OpenXmlFormats/Wordprocessing/Document.cs:365— CT_Body.Write has cyclomatic complexity 53 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_FtnEdn.Write (cyclomatic 52) OpenXmlFormats/Wordprocessing/HdrFtr.cs:1047— CT_FtnEdn.Write has cyclomatic complexity 52 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_RunTrackChange.Parse (cyclomatic 52) OpenXmlFormats/Wordprocessing/Run.cs:2079— CT_RunTrackChange.Parse has cyclomatic complexity 52 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_PivotField.Parse (cyclomatic 51) OpenXmlFormats/Spreadsheet/PivotTable/CT_PivotTableDefinition.cs:2139— CT_PivotField.Parse has cyclomatic complexity 51 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_RunTrackChange.Write (cyclomatic 51) OpenXmlFormats/Wordprocessing/Run.cs:2335— CT_RunTrackChange.Write has cyclomatic complexity 51 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OperatorEnumHelper.IsValid (cyclomatic 50) main/SS/Formula/EvaluationConditionalFormatRule.cs:26— OperatorEnumHelper.IsValid has cyclomatic complexity 50 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CT_Tbl.Parse (cyclomatic 49) OpenXmlFormats/Wordprocessing/Table.cs:43— CT_Tbl.Parse has cyclomatic complexity 49 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_Tbl.Write (cyclomatic 49) OpenXmlFormats/Wordprocessing/Table.cs:279— CT_Tbl.Write has cyclomatic complexity 49 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EvaluationConditionalFormatRule.CheckFilter (cyclomatic 48) main/SS/Formula/EvaluationConditionalFormatRule.cs:550— EvaluationConditionalFormatRule.CheckFilter has cyclomatic complexity 48 (threshold 15). Of this number, 30 points are the body's own statements and 18 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CT_ParaRPr.Parse (cyclomatic 47) OpenXmlFormats/Wordprocessing/Paragraph.cs:1924— CT_ParaRPr.Parse has cyclomatic complexity 47 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_RubyContent.Write (cyclomatic 47) OpenXmlFormats/Wordprocessing/Run.cs:1351— CT_RubyContent.Write has cyclomatic complexity 47 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_ParaRPrOriginal.Parse (cyclomatic 46) OpenXmlFormats/Wordprocessing/Paragraph.cs:5505— CT_ParaRPrOriginal.Parse has cyclomatic complexity 46 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_ParaRPr.Write (cyclomatic 45) OpenXmlFormats/Wordprocessing/Paragraph.cs:2025— CT_ParaRPr.Write has cyclomatic complexity 45 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_RPr.Parse (cyclomatic 43) OpenXmlFormats/Wordprocessing/Paragraph.cs:4065— CT_RPr.Parse has cyclomatic complexity 43 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_Worksheet.Parse (cyclomatic 42) OpenXmlFormats/Spreadsheet/Sheet/CT_Worksheet.cs:95— CT_Worksheet.Parse has cyclomatic complexity 42 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_Worksheet.Write (cyclomatic 42) OpenXmlFormats/Spreadsheet/Sheet/CT_Worksheet.cs:193— CT_Worksheet.Write has cyclomatic complexity 42 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_RPrOriginal.Parse (cyclomatic 42) OpenXmlFormats/Wordprocessing/Paragraph.cs:7294— CT_RPrOriginal.Parse has cyclomatic complexity 42 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ChartRecordAggregate.WriteStartBlock (cyclomatic 41) main/HSSF/Record/Aggregates/Chart/ChartRecordAggregate.cs:104— ChartRecordAggregate.WriteStartBlock has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WorkbookEvaluator.EvaluateFormula (cyclomatic 41) main/SS/Formula/WorkbookEvaluator.cs:572— WorkbookEvaluator.EvaluateFormula has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CT_RPr.Write (cyclomatic 41) OpenXmlFormats/Wordprocessing/Paragraph.cs:4158— CT_RPr.Write has cyclomatic complexity 41 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
InternalSheet.InternalSheet.ctor (cyclomatic 40) main/HSSF/Model/InternalSheet.cs:206— InternalSheet.InternalSheet.ctor has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CT_PPr.Parse (cyclomatic 40) OpenXmlFormats/Wordprocessing/Paragraph.cs:981— CT_PPr.Parse has cyclomatic complexity 40 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_PPr.Write (cyclomatic 39) OpenXmlFormats/Wordprocessing/Paragraph.cs:1072— CT_PPr.Write has cyclomatic complexity 39 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_R.Parse (cyclomatic 39) OpenXmlFormats/Wordprocessing/Run.cs:531— CT_R.Parse has cyclomatic complexity 39 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_P.Parse (cyclomatic 38) OpenXmlFormats/Wordprocessing/Paragraph.cs:62— CT_P.Parse has cyclomatic complexity 38 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HSSFOptimiser.OptimiseCellStyles (cyclomatic 37) main/HSSF/UserModel/HSSFOptimiser.cs:195— HSSFOptimiser.OptimiseCellStyles has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Value.ConvertTextToNumber (cyclomatic 37) main/SS/Formula/Functions/Value.cs:59— Value.ConvertTextToNumber has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CT_PPrBase.Parse (cyclomatic 37) OpenXmlFormats/Wordprocessing/Paragraph.cs:6236— CT_PPrBase.Parse has cyclomatic complexity 37 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
VariantSupport.Write (cyclomatic 36) main/HPSF/VariantSupport.cs:266— VariantSupport.Write has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CT_SmartTagRun.Parse (cyclomatic 36) OpenXmlFormats/Wordprocessing/CustomXml.cs:1304— CT_SmartTagRun.Parse has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_SmartTagRun.Write (cyclomatic 36) OpenXmlFormats/Wordprocessing/CustomXml.cs:1482— CT_SmartTagRun.Write has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_PPrBase.Write (cyclomatic 36) OpenXmlFormats/Wordprocessing/Paragraph.cs:6321— CT_PPrBase.Write has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_SdtPr.Write (cyclomatic 36) OpenXmlFormats/Wordprocessing/Sdt.cs:1948— CT_SdtPr.Write has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_Row.Parse (cyclomatic 36) OpenXmlFormats/Wordprocessing/Table.cs:5555— CT_Row.Parse has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_CustomXmlRun.Parse (cyclomatic 35) OpenXmlFormats/Wordprocessing/CustomXml.cs:823— CT_CustomXmlRun.Parse has cyclomatic complexity 35 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_SdtContentRun.Parse (cyclomatic 35) OpenXmlFormats/Wordprocessing/Sdt.cs:2246— CT_SdtContentRun.Parse has cyclomatic complexity 35 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_Tc.Parse (cyclomatic 35) OpenXmlFormats/Wordprocessing/Table.cs:3384— CT_Tc.Parse has cyclomatic complexity 35 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DataFormatter.CreateDateFormat (cyclomatic 34) main/SS/UserModel/DataFormatter.cs:555— DataFormatter.CreateDateFormat has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CT_Shapetype.Write (cyclomatic 34) OpenXmlFormats/Vml/Main.cs:3842— CT_Shapetype.Write has cyclomatic complexity 34 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CT_CustomXmlRun.Write (cyclomatic 34) OpenXmlFormats/Wordprocessing/CustomXml.cs:997— CT_CustomXmlRun.Write has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_Body.Parse (cyclomatic 34) OpenXmlFormats/Wordprocessing/Document.cs:195— CT_Body.Parse has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_FtnEdn.Parse (cyclomatic 34) OpenXmlFormats/Wordprocessing/HdrFtr.cs:882— CT_FtnEdn.Parse has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CT_SdtContentRun.Write (cyclomatic 34) OpenXmlFormats/Wordprocessing/Sdt.cs:2417— CT_SdtContentRun.Write has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
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.