Public report of nanami5270/GARbro-Mod, published 17 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 17 November 2026, 18:40 UTC · Survey ID cd_dbac5e92398f460b9d667e9e5539fd29

nanami5270/GARbro-Mod

Measured 17 November 2026, 18:39 UTC, at code version 009c09d

Boundary Type-Coupling is not measured: Bounded contexts not declared.

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 35.3out of 100 Provisional

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 239,004 lines of product code in 9 projects, tests not counted · Estimated rebuild effort: about 3.6 person-years · Weakest lens: Security and Compliance, 27.4

Findings by how serious they are

106 critical 2162 serious 1187 minor

4 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 18:39 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The code didn't build, so the score is provisional
We couldn't build the code: the build stopped with 14 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS0246: The type or namespace name 'NAudio' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Newtonsoft' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'WaveStream' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'WaveFormatEncoding' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'DefaultContractResolver' could not be found (are you missing a using directive or an assembly reference?)

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

58of 58 dimensions measured by tools.
3441of 3455 findings point to an exact file and line, so you can open each one in the code. The other 14 concern the repository as a whole, such as missing documentation.
58dimensions across 6 lenses, read from 239,004 lines of product code in 9 projects.
Chapters

Executive summary

nanami5270/GARbro-Mod has a provisional result, because the code didn't build. Its score is held back in part because it has encryption keys written into the code. It scores 35.3 out of 100, and the ratings may change once the code builds. 20 of its 106 critical findings are security problems.

Security and Compliance, at 27.4, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the seven passwords or keys found in the code's history, worth about 4.2 points. Adding security headers and fixing weak cryptography comes next, worth about 7.6 points. Raising Security and Compliance to 70 would lift the score to about 42.7.

Eight passwords or keys are open to anyone who can read the repository. Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and forty-nine errors are caught and ignored, so failures can go unnoticed. Replacing each exposed password or key, pinning each tool to an exact version and handling or logging the ignored errors would close these risks. Loading the key from a secret store instead of the code would fix the three encryption keys written into the code, and fixing the weaknesses the scanner points to would deal with the three security weaknesses in the code. The 23 data fields that are written but never read need removing.

The product code is 239,004 lines, about €520,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Security and Compliance 27.4 · counts for 46%Production Readiness 34.0 · counts for 25%Maturity 44.3 · counts for 14%Code Health 46.4 · counts for 8%Performance 60.0 · counts for 4%Architecture 69.3 · counts for 2%

If Security and Compliance rose from 27.4 to 70, the lowest score rated Strong, the score would rise from 35.3 to about 42.7.

Code composition: what the lines of code are
Business logic 56%Supporting code 42%Generated by tools 2%
Rebuild cost: about €520,000 · Estimate
Cost to rebuild€170,000 to €870,000, for 2,820 to 9,210 hours of work, about 3.6 person-years for 2 to 7 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 35. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 239,004 lines of product code
Comment linesThe estimate prices 204,955 lines. Comment lines count towards the size of 239,004 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (6), REDACTED.
Raises the score by about 4.2 points · Low effort · Secrets (history)
2
Drop SSL 2.0/3.0 and TLS 1.0/1.1 from the enabled protocol list — prefer leaving it to the OS default (`SystemDefault`) so new versions are picked up automatically, or name `Tls12`/`Tls13` explicitly if it must be pinned.
Raises the score by about 7.6 points · Medium effort · Cryptographic Hygiene
3
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 2.3 points · Low effort · Static Analysis (SAST)

Diagnosis: what the measurements show together

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

If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS0246: The type or namespace name 'NAudio' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Newtonsoft' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'WaveStream' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'WaveFormatEncoding' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'DefaultContractResolver' could not be found (are you missing a using directive or an assembly reference?)
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €520,000 to build again, about 3.6 person-years of work. Its weakest lens is Security and Compliance, at 27.4 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 8% on every change. The history of the code shows how much it changes: about 10,738 lines over the last 90 days, which is about 43,549 lines a year. At that pace, the extra work comes to an estimated 3.9 to 23.6 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch ArcFormats ArcFormats GameRes GameRes ArcFormats->GameRes Net20 Net20 ArcFormats->Net20 Experimental Experimental Experimental->ArcFormats Experimental->GameRes GARbro.Console Console GARbro.Console->GameRes GARbro.GUI GUI GARbro.GUI->GameRes Image.Convert Convert Image.Convert->GameRes Legacy Legacy Legacy->ArcFormats Legacy->GameRes SchemeTool SchemeTool SchemeTool->ArcFormats SchemeTool->GameRes SchemeTool->Legacy

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

469 modules, with 562 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 429 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 GameRes2 GameRes.Cryptography3 GameRes.Utility4 SevenZip.Compression.LZMA5 GARbro.GUI6 GameRes.Formats7 GameRes.Formats.Artifact8 GameRes.Formats.Cmvs9 GameRes.Formats.KiriKiri10 GameRes.Compression11 GameRes.Formats.Abogado12 GameRes.Formats.AdvSys13 GameRes.Formats.AliceSoft14 GameRes.Formats.Ark15 GameRes.Formats.Artemis16 GameRes.Formats.BGI17 GameRes.Formats.Bishop18 GameRes.Formats.Brownie19 GameRes.Formats.Bruns20 GameRes.Formats.C421 GameRes.Formats.CaramelBox22 GameRes.Formats.CatSystem23 GameRes.Formats.Circus24 GameRes.Formats.DigitalWorks25 GameRes.Formats.Entis26 GameRes.Formats.FVP27 GameRes.Formats.Kaguya28 GameRes.Formats.Musica29 GameRes.Formats.NScripter30 GameRes.Formats.PkWare31 GameRes.Formats.Aaru32 GameRes.Formats.Ads33 GameRes.Formats.AirNovel34 GameRes.Formats.FC0135 GameRes.Formats.GUI36 GameRes.Formats.HuneX37 GameRes.Formats.Maika38 GameRes.Formats.Melody39 GameRes.Formats.PalmTree40 GameRes.Formats.BellDa
1 GameRes
2 GameRes.Cryptography
3 GameRes.Utility
4 SevenZip.Compression.LZMA
5 GARbro.GUI29
6 GameRes.Formats80
7 GameRes.Formats.Artifact4
8 GameRes.Formats.Cmvs1
9 GameRes.Formats.KiriKiri41
10 GameRes.Compression13
11 GameRes.Formats.Abogado201
12 GameRes.Formats.AdvSys221
13 GameRes.Formats.AliceSoft422
14 GameRes.Formats.Ark61
15 GameRes.Formats.Artemis251
16 GameRes.Formats.BGI222
17 GameRes.Formats.Bishop231
18 GameRes.Formats.Brownie151
19 GameRes.Formats.Bruns61
20 GameRes.Formats.C4131
21 GameRes.Formats.CaramelBox163
22 GameRes.Formats.CatSystem6511
23 GameRes.Formats.Circus402
24 GameRes.Formats.DigitalWorks301
25 GameRes.Formats.Entis4413
26 GameRes.Formats.FVP281
27 GameRes.Formats.Kaguya16012
28 GameRes.Formats.Musica5612
29 GameRes.Formats.NScripter3311
30 GameRes.Formats.PkWare141
31 GameRes.Formats.Aaru182
32 GameRes.Formats.Ads111
33 GameRes.Formats.AirNovel102
34 GameRes.Formats.FC017512
35 GameRes.Formats.GUI131
36 GameRes.Formats.HuneX2421
37 GameRes.Formats.Maika2012
38 GameRes.Formats.Melody511
39 GameRes.Formats.PalmTree311
40 GameRes.Formats.BellDa911
Uses a module listed above itPart of a loopThe module itself
1 GameRes2 GameRes.Cryptography3 GameRes.Utility4 SevenZip.Compression.LZMA5 GARbro.GUI6 GameRes.Formats7 GameRes.Formats.Artifact8 GameRes.Formats.Cmvs9 GameRes.Formats.KiriKiri10 GameRes.Compression11 GameRes.Formats.Abogado12 GameRes.Formats.AdvSys13 GameRes.Formats.AliceSoft14 GameRes.Formats.Ark15 GameRes.Formats.Artemis16 GameRes.Formats.BGI17 GameRes.Formats.Bishop18 GameRes.Formats.Brownie19 GameRes.Formats.Bruns20 GameRes.Formats.C421 GameRes.Formats.CaramelBox22 GameRes.Formats.CatSystem23 GameRes.Formats.Circus24 GameRes.Formats.DigitalWorks25 GameRes.Formats.Entis26 GameRes.Formats.FVP27 GameRes.Formats.Kaguya28 GameRes.Formats.Musica29 GameRes.Formats.NScripter30 GameRes.Formats.PkWare31 GameRes.Formats.Aaru32 GameRes.Formats.Ads33 GameRes.Formats.AirNovel34 GameRes.Formats.FC0135 GameRes.Formats.GUI36 GameRes.Formats.HuneX37 GameRes.Formats.Maika38 GameRes.Formats.Melody39 GameRes.Formats.PalmTree40 GameRes.Formats.BellDaGameRes1GameRes.Cryptography2GameRes.Utility3SevenZip.Compression.LZMA4GARbro.GUI5GameRes.Formats6GameRes.Formats.Artifact7GameRes.Formats.Cmvs8GameRes.Formats.KiriKiri9GameRes.Compression10GameRes.Formats.Abogado11GameRes.Formats.AdvSys12GameRes.Formats.AliceSoft13GameRes.Formats.Ark14GameRes.Formats.Artemis15GameRes.Formats.BGI16GameRes.Formats.Bishop17GameRes.Formats.Brownie18GameRes.Formats.Bruns19GameRes.Formats.C420GameRes.Formats.CaramelBox21GameRes.Formats.CatSystem22GameRes.Formats.Circus23GameRes.Formats.DigitalWorks24GameRes.Formats.Entis25GameRes.Formats.FVP26GameRes.Formats.Kaguya27GameRes.Formats.Musica28GameRes.Formats.NScripter29GameRes.Formats.PkWare30GameRes.Formats.Aaru31GameRes.Formats.Ads32GameRes.Formats.AirNovel33GameRes.Formats.FC0134GameRes.Formats.GUI35GameRes.Formats.HuneX36GameRes.Formats.Maika37GameRes.Formats.Melody38GameRes.Formats.PalmTree39GameRes.Formats.BellDa4029804141132012214226125122223115161131163651140230144132811601256123311141182111102751213124212012511311911+429 more modules (most-connected shown)

At a glance — Code Health · 46.4 · Weak · gated by D18, X1 ·

At a glance — Architecture · 69.3 · Adequate · gated by AX2 ·

At a glance — Maturity · 44.3 · Weak · gated by D34, M2 ·

At a glance — Readiness · 34.0 · Weak · gated by D8, P3 ·

At a glance — Security · 27.4 · Weak · gated by D28, S1 ·

At a glance — Performance · 60.0 · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection11High / Critical
A07:2025 — Authentication Failures9High / Critical
A03:2025 — Software Supply Chain Failures2High / Critical
A01:2025 — Broken Access Control1Medium

Roadmap

Top priorities: Drop SSL 2.0/3.0 and TLS 1.0/1.1 from the enabled protocol list — prefer leaving it to the OS default (`SystemDefault`) so new versions are picked up automatically, or name `Tls12`/`Tls13` explicitly if it must be pinned; Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (6), REDACTED.

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

Do thisHelpsEffortDimension
Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (6), REDACTED.+4.2 ptsLowSecrets (history)
Drop SSL 2.0/3.0 and TLS 1.0/1.1 from the enabled protocol list — prefer leaving it to the OS default (`SystemDefault`) so new versions are picked up automatically, or name `Tls12`/`Tls13` explicitly if it must be pinned.+7.6 ptsMediumCryptographic Hygiene
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED.+2.3 ptsLowStatic Analysis (SAST)
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with GARbro.Console.csproj.+1.7 ptsLowADR Quality
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED.+1.7 ptsLowStatic Analysis (SAST)
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+3.4 ptsMediumSecurity & performance tooling
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED.+1.7 ptsLowSecrets (history)
Resolve the 2 FileScopedPragmaDisable finding(s) in Explicit Debt — start with HxCrypt.cs, FileErrorDialog.xaml.cs.+1.3 ptsLowExplicit Debt

File quality

Per-file score 0–10 — a quality signature. Of 767 files carrying findings, judged against the Production bar: 2% slop · 58% mixed · 40% near-clean.

FileScoreBandWorst signal
ArcFormats/Entis/EriReader.cs1.0SlopExplicit Debt: WriteOnlyPrivateField
ArcFormats/Emote/ArcPSB.cs1.0SlopExplicit Debt: EmptyCatchBlock
ArcFormats/Gss/ArcARC.cs1.1SlopExplicit Debt: WriteOnlyPrivateField
ArcFormats/Qlie/ArcQLIE.cs2.0SlopExplicit Debt: EmptyCatchBlock
REDACTED2.0SlopStatic Analysis (SAST): High: REDACTED
ArcFormats/Macintosh/ImagePICT.cs2.1SlopExplicit Debt: WriteOnlyPrivateField
REDACTED2.9SlopExplicit Debt: EmptyCatchBlock
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
ArcFormats/Majiro/ImageRCT.cs3.2SlopExplicit Debt: EmptyCatchBlock
ArcFormats/KiriKiri/HxCrypt.cs3.4SlopExplicit Debt: EmptyCatchBlock
ArcFormats/Ankh/ArcGRP.cs3.4SlopExplicit Debt: EmptyCatchBlock
ArcFormats/Leaf/ArcPAK.cs3.6SlopExplicit Debt: EmptyCatchBlock
REDACTED4.0MixedExplicit Debt: WriteOnlyPrivateField
ArcFormats/AZSys/ArcAZSys.cs4.2MixedExplicit Debt: WriteOnlyPrivateField
REDACTED4.3MixedSecrets (history): REDACTED: REDACTED
ArcFormats/Suika/ArcSuika.cs4.3MixedExplicit Debt: EmptyCatchBlock
REDACTED4.5MixedSecrets (history): REDACTED: REDACTED
ArcFormats/KiriKiri/ArcXP3.cs4.6MixedExplicit Debt: EmptyCatchBlock
ArcFormats/rUGP/ImageRIP.cs4.6MixedExplicit Debt: WriteOnlyPrivateField
ArcFormats/WildBug/ImageWBM.cs4.6MixedExplicit Debt: EmptyCatchBlock

How the grades work

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

Critical — 106

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 2162

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 1187

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

Could not be resolved — 4

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 58 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 58 dimensions across the health lenses
D1D2D3D4D5D6D8D13D14D15D16D17D18D19D20D21D24D26D28D29D30D32D34D35D43D44AX10AX2AX3AX4AX5AX6GD1IC1M1M2M3P1P2P3P6PF3S1X1X12X13X15X16X18X19X20X25X26X27X28X29X3X30

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 3441 of 3455 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

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

Every finding is locatable in findings.md. Run 01a1eace-f4c3-7382-8a97-1c83f08d79f3.

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

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'ArcFormats/ArcFormats.csproj' with message: This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\System.ValueTuple.4.6.2\bui….
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (238,947 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a REDACTED / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan. 1 of 2 declared ecosystem(s) (nuget REDACTED) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
  • D32 Data Compliance (PII/GDPR) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `ArcFormats/DraftArc.cs`, `ArcFormats/DraftAudio.cs`, `ArcFormats/DraftImage.cs`, `ArcFormats/Primel/AudioWBC.cs`, `Experimental/Artemis/IPT.Scanner.Generated.cs`, … (+2 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AX2 Stateful singletons — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (GUI/AboutBox.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 220 further occurrence(s) are not listed individually; the score already reflects all 260.
  • P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 17 further occurrence(s) are not listed individually; the score already reflects all 57.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 15 further occurrence(s) are not listed individually; the score already reflects all 55.

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

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D13 REDACTED Scanning: REDACTED 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.4 / 10Adequate✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

174 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Xp3Opener.TryOpen at 66. A further 7 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 PsbReader.GetObject at 30 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: ArcFormats/Eushully/ImageGP.cs (GpFormat.ReadMetaData at 21), GameRes/ImageTGA.cs (TgaFormat.ReadMetaData at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

ArcOpener.TryOpen (cyclomatic 19) · ×2ArcFormats/MAI/ArcMAI.cs:55
DatOpener.TryOpen (cyclomatic 17) · ×2ArcFormats/Adobe/ArcAIR.cs:44
ArcOpener.TryOpen (cyclomatic 17) · ×2ArcFormats/AZSys/ArcAZSys.cs:82
Xp3Opener.TryOpen (cyclomatic 66)ArcFormats/KiriKiri/ArcXP3.cs:105
GdtReader.UnpackDouble (cyclomatic 57)ArcFormats/CsWare/ImageGDT.cs:141

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

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with Xp3Opener.TryOpen (cyclomatic 66). — Refactoring it lifts Cyclomatic Complexity from 6.4 to about 6.5/10.

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

D2 · Cognitive Complexity4.1 / 10Weak✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

564 method(s) exceeded the cognitive complexity threshold of 15; the worst was Xp3Opener.TryOpen at 184.

RleDecompressor.Unpack (cognitive 29) · ×2ArcFormats/uGOS/ArcDET.cs:141
Reader.Unpack (cognitive 24) · ×2ArcFormats/Majiro/ImageRC8.cs:108
CbgReader.ReverseAverageSampling (cognitive 23) · ×2ArcFormats/HuneX/ImageCBG.cs:216
Reader.Unpack (cognitive 23) · ×2ArcFormats/ActiveSoft/ImageEDT.cs:329
PakOpener.TryOpen (cognitive 19) · ×2ArcFormats/HCSystem/ArcPAK.cs:45

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

What to do

  1. Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with Xp3Opener.TryOpen (cognitive 184), Mai2Reader.UnpackPlane (cognitive 181), Pl4Reader.UnpackV1 (cognitive 135). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 4.1 to about 4.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.

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

D3 · God Classes9.3 / 10Stronggated by 56 serious findings✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

56 god class(es) detected.

FileTooLong: Giga/ArcALL.cs · ×21Legacy/Giga/ArcALL.cs
MethodTooLong: PcmDecoder.sub_411AB0 · ×20ArcFormats/Circus/AudioPCM.cs:266
ClassTooLong: AllOpener · ×10Legacy/Giga/ArcALL.cs
TooManyMethods: MainWindow · ×5GUI/MainWindow.xaml.cs

What to do

  1. Resolve the 21 FileTooLong finding(s) in God Classes — start with ArcALL.cs, EriReader.cs, Palettes.cs. — One of this dimension's main actionable groups (21 warning-level).
  2. Resolve the 20 MethodTooLong finding(s) in God Classes — start with ArcXP3.cs (2), ImagePT1.cs (2), MioDecoder.cs (2). — One of this dimension's main actionable groups (20 warning-level).
  3. Resolve the 10 ClassTooLong finding(s) in God Classes — start with ArcALL.cs, Palettes.cs, ArcYK.cs. — One of this dimension's main actionable groups (10 warning-level).

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

D4 · Code Duplication5.7 / 10Adequate✓ Tool-verified

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

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

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

537 duplicated block group(s) detected. 10.6 % of the production lines (25,423 of 238,947) are in a reported copy. A further 469 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (8 lines × 2) · ×47ArcFormats/Entis/EriReader.cs:2048
Duplicated block (7 lines × 2) · ×47ArcFormats/AdvSys/ImageGWD.cs:89
Duplicated block (5 lines × 2) · ×38ArcFormats/Ankh/ArcGRP.cs:296
Duplicated block (9 lines × 2) · ×35ArcFormats/Qlie/Encryption.cs:381
Duplicated block (6 lines × 2) · ×31ArcFormats/Cmvs/CpzHeader.cs:96

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

What to do

  1. Resolve the 47 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with MioDecoder.cs (2), REDACTED (2), ImageRIP.cs (2). — One of this dimension's main actionable groups (47 warning-level).
  2. Resolve the 47 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with REDACTED (4), REDACTED (3), AudioPCM.cs (3). — One of this dimension's main actionable groups (47 warning-level).
  3. Resolve the 38 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ArcZIP.cs (2), ArcEncrypted.cs (2), ArcGRP.cs. — One of this dimension's main actionable groups (38 warning-level).

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

D5 · Coupling9.1 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

9 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

Off the main sequence: GameResGameRes/GameRes.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with GameRes.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 3 serious findings✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

3 of 659 classes have LCOM4 above 3.

Low cohesion: CpzOpener (LCOM4 4) · ×3ArcFormats/Cmvs/ArcCPZ.cs:82

What to do

  1. Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with ArcCPZ.cs, ArcNEKO2.cs, REDACTED. — One of this dimension's main actionable groups (3 warning-level).

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

D8 · Code Coverage0.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

No automated tests — no test code was found in this repository.

No automated tests

What to do

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).

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

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

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 163 packages use a banned license. The depth of this set was not established for this repository: the graded packages are what this pass resolved, and no lockfile was read, so it is not certified to be the full transitive closure.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: ArcFormats/Succubus/ImageGH.cs (2×17=34); ArcFormats/GsPack/ImageGS.cs (2×16=32)

Hotspot: ArcFormats/Succubus/ImageGH.cs · ×2ArcFormats/Succubus/ImageGH.cs:199

What to do

  1. Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with ImageGH.cs, ImageGS.cs. — One of this dimension's main actionable groups (2 warning-level).

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

D16 · Bus Factor7.8 / 10Strong✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

99 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Legacy/Giga/ArcBBWAV.cs. Counted over 446 of the 1328 production source files in this repository: 109 are under the ~2,400-byte size floor this dimension measures over, and the remaining 773 have no attributable history left to measure.

Off-boarding risk: anonymized user #1 · ×4
Further sole-owners (lower concentration)

What to do

  1. Resolve the 4 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (4 recommendation-level).
  2. Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

D17 · Explicit Debt9.1 / 10Adequategated by 75 critical findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

238 deducted debt markers + unmeasured dead symbols across 238947 LoC in the .NET projects (0.4/KLoC) → score 9.1. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

EmptyCatchBlock · ×49ArcFormats/AZSys/ArcEncrypted.cs:215
WriteOnlyPrivateField · ×23ArcFormats/AZSys/ArcAZSys.cs:187
FileScopedPragmaDisable · ×2ArcFormats/KiriKiri/HxCrypt.cs:35
DeadLoopAccumulatorArcFormats/Ail/ArcAil.cs:111
CommentedOutCode · ×61ArcFormats/Cri/AudioADX.cs:203

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

What to do

  1. Resolve the 49 EmptyCatchBlock finding(s) in Explicit Debt — start with ImageRCT.cs (3), ArcGRP.cs (2), ArcPAC.cs (2). — One of this dimension's main actionable groups (49 issue-level).
  2. Resolve the 23 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ArcSWF.cs (3), ArcARC.cs (3), ArcAZSys.cs (2). — One of this dimension's main actionable groups (23 issue-level).
  3. Resolve the 2 FileScopedPragmaDisable finding(s) in Explicit Debt — start with HxCrypt.cs, FileErrorDialog.xaml.cs. — One of this dimension's main actionable groups (2 issue-level).

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

D18 · Solution Shape3.0 / 10Weak✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

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

9 projects, 1349 source files, 238947 hand-written lines of code (238947 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 4162 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 12 inter-project edges (build failed).

Build failed

What to do

  1. Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation Quality5.0 / 10Adequate✓ Tool-verified

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 2 documentation facets pass in full; short on: F2 example. 6 document(s) read across 10 unit(s).

Documentation: no build, run or usage example · ×3README.md:1

What to do

  1. Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).

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

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

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

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

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

No architecture decision records were found.

No ADRs foundConsole/GARbro.Console.csproj:8

What to do

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

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

D21 · Naming Consistency3.0 / 10Weak✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

3 naming inconsistencies among 43 declarations measured against a convention their peers follow.

`CreateINTWidget` spells `INT` where 23 names in the project spell it `Int`ArcFormats/CatSystem/CreateINTWidget.xaml.cs:8
`WidgetINT` spells `INT` where 23 names in the project spell it `Int`ArcFormats/CatSystem/WidgetINT.xaml.cs:43
`CoderPropID` spells `ID` where 20 names in the project spell it `Id`ArcFormats/Lzma/ICoder.cs:81

What to do

  1. Resolve the 1 `CreateINTWidget` spells `INT` where 23 names in the project spell it… finding(s) in Naming Consistency — start with CreateINTWidget.xaml.cs. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 `WidgetINT` spells `INT` where 23 names in the project spell it `Int` finding(s) in Naming Consistency — start with WidgetINT.xaml.cs. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 `CoderPropID` spells `ID` where 20 names in the project spell it `Id` finding(s) in Naming Consistency — start with ICoder.cs. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value4.8 4.6 / 10Weak✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 4.6 / 10 · rule-coverage 94% · ceiling Documented

46 of 888 judged comments only repeat the code they sit on (5.2 %). 147 comment(s) in another language or script were not judged.

redundant comment · ×39ArcFormats/DxLib/HuffmanDecoder.cs:108
doc comments repeat the names · ×4ArcFormats/AZSys/FastMersenneTwister.cs:179

What to do

  1. Resolve the 39 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (33), MioDecoder.cs (2), HuffmanDecoder.cs. — One of this dimension's main actionable groups (39 recommendation-level).

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

D26 · Project Cohesion5.6 / 10Adequate✓ Tool-verified

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

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

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

2 of 9 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×2ArcFormats/ArcFormats.csproj:1
Split ArcFormatsArcFormats/ArcFormats.csproj:1
Split LegacyLegacy/Legacy.csproj:1

What to do

  1. Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with ArcFormats.csproj, Legacy.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
  2. Resolve the 1 Split ArcFormats finding(s) in Project Cohesion — start with ArcFormats.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 Split Legacy finding(s) in Project Cohesion — start with Legacy.csproj. — One of this dimension's main actionable groups (1 recommendation-level).

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

D28 · Secrets (history)2.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
  2. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)4.6 / 10Weak✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

11 finding(s): 0 critical, 6 high, 5 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 8 file(s) — `ArcFormats/DraftArc.cs` (line 27), `ArcFormats/DraftAudio.cs` (line 24), `ArcFormats/DraftImage.cs` (line 26), `ArcFormats/Primel/AudioWBC.cs` (line 245, line 249, line 251, …), `Experimental/Artemis/IPT.Scanner.Generated.cs` (lines 33–713), … (+3 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 3 of those file(s) — `Experimental/Artemis/IPT.Scanner.Generated.cs`, `Experimental/Artemis/ShiftReduceParserCode.cs`, `Legacy/Mink/ImageMCP.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  3. No action in Static Analysis (SAST) — all 3 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (3 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities8.8 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget REDACTED), and the findings above are real and complete for them. nuget was not scanned (nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a REDACTED / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

REDACTED

What to do

  1. Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).

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

D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 7 file(s) — `ArcFormats/DraftArc.cs`, `ArcFormats/DraftAudio.cs`, `ArcFormats/DraftImage.cs`, `ArcFormats/Primel/AudioWBC.cs`, `Experimental/Artemis/IPT.Scanner.Generated.cs`, … (+2 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.

REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D34 · Knowledge Freshness1.2 / 10Critical✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

1068 of 1219 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Legacy/Giga/ArcALL.cs. Counted over 1219 of the 1328 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×1065GUI/MainWindow.xaml.cs:1
Most significant orphaned file · ×3Legacy/Giga/ArcALL.cs:1
Concentrated knowledge decay

What to do

  1. Resolve the 1065 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (38), REDACTED (22), ArcBIN.cs (15). — One of this dimension's main actionable groups (1065 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with ArcALL.cs, YkTables.cs, AudioHCA.cs. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Concentrated knowledge decay 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.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

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.

AX2 · Stateful singletons1.0 / 10Critical✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `InfoReader` is not registered, but `PgxFormat` creates it and keeps it in the static `InfoCache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_layer_map, m_last_info_dir; e.g. `m_layer_map` at line 179). — ArcFormats/Glib2/ImagePGX.cs:132
  • `FileSystemStack` is not registered, but `VFS` creates it and keeps it in the static `m_vfs`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (CurrentArchive, m_fs_stack, m_arc_name_stack, LastVisitedArc, LastVisitedPath; e.g. `CurrentArchive` at line 596). — GameRes/FileSystem.cs:553
  • `FormatCatalog` keeps one instance of itself in the static `m_instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (CurrentSchemeVersion, m_game_map; e.g. `CurrentSchemeVersion` at line 350). — REDACTED:42
  • `WebPCodec` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (loaded; e.g. `loaded` at line 61). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/WebPCodec.cs:34
  • `OggInput` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_conversionBuffer; e.g. `_conversionBuffer` at line 94). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/AudioOGG.cs:35
  • `DatOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 167). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Actgs/ArcDAT.cs:53
  • `IntOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 247). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/CatSystem/ArcINT.cs:112
  • `DataOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 70). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Cyberworks/ArcDATA.cs:54
  • `DatOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 385). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Cyberworks/ArcDAT.cs:178
  • `TinkAudio` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 59). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Cyberworks/AudioTINK.cs:41
  • `MedOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 111). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/DxLib/ArcMED.cs:92
  • `PakOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 198). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — REDACTED:65
  • `McgFormat` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 70). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/FC01/ImageMCG.cs:56
  • `Xp3Opener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KiriKiriScheme; e.g. `KiriKiriScheme` at line 786). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/KiriKiri/ArcXP3.cs:81
  • `GrpUnpacker` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (LastUsedMethod; e.g. `LastUsedMethod` at line 369). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Ankh/ArcGRP.cs:335
  • `LeafPackOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 220). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Leaf/ArcLEAF.cs:52
  • `AmOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DecryptTable; e.g. `DecryptTable` at line 92). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Leaf/ArcAM.cs:34
  • `Reader` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownFourCC; e.g. `KnownFourCC` at line 759). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Macromedia/DirectorFile.cs:704
  • `Ns2Opener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 50). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/NScripter/ArcNS2.cs:36
  • `NsaOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 89). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/NScripter/ArcNSA.cs:74
  • `YpfOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 135). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/YuRis/ArcYPF.cs:114
  • `MpxOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownSecrets; e.g. `KnownSecrets` at line 244). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Ikura/ArcDRS.cs:111
  • `AdsOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 61). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/BlackRainbow/ArcADS.cs:42
  • `CpzOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 103). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Cmvs/ArcCPZ.cs:82
  • `ArcAI5Opener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 67). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/elf/ArcAi5Win.cs:51
  • `PsbOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 146). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Emote/ArcPSB.cs:54
  • `MgpkOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 209). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/MangaGamer/ArcMGPK.cs:58
  • `NpkOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 102). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/NitroPlus/ArcNPK.cs:84
  • `NpaOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownSchemes; e.g. `KnownSchemes` at line 114). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/NitroPlus/ArcNPA.cs:100
  • `CmpOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (GameScheme; e.g. `GameScheme` at line 159). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/GameSystem/ArcCMP.cs:35
  • `DatOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DatScheme; e.g. `DatScheme` at line 271). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Littlewitch/ArcDAT.cs:70
  • `DatOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownSchemes; e.g. `KnownSchemes` at line 347). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Malie/ArcLIB.cs:131
  • `PackOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 102). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Qlie/ArcQLIE.cs:75
  • `SceneOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 243). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/RealLive/ArcSCENE.cs:62
  • `NoaOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 408). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — REDACTED:70
  • `RctFormat` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 85). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Majiro/ImageRCT.cs:62
  • `FjsysOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownPasswords; e.g. `KnownPasswords` at line 140). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/NSystem/ArcFJSYS.cs:48
  • `PbzOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownSchemes; e.g. `KnownSchemes` at line 75). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Cmvs/ArcPBZ.cs:61
  • `MblOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 171). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Marble/ArcMBL.cs:58
  • `FpkOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 72). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ArcFormats/Moonhir/ArcFPK.cs:58

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
  • A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

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

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation9.8 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IBinaryStream` declares 25 members: `Name`, `Signature`, `AsStream`, `CanSeek`, `Length`, `Position`, `Seek`, `Read`, `ReadByte`, `PeekByte`, `ReadInt8`, `ReadUInt8`, `ReadInt16`, `ReadUInt16`, `ReadInt24`, `ReadInt32`, `ReadUInt32`, `ReadInt64`, `ReadUInt64`, `ReadHeader`, `ReadCString`, `ReadCString`, `ReadCString`, `ReadCString`, `ReadBytes`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 25 declarations carry 22 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 22 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — GameRes/BinaryStream.cs:35

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code9.9 / 10Exemplary✓ Tool-verified

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. (×28) — ArcFormats/Ice/ScriptISD.cs:53, ArcFormats/Ps1/ImageTIM.cs:191, ArcFormats/Psp/ArcGim.cs:230, …

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs5.8 / 10Adequate✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `DecodeLossyV9` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Entis/EriReader.cs:653 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — ArcFormats/Entis/EriReader.cs:769
  • `UnpackW` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Gss/ArcARC.cs:94 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — ArcFormats/Gss/ArcARC.cs:436
  • `Unpack24bpp` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Ikura/ImageTAN.cs:111 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — ArcFormats/Ikura/ImageTAN.cs:165
  • `UnpackBlock_4_8` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Leaf/ImagePX.cs:282 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — ArcFormats/Leaf/ImagePX.cs:323
  • `UnpackRaw` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Sviu/AudioKPV.cs:87 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — ArcFormats/Sviu/AudioKPV.cs:95
  • `UnpackV10` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Sviu/AudioKPV.cs:90 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — ArcFormats/Sviu/AudioKPV.cs:134
  • `UnpackLzma` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Unity/ArcUnityFS.cs:88 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — ArcFormats/Unity/ArcUnityFS.cs:161
  • `GetRtcFromMessageName` is a shipped member whose body only throws — and it is REACHED: ArcFormats/rUGP/ArcRIO.cs:561 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — ArcFormats/rUGP/ArcRIO.cs:597
  • `FindObject` is a shipped member whose body only throws — and it is REACHED: ArcFormats/rUGP/ArcRIO.cs:454 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — ArcFormats/rUGP/ArcRIO.cs:607
  • `CreateAnonymousRio` is a shipped member whose body only throws — and it is REACHED: ArcFormats/rUGP/ArcRIO.cs:655 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — ArcFormats/rUGP/ArcRIO.cs:622
  • Control only reaches here when `0x04 != index.ReadUInt8()` is false, because the guard on line 76 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — ArcFormats/Adobe/ArcAIR.cs:79
  • The branch `if (null == bitmap)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — ArcFormats/BlackCyc/ImageDWQ.cs:189
  • The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. — ArcFormats/CaramelBox/ImageFCB.cs:118
  • `Image` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — ArcFormats/CatSystem/ImageHG3.cs:104
  • The branch `if (0 != (fOpTable & 0xC))` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — ArcFormats/Entis/EriReader.cs:764
  • Control only reaches here when `context.GetABit() != 0` is false, because the guard on line 311 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — ArcFormats/Entis/MioDecoder.cs:358
  • The branch `if (m_mioih.Architecture == EriCode.Nemesis)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. (×2) — ArcFormats/Entis/MioDecoder.cs:376, ArcFormats/Entis/MioDecoder.cs:673
  • Control only reaches here when `context.GetABit() != 0` is false, because the guard on line 604 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — ArcFormats/Entis/MioDecoder.cs:655
  • `Unpack` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:413
  • `OpenImage` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — ArcFormats/Gss/ArcARC.cs:139
  • `ConvertBack` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — ArcFormats/Ice/ScriptISD.cs:53
  • `Encrypt` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×4) — ArcFormats/KiriKiri/HxCrypt.cs:301, ArcFormats/KiriKiri/HxCryptLite.cs:104, ArcFormats/ShiinaRio/WarcEncryption.cs:1347, …
  • The branch `if (0 == block_count)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — ArcFormats/KiriKiri/ImageTLG.cs:1329
  • The branch `if (final_size != 0)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — ArcFormats/Lambda/ArcLAX.cs:140
  • The branch `if (meta.Shuffled)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — REDACTED:100
  • The branch `if (!info.IndependentBlocks)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — ArcFormats/Lz4Stream.cs:115
  • The branch `if (info.HasDictionary)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — ArcFormats/Lz4Stream.cs:117
  • The branch `if (mode != LzssMode.Decompress)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — ArcFormats/LzssStream.cs:118
  • Both arms of `info.DepthType == 0x87 // i have no clue what this is || info.DepthType == 0x8A ? … : …` are `PixelFormats.Bgra32`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — ArcFormats/Macromedia/ImageBITD.cs:73
  • `Write` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — ArcFormats/Ps1/ImageTIM.cs:191, ArcFormats/Psp/ArcGim.cs:230
  • Control only reaches here when `iterator.MoveNext()` is true, because the guard on line 335 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — ArcFormats/RenPy/ArcRPA.cs:338
  • The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. — ArcFormats/Seraphim/ImageSeraph.cs:347
  • The branch `if ((flags & 0x104) == 0x104)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. (×3) — ArcFormats/ShiinaRio/WarcEncryption.cs:959, ArcFormats/ShiinaRio/WarcEncryption.cs:1039, ArcFormats/ShiinaRio/WarcEncryption.cs:1139

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.
M1 · Documentation (README)7.1 / 10Strong✓ Tool-verified

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

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

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

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

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

P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

What to do

  • Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P2 · Observability7.8 / 10Strong✓ Tool-verified

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

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

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:2
  • `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:3

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

  • 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.
PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • 3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `complete.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — ArcFormats/Ethornell/ImageCBG.cs:309
  • `m_conversion_task.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — ArcFormats/Cri/AudioHCA.cs:164
  • `.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — ArcFormats/KiriKiri/ImageTLG.cs:1374

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Cryptographic Hygiene0.0 / 10Critical✓ Tool-verified

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. Outbound TLS (certificate validation, protocol version) is scored wherever it appears — a client verifies its peer whether or not it serves anything itself.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • `SecurityProtocol` explicitly selects `SecurityProtocolType.Tls11`, a protocol version that is broken (SSL 2.0/3.0) or withdrawn (TLS 1.0/1.1, RFC 8996). Offering an obsolete version does not merely permit it — it is what a downgrade attack negotiates, so the weakest version on the list is the one that decides the connection's strength. Stop pinning versions here: leave the protocol unset (`SecurityProtocolType.SystemDefault`, or simply do not assign it) so the connection uses the OS policy and picks up TLS 1.3 and future versions without a code change. Where a version must be named explicitly, name `Tls12` and `Tls13` only. — REDACTED:47
  • 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. (×18) — ArcFormats/aNCHOR/AudioFCD.cs:69, ArcFormats/AZSys/ArcEncrypted.cs:422, ArcFormats/Artemis/ArcPFS.cs:101, …
  • A digest from `Read` (MD5/SHA1) is compared against an expected value here, and a mismatch rejects the input — so a collision-broken hash IS the integrity check. — ArcFormats/Abel/ArcARC.cs:71
  • `CzDefaultKey` is the symmetric cipher key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — ArcFormats/KiriKiri/CzCrypt.cs:43
  • `DefaultSalt` is the key-derivation salt and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — ArcFormats/Unity/ArcDSM.cs:88
  • `bytes` is the key-derivation salt and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — ArcFormats/Unity/ScriptDSM.cs:66
  • This type encrypts through `SymmetricAlgorithm`, whose every cipher mode (CBC/ECB/OFB/CFB/CTS) is unauthenticated, and no keyed MAC or AEAD cipher appears anywhere in it — so nothing establishes that the ciphertext it produced is the ciphertext it later reads back. Encryption alone provides confidentiality, not integrity: unauthenticated CBC is MALLEABLE, and an attacker who can modify stored or transmitted ciphertext can flip chosen plaintext bits in the following block by flipping ciphertext bits in the preceding one, without ever knowing the key. Where the decrypt path reports failure differently for a padding error than for a downstream one — a broad `catch` that returns null is the usual spelling — the same construction also answers the attacker's questions, which is the padding-oracle shape that recovers plaintext outright. Prefer an AEAD cipher: `AesGcm` or `ChaCha20Poly1305` authenticate the ciphertext as part of encrypting it, and give you an associated-data slot for the surrounding context. Where the format cannot change, MAC it with encrypt-then-MAC — HMAC-SHA256 over the IV and the ciphertext together, with a key derived separately from the encryption key — and verify that tag with `CryptographicOperations.FixedTimeEquals` BEFORE decrypting anything. — ArcFormats/NitroPlus/ArcNPK.cs:301
  • This code fixes PBKDF2-SHA-1 at 1,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price. (×2) — ArcFormats/Unity/ArcDSM.cs:92, ArcFormats/Unity/ScriptDSM.cs:67
  • DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes. (×3) — ArcFormats/Unity/ScriptDSM.cs:75, REDACTED:144, ArcFormats/Unity/ArcDSM.cs:76

What to do

  • Drop SSL 2.0/3.0 and TLS 1.0/1.1 from the enabled protocol list — prefer leaving it to the OS default (`SystemDefault`) so new versions are picked up automatically, or name `Tls12`/`Tls13` explicitly if it must be pinned.
  • 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. This repository constructs a collision-broken hash (MD5/SHA1) at 18 sites, not one: `ArcFormats/AZSys/ArcEncrypted.cs:422` (SHA1), `ArcFormats/Artemis/ArcPFS.cs:101` (SHA1), `ArcFormats/Cmvs/ArcCPZ.cs:151` (MD5), `ArcFormats/Cmvs/CpzHeader.cs:132` (MD5), `ArcFormats/CsWare/ArcPCS.cs:191` (SHA1), `ArcFormats/Dogenzaka/ImageRSA.cs:58` (SHA1), `ArcFormats/Dogenzaka/ImageRSA.cs:84` (SHA1), `ArcFormats/FamilyAdvSystem/ArcCSAF.cs:92` (MD5), and 10 further site(s). Each is a separate decision — fixing only the line this row cites leaves the others in place.
  • Verify integrity with SHA-256+ rather than MD5/SHA1: a collision-broken digest cannot establish that content matches what was expected, since an attacker able to influence the content can produce a colliding replacement. Where the content is downloaded or otherwise attacker-reachable, prefer an authenticated check — a signature over the digest, or the publisher's SHA-256 fetched over a channel the content itself does not come from. The gate is at `ArcFormats/Abel/ArcARC.cs:71`.
  • Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations. This repository constructs key or salt material fixed at compile time at 3 sites, not one: `ArcFormats/KiriKiri/CzCrypt.cs:43` (symmetric cipher key, `CzDefaultKey`), `ArcFormats/Unity/ArcDSM.cs:88` (key-derivation salt, `DefaultSalt`), `ArcFormats/Unity/ScriptDSM.cs:66` (key-derivation salt, `bytes`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
  • Authenticate ciphertext, do not just encrypt it: move to an AEAD cipher (`AesGcm`, `ChaCha20Poly1305`), or where the wire format is fixed, add encrypt-then-MAC with HMAC-SHA256 over IV+ciphertext under a separately derived key and verify the tag with `CryptographicOperations.FixedTimeEquals` before decrypting. Unauthenticated CBC is malleable, and a decrypt path that distinguishes padding failures from other failures is a padding oracle.
  • Raise the cost parameter to current guidance — PBKDF2 at 1,300,000 (HMAC-SHA1), 600,000 (SHA-256) or 210,000 (SHA-512) iterations; scrypt at N=2^17, r=8, p=1; bcrypt at a work factor of 10 or more — or move to a memory-hard KDF (Argon2id, scrypt) where the platform offers one. Read the parameter from configuration and tune it to roughly 100 ms per derivation on the slowest hardware that must run it, so the price can be raised again without shipping new code. This repository constructs a key derivation priced below the floor at 2 sites, not one: `ArcFormats/Unity/ArcDSM.cs:92` (PBKDF2-SHA-1, 1,000 iterations), `ArcFormats/Unity/ScriptDSM.cs:67` (PBKDF2-SHA-1, 1,000 iterations). Each is a separate decision — fixing only the line this row cites leaves the others in place.
  • Replace DES/3DES (and bare RijndaelManaged) with AES-GCM via `Aes.Create()`. This repository constructs a broken or deprecated cipher at 3 sites, not one: `REDACTED:144` (DES), `ArcFormats/Unity/ArcDSM.cs:76` (RijndaelManaged), `ArcFormats/Unity/ScriptDSM.cs:75` (RijndaelManaged). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X1 · Async correctness2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×2) — ArcFormats/Ethornell/ImageCBG.cs:309, ArcFormats/KiriKiri/ImageTLG.cs:1374
  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. — ArcFormats/Cri/AudioHCA.cs:164
  • `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — REDACTED:222

What to do

  • Sync-over-async (deadlock risk)
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader4.0 / 10Weak✓ Tool-verified

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

  • `unpacked_size` is read from the stream being parsed at line 154 (`ReadUInt32`), then used to size an array at line 155 — and nowhere in this method is `unpacked_size` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `unpacked_size` against the bytes actually remaining in the stream before spending it. — ArcFormats/CaramelBox/ArcARC4.cs:155
  • `length` is read from the stream being parsed at line 232 (`ReadInt32`), then read in bulk from that same stream at line 234 — and nowhere in this method is `length` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `length` against the bytes actually remaining in the stream before spending it. — REDACTED:234
  • `code_size` is read from the stream being parsed at line 200 (`ReadUInt32`), then read in bulk from that same stream at line 204 — and nowhere in this method is `code_size` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `code_size` against the bytes actually remaining in the stream before spending it. — ArcFormats/Liar/ArcXFL.cs:204
  • `count` is read from the stream being parsed at line 134 (`ReadInt32`), then used to size an array at line 135 — and nowhere in this method is `count` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `count` against the bytes actually remaining in the stream before spending it. — Legacy/WestGate/ArcUSF.cs:135

What to do

  • Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness6.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `m_input` is never created by `DataImageDecoder` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 317). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/Cyberworks/ImageDATA.cs:317
  • `m_input` is never created by `MzxImageReader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 314). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/HuneX/ArcMZP.cs:314
  • `m_input` is never created by `GrpUnpacker` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 613). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/Ankh/ArcGRP.cs:613
  • `m_input` is never created by `PcgReaderBase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 175). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/Groover/ArcPCG.cs:175
  • `m_input` is never created by `CDecoderBase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 142). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/Foster/ImageC24.cs:142
  • `m_input` is never created by `AImageReader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 488). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/Cyberworks/ImageTINK.cs:488
  • `m_input` is never created by `IpfReader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 250). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/TechnoBrain/ImageIPF.cs:250
  • `m_input` is never created by `AssetReader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 214). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/Unity/AssetReader.cs:214
  • `m_input` is never created by `PackedReader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 199). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/ArcSPack.cs:199
  • `m_input` is never created by `Reader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 291). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/AnimeGameSystem/ImageAinos.cs:291
  • `m_input` is never created by `Reader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 232). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/Marble/ImagePRS.cs:232
  • `m_input` is never created by `Reader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 381). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — ArcFormats/ShiinaRio/ImageS25.cs:381
  • `sw` is a `StreamWriter`, which implements `IDisposable`, and it is created here (line 462). Every use of it in `SerializeSchemeJson` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var sw = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:462
  • `m_file` is never created by `ImageFormatDecoder` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 113). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — GameRes/ImageDecoder.cs:113
  • `m_input` is never created by `BinaryImageDecoder` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 155). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — GameRes/ImageDecoder.cs:155
  • `reader` is a `BinaryReader`, which implements `IDisposable`, and it is created here (line 42). Every use of it in `ReadMetaData` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var reader = …;`), which releases it at the end of the scope on every path including a throw. — Legacy/Broccoli/BroccoliGrp.cs:42
  • `reader` is a `CgdDecoder`, which implements `IDisposable`, and it is created here (line 56). Every use of it in `Read` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var reader = …;`), which releases it at the end of the scope on every path including a throw. — Legacy/KApp/ImageCGD.cs:56
  • `reader` is a `CgdDecoder`, which implements `IDisposable`, and it is created here (line 94). Every use of it in `Read` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var reader = …;`), which releases it at the end of the scope on every path including a throw. — Legacy/KApp/ImageCGD.cs:94
  • `m_input` is never created by `BitmapDecoder` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 293). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — Legacy/Mina/ArcPAK.cs:293
  • `m_input` is never created by `GCmpDecoder` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 668). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — Legacy/Nekotaro/ImageGCmp.cs:668

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard5.4 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

  • This access `ext[0]` has no test of the length of `ext` on its own path, while this method tests it for that position at line 106 (`string.IsNullOrEmpty (ext)`): where that test fails, this read throws. Either the test is load-bearing and this read needs it too, or the length of `ext` is fixed here and the test is dead. — ArcFormats/ArcCommon.cs:107
  • This guard bounds `fmt_index` with `fmt_index > formats.Count`, which admits `fmt_index` equal to the length of `formats`; `formats[fmt_index]` then reads one past the last element and throws. The bound is off by one: test `fmt_index < formats.Length` (or `.Count`). — ArcFormats/Crowd/ArcPCK.cs:146

What to do

  • Each finding names the index access that escapes the guard and the line of the correctly bracketed access beside it. Compare the two: they differ only in where one parenthesis sits. Move it so the emptiness test brackets every access to that symbol — and if the value provably cannot be empty at this point, delete the test rather than leave a condition that guards one access and not its neighbour.
X29 · Per-element action decided by a fixed element7.9 / 10Strong✓ Tool-verified

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

  • This loop runs once per element of `m_dxt_buffer`, and the statement it guards acts on the element it is on — `m_dxt_buffer[i]`. The test deciding whether that statement runs does not: `has_alpha` reads `m_dxt_buffer[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 91, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out. — ArcFormats/DirectDraw/DxtDecoder.cs:96

What to do

  • Each finding names the test and the statement it guards, which index the same collection at two different subscripts — one fixed, one the loop variable. Confirm from the two, then decide which subscript the test meant. If it was meant to be per-element, give it the loop variable so each element is judged on itself. If it really is one answer for the whole collection, hoist the test OUT of the loop, where a reader can see it is asked once and where it is not re-evaluated on every pass — leaving it inside, reading a fixed element, is the one arrangement that cannot be right under either reading.
X3 · Exception handling4.8 / 10Weak✓ Tool-verified

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. (×36) — ArcFormats/Abel/ImageCBF.cs:80, ArcFormats/Ankh/ArcGRP.cs:364, ArcFormats/Ankh/ArcGRP.cs:453, …
  • `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — ArcFormats/Abogado/ImageKG.cs:138, ArcFormats/Dvn/ArcDVN.cs:77
  • 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: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). — ArcFormats/Cri/AudioHCA.cs:166
  • `catch (InvalidFormatException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — ArcFormats/FC01/ImageMCG.cs:297

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health46.4Weak — gated by D18, X1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture69.3Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity44.3Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness34.0Weak — gated by D8, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security27.4Weak — gated by D28, S1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60.0AdequateStrongest area.
Unscored — 4 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • SC1 Supply-chain hygiene — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 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.
  • AX1 Captive dependencies — no DI registrations detected
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • M4 Documentation accuracy — Not applicable: the 6 current-state document(s) make no claim of a kind M4 checks.
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no async method does work a token could cancel
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X5 Nullable reference types — no NRT-eligible projects
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 106 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×49
  • EmptyCatchBlock ArcFormats/AZSys/ArcEncrypted.cs:215 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Abel/ImageCBF.cs:80 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Ankh/ArcGRP.cs:364 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Ankh/ArcGRP.cs:453 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock REDACTED:130 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Bishop/ImageGSA.cs:92 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/CaramelBox/ArcARC3.cs:184 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/CatSystem/ArcINT.cs:165 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Cri/AudioHCA.cs:166 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/DxLib/ArcDX.cs:150 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Emote/ArcPSB.cs:84 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock REDACTED:220 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Interheart/ArcFPK.cs:70 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Kaas/ArcKAAS.cs:85 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/KiriKiri/ArcXP3.cs:317 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/KiriKiri/HxCrypt.cs:140 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Leaf/ArcPAK.cs:163 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Lucifen/ArcLPK.cs:175 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Majiro/ImageRCT.cs:145 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Majiro/ImageRCT.cs:249 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Majiro/ImageRCT.cs:357 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/NScripter/ArcNS2.cs:68 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/NScripter/ArcNSA.cs:107 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Nexas/ArcPAC.cs:97 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ArcFormats/Nexas/ArcPAC.cs:144 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • + 24 more in this group — see findings.md.
D17 · Explicit Debt · WriteOnlyPrivateField · ×23
  • WriteOnlyPrivateField ArcFormats/AZSys/ArcAZSys.cs:187 — private int m_compr2_len — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/AZSys/ArcAZSys.cs:188 — private int m_output_len — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/AudioVOC.cs:35 — private int m_version — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Macromedia/ArcSWF.cs:291 — private int m_version — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Qlie/ArcABMP.cs:79 — private int m_version — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Cmvs/ImagePB2.cs:89 — private int m_frame_count — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Macromedia/ArcSWF.cs:309 — private int m_frame_count — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Emote/ArcPSB.cs:348 — private int m_extra_data — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Entis/EriReader.cs:62 — private sbyte[] m_ptrNextBlockBuf — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Entis/EriReader.cs:69 — private int[] m_ptrNextPrevBlocks — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField REDACTED:398 — private int m_unpacked_size — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Gss/ArcARC.cs:498 — private int[] dword_455540 — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Gss/ArcARC.cs:502 — private int[] dword_455580 — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Gss/ArcARC.cs:506 — private int[] dword_4554E8 — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Ivory/AudioCTRK.cs:107 — private int m_end — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Macintosh/ImagePICT.cs:373 — private byte[] m_unpack_buffer — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Macromedia/ArcSWF.cs:308 — private int m_frame_rate — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/ShiinaRio/AudioPAD.cs:71 — private int m_pcm_size — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/Unity/OggStream.cs:138 — private int HeaderFill — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField ArcFormats/rUGP/ImageRIP.cs:463 — private CObject field_4C — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField GameRes/ImageTIFF.cs:126 — private UInt64Reader ReadUInt64 — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Legacy/Jupiter/ArcLB5.cs:96 — private byte[] m_output — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Legacy/Kurumi/ArcMPK.cs:148 — private short word_471D4E — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
IC1 · Incompleteness & stubs · Unfinished stub · ×10
  • Unfinished stub — throws NotImplementedException ArcFormats/Entis/EriReader.cs:769 — `DecodeLossyV9` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Entis/EriReader.cs:653 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException ArcFormats/Gss/ArcARC.cs:436 — `UnpackW` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Gss/ArcARC.cs:94 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException ArcFormats/Ikura/ImageTAN.cs:165 — `Unpack24bpp` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Ikura/ImageTAN.cs:111 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException ArcFormats/Leaf/ImagePX.cs:323 — `UnpackBlock_4_8` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Leaf/ImagePX.cs:282 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException ArcFormats/Sviu/AudioKPV.cs:95 — `UnpackRaw` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Sviu/AudioKPV.cs:87 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException ArcFormats/Sviu/AudioKPV.cs:134 — `UnpackV10` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Sviu/AudioKPV.cs:90 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException ArcFormats/Unity/ArcUnityFS.cs:161 — `UnpackLzma` is a shipped member whose body only throws — and it is REACHED: ArcFormats/Unity/ArcUnityFS.cs:88 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException ArcFormats/rUGP/ArcRIO.cs:597 — `GetRtcFromMessageName` is a shipped member whose body only throws — and it is REACHED: ArcFormats/rUGP/ArcRIO.cs:561 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException ArcFormats/rUGP/ArcRIO.cs:607 — `FindObject` is a shipped member whose body only throws — and it is REACHED: ArcFormats/rUGP/ArcRIO.cs:454 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException ArcFormats/rUGP/ArcRIO.cs:622 — `CreateAnonymousRio` is a shipped member whose body only throws — and it is REACHED: ArcFormats/rUGP/ArcRIO.cs:655 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
D28 · Secrets (history) · REDACTED · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
S1 · Cryptographic Hygiene · Cryptographic key material is a compile-time constant · ×3
  • Cryptographic key material is a compile-time constant ArcFormats/KiriKiri/CzCrypt.cs:43 — `CzDefaultKey` is the symmetric cipher key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
  • Cryptographic key material is a compile-time constant ArcFormats/Unity/ArcDSM.cs:88 — `DefaultSalt` is the key-derivation salt and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
  • Cryptographic key material is a compile-time constant ArcFormats/Unity/ScriptDSM.cs:66 — `bytes` is the key-derivation salt and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
D17 · Explicit Debt · FileScopedPragmaDisable · ×2
  • FileScopedPragmaDisable ArcFormats/KiriKiri/HxCrypt.cs:35 — #pragma warning disable IDE0019 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable GUI/FileErrorDialog.xaml.cs:82 — #pragma warning disable 67 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
D30 · Dependency Vulnerabilities · High CVE · ×2
  • REDACTED
  • REDACTED
D17 · Explicit Debt · DeadLoopAccumulator · ×1
  • DeadLoopAccumulator ArcFormats/Ail/ArcAil.cs:111 — uint extra = 6; … if (extra > entry.Size) — this reset runs at the top of every pass, so the value is back to its starting constant before the test below it is reached: the test is decided the same way on every iteration, and whatever the loop adds to this variable further down is wiped out before anything can read it. The threshold it is guarding can therefore never be crossed, however many times the loop goes round, which is why nothing has ever been seen to trip. Move the reset ABOVE the loop, so the count accumulates across iterations the way the test below assumes; if it really is meant to be per-iteration state, then the test belongs with it and the accumulation does not.
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
S1 · Cryptographic Hygiene · Weak hash is the integrity check · ×1
  • Weak hash is the integrity check ArcFormats/Abel/ArcARC.cs:71 — A digest from `Read` (MD5/SHA1) is compared against an expected value here, and a mismatch rejects the input — so a collision-broken hash IS the integrity check.
Serious — 2162 finding(s)
D17 · Explicit Debt · CommentedOutCode · ×61
  • CommentedOutCode ArcFormats/Cri/AudioADX.cs:203 — 17 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Entis/EriReader.cs:859 — 17 consecutive commented-code lines
  • CommentedOutCode ArcFormats/DxLib/ArcDX8.cs:250 — 7 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Kid/ImageKLZ.cs:76 — 7 consecutive commented-code lines
  • CommentedOutCode ArcFormats/KogadoCocotte.cs:469 — 7 consecutive commented-code lines
  • CommentedOutCode ArcFormats/KogadoCocotte.cs:501 — 7 consecutive commented-code lines
  • CommentedOutCode ArcFormats/DxLib/DxKey.cs:249 — 6 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Kid/ImageKLZ.cs:122 — 6 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Kid/ImageKLZ.cs:148 — 6 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Seraphim/ArcSCN.cs:89 — 6 consecutive commented-code lines
  • CommentedOutCode Legacy/Factor/ArcRES.cs:61 — 6 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Entis/EriReader.cs:774 — 3 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Entis/EriReader.cs:778 — 3 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Entis/EriReader.cs:1145 — 3 consecutive commented-code lines
  • CommentedOutCode ArcFormats/KogadoCocotte.cs:55 — 3 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Mnp/ArcMMA.cs:109 — 3 consecutive commented-code lines
  • CommentedOutCode GameRes/MultiDict.cs:100 — 3 consecutive commented-code lines
  • CommentedOutCode GameRes/MultiDict.cs:116 — 3 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Entis/EriReader.cs:843 — 15 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Entis/EriReader.cs:909 — 8 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Entis/MioDecoder.cs:404 — 8 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Key/ArcPAK.cs:186 — 8 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Kid/ImageKLZ.cs:155 — 8 consecutive commented-code lines
  • CommentedOutCode Legacy/Paprika/ImageNP.cs:265 — 8 consecutive commented-code lines
  • CommentedOutCode ArcFormats/Entis/MioDecoder.cs:701 — 9 consecutive commented-code lines
  • + 36 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×47
  • Duplicated block (8 lines × 2) ArcFormats/Entis/EriReader.cs:2048 — ArcFormats/Entis/EriReader.cs:2048-2055 | ArcFormats/Entis/EriReader.cs:2062-2069 — 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 `ArcFormats/Entis/EriReader.cs:2048` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) ArcFormats/Entis/MioDecoder.cs:451 — ArcFormats/Entis/MioDecoder.cs:451-458 | ArcFormats/Entis/MioDecoder.cs:501-508 — 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 `ArcFormats/Entis/MioDecoder.cs:451` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) ArcFormats/MersenneTwister.cs:18 — ArcFormats/MersenneTwister.cs:18-25 | ArcFormats/Qlie/QlieMersenneTwister.cs:23-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.
  • Duplicated block (8 lines × 2) ArcFormats/Carriere/ArcARC.cs:59 — ArcFormats/Carriere/ArcARC.cs:59-66 | ArcFormats/Taskforce/ArcDAT.cs:60-67 — before extracting anything, compare `ArcFormats/Carriere/ArcARC.cs` and `ArcFormats/Taskforce/ArcDAT.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Carriere/ArcARC.cs:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) ArcFormats/Zyx/ImageSPL.cs:154 — ArcFormats/Zyx/ImageSPL.cs:154-161 | ArcFormats/Zyx/ImageSPL.cs:165-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. 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) Legacy/Asura/ImageMTG.cs:75 — Legacy/Asura/ImageMTG.cs:75-82 | Legacy/Rina/ImageRAD.cs:81-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) Legacy/DMotion/ArcDM.cs:80 — Legacy/DMotion/ArcDM.cs:80-87 | Legacy/Pochette/ArcPAC.cs:79-86 — 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 `Legacy/DMotion/ArcDM.cs:80` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) ArcFormats/Abel/ArcBIN.cs:61 — ArcFormats/Abel/ArcBIN.cs:61-68 | ArcFormats/Leaf/ArcLEAF.cs:100-107 — 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 `ArcFormats/Abel/ArcBIN.cs:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) ArcFormats/Kaguya/ArcAN21.cs:133 — ArcFormats/Kaguya/ArcAN21.cs:133-140 | ArcFormats/Kaguya/ArcPL10.cs:115-122 — before extracting anything, compare `ArcFormats/Kaguya/ArcAN21.cs` and `ArcFormats/Kaguya/ArcPL10.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Kaguya/ArcAN21.cs:133` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) ArcFormats/Ethornell/ArcBGI.cs:147 — ArcFormats/Ethornell/ArcBGI.cs:147-154 | ArcFormats/Key/ArcPAK.cs:96-103 — 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 `ArcFormats/Ethornell/ArcBGI.cs:147` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) ArcFormats/Palette/ArcPAK.cs:51 — ArcFormats/Palette/ArcPAK.cs:51-58 | ArcFormats/Sohfu/ArcSKA.cs:45-52 — 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 `ArcFormats/Palette/ArcPAK.cs:51` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Palette/ArcPAK.cs:48` calls `AsciiEqual` and `ArcFormats/Sohfu/ArcSKA.cs:43` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) REDACTED:195 — REDACTED:195-202 | ArcFormats/Stack/ArcGPK.cs:120-127 — 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 `REDACTED: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:194` calls `GetFileName` and `ArcFormats/Stack/ArcGPK.cs:119` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) ArcFormats/RealLive/AudioNWA.cs:177 — ArcFormats/RealLive/AudioNWA.cs:177-184 | ArcFormats/RealLive/AudioNWA.cs:199-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/RealLive/AudioNWA.cs:177` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) ArcFormats/rUGP/ImageRIP.cs:581 — ArcFormats/rUGP/ImageRIP.cs:581-588 | ArcFormats/rUGP/ImageRIP.cs:591-598 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) ArcFormats/rUGP/ImageRIP.cs:710 — ArcFormats/rUGP/ImageRIP.cs:710-717 | ArcFormats/rUGP/ImageRIP.cs:720-727 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) ArcFormats/AdvSys/ArcGR2.cs:65 — ArcFormats/AdvSys/ArcGR2.cs:65-72 | Legacy/Electriciteit/ArcDAT.cs:64-71 — 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 `ArcFormats/AdvSys/ArcGR2.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) ArcFormats/VnSystem/ArcVFS.cs:47 — ArcFormats/VnSystem/ArcVFS.cs:47-54 | ArcFormats/Youkai/ArcDAT.cs:98-105 — 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 `ArcFormats/VnSystem/ArcVFS.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. 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) ArcFormats/ShiinaRio/ImageMI4.cs:242 — ArcFormats/ShiinaRio/ImageMI4.cs:242-249 | ArcFormats/ShiinaRio/ImageMI4.cs:277-284 — 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 `ArcFormats/ShiinaRio/ImageMI4.cs:242` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/ShiinaRio/ImageMI4.cs:285` calls `GetBits` and `ArcFormats/ShiinaRio/ImageMI4.cs:250` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) Legacy/BRoom/ArcCPC.cs:80 — Legacy/BRoom/ArcCPC.cs:80-87 | Legacy/BRoom/ArcPK.cs:62-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) Legacy/Dall/ArcPEL.cs:47 — Legacy/Dall/ArcPEL.cs:47-54 | Legacy/Sceplay/ArcPAK.cs:44-51 — 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 `Legacy/Dall/ArcPEL.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. 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) Legacy/Mina/ArcPAK.cs:49 — Legacy/Mina/ArcPAK.cs:49-56 | Legacy/Mina/ArcPAK.cs:99-106 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) ArcFormats/ComicPlayer/ArcCPF.cs:68 — ArcFormats/ComicPlayer/ArcCPF.cs:68-75 | ArcFormats/YuukiNovel/ArcYuuki.cs:56-63 — 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 `ArcFormats/ComicPlayer/ArcCPF.cs:68` 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) ArcFormats/Ice/ImageIBM.cs:74 — ArcFormats/Ice/ImageIBM.cs:74-81 | ArcFormats/Triangle/ImageTRI.cs:72-79 — 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 `ArcFormats/Ice/ImageIBM.cs:74` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) ArcFormats/Interheart/ArcFPK2.cs:45 — ArcFormats/Interheart/ArcFPK2.cs:45-52 | ArcFormats/Silky/ArcAWF.cs:47-54 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Silky/ArcAWF.cs:57` calls `IsPathEqualsToFileName` and `ArcFormats/Interheart/ArcFPK2.cs:53` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) ArcFormats/Kid/AudioWAF.cs:64 — ArcFormats/Kid/AudioWAF.cs:64-71 | GameRes/AudioWAV.cs:158-165 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Kid/AudioWAF.cs:72` calls `Write` and `GameRes/AudioWAV.cs:166` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • + 22 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×47
  • Duplicated block (7 lines × 2) ArcFormats/AdvSys/ImageGWD.cs:89 — ArcFormats/AdvSys/ImageGWD.cs:89-95 | Legacy/HillField/ImageIMA.cs:76-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) ArcFormats/Amaterasu/ImageGRP.cs:80 — ArcFormats/Amaterasu/ImageGRP.cs:80-86 | ArcFormats/MAGES/ImageBIN.cs:121-127 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/MAGES/ImageBIN.cs:119` calls `Write` and `ArcFormats/Amaterasu/ImageGRP.cs:78` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) ArcFormats/ArcPACKDAT.cs:72 — ArcFormats/ArcPACKDAT.cs:72-78 | ArcFormats/EntExec/ArcCAB.cs:58-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/ArcPACKDAT.cs:72` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) ArcFormats/Leaf/ArcTEX.cs:65 — ArcFormats/Leaf/ArcTEX.cs:65-71 | ArcFormats/YuukiNovel/ArcYuuki.cs:72-78 — 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 `ArcFormats/Leaf/ArcTEX.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) ArcFormats/Amaterasu/ImageGRP.cs:85 — ArcFormats/Amaterasu/ImageGRP.cs:85-91 | ArcFormats/Kaguya/ImageAP.cs:102-108 — 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 `ArcFormats/Amaterasu/ImageGRP.cs:85` 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) Legacy/KeroQ/ArcDAT.cs:69 — Legacy/KeroQ/ArcDAT.cs:69-75 | Legacy/Tetratech/ArcBND.cs:68-74 — 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 `Legacy/KeroQ/ArcDAT.cs:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Legacy/Iris/ArcFPACK.cs:51 — Legacy/Iris/ArcFPACK.cs:51-57 | Legacy/Mink/ArcBINZ.cs:46-52 — 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 `Legacy/Iris/ArcFPACK.cs:51` 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) ArcFormats/Abogado/ArcPAK.cs:60 — ArcFormats/Abogado/ArcPAK.cs:60-66 | ArcFormats/CDPA/ArcPACK.cs:52-58 — 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 `ArcFormats/Abogado/ArcPAK.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 (7 lines × 2) ArcFormats/Antique/ArcDAT.cs:43 — ArcFormats/Antique/ArcDAT.cs:43-49 | ArcFormats/FC01/ArcMRG0.cs:45-51 — 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 `ArcFormats/Antique/ArcDAT.cs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) ArcFormats/SoftwareHouseParsley/ArcCG.cs:66 — ArcFormats/SoftwareHouseParsley/ArcCG.cs:66-72 | ArcFormats/SoftwareHouseParsley/ArcUCG.cs:58-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/SoftwareHouseParsley/ArcCG.cs:66` 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) ArcFormats/Cromwell/ArcPAK.cs:77 — ArcFormats/Cromwell/ArcPAK.cs:77-83 | ArcFormats/Kiss/ArcARC.cs:72-78 — 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 `ArcFormats/Cromwell/ArcPAK.cs:77` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) ArcFormats/KScript/ArcKPC.cs:66 — ArcFormats/KScript/ArcKPC.cs:66-72 | ArcFormats/Leaf/ArcAM.cs:71-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 `ArcFormats/KScript/ArcKPC.cs:66` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) ArcFormats/Leaf/ArcLAC.cs:103 — ArcFormats/Leaf/ArcLAC.cs:103-109 | ArcFormats/NekoSDK/ArcDAT.cs:60-66 — 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 `ArcFormats/Leaf/ArcLAC.cs:103` 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) ArcFormats/ImageLZ.cs:48 — ArcFormats/ImageLZ.cs:48-54 | ArcFormats/ImageLZ.cs:61-67 — 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 `ArcFormats/ImageLZ.cs:48` 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) ArcFormats/Softpal/ArcPAC.cs:50 — ArcFormats/Softpal/ArcPAC.cs:50-56 | ArcFormats/Softpal/ArcPAC.cs:126-132 — 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 (7 lines × 2) ArcFormats/Nags/ArcNFS.cs:74 — ArcFormats/Nags/ArcNFS.cs:74-80 | ArcFormats/Propeller/ArcMPK.cs:69-75 — 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 `ArcFormats/Nags/ArcNFS.cs:74` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) ArcFormats/Softpal/ImagePIC.cs:160 — ArcFormats/Softpal/ImagePIC.cs:160-166 | ArcFormats/Softpal/ImagePIC.cs:207-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Softpal/ImagePIC.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 (7 lines × 2) ArcFormats/KiriKiri/ImageTLG.cs:679 — ArcFormats/KiriKiri/ImageTLG.cs:679-685 | ArcFormats/KiriKiri/ImageTLG.cs:735-741 — 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 `ArcFormats/KiriKiri/ImageTLG.cs:679` 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) Legacy/AdvS/ArcDAT.cs:55 — Legacy/AdvS/ArcDAT.cs:55-61 | Legacy/BRoom/ArcPK.cs:62-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/AdvS/ArcDAT.cs:52` calls `ReadUInt32` and `Legacy/BRoom/ArcPK.cs:59` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) Legacy/AlphaSystem/ArcPAK.cs:58 — Legacy/AlphaSystem/ArcPAK.cs:58-64 | Legacy/Zone/ArcPKD.cs:53-59 — 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 `Legacy/AlphaSystem/ArcPAK.cs:58` 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) Legacy/ApplePie/ArcARC.cs:52 — Legacy/ApplePie/ArcARC.cs:52-58 | Legacy/Iris/ArcFPACK.cs:55-61 — 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 `Legacy/ApplePie/ArcARC.cs:52` 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) ArcFormats/BlackRainbow/ArcCCF.cs:65 — ArcFormats/BlackRainbow/ArcCCF.cs:65-71 | ArcFormats/BlackRainbow/ArcSPPAK.cs:81-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/BlackRainbow/ArcCCF.cs:65` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 2) ArcFormats/Leaf/ArcLEAF.cs:93 — ArcFormats/Leaf/ArcLEAF.cs:93-99 | ArcFormats/Leaf/ArcLEAF.cs:135-141 — 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 `ArcFormats/Leaf/ArcLEAF.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 (7 lines × 2) ArcFormats/SoftwareHouseParsley/ArcCG.cs:70 — ArcFormats/SoftwareHouseParsley/ArcCG.cs:70-76 | Legacy/Peach/ArcNIJI.cs:52-58 — 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 (7 lines × 2) ArcFormats/Kaguya/ArcLINK.cs:828 — ArcFormats/Kaguya/ArcLINK.cs:828-834 | ArcFormats/Kaguya/ArcLINK.cs:840-846 — 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 `ArcFormats/Kaguya/ArcLINK.cs:828` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • + 22 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×38
  • Duplicated block (5 lines × 2) ArcFormats/Ankh/ArcGRP.cs:296 — ArcFormats/Ankh/ArcGRP.cs:296-300 | ArcFormats/Ankh/ArcGRP.cs:311-315 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) ArcFormats/DigitalWorks/ImageTM2.cs:163 — ArcFormats/DigitalWorks/ImageTM2.cs:163-167 | ArcFormats/DigitalWorks/ImageTM2.cs:177-181 — 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 `ArcFormats/DigitalWorks/ImageTM2.cs:163` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) ArcFormats/Abogado/ArcPAK.cs:69 — ArcFormats/Abogado/ArcPAK.cs:69-73 | ArcFormats/Ikura/ArcDRS.cs:157-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Abogado/ArcPAK.cs:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) ArcFormats/HSP/ArcDPM.cs:159 — ArcFormats/HSP/ArcDPM.cs:159-163 | ArcFormats/HSP/ArcDPM.cs:173-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 `ArcFormats/HSP/ArcDPM.cs:159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) ArcFormats/Entis/ErisaMatrix.cs:409 — ArcFormats/Entis/ErisaMatrix.cs:409-413 | ArcFormats/Entis/ErisaMatrix.cs:436-440 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (5 lines × 2) Legacy/Harvest/ArcDAT.cs:50 — Legacy/Harvest/ArcDAT.cs:50-54 | Legacy/RedZone/ArcPAK.cs:53-57 — 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 `Legacy/Harvest/ArcDAT.cs:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) ArcFormats/Abel/ArcARC.cs:54 — ArcFormats/Abel/ArcARC.cs:54-58 | ArcFormats/Key/ArcPAK.cs:49-53 — 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 (5 lines × 2) ArcFormats/Lilim/ArcFGA.cs:68 — ArcFormats/Lilim/ArcFGA.cs:68-72 | ArcFormats/ShiinaRio/ArcWARC1.0.cs:66-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) ArcFormats/DxLib/DxKey.cs:149 — ArcFormats/DxLib/DxKey.cs:149-153 | ArcFormats/DxLib/DxKey.cs:191-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/DxLib/DxKey.cs:149` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) ArcFormats/Interheart/ArcFPK.cs:125 — ArcFormats/Interheart/ArcFPK.cs:125-129 | ArcFormats/KScript/ArcKPC.cs:64-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. 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) ArcFormats/ActiveSoft/ArcADPACK.cs:66 — ArcFormats/ActiveSoft/ArcADPACK.cs:66-70 | ArcFormats/ActiveSoft/ArcADPACK.cs:153-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) ArcFormats/BlackRainbow/ArcGSP.cs:57 — ArcFormats/BlackRainbow/ArcGSP.cs:57-61 | ArcFormats/Interheart/ArcFPK.cs:93-97 — 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 (5 lines × 2) ArcFormats/Pajamas/ArcGameDat.cs:72 — ArcFormats/Pajamas/ArcGameDat.cs:72-76 | ArcFormats/Valkyria/ArcDAT.cs:61-65 — 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) ArcFormats/Camellia.cs:189 — ArcFormats/Camellia.cs:189-193 | ArcFormats/Camellia.cs:200-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Legacy/Aquarium/ArcAAP.cs:51 — Legacy/Aquarium/ArcAAP.cs:51-55 | Legacy/Asura/ArcPAK.cs:56-60 — 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 `Legacy/Aquarium/ArcAAP.cs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Legacy/Aquarium/ArcAAP.cs:56` calls `ReadUInt32` and `Legacy/Asura/ArcPAK.cs:61` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) Legacy/Dice/ArcRLZ.cs:52 — Legacy/Dice/ArcRLZ.cs:52-56 | Legacy/Sogna/ArcSGS.cs:53-57 — 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 `Legacy/Dice/ArcRLZ.cs:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Legacy/Sogna/ArcSGS.cs:58` calls `ReadByte` and `Legacy/Dice/ArcRLZ.cs:57` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) ArcFormats/PkWare/ArcZIP.cs:129 — ArcFormats/PkWare/ArcZIP.cs:129-133 | ArcFormats/VnMaker/ArcZIP.cs:105-109 — `ArcFormats/PkWare/ArcZIP.cs` and `ArcFormats/VnMaker/ArcZIP.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 30 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/PkWare/ArcZIP.cs:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/PkWare/ArcZIP.cs:134` calls `Any`, `QueryPassword` and `ArcFormats/VnMaker/ArcZIP.cs:110` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) ArcFormats/Circus/ArcValkyrieComplex.cs:89 — ArcFormats/Circus/ArcValkyrieComplex.cs:89-93 | ArcFormats/Propeller/ArcMPK.cs:66-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Circus/ArcValkyrieComplex.cs:94` calls `HasExtension` and `ArcFormats/Propeller/ArcMPK.cs:71` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) ArcFormats/AZSys/ArcEncrypted.cs:543 — ArcFormats/AZSys/ArcEncrypted.cs:543-547 | ArcFormats/AZSys/ArcEncrypted.cs:551-555 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (5 lines × 2) ArcFormats/VnSystem/ArcVFS.cs:71 — ArcFormats/VnSystem/ArcVFS.cs:71-75 | Legacy/Pinpai/ArcARC.cs:75-79 — 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 (5 lines × 2) ArcFormats/Entis/MioDecoder.cs:295 — ArcFormats/Entis/MioDecoder.cs:295-299 | ArcFormats/Entis/MioDecoder.cs:587-591 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) ArcFormats/ArcIKS.cs:67 — ArcFormats/ArcIKS.cs:67-71 | ArcFormats/Irrlicht/ArcARK.cs:62-66 — 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. 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) ArcFormats/Cri/ImageXTX.cs:202 — ArcFormats/Cri/ImageXTX.cs:202-206 | ArcFormats/Cri/ImageXTX.cs:214-218 — 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 `ArcFormats/Cri/ImageXTX.cs:202` 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 (5 lines × 2) ArcFormats/Primel/ImageGBC.cs:192 — ArcFormats/Primel/ImageGBC.cs:192-196 | ArcFormats/Primel/ImageGBC.cs:199-203 — 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 `ArcFormats/Primel/ImageGBC.cs:192` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) ArcFormats/AZSys/ArcEncrypted.cs:505 — ArcFormats/AZSys/ArcEncrypted.cs:505-509 | ArcFormats/AZSys/ArcEncrypted.cs:515-519 — 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.
  • + 13 more in this group — see findings.md.
AX2 · Stateful singletons · Process-global static state · ×37
  • Process-global static state: WebPCodec ArcFormats/WebPCodec.cs:34 — `WebPCodec` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (loaded; e.g. `loaded` at line 61). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: OggInput ArcFormats/AudioOGG.cs:35 — `OggInput` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_conversionBuffer; e.g. `_conversionBuffer` at line 94). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: DatOpener ArcFormats/Actgs/ArcDAT.cs:53 — `DatOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 167). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: IntOpener ArcFormats/CatSystem/ArcINT.cs:112 — `IntOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 247). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: DataOpener ArcFormats/Cyberworks/ArcDATA.cs:54 — `DataOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 70). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: DatOpener ArcFormats/Cyberworks/ArcDAT.cs:178 — `DatOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 385). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: TinkAudio ArcFormats/Cyberworks/AudioTINK.cs:41 — `TinkAudio` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 59). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: MedOpener ArcFormats/DxLib/ArcMED.cs:92 — `MedOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 111). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: PakOpener REDACTED:65 — `PakOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 198). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: McgFormat ArcFormats/FC01/ImageMCG.cs:56 — `McgFormat` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 70). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Xp3Opener ArcFormats/KiriKiri/ArcXP3.cs:81 — `Xp3Opener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KiriKiriScheme; e.g. `KiriKiriScheme` at line 786). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: GrpUnpacker ArcFormats/Ankh/ArcGRP.cs:335 — `GrpUnpacker` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (LastUsedMethod; e.g. `LastUsedMethod` at line 369). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: LeafPackOpener ArcFormats/Leaf/ArcLEAF.cs:52 — `LeafPackOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 220). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AmOpener ArcFormats/Leaf/ArcAM.cs:34 — `AmOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DecryptTable; e.g. `DecryptTable` at line 92). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Reader ArcFormats/Macromedia/DirectorFile.cs:704 — `Reader` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownFourCC; e.g. `KnownFourCC` at line 759). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Ns2Opener ArcFormats/NScripter/ArcNS2.cs:36 — `Ns2Opener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 50). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: NsaOpener ArcFormats/NScripter/ArcNSA.cs:74 — `NsaOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 89). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: YpfOpener ArcFormats/YuRis/ArcYPF.cs:114 — `YpfOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 135). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: MpxOpener ArcFormats/Ikura/ArcDRS.cs:111 — `MpxOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownSecrets; e.g. `KnownSecrets` at line 244). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AdsOpener ArcFormats/BlackRainbow/ArcADS.cs:42 — `AdsOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 61). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: CpzOpener ArcFormats/Cmvs/ArcCPZ.cs:82 — `CpzOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 103). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ArcAI5Opener ArcFormats/elf/ArcAi5Win.cs:51 — `ArcAI5Opener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 67). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: PsbOpener ArcFormats/Emote/ArcPSB.cs:54 — `PsbOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (KnownKeys; e.g. `KnownKeys` at line 146). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: MgpkOpener ArcFormats/MangaGamer/ArcMGPK.cs:58 — `MgpkOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 209). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: NpkOpener ArcFormats/NitroPlus/ArcNPK.cs:84 — `NpkOpener` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DefaultScheme; e.g. `DefaultScheme` at line 102). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • + 12 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×37
  • Swallowed exception (empty catch) ArcFormats/Abel/ImageCBF.cs:80 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Ankh/ArcGRP.cs:364 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Ankh/ArcGRP.cs:453 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/SoftwareHouseParsley/ArcCG3.cs:139 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Bishop/ImageGSA.cs:92 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/KiriKiri/HxCrypt.cs:140 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Leaf/ArcPAK.cs:163 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Stack/ArcGPK.cs:136 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Suika/ArcSuika.cs:75 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/rUGP/ArcRIO.cs:1298 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/CaramelBox/ArcARC3.cs:184 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Cri/AudioHCA.cs:166 — 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: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
  • Swallowed exception (empty catch) ArcFormats/Emote/ArcPSB.cs:84 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/NScripter/ArcNS2.cs:68 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Primel/ArcPCF.cs:143 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/AZSys/ArcEncrypted.cs:215 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/DxLib/ArcDX.cs:150 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/elf/ArcAi5Win.cs:119 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:130 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Interheart/ArcFPK.cs:70 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/CatSystem/ArcINT.cs:165 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Kaas/ArcKAAS.cs:85 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Lucifen/ArcLPK.cs:175 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Tactics/ArcLST.cs:65 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) ArcFormats/Nexas/ArcPAC.cs:97 — 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.
  • + 12 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×35
  • Duplicated block (9 lines × 2) ArcFormats/Qlie/Encryption.cs:381 — ArcFormats/Qlie/Encryption.cs:381-389 | ArcFormats/Qlie/Encryption.cs:416-424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) ArcFormats/Majiro/ArcMajiro.cs:177 — ArcFormats/Majiro/ArcMajiro.cs:177-185 | ArcFormats/YuRis/ArcYPF.cs:319-327 — 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 `ArcFormats/Majiro/ArcMajiro.cs:177` 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) ArcFormats/ShiinaRio/ImageMI4.cs:173 — ArcFormats/ShiinaRio/ImageMI4.cs:173-181 | ArcFormats/ShiinaRio/ImageMI4.cs:189-197 — 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 `ArcFormats/ShiinaRio/ImageMI4.cs:173` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) ArcFormats/Strikes/ImageLAG.cs:235 — ArcFormats/Strikes/ImageLAG.cs:235-243 | ArcFormats/Strikes/ImageLAG.cs:250-258 — 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 `ArcFormats/Strikes/ImageLAG.cs:235` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) ArcFormats/Cmvs/ImagePSB.cs:129 — ArcFormats/Cmvs/ImagePSB.cs:129-137 | ArcFormats/Cmvs/ImagePSB.cs:172-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Legacy/KApp/ArcASD.cs:49 — Legacy/KApp/ArcASD.cs:49-57 | Legacy/PineSoft/ArcVoice.cs:58-66 — 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 `Legacy/KApp/ArcASD.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 (9 lines × 2) ArcFormats/FC01/ArcSCXA.cs:30 — ArcFormats/FC01/ArcSCXA.cs:30-38 | ArcFormats/MAGES/ArcARC20.cs:28-36 — 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) ArcFormats/DirectDraw/DxtDecoder.cs:107 — ArcFormats/DirectDraw/DxtDecoder.cs:107-115 | ArcFormats/DirectDraw/DxtDecoder.cs:151-159 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/DirectDraw/DxtDecoder.cs:107` 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) ArcFormats/rUGP/ImageRIP.cs:220 — ArcFormats/rUGP/ImageRIP.cs:220-228 | ArcFormats/rUGP/ImageRIP.cs:247-255 — 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 `ArcFormats/rUGP/ImageRIP.cs:220` 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) ArcFormats/AZSys/ImageCPB.cs:164 — ArcFormats/AZSys/ImageCPB.cs:164-172 | ArcFormats/AZSys/ImageTYP1.cs:159-167 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/AZSys/ImageCPB.cs:164` 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) ArcFormats/MangaGamer/ArcMGPK.cs:85 — ArcFormats/MangaGamer/ArcMGPK.cs:85-93 | ArcFormats/MangaGamer/ArcMGPK.cs:234-242 — 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 `ArcFormats/MangaGamer/ArcMGPK.cs:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) ArcFormats/Kaas/ImageKAAS.cs:260 — ArcFormats/Kaas/ImageKAAS.cs:260-268 | ArcFormats/Kaas/ImageKAAS.cs:311-319 — 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 `ArcFormats/Kaas/ImageKAAS.cs:260` 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) ArcFormats/elf/ArcAi5DAT.cs:66 — ArcFormats/elf/ArcAi5DAT.cs:66-74 | ArcFormats/elf/ArcAi5Win.cs:126-134 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/elf/ArcAi5DAT.cs:66` 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) ArcFormats/Palette/ArcPAK.cs:49 — ArcFormats/Palette/ArcPAK.cs:49-57 | ArcFormats/Palette/ArcPAK2.cs:50-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) ArcFormats/Cmvs/ArcCPZ2.cs:98 — ArcFormats/Cmvs/ArcCPZ2.cs:98-106 | ArcFormats/Cmvs/ArcCPZ3.cs:101-109 — before extracting anything, compare `ArcFormats/Cmvs/ArcCPZ2.cs` and `ArcFormats/Cmvs/ArcCPZ3.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cmvs/ArcCPZ2.cs:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) ArcFormats/Cmvs/AudioMV.cs:130 — ArcFormats/Cmvs/AudioMV.cs:130-138 | ArcFormats/Cmvs/AudioMV2.cs:61-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) ArcFormats/LiveMaker/ImageGAL.cs:474 — ArcFormats/LiveMaker/ImageGAL.cs:474-482 | ArcFormats/LiveMaker/ImageGAL.cs:494-502 — 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 `ArcFormats/LiveMaker/ImageGAL.cs:474` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) ArcFormats/Moonhir/ArcFPK.cs:213 — ArcFormats/Moonhir/ArcFPK.cs:213-221 | ArcFormats/Moonhir/ArcFPK.cs:238-246 — 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 (9 lines × 2) ArcFormats/Primel/Encryption.cs:128 — ArcFormats/Primel/Encryption.cs:128-136 | ArcFormats/Primel/RC6.cs:71-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) ArcFormats/ShiinaRio/WarcEncryption.cs:799 — ArcFormats/ShiinaRio/WarcEncryption.cs:799-807 | ArcFormats/ShiinaRio/WarcEncryption.cs:857-865 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) ArcFormats/ShiinaRio/WarcEncryption.cs:811 — ArcFormats/ShiinaRio/WarcEncryption.cs:811-819 | ArcFormats/ShiinaRio/WarcEncryption.cs:869-877 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) ArcFormats/ShiinaRio/ArcWARC.cs:232 — ArcFormats/ShiinaRio/ArcWARC.cs:232-240 | ArcFormats/ShiinaRio/ArcWARC.cs:257-265 — 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 `ArcFormats/ShiinaRio/ArcWARC.cs:232` 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) Legacy/Aaru/ArcDL1.cs:50 — Legacy/Aaru/ArcDL1.cs:50-58 | Legacy/Aquarium/ArcCPA.cs:47-55 — 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 `Legacy/Aaru/ArcDL1.cs:50` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Legacy/Aquarium/ArcCPA.cs:56` calls `ReadByte` and `Legacy/Aaru/ArcDL1.cs:59` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) Legacy/KApp/ArcASD.cs:193 — Legacy/KApp/ArcASD.cs:193-201 | Legacy/Pias/ArcDAT.cs:210-218 — 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 `Legacy/KApp/ArcASD.cs:193` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) Legacy/Witch/ArcPCD.cs:55 — Legacy/Witch/ArcPCD.cs:55-63 | Legacy/Witch/ArcVBD.cs:44-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Witch/ArcPCD.cs:55` 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.
  • + 10 more in this group — see findings.md.
D17 · Explicit Debt · XxxComment · ×33
  • XxxComment ArcFormats/CatSystem/ImageHG3.cs:316 — // XXX ??? — 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 ArcFormats/Cmvs/ArcPBZ.cs:90 — // XXX — 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 ArcFormats/Entis/EriReader.cs:2070 — // XXX — 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 ArcFormats/MnoViolet/ImageDIF.cs:124 — // XXX — 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 ArcFormats/Cri/AudioADX.cs:216 — output.Write (frame, 0, samples_in_frame * block_align); // XXX convert to byte array — 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 ArcFormats/Cri/ImageXTX.cs:60 — // XXX use some arbitrary "large" value to avoid call to Stream.Length — 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 ArcFormats/GameSystem/AudioADP4.cs:46 — // XXX varies — 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 ArcFormats/Ikura/ImageDRG.cs:86 — // DGD extensions doesn't always mean encrypted contents XXX — 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 ArcFormats/Interheart/ImageBMP.cs:69 — // XXX BMMP08 and BMP16 bitmaps use exactly the same algorithm, just different pixel size — 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 ArcFormats/Leaf/ImagePX.cs:44 — // XXX this format changes significantly from game to game — 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 ArcFormats/LiveMaker/ImageGAL.cs:259 — // XXX only first frame is interpreted. — 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 ArcFormats/LiveMaker/ImageGAL.cs:422 — // XXX only first layer is considered. — 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 ArcFormats/Lz4Stream.cs:187 — // XXX checksum is ignored — 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 ArcFormats/MD5.cs:191 — // XXX m_bit_count is not reset -- this is intentional. — 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 ArcFormats/Maika/ArcMK2.cs:144 — // XXX scrambling might be applicable for 'E1' signatures only — 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 ArcFormats/Primel/Compression.cs:349 — // XXX stream is endless, should be wrapped into LimitStream — 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 ArcFormats/Qlie/ArcQLIE.cs:343 — // XXX add button to query dialog like with CatSystem? — 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 ArcFormats/Suika/ArcSuika.cs:111 — // XXX may not throw exception on invalid 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.
  • XxxComment ArcFormats/Tamamo/ArcPCK.cs:169 — // XXX Senkou no Kishi texture — 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 ArcFormats/TechnoBrain/ImageIPH.cs:70 — // XXX int16@[0x54] is a transparency color or 0xFFFF if image is not transparent — 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 ArcFormats/Unity/AudioFSB5.cs:170 — // XXX unused — 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 ArcFormats/Unity/Texture2D.cs:323 — // XXX conversion performed in-place. — 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 ArcFormats/Vitamin/ImageMFC.cs:80 — // XXX implemented like in reference code, width is expected to be even. — 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 REDACTED:174 — // XXX add GUI widget to select scheme — 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 Experimental/Artemis/ImageIPT.cs:78 — // XXX order by Id? — 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.
  • + 8 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×31
  • Duplicated block (6 lines × 2) ArcFormats/Cmvs/CpzHeader.cs:96 — ArcFormats/Cmvs/CpzHeader.cs:96-101 | ArcFormats/Cmvs/CpzHeader.cs:112-117 — 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 `ArcFormats/Cmvs/CpzHeader.cs:96` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) ArcFormats/Primel/Encryption.cs:231 — ArcFormats/Primel/Encryption.cs:231-236 | ArcFormats/Primel/Encryption.cs:298-303 — 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) ArcFormats/BlackRainbow/ArcGSP.cs:43 — ArcFormats/BlackRainbow/ArcGSP.cs:43-48 | ArcFormats/Ethornell/ArcBGI.cs:133-138 — 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 (6 lines × 2) ArcFormats/MAGES/ArcMPK.cs:58 — ArcFormats/MAGES/ArcMPK.cs:58-63 | ArcFormats/MAGES/ArcMPK.cs:74-79 — 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 `ArcFormats/MAGES/ArcMPK.cs:58` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) ArcFormats/NScripter/ArcNS2.cs:197 — ArcFormats/NScripter/ArcNS2.cs:197-202 | ArcFormats/NScripter/ArcNS2.cs:208-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/NScripter/ArcNS2.cs:197` 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) ArcFormats/Tactics/ArcLST.cs:78 — ArcFormats/Tactics/ArcLST.cs:78-83 | ArcFormats/Tactics/ArcLST.cs:109-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Tactics/ArcLST.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 (6 lines × 2) ArcFormats/Artdink/Ps2ImageUtil.cs:142 — ArcFormats/Artdink/Ps2ImageUtil.cs:142-147 | ArcFormats/Artdink/Ps2ImageUtil.cs:157-162 — 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 `ArcFormats/Artdink/Ps2ImageUtil.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 (6 lines × 2) ArcFormats/GameSystem/ImageBGD.cs:71 — ArcFormats/GameSystem/ImageBGD.cs:71-76 | ArcFormats/GameSystem/ImageBGD.cs:80-85 — 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) ArcFormats/Aoi/ArcBOX.cs:238 — ArcFormats/Aoi/ArcBOX.cs:238-243 | ArcFormats/Mixwill/ArcARC0.cs:54-59 — 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 `ArcFormats/Aoi/ArcBOX.cs:238` 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) ArcFormats/Cyberworks/ImageTINK.cs:326 — ArcFormats/Cyberworks/ImageTINK.cs:326-331 | ArcFormats/Cyberworks/ImageTINK.cs:338-343 — 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 `ArcFormats/Cyberworks/ImageTINK.cs:326` 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) ArcFormats/KiriKiri/CryptAlgorithms.cs:575 — ArcFormats/KiriKiri/CryptAlgorithms.cs:575-580 | ArcFormats/KiriKiri/CryptAlgorithms.cs:591-596 — 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 `ArcFormats/KiriKiri/CryptAlgorithms.cs:575` 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) ArcFormats/BellDa/ArcDAT.cs:66 — ArcFormats/BellDa/ArcDAT.cs:66-71 | Legacy/Aaru/ArcDL1.cs:59-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6 lines × 2) ArcFormats/Cadath/ArcDAF.cs:50 — ArcFormats/Cadath/ArcDAF.cs:50-55 | ArcFormats/Kid/ArcDAT.cs:56-61 — 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 `ArcFormats/Cadath/ArcDAF.cs:50` 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) ArcFormats/Cadath/ArcDAF.cs:51 — ArcFormats/Cadath/ArcDAF.cs:51-56 | ArcFormats/Tanaka/ArcARC0.cs:57-62 — 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 `ArcFormats/Cadath/ArcDAF.cs:51` 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) ArcFormats/Masys/ArcMGD.cs:61 — ArcFormats/Masys/ArcMGD.cs:61-66 | ArcFormats/Masys/ArcMGS.cs:67-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Masys/ArcMGS.cs:65` calls `ReadByte` and `ArcFormats/Masys/ArcMGD.cs:59` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) ArcFormats/Tanaka/ArcWSM.cs:151 — ArcFormats/Tanaka/ArcWSM.cs:151-156 | ArcFormats/Tanaka/ArcWSM.cs:214-219 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Tanaka/ArcWSM.cs:151` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6 lines × 2) Legacy/Clio/ArcPAC.cs:50 — Legacy/Clio/ArcPAC.cs:50-55 | Legacy/DigitalMonkey/ArcDM.cs:58-63 — 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 `Legacy/Clio/ArcPAC.cs:50` 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) Legacy/HillField/ImageIMG.cs:56 — Legacy/HillField/ImageIMG.cs:56-61 | Legacy/PenguinWorks/ImagePXL.cs:50-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) Legacy/Mmfass/ArcSDA.cs:64 — Legacy/Mmfass/ArcSDA.cs:64-69 | Legacy/Zone/ArcPKD.cs:58-63 — 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 (6 lines × 2) ArcFormats/Cyberworks/ImageDATA.cs:170 — ArcFormats/Cyberworks/ImageDATA.cs:170-175 | ArcFormats/Cyberworks/ImageDATA.cs:248-253 — 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 `ArcFormats/Cyberworks/ImageDATA.cs:170` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 2) ArcFormats/DirectDraw/DxtDecoder.cs:175 — ArcFormats/DirectDraw/DxtDecoder.cs:175-180 | ArcFormats/DirectDraw/DxtDecoder.cs:182-187 — 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) ArcFormats/AZSys/ArcEncrypted.cs:290 — ArcFormats/AZSys/ArcEncrypted.cs:290-295 | ArcFormats/AZSys/ArcEncrypted.cs:381-387 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 2) ArcFormats/Kaas/ImageKAAS.cs:242 — ArcFormats/Kaas/ImageKAAS.cs:242-247 | ArcFormats/Kaas/ImageKAAS.cs:297-302 — 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 `ArcFormats/Kaas/ImageKAAS.cs:242` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Kaas/ImageKAAS.cs:248` calls `CopyOverlapped` and `ArcFormats/Kaas/ImageKAAS.cs:303` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) Legacy/Witch/ArcPCD.cs:71 — Legacy/Witch/ArcPCD.cs:71-76 | Legacy/Witch/ArcPCD.cs:79-84 — 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) ArcFormats/ArcARCX.cs:74 — ArcFormats/ArcARCX.cs:74-79 | ArcFormats/DeepBlue/ArcAC.cs:85-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×28
  • Edited copy of a member (12 corresponding lines) ArcFormats/AZSys/FastMersenneTwister.cs:181 — ArcFormats/AZSys/FastMersenneTwister.cs:181-192 | ArcFormats/AZSys/FastMersenneTwister.cs:195-206 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/HSP/ArcDPM.cs:156 — ArcFormats/HSP/ArcDPM.cs:156-167 | ArcFormats/HSP/ArcDPM.cs:170-181 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/YaneSDK/ArcDAT.cs:82 — ArcFormats/YaneSDK/ArcDAT.cs:82-93 | REDACTED:155-168 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Cmvs/AudioMV2.cs:60 — ArcFormats/Cmvs/AudioMV2.cs:60-72 | ArcFormats/Cmvs/AudioMV.cs:129-140 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/KiriKiri/ChainReactionCrypt.cs:61 — ArcFormats/KiriKiri/ChainReactionCrypt.cs:61-72 | ArcFormats/KiriKiri/ChainReactionCrypt.cs:334-345 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Legacy/Adviz/ImageGIZ2.cs:218 — Legacy/Adviz/ImageGIZ2.cs:218-229 | Legacy/Miami/ImageMIA.cs:305-316 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Legacy/Ags32i/ImageGSS.cs:150 — Legacy/Ags32i/ImageGSS.cs:150-161 | Legacy/Ags32i/ImageGSS.cs:164-175 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Unity/ScriptDSM.cs:74 — ArcFormats/Unity/ScriptDSM.cs:74-85 | ArcFormats/Unity/ArcDSM.cs:75-86 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Cmvs/ArcPBZ.cs:114 — ArcFormats/Cmvs/ArcPBZ.cs:114-126 | ArcFormats/Cmvs/ArcCPZ3.cs:78-89 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/DDSystem/ArcDDP.cs:117 — ArcFormats/DDSystem/ArcDDP.cs:117-130 | ArcFormats/SHSystem/ArcHXP.cs:118-129 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Otemoto/ImageMAG.cs:174 — ArcFormats/Otemoto/ImageMAG.cs:174-185 | Legacy/Pearl/ImagePL4.cs:105-117 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Cmvs/ArcCPZ.cs:499 — ArcFormats/Cmvs/ArcCPZ.cs:499-510 | ArcFormats/Cmvs/ArcCPZ.cs:513-524 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Artdink/Ps2ImageUtil.cs:51 — ArcFormats/Artdink/Ps2ImageUtil.cs:51-62 | ArcFormats/Artdink/Ps2ImageUtil.cs:156-167 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Lilim/ArcABM.cs:381 — ArcFormats/Lilim/ArcABM.cs:381-394 | Legacy/DigitalMonkey/ImagePKT.cs:146-157 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Legacy/RedZone/ScriptQDO.cs:47 — Legacy/RedZone/ScriptQDO.cs:47-58 | Legacy/RedZone/ScriptQDO.cs:61-72 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/FlyingShine/ArcPD.cs:196 — ArcFormats/FlyingShine/ArcPD.cs:196-207 | ArcFormats/Will/ArcPulltop.cs:209-222 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Crowd/ImageCWL.cs:84 — ArcFormats/Crowd/ImageCWL.cs:84-95 | ArcFormats/Crowd/ImageZBM.cs:43-57 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/ExeFile.cs:350 — ArcFormats/ExeFile.cs:350-361 | ArcFormats/ExeFile.cs:364-375 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Eushully/ImageAGF.cs:205 — ArcFormats/Eushully/ImageAGF.cs:205-216 | ArcFormats/Eushully/ImageAGF.cs:219-230 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) GameRes/ImageTIFF.cs:323 — GameRes/ImageTIFF.cs:323-334 | GameRes/ImageTIFF.cs:337-349 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/KiriKiri/CryptAlgorithms.cs:1349 — ArcFormats/KiriKiri/CryptAlgorithms.cs:1349-1360 | ArcFormats/KiriKiri/CryptAlgorithms.cs:1363-1374 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Entis/EriReader.cs:1297 — ArcFormats/Entis/EriReader.cs:1297-1312 | ArcFormats/Entis/EriReader.cs:1411-1422 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Marble/AudioWADY.cs:125 — ArcFormats/Marble/AudioWADY.cs:125-136 | ArcFormats/Marble/AudioWADY.cs:139-150 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/JamCreation/ImageDPO.cs:174 — ArcFormats/JamCreation/ImageDPO.cs:174-185 | Experimental/Artemis/ImageIPT.cs:198-209 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) ArcFormats/Littlewitch/ArcDAT.cs:301 — ArcFormats/Littlewitch/ArcDAT.cs:301-312 | GameRes/Utility.cs:435-446 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 3 more in this group — see findings.md.
GD1 · Unfinished & placeholder code · Unfinished stub · ×28
  • Unfinished stub — throws NotImplementedException ArcFormats/Ice/ScriptISD.cs:53 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Ps1/ImageTIM.cs:191 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Psp/ArcGim.cs:230 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException REDACTED:413 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Gss/ArcARC.cs:139 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Gss/ArcARC.cs:436 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Ikura/ImageTAN.cs:165 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/KiriKiri/HxCrypt.cs:301 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/KiriKiri/HxCryptLite.cs:104 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/rUGP/ArcRIO.cs:597 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/rUGP/ArcRIO.cs:607 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/rUGP/ArcRIO.cs:622 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Leaf/ImagePX.cs:323 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/ShiinaRio/WarcEncryption.cs:1347 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/ShiinaRio/WarcEncryption.cs:1380 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Sviu/AudioKPV.cs:95 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Sviu/AudioKPV.cs:134 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Unity/ArcUnityFS.cs:161 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Entis/EriReader.cs:769 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/CatSystem/ImageHG3.cs:104 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/KiriKiri/WidgetXP3.xaml.cs:46 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException REDACTED:414 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException GameRes/ScriptText.cs:78 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException GameRes/ScriptText.cs:83 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException GUI/SettingsWindow.xaml.cs:386 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • + 3 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×24
  • Edited copy of a member (7 corresponding lines) ArcFormats/Kaguya/ArcPLT.cs:96 — ArcFormats/Kaguya/ArcPLT.cs:96-102 | ArcFormats/Kaguya/ArcANM.cs:231-237 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/KScript/ImageKGP.cs:82 — ArcFormats/KScript/ImageKGP.cs:82-88 | ArcFormats/Ikura/ImageGGP.cs:80-86 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/Qlie/Encryption.cs:104 — ArcFormats/Qlie/Encryption.cs:104-110 | ArcFormats/Qlie/Encryption.cs:158-164 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/Lilim/ImageIMG.cs:34 — ArcFormats/Lilim/ImageIMG.cs:34-41 | ArcFormats/ImagePSM.cs:45-51 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/Nekopack/ArcNEKO3.cs:126 — ArcFormats/Nekopack/ArcNEKO3.cs:126-132 | ArcFormats/Nonono/ArcNPF.cs:129-137 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/RealLive/ArcSCENE.cs:218 — ArcFormats/RealLive/ArcSCENE.cs:218-224 | ArcFormats/Marble/ArcMBL.cs:198-204 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/BlackRainbow/ImageBMZ.cs:67 — ArcFormats/BlackRainbow/ImageBMZ.cs:67-73 | ArcFormats/AdvRun/ImagePIZ.cs:59-66 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/Crowd/ImageCRZ.cs:99 — ArcFormats/Crowd/ImageCRZ.cs:99-105 | Legacy/System21/ImageTEX.cs:69-76 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) GUI/Shell.cs:377 — GUI/Shell.cs:377-388 | GUI/Shell.cs:391-397 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Legacy/Regrips/ImagePRG.cs:73 — Legacy/Regrips/ImagePRG.cs:73-80 | Legacy/Saiki/ImageJPX.cs:107-113 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/BeF/ImageALO.cs:40 — ArcFormats/BeF/ImageALO.cs:40-48 | Legacy/Brownie/ImageNGW.cs:40-46 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/NScripter/WidgetNSA.xaml.cs:26 — ArcFormats/NScripter/WidgetNSA.xaml.cs:26-32 | ArcFormats/Majiro/WidgetRCT.xaml.cs:25-31 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/Foster/ImageC24.cs:49 — ArcFormats/Foster/ImageC24.cs:49-55 | ArcFormats/Foster/ImageC25.cs:44-50 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/Leaf/ImagePX.cs:135 — ArcFormats/Leaf/ImagePX.cs:135-141 | Legacy/MayBeSoft/ImageHHP.cs:51-57 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/ClickTeam/ArcMF.cs:92 — ArcFormats/ClickTeam/ArcMF.cs:92-98 | ArcFormats/Mugi/ArcBIN.cs:86-92 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/Artemis/ArcPFS.cs:155 — ArcFormats/Artemis/ArcPFS.cs:155-161 | Legacy/KApp/ArcCGD.cs:86-92 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/RealLive/ImageG00.cs:79 — ArcFormats/RealLive/ImageG00.cs:79-85 | ArcFormats/RealLive/ImagePDT.cs:65-71 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) GameRes/ImageJPEG.cs:60 — GameRes/ImageJPEG.cs:60-66 | GameRes/ImageTIFF.cs:51-57 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/Leaf/ArcLAC.cs:74 — ArcFormats/Leaf/ArcLAC.cs:74-82 | ArcFormats/Taskforce/ArcDAT.cs:70-76 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/SimpleEncryption.cs:85 — ArcFormats/SimpleEncryption.cs:85-91 | Legacy/Pias/EncryptedGraphDat.cs:271-277 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/Selene/WidgetKCAP.xaml.cs:16 — ArcFormats/Selene/WidgetKCAP.xaml.cs:16-23 | ArcFormats/Marble/WidgetMBL.xaml.cs:15-21 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/SimpleEncryption.cs:65 — ArcFormats/SimpleEncryption.cs:65-71 | ArcFormats/Selene/ArcKCAP.cs:247-253 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/Bruns/ImageEENC.cs:142 — ArcFormats/Bruns/ImageEENC.cs:142-148 | ArcFormats/VnEngine/ArcAXR.cs:159-165 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) ArcFormats/ScrPlayer/ImageIMG.cs:435 — ArcFormats/ScrPlayer/ImageIMG.cs:435-441 | ArcFormats/ScrPlayer/ImageI.cs:79-88 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×23
  • Duplicated block (10 lines × 2) ArcFormats/WildBug/ArcWBP.cs:106 — ArcFormats/WildBug/ArcWBP.cs:106-115 | ArcFormats/WildBug/ArcWBP.cs:130-139 — 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 (10 lines × 2) ArcFormats/Unity/ArcDSM.cs:77 — ArcFormats/Unity/ArcDSM.cs:77-86 | ArcFormats/Unity/ScriptDSM.cs:76-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Unity/ArcDSM.cs:77` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) ArcFormats/ScrPlayer/ImageI.cs:139 — ArcFormats/ScrPlayer/ImageI.cs:139-148 | ArcFormats/ScrPlayer/ImageI.cs:197-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/ScrPlayer/ImageI.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.
  • Duplicated block (10 lines × 2) ArcFormats/ShiinaRio/WarcEncryption.cs:911 — ArcFormats/ShiinaRio/WarcEncryption.cs:911-920 | ArcFormats/ShiinaRio/WarcEncryption.cs:970-979 — 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 `ArcFormats/ShiinaRio/WarcEncryption.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. 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) ArcFormats/Entis/EriReader.cs:1185 — ArcFormats/Entis/EriReader.cs:1185-1194 | ArcFormats/Entis/EriReader.cs:1211-1220 — 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 `ArcFormats/Entis/EriReader.cs:1185` 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) ArcFormats/Crowd/ImageCWL.cs:100 — ArcFormats/Crowd/ImageCWL.cs:100-109 | ArcFormats/Crowd/ImageZBM.cs:62-71 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Crowd/ImageCWL.cs:100` 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) ArcFormats/KiriKiri/ImageTLG.cs:898 — ArcFormats/KiriKiri/ImageTLG.cs:898-907 | ArcFormats/KiriKiri/ImageTLG.cs:947-956 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) ArcFormats/KiriKiri/ImageTLG.cs:1014 — ArcFormats/KiriKiri/ImageTLG.cs:1014-1023 | ArcFormats/KiriKiri/ImageTLG.cs:1063-1072 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Legacy/Mina/ArcPAK.cs:58 — Legacy/Mina/ArcPAK.cs:58-67 | Legacy/Mina/ArcPAK.cs:175-184 — 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 `Legacy/Mina/ArcPAK.cs:58` 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 (10 lines × 2) ArcFormats/ShiinaRio/WarcEncryption.cs:942 — ArcFormats/ShiinaRio/WarcEncryption.cs:942-951 | ArcFormats/ShiinaRio/WarcEncryption.cs:1122-1131 — 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 `ArcFormats/ShiinaRio/WarcEncryption.cs:942` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) ArcFormats/Escude/ArcBIN.cs:90 — ArcFormats/Escude/ArcBIN.cs:90-99 | ArcFormats/Escude/ArcBIN.cs:126-135 — 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 `ArcFormats/Escude/ArcBIN.cs:90` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) ArcFormats/SysD/ArcDPK.cs:57 — ArcFormats/SysD/ArcDPK.cs:57-66 | REDACTED:73-82 — 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 `ArcFormats/SysD/ArcDPK.cs:57` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) ArcFormats/Tanaka/ArcARC0.cs:49 — ArcFormats/Tanaka/ArcARC0.cs:49-58 | ArcFormats/Tanaka/ArcBMX.cs:48-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Tanaka/ArcARC0.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. 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) Legacy/Gsx/ImageK4.cs:199 — Legacy/Gsx/ImageK4.cs:199-208 | Legacy/Gsx/ImageK4.cs:240-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 (10 lines × 2) Legacy/Eve/ArcGM.cs:71 — Legacy/Eve/ArcGM.cs:71-80 | Legacy/Kasane/ArcAR2.cs:71-80 — 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 `Legacy/Eve/ArcGM.cs:71` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) ArcFormats/Cyberworks/ImageDATA.cs:191 — ArcFormats/Cyberworks/ImageDATA.cs:191-200 | ArcFormats/Cyberworks/ImageDATA.cs:234-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.
  • Duplicated block (10 lines × 2) ArcFormats/Banana/ImageMAG.cs:118 — ArcFormats/Banana/ImageMAG.cs:118-127 | ArcFormats/Tail/ImageCFP.cs:144-153 — 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 `ArcFormats/Banana/ImageMAG.cs:118` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 2) ArcFormats/BitStream.cs:94 — ArcFormats/BitStream.cs:94-103 | ArcFormats/RiddleSoft/ImageGCP.cs:175-184 — 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 `ArcFormats/BitStream.cs:94` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/BitStream.cs:105` calls `GetNextBit`, `GetBits` and `ArcFormats/RiddleSoft/ImageGCP.cs:185` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) ArcFormats/Kaguya/ArcKaguya.cs:107 — ArcFormats/Kaguya/ArcKaguya.cs:107-116 | ArcFormats/Kaguya/ArcKaguya.cs:139-148 — 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 `ArcFormats/Kaguya/ArcKaguya.cs:107` 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 (10 lines × 2) ArcFormats/AnimeGameSystem/ImageAinos.cs:181 — ArcFormats/AnimeGameSystem/ImageAinos.cs:181-190 | ArcFormats/AnimeGameSystem/ImageAinos.cs:238-247 — 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 `ArcFormats/AnimeGameSystem/ImageAinos.cs:181` 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) ArcFormats/Circus/ImageCRX.cs:234 — ArcFormats/Circus/ImageCRX.cs:234-243 | ArcFormats/Circus/ImageCRX.cs:467-477 — 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 `ArcFormats/Circus/ImageCRX.cs:234` 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) ArcFormats/Pandora/ImageXL24.cs:47 — ArcFormats/Pandora/ImageXL24.cs:47-56 | ArcFormats/ShiinaRio/ImageMI4.cs:42-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) ArcFormats/AnimeGameSystem/ImageAinos.cs:287 — ArcFormats/AnimeGameSystem/ImageAinos.cs:287-296 | ArcFormats/ShiinaRio/ImageS25.cs:377-386 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D17 · Explicit Debt · DeadPreprocessorBranch · ×22
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:21 — #if EXPORT_GPPG — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:585 — #if EXPORT_GPPG — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:608 — #if EXPORT_GPPG — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:670 — #if EXPORT_GPPG — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:734 — #if EXPORT_GPPG — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:802 — #if EXPORT_GPPG — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:832 — #if EXPORT_GPPG — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:214 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:227 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:231 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:269 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:291 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:394 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:408 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:415 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:419 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:437 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:442 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:454 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch Experimental/Artemis/ShiftReduceParserCode.cs:476 — #if TRACE_ACTIONS — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch SchemeTool/Program.cs:21 — #if false — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch SchemeTool/Program.cs:64 — #else — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×22
  • Edited copy of a member (6 corresponding lines) ArcFormats/Bishop/ImageGSA.cs:288 — ArcFormats/Bishop/ImageGSA.cs:288-293 | ArcFormats/Bishop/ImageGSA.cs:296-302 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) GameRes/Utility.cs:240 — GameRes/Utility.cs:240-245 | GameRes/Utility.cs:356-361 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/ActiveSoft/ImageEDT.cs:296 — ArcFormats/ActiveSoft/ImageEDT.cs:296-301 | ArcFormats/Majiro/ImageRC8.cs:62-69 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/Seraphim/ArcCP3.cs:90 — ArcFormats/Seraphim/ArcCP3.cs:90-95 | ArcFormats/Kaguya/ArcANM.cs:166-171 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Legacy/Pisckiss/Image1.cs:75 — Legacy/Pisckiss/Image1.cs:75-80 | Legacy/hmp/ImageMBP.cs:59-64 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/Crc32.cs:57 — ArcFormats/Crc32.cs:57-62 | GameRes/Checksum.cs:67-72 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/Adobe/ArcAIR.cs:94 — ArcFormats/Adobe/ArcAIR.cs:94-99 | ArcFormats/CatSystem/ArcZT.cs:112-118 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/TamaSoft/ImageSUR.cs:53 — ArcFormats/TamaSoft/ImageSUR.cs:53-58 | ArcFormats/Emic/ImageMWP.cs:58-64 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/Unity/ScriptDSM.cs:65 — ArcFormats/Unity/ScriptDSM.cs:65-71 | ArcFormats/Unity/ArcDSM.cs:91-96 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/Nonono/ArcNPF.cs:175 — ArcFormats/Nonono/ArcNPF.cs:175-180 | ArcFormats/Escude/ArcBIN.cs:150-155 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/Interheart/ImageHMP.cs:52 — ArcFormats/Interheart/ImageHMP.cs:52-57 | ArcFormats/NipponIchi/ImageNMT.cs:27-33 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/FlyingShine/ArcPD.cs:87 — ArcFormats/FlyingShine/ArcPD.cs:87-92 | Legacy/Factor/ArcRES.cs:93-98 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/Kaguya/ArcPL10.cs:125 — ArcFormats/Kaguya/ArcPL10.cs:125-130 | ArcFormats/Kaguya/ArcAN21.cs:143-148 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/Xuse/ArcXARC.cs:84 — ArcFormats/Xuse/ArcXARC.cs:84-90 | ArcFormats/Will/ArcWILL.cs:139-144 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/FC01/ArcMCA.cs:120 — ArcFormats/FC01/ArcMCA.cs:120-125 | ArcFormats/FC01/ImageMCG.cs:138-143 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/NScripter/ArcNS2.cs:156 — ArcFormats/NScripter/ArcNS2.cs:156-161 | ArcFormats/NScripter/ArcNSA.cs:223-228 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/AdvSys/ImageGWD.cs:204 — ArcFormats/AdvSys/ImageGWD.cs:204-209 | Legacy/Types/ImageTPGF.cs:207-212 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/HuneX/ImageCBG.cs:167 — ArcFormats/HuneX/ImageCBG.cs:167-173 | ArcFormats/Ethornell/ImageCBG.cs:203-208 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/RealLive/ArcSCENE.cs:227 — ArcFormats/RealLive/ArcSCENE.cs:227-232 | ArcFormats/MangaGamer/ArcMGPK.cs:195-200 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Legacy/Gaia/ImageJPG.cs:39 — Legacy/Gaia/ImageJPG.cs:39-44 | Legacy/Mina/ImageMD.cs:40-45 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/Leaf/ArcLEAF.cs:202 — ArcFormats/Leaf/ArcLEAF.cs:202-207 | ArcFormats/Tamamo/ArcPCK.cs:259-264 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) ArcFormats/NitroPlus/ArcNPA.cs:642 — ArcFormats/NitroPlus/ArcNPA.cs:642-647 | ArcFormats/NitroPlus/ArcSteinsGate.cs:268-273 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×22
  • Duplicated block (12 lines × 2) ArcFormats/Ffa/AudioWA1.cs:215 — ArcFormats/Ffa/AudioWA1.cs:215-226 | ArcFormats/Ffa/AudioWA1.cs:502-513 — 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 `ArcFormats/Ffa/AudioWA1.cs:215` 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) ArcFormats/Unity/Bc7Decoder.cs:154 — ArcFormats/Unity/Bc7Decoder.cs:154-165 | ArcFormats/Unity/Bc7Decoder.cs:205-216 — 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 (12 lines × 2) ArcFormats/Entis/EriReader.cs:1744 — ArcFormats/Entis/EriReader.cs:1744-1755 | ArcFormats/Entis/EriReader.cs:1793-1804 — 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 (12 lines × 2) Legacy/Nekotaro/ImageNCG.cs:149 — Legacy/Nekotaro/ImageNCG.cs:149-160 | Legacy/Nekotaro/ImageNCG.cs:164-175 — 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 `Legacy/Nekotaro/ImageNCG.cs:149` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 2) Legacy/Discovery/ArcDAT.cs:91 — Legacy/Discovery/ArcDAT.cs:91-102 | Legacy/Discovery/ArcDAT.cs:126-137 — 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 `Legacy/Discovery/ArcDAT.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) ArcFormats/ScrPlayer/ImageI.cs:146 — ArcFormats/ScrPlayer/ImageI.cs:146-157 | ArcFormats/ScrPlayer/ImageIMG.cs:111-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/ScrPlayer/ImageI.cs:146` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) ArcFormats/TechnoBrain/AudioWAPE.cs:91 — ArcFormats/TechnoBrain/AudioWAPE.cs:91-102 | ArcFormats/TechnoBrain/AudioWAPE.cs:111-122 — 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 `ArcFormats/TechnoBrain/AudioWAPE.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. 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) ArcFormats/Entis/EriReader.cs:1094 — ArcFormats/Entis/EriReader.cs:1094-1105 | ArcFormats/Entis/EriReader.cs:1180-1191 — 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 `ArcFormats/Entis/EriReader.cs:1094` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) ArcFormats/Entis/EriReader.cs:1119 — ArcFormats/Entis/EriReader.cs:1119-1130 | ArcFormats/Entis/EriReader.cs:1206-1217 — 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 `ArcFormats/Entis/EriReader.cs:1119` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) ArcFormats/PkWare/ArcZIP.cs:45 — ArcFormats/PkWare/ArcZIP.cs:45-56 | ArcFormats/VnMaker/ArcZIP.cs:17-28 — `ArcFormats/PkWare/ArcZIP.cs` and `ArcFormats/VnMaker/ArcZIP.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 30 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) ArcFormats/Kaguya/ArcAN21.cs:100 — ArcFormats/Kaguya/ArcAN21.cs:100-111 | ArcFormats/Kaguya/ArcPL10.cs:82-93 — before extracting anything, compare `ArcFormats/Kaguya/ArcAN21.cs` and `ArcFormats/Kaguya/ArcPL10.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Kaguya/ArcAN21.cs:100` 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 (12 lines × 2) ArcFormats/Primel/ImageGBC.cs:109 — ArcFormats/Primel/ImageGBC.cs:109-120 | ArcFormats/Primel/ImageGBC.cs:161-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 `ArcFormats/Primel/ImageGBC.cs:109` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) ArcFormats/Succubus/ImageGH.cs:184 — ArcFormats/Succubus/ImageGH.cs:184-195 | ArcFormats/Succubus/ImageGH.cs:254-265 — 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 `ArcFormats/Succubus/ImageGH.cs:184` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) ArcFormats/ShiinaRio/ImageMI4.cs:212 — ArcFormats/ShiinaRio/ImageMI4.cs:212-223 | ArcFormats/ShiinaRio/ImageMI4.cs:302-313 — 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 `ArcFormats/ShiinaRio/ImageMI4.cs:212` 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) ArcFormats/ShiinaRio/ImageS25.cs:341 — ArcFormats/ShiinaRio/ImageS25.cs:341-352 | ArcFormats/ShiinaRio/ImageS25.cs:354-365 — 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 (12 lines × 2) Legacy/Aaru/ArcFL2.cs:65 — Legacy/Aaru/ArcFL2.cs:65-76 | Legacy/Aaru/ArcFL3.cs:65-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Aaru/ArcFL2.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Legacy/NAUTS/ArcMSP.cs:50 — Legacy/NAUTS/ArcMSP.cs:50-61 | Legacy/NAUTS/ArcTTP.cs:69-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/NAUTS/ArcMSP.cs:50` 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) ArcFormats/rUGP/ImageRIP.cs:322 — ArcFormats/rUGP/ImageRIP.cs:322-333 | ArcFormats/rUGP/ImageRIP.cs:335-346 — 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 `ArcFormats/rUGP/ImageRIP.cs:322` 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) ArcFormats/Aoi/ArcVFS.cs:70 — ArcFormats/Aoi/ArcVFS.cs:70-81 | ArcFormats/Aoi/ArcVFS.cs:101-112 — 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 `ArcFormats/Aoi/ArcVFS.cs:70` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) Legacy/Tigerman/ArcPAC.cs:52 — Legacy/Tigerman/ArcPAC.cs:52-63 | Legacy/Uran/ArcPHS.cs:46-57 — before extracting anything, compare `Legacy/Tigerman/ArcPAC.cs` and `Legacy/Uran/ArcPHS.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Tigerman/ArcPAC.cs:52` 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) ArcFormats/CaramelBox/ArcARC4.cs:354 — ArcFormats/CaramelBox/ArcARC4.cs:354-365 | ArcFormats/NitroPlus/ArcNPK.cs:606-617 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) ArcFormats/KiriKiri/ArcXP3.cs:899 — ArcFormats/KiriKiri/ArcXP3.cs:899-910 | Legacy/Pinky/ArcA5R.cs:277-288 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D3 · God Classes · FileTooLong · ×21
  • FileTooLong: Giga/ArcALL.cs Legacy/Giga/ArcALL.cs — FileTooLong — 2014 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1514 over it, 4.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Entis/EriReader.cs ArcFormats/Entis/EriReader.cs — FileTooLong — 1688 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1188 over it, 3.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Macromedia/Palettes.cs ArcFormats/Macromedia/Palettes.cs — FileTooLong — 1289 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 789 over it, 2.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: KiriKiri/ImageTLG.cs ArcFormats/KiriKiri/ImageTLG.cs — FileTooLong — 1093 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 593 over it, 2.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: rUGP/ArcRIO.cs ArcFormats/rUGP/ArcRIO.cs — FileTooLong — 958 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 458 over it, 1.92× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: KiriKiri/CryptAlgorithms.cs ArcFormats/KiriKiri/CryptAlgorithms.cs — FileTooLong — 904 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 404 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Koei/YkTables.cs Legacy/Koei/YkTables.cs — FileTooLong — 892 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 392 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: GUI/MainWindow.xaml.cs GUI/MainWindow.xaml.cs — FileTooLong — 849 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 349 over it, 1.70× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ShiinaRio/WarcEncryption.cs ArcFormats/ShiinaRio/WarcEncryption.cs — FileTooLong — 847 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 347 over it, 1.69× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Cri/AudioHCA.cs ArcFormats/Cri/AudioHCA.cs — FileTooLong — 843 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 343 over it, 1.69× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: WildBug/ImageWBM.cs ArcFormats/WildBug/ImageWBM.cs — FileTooLong — 796 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 296 over it, 1.59× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Circus/AudioPCM.cs ArcFormats/Circus/AudioPCM.cs — FileTooLong — 648 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 148 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: KiriKiri/ArcXP3.cs ArcFormats/KiriKiri/ArcXP3.cs — FileTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 117 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: rUGP/ImageRIP.cs ArcFormats/rUGP/ImageRIP.cs — FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 102 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: KiriKiri/HxCrypt.cs ArcFormats/KiriKiri/HxCrypt.cs — FileTooLong — 594 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 94 over it, 1.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Cmvs/ImagePB3.cs ArcFormats/Cmvs/ImagePB3.cs — FileTooLong — 593 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 93 over it, 1.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Emote/ArcPSB.cs ArcFormats/Emote/ArcPSB.cs — FileTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 75 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Entis/MioDecoder.cs ArcFormats/Entis/MioDecoder.cs — FileTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 68 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Macromedia/DirectorFile.cs ArcFormats/Macromedia/DirectorFile.cs — FileTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 44 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Nekotaro/ImageGCmp.cs Legacy/Nekotaro/ImageGCmp.cs — FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 20 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Ethornell/ImageCBG.cs ArcFormats/Ethornell/ImageCBG.cs — FileTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2 over it, 1.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D3 · God Classes · MethodTooLong · ×20
  • MethodTooLong: PcmDecoder.sub_411AB0 ArcFormats/Circus/AudioPCM.cs:266 — MethodTooLong — sub_411AB0 runs 202 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 102 over it, 2.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Mai2Reader.UnpackPlane Legacy/Izumi/ImageMAI2.cs:139 — MethodTooLong — UnpackPlane runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Xp3Opener.TryOpen ArcFormats/KiriKiri/ArcXP3.cs:105 — MethodTooLong — TryOpen runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TlgFormat.TVPTLG6DecodeLineGeneric ArcFormats/KiriKiri/ImageTLG.cs:634 — MethodTooLong — TVPTLG6DecodeLineGeneric runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Reader.UnpackV2 ArcFormats/Ffa/ImagePT1.cs:178 — MethodTooLong — UnpackV2 runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SjTransform.DoTransform ArcFormats/StudioJikkenshitsu/SjTransform.cs:183 — MethodTooLong — DoTransform runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: GdtReader.UnpackDouble ArcFormats/CsWare/ImageGDT.cs:141 — MethodTooLong — UnpackDouble runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: KlzFormat.LzhStreamDecode ArcFormats/Kid/ImageKLZ.cs:54 — MethodTooLong — LzhStreamDecode runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: NemesisDecodeContext.DecodeNemesisCodeBytes ArcFormats/Entis/ErisaNemesis.cs:71 — MethodTooLong — DecodeNemesisCodeBytes runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MioDecoder.DecodeSoundDCT ArcFormats/Entis/MioDecoder.cs:292 — MethodTooLong — DecodeSoundDCT runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Reader.sub_4225EA ArcFormats/Ffa/ImagePT1.cs:399 — MethodTooLong — sub_4225EA runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Xp3Opener.Create ArcFormats/KiriKiri/ArcXP3.cs:467 — MethodTooLong — Create runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: NcgReader.Unpack Legacy/Nekotaro/ImageNCG.cs:92 — MethodTooLong — Unpack runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LsdOpener.UnpackH ArcFormats/Gss/ArcARC.cs:275 — MethodTooLong — UnpackH runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MioDecoder.DecodeSoundDCT_MSS ArcFormats/Entis/MioDecoder.cs:585 — MethodTooLong — DecodeSoundDCT_MSS runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Reader.Unpack ArcFormats/uGOS/ImageBMP.cs:133 — MethodTooLong — Unpack runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: PicReader.DecodeBlock ArcFormats/Softpal/ImagePIC.cs:275 — MethodTooLong — DecodeBlock runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Wa1Reader.UnpackV4 ArcFormats/Ffa/AudioWA1.cs:123 — MethodTooLong — UnpackV4 runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Wa1Reader.UnpackV12 ArcFormats/Ffa/AudioWA1.cs:403 — MethodTooLong — UnpackV12 runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: EriReader.DecodeLosslessImage ArcFormats/Entis/EriReader.cs:435 — MethodTooLong — DecodeLosslessImage runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×20
  • Duplicated block (11 lines × 2) ArcFormats/NScripter/ArcNSA.cs:303 — ArcFormats/NScripter/ArcNSA.cs:303-313 | ArcFormats/NScripter/ArcSAR.cs:126-136 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/NScripter/ArcNSA.cs:303` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/NScripter/ArcNSA.cs:314` calls `Write` and `ArcFormats/NScripter/ArcSAR.cs:137` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) ArcFormats/Primel/ImageGBC.cs:135 — ArcFormats/Primel/ImageGBC.cs:135-145 | ArcFormats/Primel/ImageGBC.cs:181-191 — 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 `ArcFormats/Primel/ImageGBC.cs:135` 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 (11 lines × 2) ArcFormats/FlyingShine/ArcPD.cs:160 — ArcFormats/FlyingShine/ArcPD.cs:160-170 | ArcFormats/StudioEgo/ArcEGO.cs:112-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. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/FlyingShine/ArcPD.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 (11 lines × 2) ArcFormats/Malie/MalieEncryption.cs:136 — ArcFormats/Malie/MalieEncryption.cs:136-146 | ArcFormats/NScripter/EncryptedStream.cs:63-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Malie/MalieEncryption.cs:136` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 2) ArcFormats/Ivory/ImageSG.cs:244 — ArcFormats/Ivory/ImageSG.cs:244-254 | ArcFormats/Ivory/ImageSG.cs:352-362 — 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 `ArcFormats/Ivory/ImageSG.cs:244` 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) ArcFormats/Leaf/AudioG.cs:163 — ArcFormats/Leaf/AudioG.cs:163-173 | ArcFormats/Leaf/AudioG.cs:212-222 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Leaf/AudioG.cs:163` 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 (11 lines × 2) ArcFormats/Winters/ArcCFP.cs:47 — ArcFormats/Winters/ArcCFP.cs:47-57 | ArcFormats/Winters/ArcDAT.cs:47-57 — before extracting anything, compare `ArcFormats/Winters/ArcCFP.cs` and `ArcFormats/Winters/ArcDAT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Winters/ArcCFP.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. 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) Legacy/Mink/ImageFD.cs:194 — Legacy/Mink/ImageFD.cs:194-204 | Legacy/Mink/ImageFD.cs:245-255 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) ArcFormats/WebPCodec.cs:52 — ArcFormats/WebPCodec.cs:52-62 | Experimental/WebP/ImageWEBP.cs:194-204 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) ArcFormats/Qlie/Encryption.cs:402 — ArcFormats/Qlie/Encryption.cs:402-412 | ArcFormats/Qlie/Encryption.cs:441-451 — 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 `ArcFormats/Qlie/Encryption.cs:402` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) ArcFormats/Dac/ImageDGC.cs:144 — ArcFormats/Dac/ImageDGC.cs:144-154 | ArcFormats/Dac/ImageDGC.cs:184-194 — 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 `ArcFormats/Dac/ImageDGC.cs:144` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Dac/ImageDGC.cs:142` calls `UnpackLine16` and `ArcFormats/Dac/ImageDGC.cs:183` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) Legacy/Dall/ArcPEL.cs:57 — Legacy/Dall/ArcPEL.cs:57-67 | Legacy/Neon/ArcAR2.cs:72-82 — 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 `Legacy/Dall/ArcPEL.cs:57` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) ArcFormats/KiriKiri/HxCrypt.cs:641 — ArcFormats/KiriKiri/HxCrypt.cs:641-651 | ArcFormats/KiriKiri/HxCrypt.cs:684-694 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) ArcFormats/ScenePlayer/ArcPMA.cs:48 — ArcFormats/ScenePlayer/ArcPMA.cs:48-58 | ArcFormats/ScenePlayer/ArcPMX.cs:46-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/ScenePlayer/ArcPMA.cs:48` 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 (11 lines × 2) ArcFormats/Softpal/ArcVAFS.cs:102 — ArcFormats/Softpal/ArcVAFS.cs:102-113 | Legacy/Witch/ArcARC.cs:70-80 — 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 `ArcFormats/Softpal/ArcVAFS.cs:102` 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) ArcFormats/NScripter/ArcNSA.cs:272 — ArcFormats/NScripter/ArcNSA.cs:272-282 | ArcFormats/NScripter/ArcSAR.cs:104-114 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/NScripter/ArcNSA.cs:272` 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) ArcFormats/Unity/Texture2D.cs:115 — ArcFormats/Unity/Texture2D.cs:115-125 | ArcFormats/Unity/Texture2D.cs:143-153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Unity/Texture2D.cs:127` calls `ReadInt32` and `ArcFormats/Unity/Texture2D.cs:154` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) ArcFormats/Risa/ImageSYG.cs:72 — ArcFormats/Risa/ImageSYG.cs:72-82 | Legacy/Nabe/ImageYPF.cs:73-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (11 lines × 2) ArcFormats/Entis/EriReader.cs:1692 — ArcFormats/Entis/EriReader.cs:1692-1702 | ArcFormats/Entis/EriReader.cs:1719-1729 — 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 `ArcFormats/Entis/EriReader.cs:1719` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) ArcFormats/ScrPlayer/ImageIMG.cs:44 — ArcFormats/ScrPlayer/ImageIMG.cs:44-54 | Legacy/Aaru/ImageBM2.cs:42-54 — 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.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×19
  • Edited copy of a member (11 corresponding lines) ArcFormats/KiriKiri/ImageTLG.cs:521 — ArcFormats/KiriKiri/ImageTLG.cs:521-536 | ArcFormats/KiriKiri/ImageTLG.cs:540-556 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/Pandora/ArcPBX.cs:69 — ArcFormats/Pandora/ArcPBX.cs:69-87 | ArcFormats/Favorite/ArcFVP.cs:76-86 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/ArcCommon.cs:267 — ArcFormats/ArcCommon.cs:267-277 | ArcFormats/ArcCommon.cs:298-308 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/DxLib/DxKey.cs:148 — ArcFormats/DxLib/DxKey.cs:148-158 | ArcFormats/DxLib/DxKey.cs:190-200 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/aNCHOR/Blowfish.cs:238 — ArcFormats/aNCHOR/Blowfish.cs:238-248 | ArcFormats/Blowfish.cs:467-477 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/Ikura/ImageGGA.cs:46 — ArcFormats/Ikura/ImageGGA.cs:46-61 | ArcFormats/Ikura/ImageGGS.cs:40-50 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/Kaguya/ImageAO.cs:72 — ArcFormats/Kaguya/ImageAO.cs:72-84 | ArcFormats/Kaguya/ImageAP.cs:83-93 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/Illusion/ImageEMA.cs:47 — ArcFormats/Illusion/ImageEMA.cs:47-57 | ArcFormats/Illusion/ImageEMA.cs:93-103 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/Cyberworks/ArcDAT.cs:681 — ArcFormats/Cyberworks/ArcDAT.cs:681-691 | ArcFormats/Cyberworks/ArcDAT.cs:766-776 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/KiriKiri/CryptAlgorithms.cs:852 — ArcFormats/KiriKiri/CryptAlgorithms.cs:852-862 | ArcFormats/KiriKiri/CryptAlgorithms.cs:1290-1300 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/AdvSys/ArcGR2.cs:75 — ArcFormats/AdvSys/ArcGR2.cs:75-85 | Legacy/Unison/ArcVCT.cs:80-90 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Legacy/Desire/ImageDES.cs:48 — Legacy/Desire/ImageDES.cs:48-58 | Legacy/System98/ImageG.cs:49-62 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/elf/ImageGCC.cs:140 — ArcFormats/elf/ImageGCC.cs:140-150 | ArcFormats/Seraphim/ImageSeraph.cs:469-479 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/NitroPlus/ArcSteinsGate.cs:281 — ArcFormats/NitroPlus/ArcSteinsGate.cs:281-292 | ArcFormats/Ikura/ImageGGP.cs:124-134 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/Entis/ErisaMatrix.cs:463 — ArcFormats/Entis/ErisaMatrix.cs:463-473 | ArcFormats/Entis/ErisaMatrix.cs:476-486 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/ScrPlayer/ArcPAK.cs:113 — ArcFormats/ScrPlayer/ArcPAK.cs:113-123 | ArcFormats/Qlie/QlieMersenneTwister.cs:47-60 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Legacy/Miami/ImageMIA.cs:277 — Legacy/Miami/ImageMIA.cs:277-287 | ArcFormats/Rits/ArcSAF.cs:118-128 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Legacy/Akatombo/ImageFB.cs:129 — Legacy/Akatombo/ImageFB.cs:129-141 | Legacy/Mink/ImageFC.cs:279-289 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ArcFormats/HuneX/ImageCBG.cs:154 — ArcFormats/HuneX/ImageCBG.cs:154-164 | ArcFormats/Ethornell/ImageCBG.cs:176-186 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D17 · Explicit Debt · FixmeComment · ×18
  • FixmeComment ArcFormats/Cherry/ArcCherry.cs:201 — // FIXME: Exile-specific? — 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 ArcFormats/Cherry/ImageGRP.cs:205 — // 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 ArcFormats/Cri/AudioADX.cs:119 — // 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 ArcFormats/Eagls/ArcEAGLS.cs:173 — // 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 ArcFormats/DxLib/ArcDX8.cs:165 — //FIXME: ReadBytes sets hard cap of filesize to 4GB. — 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 ArcFormats/Emote/ArcPSB.cs:444 — // FIXME works for ASCII names only. — 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 ArcFormats/Emote/ArcPSB.cs:468 — // this implementation is utterly inefficient. 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 ArcFormats/Emote/ArcPSB.cs:596 — // FIXME endianness — 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 ArcFormats/Emote/ArcPSB.cs:604 — // FIXME endianness — 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 ArcFormats/HSP/ArcDPM.cs:157 — // FIXME these constants seem to vary across games — 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 ArcFormats/KiriKiri/ImageTLG.cs:234 — // FIXME this blending algorithm is oversimplified. — 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 ArcFormats/Leaf/ImageBJR.cs:102 — // FIXME read palette — 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 ArcFormats/Macintosh/ImagePICT.cs:208 — // FIXME we just read the first bitmap and override an existing frame — 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 ArcFormats/Silky/ImageAKB.cs:111 — // FIXME what if baseline image is incremental itself? — 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 ArcFormats/Silky/ImageMMO.cs:38 — // FIXME: Implement reliable way to detect difference image and find the corresponding base image name Find base image — 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 ArcFormats/TopCat/ImageSPD.cs:379 — // FIXME: add 'peek' feature to MsbBitStream class — 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 GUI/GarConvert.cs:252 — // FIXME if user chooses to overwrite file, and conversion results in error, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment GameRes/StructSerialization.cs:90 — // FIXME check object graph for cycles — 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.
S1 · Cryptographic Hygiene · Weak hash algorithm · ×18
  • Weak hash algorithm ArcFormats/aNCHOR/AudioFCD.cs:69 — 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.
  • Weak hash algorithm ArcFormats/AZSys/ArcEncrypted.cs:422 — 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.
  • Weak hash algorithm ArcFormats/Artemis/ArcPFS.cs:101 — 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.
  • Weak hash algorithm ArcFormats/Cmvs/ArcCPZ.cs:151 — 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.
  • Weak hash algorithm ArcFormats/Cmvs/CpzHeader.cs:132 — 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.
  • Weak hash algorithm ArcFormats/CsWare/ArcPCS.cs:191 — 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.
  • Weak hash algorithm ArcFormats/Dogenzaka/ImageRSA.cs:58 — 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.
  • Weak hash algorithm ArcFormats/Dogenzaka/ImageRSA.cs:84 — 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.
  • Weak hash algorithm ArcFormats/FamilyAdvSystem/ArcCSAF.cs:92 — 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.
  • Weak hash algorithm ArcFormats/FamilyAdvSystem/ArcCSAF.cs:177 — 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.
  • Weak hash algorithm ArcFormats/KiriKiri/ArcXP3.cs:559 — 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.
  • Weak hash algorithm ArcFormats/KiriKiri/ArcXP3.cs:921 — 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.
  • Weak hash algorithm ArcFormats/Littlewitch/ArcDAT.cs:54 — 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.
  • Weak hash algorithm ArcFormats/Littlewitch/ArcDAT.cs:283 — 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.
  • Weak hash algorithm ArcFormats/NScripter/ArcNS2.cs:173 — 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.
  • Weak hash algorithm ArcFormats/NScripter/EncryptedStream.cs:134 — 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.
  • Weak hash algorithm ArcFormats/NScripter/EncryptedStream.cs:135 — 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.
  • Weak hash algorithm ArcFormats/NSystem/ArcFJSYS.cs:160 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×17
  • Duplicated block (13 lines × 2) ArcFormats/Blowfish.cs:296 — ArcFormats/Blowfish.cs:296-308 | ArcFormats/aNCHOR/Blowfish.cs:122-134 — 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 (13 lines × 2) ArcFormats/ScrPlayer/ImageIMG.cs:101 — ArcFormats/ScrPlayer/ImageIMG.cs:101-113 | ArcFormats/ScrPlayer/ImageIMG.cs:191-203 — 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 `ArcFormats/ScrPlayer/ImageIMG.cs:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) ArcFormats/ShiinaRio/WarcEncryption.cs:1235 — ArcFormats/ShiinaRio/WarcEncryption.cs:1235-1247 | ArcFormats/ShiinaRio/WarcEncryption.cs:1268-1280 — 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 `ArcFormats/ShiinaRio/WarcEncryption.cs:1235` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) ArcFormats/Entis/EriReader.cs:1767 — ArcFormats/Entis/EriReader.cs:1767-1779 | ArcFormats/Entis/EriReader.cs:1806-1818 — 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 `ArcFormats/Entis/EriReader.cs:1767` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) ArcFormats/Qlie/Encryption.cs:213 — ArcFormats/Qlie/Encryption.cs:213-225 | ArcFormats/Qlie/Encryption.cs:320-332 — 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 `ArcFormats/Qlie/Encryption.cs:213` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) ArcFormats/GameSystem/ImageBGD.cs:42 — ArcFormats/GameSystem/ImageBGD.cs:42-54 | ArcFormats/GameSystem/ImageCGD.cs:47-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/GameSystem/ImageBGD.cs:42` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) ArcFormats/Primel/Encryption.cs:183 — ArcFormats/Primel/Encryption.cs:183-195 | ArcFormats/Primel/Encryption.cs:244-256 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) ArcFormats/Kaguya/ArcANM.cs:118 — ArcFormats/Kaguya/ArcANM.cs:118-130 | ArcFormats/Kaguya/ArcANM.cs:182-194 — 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 `ArcFormats/Kaguya/ArcANM.cs:118` 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 (13 lines × 2) ArcFormats/NScripter/ArcSAR.cs:115 — ArcFormats/NScripter/ArcSAR.cs:115-127 | ArcFormats/Yuka/ArcYKC.cs:122-134 — 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 `ArcFormats/NScripter/ArcSAR.cs:115` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) ArcFormats/Triangle/ArcBMX.cs:49 — ArcFormats/Triangle/ArcBMX.cs:49-61 | Legacy/Pearl/ArcARY.cs:47-59 — 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 (13 lines × 2) ArcFormats/Ffa/ImagePT1.cs:226 — ArcFormats/Ffa/ImagePT1.cs:226-238 | ArcFormats/Ffa/ImagePT1.cs:270-282 — 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 `ArcFormats/Ffa/ImagePT1.cs:226` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Legacy/Izumi/ImageMAI2.cs:422 — Legacy/Izumi/ImageMAI2.cs:422-434 | Legacy/Izumi/ImageMAI3.cs:318-330 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Legacy/Rave/ImageRCG.cs:84 — Legacy/Rave/ImageRCG.cs:84-96 | Legacy/Rave/ImageRCG.cs:153-165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) ArcFormats/ArcARCX.cs:50 — ArcFormats/ArcARCX.cs:50-62 | ArcFormats/EntExec/ArcCAB.cs:45-57 — before extracting anything, compare `ArcFormats/ArcARCX.cs` and `ArcFormats/EntExec/ArcCAB.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/ArcARCX.cs:50` 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 (13 lines × 2) ArcFormats/AudioOGG.cs:218 — ArcFormats/AudioOGG.cs:218-230 | ArcFormats/Leaf/AudioG.cs:95-107 — 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 `ArcFormats/AudioOGG.cs:218` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) ArcFormats/KiriKiri/CryptAlgorithms.cs:272 — ArcFormats/KiriKiri/CryptAlgorithms.cs:272-284 | ArcFormats/KiriKiri/CryptAlgorithms.cs:301-313 — 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 `ArcFormats/KiriKiri/CryptAlgorithms.cs:301` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) Legacy/Aaru/ArcFL4.cs:159 — Legacy/Aaru/ArcFL4.cs:159-171 | Legacy/Inspire/ArcIDA.cs:222-234 — 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 `Legacy/Aaru/ArcFL4.cs:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×16
  • Edited copy of a member (13 corresponding lines) ArcFormats/Cmvs/CpzHeader.cs:89 — ArcFormats/Cmvs/CpzHeader.cs:89-101 | ArcFormats/Cmvs/CpzHeader.cs:104-117 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/Silky/ArcIFL.cs:69 — ArcFormats/Silky/ArcIFL.cs:69-87 | ArcFormats/RiddleSoft/ArcPAC.cs:86-98 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/Kaguya/ImageAO.cs:49 — ArcFormats/Kaguya/ImageAO.cs:49-63 | ArcFormats/Kaguya/ImageAP.cs:49-61 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/BlueGale/ImageBBM.cs:57 — ArcFormats/BlueGale/ImageBBM.cs:57-69 | ArcFormats/TopCat/ImageSPD.cs:108-131 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/Kaguya/ArcUF.cs:81 — ArcFormats/Kaguya/ArcUF.cs:81-97 | ArcFormats/Kaguya/ArcKaguya.cs:64-76 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Legacy/UMeSoft/AudioIKE.cs:39 — Legacy/UMeSoft/AudioIKE.cs:39-51 | Legacy/UMeSoft/ImageIKE.cs:45-62 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Legacy/AyPio/ArcDLB.cs:41 — Legacy/AyPio/ArcDLB.cs:41-53 | Legacy/AyPio/ArcDLB.cs:82-97 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/Sas5/ArcGAR.cs:86 — ArcFormats/Sas5/ArcGAR.cs:86-98 | ArcFormats/Sas5/ArcWAR.cs:100-112 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/KogadoCocotte.cs:604 — ArcFormats/KogadoCocotte.cs:604-619 | ArcFormats/KogadoCocotte.cs:623-635 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/KiriKiri/ArcXP3.cs:818 — ArcFormats/KiriKiri/ArcXP3.cs:818-831 | Legacy/Pinky/ArcA5R.cs:203-215 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/KiriKiri/ArcXP3.cs:453 — ArcFormats/KiriKiri/ArcXP3.cs:453-465 | ArcFormats/KiriKiri/ArcXP3.cs:731-743 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/TanukiSoft/ArcTAC.cs:224 — ArcFormats/TanukiSoft/ArcTAC.cs:224-236 | ArcFormats/Nekopack/ArcNEKO.cs:167-179 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/TamaSoft/AudioESD.cs:41 — ArcFormats/TamaSoft/AudioESD.cs:41-54 | Legacy/UMeSoft/AudioSTR.cs:39-51 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/KiriKiri/HxCrypt.cs:960 — ArcFormats/KiriKiri/HxCrypt.cs:960-972 | ArcFormats/KiriKiri/HxCrypt.cs:975-988 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Legacy/Miami/ImageMIA.cs:93 — Legacy/Miami/ImageMIA.cs:93-105 | Legacy/Ucom/ImageUG.cs:87-100 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) ArcFormats/Cyberworks/ImageTB1.cs:41 — ArcFormats/Cyberworks/ImageTB1.cs:41-53 | ArcFormats/Eternity/ImageSGF.cs:54-70 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×16
  • Edited copy of a member (10 corresponding lines) ArcFormats/Ankh/ImageGPD.cs:57 — ArcFormats/Ankh/ImageGPD.cs:57-67 | ArcFormats/Ankh/ImageMSK.cs:52-61 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/DigitalWorks/ArcPACsingle.cs:49 — ArcFormats/DigitalWorks/ArcPACsingle.cs:49-61 | ArcFormats/MokoPro/CompressedFile.cs:179-188 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/SoftwareHouseParsley/ArcCG2.cs:102 — ArcFormats/SoftwareHouseParsley/ArcCG2.cs:102-111 | ArcFormats/SoftwareHouseParsley/ArcUCG.cs:106-115 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/Valkyria/ImageMG2.cs:124 — ArcFormats/Valkyria/ImageMG2.cs:124-133 | ArcFormats/Valkyria/ImageMG2.cs:218-232 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/Entis/ErisaMatrix.cs:182 — ArcFormats/Entis/ErisaMatrix.cs:182-191 | ArcFormats/Entis/ErisaMatrix.cs:194-203 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Legacy/YellowCap/ImageGEF.cs:44 — Legacy/YellowCap/ImageGEF.cs:44-53 | Legacy/YellowCap/ImageGGF.cs:39-50 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/NScripter/WidgetNSA.xaml.cs:13 — ArcFormats/NScripter/WidgetNSA.xaml.cs:13-23 | ArcFormats/Majiro/WidgetRCT.xaml.cs:13-22 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/elf/ImageGP8.cs:62 — ArcFormats/elf/ImageGP8.cs:62-72 | ArcFormats/elf/ImageGP8.cs:111-120 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/AliceSoft/ArcAFA.cs:102 — ArcFormats/AliceSoft/ArcAFA.cs:102-111 | ArcFormats/Primel/ArcPCF.cs:63-74 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/Amaterasu/ImageGRP.cs:44 — ArcFormats/Amaterasu/ImageGRP.cs:44-53 | ArcFormats/Kaguya/ImageAP.cs:168-179 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/Origin/ArcDAT.cs:415 — ArcFormats/Origin/ArcDAT.cs:415-424 | ArcFormats/Origin/ArcGAF.cs:123-132 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Legacy/DigitalMonkey/ImagePKT.cs:172 — Legacy/DigitalMonkey/ImagePKT.cs:172-181 | Legacy/Force/ImageDZP.cs:86-95 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/Amaterasu/CreateAMIWidget.xaml.cs:48 — ArcFormats/Amaterasu/CreateAMIWidget.xaml.cs:48-57 | GUI/DragScroll.cs:169-178 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) ArcFormats/BeF/ImageALO.cs:65 — ArcFormats/BeF/ImageALO.cs:65-74 | ArcFormats/ImageMB.cs:85-94 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Legacy/Adviz/ImageGIZ.cs:298 — Legacy/Adviz/ImageGIZ.cs:298-307 | Legacy/Ponytail/ImageTSZ.cs:243-252 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) GUI/FileErrorDialog.xaml.cs:51 — GUI/FileErrorDialog.xaml.cs:51-60 | GUI/TroubleShootingDialog.xaml.cs:33-42 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
X18 · Disposal-pattern correctness · Disposes a dependency it does not own · ×16
  • Disposes a dependency it does not own ArcFormats/Cyberworks/ImageDATA.cs:317 — `m_input` is never created by `DataImageDecoder` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 317). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/HuneX/ArcMZP.cs:314 — `m_input` is never created by `MzxImageReader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 314). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/Ankh/ArcGRP.cs:613 — `m_input` is never created by `GrpUnpacker` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 613). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/Groover/ArcPCG.cs:175 — `m_input` is never created by `PcgReaderBase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 175). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/Foster/ImageC24.cs:142 — `m_input` is never created by `CDecoderBase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 142). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/Cyberworks/ImageTINK.cs:488 — `m_input` is never created by `AImageReader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 488). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/TechnoBrain/ImageIPF.cs:250 — `m_input` is never created by `IpfReader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 250). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/Unity/AssetReader.cs:214 — `m_input` is never created by `AssetReader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 214). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/ArcSPack.cs:199 — `m_input` is never created by `PackedReader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 199). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/AnimeGameSystem/ImageAinos.cs:291 — `m_input` is never created by `Reader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 291). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/Marble/ImagePRS.cs:232 — `m_input` is never created by `Reader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 232). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own ArcFormats/ShiinaRio/ImageS25.cs:381 — `m_input` is never created by `Reader` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 381). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own GameRes/ImageDecoder.cs:113 — `m_file` is never created by `ImageFormatDecoder` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 113). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own GameRes/ImageDecoder.cs:155 — `m_input` is never created by `BinaryImageDecoder` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 155). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own Legacy/Mina/ArcPAK.cs:293 — `m_input` is never created by `BitmapDecoder` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 293). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own Legacy/Nekotaro/ImageGCmp.cs:668 — `m_input` is never created by `GCmpDecoder` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 668). Its declared type `IBinaryStream` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×14
  • Edited copy of a member (8 corresponding lines) ArcFormats/Cri/ImageXTX.cs:202 — ArcFormats/Cri/ImageXTX.cs:202-211 | ArcFormats/Cri/ImageXTX.cs:214-221 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/KiriKiri/CryptAlgorithms.cs:1048 — ArcFormats/KiriKiri/CryptAlgorithms.cs:1048-1055 | ArcFormats/KiriKiri/CryptAlgorithms.cs:1678-1685 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/Tactics/ArcLST.cs:146 — ArcFormats/Tactics/ArcLST.cs:146-154 | ArcFormats/Xuse/ArcWAG.cs:80-87 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Legacy/Peach/ArcPAK.cs:143 — Legacy/Peach/ArcPAK.cs:143-150 | Legacy/Peach/ArcPAK.cs:153-160 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/HuneX/ImageCBG.cs:73 — ArcFormats/HuneX/ImageCBG.cs:73-80 | ArcFormats/Ethornell/ImageCBG.cs:83-90 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/BellDa/ImageCP.cs:46 — ArcFormats/BellDa/ImageCP.cs:46-53 | ArcFormats/Nekopunch/ImagePBM.cs:40-48 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/Ikura/ImageDRG.cs:298 — ArcFormats/Ikura/ImageDRG.cs:298-305 | ArcFormats/Majiro/ImageRCT.cs:514-521 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/Adobe/ImagePSD.cs:74 — ArcFormats/Adobe/ImagePSD.cs:74-81 | ArcFormats/Lucifen/ImageELG.cs:102-109 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/Softpal/ImagePIC.cs:73 — ArcFormats/Softpal/ImagePIC.cs:73-80 | ArcFormats/Dac/ImageDGC.cs:60-68 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/ResourceSettings.cs:62 — ArcFormats/ResourceSettings.cs:62-69 | REDACTED:184-195 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/Cmvs/ArcCPZ1.cs:85 — ArcFormats/Cmvs/ArcCPZ1.cs:85-92 | ArcFormats/Cmvs/ArcPBZ.cs:129-136 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/RenPy/CreateRPAWidget.xaml.cs:30 — ArcFormats/RenPy/CreateRPAWidget.xaml.cs:30-37 | ArcFormats/CatSystem/WidgetINT.xaml.cs:97-104 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/Groover/ArcPCG.cs:140 — ArcFormats/Groover/ArcPCG.cs:140-147 | ArcFormats/ShiinaRio/ImageS25.cs:106-113 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ArcFormats/Cmvs/AudioMV.cs:103 — ArcFormats/Cmvs/AudioMV.cs:103-110 | ArcFormats/Sviu/AudioKPV.cs:140-147 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×14
  • Duplicated block (14 lines × 2) ArcFormats/WildBug/ImageWBM.cs:601 — ArcFormats/WildBug/ImageWBM.cs:601-614 | ArcFormats/WildBug/ImageWBM.cs:780-793 — 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 `ArcFormats/WildBug/ImageWBM.cs:601` 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) ArcFormats/ImageLZS.cs:99 — ArcFormats/ImageLZS.cs:99-112 | ArcFormats/RealLive/ArcSEEN.cs:97-110 — 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 `ArcFormats/ImageLZS.cs:99` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) ArcFormats/CatSystem/ArcINT.cs:334 — ArcFormats/CatSystem/ArcINT.cs:334-347 | ArcFormats/Majiro/ArcMajiro.cs:177-190 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) ArcFormats/Kaguya/ArcPL00.cs:57 — ArcFormats/Kaguya/ArcPL00.cs:57-70 | ArcFormats/Kaguya/ArcPL10.cs:57-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) ArcFormats/Kaguya/ArcAN21.cs:78 — ArcFormats/Kaguya/ArcAN21.cs:78-91 | ArcFormats/Kaguya/ArcPL10.cs:60-73 — before extracting anything, compare `ArcFormats/Kaguya/ArcAN21.cs` and `ArcFormats/Kaguya/ArcPL10.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) ArcFormats/Entis/EriReader.cs:1271 — ArcFormats/Entis/EriReader.cs:1271-1284 | ArcFormats/Entis/EriReader.cs:1319-1332 — 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 `ArcFormats/Entis/EriReader.cs:1271` 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 (14 lines × 2) ArcFormats/Ikura/ImageDRG.cs:216 — ArcFormats/Ikura/ImageDRG.cs:216-229 | ArcFormats/Majiro/ImageRCT.cs:434-447 — 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 `ArcFormats/Ikura/ImageDRG.cs:216` 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 (14 lines × 2) ArcFormats/Ethornell/ImageCBG.cs:160 — ArcFormats/Ethornell/ImageCBG.cs:160-173 | ArcFormats/HuneX/ImageCBG.cs:138-151 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) ArcFormats/Apricot/ArcDAT.cs:87 — ArcFormats/Apricot/ArcDAT.cs:87-100 | ArcFormats/Musica/ArcPAZ.cs:267-280 — 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) ArcFormats/ShiinaRio/WarcEncryption.cs:1332 — ArcFormats/ShiinaRio/WarcEncryption.cs:1332-1345 | ArcFormats/ShiinaRio/WarcEncryption.cs:1365-1378 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) ArcFormats/Silky/ImageZIT.cs:122 — ArcFormats/Silky/ImageZIT.cs:122-135 | ArcFormats/Silky/ImageZIT.cs:152-165 — 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 `ArcFormats/Silky/ImageZIT.cs:122` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Legacy/Mapl/ImageMI2.cs:253 — Legacy/Mapl/ImageMI2.cs:253-266 | Legacy/Mapl/ImageMI2.cs:410-423 — 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 `Legacy/Mapl/ImageMI2.cs:253` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) ArcFormats/BlueGale/VideoAMV.cs:60 — ArcFormats/BlueGale/VideoAMV.cs:60-75 | Legacy/ShapeShifter/ArcBND.cs:62-75 — 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 `ArcFormats/BlueGale/VideoAMV.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (14 lines × 2) ArcFormats/Ffa/AudioWA1.cs:134 — ArcFormats/Ffa/AudioWA1.cs:134-147 | ArcFormats/Ffa/AudioWA1.cs:417-430 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×14
  • Duplicated block (6 lines × 3) ArcFormats/StudioEgo/ArcEGO.cs:62 — ArcFormats/StudioEgo/ArcEGO.cs:62-67 | ArcFormats/StudioEgo/ArcEGO.cs:175-180 | Legacy/RedZone/ArcPAK.cs:61-66 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/StudioEgo/ArcEGO.cs:62` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 3) ArcFormats/Bishop/ArcPK.cs:49 — ArcFormats/Bishop/ArcPK.cs:49-54 | ArcFormats/Leaf/ArcTEX.cs:57-62 | ArcFormats/Valkyria/ArcDAT.cs:56-61 — 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 `ArcFormats/Bishop/ArcPK.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 (6 lines × 3) ArcFormats/Bishop/ArcPK.cs:54 — ArcFormats/Bishop/ArcPK.cs:54-59 | ArcFormats/Gpk2/ArcGPK2.cs:62-67 | ArcFormats/WildBug/ArcWBP.cs:76-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 3) ArcFormats/ArcPACKDAT.cs:57 — ArcFormats/ArcPACKDAT.cs:57-62 | ArcFormats/BlackRainbow/ArcGSP.cs:43-48 | ArcFormats/Ethornell/ArcBGI.cs:133-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 3) ArcFormats/SoftwareHouseParsley/ArcScn.cs:50 — ArcFormats/SoftwareHouseParsley/ArcScn.cs:50-55 | Legacy/Aquarium/ArcCPA.cs:59-64 | Legacy/Zone/ArcPKD.cs:59-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Zone/ArcPKD.cs:57` calls `IsNullOrWhiteSpace` and `ArcFormats/SoftwareHouseParsley/ArcScn.cs:49` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 3) ArcFormats/BlackRainbow/ArcCCF.cs:67 — ArcFormats/BlackRainbow/ArcCCF.cs:67-72 | ArcFormats/BlackRainbow/ArcSPPAK.cs:83-88 | ArcFormats/Foster/ArcC24.cs:66-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Foster/ArcC24.cs:65` calls `Sort` and `ArcFormats/BlackRainbow/ArcCCF.cs:66` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 3) ArcFormats/CsWare/ImageGDT.cs:217 — ArcFormats/CsWare/ImageGDT.cs:217-222 | ArcFormats/CsWare/ImageGDT.cs:226-231 | ArcFormats/CsWare/ImageGDT.cs:234-239 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/CsWare/ImageGDT.cs:217` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 × 3) ArcFormats/RealLive/ArcOVK.cs:72 — ArcFormats/RealLive/ArcOVK.cs:72-77 | ArcFormats/StudioJikkenshitsu/ArcUMPK.cs:60-65 | Legacy/Nyoken/ArcZLK.cs:52-57 — 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 `ArcFormats/RealLive/ArcOVK.cs:72` 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 × 3) ArcFormats/Softpal/ImagePIC.cs:161 — ArcFormats/Softpal/ImagePIC.cs:161-166 | ArcFormats/Softpal/ImagePIC.cs:208-213 | ArcFormats/Softpal/ImagePIC.cs:242-247 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Softpal/ImagePIC.cs:161` 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 × 3) ArcFormats/FlyingShine/ArcPD.cs:319 — ArcFormats/FlyingShine/ArcPD.cs:319-324 | ArcFormats/MOONSTONE/ArcPAK.cs:57-63 | Legacy/PenguinWorks/ArcDAT.cs:52-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 3) ArcFormats/Circus/AudioPCM.cs:307 — ArcFormats/Circus/AudioPCM.cs:307-312 | ArcFormats/Circus/AudioPCM.cs:323-328 | ArcFormats/Circus/AudioPCM.cs:370-375 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Circus/AudioPCM.cs:307` 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 × 3) ArcFormats/Crowd/ImageGAX.cs:132 — ArcFormats/Crowd/ImageGAX.cs:132-137 | ArcFormats/Crowd/ImageGAX.cs:150-155 | ArcFormats/Crowd/ImageGAX.cs:156-161 — 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.
  • Duplicated block (6 lines × 3) ArcFormats/Banana/ArcPK.cs:90 — ArcFormats/Banana/ArcPK.cs:90-95 | ArcFormats/HCSystem/ArcPAK.cs:105-110 | ArcFormats/Silky/ArcAi6Win.cs:95-100 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 3) Legacy/AyPio/PdtBitmap.cs:46 — Legacy/AyPio/PdtBitmap.cs:46-51 | Legacy/Harvest/ImageUNH.cs:42-51 | Legacy/Powerd/ImageNCL.cs:43-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
IC1 · Incompleteness & stubs · Unfinished branch · ×13
  • Unfinished branch — throws NotImplementedException ArcFormats/BlackCyc/ImageDWQ.cs:189 — The branch `if (null == bitmap)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/Entis/EriReader.cs:764 — The branch `if (0 != (fOpTable & 0xC))` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/Entis/MioDecoder.cs:376 — The branch `if (m_mioih.Architecture == EriCode.Nemesis)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/Entis/MioDecoder.cs:673 — The branch `if (m_mioih.Architecture == EriCode.Nemesis)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/KiriKiri/ImageTLG.cs:1329 — The branch `if (0 == block_count)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/Lambda/ArcLAX.cs:140 — The branch `if (final_size != 0)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException REDACTED:100 — The branch `if (meta.Shuffled)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/Lz4Stream.cs:115 — The branch `if (!info.IndependentBlocks)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/Lz4Stream.cs:117 — The branch `if (info.HasDictionary)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/LzssStream.cs:118 — The branch `if (mode != LzssMode.Decompress)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/ShiinaRio/WarcEncryption.cs:959 — The branch `if ((flags & 0x104) == 0x104)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/ShiinaRio/WarcEncryption.cs:1039 — The branch `if ((flags & 0x104) == 0x104)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException ArcFormats/ShiinaRio/WarcEncryption.cs:1139 — The branch `if ((flags & 0x104) == 0x104)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×12
  • Edited copy of a member (14 corresponding lines) Legacy/Izumi/ImageMAI2.cs:390 — Legacy/Izumi/ImageMAI2.cs:390-418 | Legacy/Ponytail/ImageTSZ.cs:138-163 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) ArcFormats/KiriKiri/CryptAlgorithms.cs:574 — ArcFormats/KiriKiri/CryptAlgorithms.cs:574-587 | ArcFormats/KiriKiri/CryptAlgorithms.cs:590-603 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) ArcFormats/KiriKiri/CryptAlgorithms.cs:271 — ArcFormats/KiriKiri/CryptAlgorithms.cs:271-284 | ArcFormats/KiriKiri/CryptAlgorithms.cs:298-313 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) ArcFormats/Lucifen/ArcLPK.cs:74 — ArcFormats/Lucifen/ArcLPK.cs:74-87 | ArcFormats/Lucifen/ArcLPK.cs:90-103 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) GameRes/ArcView.cs:326 — GameRes/ArcView.cs:326-339 | GameRes/ArcView.cs:342-355 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) ArcFormats/ImageLZS.cs:74 — ArcFormats/ImageLZS.cs:74-87 | Legacy/Artifact/ImageLZS.cs:42-55 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) ArcFormats/Abel/ImageCBF.cs:200 — ArcFormats/Abel/ImageCBF.cs:200-214 | Legacy/Force/ImageDZP.cs:98-111 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) ArcFormats/Cadath/ImageKGF.cs:83 — ArcFormats/Cadath/ImageKGF.cs:83-96 | ArcFormats/Liar/ImageLIM.cs:90-103 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) GameRes/ImageTIFF.cs:291 — GameRes/ImageTIFF.cs:291-304 | GameRes/ImageTIFF.cs:307-320 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) ArcFormats/LightVN/ArcVNDAT.cs:53 — ArcFormats/LightVN/ArcVNDAT.cs:53-68 | ArcFormats/PkWare/ArcZIP.cs:112-125 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) ArcFormats/Abel/ImageCBF.cs:53 — ArcFormats/Abel/ImageCBF.cs:53-66 | ArcFormats/RealLive/ImagePDT.cs:49-62 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) ArcFormats/Cri/ImageGXT.cs:66 — ArcFormats/Cri/ImageGXT.cs:66-80 | ArcFormats/FrontWing/ImageFG.cs:47-60 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×12
  • Edited copy of a member (21 corresponding lines) ArcFormats/WildBug/ImageWBM.cs:217 — ArcFormats/WildBug/ImageWBM.cs:217-237 | ArcFormats/WildBug/ImageWBM.cs:240-260 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) ArcFormats/Primel/Encryption.cs:220 — ArcFormats/Primel/Encryption.cs:220-240 | ArcFormats/Primel/Encryption.cs:286-306 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Legacy/Tigerman/ArcPAC.cs:47 — Legacy/Tigerman/ArcPAC.cs:47-69 | Legacy/Uran/ArcPHS.cs:43-63 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) ArcFormats/SoftwareHouseParsley/ArcScn.cs:41 — ArcFormats/SoftwareHouseParsley/ArcScn.cs:41-61 | Legacy/Herb/ArcPAK.cs:48-71 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) ArcFormats/ShiinaRio/ImageCHD.cs:48 — ArcFormats/ShiinaRio/ImageCHD.cs:48-68 | ArcFormats/ShiinaRio/ImageS25.cs:54-74 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) ArcFormats/AZSys/ImageTYP1.cs:153 — ArcFormats/AZSys/ImageTYP1.cs:153-173 | ArcFormats/AZSys/ImageCPB.cs:158-178 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) ArcFormats/Malie/MalieEncryption.cs:126 — ArcFormats/Malie/MalieEncryption.cs:126-146 | ArcFormats/NScripter/EncryptedStream.cs:52-73 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) ArcFormats/Seraphim/ArcVoice.cs:77 — ArcFormats/Seraphim/ArcVoice.cs:77-98 | ArcFormats/Aoi/ArcBOX.cs:115-135 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) ArcFormats/aNCHOR/Blowfish.cs:121 — ArcFormats/aNCHOR/Blowfish.cs:121-141 | ArcFormats/Blowfish.cs:295-315 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) ArcFormats/Silky/ImageZIT.cs:115 — ArcFormats/Silky/ImageZIT.cs:115-135 | ArcFormats/Silky/ImageZIT.cs:143-165 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) ArcFormats/Mebius/ImageMCG.cs:133 — ArcFormats/Mebius/ImageMCG.cs:133-155 | ArcFormats/Mebius/ImageMCG.cs:158-178 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) ArcFormats/Macromedia/ImageBITD.cs:175 — ArcFormats/Macromedia/ImageBITD.cs:175-202 | Legacy/Lazycrew/ImageDAT.cs:125-145 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×11
  • Edited copy of a member (32 corresponding lines) ArcFormats/Softpal/ImagePIC.cs:158 — ArcFormats/Softpal/ImagePIC.cs:158-202 | ArcFormats/Softpal/ImagePIC.cs:205-236 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Legacy/Discovery/ArcDAT.cs:89 — Legacy/Discovery/ArcDAT.cs:89-121 | Legacy/Discovery/ArcDAT.cs:124-155 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Legacy/Aaru/ArcFL2.cs:45 — Legacy/Aaru/ArcFL2.cs:45-76 | Legacy/Aaru/ArcFL3.cs:43-76 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) ArcFormats/Ethornell/ArcBGI.cs:51 — ArcFormats/Ethornell/ArcBGI.cs:51-82 | ArcFormats/Ethornell/ArcBGI.cs:131-166 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) ArcFormats/ComicPlayer/ArcCPF.cs:55 — ArcFormats/ComicPlayer/ArcCPF.cs:55-93 | ArcFormats/YuukiNovel/ArcYuuki.cs:47-78 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Legacy/Mina/ArcPAK.cs:48 — Legacy/Mina/ArcPAK.cs:48-79 | Legacy/Mina/ArcPAK.cs:98-131 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) ArcFormats/DeepBlue/ArcAC.cs:50 — ArcFormats/DeepBlue/ArcAC.cs:50-81 | ArcFormats/FrontWing/ArcTLP.cs:45-77 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) ArcFormats/Dac/ImageDGC.cs:128 — ArcFormats/Dac/ImageDGC.cs:128-169 | ArcFormats/Dac/ImageDGC.cs:172-203 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) ArcFormats/Maika/ArcMK2.cs:210 — ArcFormats/Maika/ArcMK2.cs:210-241 | Legacy/Eve/ArcGM.cs:136-169 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) ArcFormats/Leaf/ImagePX.cs:371 — ArcFormats/Leaf/ImagePX.cs:371-402 | ArcFormats/Leaf/ImagePX.cs:405-439 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) ArcFormats/Entis/EriReader.cs:1022 — ArcFormats/Entis/EriReader.cs:1022-1056 | ArcFormats/Entis/EriReader.cs:1059-1090 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×11
  • Edited copy of a member (23 corresponding lines) ArcFormats/Artemis/ArcPFS.cs:76 — ArcFormats/Artemis/ArcPFS.cs:76-106 | ArcFormats/Artemis/ArcPFS.cs:109-131 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) ArcFormats/Pandora/ArcPBX.cs:44 — ArcFormats/Pandora/ArcPBX.cs:44-66 | ArcFormats/AdvSys/ArcAdvSysT.cs:49-72 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Legacy/PenguinWorks/ArcPAC.cs:52 — Legacy/PenguinWorks/ArcPAC.cs:52-78 | Legacy/Force/ArcPAQ.cs:43-65 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Legacy/Mapl/ImageMI2.cs:269 — Legacy/Mapl/ImageMI2.cs:269-291 | Legacy/Mapl/ImageMI2.cs:294-317 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Legacy/Rave/ImageRCG.cs:82 — Legacy/Rave/ImageRCG.cs:82-104 | Legacy/Rave/ImageRCG.cs:150-177 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) ArcFormats/Mnp/ArcMMA.cs:130 — ArcFormats/Mnp/ArcMMA.cs:130-152 | ArcFormats/Mnp/ArcMMA.cs:374-396 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) ArcFormats/Ikura/ImageDRG.cs:212 — ArcFormats/Ikura/ImageDRG.cs:212-234 | ArcFormats/Majiro/ImageRCT.cs:430-452 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) ArcFormats/Lambda/ArcCLS.cs:43 — ArcFormats/Lambda/ArcCLS.cs:43-65 | ArcFormats/Sviu/VideoMOV.cs:47-79 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) ArcFormats/ShiinaRio/ArcWARC.cs:228 — ArcFormats/ShiinaRio/ArcWARC.cs:228-250 | ArcFormats/ShiinaRio/ArcWARC.cs:253-275 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) ArcFormats/elf/ImageGPH.cs:225 — ArcFormats/elf/ImageGPH.cs:225-253 | ArcFormats/elf/ImageGPH.cs:274-296 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) ArcFormats/Emote/ArcPSB.cs:215 — ArcFormats/Emote/ArcPSB.cs:215-242 | ArcFormats/Emote/ArcPSB.cs:268-290 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×11
  • Edited copy of a member (16 corresponding lines) ArcFormats/Eushully/ArcGPC.cs:109 — ArcFormats/Eushully/ArcGPC.cs:109-125 | Legacy/Lazycrew/ArcDAT.cs:167-182 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) ArcFormats/ShiinaRio/ArcWARC1.0.cs:79 — ArcFormats/ShiinaRio/ArcWARC1.0.cs:79-94 | ArcFormats/Triangle/ArcBMX.cs:95-112 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) ArcFormats/BlackCyc/ImageDWQ.cs:228 — ArcFormats/BlackCyc/ImageDWQ.cs:228-243 | ArcFormats/Crowd/ImageCWP.cs:129-146 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) ArcFormats/Crowd/ImageCWL.cs:98 — ArcFormats/Crowd/ImageCWL.cs:98-113 | ArcFormats/Crowd/ImageZBM.cs:60-79 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) GameRes/ArcView.cs:57 — GameRes/ArcView.cs:57-72 | Legacy/Omi/ArcDAT.cs:190-206 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) ArcFormats/Crc32.cs:38 — ArcFormats/Crc32.cs:38-54 | GameRes/Checksum.cs:45-60 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) ArcFormats/elf/ImageGPH.cs:256 — ArcFormats/elf/ImageGPH.cs:256-271 | ArcFormats/elf/ImageGPH.cs:299-315 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) GameRes/ArcStream.cs:123 — GameRes/ArcStream.cs:123-138 | GameRes/BinaryStream.cs:209-226 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) GameRes/Utility.cs:93 — GameRes/Utility.cs:93-108 | Legacy/Ponytail/ImageTSZ.cs:310-328 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) ArcFormats/Unity/OggStream.cs:250 — ArcFormats/Unity/OggStream.cs:250-265 | ArcFormats/Unity/OggStream.cs:268-284 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) ArcFormats/Nags/ImageNGP.cs:47 — ArcFormats/Nags/ImageNGP.cs:47-65 | ArcFormats/Bishop/ImageGSA.cs:57-72 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×11
  • Edited copy of a member (9 corresponding lines) Legacy/Mink/ImageFC.cs:98 — Legacy/Mink/ImageFC.cs:98-108 | Legacy/Mink/ImageFD.cs:85-93 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) ArcFormats/Cyberworks/ArcDAT.cs:136 — ArcFormats/Cyberworks/ArcDAT.cs:136-148 | ArcFormats/Cyberworks/ArcDAT.cs:156-164 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) ArcFormats/UMeSoft/ArcMGX.cs:111 — ArcFormats/UMeSoft/ArcMGX.cs:111-119 | ArcFormats/UMeSoft/ImageGRX.cs:322-330 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) ArcFormats/Ail/ArcLNK2.cs:48 — ArcFormats/Ail/ArcLNK2.cs:48-56 | ArcFormats/Ail/ArcAil.cs:49-57 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) ArcFormats/Interheart/ImageHMP.cs:41 — ArcFormats/Interheart/ImageHMP.cs:41-49 | Legacy/System21/ImageBET.cs:43-52 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) REDACTED:190 — REDACTED:190-198 | ArcFormats/FamilyAdvSystem/ArcCSAF.cs:147-155 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) ArcFormats/Malie/MalieEncryption.cs:170 — ArcFormats/Malie/MalieEncryption.cs:170-178 | ArcFormats/NScripter/EncryptedStream.cs:90-98 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) ArcFormats/Qlie/DelphiDeserializer.cs:103 — ArcFormats/Qlie/DelphiDeserializer.cs:103-111 | ArcFormats/rUGP/ArcRIO.cs:815-825 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) ArcFormats/AdvSys/ImageGR2.cs:273 — ArcFormats/AdvSys/ImageGR2.cs:273-281 | Legacy/UMeSoft/ArcBIN.cs:241-249 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) ArcFormats/VnMaker/ArcZIP.cs:46 — ArcFormats/VnMaker/ArcZIP.cs:46-54 | ArcFormats/PkWare/ArcZIP.cs:74-82 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) ArcFormats/Unity/BundleStream.cs:217 — ArcFormats/Unity/BundleStream.cs:217-225 | Legacy/Inspire/ArcIDA.cs:240-248 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×11
  • Edited copies of one member (3 members, 7+ corresponding lines) ArcFormats/ShiinaRio/WarcEncryption.cs:1052 — ArcFormats/ShiinaRio/WarcEncryption.cs:1052-1058 | ArcFormats/ShiinaRio/WarcEncryption.cs:1065-1071 | ArcFormats/Strikes/ArcPCK.cs:264-273 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Legacy/Desire/ImageDES.cs:61 — Legacy/Desire/ImageDES.cs:61-67 | Legacy/System98/ImageG.cs:65-71 | Legacy/Tiare/ImageGRA.cs:83-94 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Legacy/HillField/ImageIMG.cs:55 — Legacy/HillField/ImageIMG.cs:55-61 | Legacy/PenguinWorks/ImagePXL.cs:49-55 | Legacy/hmp/ImageCBF.cs:54-60 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) ArcFormats/Crowd/ImageGAX.cs:70 — ArcFormats/Crowd/ImageGAX.cs:70-76 | ArcFormats/Dogenzaka/ImageRSA.cs:82-89 | ArcFormats/Malie/ImageMGF.cs:56-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) ArcFormats/Yox/ArcYOX.cs:123 — ArcFormats/Yox/ArcYOX.cs:123-129 | REDACTED:306-313 | Legacy/Broccoli/ArcP00.cs:40-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) ArcFormats/MicroVision/ArcARC.cs:85 — ArcFormats/MicroVision/ArcARC.cs:85-93 | Legacy/DigitalMonkey/ArcDM.cs:81-87 | Legacy/Logg/ArcARF.cs:84-92 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) ArcFormats/CatSystem/ArcINT.cs:279 — ArcFormats/CatSystem/ArcINT.cs:279-285 | ArcFormats/Cyberworks/ArcDAT.cs:350-356 | ArcFormats/DxLib/ArcMED.cs:191-197 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) ArcFormats/Marble/ImageYP.cs:71 — ArcFormats/Marble/ImageYP.cs:71-77 | Legacy/Mink/ImageDAT.cs:72-79 | Legacy/QSoft/ImageBPE.cs:52-58 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) ArcFormats/Aoi/ArcBOX.cs:138 — ArcFormats/Aoi/ArcBOX.cs:138-144 | ArcFormats/StudioJikkenshitsu/ArcUMPK.cs:82-88 | Legacy/Marron/ArcCPN.cs:100-106 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) ArcFormats/FrontierWorks/ImageEXT.cs:69 — ArcFormats/FrontierWorks/ImageEXT.cs:69-75 | ArcFormats/G2/ImageBGRA.cs:60-66 | ArcFormats/Kaguya/ImageAP.cs:141-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) ArcFormats/Cri/AudioHCA.cs:503 — ArcFormats/Cri/AudioHCA.cs:503-510 | ArcFormats/GameSystem/AudioADP4.cs:195-201 | Legacy/AyPio/AudioVOC.cs:141-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×11
  • Duplicated block (15 lines × 2) ArcFormats/Lucifen/ImageELG.cs:274 — ArcFormats/Lucifen/ImageELG.cs:274-288 | ArcFormats/Lucifen/ImageELG.cs:483-497 — 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 `ArcFormats/Lucifen/ImageELG.cs:274` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) ArcFormats/Cmvs/ArcCPZ.cs:273 — ArcFormats/Cmvs/ArcCPZ.cs:273-287 | ArcFormats/Cmvs/ArcCPZ.cs:305-319 — 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 `ArcFormats/Cmvs/ArcCPZ.cs:273` 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) ArcFormats/Entergram/ArcPacV1.cs:78 — ArcFormats/Entergram/ArcPacV1.cs:78-92 | ArcFormats/Entergram/ArcPacV1.cs:106-120 — 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 `ArcFormats/Entergram/ArcPacV1.cs:78` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) ArcFormats/Mnp/ArcMMA.cs:138 — ArcFormats/Mnp/ArcMMA.cs:138-152 | ArcFormats/Mnp/ArcMMA.cs:382-396 — 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 `ArcFormats/Mnp/ArcMMA.cs:138` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 2) ArcFormats/Qlie/Encryption.cs:122 — ArcFormats/Qlie/Encryption.cs:122-136 | ArcFormats/Qlie/Encryption.cs:176-190 — 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 `ArcFormats/Qlie/Encryption.cs:122` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) ArcFormats/CaramelBox/ArcARC4.cs:297 — ArcFormats/CaramelBox/ArcARC4.cs:297-311 | ArcFormats/NitroPlus/ArcNPK.cs:537-551 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) ArcFormats/StudioEgo/ArcEGO.cs:47 — ArcFormats/StudioEgo/ArcEGO.cs:47-61 | ArcFormats/StudioEgo/ArcEGO.cs:160-174 — 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 `ArcFormats/StudioEgo/ArcEGO.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. 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) ArcFormats/NitroPlus/ArcNPA.cs:221 — ArcFormats/NitroPlus/ArcNPA.cs:221-235 | ArcFormats/YuRis/ArcYPF.cs:331-345 — 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 (15 lines × 2) Legacy/Mink/ImageFC.cs:145 — Legacy/Mink/ImageFC.cs:145-159 | Legacy/Mink/ImageFC.cs:166-180 — 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 `Legacy/Mink/ImageFC.cs:145` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Legacy/Yaneurao/ArcDAT.cs:64 — Legacy/Yaneurao/ArcDAT.cs:64-78 | Legacy/Yaneurao/ArcDAT.cs:114-128 — 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 `Legacy/Yaneurao/ArcDAT.cs:64` 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) ArcFormats/Triangle/ArcBMX.cs:68 — ArcFormats/Triangle/ArcBMX.cs:68-82 | Legacy/BlackButterfly/ArcDAT.cs:51-65 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×11
  • Duplicated block (8 lines × 3) ArcFormats/Cherry/ArcMyk.cs:69 — ArcFormats/Cherry/ArcMyk.cs:69-76 | ArcFormats/FC01/ArcMRG0.cs:56-63 | Legacy/Aaru/ArcDL1.cs:63-70 — 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 `ArcFormats/Cherry/ArcMyk.cs:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 3) Legacy/Asura/ArcPAK.cs:64 — Legacy/Asura/ArcPAK.cs:64-71 | Legacy/Yaneurao/ArcDAT.cs:76-83 | Legacy/Yaneurao/ArcDAT.cs:126-133 — before extracting anything, compare `Legacy/Asura/ArcPAK.cs` and `Legacy/Yaneurao/ArcDAT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Asura/ArcPAK.cs:64` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Legacy/Yaneurao/ArcDAT.cs:87` calls `CreateStream` and `Legacy/Asura/ArcPAK.cs:75` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 3) ArcFormats/AliceSoft/ArcAFA.cs:92 — ArcFormats/AliceSoft/ArcAFA.cs:92-99 | ArcFormats/Carriere/ArcARC.cs:105-112 | ArcFormats/CsWare/ArcDAT.cs:66-73 — 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 `ArcFormats/AliceSoft/ArcAFA.cs:92` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) ArcFormats/Cmvs/ArcCPZ1.cs:56 — ArcFormats/Cmvs/ArcCPZ1.cs:56-63 | ArcFormats/Cmvs/ArcCPZ2.cs:57-64 | ArcFormats/Cmvs/ArcCPZ3.cs:57-64 — before extracting anything, compare `ArcFormats/Cmvs/ArcCPZ2.cs` and `ArcFormats/Cmvs/ArcCPZ3.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cmvs/ArcCPZ1.cs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 × 3) ArcFormats/BlueGale/ArcSNN.cs:65 — ArcFormats/BlueGale/ArcSNN.cs:65-72 | ArcFormats/Ffa/ArcBlackPackage.cs:68-75 | ArcFormats/Ucom/ArcDATA.cs:74-81 — before extracting anything, compare `ArcFormats/BlueGale/ArcSNN.cs` and `ArcFormats/Ucom/ArcDATA.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/BlueGale/ArcSNN.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) ArcFormats/Tanaka/ArcARC0.cs:49 — ArcFormats/Tanaka/ArcARC0.cs:49-56 | ArcFormats/Tanaka/ArcBMX.cs:48-55 | ArcFormats/Tanaka/ArcWRC.cs:48-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Tanaka/ArcWRC.cs:56` calls `ReadUInt32` and `ArcFormats/Tanaka/ArcARC0.cs:57` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 3) Legacy/Dice/ArcRLZ.cs:47 — Legacy/Dice/ArcRLZ.cs:47-54 | Legacy/Tigerman/ArcPAC.cs:51-58 | Legacy/Uran/ArcPHS.cs:45-52 — before extracting anything, compare `Legacy/Tigerman/ArcPAC.cs` and `Legacy/Uran/ArcPHS.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Dice/ArcRLZ.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Tigerman/ArcPAC.cs:48` calls `ReadInt32` and `Legacy/Dice/ArcRLZ.cs:45` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 3) ArcFormats/Kid/ImageBIP.cs:211 — ArcFormats/Kid/ImageBIP.cs:211-218 | ArcFormats/Kid/ImageBIP.cs:248-255 | ArcFormats/Kid/ImageLBG.cs:87-94 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Kid/ImageLBG.cs:87` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) ArcFormats/Psp/ArcQPK.cs:83 — ArcFormats/Psp/ArcQPK.cs:83-90 | ArcFormats/SoftwareHouseParsley/ArcCG3.cs:84-91 | Legacy/SquadraD/ArcPLA.cs:98-105 — 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 `ArcFormats/Psp/ArcQPK.cs:83` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8 lines × 3) ArcFormats/Kid/ArcDAT.cs:51 — ArcFormats/Kid/ArcDAT.cs:51-58 | ArcFormats/VnSystem/ArcVFS.cs:46-54 | ArcFormats/Youkai/ArcDAT.cs:97-105 — 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 `ArcFormats/Kid/ArcDAT.cs:51` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/VnSystem/ArcVFS.cs:43` calls `AsciiEqual`, `ReadInt32` and `ArcFormats/Kid/ArcDAT.cs:50` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 3) ArcFormats/Cyberworks/ImageTINK.cs:473 — ArcFormats/Cyberworks/ImageTINK.cs:473-480 | ArcFormats/Kaguya/ArcAN21.cs:238-245 | ArcFormats/Kaguya/ArcANM.cs:342-349 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Kaguya/ArcAN21.cs:247` calls `Dispose` and `ArcFormats/Kaguya/ArcANM.cs:350` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D3 · God Classes · ClassTooLong · ×10
  • ClassTooLong: AllOpener Legacy/Giga/ArcALL.cs — ClassTooLong — 2008 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 1608 over it, 5.02× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: Palettes ArcFormats/Macromedia/Palettes.cs — ClassTooLong — 1286 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 886 over it, 3.22× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: YkOpener Legacy/Koei/ArcYK.cs — ClassTooLong — 984 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 584 over it, 2.46× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: TlgFormat ArcFormats/KiriKiri/ImageTLG.cs — ClassTooLong — 886 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 486 over it, 2.22× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: PcmDecoder ArcFormats/Circus/AudioPCM.cs — ClassTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 204 over it, 1.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: WbmReader ArcFormats/WildBug/ImageWBM.cs — ClassTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 174 over it, 1.44× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: MioDecoder ArcFormats/Entis/MioDecoder.cs — ClassTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 146 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: GCmpDecoder Legacy/Nekotaro/ImageGCmp.cs — ClassTooLong — 486 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 86 over it, 1.22× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Xp3Opener ArcFormats/KiriKiri/ArcXP3.cs — ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 69 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Reader ArcFormats/Ffa/ImagePT1.cs — ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 9 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×10
  • Duplicated block (7 lines × 3) ArcFormats/ArcARCX.cs:50 — ArcFormats/ArcARCX.cs:50-56 | ArcFormats/Bishop/ArcPK.cs:45-51 | ArcFormats/EntExec/ArcCAB.cs:45-51 — before extracting anything, compare `ArcFormats/ArcARCX.cs` and `ArcFormats/Bishop/ArcPK.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/ArcARCX.cs:50` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/EntExec/ArcCAB.cs:42` calls `AsciiEqual` and `ArcFormats/ArcARCX.cs:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) ArcFormats/Cyberworks/ArcP8.cs:45 — ArcFormats/Cyberworks/ArcP8.cs:45-51 | ArcFormats/Leaf/ArcLAC.cs:48-54 | ArcFormats/Slg/ArcSZS.cs:48-54 — before extracting anything, compare `ArcFormats/Cyberworks/ArcP8.cs` and `ArcFormats/Slg/ArcSZS.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cyberworks/ArcP8.cs:45` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Cyberworks/ArcP8.cs:42` calls `HasExtension` and `ArcFormats/Leaf/ArcLAC.cs:46` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) REDACTED:64 — REDACTED:64-70 | Legacy/Tigerman/ArcPAC.cs:52-58 | Legacy/Uran/ArcPHS.cs:46-52 — before extracting anything, compare `Legacy/Tigerman/ArcPAC.cs` and `Legacy/Uran/ArcPHS.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:64` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:62` calls `ReadString`, `All` and `Legacy/Tigerman/ArcPAC.cs:51` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) ArcFormats/AdvDx/ArcPKD.cs:69 — ArcFormats/AdvDx/ArcPKD.cs:69-75 | ArcFormats/Yatagarasu/ArcPKG.cs:63-69 | Legacy/KeroQ/ArcDAT.cs:66-72 — 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 `ArcFormats/AdvDx/ArcPKD.cs:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/AdvDx/ArcPKD.cs:67` calls `IsNullOrWhiteSpace` and `ArcFormats/Yatagarasu/ArcPKG.cs:62` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) ArcFormats/Kaguya/ArcANM.cs:124 — ArcFormats/Kaguya/ArcANM.cs:124-130 | ArcFormats/Kaguya/ArcANM.cs:188-194 | ArcFormats/Kaguya/ArcPLT.cs:53-59 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Kaguya/ArcANM.cs:124` 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 × 3) ArcFormats/Tanaka/ArcWRC.cs:57 — ArcFormats/Tanaka/ArcWRC.cs:57-63 | ArcFormats/Youkai/ArcDAT.cs:56-62 | ArcFormats/Youkai/ArcDAT.cs:188-194 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Tanaka/ArcWRC.cs:57` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Tanaka/ArcWRC.cs:56` calls `ReadUInt32` and `ArcFormats/Youkai/ArcDAT.cs:55` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) ArcFormats/Emic/ArcPACK.cs:95 — ArcFormats/Emic/ArcPACK.cs:95-101 | ArcFormats/Yatagarasu/ArcPKG.cs:63-69 | Legacy/KeroQ/ArcDAT.cs:66-72 — 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 `ArcFormats/Emic/ArcPACK.cs:95` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Emic/ArcPACK.cs:103` calls `EmicArchive` and `Legacy/KeroQ/ArcDAT.cs:73` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) ArcFormats/Carriere/ArcARC.cs:55 — ArcFormats/Carriere/ArcARC.cs:55-61 | Legacy/Asura/ArcPAK.cs:60-66 | Legacy/Mink/ArcBINZ.cs:56-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 3) ArcFormats/Risa/ImageSYG.cs:74 — ArcFormats/Risa/ImageSYG.cs:74-80 | ArcFormats/Tail/ImageCFP.cs:143-149 | Legacy/Nabe/ImageYPF.cs:75-81 — 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 `ArcFormats/Risa/ImageSYG.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 3) ArcFormats/Taskforce/ArcDAT.cs:56 — ArcFormats/Taskforce/ArcDAT.cs:56-62 | Legacy/Yaneurao/ArcDAT.cs:72-78 | Legacy/Yaneurao/ArcDAT.cs:122-128 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. 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.
IC1 · Incompleteness & stubs · Unfinished stub · ×10
  • Unfinished stub — throws NotImplementedException ArcFormats/CatSystem/ImageHG3.cs:104 — `Image` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException REDACTED:413 — `Unpack` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Gss/ArcARC.cs:139 — `OpenImage` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Ice/ScriptISD.cs:53 — `ConvertBack` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/KiriKiri/HxCrypt.cs:301 — `Encrypt` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/KiriKiri/HxCryptLite.cs:104 — `Encrypt` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Ps1/ImageTIM.cs:191 — `Write` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/Psp/ArcGim.cs:230 — `Write` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/ShiinaRio/WarcEncryption.cs:1347 — `Encrypt` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException ArcFormats/ShiinaRio/WarcEncryption.cs:1380 — `Encrypt` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×9
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ArcFormats/Cyberworks/ImageDATA.cs:137 — ArcFormats/Cyberworks/ImageDATA.cs:137-187 | ArcFormats/Cyberworks/ImageDATA.cs:190-228 | ArcFormats/Cyberworks/ImageDATA.cs:231-261 | ArcFormats/Cyberworks/ImageDATA.cs:267-309 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ArcFormats/Cri/ImageSPC.cs:46 — ArcFormats/Cri/ImageSPC.cs:46-55 | ArcFormats/DigitalWorks/ImageTM2arc.cs:22-39 | ArcFormats/Kid/ImageBIParc.cs:21-30 | ArcFormats/Kid/ImageSPC.cs:19-28 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ArcFormats/Cri/ImageSPC.cs:58 — ArcFormats/Cri/ImageSPC.cs:58-64 | ArcFormats/DigitalWorks/ImageTM2arc.cs:41-47 | ArcFormats/Kid/ImageBIParc.cs:32-38 | ArcFormats/Kid/ImageSPC.cs:31-37 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ArcFormats/ScrPlayer/ImageI.cs:137 — ArcFormats/ScrPlayer/ImageI.cs:137-187 | ArcFormats/ScrPlayer/ImageI.cs:190-253 | ArcFormats/ScrPlayer/ImageIMG.cs:100-185 | ArcFormats/ScrPlayer/ImageIMG.cs:188-282 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ArcFormats/Kaguya/ArcANM.cs:117 — ArcFormats/Kaguya/ArcANM.cs:117-143 | ArcFormats/Kaguya/ArcANM.cs:181-208 | ArcFormats/Kaguya/ArcANM.cs:247-273 | ArcFormats/Kaguya/ArcPLT.cs:47-73 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ArcFormats/Kaguya/ArcLIN2.cs:43 — ArcFormats/Kaguya/ArcLIN2.cs:43-77 | ArcFormats/Palette/ArcPAK.cs:47-74 | ArcFormats/Palette/ArcPAK2.cs:48-77 | ArcFormats/Sohfu/ArcSKA.cs:43-73 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ArcFormats/FlyingShine/ArcPD.cs:300 — ArcFormats/FlyingShine/ArcPD.cs:300-331 | ArcFormats/Leaf/ArcA.cs:53-79 | ArcFormats/MOONSTONE/ArcPAK.cs:42-67 | Legacy/PenguinWorks/ArcDAT.cs:39-61 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) ArcFormats/Entis/EriReader.cs:1093 — ArcFormats/Entis/EriReader.cs:1093-1115 | ArcFormats/Entis/EriReader.cs:1118-1140 | ArcFormats/Entis/EriReader.cs:1179-1202 | ArcFormats/Entis/EriReader.cs:1205-1227 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Legacy/Adviz/ImageGIZ.cs:281 — Legacy/Adviz/ImageGIZ.cs:281-292 | Legacy/Discovery/ImagePR1.cs:330-341 | Legacy/Grocer/ImagePIC.cs:180-191 | Legacy/Ponytail/ImageTSZ.cs:286-297 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×9
  • Edited copy of a member (26 corresponding lines) ArcFormats/BlackRainbow/ArcCCF.cs:48 — ArcFormats/BlackRainbow/ArcCCF.cs:48-74 | ArcFormats/BlackRainbow/ArcSPPAK.cs:65-90 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) ArcFormats/Ffa/ArcBlackPackage.cs:50 — ArcFormats/Ffa/ArcBlackPackage.cs:50-75 | ArcFormats/BlackCyc/ArcVPK.cs:44-75 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) ArcFormats/Circus/ArcPCK.cs:48 — ArcFormats/Circus/ArcPCK.cs:48-76 | ArcFormats/Youkai/ArcDAT.cs:178-203 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) ArcFormats/Valkyria/ArcDAT.cs:45 — ArcFormats/Valkyria/ArcDAT.cs:45-70 | ArcFormats/VnSystem/ArcVFS.cs:42-67 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) ArcFormats/Triangle/ArcDAT.cs:43 — ArcFormats/Triangle/ArcDAT.cs:43-68 | ArcFormats/Youkai/ArcDAT.cs:137-165 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) ArcFormats/Banana/ImageGEC.cs:255 — ArcFormats/Banana/ImageGEC.cs:255-280 | ArcFormats/elf/ImageGCC.cs:285-311 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) ArcFormats/Seraphim/ArcMC.cs:43 — ArcFormats/Seraphim/ArcMC.cs:43-68 | ArcFormats/BlueGale/VideoAMV.cs:49-79 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) ArcFormats/Cyberworks/ImageTINK.cs:291 — ArcFormats/Cyberworks/ImageTINK.cs:291-316 | ArcFormats/Cyberworks/ImageTINK.cs:391-416 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) ArcFormats/RealLive/ArcSEEN.cs:93 — ArcFormats/RealLive/ArcSEEN.cs:93-118 | Legacy/Ponytail/ArcBND.cs:96-123 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×9
  • Edited copy of a member (15 corresponding lines) ArcFormats/Liar/ImageLIM.cs:226 — ArcFormats/Liar/ImageLIM.cs:226-240 | ArcFormats/LiveMaker/ImageGAL.cs:505-522 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Legacy/Nekotaro/ImageNCG.cs:307 — Legacy/Nekotaro/ImageNCG.cs:307-321 | Legacy/Adv98/ImageGPC.cs:221-237 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) ArcFormats/TopCat/ArcTCD3.cs:381 — ArcFormats/TopCat/ArcTCD3.cs:381-395 | ArcFormats/TopCat/ArcTCD3.cs:416-431 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) ArcFormats/ShiinaRio/WarcEncryption.cs:1233 — ArcFormats/ShiinaRio/WarcEncryption.cs:1233-1247 | ArcFormats/ShiinaRio/WarcEncryption.cs:1266-1280 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) ArcFormats/Musica/ArcPAK.cs:152 — ArcFormats/Musica/ArcPAK.cs:152-166 | ArcFormats/CommonStreams.cs:593-607 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) ArcFormats/Circus/ImageCRX.cs:176 — ArcFormats/Circus/ImageCRX.cs:176-190 | ArcFormats/Circus/ImageCRX.cs:425-442 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) ArcFormats/Hypatia/AudioADP.cs:105 — ArcFormats/Hypatia/AudioADP.cs:105-120 | Legacy/CrossNet/AudioADP.cs:130-144 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Legacy/Types/ImageTPGF.cs:134 — Legacy/Types/ImageTPGF.cs:134-151 | Legacy/Types/ImageTPGF.cs:170-184 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Legacy/Mermaid/ImageMG1.cs:53 — Legacy/Mermaid/ImageMG1.cs:53-70 | Legacy/ProjectMyu/ImageKGR.cs:40-54 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×9
  • Duplicated block (5 lines × 3) ArcFormats/Abel/ArcBIN.cs:64 — ArcFormats/Abel/ArcBIN.cs:64-68 | ArcFormats/Leaf/ArcLEAF.cs:103-107 | ArcFormats/Morning/ArcPAK.cs:68-72 — 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 `ArcFormats/Abel/ArcBIN.cs:64` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 3) ArcFormats/EntExec/ArcCAB.cs:58 — ArcFormats/EntExec/ArcCAB.cs:58-62 | ArcFormats/MAGES/ArcMPK.cs:58-62 | ArcFormats/MAGES/ArcMPK.cs:74-78 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/EntExec/ArcCAB.cs:58` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 3) ArcFormats/Ipac/ArcIPAC.cs:53 — ArcFormats/Ipac/ArcIPAC.cs:53-57 | ArcFormats/Sohfu/ArcSKA.cs:64-68 | Legacy/Nug/ArcDAT.cs:59-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 3) ArcFormats/Primel/Encryption.cs:171 — ArcFormats/Primel/Encryption.cs:171-175 | ArcFormats/Primel/Encryption.cs:221-225 | ArcFormats/Primel/Encryption.cs:287-291 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Primel/Encryption.cs:171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 3) Legacy/Mutation/ArcDPF.cs:51 — Legacy/Mutation/ArcDPF.cs:51-55 | Legacy/Tigerman/ArcPAC.cs:56-60 | Legacy/Uran/ArcPHS.cs:50-54 — before extracting anything, compare `Legacy/Tigerman/ArcPAC.cs` and `Legacy/Uran/ArcPHS.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Mutation/ArcDPF.cs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 3) ArcFormats/Cadath/ArcKAR.cs:58 — ArcFormats/Cadath/ArcKAR.cs:58-62 | ArcFormats/Succubus/ArcARC.cs:58-62 | Legacy/ApplePie/ArcARC.cs:58-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/ApplePie/ArcARC.cs:56` calls `IsNullOrEmpty` and `ArcFormats/Cadath/ArcKAR.cs:57` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) ArcFormats/DirectDraw/DxtDecoder.cs:107 — ArcFormats/DirectDraw/DxtDecoder.cs:107-111 | ArcFormats/DirectDraw/DxtDecoder.cs:151-155 | ArcFormats/DirectDraw/DxtDecoder.cs:189-194 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/DirectDraw/DxtDecoder.cs:107` 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 × 3) ArcFormats/CaramelBox/ImageFCB.cs:136 — ArcFormats/CaramelBox/ImageFCB.cs:136-140 | ArcFormats/CaramelBox/ImageFCB.cs:146-150 | ArcFormats/CaramelBox/ImageFCB.cs:156-160 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 3) ArcFormats/Cmvs/ImageMSK.cs:56 — ArcFormats/Cmvs/ImageMSK.cs:56-60 | ArcFormats/FC01/ImageWMK.cs:53-57 | Legacy/Pan/ImageTBL.cs:50-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×8
  • Edited copy of a member (24 corresponding lines) Legacy/Aquarium/ArcAAP.cs:43 — Legacy/Aquarium/ArcAAP.cs:43-66 | Legacy/Yaneurao/ArcDAT.cs:54-83 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) ArcFormats/NipponIchi/ArcPSFS.cs:17 — ArcFormats/NipponIchi/ArcPSFS.cs:17-40 | ArcFormats/FlyingShine/ArcPD.cs:60-84 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) ArcFormats/SuperNekoX/ArcGPC.cs:50 — ArcFormats/SuperNekoX/ArcGPC.cs:50-73 | Legacy/RSystem/ArcRAD.cs:43-68 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) ArcFormats/AdvSys/ImageGWD.cs:214 — ArcFormats/AdvSys/ImageGWD.cs:214-241 | Legacy/Types/ImageTPGF.cs:227-250 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) ArcFormats/Kid/ImagePRT.cs:134 — ArcFormats/Kid/ImagePRT.cs:134-157 | ArcFormats/Kid/ImagePRT.cs:160-184 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) ArcFormats/Xuse/ArcNT.cs:49 — ArcFormats/Xuse/ArcNT.cs:49-73 | ArcFormats/Xuse/ArcNT.cs:114-137 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) ArcFormats/Primel/ImageGBC.cs:262 — ArcFormats/Primel/ImageGBC.cs:262-285 | ArcFormats/Primel/ImageGBC.cs:288-319 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) ArcFormats/Qlie/Encryption.cs:113 — ArcFormats/Qlie/Encryption.cs:113-136 | ArcFormats/Qlie/Encryption.cs:167-190 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×8
  • Edited copies of one member (3 members, 8+ corresponding lines) ArcFormats/Morning/ArcTTD.cs:73 — ArcFormats/Morning/ArcTTD.cs:73-80 | Legacy/Alterna/ArcBIN.cs:91-99 | Legacy/Rain/ArcBIN.cs:83-91 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) ArcFormats/Cmvs/ArcCPZ2.cs:78 — ArcFormats/Cmvs/ArcCPZ2.cs:78-87 | ArcFormats/GsPack/ArcGsPack.cs:137-144 | Legacy/Rune/ArcYK.cs:101-108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) ArcFormats/ImageLZ.cs:47 — ArcFormats/ImageLZ.cs:47-57 | ArcFormats/ImageLZ.cs:60-70 | Legacy/System21/ImageBET.cs:100-107 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) ArcFormats/Key/AudioOGGPAK.cs:39 — ArcFormats/Key/AudioOGGPAK.cs:39-46 | Legacy/Harvest/AudioBGM.cs:39-54 | Legacy/Harvest/AudioSED.cs:44-59 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) ArcFormats/KiriKiri/CryptAlgorithms.cs:413 — ArcFormats/KiriKiri/CryptAlgorithms.cs:413-421 | ArcFormats/Mnp/ArcMMA.cs:175-182 | ArcFormats/Mnp/ArcMMA.cs:439-446 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) ArcFormats/Ankh/ArcGRP.cs:245 — ArcFormats/Ankh/ArcGRP.cs:245-252 | ArcFormats/Propeller/ArcMGR.cs:94-101 | Legacy/Rare/ArcX.cs:91-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) ArcFormats/Escude/ArcBIN.cs:138 — ArcFormats/Escude/ArcBIN.cs:138-147 | ArcFormats/Morning/ArcTTD.cs:83-90 | REDACTED:158-165 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) ArcFormats/Musica/ArcPAK.cs:140 — ArcFormats/Musica/ArcPAK.cs:140-147 | Legacy/Uran/ArcNCL.cs:127-134 | Legacy/Yaneurao/ImageGTO.cs:93-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×8
  • Edited copy of a member (5 corresponding lines) ArcFormats/Carriere/ImageCGD.cs:50 — ArcFormats/Carriere/ImageCGD.cs:50-54 | ArcFormats/GameSystem/ImageALP.cs:55-59 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) ArcFormats/ScenePlayer/AudioPMW.cs:69 — ArcFormats/ScenePlayer/AudioPMW.cs:69-73 | ArcFormats/ScenePlayer/ImagePMP.cs:43-47 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) ArcFormats/Ucom/ImageGPC.cs:71 — ArcFormats/Ucom/ImageGPC.cs:71-75 | Legacy/Uncanny/ImageCII.cs:80-84 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) ArcFormats/TamaSoft/ImageBTN.cs:65 — ArcFormats/TamaSoft/ImageBTN.cs:65-70 | Legacy/YellowCap/ImageGEF.cs:56-60 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) ArcFormats/Banana/ImageGEC.cs:74 — ArcFormats/Banana/ImageGEC.cs:74-78 | ArcFormats/uGOS/ImageBMP.cs:73-77 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) GameRes/ImageBMP.cs:102 — GameRes/ImageBMP.cs:102-106 | GameRes/ImageJPEG.cs:69-74 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) ArcFormats/SoftwareHouseParsley/ArcCG2.cs:89 — ArcFormats/SoftwareHouseParsley/ArcCG2.cs:89-93 | Legacy/Weapon/ArcDAT.cs:87-92 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) ArcFormats/KiriKiri/HxCryptLite.cs:54 — ArcFormats/KiriKiri/HxCryptLite.cs:54-58 | ArcFormats/KiriKiri/CryptAlgorithms.cs:63-67 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×8
  • Duplicated block (16 lines × 2) Legacy/System98/ImageG.cs:152 — Legacy/System98/ImageG.cs:152-167 | Legacy/Ucom/ImageUG.cs:139-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. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/System98/ImageG.cs:152` 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) ArcFormats/Aoi/ArcBOX.cs:97 — ArcFormats/Aoi/ArcBOX.cs:97-112 | ArcFormats/Seraphim/ArcVoice.cs:103-118 — 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 `ArcFormats/Aoi/ArcBOX.cs:97` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) ArcFormats/WildBug/AudioWWA.cs:149 — ArcFormats/WildBug/AudioWWA.cs:149-164 | ArcFormats/WildBug/AudioWWA.cs:211-226 — 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 `ArcFormats/WildBug/AudioWWA.cs:149` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) ArcFormats/Artdink/ImageFAC.cs:86 — ArcFormats/Artdink/ImageFAC.cs:86-101 | ArcFormats/Artdink/ImageTXF.cs:95-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Artdink/ImageFAC.cs:86` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (16 lines × 2) ArcFormats/Xuse/ArcNT.cs:58 — ArcFormats/Xuse/ArcNT.cs:58-73 | ArcFormats/Xuse/ArcNT.cs:122-137 — 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 `ArcFormats/Xuse/ArcNT.cs:58` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) ArcFormats/Littlewitch/ArcDAT.cs:90 — ArcFormats/Littlewitch/ArcDAT.cs:90-105 | ArcFormats/Littlewitch/ArcDAT.cs:123-138 — 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 `ArcFormats/Littlewitch/ArcDAT.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. 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) ArcFormats/Winters/ArcCFP.cs:58 — ArcFormats/Winters/ArcCFP.cs:58-73 | ArcFormats/Winters/ArcDAT.cs:60-75 — before extracting anything, compare `ArcFormats/Winters/ArcCFP.cs` and `ArcFormats/Winters/ArcDAT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Winters/ArcCFP.cs:58` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) Legacy/Ponytail/ImageTSZ.cs:313 — Legacy/Ponytail/ImageTSZ.cs:313-328 | Legacy/System98/ImageG.cs:300-315 — 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 `Legacy/Ponytail/ImageTSZ.cs:313` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×7
  • Edited copy of a member (28 corresponding lines) ArcFormats/DirectDraw/DxtDecoder.cs:88 — ArcFormats/DirectDraw/DxtDecoder.cs:88-119 | ArcFormats/DirectDraw/DxtDecoder.cs:136-163 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) ArcFormats/Scoop/ArcGX.cs:49 — ArcFormats/Scoop/ArcGX.cs:49-79 | ArcFormats/DenSDK/ArcDAF.cs:50-77 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Legacy/Mmfass/ArcSDA.cs:48 — Legacy/Mmfass/ArcSDA.cs:48-76 | Legacy/SquadraD/ArcSDA.cs:48-75 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) ArcFormats/ShiinaRio/ArcWARC1.0.cs:46 — ArcFormats/ShiinaRio/ArcWARC1.0.cs:46-76 | Legacy/Unknown/ArcAQA.cs:46-73 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) ArcFormats/ActiveSoft/ArcADPACK.cs:49 — ArcFormats/ActiveSoft/ArcADPACK.cs:49-77 | ArcFormats/ArcIKS.cs:50-77 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) ArcFormats/Kaguya/ArcKaguya.cs:102 — ArcFormats/Kaguya/ArcKaguya.cs:102-134 | ArcFormats/Kaguya/ArcKaguya.cs:137-164 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) ArcFormats/Softpal/ImagePGD.cs:389 — ArcFormats/Softpal/ImagePGD.cs:389-416 | ArcFormats/Softpal/ImagePGD.cs:419-448 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×7
  • Edited copy of a member (18 corresponding lines) ArcFormats/KiriKiri/CryptAlgorithms.cs:1482 — ArcFormats/KiriKiri/CryptAlgorithms.cs:1482-1499 | ArcFormats/KiriKiri/CryptAlgorithms.cs:1502-1519 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) ArcFormats/Artdink/ImageFAC.cs:84 — ArcFormats/Artdink/ImageFAC.cs:84-101 | ArcFormats/Artdink/ImageTXF.cs:93-110 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) ArcFormats/MangaGamer/ArcSHA.cs:42 — ArcFormats/MangaGamer/ArcSHA.cs:42-61 | ArcFormats/WildBug/ArcWBP.cs:68-85 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Experimental/RPGMaker/AudioRPGMV.cs:44 — Experimental/RPGMaker/AudioRPGMV.cs:44-61 | Experimental/RPGMaker/ImageRPGMV.cs:53-82 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) ArcFormats/Leaf/ImageLFB.cs:227 — ArcFormats/Leaf/ImageLFB.cs:227-244 | ArcFormats/Leaf/ImageLFB.cs:310-329 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) ArcFormats/Foster/ArcFA2.cs:226 — ArcFormats/Foster/ArcFA2.cs:226-244 | ArcFormats/ShiinaRio/ImageMI4.cs:131-148 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) ArcFormats/Seraphim/ArcVoice.cs:101 — ArcFormats/Seraphim/ArcVoice.cs:101-118 | ArcFormats/Aoi/ArcBOX.cs:95-112 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×7
  • Duplicated block (9–10 lines × 2) ArcFormats/BellDa/ArcDAT.cs:60 — ArcFormats/BellDa/ArcDAT.cs:60-68 | ArcFormats/Ipac/ArcIPAC.cs:45-54 — 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 `ArcFormats/BellDa/ArcDAT.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/BellDa/ArcDAT.cs:59` calls `ReadUInt32` and `ArcFormats/Ipac/ArcIPAC.cs:45` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9–10 lines × 2) ArcFormats/MicroVision/ArcGSD.cs:43 — ArcFormats/MicroVision/ArcGSD.cs:43-51 | ArcFormats/SHSystem/ArcHXP.cs:52-61 — 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 `ArcFormats/MicroVision/ArcGSD.cs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–10 lines × 2) ArcFormats/Entis/MioDecoder.cs:524 — ArcFormats/Entis/MioDecoder.cs:524-532 | ArcFormats/Entis/MioDecoder.cs:574-583 — 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 `ArcFormats/Entis/MioDecoder.cs:524` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Entis/MioDecoder.cs:524` calls `Copy` and `ArcFormats/Entis/MioDecoder.cs:574` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9–10 lines × 2) Legacy/Aaru/ArcDL1.cs:53 — Legacy/Aaru/ArcDL1.cs:53-61 | Legacy/Asura/ArcPAK.cs:52-61 — 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 `Legacy/Aaru/ArcDL1.cs:53` 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 (9–10 lines × 2) Legacy/Mink/ArcBINZ.cs:44 — Legacy/Mink/ArcBINZ.cs:44-53 | Legacy/Rhss/ArcCRG.cs:43-51 — 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 `Legacy/Mink/ArcBINZ.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 2) Legacy/Clio/ArcPAC.cs:49 — Legacy/Clio/ArcPAC.cs:49-57 | Legacy/Mink/ArcMINK.cs:56-65 — 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 `Legacy/Clio/ArcPAC.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. 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–10 lines × 2) Legacy/Gsx/ArcK3.cs:44 — Legacy/Gsx/ArcK3.cs:44-52 | Legacy/Tigerman/ArcPAC.cs:48-57 — 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.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×6
  • Edited copy of a member (39 corresponding lines) ArcFormats/DxLib/ArcDX8.cs:290 — ArcFormats/DxLib/ArcDX8.cs:290-343 | ArcFormats/DxLib/ArcDX.cs:502-540 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) ArcFormats/Softpal/ArcVAFS.cs:207 — ArcFormats/Softpal/ArcVAFS.cs:207-253 | ArcFormats/Softpal/ArcVAFS.cs:256-294 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) ArcFormats/MicroVision/ArcARC.cs:96 — ArcFormats/MicroVision/ArcARC.cs:96-134 | ArcFormats/Kaguya/ArcLIN2.cs:94-142 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) ArcFormats/Scoop/ImageSCP.cs:82 — ArcFormats/Scoop/ImageSCP.cs:82-120 | ArcFormats/Triangle/ImageTRI.cs:87-125 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) ArcFormats/Lambda/ArcLAX.cs:165 — ArcFormats/Lambda/ArcLAX.cs:165-203 | Legacy/System98/ArcLIB.cs:101-139 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) ArcFormats/HuneX/ImageCBG.cs:176 — ArcFormats/HuneX/ImageCBG.cs:176-214 | ArcFormats/Ethornell/ImageCBG.cs:211-249 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×6
  • Edited copy of a member (30 corresponding lines) ArcFormats/Cmvs/ArcCPZ.cs:272 — ArcFormats/Cmvs/ArcCPZ.cs:272-301 | ArcFormats/Cmvs/ArcCPZ.cs:304-333 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) ArcFormats/MersenneTwister.cs:46 — ArcFormats/MersenneTwister.cs:46-75 | ArcFormats/Qlie/QlieMersenneTwister.cs:65-94 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) ArcFormats/Abel/ArcARC.cs:52 — ArcFormats/Abel/ArcARC.cs:52-85 | ArcFormats/CsWare/ArcDAT.cs:44-73 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) ArcFormats/Cmvs/ArcCPZ2.cs:90 — ArcFormats/Cmvs/ArcCPZ2.cs:90-120 | ArcFormats/Cmvs/ArcCPZ3.cs:92-121 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) ArcFormats/Kogado/ArcARC.cs:160 — ArcFormats/Kogado/ArcARC.cs:160-192 | ArcFormats/Kogado/ArcARC.cs:195-224 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) ArcFormats/DDSystem/ArcDDP.cs:157 — ArcFormats/DDSystem/ArcDDP.cs:157-190 | ArcFormats/SHSystem/ArcHXP.cs:148-177 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×6
  • Edited copy of a member (22 corresponding lines) ArcFormats/StudioEgo/ArcEGO.cs:46 — ArcFormats/StudioEgo/ArcEGO.cs:46-67 | ArcFormats/StudioEgo/ArcEGO.cs:159-180 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Legacy/Mina/ArcPAK.cs:134 — Legacy/Mina/ArcPAK.cs:134-155 | Legacy/WestGate/ArcUWF.cs:63-87 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Legacy/Mina/ArcPAK.cs:173 — Legacy/Mina/ArcPAK.cs:173-194 | Legacy/Uma/ArcCDT.cs:50-73 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) ArcFormats/HuneX/ImageCBG.cs:217 — ArcFormats/HuneX/ImageCBG.cs:217-238 | ArcFormats/Ethornell/ImageCBG.cs:252-273 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) ArcFormats/Cherry/ImageGRP.cs:64 — ArcFormats/Cherry/ImageGRP.cs:64-85 | ArcFormats/Cherry/ImageGRP.cs:107-131 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) ArcFormats/Cyberworks/ArcDATA.cs:108 — ArcFormats/Cyberworks/ArcDATA.cs:108-130 | ArcFormats/Cyberworks/ArcDAT.cs:298-319 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×6
  • Edited copy of a member (17 corresponding lines) Legacy/Pias/EncryptedGraphDat.cs:151 — Legacy/Pias/EncryptedGraphDat.cs:151-170 | Legacy/Pias/ArcDAT.cs:159-175 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) ArcFormats/Basil/AudioWHC.cs:44 — ArcFormats/Basil/AudioWHC.cs:44-60 | Legacy/Pan/AudioNSF.cs:46-63 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) ArcFormats/KiriKiri/ArcXP3.cs:834 — ArcFormats/KiriKiri/ArcXP3.cs:834-852 | Legacy/Pinky/ArcA5R.cs:218-234 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Legacy/Broccoli/ArcP00.cs:94 — Legacy/Broccoli/ArcP00.cs:94-110 | Legacy/Broccoli/ArcP00.cs:231-247 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) ArcFormats/Ice/ImageIBM.cs:48 — ArcFormats/Ice/ImageIBM.cs:48-67 | ArcFormats/Triangle/ImageTRI.cs:48-64 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Legacy/Gsx/ImageK4.cs:50 — Legacy/Gsx/ImageK4.cs:50-66 | ArcFormats/Vitamin/ImageSBI.cs:55-71 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×6
  • Duplicated block (9 lines × 3) ArcFormats/NekoNyan/ArcDAT.cs:270 — ArcFormats/NekoNyan/ArcDAT.cs:270-278 | ArcFormats/NekoNyan/ArcDAT.cs:344-352 | ArcFormats/NekoNyan/ArcDAT.cs:394-402 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/NekoNyan/ArcDAT.cs:270` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) ArcFormats/Abogado/ArcPAK.cs:57 — ArcFormats/Abogado/ArcPAK.cs:57-65 | ArcFormats/Slg/ArcSZS.cs:49-57 | ArcFormats/SoftwareHouseParsley/ArcCG.cs:63-71 — 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 `ArcFormats/Abogado/ArcPAK.cs:57` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/SoftwareHouseParsley/ArcCG.cs:61` calls `ReadInt32` and `ArcFormats/Slg/ArcSZS.cs:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 3) ArcFormats/Emote/ArcPSB.cs:786 — ArcFormats/Emote/ArcPSB.cs:786-794 | ArcFormats/Emote/ArcPSB.cs:807-815 | ArcFormats/Emote/ArcPSB.cs:829-837 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Emote/ArcPSB.cs:786` 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 × 3) ArcFormats/Cromwell/ArcPAK.cs:58 — ArcFormats/Cromwell/ArcPAK.cs:58-67 | ArcFormats/Nekopunch/ArcPAK.cs:52-60 | ArcFormats/Slg/ArcSZS.cs:49-58 — 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 `ArcFormats/Cromwell/ArcPAK.cs:58` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Nekopunch/ArcPAK.cs:52` calls `ReadInt32` and `ArcFormats/Slg/ArcSZS.cs:49` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 3) ArcFormats/rUGP/ImageRIP.cs:377 — ArcFormats/rUGP/ImageRIP.cs:377-385 | ArcFormats/rUGP/ImageRIP.cs:413-421 | ArcFormats/rUGP/ImageRIP.cs:449-457 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/rUGP/ImageRIP.cs:377` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) ArcFormats/Sas5/ArcWAR.cs:177 — ArcFormats/Sas5/ArcWAR.cs:177-185 | Legacy/BlackButterfly/ArcDAT.cs:59-67 | Legacy/Weapon/ArcVoice.cs:66-74 — 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 `ArcFormats/Sas5/ArcWAR.cs:177` 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.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×6
  • Duplicated block (6 lines × 4) ArcFormats/Cherry/ArcMyk.cs:69 — ArcFormats/Cherry/ArcMyk.cs:69-74 | ArcFormats/FC01/ArcMRG0.cs:56-61 | ArcFormats/Maika/ArcMIK01.cs:63-68 | Legacy/Aaru/ArcDL1.cs:63-68 — before extracting anything, compare `ArcFormats/FC01/ArcMRG0.cs` and `ArcFormats/Maika/ArcMIK01.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cherry/ArcMyk.cs:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 4) ArcFormats/Abel/ArcFPK.cs:64 — ArcFormats/Abel/ArcFPK.cs:64-69 | ArcFormats/Eternity/ArcGLNK.cs:65-70 | ArcFormats/Palette/ArcPAK2.cs:68-73 | Legacy/HyperWorks/ArcPAK.cs:60-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 4) ArcFormats/ArcARCX.cs:54 — ArcFormats/ArcARCX.cs:54-59 | ArcFormats/EntExec/ArcCAB.cs:49-54 | ArcFormats/Nejii/ArcCDT.cs:57-62 | ArcFormats/VnSystem/ArcVFS.cs:52-57 — before extracting anything, compare `ArcFormats/ArcARCX.cs` and `ArcFormats/EntExec/ArcCAB.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/ArcARCX.cs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Nejii/ArcCDT.cs:65` calls `ReadInt32` and `ArcFormats/EntExec/ArcCAB.cs:57` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 4) ArcFormats/Cherry/ArcMyk.cs:66 — ArcFormats/Cherry/ArcMyk.cs:66-71 | ArcFormats/FC01/ArcMRG0.cs:53-58 | ArcFormats/Maika/ArcMIK01.cs:60-65 | ArcFormats/SysD/ArcDPK.cs:56-61 — before extracting anything, compare `ArcFormats/FC01/ArcMRG0.cs` and `ArcFormats/Maika/ArcMIK01.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 × 4) ArcFormats/BlackRainbow/ArcPAK.cs:94 — ArcFormats/BlackRainbow/ArcPAK.cs:94-99 | ArcFormats/DenSDK/ArcDAF.cs:81-86 | ArcFormats/Patisserie/ArcBIN.cs:133-138 | ArcFormats/Scoop/ArcGX.cs:83-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 4) Legacy/PineSoft/ArcCMB.cs:80 — Legacy/PineSoft/ArcCMB.cs:80-85 | Legacy/Uma/ArcCDT.cs:77-82 | Legacy/Yaneurao/ArcDAT.cs:87-92 | Legacy/Yaneurao/ArcSDA.cs:80-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×6
  • Duplicated block (7 lines × 4) ArcFormats/Masys/ArcMGS.cs:88 — ArcFormats/Masys/ArcMGS.cs:88-94 | ArcFormats/Mixwill/ArcARC0.cs:73-79 | ArcFormats/Softpal/ArcPAC.cs:78-84 | ArcFormats/Youkai/ArcDAT.cs:197-203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Masys/ArcMGS.cs:88` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 4) ArcFormats/ArcIKS.cs:71 — ArcFormats/ArcIKS.cs:71-77 | ArcFormats/BlackRainbow/ArcGSP.cs:59-65 | Legacy/Artel/ArcPFD.cs:62-68 | Legacy/Rain/ArcBIN.cs:74-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/ArcIKS.cs:71` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 4) Legacy/Dice/ArcRLZ.cs:48 — Legacy/Dice/ArcRLZ.cs:48-54 | REDACTED:64-70 | Legacy/Tigerman/ArcPAC.cs:52-58 | Legacy/Uran/ArcPHS.cs:46-52 — before extracting anything, compare `Legacy/Tigerman/ArcPAC.cs` and `Legacy/Uran/ArcPHS.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Dice/ArcRLZ.cs:48` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:62` calls `ReadString`, `All` and `Legacy/Dice/ArcRLZ.cs:47` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 4) ArcFormats/Cri/ImageSPC.cs:58 — ArcFormats/Cri/ImageSPC.cs:58-64 | ArcFormats/DigitalWorks/ImageTM2arc.cs:41-47 | ArcFormats/Kid/ImageBIParc.cs:32-38 | ArcFormats/Kid/ImageSPC.cs:31-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 4) ArcFormats/Softpal/ImagePIC.cs:316 — ArcFormats/Softpal/ImagePIC.cs:316-322 | ArcFormats/Softpal/ImagePIC.cs:335-341 | ArcFormats/Softpal/ImagePIC.cs:354-360 | ArcFormats/Softpal/ImagePIC.cs:373-379 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (7 lines × 4) GameRes/Checksum.cs:168 — GameRes/Checksum.cs:168-174 | GameRes/Checksum.cs:175-181 | GameRes/Checksum.cs:194-200 | GameRes/Checksum.cs:201-207 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×6
  • NuGet dependencies are not locked REDACTED:3 — REDACTED declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked Experimental/packages.config:3 — Experimental/packages.config declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked GUI/packages.config:3 — GUI/packages.config declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked GameRes/packages.config:3 — GameRes/packages.config declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked Legacy/packages.config:3 — Legacy/packages.config declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked SchemeTool/packages.config:3 — SchemeTool/packages.config declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
D3 · God Classes · TooManyMethods · ×5
  • TooManyMethods: MainWindow GUI/MainWindow.xaml.cs — TooManyMethods — 1046 significant lines (blank, comment-only and punctuation-only lines excluded), 119 methods, declared across 6 files: GUI/MainWindow.xaml.cs (96), GUI/ImagePreview.cs (15), GUI/GarConvert.cs (3), REDACTED (3), +2 more file(s). The bar is 30 methods; this is 89 over it, 3.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: EriReader ArcFormats/Entis/EriReader.cs — TooManyMethods — 1130 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CRioArchive ArcFormats/rUGP/ArcRIO.cs — TooManyMethods — 454 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ArcViewStream GameRes/ArcStream.cs — TooManyMethods — 246 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: BinaryStream GameRes/BinaryStream.cs — TooManyMethods — 222 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×5
  • Edited copy of a member (29 corresponding lines) ArcFormats/CsWare/ImageGDT.cs:497 — ArcFormats/CsWare/ImageGDT.cs:497-525 | Legacy/Adv98/ImageGPC.cs:112-150 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) ArcFormats/Winters/ArcCFP.cs:45 — ArcFormats/Winters/ArcCFP.cs:45-73 | ArcFormats/Winters/ArcDAT.cs:45-75 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) ArcFormats/Majiro/ImageRCT.cs:154 — ArcFormats/Majiro/ImageRCT.cs:154-182 | ArcFormats/Will/ImageWIP.cs:133-162 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) ArcFormats/Dogenzaka/ArcBIN.cs:115 — ArcFormats/Dogenzaka/ArcBIN.cs:115-143 | Legacy/Weapon/ArcVoice.cs:43-74 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) ArcFormats/elf/ImageGPH.cs:318 — ArcFormats/elf/ImageGPH.cs:318-346 | ArcFormats/elf/ImageGPH.cs:349-377 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×5
  • Edited copy of a member (31 corresponding lines) ArcFormats/Primel/RC6.cs:82 — ArcFormats/Primel/RC6.cs:82-112 | ArcFormats/Primel/RC6.cs:115-146 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Legacy/Broccoli/ArcP00.cs:61 — Legacy/Broccoli/ArcP00.cs:61-91 | Legacy/Broccoli/ArcP00.cs:179-228 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) ArcFormats/StudioJikkenshitsu/ArcUMPK.cs:48 — ArcFormats/StudioJikkenshitsu/ArcUMPK.cs:48-79 | Legacy/Nyoken/ArcZLK.cs:43-73 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) ArcFormats/Leaf/ArcPX.cs:43 — ArcFormats/Leaf/ArcPX.cs:43-73 | ArcFormats/Xuse/ArcXuse.cs:136-171 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) ArcFormats/Maika/ArcBK.cs:101 — ArcFormats/Maika/ArcBK.cs:101-136 | Legacy/Melody/ImageMGO.cs:109-139 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×5
  • Edited copy of a member (25 corresponding lines) ArcFormats/elf/ArcAi5DAT.cs:65 — ArcFormats/elf/ArcAi5DAT.cs:65-93 | ArcFormats/elf/ArcAi5Win.cs:125-149 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Legacy/Pan/ArcPAN.cs:45 — Legacy/Pan/ArcPAN.cs:45-69 | Legacy/Kurumi/ArcMPK.cs:44-73 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) ArcFormats/AliceSoft/ArcAAR.cs:48 — ArcFormats/AliceSoft/ArcAAR.cs:48-73 | Legacy/Dall/ArcPEL.cs:43-67 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) ArcFormats/Ankh/ArcDAT.cs:46 — ArcFormats/Ankh/ArcDAT.cs:46-72 | Legacy/SystemAqua/ArcDAT.cs:48-72 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) ArcFormats/TopCat/ImageSPD.cs:231 — ArcFormats/TopCat/ImageSPD.cs:231-255 | ArcFormats/TopCat/ImageSPD.cs:258-287 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 9+ corresponding lines) Legacy/Aquarium/ArcAAP.cs:69 — Legacy/Aquarium/ArcAAP.cs:69-77 | Legacy/Giga/ArcALL.cs:59-67 | Legacy/Ponytail/ArcBND.cs:85-93 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) ArcFormats/Eushully/ImageGP.cs:209 — ArcFormats/Eushully/ImageGP.cs:209-217 | ArcFormats/Macromedia/ArcDXR.cs:376-384 | ArcFormats/WildBug/ImageWBM.cs:198-207 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) ArcFormats/ComicPlayer/ArcCP3.cs:94 — ArcFormats/ComicPlayer/ArcCP3.cs:94-105 | ArcFormats/FrontWing/ArcFLT.cs:103-111 | ArcFormats/Stack/ArcGPK.cs:105-113 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) ArcFormats/Leaf/ArcAM.cs:106 — ArcFormats/Leaf/ArcAM.cs:106-114 | ArcFormats/SimpleEncryption.cs:112-120 | ArcFormats/VnEngine/ArcAXR.cs:148-156 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) ArcFormats/Cyberworks/ImageTINK.cs:472 — ArcFormats/Cyberworks/ImageTINK.cs:472-480 | ArcFormats/Kaguya/ArcAN21.cs:237-245 | ArcFormats/Kaguya/ArcANM.cs:341-349 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 6+ corresponding lines) ArcFormats/Leaf/ArcLEAF.cs:162 — ArcFormats/Leaf/ArcLEAF.cs:162-167 | ArcFormats/Sviu/ArcPKZ.cs:99-106 | ArcFormats/Unity/PMaster/ArcDAT.cs:87-92 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) ArcFormats/BeF/ImageALO.cs:57 — ArcFormats/BeF/ImageALO.cs:57-62 | ArcFormats/Illusion/ImageEMA.cs:66-71 | ArcFormats/ImageMB.cs:77-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) ArcFormats/Unity/Asset.cs:292 — ArcFormats/Unity/Asset.cs:292-297 | ArcFormats/Unity/OggStream.cs:87-92 | Legacy/HyperWorks/ImageI24.cs:132-137 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) ArcFormats/Littlewitch/ArcDAT.cs:195 — ArcFormats/Littlewitch/ArcDAT.cs:195-200 | ArcFormats/Sviu/ArcPKZ.cs:171-177 | Legacy/Electriciteit/ArcPKK.cs:93-98 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) ArcFormats/Entis/ErisaMatrix.cs:365 — ArcFormats/Entis/ErisaMatrix.cs:365-370 | ArcFormats/Strikes/ImageLAG.cs:298-303 | Legacy/Eve/ArcGM.cs:110-115 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 5+ corresponding lines) ArcFormats/Kaas/ImageKAAS.cs:99 — ArcFormats/Kaas/ImageKAAS.cs:99-105 | ArcFormats/Marble/ImagePRS.cs:76-82 | ArcFormats/UMeSoft/ImageGRX.cs:67-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) ArcFormats/CsWare/ImageBPC.cs:53 — ArcFormats/CsWare/ImageBPC.cs:53-57 | ArcFormats/MAI/ImageMAI.cs:85-89 | Legacy/CrossNet/ImageGRB.cs:73-77 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Legacy/Ark/ImageCMP.cs:86 — Legacy/Ark/ImageCMP.cs:86-90 | Legacy/Unknown/ImageCTF.cs:71-75 | Legacy/Wing/ImageGEM.cs:74-78 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) ArcFormats/StudioJikkenshitsu/ImageDAT.cs:107 — ArcFormats/StudioJikkenshitsu/ImageDAT.cs:107-111 | Legacy/Akatombo/ImageFB.cs:54-58 | Legacy/Brownie/ImageNGC.cs:58-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) ArcFormats/ShiinaRio/ImageCHD.cs:71 — ArcFormats/ShiinaRio/ImageCHD.cs:71-75 | Legacy/Paprika/ImageNP.cs:69-73 | Legacy/RSystem/ImageRSG.cs:59-63 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×5
  • Duplicated block (18 lines × 2) ArcFormats/BellDa/ImageCP.cs:95 — ArcFormats/BellDa/ImageCP.cs:95-112 | ArcFormats/LzssStream.cs:79-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/BellDa/ImageCP.cs:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) ArcFormats/Leaf/ImageLFB.cs:116 — ArcFormats/Leaf/ImageLFB.cs:116-133 | ArcFormats/Leaf/ImageLFB.cs:158-175 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Leaf/ImageLFB.cs:136` calls `BlockCopy` and `ArcFormats/Leaf/ImageLFB.cs:177` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 2) ArcFormats/Lucifen/ImageELG.cs:350 — ArcFormats/Lucifen/ImageELG.cs:350-367 | ArcFormats/Lucifen/ImageELG.cs:559-576 — 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 `ArcFormats/Lucifen/ImageELG.cs:350` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (18 lines × 2) ArcFormats/Softpal/ImagePIC.cs:184 — ArcFormats/Softpal/ImagePIC.cs:184-201 | ArcFormats/Softpal/ImagePIC.cs:219-236 — 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 `ArcFormats/Softpal/ImagePIC.cs:184` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) ArcFormats/Kaguya/ArcLINK.cs:633 — ArcFormats/Kaguya/ArcLINK.cs:633-650 | ArcFormats/Kaguya/ArcLINK.cs:665-682 — 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 `ArcFormats/Kaguya/ArcLINK.cs:665` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×5
  • Duplicated block (10 lines × 3) ArcFormats/WildBug/ImageWBM.cs:434 — ArcFormats/WildBug/ImageWBM.cs:434-443 | ArcFormats/WildBug/ImageWBM.cs:752-761 | ArcFormats/WildBug/ImageWBM.cs:852-861 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/WildBug/ImageWBM.cs:434` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 3) ArcFormats/Tanaka/ArcARC0.cs:62 — ArcFormats/Tanaka/ArcARC0.cs:62-71 | Legacy/Jupiter/ArcLB5.cs:61-70 | Legacy/Muse/ArcDAT.cs:54-63 — 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 `ArcFormats/Tanaka/ArcARC0.cs:62` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 3) ArcFormats/Unity/Texture2D.cs:128 — ArcFormats/Unity/Texture2D.cs:128-137 | ArcFormats/Unity/Texture2D.cs:154-163 | ArcFormats/Unity/Texture2D.cs:182-191 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Unity/Texture2D.cs:127` calls `ReadInt32` and `ArcFormats/Unity/Texture2D.cs:153` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 3) ArcFormats/FC01/ArcMRG0.cs:49 — ArcFormats/FC01/ArcMRG0.cs:49-58 | ArcFormats/Maika/ArcMIK01.cs:56-65 | ArcFormats/SysD/ArcDPK.cs:52-61 — before extracting anything, compare `ArcFormats/FC01/ArcMRG0.cs` and `ArcFormats/Maika/ArcMIK01.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/FC01/ArcMRG0.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. 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 × 3) ArcFormats/CaramelBox/ArcARC4.cs:315 — ArcFormats/CaramelBox/ArcARC4.cs:315-324 | ArcFormats/NitroPlus/ArcNPK.cs:555-564 | Legacy/Pinky/ArcA5R.cs:238-247 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×5
  • Duplicated block (8–9 lines × 2) ArcFormats/Leaf/ImageLFB.cs:136 — ArcFormats/Leaf/ImageLFB.cs:136-143 | ArcFormats/Leaf/ImageLFB.cs:175-183 — 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 `ArcFormats/Leaf/ImageLFB.cs:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Leaf/ImageLFB.cs:136` calls `BlockCopy` and `ArcFormats/Leaf/ImageLFB.cs:175` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8–9 lines × 2) ArcFormats/AnimeGameSystem/ArcDAT.cs:55 — ArcFormats/AnimeGameSystem/ArcDAT.cs:55-63 | ArcFormats/BlueGale/ArcSNN.cs:56-63 — 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 `ArcFormats/AnimeGameSystem/ArcDAT.cs:55` 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–9 lines × 2) ArcFormats/Favorite/ArcFVP.cs:58 — ArcFormats/Favorite/ArcFVP.cs:58-65 | ArcFormats/Ffa/ArcBlackPackage.cs:123-131 — 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 `ArcFormats/Favorite/ArcFVP.cs:58` 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 (8–9 lines × 2) GameRes/Checksum.cs:178 — GameRes/Checksum.cs:178-185 | GameRes/Checksum.cs:204-212 — 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 `GameRes/Checksum.cs:178` 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 (8–9 lines × 2) Legacy/Brownie/ArcNAF.cs:47 — Legacy/Brownie/ArcNAF.cs:47-55 | Legacy/Gsx/ArcK5.cs:49-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Brownie/ArcNAF.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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Brownie/ArcNAF.cs:45` calls `AsciiEqual` and `Legacy/Gsx/ArcK5.cs:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×5
  • Duplicated block (5 lines × 5) ArcFormats/Cadath/ArcKAR.cs:61 — ArcFormats/Cadath/ArcKAR.cs:61-65 | ArcFormats/Palette/ArcPAK.cs:68-72 | Legacy/AlphaSystem/ArcPAK.cs:67-71 | Legacy/ApplePie/ArcARC.cs:61-65 | Legacy/Ponytail/ArcBND.cs:65-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cadath/ArcKAR.cs:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 5) ArcFormats/Aims/ArcPACK.cs:73 — ArcFormats/Aims/ArcPACK.cs:73-77 | ArcFormats/Aoi/ArcVFS.cs:66-70 | ArcFormats/Carriere/ArcARC.cs:51-55 | ArcFormats/RealLive/ArcSEEN.cs:55-59 | ArcFormats/Taskforce/ArcDAT.cs:51-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Aims/ArcPACK.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Carriere/ArcARC.cs:58` calls `ReadUInt32` and `ArcFormats/Aims/ArcPACK.cs:80` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 5) ArcFormats/DigitalWorks/ArcPAC.cs:82 — ArcFormats/DigitalWorks/ArcPAC.cs:82-86 | ArcFormats/DigitalWorks/ArcPACPS2.cs:81-85 | ArcFormats/DigitalWorks/ArcPACsingle.cs:71-75 | ArcFormats/Ipac/ArcIPAC.cs:70-74 | Legacy/Melonpan/ArcTTD.cs:79-83 — before extracting anything, compare `ArcFormats/DigitalWorks/ArcPACPS2.cs` and `ArcFormats/DigitalWorks/ArcPACsingle.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/DigitalWorks/ArcPAC.cs:82` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 5) ArcFormats/ArcIKS.cs:68 — ArcFormats/ArcIKS.cs:68-72 | ArcFormats/StudioEgo/ArcEGO.cs:58-62 | ArcFormats/StudioEgo/ArcEGO.cs:171-175 | Legacy/Electriciteit/ArcDAT.cs:60-64 | Legacy/Rain/ArcBIN.cs:71-75 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 5) ArcFormats/KiriKiri/ImageTLG.cs:694 — ArcFormats/KiriKiri/ImageTLG.cs:694-698 | ArcFormats/KiriKiri/ImageTLG.cs:710-714 | ArcFormats/KiriKiri/ImageTLG.cs:718-722 | ArcFormats/KiriKiri/ImageTLG.cs:726-730 | ArcFormats/KiriKiri/ImageTLG.cs:750-754 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/KiriKiri/ImageTLG.cs:694` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×5
  • Duplicated block (6 lines × 6) ArcFormats/SoftwareHouseParsley/ArcScn.cs:50 — ArcFormats/SoftwareHouseParsley/ArcScn.cs:50-55 | ArcFormats/Tail/ArcCAF.cs:75-80 | Legacy/Aquarium/ArcCPA.cs:59-64 | Legacy/Tigerman/ArcPAC.cs:60-65 | Legacy/Uran/ArcPHS.cs:54-59 | Legacy/Zone/ArcPKD.cs:59-64 — before extracting anything, compare `Legacy/Tigerman/ArcPAC.cs` and `Legacy/Uran/ArcPHS.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Zone/ArcPKD.cs:57` calls `IsNullOrWhiteSpace` and `ArcFormats/SoftwareHouseParsley/ArcScn.cs:49` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 6) ArcFormats/Bishop/ArcPK.cs:54 — ArcFormats/Bishop/ArcPK.cs:54-59 | ArcFormats/Gpk2/ArcGPK2.cs:62-67 | ArcFormats/Interheart/ArcFPK2.cs:59-64 | ArcFormats/WildBug/ArcWBP.cs:76-81 | ArcFormats/Winters/ArcCFP.cs:60-65 | ArcFormats/Winters/ArcDAT.cs:62-67 — before extracting anything, compare `ArcFormats/Winters/ArcCFP.cs` and `ArcFormats/Winters/ArcDAT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 × 6) Legacy/Pearl/ImagePL4.cs:176 — Legacy/Pearl/ImagePL4.cs:176-181 | Legacy/Pearl/ImagePL4.cs:182-187 | Legacy/Pearl/ImagePL4.cs:287-292 | Legacy/Pearl/ImagePL4.cs:293-298 | Legacy/Pearl/ImagePL4.cs:299-304 | Legacy/Pearl/ImagePL4.cs:305-310 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 6) ArcFormats/Carriere/ArcARC.cs:70 — ArcFormats/Carriere/ArcARC.cs:70-75 | ArcFormats/Dogenzaka/ArcBIN.cs:92-97 | ArcFormats/Misc/ArcBIN.cs:113-118 | ArcFormats/NekoSDK/ArcDAT.cs:90-95 | ArcFormats/Nekopunch/ArcPAK.cs:76-81 | ArcFormats/Otemoto/ArcTLZ.cs:79-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 6) ArcFormats/Cmvs/CmvsMD5.cs:73 — ArcFormats/Cmvs/CmvsMD5.cs:73-78 | ArcFormats/Cmvs/CmvsMD5.cs:103-108 | ArcFormats/Cmvs/CmvsMD5.cs:122-127 | ArcFormats/Cmvs/CmvsMD5.cs:141-146 | ArcFormats/Cmvs/CmvsMD5.cs:160-165 | ArcFormats/Cmvs/CmvsMD5.cs:179-184 — all 6 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.
D17 · Explicit Debt · BarePragmaDisable · ×4
  • BarePragmaDisable ArcFormats/Ffa/ArcFFA.cs:51 — #pragma warning disable 219 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable ArcFormats/Leaf/ArcPAK.cs:272 — #pragma warning disable 649,169 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable REDACTED:46 — #pragma warning disable 649 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable GameRes/ImageBMP.cs:63 — #pragma warning disable 649 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
D17 · Explicit Debt · TodoComment · ×4
  • TodoComment ArcFormats/Leaf/ArcSDAT.cs:43 — // TODO: it is said that only Steam ver has these spaces — 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 ArcFormats/Macintosh/ImagePICT.cs:209 — // TODO place bitmap into frame according to its RECT — 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 ArcFormats/Macromedia/ArcDXR.cs:421 — // TODO treat 'LPPA' archives the normal way, like archives that contain entries. — 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 ArcFormats/PkWare/ArcZIP.cs:209 — // TODO: GUI widget for options — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×4
  • Edited copy of a member (34 corresponding lines) ArcFormats/Littlewitch/ArcDAT.cs:82 — ArcFormats/Littlewitch/ArcDAT.cs:82-119 | ArcFormats/Littlewitch/ArcDAT.cs:122-155 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) ArcFormats/Bishop/ArcBSA.cs:83 — ArcFormats/Bishop/ArcBSA.cs:83-116 | ArcFormats/Bishop/ArcBSA.cs:119-159 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) ArcFormats/Kaguya/ArcAF.cs:45 — ArcFormats/Kaguya/ArcAF.cs:45-81 | ArcFormats/Kaguya/ArcUF.cs:45-78 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) ArcFormats/rUGP/ImageRIP.cs:388 — ArcFormats/rUGP/ImageRIP.cs:388-421 | ArcFormats/rUGP/ImageRIP.cs:424-457 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×4
  • Edited copy of a member (35 corresponding lines) ArcFormats/Tanaka/ArcWSM.cs:122 — ArcFormats/Tanaka/ArcWSM.cs:122-156 | ArcFormats/Tanaka/ArcWSM.cs:185-219 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) ArcFormats/Entis/EriReader.cs:2519 — ArcFormats/Entis/EriReader.cs:2519-2556 | ArcFormats/Entis/EriReader.cs:2559-2593 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) ArcFormats/Kaguya/ArcKaguya.cs:208 — ArcFormats/Kaguya/ArcKaguya.cs:208-242 | ArcFormats/RiddleSoft/ImageGCP.cs:124-164 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) ArcFormats/AZSys/ArcAZSys.cs:203 — ArcFormats/AZSys/ArcAZSys.cs:203-237 | ArcFormats/AZSys/ImageCPB.cs:202-239 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×4
  • Edited copy of a member (20 corresponding lines) ArcFormats/Blowfish.cs:323 — ArcFormats/Blowfish.cs:323-342 | ArcFormats/Blowfish.cs:386-406 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) ArcFormats/rUGP/ImageRIP.cs:219 — ArcFormats/rUGP/ImageRIP.cs:219-238 | ArcFormats/rUGP/ImageRIP.cs:246-265 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) ArcFormats/AliceSoft/ArcAFA.cs:195 — ArcFormats/AliceSoft/ArcAFA.cs:195-214 | ArcFormats/AliceSoft/ArcAFA.cs:217-237 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Legacy/AyPio/ImagePDT.cs:55 — Legacy/AyPio/ImagePDT.cs:55-78 | Legacy/AyPio/ImagePDT5.cs:50-69 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 24+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 24+ corresponding lines) Legacy/AlphaSystem/ArcPAK.cs:50 — Legacy/AlphaSystem/ArcPAK.cs:50-73 | Legacy/Mink/ArcMINK.cs:50-73 | Legacy/Zone/ArcPKD.cs:45-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) ArcFormats/Favorite/ArcFVP.cs:50 — ArcFormats/Favorite/ArcFVP.cs:50-73 | ArcFormats/Ffa/ArcBlackPackage.cs:115-139 | ArcFormats/Gpk2/ArcGPK2.cs:46-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) ArcFormats/Sas5/ArcWAR.cs:158 — ArcFormats/Sas5/ArcWAR.cs:158-185 | Legacy/KApp/ArcASD.cs:43-66 | Legacy/PineSoft/ArcVoice.cs:48-77 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) ArcFormats/Unity/Texture2D.cs:75 — ArcFormats/Unity/Texture2D.cs:75-98 | ArcFormats/Unity/Texture2D.cs:142-165 | ArcFormats/Unity/Texture2D.cs:168-194 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×4
  • Edited copies of one member (4 members, 7+ corresponding lines) ArcFormats/Banana/ArcPK.cs:89 — ArcFormats/Banana/ArcPK.cs:89-95 | ArcFormats/HCSystem/ArcPAK.cs:104-110 | ArcFormats/Silky/ArcAi6Win.cs:94-100 | Legacy/Asura/ArcPAK.cs:74-80 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) ArcFormats/Cyberworks/WidgetBELL.xaml.cs:14 — ArcFormats/Cyberworks/WidgetBELL.xaml.cs:14-20 | ArcFormats/Cyberworks/WidgetBELLDATA.xaml.cs:14-20 | ArcFormats/MangaGamer/WidgetMGPK.xaml.cs:14-20 | ArcFormats/RealLive/WidgetSCENE.xaml.cs:17-23 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) ArcFormats/AnimeGameSystem/WidgetAGS.xaml.cs:15 — ArcFormats/AnimeGameSystem/WidgetAGS.xaml.cs:15-21 | ArcFormats/Entis/WidgetNOA.xaml.cs:14-21 | ArcFormats/Ikura/WidgetISF.xaml.cs:14-20 | ArcFormats/Qlie/WidgetQLIE.xaml.cs:14-20 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) ArcFormats/Eushully/ImageAGF.cs:92 — ArcFormats/Eushully/ImageAGF.cs:92-98 | ArcFormats/Liar/ImageLIM.cs:62-68 | ArcFormats/ScrPlayer/ImageI.cs:58-64 | ArcFormats/TechnoBrain/ImageIPH.cs:75-83 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×4
  • Duplicated block (27 lines × 2) ArcFormats/Kaguya/ArcAF.cs:105 — ArcFormats/Kaguya/ArcAF.cs:105-131 | ArcFormats/Kaguya/ArcUF.cs:108-134 — before extracting anything, compare `ArcFormats/Kaguya/ArcAF.cs` and `ArcFormats/Kaguya/ArcUF.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (27 lines × 2) ArcFormats/Mnp/ArcMMA.cs:207 — ArcFormats/Mnp/ArcMMA.cs:207-233 | ArcFormats/Mnp/ArcMMA.cs:408-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Mnp/ArcMMA.cs:207` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (27 lines × 2) ArcFormats/Cmvs/ArcCPZ.cs:654 — ArcFormats/Cmvs/ArcCPZ.cs:654-680 | ArcFormats/Cmvs/ArcCPZ.cs:697-723 — 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 `ArcFormats/Cmvs/ArcCPZ.cs:654` 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 (27 lines × 2) ArcFormats/ScrPlayer/ImageI.cs:152 — ArcFormats/ScrPlayer/ImageI.cs:152-178 | ArcFormats/ScrPlayer/ImageI.cs:213-239 — 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 `ArcFormats/ScrPlayer/ImageI.cs:152` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×4
  • Duplicated block (17 lines × 2) ArcFormats/Kaguya/ArcAF.cs:48 — ArcFormats/Kaguya/ArcAF.cs:48-64 | ArcFormats/Kaguya/ArcUF.cs:48-64 — before extracting anything, compare `ArcFormats/Kaguya/ArcAF.cs` and `ArcFormats/Kaguya/ArcUF.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Kaguya/ArcAF.cs:48` 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) ArcFormats/WildBug/ImageWBM.cs:221 — ArcFormats/WildBug/ImageWBM.cs:221-237 | ArcFormats/WildBug/ImageWBM.cs:244-260 — 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 `ArcFormats/WildBug/ImageWBM.cs:221` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) ArcFormats/Sas5/ArcIAR.cs:335 — ArcFormats/Sas5/ArcIAR.cs:335-351 | ArcFormats/Sas5/ArcIAR.cs:387-403 — 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 (17 lines × 2) ArcFormats/elf/ArcHED.cs:80 — ArcFormats/elf/ArcHED.cs:80-96 | ArcFormats/elf/ArcHED.cs:100-116 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×4
  • Duplicated block (11 lines × 3) ArcFormats/CatSystem/ArcINT.cs:318 — ArcFormats/CatSystem/ArcINT.cs:318-328 | ArcFormats/FlyingShine/ArcPD.cs:145-155 | ArcFormats/Liar/ArcXFL.cs:129-139 — 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 `ArcFormats/CatSystem/ArcINT.cs:318` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) Legacy/AyPio/ImagePDT.cs:192 — Legacy/AyPio/ImagePDT.cs:192-202 | Legacy/AyPio/ImagePDT5.cs:240-250 | Legacy/Ucom/ImageUG.cs:222-232 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 3) ArcFormats/Interheart/ArcFPK2.cs:57 — ArcFormats/Interheart/ArcFPK2.cs:57-67 | ArcFormats/Winters/ArcCFP.cs:58-68 | ArcFormats/Winters/ArcDAT.cs:60-70 — before extracting anything, compare `ArcFormats/Winters/ArcCFP.cs` and `ArcFormats/Winters/ArcDAT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Interheart/ArcFPK2.cs:57` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) ArcFormats/Lucifen/ImageELG.cs:337 — ArcFormats/Lucifen/ImageELG.cs:337-347 | ArcFormats/Lucifen/ImageELG.cs:425-435 | ArcFormats/Lucifen/ImageELG.cs:545-555 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Lucifen/ImageELG.cs:337` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×4
  • Duplicated block (11–12 lines × 2) ArcFormats/Kid/ImageBIP.cs:190 — ArcFormats/Kid/ImageBIP.cs:190-201 | ArcFormats/Kid/ImageBIP.cs:229-239 — 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 `ArcFormats/Kid/ImageBIP.cs:190` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–12 lines × 2) ArcFormats/AnimeGameSystem/ArcDAT.cs:50 — ArcFormats/AnimeGameSystem/ArcDAT.cs:50-61 | ArcFormats/Interheart/ArcFPK2.cs:46-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/AnimeGameSystem/ArcDAT.cs:50` 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 (11–12 lines × 2) ArcFormats/Circus/AudioPCM.cs:326 — ArcFormats/Circus/AudioPCM.cs:326-337 | ArcFormats/Circus/AudioPCM.cs:381-391 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11–12 lines × 2) ArcFormats/KiriKiri/ImageTLG.cs:482 — ArcFormats/KiriKiri/ImageTLG.cs:482-492 | ArcFormats/KiriKiri/ImageTLG.cs:496-507 — 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 `ArcFormats/KiriKiri/ImageTLG.cs:482` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×4
  • Duplicated block (5 lines × 4) ArcFormats/Aims/ArcPACK.cs:73 — ArcFormats/Aims/ArcPACK.cs:73-77 | ArcFormats/Aoi/ArcVFS.cs:66-70 | ArcFormats/Carriere/ArcARC.cs:51-55 | ArcFormats/RealLive/ArcSEEN.cs:55-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Aims/ArcPACK.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Carriere/ArcARC.cs:58` calls `ReadUInt32` and `ArcFormats/Aims/ArcPACK.cs:80` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 4) ArcFormats/AdvSys/ArcAdvSysT.cs:63 — ArcFormats/AdvSys/ArcAdvSysT.cs:63-67 | ArcFormats/AdvSys/ArcGR2.cs:61-65 | ArcFormats/CDPA/ArcPACK.cs:58-62 | Legacy/Clio/ArcPAC.cs:56-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/CDPA/ArcPACK.cs:56` calls `IsNullOrWhiteSpace` and `ArcFormats/AdvSys/ArcAdvSysT.cs:62` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 4) ArcFormats/AdvSys/ArcAdvSysT.cs:62 — ArcFormats/AdvSys/ArcAdvSysT.cs:62-66 | ArcFormats/AdvSys/ArcGR2.cs:60-64 | ArcFormats/Cadath/ArcKAR.cs:57-61 | ArcFormats/Succubus/ArcARC.cs:57-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 4) ArcFormats/Hexenhaus/ArcARCC.cs:109 — ArcFormats/Hexenhaus/ArcARCC.cs:109-113 | ArcFormats/Kaguya/ArcAF.cs:97-101 | ArcFormats/Kaguya/ArcKaguya.cs:187-191 | ArcFormats/Kaguya/ArcUF.cs:100-104 — before extracting anything, compare `ArcFormats/Kaguya/ArcAF.cs` and `ArcFormats/Kaguya/ArcUF.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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.
IC1 · Incompleteness & stubs · Condition was already decided · ×4
  • Condition was already decided — an earlier guard makes this test constant ArcFormats/Adobe/ArcAIR.cs:79 — Control only reaches here when `0x04 != index.ReadUInt8()` is false, because the guard on line 76 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
  • Condition was already decided — an earlier guard makes this test constant ArcFormats/Entis/MioDecoder.cs:358 — Control only reaches here when `context.GetABit() != 0` is false, because the guard on line 311 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
  • Condition was already decided — an earlier guard makes this test constant ArcFormats/Entis/MioDecoder.cs:655 — Control only reaches here when `context.GetABit() != 0` is false, because the guard on line 604 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
  • Condition was already decided — an earlier guard makes this test constant ArcFormats/RenPy/ArcRPA.cs:338 — Control only reaches here when `iterator.MoveNext()` is true, because the guard on line 335 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×4
  • Sync-over-async blocking — 3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking ArcFormats/Ethornell/ImageCBG.cs:309 — `complete.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking ArcFormats/Cri/AudioHCA.cs:164 — `m_conversion_task.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking ArcFormats/KiriKiri/ImageTLG.cs:1374 — `.Wait ()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
X15 · Unvalidated length from an untrusted reader · Length read from the parsed input is spent without ever being bounded · ×4
  • Length read from the parsed input is spent without ever being bounded ArcFormats/CaramelBox/ArcARC4.cs:155 — `unpacked_size` is read from the stream being parsed at line 154 (`ReadUInt32`), then used to size an array at line 155 — and nowhere in this method is `unpacked_size` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `unpacked_size` against the bytes actually remaining in the stream before spending it.
  • Length read from the parsed input is spent without ever being bounded REDACTED:234 — `length` is read from the stream being parsed at line 232 (`ReadInt32`), then read in bulk from that same stream at line 234 — and nowhere in this method is `length` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `length` against the bytes actually remaining in the stream before spending it.
  • Length read from the parsed input is spent without ever being bounded ArcFormats/Liar/ArcXFL.cs:204 — `code_size` is read from the stream being parsed at line 200 (`ReadUInt32`), then read in bulk from that same stream at line 204 — and nowhere in this method is `code_size` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `code_size` against the bytes actually remaining in the stream before spending it.
  • Length read from the parsed input is spent without ever being bounded Legacy/WestGate/ArcUSF.cs:135 — `count` is read from the stream being parsed at line 134 (`ReadInt32`), then used to size an array at line 135 — and nowhere in this method is `count` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `count` against the bytes actually remaining in the stream before spending it.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×4
  • Disposable created and abandoned in the method that made it REDACTED:462 — `sw` is a `StreamWriter`, which implements `IDisposable`, and it is created here (line 462). Every use of it in `SerializeSchemeJson` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var sw = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Legacy/Broccoli/BroccoliGrp.cs:42 — `reader` is a `BinaryReader`, which implements `IDisposable`, and it is created here (line 42). Every use of it in `ReadMetaData` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var reader = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Legacy/KApp/ImageCGD.cs:56 — `reader` is a `CgdDecoder`, which implements `IDisposable`, and it is created here (line 56). Every use of it in `Read` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var reader = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Legacy/KApp/ImageCGD.cs:94 — `reader` is a `CgdDecoder`, which implements `IDisposable`, and it is created here (line 94). Every use of it in `Read` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var reader = …;`), which releases it at the end of the scope on every path including a throw.
AX2 · Stateful singletons · Stateful shared instance · ×3
  • Stateful shared instance: InfoReader ArcFormats/Glib2/ImagePGX.cs:132 — `InfoReader` is not registered, but `PgxFormat` creates it and keeps it in the static `InfoCache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_layer_map, m_last_info_dir; e.g. `m_layer_map` at line 179).
  • Stateful shared instance: FileSystemStack GameRes/FileSystem.cs:553 — `FileSystemStack` is not registered, but `VFS` creates it and keeps it in the static `m_vfs`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (CurrentArchive, m_fs_stack, m_arc_name_stack, LastVisitedArc, LastVisitedPath; e.g. `CurrentArchive` at line 596).
  • Stateful shared instance: FormatCatalog REDACTED:42 — `FormatCatalog` keeps one instance of itself in the static `m_instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (CurrentSchemeVersion, m_game_map; e.g. `CurrentSchemeVersion` at line 350).
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×3
  • Edited copy of a member (36 corresponding lines) ArcFormats/Leaf/ImageLFB.cs:114 — ArcFormats/Leaf/ImageLFB.cs:114-152 | ArcFormats/Leaf/ImageLFB.cs:156-191 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) ArcFormats/Triangle/ArcBMX.cs:48 — ArcFormats/Triangle/ArcBMX.cs:48-92 | Legacy/Pearl/ArcARY.cs:46-81 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Legacy/Artifact/ArcMOO.cs:49 — Legacy/Artifact/ArcMOO.cs:49-89 | Legacy/Peach/ArcPAK.cs:43-78 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×3
  • Edited copy of a member (41 corresponding lines) ArcFormats/Cmvs/ArcCPZ.cs:653 — ArcFormats/Cmvs/ArcCPZ.cs:653-693 | ArcFormats/Cmvs/ArcCPZ.cs:696-745 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (41 corresponding lines) ArcFormats/FC01/ArcMRG.cs:55 — ArcFormats/FC01/ArcMRG.cs:55-102 | ArcFormats/FC01/ArcMRG.cs:191-231 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (41 corresponding lines) ArcFormats/KiriKiri/HxCrypt.cs:637 — ArcFormats/KiriKiri/HxCrypt.cs:637-678 | ArcFormats/KiriKiri/HxCrypt.cs:681-721 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×3
  • Edited copy of a member (27 corresponding lines) ArcFormats/FC01/ArcMRG.cs:105 — ArcFormats/FC01/ArcMRG.cs:105-131 | ArcFormats/FC01/ArcMRG.cs:234-264 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) ArcFormats/SoftwareHouseParsley/ArcCG2.cs:58 — ArcFormats/SoftwareHouseParsley/ArcCG2.cs:58-86 | Legacy/Peach/ArcNIJI.cs:43-69 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) ArcFormats/Ikura/ArcGAN.cs:53 — ArcFormats/Ikura/ArcGAN.cs:53-79 | ArcFormats/Musica/ArcSQZ.cs:57-86 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 25+ corresponding lines) Legacy/ApplePie/ArcARC.cs:43 — Legacy/ApplePie/ArcARC.cs:43-67 | Legacy/Mina/ArcML2.cs:45-73 | Legacy/Nug/ArcDAT.cs:44-69 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) ArcFormats/Kid/ArcDAT.cs:50 — ArcFormats/Kid/ArcDAT.cs:50-74 | Legacy/AdvS/ArcDAT.cs:43-68 | Legacy/BRoom/ArcPK.cs:49-76 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) ArcFormats/BellDa/ArcDAT.cs:52 — ArcFormats/BellDa/ArcDAT.cs:52-77 | Legacy/Aaru/ArcDL1.cs:46-70 | Legacy/Aquarium/ArcCPA.cs:45-69 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 23+ corresponding lines) ArcFormats/AdvSys/ArcGR2.cs:47 — ArcFormats/AdvSys/ArcGR2.cs:47-72 | ArcFormats/Youkai/ArcDAT.cs:44-71 | Legacy/Clio/ArcPAC.cs:43-65 | Legacy/Electriciteit/ArcDAT.cs:45-71 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 23+ corresponding lines) ArcFormats/Leaf/ArcLAC.cs:46 — ArcFormats/Leaf/ArcLAC.cs:46-71 | ArcFormats/Sviu/ArcKLZ.cs:42-64 | Legacy/Dice/ArcRLZ.cs:45-67 | Legacy/Sogna/ArcSGS.cs:45-68 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 23+ corresponding lines) ArcFormats/Cmvs/ArcCPZ.cs:336 — ArcFormats/Cmvs/ArcCPZ.cs:336-358 | ArcFormats/Cmvs/ArcCPZ.cs:361-383 | ArcFormats/Cmvs/ArcCPZ.cs:386-411 | ArcFormats/Cmvs/ArcCPZ.cs:414-439 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 13+ corresponding lines) ArcFormats/Artdink/Ps2ImageUtil.cs:122 — ArcFormats/Artdink/Ps2ImageUtil.cs:122-137 | Legacy/Broccoli/ImageT32.cs:214-226 | Legacy/Broccoli/ImageT32.cs:229-242 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) ArcFormats/NekoNyan/ArcDAT.cs:266 — ArcFormats/NekoNyan/ArcDAT.cs:266-278 | ArcFormats/NekoNyan/ArcDAT.cs:340-352 | ArcFormats/NekoNyan/ArcDAT.cs:390-402 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) ArcFormats/NonColor/ArcACV.cs:45 — ArcFormats/NonColor/ArcACV.cs:45-57 | REDACTED:121-134 | ArcFormats/NonColor/ArcMinato.cs:61-74 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 19+ corresponding lines) ArcFormats/Cmvs/ImagePB2.cs:48 — ArcFormats/Cmvs/ImagePB2.cs:48-70 | ArcFormats/Cmvs/ImagePSB.cs:49-67 | ArcFormats/Sviu/ImageGBP.cs:49-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) ArcFormats/Lambda/ArcLAX.cs:101 — ArcFormats/Lambda/ArcLAX.cs:101-119 | ArcFormats/Leaf/AudioG.cs:89-107 | Legacy/KeroQ/ImageKGD.cs:126-146 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) ArcFormats/ActiveSoft/ImageEDT.cs:111 — ArcFormats/ActiveSoft/ImageEDT.cs:111-130 | ArcFormats/ActiveSoft/ImageEDT.cs:274-293 | ArcFormats/NSystem/ImageMGD.cs:48-66 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 10+ corresponding lines) ArcFormats/Cmvs/AudioMV.cs:41 — ArcFormats/Cmvs/AudioMV.cs:41-50 | ArcFormats/Cmvs/AudioMV2.cs:42-51 | ArcFormats/Sviu/AudioKPV.cs:42-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) ArcFormats/CommonStreams.cs:142 — ArcFormats/CommonStreams.cs:142-151 | ArcFormats/FamilyAdvSystem/ArcCSAF.cs:335-344 | GameRes/BinaryStream.cs:708-717 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Legacy/AyPio/ImagePDT5.cs:227 — Legacy/AyPio/ImagePDT5.cs:227-236 | Legacy/Miami/ImageMIA.cs:293-302 | Legacy/System98/ImageG.cs:326-335 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 7+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 7+ corresponding lines) ArcFormats/ArcARCX.cs:73 — ArcFormats/ArcARCX.cs:73-79 | ArcFormats/DeepBlue/ArcAC.cs:84-90 | ArcFormats/MyAdv/ArcPAC.cs:95-101 | Legacy/Libido/ArcARC.cs:89-95 | Legacy/Pan/ArcPAN.cs:72-78 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 7+ corresponding lines) ArcFormats/Circus/ImageCRX.cs:76 — ArcFormats/Circus/ImageCRX.cs:76-82 | ArcFormats/Eushully/ImageGP.cs:89-96 | REDACTED:97-106 | ArcFormats/Vitamin/ImageSBI.cs:74-80 | ArcFormats/elf/ImageGPH.cs:81-87 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 7+ corresponding lines) ArcFormats/BlackRainbow/ArcPAK.cs:93 — ArcFormats/BlackRainbow/ArcPAK.cs:93-99 | ArcFormats/DenSDK/ArcDAF.cs:80-86 | ArcFormats/Patisserie/ArcBIN.cs:132-138 | ArcFormats/Scoop/ArcGX.cs:82-88 | ArcFormats/Yox/ArcYOX.cs:83-89 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×3
  • Duplicated block (25 lines × 2) ArcFormats/rUGP/ImageRIP.cs:390 — ArcFormats/rUGP/ImageRIP.cs:390-414 | ArcFormats/rUGP/ImageRIP.cs:426-450 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/rUGP/ImageRIP.cs:390` 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 (25 lines × 2) ArcFormats/Tanaka/ArcWSM.cs:123 — ArcFormats/Tanaka/ArcWSM.cs:123-147 | ArcFormats/Tanaka/ArcWSM.cs:186-210 — 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 `ArcFormats/Tanaka/ArcWSM.cs:123` 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 (25 lines × 2) ArcFormats/DxLib/ArcDX.cs:503 — ArcFormats/DxLib/ArcDX.cs:503-527 | ArcFormats/DxLib/ArcDX8.cs:291-315 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/DxLib/ArcDX.cs:503` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/DxLib/ArcDX8.cs:316` calls `ReadInt64` and `ArcFormats/DxLib/ArcDX.cs:528` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×3
  • Duplicated block (24 lines × 2) ArcFormats/CatSystem/ArcINT.cs:307 — ArcFormats/CatSystem/ArcINT.cs:307-330 | ArcFormats/FlyingShine/ArcPD.cs:134-157 — 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 (24 lines × 2) Legacy/Broccoli/ArcP00.cs:115 — Legacy/Broccoli/ArcP00.cs:115-138 | Legacy/Broccoli/ArcP00.cs:252-275 — 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 `Legacy/Broccoli/ArcP00.cs:115` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `entry` to `P00Entry` in one and `IpfbEntry` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (24 lines × 2) ArcFormats/Kid/ArcDAT.cs:170 — ArcFormats/Kid/ArcDAT.cs:170-193 | ArcFormats/Kid/ArcDATRAW.cs:67-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Kid/ArcDAT.cs:170` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×3
  • Duplicated block (16–17 lines × 2) ArcFormats/elf/ImageG24.cs:47 — ArcFormats/elf/ImageG24.cs:47-63 | ArcFormats/elf/ImageGP8.cs:93-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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–17 lines × 2) ArcFormats/CatSystem/ArcINT.cs:298 — ArcFormats/CatSystem/ArcINT.cs:298-313 | ArcFormats/Liar/ArcXFL.cs:109-125 — 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 `ArcFormats/CatSystem/ArcINT.cs:298` 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–17 lines × 2) ArcFormats/Ffa/ImagePT1.cs:214 — ArcFormats/Ffa/ImagePT1.cs:214-229 | ArcFormats/Ffa/ImagePT1.cs:347-363 — 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 `ArcFormats/Ffa/ImagePT1.cs:214` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×3
  • Duplicated block (14–15 lines × 2) ArcFormats/Cyberworks/ImageDATA.cs:197 — ArcFormats/Cyberworks/ImageDATA.cs:197-211 | ArcFormats/Cyberworks/ImageDATA.cs:278-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cyberworks/ImageDATA.cs:197` 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 (14–15 lines × 2) Legacy/Artifact/ArcMOO.cs:60 — Legacy/Artifact/ArcMOO.cs:60-73 | Legacy/Peach/ArcPAK.cs:53-67 — 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 `Legacy/Artifact/ArcMOO.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 (14–15 lines × 2) Legacy/Izumi/ImageMAI2.cs:402 — Legacy/Izumi/ImageMAI2.cs:402-415 | Legacy/Ponytail/ImageTSZ.cs:147-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×3
  • Duplicated block (7 lines × 5) ArcFormats/AdvSys/ArcAdvSysT.cs:66 — ArcFormats/AdvSys/ArcAdvSysT.cs:66-72 | ArcFormats/CDPA/ArcPACK.cs:61-67 | ArcFormats/Youkai/ArcDAT.cs:65-71 | Legacy/Clio/ArcPAC.cs:59-65 | Legacy/Duke/ArcDAT.cs:68-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/AdvSys/ArcAdvSysT.cs:66` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 5) ArcFormats/DigitalWorks/ArcPAC.cs:65 — ArcFormats/DigitalWorks/ArcPAC.cs:65-71 | ArcFormats/Tail/ArcCAF.cs:78-84 | Legacy/Tigerman/ArcPAC.cs:63-69 | Legacy/Uran/ArcPHS.cs:57-63 | Legacy/Zone/ArcPKD.cs:62-68 — before extracting anything, compare `Legacy/Tigerman/ArcPAC.cs` and `Legacy/Uran/ArcPHS.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/DigitalWorks/ArcPAC.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 5) ArcFormats/Cadath/ArcKAR.cs:61 — ArcFormats/Cadath/ArcKAR.cs:61-67 | ArcFormats/Palette/ArcPAK.cs:68-74 | Legacy/AlphaSystem/ArcPAK.cs:67-73 | Legacy/ApplePie/ArcARC.cs:61-67 | Legacy/Sogna/ArcSGS.cs:62-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cadath/ArcKAR.cs:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D6 · Cohesion (LCOM4) · Low cohesion · ×3
  • Low cohesion: CpzOpener (LCOM4 4) ArcFormats/Cmvs/ArcCPZ.cs:82 — CpzOpener's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: NekoXCode (LCOM4 4) ArcFormats/Nekopack/ArcNEKO2.cs:106 — NekoXCode's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: FormatCatalog (LCOM4 4) REDACTED:42 — FormatCatalog's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
S1 · Cryptographic Hygiene · Weak cipher · ×3
  • Weak cipher ArcFormats/Unity/ScriptDSM.cs:75 — DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes.
  • Weak cipher REDACTED:144 — DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes.
  • Weak cipher ArcFormats/Unity/ArcDSM.cs:76 — DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×3
  • Sync-over-async (deadlock risk) ArcFormats/Ethornell/ImageCBG.cs:309 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) ArcFormats/Cri/AudioHCA.cs:164 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
  • Sync-over-async (deadlock risk) ArcFormats/KiriKiri/ImageTLG.cs:1374 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×3
  • Swallowed exception (caught, then discarded) ArcFormats/Abogado/ImageKG.cs:138 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) ArcFormats/Dvn/ArcDVN.cs:77 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) ArcFormats/FC01/ImageMCG.cs:297 — `catch (InvalidFormatException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
D1 · Cyclomatic Complexity · ArcOpener.TryOpen (cyclomatic 19) · ×2
  • ArcOpener.TryOpen (cyclomatic 19) ArcFormats/MAI/ArcMAI.cs:55 — ArcOpener.TryOpen has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, 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.
  • ArcOpener.TryOpen (cyclomatic 19) ArcFormats/Majiro/ArcMajiro.cs:57 — ArcOpener.TryOpen has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DatOpener.TryOpen (cyclomatic 17) · ×2
  • DatOpener.TryOpen (cyclomatic 17) ArcFormats/Adobe/ArcAIR.cs:44 — DatOpener.TryOpen has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • DatOpener.TryOpen (cyclomatic 17) ArcFormats/Seraphim/ArcArchAngel.cs:52 — DatOpener.TryOpen has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ArcOpener.TryOpen (cyclomatic 17) · ×2
  • ArcOpener.TryOpen (cyclomatic 17) ArcFormats/AZSys/ArcAZSys.cs:82 — ArcOpener.TryOpen has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. Note what this body is, though: it works in explicit hardware vector and instruction-set types. A kernel divided across a call boundary passes its vectors between the parts and depends on the runtime putting them back together, so the division can cost more than the complexity it removes. The measurement stands — a hot path is not a licence to be unreadable — but the move that pays here is to lift the COLD parts out first (argument validation, fallback and error paths, one-off setup) and leave the kernel whole. Where the kernel itself has to be divided, ask for the extracted parts to be inlined as well, and measure the result rather than assuming the division is free.
  • ArcOpener.TryOpen (cyclomatic 17) ArcFormats/Xuse/ArcXuse.cs:49 — ArcOpener.TryOpen has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D15 · Churn × Complexity Hotspots · Hotspot · ×2
  • Hotspot: ArcFormats/Succubus/ImageGH.cs ArcFormats/Succubus/ImageGH.cs:199 — ArcFormats/Succubus/ImageGH.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in GhpReader.Unpack3 at line 199. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 16:47:18 +08:00' --until='2026-11-11 16:47:18 +08:00' --full-history --no-merges -- ArcFormats/Succubus/ImageGH.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: ArcFormats/GsPack/ImageGS.cs ArcFormats/GsPack/ImageGS.cs:173 — ArcFormats/GsPack/ImageGS.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in GswinGrpFormat.Decode at line 173. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 16:47:18 +08:00' --until='2026-11-11 16:47:18 +08:00' --full-history --no-merges -- ArcFormats/GsPack/ImageGS.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D2 · Cognitive Complexity · RleDecompressor.Unpack (cognitive 29) · ×2
  • RleDecompressor.Unpack (cognitive 29) ArcFormats/uGOS/ArcDET.cs:141 — RleDecompressor.Unpack has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • RleDecompressor.Unpack (cognitive 29) Legacy/Inspire/ArcIDA.cs:183 — RleDecompressor.Unpack has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.Unpack (cognitive 24) · ×2
  • Reader.Unpack (cognitive 24) ArcFormats/Majiro/ImageRC8.cs:108 — Reader.Unpack has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Reader.Unpack (cognitive 24) ArcFormats/Majiro/ImageRCT.cs:631 — Reader.Unpack has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CbgReader.ReverseAverageSampling (cognitive 23) · ×2
  • CbgReader.ReverseAverageSampling (cognitive 23) ArcFormats/HuneX/ImageCBG.cs:216 — CbgReader.ReverseAverageSampling has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • CbgReader.ReverseAverageSampling (cognitive 23) ArcFormats/Ethornell/ImageCBG.cs:251 — CbgReader.ReverseAverageSampling has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.Unpack (cognitive 23) · ×2
  • Reader.Unpack (cognitive 23) ArcFormats/ActiveSoft/ImageEDT.cs:329 — Reader.Unpack has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Reader.Unpack (cognitive 23) ArcFormats/AliceSoft/ImageQNT.cs:138 — Reader.Unpack has cognitive complexity 23 (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.
D2 · Cognitive Complexity · PakOpener.TryOpen (cognitive 19) · ×2
  • PakOpener.TryOpen (cognitive 19) ArcFormats/HCSystem/ArcPAK.cs:45 — PakOpener.TryOpen has cognitive complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • PakOpener.TryOpen (cognitive 19) ArcFormats/Hypatia/ArcKogado.cs:70 — PakOpener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcOpener.TryOpen (cognitive 18) · ×2
  • ArcOpener.TryOpen (cognitive 18) ArcFormats/Succubus/ArcARC.cs:42 — ArcOpener.TryOpen has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ArcOpener.TryOpen (cognitive 18) Legacy/Libido/ArcARC.cs:46 — ArcOpener.TryOpen has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CbgReader.UnpackZeros (cognitive 17) · ×2
  • CbgReader.UnpackZeros (cognitive 17) ArcFormats/HuneX/ImageCBG.cs:175 — CbgReader.UnpackZeros has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • CbgReader.UnpackZeros (cognitive 17) ArcFormats/Ethornell/ImageCBG.cs:210 — CbgReader.UnpackZeros has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcOpener.TryOpen (cognitive 16) · ×2
  • ArcOpener.TryOpen (cognitive 16) ArcFormats/AdvSys/ArcAdvSys3.cs:48 — ArcOpener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ArcOpener.TryOpen (cognitive 16) Legacy/Types/ArcARC.cs:41 — ArcOpener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PakOpener.TryOpen (cognitive 16) · ×2
  • PakOpener.TryOpen (cognitive 16) ArcFormats/NekoSDK/ArcPAK.cs:49 — PakOpener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • PakOpener.TryOpen (cognitive 16) ArcFormats/G2/ArcGCEX.cs:49 — PakOpener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) ArcFormats/AdvDx/ArcPKD.cs:54 — ArcFormats/AdvDx/ArcPKD.cs:54-78 | ArcFormats/Emic/ArcPACK.cs:59-107 | ArcFormats/Yatagarasu/ArcPKG.cs:43-72 | Legacy/KeroQ/ArcDAT.cs:43-75 | Legacy/Tetratech/ArcBND.cs:50-74 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) ArcFormats/DigitalWorks/ArcPAC.cs:75 — ArcFormats/DigitalWorks/ArcPAC.cs:75-97 | ArcFormats/DigitalWorks/ArcPACPS2.cs:74-98 | ArcFormats/DigitalWorks/ArcPACsingle.cs:64-86 | ArcFormats/Ipac/ArcIPAC.cs:65-76 | Legacy/Melonpan/ArcTTD.cs:74-87 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (48 corresponding lines) · ×2
  • Edited copy of a member (48 corresponding lines) ArcFormats/Unity/Bc7Decoder.cs:139 — ArcFormats/Unity/Bc7Decoder.cs:139-186 | ArcFormats/Unity/Bc7Decoder.cs:189-237 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) ArcFormats/Kaas/ImageKAAS.cs:226 — ArcFormats/Kaas/ImageKAAS.cs:226-273 | ArcFormats/Kaas/ImageKAAS.cs:276-325 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (57 corresponding lines) · ×2
  • Edited copy of a member (57 corresponding lines) ArcFormats/Succubus/ImageGH.cs:139 — ArcFormats/Succubus/ImageGH.cs:139-195 | ArcFormats/Succubus/ImageGH.cs:200-265 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (57 corresponding lines) ArcFormats/Liar/ImageLIM.cs:155 — ArcFormats/Liar/ImageLIM.cs:155-223 | ArcFormats/Liar/ImageLIM.cs:243-299 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×2
  • Edited copy of a member (33 corresponding lines) ArcFormats/Qlie/Encryption.cs:380 — ArcFormats/Qlie/Encryption.cs:380-412 | ArcFormats/Qlie/Encryption.cs:415-451 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) ArcFormats/Kid/ArcDATRAW.cs:57 — ArcFormats/Kid/ArcDATRAW.cs:57-90 | ArcFormats/Kid/ArcDAT.cs:161-193 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (49 corresponding lines) · ×2
  • Edited copy of a member (49 corresponding lines) ArcFormats/Entis/EriReader.cs:1732 — ArcFormats/Entis/EriReader.cs:1732-1780 | ArcFormats/Entis/EriReader.cs:1783-1832 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (49 corresponding lines) ArcFormats/Kaguya/ArcPL00.cs:56 — ArcFormats/Kaguya/ArcPL00.cs:56-104 | ArcFormats/Kaguya/ArcPL10.cs:56-109 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (42 corresponding lines) · ×2
  • Edited copy of a member (42 corresponding lines) ArcFormats/CatSystem/ArcBinV1.cs:145 — ArcFormats/CatSystem/ArcBinV1.cs:145-186 | ArcFormats/CatSystem/ArcPidaV1.cs:33-84 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) ArcFormats/ScenePlayer/ArcPMA.cs:43 — ArcFormats/ScenePlayer/ArcPMA.cs:43-84 | ArcFormats/ScenePlayer/ArcPMX.cs:43-84 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (43 corresponding lines) · ×2
  • Edited copy of a member (43 corresponding lines) ArcFormats/FC01/ArcMRG.cs:315 — ArcFormats/FC01/ArcMRG.cs:315-357 | ArcFormats/LzssStream.cs:148-194 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) ArcFormats/Ikura/ImageGGS.cs:79 — ArcFormats/Ikura/ImageGGS.cs:79-138 | ArcFormats/Ikura/ImageTAN.cs:121-163 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 30+ corresponding lines) ArcFormats/FC01/ArcSCXA.cs:16 — ArcFormats/FC01/ArcSCXA.cs:16-48 | ArcFormats/MAGES/ArcARC20.cs:18-48 | ArcFormats/MAGES/ArcFARC.cs:17-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 30+ corresponding lines) ArcFormats/Irrlicht/ArcARK.cs:43 — ArcFormats/Irrlicht/ArcARK.cs:43-72 | ArcFormats/Leaf/ArcLAC.cs:100-130 | ArcFormats/Mixwill/ArcARC0.cs:48-79 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 28+ corresponding lines) ArcFormats/MangaGamer/ArcMGPK.cs:73 — ArcFormats/MangaGamer/ArcMGPK.cs:73-101 | ArcFormats/MangaGamer/ArcMGPK.cs:223-250 | ArcFormats/NSystem/ArcFJSYS.cs:63-96 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 28+ corresponding lines) ArcFormats/C4/ImageGD.cs:159 — ArcFormats/C4/ImageGD.cs:159-189 | Legacy/Rare/ArcX.cs:102-130 | Legacy/SystemAqua/ArcDAT.cs:133-160 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 22+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 22+ corresponding lines) ArcFormats/ArcARCX.cs:48 — ArcFormats/ArcARCX.cs:48-70 | ArcFormats/Nejii/ArcCDT.cs:48-73 | ArcFormats/NitroPlus/ArcNPP.cs:43-64 | ArcFormats/RealLive/ArcSEEN.cs:49-73 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 22+ corresponding lines) ArcFormats/ActiveSoft/ArcADPACK.cs:139 — ArcFormats/ActiveSoft/ArcADPACK.cs:139-164 | ArcFormats/ArcPACKDAT.cs:53-78 | ArcFormats/BlackRainbow/ArcGSP.cs:41-65 | ArcFormats/Silky/ArcIFL.cs:45-66 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 21+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 21+ corresponding lines) ArcFormats/Cadath/ArcDAF.cs:44 — ArcFormats/Cadath/ArcDAF.cs:44-67 | Legacy/Gsx/ArcK3.cs:43-67 | Legacy/Jupiter/ArcLB5.cs:43-71 | Legacy/Muse/ArcDAT.cs:43-63 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 21+ corresponding lines) ArcFormats/MAGES/ArcGPDA.cs:17 — ArcFormats/MAGES/ArcGPDA.cs:17-47 | Legacy/Artel/ArcPFD.cs:44-68 | Legacy/Gsx/ArcK5.cs:48-68 | Legacy/HyperWorks/ArcPAK.cs:43-69 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×2
  • Edited copy of a member (19 corresponding lines) ArcFormats/Emote/ArcPSB.cs:784 — ArcFormats/Emote/ArcPSB.cs:784-802 | ArcFormats/Emote/ArcPSB.cs:805-824 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) GameRes/BinaryStream.cs:174 — GameRes/BinaryStream.cs:174-192 | GameRes/BinaryStream.cs:656-674 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 12+ corresponding lines) ArcFormats/Ice/ImageIBM.cs:70 — ArcFormats/Ice/ImageIBM.cs:70-81 | ArcFormats/Ivory/ImageSG.cs:111-124 | ArcFormats/Triangle/ImageTRI.cs:67-79 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) ArcFormats/NitroPlus/ArcNPA.cs:400 — ArcFormats/NitroPlus/ArcNPA.cs:400-411 | ArcFormats/NitroPlus/ArcNPK.cs:229-240 | ArcFormats/ShiinaRio/ArcWARC.cs:297-308 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 11+ corresponding lines) ArcFormats/GameSystem/ImageBGD.cs:40 — ArcFormats/GameSystem/ImageBGD.cs:40-54 | ArcFormats/GameSystem/ImageCGD.cs:45-59 | ArcFormats/Hypatia/ImageLPG.cs:40-51 | Legacy/Force/ImageDZP.cs:49-59 | Legacy/Nabe/ImageYPF.cs:48-63 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) ArcFormats/GameSystem/ImageALP.cs:41 — ArcFormats/GameSystem/ImageALP.cs:41-52 | ArcFormats/GameSystem/ImageTEXB.cs:41-52 | Legacy/Adviz/ImageBIZ.cs:47-60 | Legacy/HillField/ImageIMG.cs:42-52 | Legacy/hmp/ImageMBP.cs:43-56 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 5+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 5+ corresponding lines) ArcFormats/Interheart/ImageCandy.cs:91 — ArcFormats/Interheart/ImageCandy.cs:91-95 | ArcFormats/Leaf/ImageLFG.cs:68-72 | ArcFormats/Otemoto/ImageMAG.cs:87-91 | GameRes/ImageTGA.cs:56-60 | Legacy/Aaru/ImageBM2.cs:57-61 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 5+ corresponding lines) ArcFormats/AZSys/ImageCPB.cs:97 — ArcFormats/AZSys/ImageCPB.cs:97-101 | ArcFormats/AZSys/ImageTYP1.cs:77-82 | ArcFormats/Ikura/ImageVRS.cs:52-56 | ArcFormats/MAI/ImageMAI.cs:198-202 | ArcFormats/Pajamas/ImageEPA.cs:86-90 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×2
  • Edited copy of a member (3 corresponding lines) GameRes/ByteArray.cs:167 — GameRes/ByteArray.cs:167-169 | GameRes/Utility.cs:289-291 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) GameRes/ByteArray.cs:252 — GameRes/ByteArray.cs:252-254 | GameRes/Utility.cs:325-327 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 4+ corresponding lines) ArcFormats/HCSystem/ArcPAK.cs:122 — ArcFormats/HCSystem/ArcPAK.cs:122-125 | ArcFormats/TopCat/ArcTCD3.cs:222-225 | Legacy/Unknown/ArcDAT.cs:97-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) ArcFormats/Qlie/ImageABMP.cs:86 — ArcFormats/Qlie/ImageABMP.cs:86-89 | ArcFormats/Qlie/ImageARGB.cs:72-75 | Legacy/Tigerman/ImageCHR.cs:90-93 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×2
  • Edited copy of a member (4 corresponding lines) Legacy/Ruri/ImageKBM.cs:49 — Legacy/Ruri/ImageKBM.cs:49-52 | Legacy/NxLib/ImageDCG.cs:49-52 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) ArcFormats/Cromwell/ArcPAK.cs:86 — ArcFormats/Cromwell/ArcPAK.cs:86-89 | Legacy/Airyu/ArcCHR.cs:77-80 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (38 lines × 2) · ×2
  • Duplicated block (38 lines × 2) ArcFormats/NekoNyan/ArcDAT.cs:200 — ArcFormats/NekoNyan/ArcDAT.cs:200-237 | ArcFormats/NekoNyan/ArcDAT.cs:300-337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (38 lines × 2) ArcFormats/Favorite/ImageHZC.cs:138 — ArcFormats/Favorite/ImageHZC.cs:138-175 | Experimental/Artemis/ImageIPT.cs:158-195 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×2
  • Duplicated block (26 lines × 2) ArcFormats/Cmvs/ArcCPZ2.cs:50 — ArcFormats/Cmvs/ArcCPZ2.cs:50-75 | ArcFormats/Cmvs/ArcCPZ3.cs:50-75 — before extracting anything, compare `ArcFormats/Cmvs/ArcCPZ2.cs` and `ArcFormats/Cmvs/ArcCPZ3.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cmvs/ArcCPZ2.cs:50` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (26 lines × 2) ArcFormats/Bishop/ArcBSA.cs:91 — ArcFormats/Bishop/ArcBSA.cs:91-116 | ArcFormats/Bishop/ArcBSA.cs:134-159 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Bishop/ArcBSA.cs:91` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×2
  • Duplicated block (23–24 lines × 2) ArcFormats/Foster/ArcC24.cs:44 — ArcFormats/Foster/ArcC24.cs:44-67 | ArcFormats/ShiinaRio/ArcS25.cs:49-71 — 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 `ArcFormats/Foster/ArcC24.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23–24 lines × 2) ArcFormats/Majiro/ImageRC8.cs:115 — ArcFormats/Majiro/ImageRC8.cs:115-138 | ArcFormats/Majiro/ImageRCT.cs:638-660 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Majiro/ImageRC8.cs:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2
  • Duplicated block (22 lines × 2) ArcFormats/rUGP/ImageRIP.cs:553 — ArcFormats/rUGP/ImageRIP.cs:553-574 | ArcFormats/rUGP/ImageRIP.cs:687-708 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (22 lines × 2) ArcFormats/AnimeGameSystem/ImageAinos.cs:212 — ArcFormats/AnimeGameSystem/ImageAinos.cs:212-233 | ArcFormats/AnimeGameSystem/ImageAinos.cs:260-281 — 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 `ArcFormats/AnimeGameSystem/ImageAinos.cs:212` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×2
  • Duplicated block (20 lines × 2) ArcFormats/elf/ImageGPH.cs:322 — ArcFormats/elf/ImageGPH.cs:322-341 | ArcFormats/elf/ImageGPH.cs:353-372 — 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 `ArcFormats/elf/ImageGPH.cs:322` 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 (20 lines × 2) ArcFormats/Artemis/ArcPFS.cs:77 — ArcFormats/Artemis/ArcPFS.cs:77-96 | ArcFormats/Artemis/ArcPFS.cs:110-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×2
  • Duplicated block (21 lines × 2) ArcFormats/Kid/ImageBIP.cs:206 — ArcFormats/Kid/ImageBIP.cs:206-226 | ArcFormats/Kid/ImageBIP.cs:243-263 — 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 `ArcFormats/Kid/ImageBIP.cs:206` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) ArcFormats/Kaguya/ArcAN21.cs:199 — ArcFormats/Kaguya/ArcAN21.cs:199-219 | ArcFormats/Kaguya/ArcPL10.cs:184-204 — before extracting anything, compare `ArcFormats/Kaguya/ArcAN21.cs` and `ArcFormats/Kaguya/ArcPL10.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2
  • Duplicated block (19 lines × 2) ArcFormats/Softpal/ArcVAFS.cs:117 — ArcFormats/Softpal/ArcVAFS.cs:117-135 | ArcFormats/Softpal/ArcVAFS.cs:154-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 `ArcFormats/Softpal/ArcVAFS.cs:117` 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 (19 lines × 2) ArcFormats/Entis/EriReader.cs:369 — ArcFormats/Entis/EriReader.cs:369-387 | ArcFormats/Entis/EriReader.cs:388-406 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×2
  • Duplicated block (17–18 lines × 2) ArcFormats/WildBug/AudioWWA.cs:130 — ArcFormats/WildBug/AudioWWA.cs:130-147 | ArcFormats/WildBug/AudioWWA.cs:193-209 — 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 `ArcFormats/WildBug/AudioWWA.cs:130` 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–18 lines × 2) Legacy/AyPio/ImagePDT5.cs:53 — Legacy/AyPio/ImagePDT5.cs:53-69 | Legacy/Ucom/ImageUG.cs:46-63 — 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 `Legacy/AyPio/ImagePDT5.cs:53` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×2
  • Duplicated block (11 lines × 4) ArcFormats/WildBug/ImageWBM.cs:348 — ArcFormats/WildBug/ImageWBM.cs:348-358 | ArcFormats/WildBug/ImageWBM.cs:428-438 | ArcFormats/WildBug/ImageWBM.cs:559-569 | ArcFormats/WildBug/ImageWBM.cs:672-682 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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 × 4) Legacy/Adviz/ImageGIZ.cs:282 — Legacy/Adviz/ImageGIZ.cs:282-292 | Legacy/Discovery/ImagePR1.cs:331-341 | Legacy/Grocer/ImagePIC.cs:181-191 | Legacy/Ponytail/ImageTSZ.cs:287-297 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×2
  • Duplicated block (12 lines × 3) ArcFormats/NekoNyan/ArcDAT.cs:282 — ArcFormats/NekoNyan/ArcDAT.cs:282-293 | ArcFormats/NekoNyan/ArcDAT.cs:356-367 | ArcFormats/NekoNyan/ArcDAT.cs:406-417 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 3) Legacy/Akatombo/ArcX.cs:51 — Legacy/Akatombo/ArcX.cs:51-62 | Legacy/Pearl/ArcARY.cs:58-69 | Legacy/Weapon/ArcVoice.cs:55-67 — 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 `Legacy/Akatombo/ArcX.cs:51` 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×2
  • Duplicated block (12–13 lines × 2) ArcFormats/rUGP/ArcRIO.cs:202 — ArcFormats/rUGP/ArcRIO.cs:202-214 | ArcFormats/rUGP/ArcRIO.cs:226-237 — 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 (12–13 lines × 2) ArcFormats/Entis/MioDecoder.cs:855 — ArcFormats/Entis/MioDecoder.cs:855-866 | ArcFormats/Entis/MioDecoder.cs:909-921 — 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 `ArcFormats/Entis/MioDecoder.cs:855` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Entis/MioDecoder.cs:855` calls `Copy` and `ArcFormats/Entis/MioDecoder.cs:909` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×2
  • Duplicated block (10–11 lines × 2) ArcFormats/Foster/ArcC24.cs:42 — ArcFormats/Foster/ArcC24.cs:42-52 | ArcFormats/Seraphim/ArcCP3.cs:43-52 — 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 `ArcFormats/Foster/ArcC24.cs:42` 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 (10–11 lines × 2) Experimental/CatSystem/ArcIRIS.cs:51 — Experimental/CatSystem/ArcIRIS.cs:51-61 | Experimental/CatSystem/ArcIRIS.cs:74-83 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Experimental/CatSystem/ArcIRIS.cs:73` calls `ReadUInt32` and `Experimental/CatSystem/ArcIRIS.cs:51` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 6) · ×2
  • Duplicated block (7 lines × 6) ArcFormats/Abel/ArcFPK.cs:67 — ArcFormats/Abel/ArcFPK.cs:67-73 | ArcFormats/Bishop/ArcPK.cs:57-63 | ArcFormats/Gpk2/ArcGPK2.cs:65-71 | ArcFormats/Palette/ArcPAK2.cs:71-77 | Legacy/HyperWorks/ArcPAK.cs:63-69 | Legacy/Rhss/ArcCRG.cs:55-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Abel/ArcFPK.cs:67` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 6) ArcFormats/ArcIKS.cs:68 — ArcFormats/ArcIKS.cs:68-74 | ArcFormats/StudioEgo/ArcEGO.cs:58-64 | ArcFormats/StudioEgo/ArcEGO.cs:171-177 | Legacy/Artel/ArcPFD.cs:59-65 | Legacy/Rain/ArcBIN.cs:71-77 | Legacy/RedZone/ArcPAK.cs:57-63 — there are 6 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 15) · ×2
  • Duplicated block (8–9 lines × 15) ArcFormats/Aims/ArcPACK.cs:68 — ArcFormats/Aims/ArcPACK.cs:68-76 | ArcFormats/ArcARCX.cs:49-57 | ArcFormats/Basil/ArcMIF.cs:44-52 | ArcFormats/Bishop/ArcPK.cs:44-52 | ArcFormats/Cadath/ArcKAR.cs:49-57 | ArcFormats/Carriere/ArcARC.cs:47-54 | ArcFormats/Cyberworks/ArcP8.cs:44-52 | ArcFormats/EntExec/ArcCAB.cs:44-52 | ArcFormats/Ipac/ArcIPAC.cs:44-52 | ArcFormats/Leaf/ArcLAC.cs:47-55 | ArcFormats/Nexas/ArcTPF.cs:53-61 | ArcFormats/RealLive/ArcSEEN.cs:50-58 | ArcFormats/Slg/ArcSZS.cs:47-55 | ArcFormats/SoftwareHouseParsley/ArcPAC.cs:44-52 | ArcFormats/Taskforce/ArcDAT.cs:46-54 — before extracting anything, compare `ArcFormats/Aims/ArcPACK.cs` and `ArcFormats/Basil/ArcMIF.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Aims/ArcPACK.cs:68` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Carriere/ArcARC.cs:45` calls `ReadUInt32` and `ArcFormats/Aims/ArcPACK.cs:67` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8–9 lines × 15) ArcFormats/Aims/ArcPACK.cs:68 — ArcFormats/Aims/ArcPACK.cs:68-76 | ArcFormats/ArcARCX.cs:49-57 | ArcFormats/Basil/ArcMIF.cs:44-52 | ArcFormats/Bishop/ArcPK.cs:44-52 | ArcFormats/Cadath/ArcKAR.cs:49-57 | ArcFormats/Carriere/ArcARC.cs:47-54 | ArcFormats/Cyberworks/ArcP8.cs:44-52 | ArcFormats/EntExec/ArcCAB.cs:44-52 | ArcFormats/Leaf/ArcLAC.cs:47-55 | ArcFormats/Nexas/ArcTPF.cs:53-61 | ArcFormats/NitroPlus/ArcNPP.cs:44-51 | ArcFormats/RealLive/ArcSEEN.cs:50-58 | ArcFormats/Slg/ArcSZS.cs:47-55 | ArcFormats/SoftwareHouseParsley/ArcPAC.cs:44-52 | ArcFormats/Taskforce/ArcDAT.cs:46-54 — before extracting anything, compare `ArcFormats/Aims/ArcPACK.cs` and `ArcFormats/Basil/ArcMIF.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Aims/ArcPACK.cs:68` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Carriere/ArcARC.cs:45` calls `ReadUInt32` and `ArcFormats/Aims/ArcPACK.cs:67` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×2
  • Duplicated block (8 lines × 4) ArcFormats/Cri/ImageSPC.cs:48 — ArcFormats/Cri/ImageSPC.cs:48-55 | ArcFormats/DigitalWorks/ImageTM2arc.cs:32-39 | ArcFormats/Kid/ImageBIParc.cs:23-30 | ArcFormats/Kid/ImageSPC.cs:21-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cri/ImageSPC.cs:48` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 4) ArcFormats/Kaguya/ArcLIN2.cs:45 — ArcFormats/Kaguya/ArcLIN2.cs:45-52 | ArcFormats/Palette/ArcPAK.cs:51-58 | ArcFormats/Palette/ArcPAK2.cs:52-59 | ArcFormats/Sohfu/ArcSKA.cs:45-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Kaguya/ArcLIN2.cs:45` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Palette/ArcPAK.cs:48` calls `AsciiEqual` and `ArcFormats/Kaguya/ArcLIN2.cs:43` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–9 lines × 3) · ×2
  • Duplicated block (8–9 lines × 3) ArcFormats/BellDa/ArcDAT.cs:61 — ArcFormats/BellDa/ArcDAT.cs:61-68 | ArcFormats/Ipac/ArcIPAC.cs:46-54 | ArcFormats/Mugi/ArcBIN.cs:67-74 — 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 `ArcFormats/BellDa/ArcDAT.cs:61` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/BellDa/ArcDAT.cs:59` calls `ReadUInt32` and `ArcFormats/Ipac/ArcIPAC.cs:45` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8–9 lines × 3) ArcFormats/BlueGale/VideoAMV.cs:55 — ArcFormats/BlueGale/VideoAMV.cs:55-62 | ArcFormats/DDSystem/ArcDDP.cs:52-60 | ArcFormats/Ikura/ArcGAN.cs:56-63 — 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 `ArcFormats/BlueGale/VideoAMV.cs:55` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Ikura/ArcGAN.cs:54` calls `AsciiEqual` and `ArcFormats/DDSystem/ArcDDP.cs:51` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (4–5 lines × 8) · ×2
  • Duplicated block (4–5 lines × 8) ArcFormats/StudioJikkenshitsu/SjTransform.cs:192 — ArcFormats/StudioJikkenshitsu/SjTransform.cs:192-196 | ArcFormats/StudioJikkenshitsu/SjTransform.cs:200-204 | ArcFormats/StudioJikkenshitsu/SjTransform.cs:208-212 | ArcFormats/StudioJikkenshitsu/SjTransform.cs:216-220 | ArcFormats/StudioJikkenshitsu/SjTransform.cs:224-228 | ArcFormats/StudioJikkenshitsu/SjTransform.cs:232-236 | ArcFormats/StudioJikkenshitsu/SjTransform.cs:240-244 | ArcFormats/StudioJikkenshitsu/SjTransform.cs:245-248 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (4–5 lines × 8) ArcFormats/KiriKiri/ImageTLG.cs:686 — ArcFormats/KiriKiri/ImageTLG.cs:686-690 | ArcFormats/KiriKiri/ImageTLG.cs:702-706 | ArcFormats/KiriKiri/ImageTLG.cs:742-746 | ArcFormats/KiriKiri/ImageTLG.cs:758-762 | ArcFormats/KiriKiri/ImageTLG.cs:766-770 | ArcFormats/KiriKiri/ImageTLG.cs:774-778 | ArcFormats/KiriKiri/ImageTLG.cs:782-786 | ArcFormats/KiriKiri/ImageTLG.cs:790-793 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/KiriKiri/ImageTLG.cs:686` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×2
  • Duplicated block (5 lines × 6) ArcFormats/KiriKiri/ImageTLG.cs:682 — ArcFormats/KiriKiri/ImageTLG.cs:682-686 | ArcFormats/KiriKiri/ImageTLG.cs:706-710 | ArcFormats/KiriKiri/ImageTLG.cs:714-718 | ArcFormats/KiriKiri/ImageTLG.cs:722-726 | ArcFormats/KiriKiri/ImageTLG.cs:754-758 | ArcFormats/KiriKiri/ImageTLG.cs:778-782 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/KiriKiri/ImageTLG.cs:682` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 6) ArcFormats/KiriKiri/ImageTLG.cs:690 — ArcFormats/KiriKiri/ImageTLG.cs:690-694 | ArcFormats/KiriKiri/ImageTLG.cs:730-734 | ArcFormats/KiriKiri/ImageTLG.cs:738-742 | ArcFormats/KiriKiri/ImageTLG.cs:762-766 | ArcFormats/KiriKiri/ImageTLG.cs:770-774 | ArcFormats/KiriKiri/ImageTLG.cs:794-798 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/KiriKiri/ImageTLG.cs:690` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
IC1 · Incompleteness & stubs · Both branches open with the same statements · ×2
  • Both branches open with the same statements — the condition does not decide them ArcFormats/CaramelBox/ImageFCB.cs:118 — The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them ArcFormats/Seraphim/ImageSeraph.cs:347 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
S1 · Cryptographic Hygiene · Password key derivation is priced too cheaply · ×2
  • Password key derivation is priced too cheaply ArcFormats/Unity/ArcDSM.cs:92 — This code fixes PBKDF2-SHA-1 at 1,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price.
  • Password key derivation is priced too cheaply ArcFormats/Unity/ScriptDSM.cs:67 — This code fixes PBKDF2-SHA-1 at 1,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price.
X28 · Index access outside its own emptiness guard · Index access outside its own emptiness guard · ×2
  • Index access outside its own emptiness guard ArcFormats/ArcCommon.cs:107 — This access `ext[0]` has no test of the length of `ext` on its own path, while this method tests it for that position at line 106 (`string.IsNullOrEmpty (ext)`): where that test fails, this read throws. Either the test is load-bearing and this read needs it too, or the length of `ext` is fixed here and the test is dead.
  • Index access outside its own emptiness guard ArcFormats/Crowd/ArcPCK.cs:146 — This guard bounds `fmt_index` with `fmt_index > formats.Count`, which admits `fmt_index` equal to the length of `formats`; `formats[fmt_index]` then reads one past the last element and throws. The bound is off by one: test `fmt_index < formats.Length` (or `.Count`).
D1 · Cyclomatic Complexity · Xp3Opener.TryOpen (cyclomatic 66) · ×1
  • Xp3Opener.TryOpen (cyclomatic 66) ArcFormats/KiriKiri/ArcXP3.cs:105 — Xp3Opener.TryOpen has cyclomatic complexity 66 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GdtReader.UnpackDouble (cyclomatic 57) · ×1
  • GdtReader.UnpackDouble (cyclomatic 57) ArcFormats/CsWare/ImageGDT.cs:141 — GdtReader.UnpackDouble 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.
D1 · Cyclomatic Complexity · Mai2Reader.UnpackPlane (cyclomatic 56) · ×1
  • Mai2Reader.UnpackPlane (cyclomatic 56) Legacy/Izumi/ImageMAI2.cs:139 — Mai2Reader.UnpackPlane has cyclomatic complexity 56 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Pl4Reader.UnpackV1 (cyclomatic 48) · ×1
  • Pl4Reader.UnpackV1 (cyclomatic 48) Legacy/Pearl/ImagePL4.cs:207 — Pl4Reader.UnpackV1 has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Pickle.Load (cyclomatic 45) · ×1
  • Pickle.Load (cyclomatic 45) ArcFormats/RenPy/ArcRPA.cs:457 — Pickle.Load has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TlgFormat.TVPTLG6DecodeLineGeneric (cyclomatic 42) · ×1
  • TlgFormat.TVPTLG6DecodeLineGeneric (cyclomatic 42) ArcFormats/KiriKiri/ImageTLG.cs:634 — TlgFormat.TVPTLG6DecodeLineGeneric has cyclomatic complexity 42 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · PictReader.Unpack (cyclomatic 39) · ×1
  • PictReader.Unpack (cyclomatic 39) ArcFormats/Macintosh/ImagePICT.cs:166 — PictReader.Unpack has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CxProgram.Execute (cyclomatic 38) · ×1
  • CxProgram.Execute (cyclomatic 38) ArcFormats/KiriKiri/KiriKiriCx.cs:477 — CxProgram.Execute has cyclomatic complexity 38 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · EriReader.DecodeLosslessImage (cyclomatic 37) · ×1
  • EriReader.DecodeLosslessImage (cyclomatic 37) ArcFormats/Entis/EriReader.cs:435 — EriReader.DecodeLosslessImage has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LeafLzss.Compress (cyclomatic 35) · ×1
  • LeafLzss.Compress (cyclomatic 35) ArcFormats/Leaf/LeafCompression.cs:38 — LeafLzss.Compress has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NcgReader.Unpack (cyclomatic 35) · ×1
  • NcgReader.Unpack (cyclomatic 35) Legacy/Nekotaro/ImageNCG.cs:92 — NcgReader.Unpack has cyclomatic complexity 35 (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.
D1 · Cyclomatic Complexity · NemesisDecodeContext.DecodeNemesisCodeBytes (cyclomatic 34) · ×1
  • NemesisDecodeContext.DecodeNemesisCodeBytes (cyclomatic 34) ArcFormats/Entis/ErisaNemesis.cs:71 — NemesisDecodeContext.DecodeNemesisCodeBytes 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.
D1 · Cyclomatic Complexity · MioDecoder.DecodeSoundDCT (cyclomatic 34) · ×1
  • MioDecoder.DecodeSoundDCT (cyclomatic 34) ArcFormats/Entis/MioDecoder.cs:292 — MioDecoder.DecodeSoundDCT 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.
D1 · Cyclomatic Complexity · BipFormat.Read (cyclomatic 32) · ×1
  • BipFormat.Read (cyclomatic 32) ArcFormats/Kid/ImageBIP.cs:139 — BipFormat.Read has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LpkOpener.ParseGameInit (cyclomatic 32) · ×1
  • LpkOpener.ParseGameInit (cyclomatic 32) ArcFormats/Lucifen/ArcLPK.cs:294 — LpkOpener.ParseGameInit has cyclomatic complexity 32 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · VorbisInfo.UnpackBooks (cyclomatic 30) · ×1
  • VorbisInfo.UnpackBooks (cyclomatic 30) ArcFormats/Unity/Vorbis.cs:215 — VorbisInfo.UnpackBooks has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · VorbisInfo.StaticBookUnpack (cyclomatic 30) · ×1
  • VorbisInfo.StaticBookUnpack (cyclomatic 30) ArcFormats/Unity/Vorbis.cs:310 — VorbisInfo.StaticBookUnpack has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GdtReader.Unpack8Line (cyclomatic 29) · ×1
  • GdtReader.Unpack8Line (cyclomatic 29) ArcFormats/CsWare/ImageGDT.cs:347 — GdtReader.Unpack8Line has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PazOpener.TryOpen (cyclomatic 29) · ×1
  • PazOpener.TryOpen (cyclomatic 29) ArcFormats/Musica/ArcPAZ.cs:179 — PazOpener.TryOpen has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EriReader.DecodeLossyImage (cyclomatic 29) · ×1
  • EriReader.DecodeLossyImage (cyclomatic 29) ArcFormats/Entis/EriReader.cs:631 — EriReader.DecodeLossyImage has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PolaReader.Unpack (cyclomatic 29) · ×1
  • PolaReader.Unpack (cyclomatic 29) ArcFormats/AdvSys/ImageGR2.cs:157 — PolaReader.Unpack has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · IkeReader.Unpack (cyclomatic 28) · ×1
  • IkeReader.Unpack (cyclomatic 28) Legacy/UMeSoft/ArcBIN.cs:126 — IkeReader.Unpack has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Pl4Reader.UnpackV0 (cyclomatic 27) · ×1
  • Pl4Reader.UnpackV0 (cyclomatic 27) Legacy/Pearl/ImagePL4.cs:119 — Pl4Reader.UnpackV0 has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AgiFormat.ReadMetaData (cyclomatic 26) · ×1
  • AgiFormat.ReadMetaData (cyclomatic 26) ArcFormats/Artdink/ImageAGI.cs:55 — AgiFormat.ReadMetaData has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Arc3Opener.TryOpen (cyclomatic 26) · ×1
  • Arc3Opener.TryOpen (cyclomatic 26) ArcFormats/CaramelBox/ArcARC3.cs:57 — Arc3Opener.TryOpen has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PsbReader.ReadHeader (cyclomatic 26) · ×1
  • PsbReader.ReadHeader (cyclomatic 26) ArcFormats/Emote/ArcPSB.cs:352 — PsbReader.ReadHeader has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: PsbReader.GetObject (cyclomatic 30) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · Parser.ScanDir (cyclomatic 26) · ×1
  • Parser.ScanDir (cyclomatic 26) ArcFormats/YuRis/ArcYPF.cs:487 — Parser.ScanDir has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Wa1Reader.UnpackV12 (cyclomatic 26) · ×1
  • Wa1Reader.UnpackV12 (cyclomatic 26) ArcFormats/Ffa/AudioWA1.cs:403 — Wa1Reader.UnpackV12 has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Reader.sub_4225EA (cyclomatic 26) · ×1
  • Reader.sub_4225EA (cyclomatic 26) ArcFormats/Ffa/ImagePT1.cs:399 — Reader.sub_4225EA has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · WebPFormat.ReadMetaData (cyclomatic 26) · ×1
  • WebPFormat.ReadMetaData (cyclomatic 26) Experimental/WebP/ImageWEBP.cs:68 — WebPFormat.ReadMetaData has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TbmFormat.Read (cyclomatic 26) · ×1
  • TbmFormat.Read (cyclomatic 26) Legacy/Broccoli/ImageTbm.cs:93 — TbmFormat.Read has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LsdOpener.UnpackH (cyclomatic 25) · ×1
  • LsdOpener.UnpackH (cyclomatic 25) ArcFormats/Gss/ArcARC.cs:275 — LsdOpener.UnpackH has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · HxCrypt.ReadIndex (cyclomatic 25) · ×1
  • HxCrypt.ReadIndex (cyclomatic 25) ArcFormats/KiriKiri/HxCrypt.cs:91 — HxCrypt.ReadIndex has cyclomatic complexity 25 (threshold 15). Of this number, 22 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LagReader.RleUnpack (cyclomatic 25) · ×1
  • LagReader.RleUnpack (cyclomatic 25) ArcFormats/Strikes/ImageLAG.cs:205 — LagReader.RleUnpack has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Bc7Decoder.UnpackBc7Mode4_5 (cyclomatic 25) · ×1
  • Bc7Decoder.UnpackBc7Mode4_5 (cyclomatic 25) ArcFormats/Unity/Bc7Decoder.cs:239 — Bc7Decoder.UnpackBc7Mode4_5 has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MioDecoder.DecodeSoundDCT_MSS (cyclomatic 25) · ×1
  • MioDecoder.DecodeSoundDCT_MSS (cyclomatic 25) ArcFormats/Entis/MioDecoder.cs:585 — MioDecoder.DecodeSoundDCT_MSS has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Wa1Reader.UnpackV4 (cyclomatic 25) · ×1
  • Wa1Reader.UnpackV4 (cyclomatic 25) ArcFormats/Ffa/AudioWA1.cs:123 — Wa1Reader.UnpackV4 has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Parser.ReadMetaData (cyclomatic 25) · ×1
  • Parser.ReadMetaData (cyclomatic 25) GameRes/ImageTIFF.cs:165 — Parser.ReadMetaData has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TagFormat.ParseImages (cyclomatic 24) · ×1
  • TagFormat.ParseImages (cyclomatic 24) ArcFormats/Artdink/ImageTAG.cs:145 — TagFormat.ParseImages has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · KlzFormat.LzhStreamDecode (cyclomatic 24) · ×1
  • KlzFormat.LzhStreamDecode (cyclomatic 24) ArcFormats/Kid/ImageKLZ.cs:54 — KlzFormat.LzhStreamDecode has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CRip.ReadLong (cyclomatic 24) · ×1
  • CRip.ReadLong (cyclomatic 24) ArcFormats/rUGP/ImageRIP.cs:315 — CRip.ReadLong has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · VafsOpener.TryOpen (cyclomatic 24) · ×1
  • VafsOpener.TryOpen (cyclomatic 24) ArcFormats/Softpal/ArcVAFS.cs:51 — VafsOpener.TryOpen has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AbmpReader.ReadIndex (cyclomatic 24) · ×1
  • AbmpReader.ReadIndex (cyclomatic 24) ArcFormats/Qlie/ArcABMP.cs:91 — AbmpReader.ReadIndex has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Xp3Opener.Create (cyclomatic 24) · ×1
  • Xp3Opener.Create (cyclomatic 24) ArcFormats/KiriKiri/ArcXP3.cs:467 — Xp3Opener.Create has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BipFormat.ReadMetaData (cyclomatic 23) · ×1
  • BipFormat.ReadMetaData (cyclomatic 23) ArcFormats/Kid/ImageBIP.cs:14 — BipFormat.ReadMetaData has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Bc7Decoder.UnpackBc7Mode1_3_7 (cyclomatic 23) · ×1
  • Bc7Decoder.UnpackBc7Mode1_3_7 (cyclomatic 23) ArcFormats/Unity/Bc7Decoder.cs:188 — Bc7Decoder.UnpackBc7Mode1_3_7 has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · VorbisInfo.UnpackMapping (cyclomatic 23) · ×1
  • VorbisInfo.UnpackMapping (cyclomatic 23) ArcFormats/Unity/Vorbis.cs:585 — VorbisInfo.UnpackMapping has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · aPLibCoroutine.Unpack (cyclomatic 23) · ×1
  • aPLibCoroutine.Unpack (cyclomatic 23) ArcFormats/aPLibStream.cs:31 — aPLibCoroutine.Unpack has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AniOpener.TryOpen (cyclomatic 22) · ×1
  • AniOpener.TryOpen (cyclomatic 22) ArcFormats/AnimeGameSystem/ArcANI.cs:50 — AniOpener.TryOpen has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PictReader.DecodeRleBitmap (cyclomatic 22) · ×1
  • PictReader.DecodeRleBitmap (cyclomatic 22) ArcFormats/Macintosh/ImagePICT.cs:376 — PictReader.DecodeRleBitmap has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CRip007.UncompressRgb (cyclomatic 22) · ×1
  • CRip007.UncompressRgb (cyclomatic 22) ArcFormats/rUGP/ImageRIP.cs:517 — CRip007.UncompressRgb has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CRip007.UncompressRgba (cyclomatic 22) · ×1
  • CRip007.UncompressRgba (cyclomatic 22) ArcFormats/rUGP/ImageRIP.cs:631 — CRip007.UncompressRgba has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ArcGOpener.TryOpen (cyclomatic 22) · ×1
  • ArcGOpener.TryOpen (cyclomatic 22) ArcFormats/Tanaka/ArcARCG.cs:51 — ArcGOpener.TryOpen has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MblOpener.ReadIndex (cyclomatic 22) · ×1
  • MblOpener.ReadIndex (cyclomatic 22) ArcFormats/Marble/ArcMBL.cs:91 — MblOpener.ReadIndex has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Reader.ReadCompressedChunk (cyclomatic 22) · ×1
  • Reader.ReadCompressedChunk (cyclomatic 22) ArcFormats/elf/ImageGCC.cs:313 — Reader.ReadCompressedChunk has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TlgFormat.ReadMetaData (cyclomatic 22) · ×1
  • TlgFormat.ReadMetaData (cyclomatic 22) ArcFormats/KiriKiri/ImageTLG.cs:46 — TlgFormat.ReadMetaData has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · T32Format.Read (cyclomatic 22) · ×1
  • T32Format.Read (cyclomatic 22) Legacy/Broccoli/ImageT32.cs:99 — T32Format.Read has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GraBaseReader.UnpackBitsInternal (cyclomatic 22) · ×1
  • GraBaseReader.UnpackBitsInternal (cyclomatic 22) Legacy/System98/ImageG.cs:115 — GraBaseReader.UnpackBitsInternal has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GimFormat.ReadMetaData (cyclomatic 21) · ×1
  • GimFormat.ReadMetaData (cyclomatic 21) ArcFormats/Psp/ArcGim.cs:30 — GimFormat.ReadMetaData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · OrgImageDecoder.GetImageData (cyclomatic 21) · ×1
  • OrgImageDecoder.GetImageData (cyclomatic 21) ArcFormats/Origin/ArcDAT.cs:178 — OrgImageDecoder.GetImageData has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · GdReader.UnpackP (cyclomatic 21) · ×1
  • GdReader.UnpackP (cyclomatic 21) ArcFormats/C4/ImageGD.cs:191 — GdReader.UnpackP has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · InfoReader.ParseInfo (cyclomatic 21) · ×1
  • InfoReader.ParseInfo (cyclomatic 21) ArcFormats/Glib2/ImagePGX.cs:176 — InfoReader.ParseInfo has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Bc7Decoder.UnpackBc7Mode0_2 (cyclomatic 21) · ×1
  • Bc7Decoder.UnpackBc7Mode0_2 (cyclomatic 21) ArcFormats/Unity/Bc7Decoder.cs:138 — Bc7Decoder.UnpackBc7Mode0_2 has cyclomatic complexity 21 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · PcmDecoder.sub_411AB0 (cyclomatic 21) · ×1
  • PcmDecoder.sub_411AB0 (cyclomatic 21) ArcFormats/Circus/AudioPCM.cs:266 — PcmDecoder.sub_411AB0 has cyclomatic complexity 21 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · Reader.UnpackRGBA (cyclomatic 21) · ×1
  • Reader.UnpackRGBA (cyclomatic 21) ArcFormats/Lucifen/ImageELG.cs:249 — Reader.UnpackRGBA has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (Reader.UnpackRGB) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · Reader.UnpackRGB (cyclomatic 21) · ×1
  • Reader.UnpackRGB (cyclomatic 21) ArcFormats/Lucifen/ImageELG.cs:460 — Reader.UnpackRGB has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (Reader.UnpackRGBA) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · EriFormat.ReadMetaData (cyclomatic 21) · ×1
  • EriFormat.ReadMetaData (cyclomatic 21) ArcFormats/Entis/ImageERI.cs:159 — EriFormat.ReadMetaData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GReader.GetColorFromTable (cyclomatic 21) · ×1
  • GReader.GetColorFromTable (cyclomatic 21) Legacy/HyperWorks/ImageG.cs:205 — GReader.GetColorFromTable has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · NpReader.UnpackBits (cyclomatic 21) · ×1
  • NpReader.UnpackBits (cyclomatic 21) Legacy/Paprika/ImageNP.cs:151 — NpReader.UnpackBits has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PakOpener.TryOpen (cyclomatic 20) · ×1
  • PakOpener.TryOpen (cyclomatic 20) ArcFormats/Ivory/ArcPK.cs:52 — PakOpener.TryOpen has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PxFormat.ReadMetaData (cyclomatic 20) · ×1
  • PxFormat.ReadMetaData (cyclomatic 20) ArcFormats/Leaf/ImagePX.cs:53 — PxFormat.ReadMetaData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Deserializer.DeserializeUTFChunk (cyclomatic 20) · ×1
  • Deserializer.DeserializeUTFChunk (cyclomatic 20) ArcFormats/Cri/ArcCPK.cs:276 — Deserializer.DeserializeUTFChunk has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · HcaReader.ParseHeader (cyclomatic 20) · ×1
  • HcaReader.ParseHeader (cyclomatic 20) ArcFormats/Cri/AudioHCA.cs:276 — HcaReader.ParseHeader has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · IndexReader.ParseDirEntry (cyclomatic 20) · ×1
  • IndexReader.ParseDirEntry (cyclomatic 20) REDACTED:331 — IndexReader.ParseDirEntry has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DrgFormat.DecodeStream (cyclomatic 20) · ×1
  • DrgFormat.DecodeStream (cyclomatic 20) ArcFormats/Ikura/ImageDRG.cs:120 — DrgFormat.DecodeStream has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Mi2Reader.UnpackChannel (cyclomatic 20) · ×1
  • Mi2Reader.UnpackChannel (cyclomatic 20) Legacy/Mapl/ImageMI2.cs:149 — Mi2Reader.UnpackChannel has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · UgReader.UnpackBitsInternal (cyclomatic 20) · ×1
  • UgReader.UnpackBitsInternal (cyclomatic 20) Legacy/Ucom/ImageUG.cs:102 — UgReader.UnpackBitsInternal has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GrpOpener.DetectFileTypes (cyclomatic 19) · ×1
  • GrpOpener.DetectFileTypes (cyclomatic 19) ArcFormats/Ankh/ArcGRP.cs:86 — GrpOpener.DetectFileTypes has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GimFormat.Read (cyclomatic 19) · ×1
  • GimFormat.Read (cyclomatic 19) ArcFormats/Psp/ArcGim.cs:128 — GimFormat.Read has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AkbReader.Unpack (cyclomatic 19) · ×1
  • AkbReader.Unpack (cyclomatic 19) ArcFormats/Silky/ImageAKB.cs:144 — AkbReader.Unpack has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TacOpener.TryOpen (cyclomatic 19) · ×1
  • TacOpener.TryOpen (cyclomatic 19) ArcFormats/TanukiSoft/ArcTAC.cs:54 — TacOpener.TryOpen has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PakOpener.TryOpen (cyclomatic 19) · ×1
  • PakOpener.TryOpen (cyclomatic 19) ArcFormats/GsPack/ArcGsPack.cs:59 — PakOpener.TryOpen has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · WarOpener.TryOpen (cyclomatic 19) · ×1
  • WarOpener.TryOpen (cyclomatic 19) ArcFormats/ShiinaRio/ArcWARC.cs:80 — WarOpener.TryOpen 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.
D1 · Cyclomatic Complexity · Reader.UnpackV2 (cyclomatic 19) · ×1
  • Reader.UnpackV2 (cyclomatic 19) ArcFormats/Circus/ImageCRX.cs:316 — Reader.UnpackV2 has cyclomatic complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · SeraphReader.UnpackBytes (cyclomatic 19) · ×1
  • SeraphReader.UnpackBytes (cyclomatic 19) ArcFormats/Seraphim/ImageSeraph.cs:368 — SeraphReader.UnpackBytes has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · WbmReader.UnpackV5 (cyclomatic 19) · ×1
  • WbmReader.UnpackV5 (cyclomatic 19) ArcFormats/WildBug/ImageWBM.cs:528 — WbmReader.UnpackV5 has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PrReader.UnpackPlanes (cyclomatic 19) · ×1
  • PrReader.UnpackPlanes (cyclomatic 19) Legacy/Discovery/ImagePR1.cs:110 — PrReader.UnpackPlanes has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PicReader.Unpack (cyclomatic 19) · ×1
  • PicReader.Unpack (cyclomatic 19) Legacy/Grocer/ImagePIC.cs:83 — PicReader.Unpack has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · I24Decoder.RebuildTree (cyclomatic 19) · ×1
  • I24Decoder.RebuildTree (cyclomatic 19) Legacy/HyperWorks/ImageI24.cs:275 — I24Decoder.RebuildTree has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PackImageDecoder.Unpack8bpp (cyclomatic 19) · ×1
  • PackImageDecoder.Unpack8bpp (cyclomatic 19) Legacy/Lune/ArcPACK.cs:233 — PackImageDecoder.Unpack8bpp has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TexFormat.Read (cyclomatic 18) · ×1
  • TexFormat.Read (cyclomatic 18) ArcFormats/Artdink/ImageTEX.cs:107 — TexFormat.Read has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MrgOpener.ReadInfo (cyclomatic 18) · ×1
  • MrgOpener.ReadInfo (cyclomatic 18) ArcFormats/HuneX/ArcMZP.cs:110 — MrgOpener.ReadInfo has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · LsdOpener.OpenEntry (cyclomatic 18) · ×1
  • LsdOpener.OpenEntry (cyclomatic 18) ArcFormats/Gss/ArcARC.cs:77 — LsdOpener.OpenEntry has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GrpOpener.TryOpen (cyclomatic 18) · ×1
  • GrpOpener.TryOpen (cyclomatic 18) ArcFormats/ExHibit/ArcGRP.cs:45 — GrpOpener.TryOpen has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AImageReader.Unpack (cyclomatic 18) · ×1
  • AImageReader.Unpack (cyclomatic 18) ArcFormats/Cyberworks/ImageTINK.cs:173 — AImageReader.Unpack has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · BinOpener.TryOpen (cyclomatic 18) · ×1
  • BinOpener.TryOpen (cyclomatic 18) ArcFormats/Patisserie/ArcBIN.cs:49 — BinOpener.TryOpen has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EriOpener.TryOpen (cyclomatic 18) · ×1
  • EriOpener.TryOpen (cyclomatic 18) ArcFormats/Entis/ArcERI.cs:53 — EriOpener.TryOpen has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CpzOpener.FindArchiveKey (cyclomatic 18) · ×1
  • CpzOpener.FindArchiveKey (cyclomatic 18) ArcFormats/Cmvs/ArcCPZ.cs:526 — CpzOpener.FindArchiveKey has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Pb3Reader.UnpackV1 (cyclomatic 18) · ×1
  • Pb3Reader.UnpackV1 (cyclomatic 18) ArcFormats/Cmvs/ImagePB3.cs:229 — Pb3Reader.UnpackV1 has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · PakOpener.TryOpen (cyclomatic 18) · ×1
  • PakOpener.TryOpen (cyclomatic 18) ArcFormats/TamaSoft/ArcEPK.cs:72 — PakOpener.TryOpen has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AmiOpener.Create (cyclomatic 18) · ×1
  • AmiOpener.Create (cyclomatic 18) ArcFormats/Amaterasu/ArcAMI.cs:153 — AmiOpener.Create has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PacOpener.TryOpen (cyclomatic 18) · ×1
  • PacOpener.TryOpen (cyclomatic 18) ArcFormats/Tmr-Hiro/ArcPAC.cs:47 — PacOpener.TryOpen has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Writer.WriteV2 (cyclomatic 18) · ×1
  • Writer.WriteV2 (cyclomatic 18) ArcFormats/Circus/ImageCRX.cs:502 — Writer.WriteV2 has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · Reader.UnpackLine (cyclomatic 18) · ×1
  • Reader.UnpackLine (cyclomatic 18) ArcFormats/ShiinaRio/ImageS25.cs:222 — Reader.UnpackLine has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Reader.ReadLine (cyclomatic 18) · ×1
  • Reader.ReadLine (cyclomatic 18) ArcFormats/ShiinaRio/ImageS25.cs:303 — Reader.ReadLine has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · TlgFormat.ReadV6 (cyclomatic 18) · ×1
  • TlgFormat.ReadV6 (cyclomatic 18) ArcFormats/KiriKiri/ImageTLG.cs:259 — TlgFormat.ReadV6 has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · WbmReader.UnpackV3 (cyclomatic 18) · ×1
  • WbmReader.UnpackV3 (cyclomatic 18) ArcFormats/WildBug/ImageWBM.cs:718 — WbmReader.UnpackV3 has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PngFormat.ReadMetaData (cyclomatic 18) · ×1
  • PngFormat.ReadMetaData (cyclomatic 18) GameRes/ImagePNG.cs:121 — PngFormat.ReadMetaData has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · A5rOpener.TryOpen (cyclomatic 18) · ×1
  • A5rOpener.TryOpen (cyclomatic 18) Legacy/Pinky/ArcA5R.cs:66 — A5rOpener.TryOpen has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PackImageDecoder.Unpack24bpp (cyclomatic 18) · ×1
  • PackImageDecoder.Unpack24bpp (cyclomatic 18) Legacy/Lune/ArcPACK.cs:165 — PackImageDecoder.Unpack24bpp has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ParallelCbgDecoder.UnpackBlock (cyclomatic 17) · ×1
  • ParallelCbgDecoder.UnpackBlock (cyclomatic 17) ArcFormats/Ethornell/ImageCBG.cs:447 — ParallelCbgDecoder.UnpackBlock has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SceneOpener.TryOpen (cyclomatic 17) · ×1
  • SceneOpener.TryOpen (cyclomatic 17) ArcFormats/RealLive/ArcSCENE.cs:76 — SceneOpener.TryOpen has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GStream.EnumeratePages (cyclomatic 17) · ×1
  • GStream.EnumeratePages (cyclomatic 17) ArcFormats/Leaf/AudioG.cs:125 — GStream.EnumeratePages has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Channel.Decode1 (cyclomatic 17) · ×1
  • Channel.Decode1 (cyclomatic 17) ArcFormats/Cri/AudioHCA.cs:682 — Channel.Decode1 has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NwaDecoder.DecodeBlock (cyclomatic 17) · ×1
  • NwaDecoder.DecodeBlock (cyclomatic 17) ArcFormats/RealLive/AudioNWA.cs:144 — NwaDecoder.DecodeBlock has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Decoder.DoEncryption (cyclomatic 17) · ×1
  • Decoder.DoEncryption (cyclomatic 17) ArcFormats/ShiinaRio/WarcEncryption.cs:140 — Decoder.DoEncryption has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PcsOpener.TryOpen (cyclomatic 17) · ×1
  • PcsOpener.TryOpen (cyclomatic 17) ArcFormats/CsWare/ArcPCS.cs:62 — PcsOpener.TryOpen has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GhpReader.Unpack3 (cyclomatic 17) · ×1
  • GhpReader.Unpack3 (cyclomatic 17) ArcFormats/Succubus/ImageGH.cs:199 — GhpReader.Unpack3 has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PakOpener.TryOpen (cyclomatic 17) · ×1
  • PakOpener.TryOpen (cyclomatic 17) ArcFormats/Eagls/ArcEAGLS.cs:54 — PakOpener.TryOpen has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TcdOpener.OpenSpdc (cyclomatic 17) · ×1
  • TcdOpener.OpenSpdc (cyclomatic 17) ArcFormats/TopCat/ArcTCD3.cs:127 — TcdOpener.OpenSpdc has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · RpaOpener.TryOpen (cyclomatic 17) · ×1
  • RpaOpener.TryOpen (cyclomatic 17) ArcFormats/RenPy/ArcRPA.cs:59 — RpaOpener.TryOpen has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · OggStreamState.Flush (cyclomatic 17) · ×1
  • OggStreamState.Flush (cyclomatic 17) ArcFormats/Unity/OggStream.cs:286 — OggStreamState.Flush has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ResourcesAssetsDeserializer.Parse (cyclomatic 17) · ×1
  • ResourcesAssetsDeserializer.Parse (cyclomatic 17) ArcFormats/Unity/ResourcesAssets.cs:41 — ResourcesAssetsDeserializer.Parse has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MioDecoder.Initialize (cyclomatic 17) · ×1
  • MioDecoder.Initialize (cyclomatic 17) ArcFormats/Entis/MioDecoder.cs:83 — MioDecoder.Initialize has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ArchPacOpener.ReadIndex (cyclomatic 17) · ×1
  • ArchPacOpener.ReadIndex (cyclomatic 17) ArcFormats/Seraphim/ArcSeraph.cs:121 — ArchPacOpener.ReadIndex has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ArcOpener.Create (cyclomatic 17) · ×1
  • ArcOpener.Create (cyclomatic 17) ArcFormats/Will/ArcWILL.cs:168 — ArcOpener.Create has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Reader.UnpackColorData (cyclomatic 17) · ×1
  • Reader.UnpackColorData (cyclomatic 17) ArcFormats/UMeSoft/ImageGRX.cs:186 — Reader.UnpackColorData has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Reader.Unpack (cyclomatic 17) · ×1
  • Reader.Unpack (cyclomatic 17) ArcFormats/Marble/ImagePRS.cs:122 — Reader.Unpack has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TbmFormat.ReadMetaData (cyclomatic 17) · ×1
  • TbmFormat.ReadMetaData (cyclomatic 17) Legacy/Broccoli/ImageTbm.cs:55 — TbmFormat.ReadMetaData 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.
D1 · Cyclomatic Complexity · Mai3Reader.UnpackLine (cyclomatic 17) · ×1
  • Mai3Reader.UnpackLine (cyclomatic 17) Legacy/Izumi/ImageMAI3.cs:125 — Mai3Reader.UnpackLine has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TtpOpener.TryOpen (cyclomatic 17) · ×1
  • TtpOpener.TryOpen (cyclomatic 17) Legacy/NAUTS/ArcTTP.cs:63 — TtpOpener.TryOpen has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MpkCompression.sub_42A540 (cyclomatic 17) · ×1
  • MpkCompression.sub_42A540 (cyclomatic 17) Legacy/Kurumi/ArcMPK.cs:412 — MpkCompression.sub_42A540 has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ConsoleBrowser.Run (cyclomatic 16) · ×1
  • ConsoleBrowser.Run (cyclomatic 16) Console/ConsoleBrowser.cs:76 — ConsoleBrowser.Run has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · IndexReader.ReadDir (cyclomatic 16) · ×1
  • IndexReader.ReadDir (cyclomatic 16) ArcFormats/Ads/ArcPAC.cs:92 — IndexReader.ReadDir has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ZtOpener.TryOpen (cyclomatic 16) · ×1
  • ZtOpener.TryOpen (cyclomatic 16) ArcFormats/CatSystem/ArcZT.cs:53 — ZtOpener.TryOpen has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DatOpener.ReadIndex (cyclomatic 16) · ×1
  • DatOpener.ReadIndex (cyclomatic 16) ArcFormats/JamCreation/ArcDAT.cs:86 — DatOpener.ReadIndex has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PmsReader.Unpack16bpp (cyclomatic 16) · ×1
  • PmsReader.Unpack16bpp (cyclomatic 16) ArcFormats/AliceSoft/ImagePMS.cs:152 — PmsReader.Unpack16bpp has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · ImgReader.Unpack32bpp (cyclomatic 16) · ×1
  • ImgReader.Unpack32bpp (cyclomatic 16) ArcFormats/ScrPlayer/ImageIMG.cs:187 — ImgReader.Unpack32bpp has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Tim2Reader.Unpack (cyclomatic 16) · ×1
  • Tim2Reader.Unpack (cyclomatic 16) ArcFormats/DigitalWorks/ImageTM2.cs:130 — Tim2Reader.Unpack has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EvbPackOpener.TryOpen (cyclomatic 16) · ×1
  • EvbPackOpener.TryOpen (cyclomatic 16) ArcFormats/Enigma/ArcEVB.cs:54 — EvbPackOpener.TryOpen has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DatOpener.TryOpen (cyclomatic 16) · ×1
  • DatOpener.TryOpen (cyclomatic 16) ArcFormats/Groover/ArcPCG.cs:47 — DatOpener.TryOpen has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Lz4Compressor.DecompressBlock (cyclomatic 16) · ×1
  • Lz4Compressor.DecompressBlock (cyclomatic 16) ArcFormats/Lz4Stream.cs:222 — Lz4Compressor.DecompressBlock has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ArcIndexReader.ReadEntryType (cyclomatic 16) · ×1
  • ArcIndexReader.ReadEntryType (cyclomatic 16) ArcFormats/Cyberworks/ArcDAT.cs:726 — ArcIndexReader.ReadEntryType has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · AImageReader.ReadBaseline (cyclomatic 16) · ×1
  • AImageReader.ReadBaseline (cyclomatic 16) ArcFormats/Cyberworks/ImageTINK.cs:110 — AImageReader.ReadBaseline has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · VffOpener.TryOpen (cyclomatic 16) · ×1
  • VffOpener.TryOpen (cyclomatic 16) ArcFormats/LiveMaker/ArcVF.cs:51 — VffOpener.TryOpen has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · VocReader.ConvertToPcm (cyclomatic 16) · ×1
  • VocReader.ConvertToPcm (cyclomatic 16) ArcFormats/AudioVOC.cs:51 — VocReader.ConvertToPcm has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Reader.UnpackChannel (cyclomatic 16) · ×1
  • Reader.UnpackChannel (cyclomatic 16) ArcFormats/Liar/ImageLIM.cs:242 — Reader.UnpackChannel has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GalReader.ReadBlocks (cyclomatic 16) · ×1
  • GalReader.ReadBlocks (cyclomatic 16) ArcFormats/LiveMaker/ImageGAL.cs:318 — GalReader.ReadBlocks has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · IphReader.Unpack (cyclomatic 16) · ×1
  • IphReader.Unpack (cyclomatic 16) ArcFormats/TechnoBrain/ImageIPH.cs:111 — IphReader.Unpack has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · IarDecompressor.Unpack (cyclomatic 16) · ×1
  • IarDecompressor.Unpack (cyclomatic 16) ArcFormats/Sas5/ArcIAR.cs:430 — IarDecompressor.Unpack has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PakOpener.TryOpen (cyclomatic 16) · ×1
  • PakOpener.TryOpen (cyclomatic 16) ArcFormats/Hypatia/ArcKogado.cs:70 — PakOpener.TryOpen has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PakOpener.OpenPakV3 (cyclomatic 16) · ×1
  • PakOpener.OpenPakV3 (cyclomatic 16) ArcFormats/NitroPlus/ArcNitro.cs:122 — PakOpener.OpenPakV3 has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Reader.Unpack (cyclomatic 16) · ×1
  • Reader.Unpack (cyclomatic 16) ArcFormats/uGOS/ImageBMP.cs:133 — Reader.Unpack has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EriReader.EriReader.ctor (cyclomatic 16) · ×1
  • EriReader.EriReader.ctor (cyclomatic 16) ArcFormats/Entis/EriReader.cs:83 — EriReader.EriReader.ctor has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DwqFormat.ReadMetaData (cyclomatic 16) · ×1
  • DwqFormat.ReadMetaData (cyclomatic 16) ArcFormats/BlackCyc/ImageDWQ.cs:89 — DwqFormat.ReadMetaData has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SplReader.Unpack (cyclomatic 16) · ×1
  • SplReader.Unpack (cyclomatic 16) ArcFormats/Zyx/ImageSPL.cs:125 — SplReader.Unpack has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · WarOpener.OpenEntry (cyclomatic 16) · ×1
  • WarOpener.OpenEntry (cyclomatic 16) ArcFormats/ShiinaRio/ArcWARC.cs:155 — WarOpener.OpenEntry has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · YpfOpener.GetFileType (cyclomatic 16) · ×1
  • YpfOpener.GetFileType (cyclomatic 16) ArcFormats/YuRis/ArcYPF.cs:380 — YpfOpener.GetFileType has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · YpfOpener.DecryptYstb (cyclomatic 16) · ×1
  • YpfOpener.DecryptYstb (cyclomatic 16) ArcFormats/YuRis/ArcYPF.cs:419 — YpfOpener.DecryptYstb has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Reader.UnpackAlpha (cyclomatic 16) · ×1
  • Reader.UnpackAlpha (cyclomatic 16) ArcFormats/Lucifen/ImageELG.cs:375 — Reader.UnpackAlpha has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GswinGrpFormat.Decode (cyclomatic 16) · ×1
  • GswinGrpFormat.Decode (cyclomatic 16) ArcFormats/GsPack/ImageGS.cs:173 — GswinGrpFormat.Decode has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Reader.UnpackV2 (cyclomatic 16) · ×1
  • Reader.UnpackV2 (cyclomatic 16) ArcFormats/Ffa/ImagePT1.cs:178 — Reader.UnpackV2 has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SeraphReader.UnpackRgb (cyclomatic 16) · ×1
  • SeraphReader.UnpackRgb (cyclomatic 16) ArcFormats/Seraphim/ImageSeraph.cs:287 — SeraphReader.UnpackRgb has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TlgFormat.ReadV5 (cyclomatic 16) · ×1
  • TlgFormat.ReadV5 (cyclomatic 16) ArcFormats/KiriKiri/ImageTLG.cs:407 — TlgFormat.ReadV5 has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · WbmReader.Unpack (cyclomatic 16) · ×1
  • WbmReader.Unpack (cyclomatic 16) ArcFormats/WildBug/ImageWBM.cs:265 — WbmReader.Unpack has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · WbmReader.UnpackVD (cyclomatic 16) · ×1
  • WbmReader.UnpackVD (cyclomatic 16) ArcFormats/WildBug/ImageWBM.cs:317 — WbmReader.UnpackVD has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MainWindow.ExtractItemExec (cyclomatic 16) · ×1
  • MainWindow.ExtractItemExec (cyclomatic 16) GUI/GarExtract.cs:47 — MainWindow.ExtractItemExec has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BpeFormat.Decompress (cyclomatic 16) · ×1
  • BpeFormat.Decompress (cyclomatic 16) Legacy/QSoft/ImageBPE.cs:65 — BpeFormat.Decompress has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D17 · Explicit Debt · BareSuppressMessage repeated 19 times in one file · ×1
  • BareSuppressMessage repeated 19 times in one file Experimental/Artemis/ShiftReduceParserCode.cs:65 — The identical BareSuppressMessage (`SuppressMessage`) appears 19 times in one file — one decision applied repeatedly (e.g. the same rule silenced on every overload of a fluent API), not 19 independent debts. Decide it once — at the type or project level, or by fixing the underlying pattern — rather than occurrence-by-occurrence. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · HackComment · ×1
  • HackComment GUI/MainWindow.xaml:205 — <!-- hack to make images within disabled toolbar buttons appear 'grayed out'. This doesn't gray them at all, but lowers their opacity so the (usually gray) background of the button shows through. If WPF had a built-in facility for grayscaling images in disabled buttons, this kind of icky kludgery wouldn't be necessary --> — 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.
D18 · Solution Shape · Build failed · ×1
  • Build failed — The target solution did not build cleanly (errors: 14), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0246: The type or namespace name 'NAudio' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Newtonsoft' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'WaveStream' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'WaveFormatEncoding' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'DefaultContractResolver' could not be found (are you missing a using directive or an assembly reference?).
D2 · Cognitive Complexity · Xp3Opener.TryOpen (cognitive 184) · ×1
  • Xp3Opener.TryOpen (cognitive 184) ArcFormats/KiriKiri/ArcXP3.cs:105 — Xp3Opener.TryOpen has cognitive complexity 184 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Mai2Reader.UnpackPlane (cognitive 181) · ×1
  • Mai2Reader.UnpackPlane (cognitive 181) Legacy/Izumi/ImageMAI2.cs:139 — Mai2Reader.UnpackPlane has cognitive complexity 181 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pl4Reader.UnpackV1 (cognitive 135) · ×1
  • Pl4Reader.UnpackV1 (cognitive 135) Legacy/Pearl/ImagePL4.cs:207 — Pl4Reader.UnpackV1 has cognitive complexity 135 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NemesisDecodeContext.DecodeNemesisCodeBytes (cognitive 104) · ×1
  • NemesisDecodeContext.DecodeNemesisCodeBytes (cognitive 104) ArcFormats/Entis/ErisaNemesis.cs:71 — NemesisDecodeContext.DecodeNemesisCodeBytes has cognitive complexity 104 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · aPLibCoroutine.Unpack (cognitive 101) · ×1
  • aPLibCoroutine.Unpack (cognitive 101) ArcFormats/aPLibStream.cs:31 — aPLibCoroutine.Unpack has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CRip007.UncompressRgba (cognitive 100) · ×1
  • CRip007.UncompressRgba (cognitive 100) ArcFormats/rUGP/ImageRIP.cs:631 — CRip007.UncompressRgba has cognitive complexity 100 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NcgReader.Unpack (cognitive 98) · ×1
  • NcgReader.Unpack (cognitive 98) Legacy/Nekotaro/ImageNCG.cs:92 — NcgReader.Unpack has cognitive complexity 98 (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.
D2 · Cognitive Complexity · PolaReader.Unpack (cognitive 95) · ×1
  • PolaReader.Unpack (cognitive 95) ArcFormats/AdvSys/ImageGR2.cs:157 — PolaReader.Unpack has cognitive complexity 95 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · IkeReader.Unpack (cognitive 92) · ×1
  • IkeReader.Unpack (cognitive 92) Legacy/UMeSoft/ArcBIN.cs:126 — IkeReader.Unpack has cognitive complexity 92 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CRip007.UncompressRgb (cognitive 91) · ×1
  • CRip007.UncompressRgb (cognitive 91) ArcFormats/rUGP/ImageRIP.cs:517 — CRip007.UncompressRgb has cognitive complexity 91 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AbmpReader.ReadIndex (cognitive 91) · ×1
  • AbmpReader.ReadIndex (cognitive 91) ArcFormats/Qlie/ArcABMP.cs:91 — AbmpReader.ReadIndex has cognitive complexity 91 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BipFormat.Read (cognitive 81) · ×1
  • BipFormat.Read (cognitive 81) ArcFormats/Kid/ImageBIP.cs:139 — BipFormat.Read has cognitive complexity 81 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MioDecoder.DecodeSoundDCT (cognitive 80) · ×1
  • MioDecoder.DecodeSoundDCT (cognitive 80) ArcFormats/Entis/MioDecoder.cs:292 — MioDecoder.DecodeSoundDCT has cognitive complexity 80 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.ReadCompressedChunk (cognitive 76) · ×1
  • Reader.ReadCompressedChunk (cognitive 76) ArcFormats/elf/ImageGCC.cs:313 — Reader.ReadCompressedChunk has cognitive complexity 76 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GraBaseReader.UnpackBitsInternal (cognitive 71) · ×1
  • GraBaseReader.UnpackBitsInternal (cognitive 71) Legacy/System98/ImageG.cs:115 — GraBaseReader.UnpackBitsInternal has cognitive complexity 71 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Reader.UnpackColorData (cognitive 70) · ×1
  • Reader.UnpackColorData (cognitive 70) ArcFormats/UMeSoft/ImageGRX.cs:186 — Reader.UnpackColorData has cognitive complexity 70 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Parser.ReadMetaData (cognitive 69) · ×1
  • Parser.ReadMetaData (cognitive 69) GameRes/ImageTIFF.cs:165 — Parser.ReadMetaData has cognitive complexity 69 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PictReader.Unpack (cognitive 68) · ×1
  • PictReader.Unpack (cognitive 68) ArcFormats/Macintosh/ImagePICT.cs:166 — PictReader.Unpack has cognitive complexity 68 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pl4Reader.UnpackV0 (cognitive 68) · ×1
  • Pl4Reader.UnpackV0 (cognitive 68) Legacy/Pearl/ImagePL4.cs:119 — Pl4Reader.UnpackV0 has cognitive complexity 68 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LsdOpener.UnpackH (cognitive 66) · ×1
  • LsdOpener.UnpackH (cognitive 66) ArcFormats/Gss/ArcARC.cs:275 — LsdOpener.UnpackH has cognitive complexity 66 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LeafLzss.Compress (cognitive 64) · ×1
  • LeafLzss.Compress (cognitive 64) ArcFormats/Leaf/LeafCompression.cs:38 — LeafLzss.Compress has cognitive complexity 64 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PrReader.UnpackPlanes (cognitive 64) · ×1
  • PrReader.UnpackPlanes (cognitive 64) Legacy/Discovery/ImagePR1.cs:110 — PrReader.UnpackPlanes has cognitive complexity 64 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · KlzFormat.LzhStreamDecode (cognitive 62) · ×1
  • KlzFormat.LzhStreamDecode (cognitive 62) ArcFormats/Kid/ImageKLZ.cs:54 — KlzFormat.LzhStreamDecode has cognitive complexity 62 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UgReader.UnpackBitsInternal (cognitive 62) · ×1
  • UgReader.UnpackBitsInternal (cognitive 62) Legacy/Ucom/ImageUG.cs:102 — UgReader.UnpackBitsInternal has cognitive complexity 62 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Pickle.Load (cognitive 61) · ×1
  • Pickle.Load (cognitive 61) ArcFormats/RenPy/ArcRPA.cs:457 — Pickle.Load has cognitive complexity 61 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriReader.DecodeLosslessImage (cognitive 61) · ×1
  • EriReader.DecodeLosslessImage (cognitive 61) ArcFormats/Entis/EriReader.cs:435 — EriReader.DecodeLosslessImage has cognitive complexity 61 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackV2 (cognitive 61) · ×1
  • Reader.UnpackV2 (cognitive 61) ArcFormats/Circus/ImageCRX.cs:316 — Reader.UnpackV2 has cognitive complexity 61 (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.
D2 · Cognitive Complexity · GdtReader.Unpack8Line (cognitive 59) · ×1
  • GdtReader.Unpack8Line (cognitive 59) ArcFormats/CsWare/ImageGDT.cs:347 — GdtReader.Unpack8Line has cognitive complexity 59 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LagReader.RleUnpack (cognitive 57) · ×1
  • LagReader.RleUnpack (cognitive 57) ArcFormats/Strikes/ImageLAG.cs:205 — LagReader.RleUnpack has cognitive complexity 57 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WebPFormat.ReadMetaData (cognitive 57) · ×1
  • WebPFormat.ReadMetaData (cognitive 57) Experimental/WebP/ImageWEBP.cs:68 — WebPFormat.ReadMetaData has cognitive complexity 57 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Pb3Reader.UnpackV1 (cognitive 54) · ×1
  • Pb3Reader.UnpackV1 (cognitive 54) ArcFormats/Cmvs/ImagePB3.cs:229 — Pb3Reader.UnpackV1 has cognitive complexity 54 (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.
D2 · Cognitive Complexity · Writer.WriteV2 (cognitive 54) · ×1
  • Writer.WriteV2 (cognitive 54) ArcFormats/Circus/ImageCRX.cs:502 — Writer.WriteV2 has cognitive complexity 54 (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.
D2 · Cognitive Complexity · NwaDecoder.DecodeBlock (cognitive 53) · ×1
  • NwaDecoder.DecodeBlock (cognitive 53) ArcFormats/RealLive/AudioNWA.cs:144 — NwaDecoder.DecodeBlock has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · I24Decoder.RebuildTree (cognitive 53) · ×1
  • I24Decoder.RebuildTree (cognitive 53) Legacy/HyperWorks/ImageI24.cs:275 — I24Decoder.RebuildTree has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GdtReader.UnpackDouble (cognitive 52) · ×1
  • GdtReader.UnpackDouble (cognitive 52) ArcFormats/CsWare/ImageGDT.cs:141 — GdtReader.UnpackDouble has cognitive complexity 52 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VorbisInfo.StaticBookUnpack (cognitive 52) · ×1
  • VorbisInfo.StaticBookUnpack (cognitive 52) ArcFormats/Unity/Vorbis.cs:310 — VorbisInfo.StaticBookUnpack has cognitive complexity 52 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PcmDecoder.sub_411AB0 (cognitive 51) · ×1
  • PcmDecoder.sub_411AB0 (cognitive 51) ArcFormats/Circus/AudioPCM.cs:266 — PcmDecoder.sub_411AB0 has cognitive complexity 51 (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.
D2 · Cognitive Complexity · NpReader.UnpackBits (cognitive 51) · ×1
  • NpReader.UnpackBits (cognitive 51) Legacy/Paprika/ImageNP.cs:151 — NpReader.UnpackBits has cognitive complexity 51 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IphReader.Unpack (cognitive 50) · ×1
  • IphReader.Unpack (cognitive 50) ArcFormats/TechnoBrain/ImageIPH.cs:111 — IphReader.Unpack has cognitive complexity 50 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackV2 (cognitive 50) · ×1
  • Reader.UnpackV2 (cognitive 50) ArcFormats/Ffa/ImagePT1.cs:178 — Reader.UnpackV2 has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MvDecoder.Unpack (cognitive 49) · ×1
  • MvDecoder.Unpack (cognitive 49) ArcFormats/Cmvs/AudioMV.cs:142 — MvDecoder.Unpack has cognitive complexity 49 (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.
D2 · Cognitive Complexity · MioDecoder.DecodeSoundDCT_MSS (cognitive 49) · ×1
  • MioDecoder.DecodeSoundDCT_MSS (cognitive 49) ArcFormats/Entis/MioDecoder.cs:585 — MioDecoder.DecodeSoundDCT_MSS has cognitive complexity 49 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TbmFormat.Read (cognitive 49) · ×1
  • TbmFormat.Read (cognitive 49) Legacy/Broccoli/ImageTbm.cs:93 — TbmFormat.Read has cognitive complexity 49 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PicReader.Unpack (cognitive 49) · ×1
  • PicReader.Unpack (cognitive 49) Legacy/Grocer/ImagePIC.cs:83 — PicReader.Unpack has cognitive complexity 49 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WbmReader.UnpackV5 (cognitive 48) · ×1
  • WbmReader.UnpackV5 (cognitive 48) ArcFormats/WildBug/ImageWBM.cs:528 — WbmReader.UnpackV5 has cognitive complexity 48 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PackImageDecoder.Unpack24bpp (cognitive 48) · ×1
  • PackImageDecoder.Unpack24bpp (cognitive 48) Legacy/Lune/ArcPACK.cs:165 — PackImageDecoder.Unpack24bpp has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Arc3Opener.TryOpen (cognitive 47) · ×1
  • Arc3Opener.TryOpen (cognitive 47) ArcFormats/CaramelBox/ArcARC3.cs:57 — Arc3Opener.TryOpen has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JbpReader.Decode (cognitive 47) · ×1
  • JbpReader.Decode (cognitive 47) ArcFormats/Cmvs/ImagePB3.cs:572 — JbpReader.Decode has cognitive complexity 47 (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.
D2 · Cognitive Complexity · Reader.Unpack (cognitive 47) · ×1
  • Reader.Unpack (cognitive 47) ArcFormats/ActiveSoft/ImageEDT.cs:184 — Reader.Unpack has cognitive complexity 47 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Reader.UnpackRGBA (cognitive 47) · ×1
  • Reader.UnpackRGBA (cognitive 47) ArcFormats/Lucifen/ImageELG.cs:249 — Reader.UnpackRGBA has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Reader.UnpackRGB) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Reader.UnpackRGB (cognitive 47) · ×1
  • Reader.UnpackRGB (cognitive 47) ArcFormats/Lucifen/ImageELG.cs:460 — Reader.UnpackRGB has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Reader.UnpackRGBA) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · BpeFormat.Decompress (cognitive 47) · ×1
  • BpeFormat.Decompress (cognitive 47) Legacy/QSoft/ImageBPE.cs:65 — BpeFormat.Decompress has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FcbFormat.Unpack (cognitive 45) · ×1
  • FcbFormat.Unpack (cognitive 45) ArcFormats/CaramelBox/ImageFCB.cs:89 — FcbFormat.Unpack has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PazOpener.TryOpen (cognitive 45) · ×1
  • PazOpener.TryOpen (cognitive 45) ArcFormats/Musica/ArcPAZ.cs:179 — PazOpener.TryOpen has cognitive complexity 45 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WbmReader.UnpackV3 (cognitive 45) · ×1
  • WbmReader.UnpackV3 (cognitive 45) ArcFormats/WildBug/ImageWBM.cs:718 — WbmReader.UnpackV3 has cognitive complexity 45 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Wa1Reader.UnpackV12 (cognitive 43) · ×1
  • Wa1Reader.UnpackV12 (cognitive 43) ArcFormats/Ffa/AudioWA1.cs:403 — Wa1Reader.UnpackV12 has cognitive complexity 43 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · I24Decoder.Unpack (cognitive 43) · ×1
  • I24Decoder.Unpack (cognitive 43) Legacy/HyperWorks/ImageI24.cs:139 — I24Decoder.Unpack has cognitive complexity 43 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PackImageDecoder.Unpack8bpp (cognitive 43) · ×1
  • PackImageDecoder.Unpack8bpp (cognitive 43) Legacy/Lune/ArcPACK.cs:233 — PackImageDecoder.Unpack8bpp has cognitive complexity 43 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GrpUnpacker.UnpackHDJVariant (cognitive 42) · ×1
  • GrpUnpacker.UnpackHDJVariant (cognitive 42) ArcFormats/Ankh/ArcGRP.cs:372 — GrpUnpacker.UnpackHDJVariant has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HxCrypt.ReadIndex (cognitive 42) · ×1
  • HxCrypt.ReadIndex (cognitive 42) ArcFormats/KiriKiri/HxCrypt.cs:91 — HxCrypt.ReadIndex has cognitive complexity 42 (threshold 15). Of this number, 39 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GdReader.UnpackP (cognitive 42) · ×1
  • GdReader.UnpackP (cognitive 42) ArcFormats/C4/ImageGD.cs:191 — GdReader.UnpackP has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriReader.DecodeLossyImage (cognitive 42) · ×1
  • EriReader.DecodeLossyImage (cognitive 42) ArcFormats/Entis/EriReader.cs:631 — EriReader.DecodeLossyImage has cognitive complexity 42 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Parser.ScanDir (cognitive 42) · ×1
  • Parser.ScanDir (cognitive 42) ArcFormats/YuRis/ArcYPF.cs:487 — Parser.ScanDir has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PsbReader.UnpackV3 (cognitive 41) · ×1
  • PsbReader.UnpackV3 (cognitive 41) ArcFormats/Cmvs/ImagePSB.cs:161 — PsbReader.UnpackV3 has cognitive complexity 41 (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.
D2 · Cognitive Complexity · Unpacker.DecodeSPB (cognitive 41) · ×1
  • Unpacker.DecodeSPB (cognitive 41) ArcFormats/NScripter/ArcNSA.cs:408 — Unpacker.DecodeSPB has cognitive complexity 41 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PictReader.DecodeRleBitmap (cognitive 40) · ×1
  • PictReader.DecodeRleBitmap (cognitive 40) ArcFormats/Macintosh/ImagePICT.cs:376 — PictReader.DecodeRleBitmap has cognitive complexity 40 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pb2Reader.UnpackV2 (cognitive 40) · ×1
  • Pb2Reader.UnpackV2 (cognitive 40) ArcFormats/Cmvs/ImagePB2.cs:166 — Pb2Reader.UnpackV2 has cognitive complexity 40 (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.
D2 · Cognitive Complexity · CRip.ReadLong (cognitive 40) · ×1
  • CRip.ReadLong (cognitive 40) ArcFormats/rUGP/ImageRIP.cs:315 — CRip.ReadLong has cognitive complexity 40 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Xp3Opener.Create (cognitive 40) · ×1
  • Xp3Opener.Create (cognitive 40) ArcFormats/KiriKiri/ArcXP3.cs:467 — Xp3Opener.Create has cognitive complexity 40 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GStream.EnumeratePages (cognitive 39) · ×1
  • GStream.EnumeratePages (cognitive 39) ArcFormats/Leaf/AudioG.cs:125 — GStream.EnumeratePages has cognitive complexity 39 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IarDecompressor.Unpack (cognitive 39) · ×1
  • IarDecompressor.Unpack (cognitive 39) ArcFormats/Sas5/ArcIAR.cs:430 — IarDecompressor.Unpack has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Packer.EncodeLZSS (cognitive 39) · ×1
  • Packer.EncodeLZSS (cognitive 39) ArcFormats/NScripter/ArcNSA.cs:515 — Packer.EncodeLZSS has cognitive complexity 39 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TlgFormat.ReadV5 (cognitive 39) · ×1
  • TlgFormat.ReadV5 (cognitive 39) ArcFormats/KiriKiri/ImageTLG.cs:407 — TlgFormat.ReadV5 has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ExpReader.Unpack (cognitive 39) · ×1
  • ExpReader.Unpack (cognitive 39) Legacy/Clio/ImageEXP.cs:93 — ExpReader.Unpack has cognitive complexity 39 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SgRgbReader.UnpackV2Alpha (cognitive 38) · ×1
  • SgRgbReader.UnpackV2Alpha (cognitive 38) ArcFormats/Ivory/ImageSG.cs:277 — SgRgbReader.UnpackV2Alpha has cognitive complexity 38 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Wa1Reader.UnpackV4 (cognitive 38) · ×1
  • Wa1Reader.UnpackV4 (cognitive 38) ArcFormats/Ffa/AudioWA1.cs:123 — Wa1Reader.UnpackV4 has cognitive complexity 38 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TrkDecoder.Decode (cognitive 37) · ×1
  • TrkDecoder.Decode (cognitive 37) ArcFormats/Ivory/AudioCTRK.cs:131 — TrkDecoder.Decode has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GbpReader.UnpackBlocks (cognitive 37) · ×1
  • GbpReader.UnpackBlocks (cognitive 37) ArcFormats/Sviu/ImageGBP.cs:213 — GbpReader.UnpackBlocks has cognitive complexity 37 (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.
D2 · Cognitive Complexity · RmskReader.UnpackV0 (cognitive 37) · ×1
  • RmskReader.UnpackV0 (cognitive 37) ArcFormats/Silky/ImageMSK.cs:105 — RmskReader.UnpackV0 has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PackOpener.Decompress (cognitive 37) · ×1
  • PackOpener.Decompress (cognitive 37) ArcFormats/Qlie/ArcQLIE.cs:187 — PackOpener.Decompress has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackAlpha (cognitive 37) · ×1
  • Reader.UnpackAlpha (cognitive 37) ArcFormats/Lucifen/ImageELG.cs:375 — Reader.UnpackAlpha has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackV2 (cognitive 37) · ×1
  • Reader.UnpackV2 (cognitive 37) ArcFormats/ShiinaRio/ImageMI4.cs:225 — Reader.UnpackV2 has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LzssCoroutine.Unpack (cognitive 37) · ×1
  • LzssCoroutine.Unpack (cognitive 37) ArcFormats/LzssStream.cs:64 — LzssCoroutine.Unpack has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MpkCompression.sub_42A540 (cognitive 37) · ×1
  • MpkCompression.sub_42A540 (cognitive 37) Legacy/Kurumi/ArcMPK.cs:412 — MpkCompression.sub_42A540 has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GimFormat.Read (cognitive 36) · ×1
  • GimFormat.Read (cognitive 36) ArcFormats/Psp/ArcGim.cs:128 — GimFormat.Read has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RangePackedStream.Unpack (cognitive 36) · ×1
  • RangePackedStream.Unpack (cognitive 36) ArcFormats/Primel/Compression.cs:214 — RangePackedStream.Unpack has cognitive complexity 36 (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.
D2 · Cognitive Complexity · GbcReader.UnpackV1 (cognitive 36) · ×1
  • GbcReader.UnpackV1 (cognitive 36) ArcFormats/Primel/ImageGBC.cs:107 — GbcReader.UnpackV1 has cognitive complexity 36 (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.
D2 · Cognitive Complexity · VorbisInfo.UnpackBooks (cognitive 36) · ×1
  • VorbisInfo.UnpackBooks (cognitive 36) ArcFormats/Unity/Vorbis.cs:215 — VorbisInfo.UnpackBooks has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.Unpack (cognitive 36) · ×1
  • Reader.Unpack (cognitive 36) ArcFormats/Marble/ImagePRS.cs:122 — Reader.Unpack has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Giz2Reader.UnpackPlane (cognitive 36) · ×1
  • Giz2Reader.UnpackPlane (cognitive 36) Legacy/Adviz/ImageGIZ2.cs:121 — Giz2Reader.UnpackPlane has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TczReader.Unpack (cognitive 36) · ×1
  • TczReader.Unpack (cognitive 36) Legacy/Ponytail/ImageTCZ.cs:91 — TczReader.Unpack has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · A5rOpener.TryOpen (cognitive 36) · ×1
  • A5rOpener.TryOpen (cognitive 36) Legacy/Pinky/ArcA5R.cs:66 — A5rOpener.TryOpen has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OrgImageDecoder.GetImageData (cognitive 35) · ×1
  • OrgImageDecoder.GetImageData (cognitive 35) ArcFormats/Origin/ArcDAT.cs:178 — OrgImageDecoder.GetImageData has cognitive complexity 35 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · MgdDecoder.UnpackColor (cognitive 35) · ×1
  • MgdDecoder.UnpackColor (cognitive 35) ArcFormats/NSystem/ImageMGD.cs:180 — MgdDecoder.UnpackColor has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GbcReader.UnpackV2 (cognitive 35) · ×1
  • GbcReader.UnpackV2 (cognitive 35) ArcFormats/Primel/ImageGBC.cs:159 — GbcReader.UnpackV2 has cognitive complexity 35 (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.
D2 · Cognitive Complexity · Bc7Decoder.UnpackBc7Mode1_3_7 (cognitive 35) · ×1
  • Bc7Decoder.UnpackBc7Mode1_3_7 (cognitive 35) ArcFormats/Unity/Bc7Decoder.cs:188 — Bc7Decoder.UnpackBc7Mode1_3_7 has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriReader.ConvertImageYUVtoRGB (cognitive 35) · ×1
  • EriReader.ConvertImageYUVtoRGB (cognitive 35) ArcFormats/Entis/EriReader.cs:1834 — EriReader.ConvertImageYUVtoRGB has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TlgFormat.ReadV6 (cognitive 35) · ×1
  • TlgFormat.ReadV6 (cognitive 35) ArcFormats/KiriKiri/ImageTLG.cs:259 — TlgFormat.ReadV6 has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WbmReader.UnpackVD (cognitive 35) · ×1
  • WbmReader.UnpackVD (cognitive 35) ArcFormats/WildBug/ImageWBM.cs:317 — WbmReader.UnpackVD has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Mai3Reader.UnpackLine (cognitive 35) · ×1
  • Mai3Reader.UnpackLine (cognitive 35) Legacy/Izumi/ImageMAI3.cs:125 — Mai3Reader.UnpackLine has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PmsReader.Unpack16bpp (cognitive 34) · ×1
  • PmsReader.Unpack16bpp (cognitive 34) ArcFormats/AliceSoft/ImagePMS.cs:152 — PmsReader.Unpack16bpp has cognitive 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.
D2 · Cognitive Complexity · CpLzssDecompressor.Unpack (cognitive 34) · ×1
  • CpLzssDecompressor.Unpack (cognitive 34) ArcFormats/BellDa/ImageCP.cs:83 — CpLzssDecompressor.Unpack has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GphReader.Unpack (cognitive 34) · ×1
  • GphReader.Unpack (cognitive 34) ArcFormats/elf/ImageGPH.cs:120 — GphReader.Unpack has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GalReader.ReadBlocks (cognitive 34) · ×1
  • GalReader.ReadBlocks (cognitive 34) ArcFormats/LiveMaker/ImageGAL.cs:318 — GalReader.ReadBlocks has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VafsOpener.TryOpen (cognitive 34) · ×1
  • VafsOpener.TryOpen (cognitive 34) ArcFormats/Softpal/ArcVAFS.cs:51 — VafsOpener.TryOpen has cognitive complexity 34 (threshold 15). Of this number, 26 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WbmReader.Unpack (cognitive 34) · ×1
  • WbmReader.Unpack (cognitive 34) ArcFormats/WildBug/ImageWBM.cs:265 — WbmReader.Unpack has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Fa2Compression.Unpack (cognitive 33) · ×1
  • Fa2Compression.Unpack (cognitive 33) ArcFormats/Foster/ArcFA2.cs:109 — Fa2Compression.Unpack has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.Unpack16bpp (cognitive 33) · ×1
  • Reader.Unpack16bpp (cognitive 33) ArcFormats/Liar/ImageLIM.cs:154 — Reader.Unpack16bpp has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackChannel (cognitive 33) · ×1
  • Reader.UnpackChannel (cognitive 33) ArcFormats/Liar/ImageLIM.cs:242 — Reader.UnpackChannel has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GhpReader.Unpack3 (cognitive 33) · ×1
  • GhpReader.Unpack3 (cognitive 33) ArcFormats/Succubus/ImageGH.cs:199 — GhpReader.Unpack3 has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MblOpener.ReadIndex (cognitive 33) · ×1
  • MblOpener.ReadIndex (cognitive 33) ArcFormats/Marble/ArcMBL.cs:91 — MblOpener.ReadIndex has cognitive complexity 33 (threshold 15). Of this number, 27 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GswinGrpFormat.Decode (cognitive 33) · ×1
  • GswinGrpFormat.Decode (cognitive 33) ArcFormats/GsPack/ImageGS.cs:173 — GswinGrpFormat.Decode has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WbmReader.UnpackV4 (cognitive 33) · ×1
  • WbmReader.UnpackV4 (cognitive 33) ArcFormats/WildBug/ImageWBM.cs:640 — WbmReader.UnpackV4 has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GCmpDecoder.Unpack24bpp (cognitive 33) · ×1
  • GCmpDecoder.Unpack24bpp (cognitive 33) Legacy/Nekotaro/ImageGCmp.cs:123 — GCmpDecoder.Unpack24bpp has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GrpOpener.UnpackTpw (cognitive 32) · ×1
  • GrpOpener.UnpackTpw (cognitive 32) ArcFormats/Ankh/ArcGRP.cs:260 — GrpOpener.UnpackTpw has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · XmgFormat.Read (cognitive 32) · ×1
  • XmgFormat.Read (cognitive 32) ArcFormats/Zyx/ImageXMG.cs:60 — XmgFormat.Read has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Lz4Compressor.DecompressBlock (cognitive 32) · ×1
  • Lz4Compressor.DecompressBlock (cognitive 32) ArcFormats/Lz4Stream.cs:222 — Lz4Compressor.DecompressBlock has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CRioArchive.DeserializeNode (cognitive 32) · ×1
  • CRioArchive.DeserializeNode (cognitive 32) ArcFormats/rUGP/ArcRIO.cs:467 — CRioArchive.DeserializeNode has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Channel.Decode1 (cognitive 32) · ×1
  • Channel.Decode1 (cognitive 32) ArcFormats/Cri/AudioHCA.cs:682 — Channel.Decode1 has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InfoReader.ParseInfo (cognitive 32) · ×1
  • InfoReader.ParseInfo (cognitive 32) ArcFormats/Glib2/ImagePGX.cs:176 — InfoReader.ParseInfo has cognitive complexity 32 (threshold 15). Of this number, 31 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacOpener.TryOpen (cognitive 32) · ×1
  • TacOpener.TryOpen (cognitive 32) ArcFormats/TanukiSoft/ArcTAC.cs:54 — TacOpener.TryOpen has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RmskReader.UnpackV1 (cognitive 32) · ×1
  • RmskReader.UnpackV1 (cognitive 32) ArcFormats/Silky/ImageMSK.cs:182 — RmskReader.UnpackV1 has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HuffmanTree.HalfAndRebuild (cognitive 32) · ×1
  • HuffmanTree.HalfAndRebuild (cognitive 32) ArcFormats/Entis/EriReader.cs:2142 — HuffmanTree.HalfAndRebuild has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SeraphReader.UnpackBytes (cognitive 32) · ×1
  • SeraphReader.UnpackBytes (cognitive 32) ArcFormats/Seraphim/ImageSeraph.cs:368 — SeraphReader.UnpackBytes has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WbmReader.UnpackVB (cognitive 32) · ×1
  • WbmReader.UnpackVB (cognitive 32) ArcFormats/WildBug/ImageWBM.cs:400 — WbmReader.UnpackVB has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RleDecompressor.Unpack (cognitive 32) · ×1
  • RleDecompressor.Unpack (cognitive 32) Legacy/Aaru/ArcFL4.cs:145 — RleDecompressor.Unpack has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pdt5Reader.Unpack (cognitive 32) · ×1
  • Pdt5Reader.Unpack (cognitive 32) Legacy/AyPio/ImagePDT5.cs:96 — Pdt5Reader.Unpack has cognitive complexity 32 (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.
D2 · Cognitive Complexity · EncryptedGraphDecoder.GetImageData (cognitive 32) · ×1
  • EncryptedGraphDecoder.GetImageData (cognitive 32) Legacy/Pias/EncryptedGraphDat.cs:289 — EncryptedGraphDecoder.GetImageData has cognitive complexity 32 (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.
D2 · Cognitive Complexity · MpkCompression.sub_42A2E0 (cognitive 32) · ×1
  • MpkCompression.sub_42A2E0 (cognitive 32) Legacy/Kurumi/ArcMPK.cs:333 — MpkCompression.sub_42A2E0 has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RleDecompressor.Unpack (cognitive 31) · ×1
  • RleDecompressor.Unpack (cognitive 31) ArcFormats/Ads/ArcPAC.cs:186 — RleDecompressor.Unpack has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PakOpener.TryOpen (cognitive 31) · ×1
  • PakOpener.TryOpen (cognitive 31) ArcFormats/Ivory/ArcPK.cs:52 — PakOpener.TryOpen has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BinOpener.TryOpen (cognitive 31) · ×1
  • BinOpener.TryOpen (cognitive 31) ArcFormats/Patisserie/ArcBIN.cs:49 — BinOpener.TryOpen has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PcsOpener.TryOpen (cognitive 31) · ×1
  • PcsOpener.TryOpen (cognitive 31) ArcFormats/CsWare/ArcPCS.cs:62 — PcsOpener.TryOpen has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcGOpener.TryOpen (cognitive 31) · ×1
  • ArcGOpener.TryOpen (cognitive 31) ArcFormats/Tanaka/ArcARCG.cs:51 — ArcGOpener.TryOpen has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WwaReader.UnpackV2 (cognitive 31) · ×1
  • WwaReader.UnpackV2 (cognitive 31) ArcFormats/WildBug/AudioWWA.cs:123 — WwaReader.UnpackV2 has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackIndexed (cognitive 31) · ×1
  • Reader.UnpackIndexed (cognitive 31) ArcFormats/Lucifen/ImageELG.cs:176 — Reader.UnpackIndexed has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriFormat.ReadMetaData (cognitive 31) · ×1
  • EriFormat.ReadMetaData (cognitive 31) ArcFormats/Entis/ImageERI.cs:159 — EriFormat.ReadMetaData has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · K4Reader.Unpack (cognitive 31) · ×1
  • K4Reader.Unpack (cognitive 31) Legacy/Gsx/ImageK4.cs:94 — K4Reader.Unpack has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BpaDecoder.Decompress (cognitive 31) · ×1
  • BpaDecoder.Decompress (cognitive 31) Legacy/Liddell/ImageBPA.cs:133 — BpaDecoder.Decompress has cognitive complexity 31 (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.
D2 · Cognitive Complexity · GamDecompressor.Unpack (cognitive 31) · ×1
  • GamDecompressor.Unpack (cognitive 31) Legacy/ProjectMyu/ImageGAM.cs:77 — GamDecompressor.Unpack has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConsoleBrowser.Run (cognitive 30) · ×1
  • ConsoleBrowser.Run (cognitive 30) Console/ConsoleBrowser.cs:76 — ConsoleBrowser.Run has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IndexReaderV8.ReadFileTable (cognitive 30) · ×1
  • IndexReaderV8.ReadFileTable (cognitive 30) ArcFormats/DxLib/ArcDX8.cs:289 — IndexReaderV8.ReadFileTable has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AniOpener.TryOpen (cognitive 30) · ×1
  • AniOpener.TryOpen (cognitive 30) ArcFormats/AnimeGameSystem/ArcANI.cs:50 — AniOpener.TryOpen has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GrpOpener.DetectFileTypes (cognitive 30) · ×1
  • GrpOpener.DetectFileTypes (cognitive 30) ArcFormats/Ankh/ArcGRP.cs:86 — GrpOpener.DetectFileTypes has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GrpUnpacker.UnpackSv2 (cognitive 30) · ×1
  • GrpUnpacker.UnpackSv2 (cognitive 30) ArcFormats/Ankh/ArcGRP.cs:496 — GrpUnpacker.UnpackSv2 has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CandyDecoder.LzUnpack (cognitive 30) · ×1
  • CandyDecoder.LzUnpack (cognitive 30) ArcFormats/Interheart/ImageCandy.cs:205 — CandyDecoder.LzUnpack has cognitive complexity 30 (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.
D2 · Cognitive Complexity · Decoder.DoEncryption (cognitive 30) · ×1
  • Decoder.DoEncryption (cognitive 30) ArcFormats/ShiinaRio/WarcEncryption.cs:140 — Decoder.DoEncryption has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PandoraCompression.Unpack (cognitive 30) · ×1
  • PandoraCompression.Unpack (cognitive 30) ArcFormats/Pandora/ArcPBX.cs:103 — PandoraCompression.Unpack has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShsCompression.Unpack (cognitive 30) · ×1
  • ShsCompression.Unpack (cognitive 30) ArcFormats/SHSystem/ArcHXP.cs:203 — ShsCompression.Unpack has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Reader.Unpack (cognitive 30) · ×1
  • Reader.Unpack (cognitive 30) ArcFormats/uGOS/ImageBMP.cs:133 — Reader.Unpack has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Bc7Decoder.UnpackBc7Mode0_2 (cognitive 30) · ×1
  • Bc7Decoder.UnpackBc7Mode0_2 (cognitive 30) ArcFormats/Unity/Bc7Decoder.cs:138 — Bc7Decoder.UnpackBc7Mode0_2 has cognitive complexity 30 (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.
D2 · Cognitive Complexity · Bc7Decoder.UnpackBc7Mode4_5 (cognitive 30) · ×1
  • Bc7Decoder.UnpackBc7Mode4_5 (cognitive 30) ArcFormats/Unity/Bc7Decoder.cs:239 — Bc7Decoder.UnpackBc7Mode4_5 has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VorbisInfo.UnpackMapping (cognitive 30) · ×1
  • VorbisInfo.UnpackMapping (cognitive 30) ArcFormats/Unity/Vorbis.cs:585 — VorbisInfo.UnpackMapping has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcOpener.Create (cognitive 30) · ×1
  • ArcOpener.Create (cognitive 30) ArcFormats/Will/ArcWILL.cs:168 — ArcOpener.Create has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PadDecoder.Unpack (cognitive 30) · ×1
  • PadDecoder.Unpack (cognitive 30) ArcFormats/ShiinaRio/AudioPAD.cs:88 — PadDecoder.Unpack has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WbmReader.UnpackV2 (cognitive 30) · ×1
  • WbmReader.UnpackV2 (cognitive 30) ArcFormats/WildBug/ImageWBM.cs:819 — WbmReader.UnpackV2 has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShiftReduceParser.Parse (cognitive 30) · ×1
  • ShiftReduceParser.Parse (cognitive 30) Experimental/Artemis/ShiftReduceParserCode.cs:203 — ShiftReduceParser.Parse has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · T32Format.Read (cognitive 30) · ×1
  • T32Format.Read (cognitive 30) Legacy/Broccoli/ImageT32.cs:99 — T32Format.Read has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HuffmanTree.HuffmanTree.ctor (cognitive 29) · ×1
  • HuffmanTree.HuffmanTree.ctor (cognitive 29) ArcFormats/Ethornell/ImageCBG.cs:329 — HuffmanTree.HuffmanTree.ctor has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ParallelCbgDecoder.UnpackBlock (cognitive 29) · ×1
  • ParallelCbgDecoder.UnpackBlock (cognitive 29) ArcFormats/Ethornell/ImageCBG.cs:447 — ParallelCbgDecoder.UnpackBlock has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DodakureCrypt.Decrypt (cognitive 29) · ×1
  • DodakureCrypt.Decrypt (cognitive 29) ArcFormats/ShiinaRio/WarcEncryption.cs:908 — DodakureCrypt.Decrypt has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CpzOpener.ReadIndex (cognitive 29) · ×1
  • CpzOpener.ReadIndex (cognitive 29) ArcFormats/Cmvs/ArcCPZ.cs:149 — CpzOpener.ReadIndex has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AkbReader.Unpack (cognitive 29) · ×1
  • AkbReader.Unpack (cognitive 29) ArcFormats/Silky/ImageAKB.cs:144 — AkbReader.Unpack has cognitive complexity 29 (threshold 15). Of this number, 19 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbmReader.UnpackStream32 (cognitive 29) · ×1
  • AbmReader.UnpackStream32 (cognitive 29) ArcFormats/Lilim/ArcABM.cs:283 — AbmReader.UnpackStream32 has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IndexReader.ParseDirEntry (cognitive 29) · ×1
  • IndexReader.ParseDirEntry (cognitive 29) REDACTED:331 — IndexReader.ParseDirEntry has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TcdOpener.OpenSpdc (cognitive 29) · ×1
  • TcdOpener.OpenSpdc (cognitive 29) ArcFormats/TopCat/ArcTCD3.cs:127 — TcdOpener.OpenSpdc has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Reader.ReadLine (cognitive 29) · ×1
  • Reader.ReadLine (cognitive 29) ArcFormats/ShiinaRio/ImageS25.cs:303 — Reader.ReadLine has cognitive complexity 29 (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.
D2 · Cognitive Complexity · WbmReader.UnpackV1 (cognitive 29) · ×1
  • WbmReader.UnpackV1 (cognitive 29) ArcFormats/WildBug/ImageWBM.cs:885 — WbmReader.UnpackV1 has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TexFormat.Read (cognitive 28) · ×1
  • TexFormat.Read (cognitive 28) ArcFormats/Artdink/ImageTEX.cs:107 — TexFormat.Read has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GimFormat.ReadMetaData (cognitive 28) · ×1
  • GimFormat.ReadMetaData (cognitive 28) ArcFormats/Psp/ArcGim.cs:30 — GimFormat.ReadMetaData has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EvbPackOpener.TryOpen (cognitive 28) · ×1
  • EvbPackOpener.TryOpen (cognitive 28) ArcFormats/Enigma/ArcEVB.cs:54 — EvbPackOpener.TryOpen has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · C25Decoder.Unpack (cognitive 28) · ×1
  • C25Decoder.Unpack (cognitive 28) ArcFormats/Foster/ImageC25.cs:71 — C25Decoder.Unpack has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.TryOpen (cognitive 28) · ×1
  • DatOpener.TryOpen (cognitive 28) ArcFormats/Seraphim/ArcArchAngel.cs:52 — DatOpener.TryOpen has cognitive complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GbpReader.UnpackFlat (cognitive 28) · ×1
  • GbpReader.UnpackFlat (cognitive 28) ArcFormats/Sviu/ImageGBP.cs:144 — GbpReader.UnpackFlat has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WbpOpener.OpenV4 (cognitive 28) · ×1
  • WbpOpener.OpenV4 (cognitive 28) ArcFormats/WildBug/ArcWBP.cs:87 — WbpOpener.OpenV4 has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GReader.GetColorFromTable (cognitive 28) · ×1
  • GReader.GetColorFromTable (cognitive 28) Legacy/HyperWorks/ImageG.cs:205 — GReader.GetColorFromTable has cognitive complexity 28 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · FdReader.UnpackAlpha (cognitive 28) · ×1
  • FdReader.UnpackAlpha (cognitive 28) Legacy/Mink/ImageFD.cs:159 — FdReader.UnpackAlpha has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HuffmanDecoder.DoUnpack (cognitive 27) · ×1
  • HuffmanDecoder.DoUnpack (cognitive 27) ArcFormats/DxLib/HuffmanDecoder.cs:120 — HuffmanDecoder.DoUnpack has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TimFormat.Read (cognitive 27) · ×1
  • TimFormat.Read (cognitive 27) ArcFormats/Ps1/ImageTIM.cs:98 — TimFormat.Read has cognitive complexity 27 (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.
D2 · Cognitive Complexity · GanFrameArchive.UnpackRefFrame (cognitive 27) · ×1
  • GanFrameArchive.UnpackRefFrame (cognitive 27) ArcFormats/Ikura/ArcGAN.cs:162 — GanFrameArchive.UnpackRefFrame has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GgsReader.Unpack (cognitive 27) · ×1
  • GgsReader.Unpack (cognitive 27) ArcFormats/Ikura/ImageGGS.cs:78 — GgsReader.Unpack has cognitive complexity 27 (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.
D2 · Cognitive Complexity · LzssPackedStream.Unpack (cognitive 27) · ×1
  • LzssPackedStream.Unpack (cognitive 27) ArcFormats/Primel/Compression.cs:105 — LzssPackedStream.Unpack has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Img2Reader.Unpack32bpp (cognitive 27) · ×1
  • Img2Reader.Unpack32bpp (cognitive 27) ArcFormats/ScrPlayer/ImageI.cs:189 — Img2Reader.Unpack32bpp has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcOpener.TryOpen (cognitive 27) · ×1
  • ArcOpener.TryOpen (cognitive 27) ArcFormats/ArcAST.cs:58 — ArcOpener.TryOpen has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OggStreamState.Flush (cognitive 27) · ×1
  • OggStreamState.Flush (cognitive 27) ArcFormats/Unity/OggStream.cs:286 — OggStreamState.Flush has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SbiReader.Unpack (cognitive 27) · ×1
  • SbiReader.Unpack (cognitive 27) ArcFormats/Vitamin/ImageSBI.cs:123 — SbiReader.Unpack has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WwaReader.UnpackVB (cognitive 27) · ×1
  • WwaReader.UnpackVB (cognitive 27) ArcFormats/WildBug/AudioWWA.cs:190 — WwaReader.UnpackVB has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackLine16 (cognitive 27) · ×1
  • Reader.UnpackLine16 (cognitive 27) ArcFormats/Dac/ImageDGC.cs:264 — Reader.UnpackLine16 has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.Unpack (cognitive 27) · ×1
  • Reader.Unpack (cognitive 27) ArcFormats/Pajamas/ImageEPA.cs:126 — Reader.Unpack has cognitive complexity 27 (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.
D2 · Cognitive Complexity · SeraphReader.UnpackRgb (cognitive 27) · ×1
  • SeraphReader.UnpackRgb (cognitive 27) ArcFormats/Seraphim/ImageSeraph.cs:287 — SeraphReader.UnpackRgb has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LzssReader.Unpack (cognitive 27) · ×1
  • LzssReader.Unpack (cognitive 27) ArcFormats/LzssStream.cs:147 — LzssReader.Unpack has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NpReader.sub_416DC0 (cognitive 27) · ×1
  • NpReader.sub_416DC0 (cognitive 27) Legacy/Paprika/ImageNP.cs:351 — NpReader.sub_416DC0 has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AgiFormat.ReadMetaData (cognitive 26) · ×1
  • AgiFormat.ReadMetaData (cognitive 26) ArcFormats/Artdink/ImageAGI.cs:55 — AgiFormat.ReadMetaData has cognitive complexity 26 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · QLZCompressor.Decompress_Unsafe (cognitive 26) · ×1
  • QLZCompressor.Decompress_Unsafe (cognitive 26) ArcFormats/Entergram/QuickLZ.cs:54 — QLZCompressor.Decompress_Unsafe has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Tim2Reader.Unpack (cognitive 26) · ×1
  • Tim2Reader.Unpack (cognitive 26) ArcFormats/DigitalWorks/ImageTM2.cs:130 — Tim2Reader.Unpack has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LzBitStream.Unpack (cognitive 26) · ×1
  • LzBitStream.Unpack (cognitive 26) REDACTED:339 — LzBitStream.Unpack has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SgRgbReader.UnpackV1 (cognitive 26) · ×1
  • SgRgbReader.UnpackV1 (cognitive 26) ArcFormats/Ivory/ImageSG.cs:178 — SgRgbReader.UnpackV1 has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PxFormat.ReadMetaData (cognitive 26) · ×1
  • PxFormat.ReadMetaData (cognitive 26) ArcFormats/Leaf/ImagePX.cs:53 — PxFormat.ReadMetaData has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.LzssUnpack (cognitive 26) · ×1
  • DatOpener.LzssUnpack (cognitive 26) ArcFormats/Ail/ArcAil.cs:162 — DatOpener.LzssUnpack has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PakOpener.TryOpen (cognitive 26) · ×1
  • PakOpener.TryOpen (cognitive 26) ArcFormats/GsPack/ArcGsPack.cs:59 — PakOpener.TryOpen has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResourcesAssetsDeserializer.Parse (cognitive 26) · ×1
  • ResourcesAssetsDeserializer.Parse (cognitive 26) ArcFormats/Unity/ResourcesAssets.cs:41 — ResourcesAssetsDeserializer.Parse has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SplReader.Unpack (cognitive 26) · ×1
  • SplReader.Unpack (cognitive 26) ArcFormats/Zyx/ImageSPL.cs:125 — SplReader.Unpack has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackRGB (cognitive 26) · ×1
  • Reader.UnpackRGB (cognitive 26) ArcFormats/AnimeGameSystem/ImageAinos.cs:179 — Reader.UnpackRGB has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackLine (cognitive 26) · ×1
  • Reader.UnpackLine (cognitive 26) ArcFormats/ShiinaRio/ImageS25.cs:222 — Reader.UnpackLine has cognitive complexity 26 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · TlgFormat.TVPTLG6DecodeGolombValuesForFirst (cognitive 26) · ×1
  • TlgFormat.TVPTLG6DecodeGolombValuesForFirst (cognitive 26) ArcFormats/KiriKiri/ImageTLG.cs:872 — TlgFormat.TVPTLG6DecodeGolombValuesForFirst has cognitive complexity 26 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (TlgFormat.TVPTLG6DecodeGolombValues) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · TlgFormat.TVPTLG6DecodeGolombValues (cognitive 26) · ×1
  • TlgFormat.TVPTLG6DecodeGolombValues (cognitive 26) ArcFormats/KiriKiri/ImageTLG.cs:990 — TlgFormat.TVPTLG6DecodeGolombValues has cognitive complexity 26 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (TlgFormat.TVPTLG6DecodeGolombValuesForFirst) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DesTransform.SetKey (cognitive 26) · ×1
  • DesTransform.SetKey (cognitive 26) REDACTED:154 — DesTransform.SetKey has cognitive complexity 26 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · TagFormat.ParseImages (cognitive 25) · ×1
  • TagFormat.ParseImages (cognitive 25) ArcFormats/Artdink/ImageTAG.cs:145 — TagFormat.ParseImages has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DATRAWOpener.UnpackLnd (cognitive 25) · ×1
  • DATRAWOpener.UnpackLnd (cognitive 25) ArcFormats/Kid/ArcDATRAW.cs:91 — DATRAWOpener.UnpackLnd has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ZtOpener.TryOpen (cognitive 25) · ×1
  • ZtOpener.TryOpen (cognitive 25) ArcFormats/CatSystem/ArcZT.cs:53 — ZtOpener.TryOpen has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LnkOpener.UnpackLnd (cognitive 25) · ×1
  • LnkOpener.UnpackLnd (cognitive 25) ArcFormats/Kid/ArcDAT.cs:100 — LnkOpener.UnpackLnd has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LzBitsDecompressor.Unpack (cognitive 25) · ×1
  • LzBitsDecompressor.Unpack (cognitive 25) ArcFormats/Maika/ArcBK.cs:100 — LzBitsDecompressor.Unpack has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ImgXDecoder.Unpack (cognitive 25) · ×1
  • ImgXDecoder.Unpack (cognitive 25) ArcFormats/Nonono/ImageIMGX.cs:93 — ImgXDecoder.Unpack has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OrgImageDecoder.UnpackHuffman (cognitive 25) · ×1
  • OrgImageDecoder.UnpackHuffman (cognitive 25) ArcFormats/Origin/ArcDAT.cs:358 — OrgImageDecoder.UnpackHuffman has cognitive complexity 25 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Xl24Format.Read (cognitive 25) · ×1
  • Xl24Format.Read (cognitive 25) ArcFormats/Pandora/ImageXL24.cs:58 — Xl24Format.Read has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CRioArchive.DecodeClassName (cognitive 25) · ×1
  • CRioArchive.DecodeClassName (cognitive 25) ArcFormats/rUGP/ArcRIO.cs:906 — CRioArchive.DecodeClassName has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CBoxOcean.Deserialize (cognitive 25) · ×1
  • CBoxOcean.Deserialize (cognitive 25) ArcFormats/rUGP/ArcRIO.cs:1390 — CBoxOcean.Deserialize has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AImageReader.ReadBaseline (cognitive 25) · ×1
  • AImageReader.ReadBaseline (cognitive 25) ArcFormats/Cyberworks/ImageTINK.cs:110 — AImageReader.ReadBaseline has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JokersCrypt.Decrypt (cognitive 25) · ×1
  • JokersCrypt.Decrypt (cognitive 25) ArcFormats/ShiinaRio/WarcEncryption.cs:967 — JokersCrypt.Decrypt has cognitive complexity 25 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Bin2Opener.TryOpen (cognitive 25) · ×1
  • Bin2Opener.TryOpen (cognitive 25) ArcFormats/Favorite/ArcBIN.cs:47 — Bin2Opener.TryOpen has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PicReader.Unpack24bpp (cognitive 25) · ×1
  • PicReader.Unpack24bpp (cognitive 25) ArcFormats/Softpal/ImagePIC.cs:157 — PicReader.Unpack24bpp has cognitive complexity 25 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · LzwDecoder.Unpack (cognitive 25) · ×1
  • LzwDecoder.Unpack (cognitive 25) ArcFormats/Favorite/ArcFVP.cs:102 — LzwDecoder.Unpack has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcOpener.TryOpen (cognitive 25) · ×1
  • ArcOpener.TryOpen (cognitive 25) ArcFormats/MAI/ArcMAI.cs:55 — ArcOpener.TryOpen has cognitive complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.TryOpen (cognitive 25) · ×1
  • DatOpener.TryOpen (cognitive 25) ArcFormats/MnoViolet/ArcMnoViolet.cs:51 — DatOpener.TryOpen has cognitive complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UnityTypeData.Load (cognitive 25) · ×1
  • UnityTypeData.Load (cognitive 25) ArcFormats/Unity/Asset.cs:433 — UnityTypeData.Load has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Wa1Reader.UnpackV8 (cognitive 25) · ×1
  • Wa1Reader.UnpackV8 (cognitive 25) ArcFormats/Ffa/AudioWA1.cs:337 — Wa1Reader.UnpackV8 has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DrgFormat.DecodeStream (cognitive 25) · ×1
  • DrgFormat.DecodeStream (cognitive 25) ArcFormats/Ikura/ImageDRG.cs:120 — DrgFormat.DecodeStream has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackV1 (cognitive 25) · ×1
  • Reader.UnpackV1 (cognitive 25) ArcFormats/ShiinaRio/ImageMI4.cs:150 — Reader.UnpackV1 has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TlgFormat.ReadMUX (cognitive 25) · ×1
  • TlgFormat.ReadMUX (cognitive 25) ArcFormats/KiriKiri/ImageTLG.cs:1403 — TlgFormat.ReadMUX has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WpxDecoder.FillRefTable (cognitive 25) · ×1
  • WpxDecoder.FillRefTable (cognitive 25) ArcFormats/WildBug/ImageWBM.cs:1059 — WpxDecoder.FillRefTable has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.Unpack (cognitive 25) · ×1
  • DatOpener.Unpack (cognitive 25) Legacy/BlackButterfly/ArcDAT.cs:85 — DatOpener.Unpack has cognitive complexity 25 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · RqfBitmapDecoder.UnpackRle (cognitive 25) · ×1
  • RqfBitmapDecoder.UnpackRle (cognitive 25) Legacy/Peach/ArcPAK.cs:162 — RqfBitmapDecoder.UnpackRle has cognitive complexity 25 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · BprDecompressor.Unpack (cognitive 25) · ×1
  • BprDecompressor.Unpack (cognitive 25) Legacy/Eve/ArcGM.cs:135 — BprDecompressor.Unpack has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MrgOpener.ReadInfo (cognitive 24) · ×1
  • MrgOpener.ReadInfo (cognitive 24) ArcFormats/HuneX/ArcMZP.cs:110 — MrgOpener.ReadInfo has cognitive complexity 24 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · DcfReader.MaskOverlay (cognitive 24) · ×1
  • DcfReader.MaskOverlay (cognitive 24) ArcFormats/AliceSoft/ImageDCF.cs:217 — DcfReader.MaskOverlay has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LeafLzs.Decompress (cognitive 24) · ×1
  • LeafLzs.Decompress (cognitive 24) ArcFormats/Leaf/ImageLFB.cs:369 — LeafLzs.Decompress has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GrpOpener.TryOpen (cognitive 24) · ×1
  • GrpOpener.TryOpen (cognitive 24) ArcFormats/ExHibit/ArcGRP.cs:45 — GrpOpener.TryOpen has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AdpDecoder.DecodeBits (cognitive 24) · ×1
  • AdpDecoder.DecodeBits (cognitive 24) ArcFormats/GameSystem/AudioADP4.cs:134 — AdpDecoder.DecodeBits has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WagOpener.TryOpen (cognitive 24) · ×1
  • WagOpener.TryOpen (cognitive 24) ArcFormats/Hexenhaus/ArcWAG.cs:49 — WagOpener.TryOpen has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FpkOpener.UnpackFbx (cognitive 24) · ×1
  • FpkOpener.UnpackFbx (cognitive 24) ArcFormats/Moonhir/ArcFPK.cs:191 — FpkOpener.UnpackFbx has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NcIndexReaderBase.Read (cognitive 24) · ×1
  • NcIndexReaderBase.Read (cognitive 24) REDACTED:307 — NcIndexReaderBase.Read has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CRip.UncompressRgba (cognitive 24) · ×1
  • CRip.UncompressRgba (cognitive 24) ArcFormats/rUGP/ImageRIP.cs:267 — CRip.UncompressRgba has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Decoder.DecryptHelper2 (cognitive 24) · ×1
  • Decoder.DecryptHelper2 (cognitive 24) ArcFormats/ShiinaRio/WarcEncryption.cs:313 — Decoder.DecryptHelper2 has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HzcFormat.Read (cognitive 24) · ×1
  • HzcFormat.Read (cognitive 24) ArcFormats/Favorite/ImageHZC.cs:73 — HzcFormat.Read has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PakOpener.TryOpen (cognitive 24) · ×1
  • PakOpener.TryOpen (cognitive 24) ArcFormats/TamaSoft/ArcEPK.cs:72 — PakOpener.TryOpen has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Sep5Opener.TryOpen (cognitive 24) · ×1
  • Sep5Opener.TryOpen (cognitive 24) ArcFormats/Sas5/ArcSec5.cs:241 — Sep5Opener.TryOpen has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AmiOpener.Create (cognitive 24) · ×1
  • AmiOpener.Create (cognitive 24) ArcFormats/Amaterasu/ArcAMI.cs:153 — AmiOpener.Create has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AosOpener.TryOpen (cognitive 24) · ×1
  • AosOpener.TryOpen (cognitive 24) ArcFormats/Lilim/ArcAOS.cs:52 — AosOpener.TryOpen has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MrgLzssReader.Unpack (cognitive 24) · ×1
  • MrgLzssReader.Unpack (cognitive 24) ArcFormats/FC01/ArcMRG.cs:314 — MrgLzssReader.Unpack has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PacOpener.TryOpen (cognitive 24) · ×1
  • PacOpener.TryOpen (cognitive 24) ArcFormats/Tmr-Hiro/ArcPAC.cs:47 — PacOpener.TryOpen has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RLEDecodeContext.DecodeGammaCodeBytes (cognitive 24) · ×1
  • RLEDecodeContext.DecodeGammaCodeBytes (cognitive 24) ArcFormats/Entis/EriReader.cs:2251 — RLEDecodeContext.DecodeGammaCodeBytes has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MioInput.Read_Threaded (cognitive 24) · ×1
  • MioInput.Read_Threaded (cognitive 24) ArcFormats/Entis/AudioMIO.cs:293 — MioInput.Read_Threaded has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.sub_4225EA (cognitive 24) · ×1
  • Reader.sub_4225EA (cognitive 24) ArcFormats/Ffa/ImagePT1.cs:399 — Reader.sub_4225EA has cognitive complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · TlgFormat.ReadMetaData (cognitive 24) · ×1
  • TlgFormat.ReadMetaData (cognitive 24) ArcFormats/KiriKiri/ImageTLG.cs:46 — TlgFormat.ReadMetaData has cognitive complexity 24 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · GarExtract.ExtractWorker (cognitive 24) · ×1
  • GarExtract.ExtractWorker (cognitive 24) GUI/GarExtract.cs:275 — GarExtract.ExtractWorker has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TtpOpener.TryOpen (cognitive 24) · ×1
  • TtpOpener.TryOpen (cognitive 24) Legacy/NAUTS/ArcTTP.cs:63 — TtpOpener.TryOpen has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IndexReader.ReadDir (cognitive 23) · ×1
  • IndexReader.ReadDir (cognitive 23) ArcFormats/Ads/ArcPAC.cs:92 — IndexReader.ReadDir has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.ReadIndex (cognitive 23) · ×1
  • DatOpener.ReadIndex (cognitive 23) ArcFormats/JamCreation/ArcDAT.cs:86 — DatOpener.ReadIndex has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GimFormat.UnswizzlePSP (cognitive 23) · ×1
  • GimFormat.UnswizzlePSP (cognitive 23) ArcFormats/Psp/ArcGim.cs:253 — GimFormat.UnswizzlePSP has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriOpener.TryOpen (cognitive 23) · ×1
  • EriOpener.TryOpen (cognitive 23) ArcFormats/Entis/ArcERI.cs:53 — EriOpener.TryOpen has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PakOpener.TryOpen (cognitive 23) · ×1
  • PakOpener.TryOpen (cognitive 23) ArcFormats/Eagls/ArcEAGLS.cs:54 — PakOpener.TryOpen has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcOpener.TryOpen (cognitive 23) · ×1
  • ArcOpener.TryOpen (cognitive 23) ArcFormats/Xuse/ArcXuse.cs:49 — ArcOpener.TryOpen has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriReader.BlockScaling444 (cognitive 23) · ×1
  • EriReader.BlockScaling444 (cognitive 23) ArcFormats/Entis/EriReader.cs:1731 — EriReader.BlockScaling444 has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriReader.BlockScaling411 (cognitive 23) · ×1
  • EriReader.BlockScaling411 (cognitive 23) ArcFormats/Entis/EriReader.cs:1782 — EriReader.BlockScaling411 has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MioDecoder.Initialize (cognitive 23) · ×1
  • MioDecoder.Initialize (cognitive 23) ArcFormats/Entis/MioDecoder.cs:83 — MioDecoder.Initialize has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArchPacOpener.ReadIndex (cognitive 23) · ×1
  • ArchPacOpener.ReadIndex (cognitive 23) ArcFormats/Seraphim/ArcSeraph.cs:121 — ArchPacOpener.ReadIndex has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WarOpener.TryOpen (cognitive 23) · ×1
  • WarOpener.TryOpen (cognitive 23) ArcFormats/ShiinaRio/ArcWARC.cs:80 — WarOpener.TryOpen has cognitive complexity 23 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · YlzReader.Unpack (cognitive 23) · ×1
  • YlzReader.Unpack (cognitive 23) ArcFormats/ShiinaRio/ArcWARC.cs:356 — YlzReader.Unpack has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackWithDictLarge (cognitive 23) · ×1
  • Reader.UnpackWithDictLarge (cognitive 23) ArcFormats/Dac/ImageDGC.cs:127 — Reader.UnpackWithDictLarge has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CmpReader.Unpack (cognitive 23) · ×1
  • CmpReader.Unpack (cognitive 23) ArcFormats/RiddleSoft/ImageGCP.cs:123 — CmpReader.Unpack has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CocotteEncoder.Decode (cognitive 23) · ×1
  • CocotteEncoder.Decode (cognitive 23) ArcFormats/KogadoCocotte.cs:90 — CocotteEncoder.Decode has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FcReader.UnpackRgb (cognitive 23) · ×1
  • FcReader.UnpackRgb (cognitive 23) Legacy/Mink/ImageFC.cs:126 — FcReader.UnpackRgb has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MpkCompression.sub_429D50 (cognitive 23) · ×1
  • MpkCompression.sub_429D50 (cognitive 23) Legacy/Kurumi/ArcMPK.cs:217 — MpkCompression.sub_429D50 has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BipFormat.ReadMetaData (cognitive 22) · ×1
  • BipFormat.ReadMetaData (cognitive 22) ArcFormats/Kid/ImageBIP.cs:14 — BipFormat.ReadMetaData has cognitive complexity 22 (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.
D2 · Cognitive Complexity · LenZuDecoder.Unpack (cognitive 22) · ×1
  • LenZuDecoder.Unpack (cognitive 22) ArcFormats/HuneX/Decoder.cs:133 — LenZuDecoder.Unpack has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ImgReader.Unpack32bpp (cognitive 22) · ×1
  • ImgReader.Unpack32bpp (cognitive 22) ArcFormats/ScrPlayer/ImageIMG.cs:187 — ImgReader.Unpack32bpp has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PacOpener.DetectFileTypes (cognitive 22) · ×1
  • PacOpener.DetectFileTypes (cognitive 22) ArcFormats/DaiSystem/ArcPAC.cs:83 — PacOpener.DetectFileTypes has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DrefFormat.Read (cognitive 22) · ×1
  • DrefFormat.Read (cognitive 22) ArcFormats/Emote/ImageDREF.cs:89 — DrefFormat.Read has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BinOpener.TryOpen (cognitive 22) · ×1
  • BinOpener.TryOpen (cognitive 22) ArcFormats/Misc/ArcBIN.cs:42 — BinOpener.TryOpen has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · KoeOpener.OpenEntry (cognitive 22) · ×1
  • KoeOpener.OpenEntry (cognitive 22) ArcFormats/RealLive/ArcKOE.cs:101 — KoeOpener.OpenEntry has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Img2Reader.Unpack24bpp (cognitive 22) · ×1
  • Img2Reader.Unpack24bpp (cognitive 22) ArcFormats/ScrPlayer/ImageI.cs:136 — Img2Reader.Unpack24bpp has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VafsOpener.OpenVoice055Entry (cognitive 22) · ×1
  • VafsOpener.OpenVoice055Entry (cognitive 22) ArcFormats/Softpal/ArcVAFS.cs:296 — VafsOpener.OpenVoice055Entry has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TxReader.Decompress (cognitive 22) · ×1
  • TxReader.Decompress (cognitive 22) ArcFormats/Tanaka/ImageBC.cs:146 — TxReader.Decompress has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Wa2Input.Decode (cognitive 22) · ×1
  • Wa2Input.Decode (cognitive 22) ArcFormats/Ffa/AudioWA2.cs:78 — Wa2Input.Decode has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NsaOpener.Create (cognitive 22) · ×1
  • NsaOpener.Create (cognitive 22) ArcFormats/NScripter/ArcNSA.cs:240 — NsaOpener.Create has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PdOpener.Create (cognitive 22) · ×1
  • PdOpener.Create (cognitive 22) ArcFormats/FlyingShine/ArcPD.cs:104 — PdOpener.Create has cognitive complexity 22 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SpdReader.UnpackLz (cognitive 22) · ×1
  • SpdReader.UnpackLz (cognitive 22) ArcFormats/TopCat/ImageSPD.cs:196 — SpdReader.UnpackLz has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VorbisInfo.UnpackFloor1 (cognitive 22) · ×1
  • VorbisInfo.UnpackFloor1 (cognitive 22) ArcFormats/Unity/Vorbis.cs:454 — VorbisInfo.UnpackFloor1 has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriReader.ArrangeAndIQuantumize (cognitive 22) · ×1
  • EriReader.ArrangeAndIQuantumize (cognitive 22) ArcFormats/Entis/EriReader.cs:1582 — EriReader.ArrangeAndIQuantumize has cognitive complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · EriReader.MatrixILOT8x8 (cognitive 22) · ×1
  • EriReader.MatrixILOT8x8 (cognitive 22) ArcFormats/Entis/EriReader.cs:1671 — EriReader.MatrixILOT8x8 has cognitive complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · HuffmanTree.Normalize (cognitive 22) · ×1
  • HuffmanTree.Normalize (cognitive 22) ArcFormats/Entis/EriReader.cs:2023 — HuffmanTree.Normalize has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HuffmanDecodeContext.DecodeErinaCodeBytes (cognitive 22) · ×1
  • HuffmanDecodeContext.DecodeErinaCodeBytes (cognitive 22) ArcFormats/Entis/EriReader.cs:2466 — HuffmanDecodeContext.DecodeErinaCodeBytes has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MtlReader.Unpack (cognitive 22) · ×1
  • MtlReader.Unpack (cognitive 22) ArcFormats/Zyx/ImageMTL.cs:99 — MtlReader.Unpack has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SplFormat.ReadMetaData (cognitive 22) · ×1
  • SplFormat.ReadMetaData (cognitive 22) ArcFormats/Zyx/ImageSPL.cs:52 — SplFormat.ReadMetaData has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DziFormat.ReadMetaData (cognitive 22) · ×1
  • DziFormat.ReadMetaData (cognitive 22) ArcFormats/Malie/ImageDZI.cs:59 — DziFormat.ReadMetaData has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriFormat.ReadImageData (cognitive 22) · ×1
  • EriFormat.ReadImageData (cognitive 22) ArcFormats/Entis/ImageERI.cs:264 — EriFormat.ReadImageData has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MainWindow.ExtractItemExec (cognitive 22) · ×1
  • MainWindow.ExtractItemExec (cognitive 22) GUI/GarExtract.cs:47 — MainWindow.ExtractItemExec has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExeOpener.OpenVersion (cognitive 22) · ×1
  • ExeOpener.OpenVersion (cognitive 22) Experimental/Microsoft/ArcEXE.cs:161 — ExeOpener.OpenVersion has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HhpReader.Unpack (cognitive 22) · ×1
  • HhpReader.Unpack (cognitive 22) Legacy/MayBeSoft/ImageHHP.cs:82 — HhpReader.Unpack has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DrefFormat.BlendLayer (cognitive 21) · ×1
  • DrefFormat.BlendLayer (cognitive 21) ArcFormats/Emote/ImageDREF.cs:152 — DrefFormat.BlendLayer has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GOpener.LzssUnpack (cognitive 21) · ×1
  • GOpener.LzssUnpack (cognitive 21) ArcFormats/GLib/ArcG.cs:112 — GOpener.LzssUnpack has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SkaOpener.LzssUnpack (cognitive 21) · ×1
  • SkaOpener.LzssUnpack (cognitive 21) ArcFormats/Sohfu/ArcSKA.cs:95 — SkaOpener.LzssUnpack has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BprDecompressor.Unpack (cognitive 21) · ×1
  • BprDecompressor.Unpack (cognitive 21) ArcFormats/Maika/ArcMK2.cs:209 — BprDecompressor.Unpack has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RlePackedStream.Unpack (cognitive 21) · ×1
  • RlePackedStream.Unpack (cognitive 21) ArcFormats/Primel/Compression.cs:167 — RlePackedStream.Unpack has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CpzOpener.FindArchiveKey (cognitive 21) · ×1
  • CpzOpener.FindArchiveKey (cognitive 21) ArcFormats/Cmvs/ArcCPZ.cs:526 — CpzOpener.FindArchiveKey has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GhpReader.Unpack2 (cognitive 21) · ×1
  • GhpReader.Unpack2 (cognitive 21) ArcFormats/Succubus/ImageGH.cs:138 — GhpReader.Unpack2 has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AmapFormat.LzssUnpack (cognitive 21) · ×1
  • AmapFormat.LzssUnpack (cognitive 21) ArcFormats/TanukiSoft/ImageAF.cs:67 — AmapFormat.LzssUnpack has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BsgReader.Unpack (cognitive 21) · ×1
  • BsgReader.Unpack (cognitive 21) ArcFormats/Bishop/ImageBSG.cs:134 — BsgReader.Unpack has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PacOpener.TryOpen (cognitive 21) · ×1
  • PacOpener.TryOpen (cognitive 21) ArcFormats/Emic/ArcPACK.cs:58 — PacOpener.TryOpen has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Zlc2Reader.Unpack (cognitive 21) · ×1
  • Zlc2Reader.Unpack (cognitive 21) ArcFormats/Interheart/ArcFPK.cs:170 — Zlc2Reader.Unpack has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcOpener.TryOpen (cognitive 21) · ×1
  • ArcOpener.TryOpen (cognitive 21) ArcFormats/Majiro/ArcMajiro.cs:57 — ArcOpener.TryOpen has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PakOpener.OpenPakV3 (cognitive 21) · ×1
  • PakOpener.OpenPakV3 (cognitive 21) ArcFormats/NitroPlus/ArcNitro.cs:122 — PakOpener.OpenPakV3 has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RpaOpener.TryOpen (cognitive 21) · ×1
  • RpaOpener.TryOpen (cognitive 21) ArcFormats/RenPy/ArcRPA.cs:59 — RpaOpener.TryOpen has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Mg2Format.ReadMetaData (cognitive 21) · ×1
  • Mg2Format.ReadMetaData (cognitive 21) ArcFormats/Valkyria/ImageMG2.cs:57 — Mg2Format.ReadMetaData has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriReader.PerformOperation (cognitive 21) · ×1
  • EriReader.PerformOperation (cognitive 21) ArcFormats/Entis/EriReader.cs:952 — EriReader.PerformOperation has cognitive complexity 21 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · RLEDecodeContext.GetGammaCode (cognitive 21) · ×1
  • RLEDecodeContext.GetGammaCode (cognitive 21) ArcFormats/Entis/EriReader.cs:2312 — RLEDecodeContext.GetGammaCode has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DwqBmpReader.Unpack (cognitive 21) · ×1
  • DwqBmpReader.Unpack (cognitive 21) ArcFormats/BlackCyc/ImageDWQ.cs:338 — DwqBmpReader.Unpack has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · YpfOpener.Create (cognitive 21) · ×1
  • YpfOpener.Create (cognitive 21) ArcFormats/YuRis/ArcYPF.cs:264 — YpfOpener.Create has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. Note what this body is, though: it works in explicit hardware vector and instruction-set types. A kernel divided across a call boundary passes its vectors between the parts and depends on the runtime putting them back together, so the division can cost more than the complexity it removes. The measurement stands — a hot path is not a licence to be unreadable — but the move that pays here is to lift the COLD parts out first (argument validation, fallback and error paths, one-off setup) and leave the kernel whole. Where the kernel itself has to be divided, ask for the extracted parts to be inlined as well, and measure the result rather than assuming the division is free.
D2 · Cognitive Complexity · Reader.UnpackIndexed (cognitive 21) · ×1
  • Reader.UnpackIndexed (cognitive 21) ArcFormats/AnimeGameSystem/ImageAinos.cs:235 — Reader.UnpackIndexed has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileSystemComparer.Compare (cognitive 21) · ×1
  • FileSystemComparer.Compare (cognitive 21) GUI/ViewModel.cs:140 — FileSystemComparer.Compare has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShiftReduceParser.DiscardInvalidTokens (cognitive 21) · ×1
  • ShiftReduceParser.DiscardInvalidTokens (cognitive 21) Experimental/Artemis/ShiftReduceParserCode.cs:429 — ShiftReduceParser.DiscardInvalidTokens has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MiaReader.UnpackInternal (cognitive 21) · ×1
  • MiaReader.UnpackInternal (cognitive 21) Legacy/Miami/ImageMIA.cs:107 — MiaReader.UnpackInternal has cognitive complexity 21 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · GrpOpener.OpenEntry (cognitive 20) · ×1
  • GrpOpener.OpenEntry (cognitive 20) ArcFormats/Ankh/ArcGRP.cs:175 — GrpOpener.OpenEntry has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DxrOpener.LookForXfir (cognitive 20) · ×1
  • DxrOpener.LookForXfir (cognitive 20) ArcFormats/Macromedia/ArcDXR.cs:399 — DxrOpener.LookForXfir has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SgfReader.GetNextByte (cognitive 20) · ×1
  • SgfReader.GetNextByte (cognitive 20) ArcFormats/Eternity/ImageSGF.cs:218 — SgfReader.GetNextByte has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ParallelCbgDecoder.UnpackAlpha (cognitive 20) · ×1
  • ParallelCbgDecoder.UnpackAlpha (cognitive 20) ArcFormats/Ethornell/ImageCBG.cs:574 — ParallelCbgDecoder.UnpackAlpha has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LsdOpener.UnpackD (cognitive 20) · ×1
  • LsdOpener.UnpackD (cognitive 20) ArcFormats/Gss/ArcARC.cs:144 — LsdOpener.UnpackD has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LzsFormat.Decompress (cognitive 20) · ×1
  • LzsFormat.Decompress (cognitive 20) ArcFormats/ImageLZS.cs:94 — LzsFormat.Decompress has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SceneOpener.TryOpen (cognitive 20) · ×1
  • SceneOpener.TryOpen (cognitive 20) ArcFormats/RealLive/ArcSCENE.cs:76 — SceneOpener.TryOpen has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RhaAudio.ConvertToMp3 (cognitive 20) · ×1
  • RhaAudio.ConvertToMp3 (cognitive 20) ArcFormats/rUGP/AudioRHA.cs:70 — RhaAudio.ConvertToMp3 has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CgV1Opener.TryOpen (cognitive 20) · ×1
  • CgV1Opener.TryOpen (cognitive 20) ArcFormats/SoftwareHouseParsley/ArcCG.cs:98 — CgV1Opener.TryOpen has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CrelicUnitedGameProject.ReadRelic (cognitive 20) · ×1
  • CrelicUnitedGameProject.ReadRelic (cognitive 20) ArcFormats/rUGP/ArcRIO.cs:1256 — CrelicUnitedGameProject.ReadRelic has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Arc4Opener.TryOpen (cognitive 20) · ×1
  • Arc4Opener.TryOpen (cognitive 20) ArcFormats/CaramelBox/ArcARC4.cs:53 — Arc4Opener.TryOpen has cognitive complexity 20 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · PakOpener.TryOpen (cognitive 20) · ×1
  • PakOpener.TryOpen (cognitive 20) ArcFormats/NitroPlus/ArcPAK.cs:50 — PakOpener.TryOpen has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Decoder.DecryptHelper1 (cognitive 20) · ×1
  • Decoder.DecryptHelper1 (cognitive 20) ArcFormats/ShiinaRio/WarcEncryption.cs:245 — Decoder.DecryptHelper1 has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ZbmFormat.Unpack (cognitive 20) · ×1
  • ZbmFormat.Unpack (cognitive 20) ArcFormats/BlueGale/ImageZBM.cs:88 — ZbmFormat.Unpack has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GpReader.UnpackV2 (cognitive 20) · ×1
  • GpReader.UnpackV2 (cognitive 20) ArcFormats/Eushully/ImageGP.cs:219 — GpReader.UnpackV2 has cognitive complexity 20 (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.
D2 · Cognitive Complexity · PakOpener.ReadMap (cognitive 20) · ×1
  • PakOpener.ReadMap (cognitive 20) ArcFormats/elf/ArcHED.cs:159 — PakOpener.ReadMap has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MarielEncoder.Unpack (cognitive 20) · ×1
  • MarielEncoder.Unpack (cognitive 20) ArcFormats/Hypatia/ArcKogado.cs:299 — MarielEncoder.Unpack has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NpaOpener.Create (cognitive 20) · ×1
  • NpaOpener.Create (cognitive 20) ArcFormats/NitroPlus/ArcNPA.cs:190 — NpaOpener.Create has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CgfOpener.TryOpen (cognitive 20) · ×1
  • CgfOpener.TryOpen (cognitive 20) ArcFormats/Triangle/ArcCGF.cs:49 — CgfOpener.TryOpen has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UnityObject.DeserializeType (cognitive 20) · ×1
  • UnityObject.DeserializeType (cognitive 20) ArcFormats/Unity/Asset.cs:246 — UnityObject.DeserializeType has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WarOpener.OpenEntry (cognitive 20) · ×1
  • WarOpener.OpenEntry (cognitive 20) ArcFormats/ShiinaRio/ArcWARC.cs:155 — WarOpener.OpenEntry has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WadyInput.Decode3 (cognitive 20) · ×1
  • WadyInput.Decode3 (cognitive 20) ArcFormats/Marble/AudioWADY.cs:152 — WadyInput.Decode3 has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackV1 (cognitive 20) · ×1
  • Reader.UnpackV1 (cognitive 20) ArcFormats/Circus/ImageCRX.cs:257 — Reader.UnpackV1 has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AllOpener.LzssUnpack (cognitive 20) · ×1
  • AllOpener.LzssUnpack (cognitive 20) Legacy/Giga/ArcALL.cs:69 — AllOpener.LzssUnpack has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArfOpener.Decompress (cognitive 20) · ×1
  • ArfOpener.Decompress (cognitive 20) Legacy/Logg/ArcARF.cs:94 — ArfOpener.Decompress has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FdReader.UnpackRgb (cognitive 20) · ×1
  • FdReader.UnpackRgb (cognitive 20) Legacy/Mink/ImageFD.cs:97 — FdReader.UnpackRgb has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FdReader.FdReader.ctor (cognitive 20) · ×1
  • FdReader.FdReader.ctor (cognitive 20) Legacy/Mink/ImageFD.cs:309 — FdReader.FdReader.ctor has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.TryOpen (cognitive 19) · ×1
  • DatOpener.TryOpen (cognitive 19) ArcFormats/Adobe/ArcAIR.cs:44 — DatOpener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LbgFormat.Read (cognitive 19) · ×1
  • LbgFormat.Read (cognitive 19) ArcFormats/Kid/ImageLBG.cs:51 — LbgFormat.Read has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PmsReader.Unpack8bpp (cognitive 19) · ×1
  • PmsReader.Unpack8bpp (cognitive 19) ArcFormats/AliceSoft/ImagePMS.cs:238 — PmsReader.Unpack8bpp has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · VwfAudio.DecodeAdp (cognitive 19) · ×1
  • VwfAudio.DecodeAdp (cognitive 19) ArcFormats/Cadath/AudioVWF.cs:99 — VwfAudio.DecodeAdp has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LsdOpener.OpenEntry (cognitive 19) · ×1
  • LsdOpener.OpenEntry (cognitive 19) ArcFormats/Gss/ArcARC.cs:77 — LsdOpener.OpenEntry has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PL10Opener.DecompressRLE (cognitive 19) · ×1
  • PL10Opener.DecompressRLE (cognitive 19) ArcFormats/Kaguya/ArcPL10.cs:132 — PL10Opener.DecompressRLE has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MmaOpener.UnpackLz (cognitive 19) · ×1
  • MmaOpener.UnpackLz (cognitive 19) ArcFormats/Mnp/ArcMMA.cs:184 — MmaOpener.UnpackLz has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · C24Decoder.Unpack (cognitive 19) · ×1
  • C24Decoder.Unpack (cognitive 19) ArcFormats/Foster/ImageC24.cs:157 — C24Decoder.Unpack has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · An21Opener.DecompressRLE (cognitive 19) · ×1
  • An21Opener.DecompressRLE (cognitive 19) ArcFormats/Kaguya/ArcAN21.cs:150 — An21Opener.DecompressRLE has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FgaOpener.TryOpen (cognitive 19) · ×1
  • FgaOpener.TryOpen (cognitive 19) ArcFormats/Lilim/ArcFGA.cs:41 — FgaOpener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PckOpener.LzssUnpack (cognitive 19) · ×1
  • PckOpener.LzssUnpack (cognitive 19) ArcFormats/Strikes/ArcPCK.cs:172 — PckOpener.LzssUnpack has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LagReader.Unpack (cognitive 19) · ×1
  • LagReader.Unpack (cognitive 19) ArcFormats/Strikes/ImageLAG.cs:113 — LagReader.Unpack has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PacOpener.TryOpen (cognitive 19) · ×1
  • PacOpener.TryOpen (cognitive 19) ArcFormats/Entis/ArcPAC.cs:47 — PacOpener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Arc3Opener.UnpackZeChunk (cognitive 19) · ×1
  • Arc3Opener.UnpackZeChunk (cognitive 19) ArcFormats/CaramelBox/ArcARC3.cs:237 — Arc3Opener.UnpackZeChunk has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VffOpener.TryOpen (cognitive 19) · ×1
  • VffOpener.TryOpen (cognitive 19) ArcFormats/LiveMaker/ArcVF.cs:51 — VffOpener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · Mk2Opener.TryOpen (cognitive 19) · ×1
  • Mk2Opener.TryOpen (cognitive 19) ArcFormats/Maika/ArcMK2.cs:70 — Mk2Opener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PsdReader.UnpackRLE (cognitive 19) · ×1
  • PsdReader.UnpackRLE (cognitive 19) ArcFormats/Adobe/ImagePSD.cs:188 — PsdReader.UnpackRLE has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · BmrDecoder.DecompressRLE (cognitive 19) · ×1
  • BmrDecoder.DecompressRLE (cognitive 19) ArcFormats/Kaguya/ArcLINK.cs:358 — BmrDecoder.DecompressRLE has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MgrOpener.TryOpen (cognitive 19) · ×1
  • MgrOpener.TryOpen (cognitive 19) ArcFormats/Propeller/ArcMGR.cs:43 — MgrOpener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PicReader.Unpack8bpp (cognitive 19) · ×1
  • PicReader.Unpack8bpp (cognitive 19) ArcFormats/Softpal/ImagePIC.cs:240 — PicReader.Unpack8bpp has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Wsm2Opener.TryOpen (cognitive 19) · ×1
  • Wsm2Opener.TryOpen (cognitive 19) ArcFormats/Tanaka/ArcWSM.cs:49 — Wsm2Opener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Res2Reader.Read (cognitive 19) · ×1
  • Res2Reader.Read (cognitive 19) ArcFormats/Sas5/ArcSec5.cs:396 — Res2Reader.Read has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbmReader.GetImageData (cognitive 19) · ×1
  • AbmReader.GetImageData (cognitive 19) ArcFormats/Lilim/ArcABM.cs:156 — AbmReader.GetImageData has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DpkOpener.TryOpen (cognitive 19) · ×1
  • DpkOpener.TryOpen (cognitive 19) ArcFormats/Dac/ArcDPK.cs:86 — DpkOpener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NpaOpener.TryOpen (cognitive 19) · ×1
  • NpaOpener.TryOpen (cognitive 19) ArcFormats/NitroPlus/ArcNPA.cs:120 — NpaOpener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TcdIndexReader.ReadIndex (cognitive 19) · ×1
  • TcdIndexReader.ReadIndex (cognitive 19) ArcFormats/TopCat/ArcTCD3.cs:276 — TcdIndexReader.ReadIndex has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · PackIndexReader.Read (cognitive 19) · ×1
  • PackIndexReader.Read (cognitive 19) ArcFormats/Qlie/ArcQLIE.cs:411 — PackIndexReader.Read has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pickle.BatchDict (cognitive 19) · ×1
  • Pickle.BatchDict (cognitive 19) ArcFormats/RenPy/ArcRPA.cs:413 — Pickle.BatchDict has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.QlzUnpack (cognitive 19) · ×1
  • DatOpener.QlzUnpack (cognitive 19) ArcFormats/Unity/Gx4Lib/ArcDAT.cs:176 — DatOpener.QlzUnpack has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Arc2Opener.TryOpen (cognitive 19) · ×1
  • Arc2Opener.TryOpen (cognitive 19) ArcFormats/Will/ArcPulltop.cs:53 — Arc2Opener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriReader.InitializeZigZagTable (cognitive 19) · ×1
  • EriReader.InitializeZigZagTable (cognitive 19) ArcFormats/Entis/EriReader.cs:360 — EriReader.InitializeZigZagTable has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BdfArchive.DecodeFrame (cognitive 19) · ×1
  • BdfArchive.DecodeFrame (cognitive 19) ArcFormats/Zyx/ArcBDF.cs:95 — BdfArchive.DecodeFrame has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PackedReader.Unpack (cognitive 19) · ×1
  • PackedReader.Unpack (cognitive 19) ArcFormats/ArcSPack.cs:133 — PackedReader.Unpack has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PcmDecoder.UnpackV1 (cognitive 19) · ×1
  • PcmDecoder.UnpackV1 (cognitive 19) ArcFormats/Circus/AudioPCM.cs:128 — PcmDecoder.UnpackV1 has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackLineAlpha (cognitive 19) · ×1
  • Reader.UnpackLineAlpha (cognitive 19) ArcFormats/Dac/ImageDGC.cs:379 — Reader.UnpackLineAlpha has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Reader.UnpackLineLZ (cognitive 19) · ×1
  • Reader.UnpackLineLZ (cognitive 19) ArcFormats/Dac/ImageDGC.cs:426 — Reader.UnpackLineLZ has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.Unpack (cognitive 19) · ×1
  • Reader.Unpack (cognitive 19) ArcFormats/Tactics/ImageTGF.cs:112 — Reader.Unpack has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TlgFormat.TVPTLG6DecodeLineGeneric (cognitive 19) · ×1
  • TlgFormat.TVPTLG6DecodeLineGeneric (cognitive 19) ArcFormats/KiriKiri/ImageTLG.cs:634 — TlgFormat.TVPTLG6DecodeLineGeneric has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.ReadRLE (cognitive 19) · ×1
  • Reader.ReadRLE (cognitive 19) GameRes/ImageTGA.cs:286 — Reader.ReadRLE has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GarConvertMedia.ConvertWorker (cognitive 19) · ×1
  • GarConvertMedia.ConvertWorker (cognitive 19) GUI/GarConvert.cs:139 — GarConvertMedia.ConvertWorker has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NeExeOpener.TryOpen (cognitive 19) · ×1
  • NeExeOpener.TryOpen (cognitive 19) Experimental/Microsoft/ArcNE.cs:56 — NeExeOpener.TryOpen has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.ReadIndex (cognitive 19) · ×1
  • DatOpener.ReadIndex (cognitive 19) Legacy/Lazycrew/ArcDAT.cs:102 — DatOpener.ReadIndex has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DesTransform.TransformQWord (cognitive 19) · ×1
  • DesTransform.TransformQWord (cognitive 19) REDACTED:229 — DesTransform.TransformQWord has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SwgFormat.Decompress (cognitive 19) · ×1
  • SwgFormat.Decompress (cognitive 19) Legacy/SplushWave/ImageSWG.cs:93 — SwgFormat.Decompress has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · MpkCompression.sub_42A1A0 (cognitive 19) · ×1
  • MpkCompression.sub_42A1A0 (cognitive 19) Legacy/Kurumi/ArcMPK.cs:281 — MpkCompression.sub_42A1A0 has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · LzssDecompressor.Unpack (cognitive 19) · ×1
  • LzssDecompressor.Unpack (cognitive 19) Legacy/Melody/ImageMGO.cs:108 — LzssDecompressor.Unpack has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · P2tOpener.LzssDecompress (cognitive 18) · ×1
  • P2tOpener.LzssDecompress (cognitive 18) ArcFormats/Kid/ArcP2T.cs:110 — P2tOpener.LzssDecompress has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TlgOpener.TryOpen (cognitive 18) · ×1
  • TlgOpener.TryOpen (cognitive 18) ArcFormats/KiriKiri/ArcTLG.cs:36 — TlgOpener.TryOpen has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HuffmanTree.Build (cognitive 18) · ×1
  • HuffmanTree.Build (cognitive 18) ArcFormats/HuneX/Decoder.cs:58 — HuffmanTree.Build has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DcfReader.Unpack (cognitive 18) · ×1
  • DcfReader.Unpack (cognitive 18) ArcFormats/AliceSoft/ImageDCF.cs:139 — DcfReader.Unpack has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DxrOpener.ImportBitmap (cognitive 18) · ×1
  • DxrOpener.ImportBitmap (cognitive 18) ArcFormats/Macromedia/ArcDXR.cs:235 — DxrOpener.ImportBitmap has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GsaFormat.TryBlendImage (cognitive 18) · ×1
  • GsaFormat.TryBlendImage (cognitive 18) ArcFormats/Bishop/ImageGSA.cs:99 — GsaFormat.TryBlendImage has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CandyDecoder.RestorePixels (cognitive 18) · ×1
  • CandyDecoder.RestorePixels (cognitive 18) ArcFormats/Interheart/ImageCandy.cs:163 — CandyDecoder.RestorePixels has cognitive complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · LaxStream.LzssUnpack (cognitive 18) · ×1
  • LaxStream.LzssUnpack (cognitive 18) ArcFormats/Lambda/ArcLAX.cs:164 — LaxStream.LzssUnpack has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · KcapOpener.TryOpen (cognitive 18) · ×1
  • KcapOpener.TryOpen (cognitive 18) ArcFormats/Leaf/ArcPAK.cs:52 — KcapOpener.TryOpen has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Wv5Decoder.Unpack (cognitive 18) · ×1
  • Wv5Decoder.Unpack (cognitive 18) ArcFormats/Maika/AudioWV5.cs:83 — Wv5Decoder.Unpack has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Ylz16Reader.Unpack (cognitive 18) · ×1
  • Ylz16Reader.Unpack (cognitive 18) ArcFormats/ShiinaRio/ArcWARC1.0.cs:130 — Ylz16Reader.Unpack has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CRioArchive.ReadRioReference (cognitive 18) · ×1
  • CRioArchive.ReadRioReference (cognitive 18) ArcFormats/rUGP/ArcRIO.cs:630 — CRioArchive.ReadRioReference has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · MtfPackedStream.Unpack (cognitive 18) · ×1
  • MtfPackedStream.Unpack (cognitive 18) ArcFormats/Primel/Compression.cs:302 — MtfPackedStream.Unpack has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PkOpener.TryOpen (cognitive 18) · ×1
  • PkOpener.TryOpen (cognitive 18) ArcFormats/Banana/ArcPK.cs:49 — PkOpener.TryOpen has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pak0Opener.DecryptScript (cognitive 18) · ×1
  • Pak0Opener.DecryptScript (cognitive 18) ArcFormats/StudioEgo/ArcPAK0.cs:81 — Pak0Opener.DecryptScript has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GpcOpener.UnpackEntry (cognitive 18) · ×1
  • GpcOpener.UnpackEntry (cognitive 18) ArcFormats/SuperNekoX/ArcGPC.cs:149 — GpcOpener.UnpackEntry has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IndexReader.ReadV2 (cognitive 18) · ×1
  • IndexReader.ReadV2 (cognitive 18) ArcFormats/Bishop/ArcBSA.cs:118 — IndexReader.ReadV2 has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GyuReader.ReadAlpha (cognitive 18) · ×1
  • GyuReader.ReadAlpha (cognitive 18) ArcFormats/ExHibit/ImageGYU.cs:344 — GyuReader.ReadAlpha has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Sec5Opener.FindSec5Resr (cognitive 18) · ×1
  • Sec5Opener.FindSec5Resr (cognitive 18) ArcFormats/Sas5/ArcSec5.cs:103 — Sec5Opener.FindSec5Resr has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PakOpener.GetFileMap (cognitive 18) · ×1
  • PakOpener.GetFileMap (cognitive 18) ArcFormats/elf/ArcHED.cs:122 — PakOpener.GetFileMap has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcIndexReader.GuessScheme (cognitive 18) · ×1
  • ArcIndexReader.GuessScheme (cognitive 18) ArcFormats/RPM/ArcARC.cs:220 — ArcIndexReader.GuessScheme has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IntOpener.TryOpen (cognitive 18) · ×1
  • IntOpener.TryOpen (cognitive 18) ArcFormats/CatSystem/ArcINT.cs:123 — IntOpener.TryOpen has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LstOpener.OpenNexton (cognitive 18) · ×1
  • LstOpener.OpenNexton (cognitive 18) ArcFormats/Tactics/ArcLST.cs:100 — LstOpener.OpenNexton has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PackOpener.TryOpen (cognitive 18) · ×1
  • PackOpener.TryOpen (cognitive 18) ArcFormats/Qlie/ArcQLIE.cs:105 — PackOpener.TryOpen has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pickle.BatchList (cognitive 18) · ×1
  • Pickle.BatchList (cognitive 18) ArcFormats/RenPy/ArcRPA.cs:330 — Pickle.BatchList has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Wa1Reader.UnpackV0 (cognitive 18) · ×1
  • Wa1Reader.UnpackV0 (cognitive 18) ArcFormats/Ffa/AudioWA1.cs:277 — Wa1Reader.UnpackV0 has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriFormat.ParseTagInfo (cognitive 18) · ×1
  • EriFormat.ParseTagInfo (cognitive 18) ArcFormats/Entis/ImageERI.cs:318 — EriFormat.ParseTagInfo has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · McgDecoder.UnpackV200 (cognitive 18) · ×1
  • McgDecoder.UnpackV200 (cognitive 18) ArcFormats/FC01/ImageMCG.cs:268 — McgDecoder.UnpackV200 has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Adler32.Update (cognitive 18) · ×1
  • Adler32.Update (cognitive 18) GameRes/Checksum.cs:133 — Adler32.Update has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Localization.Plural (cognitive 18) · ×1
  • Localization.Plural (cognitive 18) GUI/Utility.cs:129 — Localization.Plural has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MainWindow.OpenDirectoryEntry (cognitive 18) · ×1
  • MainWindow.OpenDirectoryEntry (cognitive 18) GUI/MainWindow.xaml.cs:922 — MainWindow.OpenDirectoryEntry has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IrisPckOpener.TryOpen (cognitive 18) · ×1
  • IrisPckOpener.TryOpen (cognitive 18) Experimental/CatSystem/ArcIRIS.cs:41 — IrisPckOpener.TryOpen has cognitive complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · NeExeOpener.OpenVersion (cognitive 18) · ×1
  • NeExeOpener.OpenVersion (cognitive 18) Experimental/Microsoft/ArcNE.cs:119 — NeExeOpener.OpenVersion has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.LzUnpack (cognitive 18) · ×1
  • DatOpener.LzUnpack (cognitive 18) Legacy/Peach/ArcDAT.cs:112 — DatOpener.LzUnpack has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AdpAudio.TryOpen (cognitive 18) · ×1
  • AdpAudio.TryOpen (cognitive 18) Legacy/CrossNet/AudioADP.cs:40 — AdpAudio.TryOpen has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · AbcDecoder.sub_4118F0 (cognitive 18) · ×1
  • AbcDecoder.sub_4118F0 (cognitive 18) Legacy/Sarang/ImageABC.cs:250 — AbcDecoder.sub_4118F0 has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GCmpDecoder.Unpack8bpp (cognitive 18) · ×1
  • GCmpDecoder.Unpack8bpp (cognitive 18) Legacy/Nekotaro/ImageGCmp.cs:201 — GCmpDecoder.Unpack8bpp has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GCmpDecoder.RetrievePalette (cognitive 18) · ×1
  • GCmpDecoder.RetrievePalette (cognitive 18) Legacy/Nekotaro/ImageGCmp.cs:312 — GCmpDecoder.RetrievePalette has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pb6Format.Read (cognitive 17) · ×1
  • Pb6Format.Read (cognitive 17) ArcFormats/Actgs/ImagePB6.cs:79 — Pb6Format.Read has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pb6Format.DecodeRle (cognitive 17) · ×1
  • Pb6Format.DecodeRle (cognitive 17) ArcFormats/Actgs/ImagePB6.cs:150 — Pb6Format.DecodeRle has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.ReadTable2 (cognitive 17) · ×1
  • DatOpener.ReadTable2 (cognitive 17) ArcFormats/Artdink/ArcDAT.cs:99 — DatOpener.ReadTable2 has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TagFormat.Read (cognitive 17) · ×1
  • TagFormat.Read (cognitive 17) ArcFormats/Artdink/ImageTAG.cs:102 — TagFormat.Read has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DirectorFile.ReadCasts (cognitive 17) · ×1
  • DirectorFile.ReadCasts (cognitive 17) ArcFormats/Macromedia/DirectorFile.cs:264 — DirectorFile.ReadCasts has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ImgReader.Unpack24bpp (cognitive 17) · ×1
  • ImgReader.Unpack24bpp (cognitive 17) ArcFormats/ScrPlayer/ImageIMG.cs:99 — ImgReader.Unpack24bpp has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BpcReader.Unpack24bpp (cognitive 17) · ×1
  • BpcReader.Unpack24bpp (cognitive 17) ArcFormats/CsWare/ImageBPC.cs:148 — BpcReader.Unpack24bpp has cognitive complexity 17 (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.
D2 · Cognitive Complexity · DatOpener.TryOpen (cognitive 17) · ×1
  • DatOpener.TryOpen (cognitive 17) ArcFormats/Groover/ArcPCG.cs:47 — DatOpener.TryOpen has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · PakOpener.TryOpen (cognitive 17) · ×1
  • PakOpener.TryOpen (cognitive 17) ArcFormats/Key/ArcPAK.cs:46 — PakOpener.TryOpen has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ClsReader.ReadV1 (cognitive 17) · ×1
  • ClsReader.ReadV1 (cognitive 17) ArcFormats/Lambda/ImageCLS.cs:215 — ClsReader.ReadV1 has cognitive complexity 17 (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.
D2 · Cognitive Complexity · SDatOpener.TryOpen (cognitive 17) · ×1
  • SDatOpener.TryOpen (cognitive 17) ArcFormats/Leaf/ArcSDAT.cs:41 — SDatOpener.TryOpen has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcOpener.LzUnpack (cognitive 17) · ×1
  • ArcOpener.LzUnpack (cognitive 17) ArcFormats/MicroVision/ArcARC.cs:95 — ArcOpener.LzUnpack has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcOpener.TryOpen (cognitive 17) · ×1
  • ArcOpener.TryOpen (cognitive 17) ArcFormats/Suika/ArcSuika.cs:61 — ArcOpener.TryOpen has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Mv2Decoder.Unpack (cognitive 17) · ×1
  • Mv2Decoder.Unpack (cognitive 17) ArcFormats/Cmvs/AudioMV2.cs:79 — Mv2Decoder.Unpack has cognitive complexity 17 (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.
D2 · Cognitive Complexity · ExeFile.FindString (cognitive 17) · ×1
  • ExeFile.FindString (cognitive 17) ArcFormats/ExeFile.cs:136 — ExeFile.FindString has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Lz4Stream.ReadNextBlock (cognitive 17) · ×1
  • Lz4Stream.ReadNextBlock (cognitive 17) ArcFormats/Lz4Stream.cs:148 — Lz4Stream.ReadNextBlock has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pb00Format.Read (cognitive 17) · ×1
  • Pb00Format.Read (cognitive 17) ArcFormats/Mixwill/ImagePB00.cs:66 — Pb00Format.Read has cognitive complexity 17 (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.
D2 · Cognitive Complexity · PakOpener.TryOpenGxpFile (cognitive 17) · ×1
  • PakOpener.TryOpenGxpFile (cognitive 17) ArcFormats/Astronauts/ArcGXP.cs:63 — PakOpener.TryOpenGxpFile has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AImageReader.Unpack (cognitive 17) · ×1
  • AImageReader.Unpack (cognitive 17) ArcFormats/Cyberworks/ImageTINK.cs:173 — AImageReader.Unpack has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · MmdFormat.Read (cognitive 17) · ×1
  • MmdFormat.Read (cognitive 17) ArcFormats/Ivory/ImageMMD.cs:68 — MmdFormat.Read has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Lin2Opener.UnpackLzss (cognitive 17) · ×1
  • Lin2Opener.UnpackLzss (cognitive 17) ArcFormats/Kaguya/ArcLIN2.cs:93 — Lin2Opener.UnpackLzss has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VocReader.ConvertToPcm (cognitive 17) · ×1
  • VocReader.ConvertToPcm (cognitive 17) ArcFormats/AudioVOC.cs:51 — VocReader.ConvertToPcm has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Channel.Decode5 (cognitive 17) · ×1
  • Channel.Decode5 (cognitive 17) ArcFormats/Cri/AudioHCA.cs:802 — Channel.Decode5 has cognitive complexity 17 (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.
D2 · Cognitive Complexity · PsbReader.ReadNames (cognitive 17) · ×1
  • PsbReader.ReadNames (cognitive 17) ArcFormats/Emote/ArcPSB.cs:466 — PsbReader.ReadNames has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PbReaderBase.UnpackJbp (cognitive 17) · ×1
  • PbReaderBase.UnpackJbp (cognitive 17) ArcFormats/Cmvs/ImagePB3.cs:147 — PbReaderBase.UnpackJbp has cognitive complexity 17 (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.
D2 · Cognitive Complexity · WapeDecoder.ConvertToPcm (cognitive 17) · ×1
  • WapeDecoder.ConvertToPcm (cognitive 17) ArcFormats/TechnoBrain/AudioWAPE.cs:78 — WapeDecoder.ConvertToPcm has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IndexReaderV2.ReadFileTable (cognitive 17) · ×1
  • IndexReaderV2.ReadFileTable (cognitive 17) ArcFormats/DxLib/ArcDX.cs:430 — IndexReaderV2.ReadFileTable has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MpxOpener.TryOpen (cognitive 17) · ×1
  • MpxOpener.TryOpen (cognitive 17) ArcFormats/Ikura/ArcDRS.cs:125 — MpxOpener.TryOpen has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · IntOpener.Create (cognitive 17) · ×1
  • IntOpener.Create (cognitive 17) ArcFormats/CatSystem/ArcINT.cs:287 — IntOpener.Create has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PakOpener.Create (cognitive 17) · ×1
  • PakOpener.Create (cognitive 17) ArcFormats/Hypatia/ArcKogado.cs:187 — PakOpener.Create has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OdnIndexReader.FixupDir (cognitive 17) · ×1
  • OdnIndexReader.FixupDir (cognitive 17) ArcFormats/Valkyria/ArcODN.cs:345 — OdnIndexReader.FixupDir has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DwqFormat.Read (cognitive 17) · ×1
  • DwqFormat.Read (cognitive 17) ArcFormats/BlackCyc/ImageDWQ.cs:148 — DwqFormat.Read has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · YpfOpener.DecryptYstb (cognitive 17) · ×1
  • YpfOpener.DecryptYstb (cognitive 17) ArcFormats/YuRis/ArcYPF.cs:419 — YpfOpener.DecryptYstb has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PcmDecoder.DecodeV1 (cognitive 17) · ×1
  • PcmDecoder.DecodeV1 (cognitive 17) ArcFormats/Circus/AudioPCM.cs:188 — PcmDecoder.DecodeV1 has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.UnpackChannel (cognitive 17) · ×1
  • Reader.UnpackChannel (cognitive 17) ArcFormats/Pajamas/ImageEPA.cs:205 — Reader.UnpackChannel has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IafFormat.Read (cognitive 17) · ×1
  • IafFormat.Read (cognitive 17) ArcFormats/Triangle/ImageIAF.cs:120 — IafFormat.Read has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OggAudio.TryOpen (cognitive 17) · ×1
  • OggAudio.TryOpen (cognitive 17) ArcFormats/AudioOGG.cs:143 — OggAudio.TryOpen has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileSystemStack.ChDir (cognitive 17) · ×1
  • FileSystemStack.ChDir (cognitive 17) GameRes/FileSystem.cs:573 — FileSystemStack.ChDir has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GpcReader.UnpackData (cognitive 17) · ×1
  • GpcReader.UnpackData (cognitive 17) Legacy/Adv98/ImageGPC.cs:152 — GpcReader.UnpackData has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · YskOpener.OpenEntry (cognitive 17) · ×1
  • YskOpener.OpenEntry (cognitive 17) REDACTED:84 — YskOpener.OpenEntry has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LibOpener.LzssUnpack (cognitive 17) · ×1
  • LibOpener.LzssUnpack (cognitive 17) Legacy/System98/ArcLIB.cs:100 — LibOpener.LzssUnpack has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MpkOpener.TryOpen (cognitive 17) · ×1
  • MpkOpener.TryOpen (cognitive 17) Legacy/Tako/ArcMPK.cs:47 — MpkOpener.TryOpen has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GdpOpener.TryOpen (cognitive 16) · ×1
  • GdpOpener.TryOpen (cognitive 16) ArcFormats/Guyzware/ArcDat.cs:18 — GdpOpener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DcfReader.BlendOverlay (cognitive 16) · ×1
  • DcfReader.BlendOverlay (cognitive 16) ArcFormats/AliceSoft/ImageDCF.cs:256 — DcfReader.BlendOverlay has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · B5Reader.Unpack (cognitive 16) · ×1
  • B5Reader.Unpack (cognitive 16) ArcFormats/CsWare/ImageB5.cs:88 — B5Reader.Unpack has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Tim2Reader.ReadPalette (cognitive 16) · ×1
  • Tim2Reader.ReadPalette (cognitive 16) ArcFormats/DigitalWorks/ImageTM2.cs:188 — Tim2Reader.ReadPalette has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DxtDecoder.DecompressDXT5Block (cognitive 16) · ×1
  • DxtDecoder.DecompressDXT5Block (cognitive 16) ArcFormats/DirectDraw/DxtDecoder.cs:165 — DxtDecoder.DecompressDXT5Block has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CsafOpener.TryOpen (cognitive 16) · ×1
  • CsafOpener.TryOpen (cognitive 16) ArcFormats/FamilyAdvSystem/ArcCSAF.cs:60 — CsafOpener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HxChachaDecryptor.Decrypt (cognitive 16) · ×1
  • HxChachaDecryptor.Decrypt (cognitive 16) ArcFormats/KiriKiri/HxCrypt.cs:843 — HxChachaDecryptor.Decrypt has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · LfgReader.Unpack (cognitive 16) · ×1
  • LfgReader.Unpack (cognitive 16) ArcFormats/Leaf/ImageLFG.cs:107 — LfgReader.Unpack has cognitive complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LcfFormat.Read (cognitive 16) · ×1
  • LcfFormat.Read (cognitive 16) ArcFormats/Leaf/ImageLFB.cs:246 — LcfFormat.Read has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PmDatOpener.LzUnpack (cognitive 16) · ×1
  • PmDatOpener.LzUnpack (cognitive 16) ArcFormats/GameSystem/ArcPureMail.cs:104 — PmDatOpener.LzUnpack has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PcmDecoder.Decode (cognitive 16) · ×1
  • PcmDecoder.Decode (cognitive 16) ArcFormats/Masys/ArcMGS.cs:172 — PcmDecoder.Decode has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · ChdReader.Unpack (cognitive 16) · ×1
  • ChdReader.Unpack (cognitive 16) ArcFormats/ShiinaRio/ImageCHD.cs:98 — ChdReader.Unpack has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PbzOpener.DecryptScript (cognitive 16) · ×1
  • PbzOpener.DecryptScript (cognitive 16) ArcFormats/Cmvs/ArcPBZ.cs:138 — PbzOpener.DecryptScript has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · SgRgbReader.UnpackV3 (cognitive 16) · ×1
  • SgRgbReader.UnpackV3 (cognitive 16) ArcFormats/Ivory/ImageSG.cs:347 — SgRgbReader.UnpackV3 has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HcaReader.ParseHeader (cognitive 16) · ×1
  • HcaReader.ParseHeader (cognitive 16) ArcFormats/Cri/AudioHCA.cs:276 — HcaReader.ParseHeader 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.
D2 · Cognitive Complexity · HcaReader.InitChannels (cognitive 16) · ×1
  • HcaReader.InitChannels (cognitive 16) ArcFormats/Cri/AudioHCA.cs:347 — HcaReader.InitChannels has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AlpBitmap.Read (cognitive 16) · ×1
  • AlpBitmap.Read (cognitive 16) ArcFormats/NekoSDK/ImageALP.cs:37 — AlpBitmap.Read has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AlbStream.ReadSeq (cognitive 16) · ×1
  • AlbStream.ReadSeq (cognitive 16) ArcFormats/Slg/ImageALB.cs:132 — AlbStream.ReadSeq has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Pb3Reader.BlendInput (cognitive 16) · ×1
  • Pb3Reader.BlendInput (cognitive 16) ArcFormats/Cmvs/ImagePB3.cs:411 — Pb3Reader.BlendInput has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HOpener.TryOpenWithIndex (cognitive 16) · ×1
  • HOpener.TryOpenWithIndex (cognitive 16) ArcFormats/Eushully/ArcGPC.cs:39 — HOpener.TryOpenWithIndex has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · G2Opener.TryOpen (cognitive 16) · ×1
  • G2Opener.TryOpen (cognitive 16) ArcFormats/Glib2/ArcG2.cs:94 — G2Opener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · Ai6Opener.TryOpen (cognitive 16) · ×1
  • Ai6Opener.TryOpen (cognitive 16) ArcFormats/Silky/ArcAi6Win.cs:51 — Ai6Opener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Ai6Opener.Create (cognitive 16) · ×1
  • Ai6Opener.Create (cognitive 16) ArcFormats/Silky/ArcAi6Win.cs:102 — Ai6Opener.Create has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VafsOpener.OpenAudioEntry (cognitive 16) · ×1
  • VafsOpener.OpenAudioEntry (cognitive 16) ArcFormats/Softpal/ArcVAFS.cs:206 — VafsOpener.OpenAudioEntry has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DxOpener.GuessKey (cognitive 16) · ×1
  • DxOpener.GuessKey (cognitive 16) ArcFormats/DxLib/ArcDX.cs:114 — DxOpener.GuessKey has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IndexReader.ReadV1 (cognitive 16) · ×1
  • IndexReader.ReadV1 (cognitive 16) ArcFormats/Bishop/ArcBSA.cs:82 — IndexReader.ReadV1 has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GyuReader.UnpackGyu (cognitive 16) · ×1
  • GyuReader.UnpackGyu (cognitive 16) ArcFormats/ExHibit/ImageGYU.cs:295 — GyuReader.UnpackGyu has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IarOpener.TryOpen (cognitive 16) · ×1
  • IarOpener.TryOpen (cognitive 16) ArcFormats/Sas5/ArcIAR.cs:67 — IarOpener.TryOpen has cognitive complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · IarImage.Blend (cognitive 16) · ×1
  • IarImage.Blend (cognitive 16) ArcFormats/Sas5/ArcIAR.cs:331 — IarImage.Blend has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Him4Opener.DetectFileTypes (cognitive 16) · ×1
  • Him4Opener.DetectFileTypes (cognitive 16) ArcFormats/SHSystem/ArcHXP.cs:77 — Him4Opener.DetectFileTypes has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AldOpener.TryOpen (cognitive 16) · ×1
  • AldOpener.TryOpen (cognitive 16) ArcFormats/AliceSoft/ArcALD.cs:43 — AldOpener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DscDecoder.HuffmanDecompress (cognitive 16) · ×1
  • DscDecoder.HuffmanDecompress (cognitive 16) ArcFormats/Ethornell/ArcBGI.cs:330 — DscDecoder.HuffmanDecompress has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.Create (cognitive 16) · ×1
  • DatOpener.Create (cognitive 16) ArcFormats/StudioEgo/ArcEGO.cs:69 — DatOpener.Create has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MgpkOpener.lzf_decompress (cognitive 16) · ×1
  • MgpkOpener.lzf_decompress (cognitive 16) ArcFormats/MangaGamer/ArcMGPK.cs:137 — MgpkOpener.lzf_decompress has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Unpacker.DecodeLZSS (cognitive 16) · ×1
  • Unpacker.DecodeLZSS (cognitive 16) ArcFormats/NScripter/ArcNSA.cs:370 — Unpacker.DecodeLZSS has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PckOpener.TryOpen (cognitive 16) · ×1
  • PckOpener.TryOpen (cognitive 16) ArcFormats/Crowd/ArcPCK.cs:43 — PckOpener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reader.InitTable0 (cognitive 16) · ×1
  • Reader.InitTable0 (cognitive 16) ArcFormats/uGOS/ImageBMP.cs:377 — Reader.InitTable0 has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · PkOpener.LzUnpack (cognitive 16) · ×1
  • PkOpener.LzUnpack (cognitive 16) ArcFormats/UMeSoft/ArcPK.cs:100 — PkOpener.LzUnpack has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriReader.EriReader.ctor (cognitive 16) · ×1
  • EriReader.EriReader.ctor (cognitive 16) ArcFormats/Entis/EriReader.cs:83 — EriReader.EriReader.ctor has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EriReader.InitializeArrangeTable (cognitive 16) · ×1
  • EriReader.InitializeArrangeTable (cognitive 16) ArcFormats/Entis/EriReader.cs:302 — EriReader.InitializeArrangeTable has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · EriReader.GetLLRestoreFunc (cognitive 16) · ×1
  • EriReader.GetLLRestoreFunc (cognitive 16) ArcFormats/Entis/EriReader.cs:1021 — EriReader.GetLLRestoreFunc has cognitive complexity 16 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · EriReader.GetLSRestoreFunc (cognitive 16) · ×1
  • EriReader.GetLSRestoreFunc (cognitive 16) ArcFormats/Entis/EriReader.cs:1058 — EriReader.GetLSRestoreFunc has cognitive complexity 16 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ProbDecodeContext.DecodeERISACodeBytes (cognitive 16) · ×1
  • ProbDecodeContext.DecodeERISACodeBytes (cognitive 16) ArcFormats/Entis/EriReader.cs:2636 — ProbDecodeContext.DecodeERISACodeBytes has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ArcOpener.UnpackCustomLzss (cognitive 16) · ×1
  • ArcOpener.UnpackCustomLzss (cognitive 16) ArcFormats/Tactics/ArcTactics.cs:276 — ArcOpener.UnpackCustomLzss has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · XflOpener.ReadDirectory (cognitive 16) · ×1
  • XflOpener.ReadDirectory (cognitive 16) ArcFormats/Liar/ArcXFL.cs:54 — XflOpener.ReadDirectory has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · XflOpener.Create (cognitive 16) · ×1
  • XflOpener.Create (cognitive 16) ArcFormats/Liar/ArcXFL.cs:100 — XflOpener.Create has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BitdDecoder.BitdDecoder.ctor (cognitive 16) · ×1
  • BitdDecoder.BitdDecoder.ctor (cognitive 16) ArcFormats/Macromedia/ImageBITD.cs:60 — BitdDecoder.BitdDecoder.ctor has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BitdDecoder.GetImageData (cognitive 16) · ×1
  • BitdDecoder.GetImageData (cognitive 16) ArcFormats/Macromedia/ImageBITD.cs:96 — BitdDecoder.GetImageData has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BitdDecoder.UnpackScanLine (cognitive 16) · ×1
  • BitdDecoder.UnpackScanLine (cognitive 16) ArcFormats/Macromedia/ImageBITD.cs:174 — BitdDecoder.UnpackScanLine has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DziFormat.Read (cognitive 16) · ×1
  • DziFormat.Read (cognitive 16) ArcFormats/Malie/ImageDZI.cs:125 — DziFormat.Read has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RctFormat.FindImageKey (cognitive 16) · ×1
  • RctFormat.FindImageKey (cognitive 16) ArcFormats/Majiro/ImageRCT.cs:304 — RctFormat.FindImageKey has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TlgFormat.ReadREF (cognitive 16) · ×1
  • TlgFormat.ReadREF (cognitive 16) ArcFormats/KiriKiri/ImageTLG.cs:1461 — TlgFormat.ReadREF has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WbmReader.UnpackV9 (cognitive 16) · ×1
  • WbmReader.UnpackV9 (cognitive 16) ArcFormats/WildBug/ImageWBM.cs:473 — WbmReader.UnpackV9 has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CxEncryption.Init (cognitive 16) · ×1
  • CxEncryption.Init (cognitive 16) ArcFormats/KiriKiri/KiriKiriCx.cs:101 — CxEncryption.Init has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ListViewEx.ContinueDragSelect (cognitive 16) · ×1
  • ListViewEx.ContinueDragSelect (cognitive 16) GUI/ListViewEx.cs:105 — ListViewEx.ContinueDragSelect has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ImageConverter.Run (cognitive 16) · ×1
  • ImageConverter.Run (cognitive 16) Image.Convert/Program.cs:81 — ImageConverter.Run has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GrpReader.PutByte (cognitive 16) · ×1
  • GrpReader.PutByte (cognitive 16) Legacy/Bom/ImageGRP.cs:376 — GrpReader.PutByte has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TbmFormat.ReadMetaData (cognitive 16) · ×1
  • TbmFormat.ReadMetaData (cognitive 16) Legacy/Broccoli/ImageTbm.cs:55 — TbmFormat.ReadMetaData has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · D000Opener.TryOpen (cognitive 16) · ×1
  • D000Opener.TryOpen (cognitive 16) Legacy/Desire/ArcDSV.cs:42 — D000Opener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CpcOpener.TryOpen (cognitive 16) · ×1
  • CpcOpener.TryOpen (cognitive 16) Legacy/BRoom/ArcCPC.cs:44 — CpcOpener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PwvAudio.Unpack (cognitive 16) · ×1
  • PwvAudio.Unpack (cognitive 16) Legacy/Mermaid/AudioPWV.cs:63 — PwvAudio.Unpack has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EncryptedIndexReader.GetIndex (cognitive 16) · ×1
  • EncryptedIndexReader.GetIndex (cognitive 16) Legacy/Pias/EncryptedGraphDat.cs:51 — EncryptedIndexReader.GetIndex has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PkDatOpener.TryOpen (cognitive 16) · ×1
  • PkDatOpener.TryOpen (cognitive 16) Legacy/Paprika/ArcPKDAT.cs:44 — PkDatOpener.TryOpen has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NijiDatOpener.LzUnpack (cognitive 16) · ×1
  • NijiDatOpener.LzUnpack (cognitive 16) Legacy/Peach/ArcNIJI.cs:86 — NijiDatOpener.LzUnpack has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Wv3Decoder.Decode (cognitive 16) · ×1
  • Wv3Decoder.Decode (cognitive 16) Legacy/Eve/AudioWV.cs:85 — Wv3Decoder.Decode has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NorOpener.NcmbDecompress (cognitive 16) · ×1
  • NorOpener.NcmbDecompress (cognitive 16) Legacy/Sophia/ArcNOR.cs:101 — NorOpener.NcmbDecompress has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DatOpener.LzssUnpack (cognitive 16) · ×1
  • DatOpener.LzssUnpack (cognitive 16) Legacy/SplushWave/ArcDAT.cs:98 — DatOpener.LzssUnpack has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Swg1ImageDecoder.GetImageData (cognitive 16) · ×1
  • Swg1ImageDecoder.GetImageData (cognitive 16) Legacy/SplushWave/ArcDAT.cs:176 — Swg1ImageDecoder.GetImageData has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · TpgfReader.InitTransformMap (cognitive 16) · ×1
  • TpgfReader.InitTransformMap (cognitive 16) Legacy/Types/ImageTPGF.cs:226 — TpgfReader.InitTransformMap has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CtfReader.UnpackRle (cognitive 16) · ×1
  • CtfReader.UnpackRle (cognitive 16) Legacy/Unknown/ImageCTF.cs:139 — CtfReader.UnpackRle has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CgdImageDecoder.UnpackBlocks (cognitive 16) · ×1
  • CgdImageDecoder.UnpackBlocks (cognitive 16) Legacy/Rain/ArcBIN.cs:153 — CgdImageDecoder.UnpackBlocks has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (6 members, 12 shared lines) · ×1
  • Near-duplicate member family (6 members, 12 shared lines) ArcFormats/AnimeGameSystem/ArcDAT.cs:49 — ArcFormats/AnimeGameSystem/ArcDAT.cs:49-79 | ArcFormats/Basil/ArcMIF.cs:43-62 | ArcFormats/BlueGale/ArcSNN.cs:43-72 | ArcFormats/Ffa/ArcFFA.cs:50-82 | ArcFormats/Ucom/ArcDATA.cs:49-81 | ArcFormats/Ucom/ArcUK.cs:48-69 — These 6 members are variants of one another: a block of 12 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 18 shared lines) · ×1
  • Near-duplicate member family (4 members, 18 shared lines) ArcFormats/Ffa/AudioWA1.cs:124 — ArcFormats/Ffa/AudioWA1.cs:124-275 | ArcFormats/Ffa/AudioWA1.cs:278-335 | ArcFormats/Ffa/AudioWA1.cs:338-401 | ArcFormats/Ffa/AudioWA1.cs:404-556 — These 4 members are variants of one another: a block of 18 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 15 shared lines) · ×1
  • Near-duplicate member family (4 members, 15 shared lines) Legacy/Harvest/ArcDAT.cs:43 — Legacy/Harvest/ArcDAT.cs:43-63 | Legacy/Iris/ArcFPACK.cs:45-70 | Legacy/Mink/ArcBINZ.cs:44-66 | Legacy/Mutation/ArcDPF.cs:45-64 — These 4 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 14 shared lines) · ×1
  • Near-duplicate member family (4 members, 14 shared lines) ArcFormats/Aims/ArcPACK.cs:67 — ArcFormats/Aims/ArcPACK.cs:67-86 | ArcFormats/Basil/ArcMIF.cs:43-62 | ArcFormats/Ipac/ArcIPAC.cs:43-62 | ArcFormats/SoftwareHouseParsley/ArcPAC.cs:43-62 — These 4 members are variants of one another: a block of 14 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member pair (109 shared lines) · ×1
  • Near-duplicate member pair (109 shared lines) ArcFormats/Lucifen/ImageELG.cs:250 — ArcFormats/Lucifen/ImageELG.cs:250-373 | ArcFormats/Lucifen/ImageELG.cs:461-583 — These two members are variants of one another: 109 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) ArcFormats/WildBug/ImageWBM.cs:318 — ArcFormats/WildBug/ImageWBM.cs:318-398 | ArcFormats/WildBug/ImageWBM.cs:401-471 | ArcFormats/WildBug/ImageWBM.cs:529-638 | ArcFormats/WildBug/ImageWBM.cs:641-716 | ArcFormats/WildBug/ImageWBM.cs:719-817 | ArcFormats/WildBug/ImageWBM.cs:820-883 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Edited copy of a member (189 corresponding lines) · ×1
  • Edited copy of a member (189 corresponding lines) ArcFormats/Entis/MioDecoder.cs:293 — ArcFormats/Entis/MioDecoder.cs:293-511 | ArcFormats/Entis/MioDecoder.cs:586-774 — These two members are one piece of code written twice and then edited apart: 189 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (115 corresponding lines) · ×1
  • Edited copy of a member (115 corresponding lines) ArcFormats/KiriKiri/ImageTLG.cs:873 — ArcFormats/KiriKiri/ImageTLG.cs:873-988 | ArcFormats/KiriKiri/ImageTLG.cs:991-1105 — These two members are one piece of code written twice and then edited apart: 115 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (94 corresponding lines) · ×1
  • Edited copy of a member (94 corresponding lines) Legacy/System98/ImageG.cs:116 — Legacy/System98/ImageG.cs:116-221 | Legacy/Ucom/ImageUG.cs:103-196 — These two members are one piece of code written twice and then edited apart: 94 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (80 corresponding lines) · ×1
  • Edited copy of a member (80 corresponding lines) ArcFormats/Circus/ImageCRX.cs:317 — ArcFormats/Circus/ImageCRX.cs:317-396 | ArcFormats/Circus/ImageCRX.cs:503-608 — These two members are one piece of code written twice and then edited apart: 80 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (73 corresponding lines) · ×1
  • Edited copy of a member (73 corresponding lines) ArcFormats/ShiinaRio/ImageMI4.cs:151 — ArcFormats/ShiinaRio/ImageMI4.cs:151-223 | ArcFormats/ShiinaRio/ImageMI4.cs:226-313 — These two members are one piece of code written twice and then edited apart: 73 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (79 corresponding lines) · ×1
  • Edited copy of a member (79 corresponding lines) ArcFormats/Seraphim/ImageSeraph.cs:288 — ArcFormats/Seraphim/ImageSeraph.cs:288-366 | ArcFormats/Seraphim/ImageSeraph.cs:369-466 — These two members are one piece of code written twice and then edited apart: 79 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (71 corresponding lines) · ×1
  • Edited copy of a member (71 corresponding lines) ArcFormats/Lucifen/ImageELG.cs:177 — ArcFormats/Lucifen/ImageELG.cs:177-247 | ArcFormats/Lucifen/ImageELG.cs:376-458 — These two members are one piece of code written twice and then edited apart: 71 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (56 corresponding lines) · ×1
  • Edited copy of a member (56 corresponding lines) Experimental/Microsoft/ArcEXE.cs:162 — Experimental/Microsoft/ArcEXE.cs:162-227 | Experimental/Microsoft/ArcNE.cs:120-175 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 72+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 72+ corresponding lines) ArcFormats/CatSystem/ArcINT.cs:289 — ArcFormats/CatSystem/ArcINT.cs:289-362 | ArcFormats/FlyingShine/ArcPD.cs:106-193 | ArcFormats/Liar/ArcXFL.cs:102-173 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 72 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (75 corresponding lines) · ×1
  • Edited copy of a member (75 corresponding lines) ArcFormats/Silky/ImageMSK.cs:106 — ArcFormats/Silky/ImageMSK.cs:106-180 | ArcFormats/Silky/ImageMSK.cs:183-257 — These two members are one piece of code written twice and then edited apart: 75 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (69 corresponding lines) · ×1
  • Edited copy of a member (69 corresponding lines) ArcFormats/Leaf/ArcPAK.cs:171 — ArcFormats/Leaf/ArcPAK.cs:171-239 | ArcFormats/Leaf/ArcLAC.cs:160-242 — These two members are one piece of code written twice and then edited apart: 69 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (53 corresponding lines) · ×1
  • Edited copy of a member (53 corresponding lines) ArcFormats/WildBug/ImageWBM.cs:474 — ArcFormats/WildBug/ImageWBM.cs:474-526 | ArcFormats/WildBug/ImageWBM.cs:886-966 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×1
  • Edited copy of a member (40 corresponding lines) ArcFormats/Entis/MioDecoder.cs:777 — ArcFormats/Entis/MioDecoder.cs:777-816 | ArcFormats/Entis/MioDecoder.cs:869-921 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) ArcFormats/Entis/EriReader.cs:1315 — ArcFormats/Entis/EriReader.cs:1315-1358 | ArcFormats/Entis/EriReader.cs:1361-1408 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (51 corresponding lines) · ×1
  • Edited copy of a member (51 corresponding lines) ArcFormats/WildBug/AudioWWA.cs:124 — ArcFormats/WildBug/AudioWWA.cs:124-188 | ArcFormats/WildBug/AudioWWA.cs:191-241 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 31+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 31+ corresponding lines) ArcFormats/KScript/ArcKPC.cs:42 — ArcFormats/KScript/ArcKPC.cs:42-72 | ArcFormats/Nags/ArcNFS.cs:45-80 | ArcFormats/Propeller/ArcMPK.cs:44-75 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 22+ corresponding lines) Legacy/Adviz/ImageGIZ.cs:154 — Legacy/Adviz/ImageGIZ.cs:154-175 | Legacy/Adviz/ImageGIZ2.cs:194-215 | Legacy/AyPio/ImagePDT.cs:166-188 | Legacy/Discovery/ImagePR1.cs:306-327 | Legacy/Miami/ImageMIA.cs:244-272 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) ArcFormats/Ffa/ImagePT1.cs:539 — ArcFormats/Ffa/ImagePT1.cs:539-580 | ArcFormats/Ffa/ImagePT1.cs:583-620 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 26+ corresponding lines) ArcFormats/Cmvs/ArcCPZ1.cs:48 — ArcFormats/Cmvs/ArcCPZ1.cs:48-73 | ArcFormats/Cmvs/ArcPBZ.cs:79-111 | ArcFormats/Morning/ArcTTD.cs:44-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 27+ corresponding lines) ArcFormats/Cherry/ArcMyk.cs:47 — ArcFormats/Cherry/ArcMyk.cs:47-76 | ArcFormats/Interheart/ArcFPK2.cs:43-69 | ArcFormats/Silky/ArcAWF.cs:44-73 | Legacy/Unison/ArcVCT.cs:46-77 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) ArcFormats/Tail/ArcCAF.cs:196 — ArcFormats/Tail/ArcCAF.cs:196-233 | Legacy/Sophia/ArcNOR.cs:102-138 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 40+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 40+ corresponding lines) ArcFormats/BellDa/ImageCP.cs:84 — ArcFormats/BellDa/ImageCP.cs:84-125 | REDACTED:340-379 | Legacy/ProjectMyu/ImageGAM.cs:78-124 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 40 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×1
  • Edited copy of a member (45 corresponding lines) ArcFormats/Majiro/ImageRC8.cs:109 — ArcFormats/Majiro/ImageRC8.cs:109-153 | ArcFormats/Majiro/ImageRCT.cs:632-676 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 25+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 25+ corresponding lines) ArcFormats/Abogado/ArcPAK.cs:51 — ArcFormats/Abogado/ArcPAK.cs:51-78 | ArcFormats/Nekopunch/ArcPAK.cs:48-72 | ArcFormats/Slg/ArcSZS.cs:43-69 | ArcFormats/SoftwareHouseParsley/ArcCG.cs:52-81 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 23+ corresponding lines) ArcFormats/Maika/ArcMIK01.cs:48 — ArcFormats/Maika/ArcMIK01.cs:48-70 | ArcFormats/SysD/ArcDPK.cs:41-66 | REDACTED:56-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 36+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 36+ corresponding lines) ArcFormats/GLib/ArcG.cs:113 — ArcFormats/GLib/ArcG.cs:113-154 | ArcFormats/GameSystem/ArcPureMail.cs:105-142 | ArcFormats/Sohfu/ArcSKA.cs:96-137 | ArcFormats/TanukiSoft/ImageAF.cs:68-109 | Legacy/Dice/ArcRLZ.cs:84-119 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 27+ corresponding lines) ArcFormats/SuperNekoX/ArcGPC.cs:219 — ArcFormats/SuperNekoX/ArcGPC.cs:219-246 | ArcFormats/TopCat/ArcTCD3.cs:193-219 | Legacy/Sogna/ArcSGS.cs:84-111 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) ArcFormats/LiveMaker/ImageGAL.cs:463 — ArcFormats/LiveMaker/ImageGAL.cs:463-482 | ArcFormats/LiveMaker/ImageGAL.cs:485-502 | ArcFormats/LiveMaker/ImageGAL.cs:525-542 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) ArcFormats/LightVN/ArcVNDAT.cs:71 — ArcFormats/LightVN/ArcVNDAT.cs:71-88 | ArcFormats/PkWare/ArcZIP.cs:128-145 | ArcFormats/VnMaker/ArcZIP.cs:104-118 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 29+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 29+ corresponding lines) ArcFormats/Blowfish.cs:350 — ArcFormats/Blowfish.cs:350-378 | ArcFormats/Blowfish.cs:414-444 | ArcFormats/aNCHOR/Blowfish.cs:149-177 | ArcFormats/aNCHOR/Blowfish.cs:185-215 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 17+ corresponding lines) Legacy/Mapl/ImageMI2.cs:230 — Legacy/Mapl/ImageMI2.cs:230-246 | Legacy/Mapl/ImageMI2.cs:249-266 | Legacy/Mapl/ImageMI2.cs:385-403 | Legacy/Mapl/ImageMI2.cs:406-423 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 9+ corresponding lines) ArcFormats/GameSystem/ArcCMP.cs:137 — ArcFormats/GameSystem/ArcCMP.cs:137-147 | ArcFormats/Kaguya/ArcLIN2.cs:80-91 | ArcFormats/Leaf/ArcPAK.cs:131-139 | ArcFormats/VnSystem/ArcVFS.cs:70-81 | Legacy/Pinpai/ArcARC.cs:74-82 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 11+ corresponding lines) ArcFormats/GameSystem/ArcPureMail.cs:86 — ArcFormats/GameSystem/ArcPureMail.cs:86-102 | Legacy/Sogna/ArcSGS.cs:71-81 | Legacy/UMeSoft/ArcBIN.cs:89-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 13+ corresponding lines) ArcFormats/Gpk2/ImageGFB.cs:117 — ArcFormats/Gpk2/ImageGFB.cs:117-130 | ArcFormats/Ikura/ImageVRS.cs:118-130 | ArcFormats/Interheart/ImageCandy.cs:265-277 | ArcFormats/Sas5/ImageIAR.cs:113-126 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 8+ corresponding lines) ArcFormats/Abel/ArcARC.cs:99 — ArcFormats/Abel/ArcARC.cs:99-106 | ArcFormats/BlackRainbow/ArcDX.cs:62-69 | ArcFormats/BlackRainbow/ArcSPPAK.cs:93-102 | ArcFormats/Marble/ArcDNS.cs:73-80 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) ArcFormats/BitStream.cs:90 — ArcFormats/BitStream.cs:90-103 | ArcFormats/Cri/AudioHCA.cs:1178-1189 | ArcFormats/RiddleSoft/ImageGCP.cs:170-184 | ArcFormats/TopCat/ImageSPD.cs:381-395 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 11+ corresponding lines) ArcFormats/Ail/ArcAil.cs:60 — ArcFormats/Ail/ArcAil.cs:60-71 | ArcFormats/Kaguya/ArcAN21.cs:130-140 | ArcFormats/Kaguya/ArcPL10.cs:112-122 | Legacy/Dice/ArcRLZ.cs:70-81 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 14+ corresponding lines) ArcFormats/uGOS/ImageBMP.cs:53 — ArcFormats/uGOS/ImageBMP.cs:53-70 | Legacy/Mink/ImageFC.cs:56-72 | Legacy/Mink/ImageFD.cs:46-59 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 6+ corresponding lines) ArcFormats/CommonStreams.cs:571 — ArcFormats/CommonStreams.cs:571-578 | ArcFormats/Hexenhaus/ArcWAG.cs:131-136 | ArcFormats/Musica/ArcPAK.cs:130-137 | ArcFormats/YuukiNovel/ArcYuuki.cs:136-143 | Legacy/Uran/ArcNCL.cs:117-124 | Legacy/Yaneurao/ImageGTO.cs:83-90 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 5+ corresponding lines) ArcFormats/DigitalWorks/ImageTM2.cs:96 — ArcFormats/DigitalWorks/ImageTM2.cs:96-100 | ArcFormats/Ikura/ImageTAN.cs:66-70 | ArcFormats/Lambda/ImageCLS.cs:87-91 | ArcFormats/Macintosh/ImagePICT.cs:81-85 | ArcFormats/Strikes/ImageLAG.cs:72-76 | Legacy/DigitalMonkey/ImagePKT.cs:78-82 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 5+ corresponding lines) ArcFormats/Cadath/ImageCGF.cs:63 — ArcFormats/Cadath/ImageCGF.cs:63-67 | ArcFormats/Cri/ImageXTX.cs:89-93 | ArcFormats/Eternity/ImageSGF.cs:73-77 | ArcFormats/Ikura/ImageGGS.cs:53-57 | ArcFormats/Sviu/ImageGBP.cs:74-78 | ArcFormats/Zyx/ImageMTL.cs:70-74 | Legacy/Acme/ImagePMG.cs:68-72 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 5+ corresponding lines) ArcFormats/Masys/ImageAG.cs:53 — ArcFormats/Masys/ImageAG.cs:53-57 | ArcFormats/Tmr-Hiro/ImageGRD.cs:89-94 | ArcFormats/YuRis/ImageYDG.cs:81-86 | ArcFormats/elf/ImageGCC.cs:70-75 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 6+ corresponding lines) ArcFormats/AnimeGameSystem/ArcDAT.cs:111 — ArcFormats/AnimeGameSystem/ArcDAT.cs:111-116 | ArcFormats/DxLib/ArcMED.cs:183-188 | ArcFormats/KiriKiri/ArcXP3.cs:445-450 | ArcFormats/Selene/ArcKCAP.cs:131-136 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (61 lines × 2) · ×1
  • Duplicated block (61 lines × 2) ArcFormats/ScrPlayer/ImageIMG.cs:117 — ArcFormats/ScrPlayer/ImageIMG.cs:117-177 | ArcFormats/ScrPlayer/ImageIMG.cs:209-269 — 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 `ArcFormats/ScrPlayer/ImageIMG.cs:117` 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.
D4 · Code Duplication · Duplicated block (55 lines × 2) · ×1
  • Duplicated block (55 lines × 2) ArcFormats/Lucifen/ImageELG.cs:292 — ArcFormats/Lucifen/ImageELG.cs:292-346 | ArcFormats/Lucifen/ImageELG.cs:500-554 — 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 `ArcFormats/Lucifen/ImageELG.cs:292` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (52 lines × 2) · ×1
  • Duplicated block (52 lines × 2) ArcFormats/Kid/ArcDAT.cs:102 — ArcFormats/Kid/ArcDAT.cs:102-153 | ArcFormats/Kid/ArcDATRAW.cs:93-144 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (42 lines × 2) · ×1
  • Duplicated block (42 lines × 2) Legacy/System98/ImageG.cs:180 — Legacy/System98/ImageG.cs:180-221 | Legacy/Ucom/ImageUG.cs:155-196 — 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 `Legacy/System98/ImageG.cs:180` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (40–41 lines × 2) · ×1
  • Duplicated block (40–41 lines × 2) ArcFormats/Entis/MioDecoder.cs:356 — ArcFormats/Entis/MioDecoder.cs:356-396 | ArcFormats/Entis/MioDecoder.cs:654-693 — 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 `ArcFormats/Entis/MioDecoder.cs:356` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) ArcFormats/StudioJikkenshitsu/SjTransform.cs:253 — ArcFormats/StudioJikkenshitsu/SjTransform.cs:253-292 | ArcFormats/StudioJikkenshitsu/SjTransform.cs:293-332 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) ArcFormats/Kaguya/ArcAN21.cs:152 — ArcFormats/Kaguya/ArcAN21.cs:152-184 | ArcFormats/Kaguya/ArcPL10.cs:134-166 — before extracting anything, compare `ArcFormats/Kaguya/ArcAN21.cs` and `ArcFormats/Kaguya/ArcPL10.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) ArcFormats/Cmvs/ImagePB3.cs:112 — ArcFormats/Cmvs/ImagePB3.cs:112-145 | ArcFormats/Cmvs/ImagePSB.cs:259-292 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cmvs/ImagePSB.cs:259` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (29–34 lines × 2) · ×1
  • Duplicated block (29–34 lines × 2) ArcFormats/Entis/EriReader.cs:1323 — ArcFormats/Entis/EriReader.cs:1323-1351 | ArcFormats/Entis/EriReader.cs:1367-1400 — 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 `ArcFormats/Entis/EriReader.cs:1323` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) ArcFormats/WildBug/ImageWBM.cs:367 — ArcFormats/WildBug/ImageWBM.cs:367-398 | ArcFormats/WildBug/ImageWBM.cs:440-471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/WildBug/ImageWBM.cs:367` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) ArcFormats/Entis/EriReader.cs:2520 — ArcFormats/Entis/EriReader.cs:2520-2548 | ArcFormats/Entis/EriReader.cs:2560-2588 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (30 lines × 3) · ×1
  • Duplicated block (30 lines × 3) ArcFormats/Ffa/AudioWA1.cs:239 — ArcFormats/Ffa/AudioWA1.cs:239-268 | ArcFormats/Ffa/AudioWA1.cs:299-328 | ArcFormats/Ffa/AudioWA1.cs:363-392 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (12–29 lines × 4) · ×1
  • Duplicated block (12–29 lines × 4) ArcFormats/Ffa/ImagePT1.cs:421 — ArcFormats/Ffa/ImagePT1.cs:421-449 | ArcFormats/Ffa/ImagePT1.cs:455-466 | ArcFormats/Ffa/ImagePT1.cs:467-495 | ArcFormats/Ffa/ImagePT1.cs:497-525 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Ffa/ImagePT1.cs:421` 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.
D4 · Code Duplication · Duplicated block (23 lines × 3) · ×1
  • Duplicated block (23 lines × 3) ArcFormats/WildBug/ImageWBM.cs:348 — ArcFormats/WildBug/ImageWBM.cs:348-370 | ArcFormats/WildBug/ImageWBM.cs:559-581 | ArcFormats/WildBug/ImageWBM.cs:672-694 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/WildBug/ImageWBM.cs:348` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×1
  • Duplicated block (25 lines × 3) ArcFormats/WildBug/ImageWBM.cs:475 — ArcFormats/WildBug/ImageWBM.cs:475-499 | ArcFormats/WildBug/ImageWBM.cs:887-911 | ArcFormats/WildBug/ImageWBM.cs:970-994 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/WildBug/ImageWBM.cs:475` 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.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) ArcFormats/Leaf/ArcLAC.cs:169 — ArcFormats/Leaf/ArcLAC.cs:169-191 | ArcFormats/Leaf/ArcPAK.cs:179-201 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Leaf/ArcLAC.cs:169` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22–24 lines × 2) · ×1
  • Duplicated block (22–24 lines × 2) ArcFormats/Silky/ImageMSK.cs:144 — ArcFormats/Silky/ImageMSK.cs:144-165 | ArcFormats/Silky/ImageMSK.cs:222-245 — 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 `ArcFormats/Silky/ImageMSK.cs:144` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×1
  • Duplicated block (20 lines × 3) ArcFormats/Kaguya/ArcANM.cs:189 — ArcFormats/Kaguya/ArcANM.cs:189-208 | ArcFormats/Kaguya/ArcANM.cs:254-273 | ArcFormats/Kaguya/ArcPLT.cs:54-73 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Kaguya/ArcANM.cs:189` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×1
  • Duplicated block (20–21 lines × 2) ArcFormats/Lucifen/ImageELG.cs:250 — ArcFormats/Lucifen/ImageELG.cs:250-270 | ArcFormats/Lucifen/ImageELG.cs:461-480 — 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 `ArcFormats/Lucifen/ImageELG.cs:250` 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.
D4 · Code Duplication · Duplicated block (18–19 lines × 4) · ×1
  • Duplicated block (18–19 lines × 4) ArcFormats/Ffa/AudioWA1.cs:257 — ArcFormats/Ffa/AudioWA1.cs:257-274 | ArcFormats/Ffa/AudioWA1.cs:317-334 | ArcFormats/Ffa/AudioWA1.cs:380-398 | ArcFormats/Ffa/AudioWA1.cs:535-553 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Ffa/AudioWA1.cs:257` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17–18 lines × 6) · ×1
  • Duplicated block (17–18 lines × 6) ArcFormats/WildBug/ImageWBM.cs:320 — ArcFormats/WildBug/ImageWBM.cs:320-336 | ArcFormats/WildBug/ImageWBM.cs:403-419 | ArcFormats/WildBug/ImageWBM.cs:531-547 | ArcFormats/WildBug/ImageWBM.cs:643-659 | ArcFormats/WildBug/ImageWBM.cs:720-737 | ArcFormats/WildBug/ImageWBM.cs:821-837 — all 6 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.
D4 · Code Duplication · Duplicated block (14–17 lines × 2) · ×1
  • Duplicated block (14–17 lines × 2) Legacy/Rare/ArcX.cs:69 — Legacy/Rare/ArcX.cs:69-85 | Legacy/SystemAqua/ArcDAT.cs:56-69 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Legacy/SystemAqua/ArcDAT.cs:70` calls `DetectFileTypes` and `Legacy/Rare/ArcX.cs:86` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13–16 lines × 7) · ×1
  • Duplicated block (13–16 lines × 7) ArcFormats/Antique/ArcDAT.cs:46 — ArcFormats/Antique/ArcDAT.cs:46-58 | ArcFormats/Aoi/ArcBOX.cs:168-182 | ArcFormats/Lambda/ArcCLS.cs:49-62 | ArcFormats/MicroVision/ArcGSD.cs:48-62 | ArcFormats/Musica/ArcSQZ.cs:70-84 | ArcFormats/Tanaka/ArcSMV.cs:60-75 | ArcFormats/Valkyria/ArcAM2.cs:51-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Antique/ArcDAT.cs:45` calls `ReadUInt32` and `ArcFormats/Aoi/ArcBOX.cs:167` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×1
  • Duplicated block (14–16 lines × 2) ArcFormats/DDSystem/ArcDDP.cs:162 — ArcFormats/DDSystem/ArcDDP.cs:162-177 | ArcFormats/SHSystem/ArcHXP.cs:154-167 — 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 `ArcFormats/DDSystem/ArcDDP.cs:162` 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.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) ArcFormats/Entis/ErisaMatrix.cs:417 — ArcFormats/Entis/ErisaMatrix.cs:417-432 | ArcFormats/Entis/ErisaMatrix.cs:441-455 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Entis/ErisaMatrix.cs:417` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (14–15 lines × 4) · ×1
  • Duplicated block (14–15 lines × 4) ArcFormats/Sas5/ArcWAR.cs:169 — ArcFormats/Sas5/ArcWAR.cs:169-183 | Legacy/KApp/ArcASD.cs:50-63 | Legacy/Pearl/ArcARY.cs:61-74 | Legacy/Weapon/ArcVoice.cs:58-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Legacy/KApp/ArcASD.cs:64` calls `DetectFileTypes` and `ArcFormats/Sas5/ArcWAR.cs:184` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) ArcFormats/Maika/ArcMK2.cs:217 — ArcFormats/Maika/ArcMK2.cs:217-231 | Legacy/Eve/ArcGM.cs:143-157 | Legacy/Inspire/ArcIDA.cs:210-224 — 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 `ArcFormats/Maika/ArcMK2.cs:217` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–14 lines × 5) · ×1
  • Duplicated block (12–14 lines × 5) ArcFormats/Antique/ArcDAT.cs:46 — ArcFormats/Antique/ArcDAT.cs:46-57 | ArcFormats/Aoi/ArcBOX.cs:168-181 | ArcFormats/MicroVision/ArcGSD.cs:48-61 | ArcFormats/Musica/ArcSQZ.cs:70-83 | ArcFormats/Seraphim/ArcMC.cs:52-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Antique/ArcDAT.cs:46` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Antique/ArcDAT.cs:45` calls `ReadUInt32` and `ArcFormats/Aoi/ArcBOX.cs:167` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) ArcFormats/DigitalWorks/ArcPAC.cs:76 — ArcFormats/DigitalWorks/ArcPAC.cs:76-88 | ArcFormats/DigitalWorks/ArcPACPS2.cs:75-87 | ArcFormats/DigitalWorks/ArcPACsingle.cs:65-77 — before extracting anything, compare `ArcFormats/DigitalWorks/ArcPACPS2.cs` and `ArcFormats/DigitalWorks/ArcPACsingle.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) ArcFormats/Youkai/ArcDAT.cs:52 — ArcFormats/Youkai/ArcDAT.cs:52-65 | ArcFormats/Youkai/ArcDAT.cs:185-197 — 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 `ArcFormats/Youkai/ArcDAT.cs:52` 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.
D4 · Code Duplication · Duplicated block (11–13 lines × 4) · ×1
  • Duplicated block (11–13 lines × 4) ArcFormats/ScrPlayer/ImageI.cs:150 — ArcFormats/ScrPlayer/ImageI.cs:150-161 | ArcFormats/ScrPlayer/ImageI.cs:210-222 | ArcFormats/ScrPlayer/ImageIMG.cs:115-125 | ArcFormats/ScrPlayer/ImageIMG.cs:207-217 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (11–12 lines × 3) · ×1
  • Duplicated block (11–12 lines × 3) ArcFormats/Lucifen/ImageELG.cs:257 — ArcFormats/Lucifen/ImageELG.cs:257-268 | ArcFormats/Lucifen/ImageELG.cs:384-395 | ArcFormats/Lucifen/ImageELG.cs:468-478 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Lucifen/ImageELG.cs:257` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10–11 lines × 6) · ×1
  • Duplicated block (10–11 lines × 6) ArcFormats/Carriere/ArcARC.cs:45 — ArcFormats/Carriere/ArcARC.cs:45-54 | ArcFormats/Cyberworks/ArcP8.cs:42-52 | ArcFormats/EntExec/ArcCAB.cs:42-52 | ArcFormats/Nexas/ArcTPF.cs:51-61 | ArcFormats/Slg/ArcSZS.cs:45-55 | ArcFormats/Taskforce/ArcDAT.cs:44-54 — before extracting anything, compare `ArcFormats/Carriere/ArcARC.cs` and `ArcFormats/Taskforce/ArcDAT.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Carriere/ArcARC.cs:45` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Cyberworks/ArcP8.cs:53` calls `IsNullOrEmpty` and `ArcFormats/Carriere/ArcARC.cs:55` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10–11 lines × 3) · ×1
  • Duplicated block (10–11 lines × 3) ArcFormats/Leaf/ArcA.cs:70 — ArcFormats/Leaf/ArcA.cs:70-79 | ArcFormats/MOONSTONE/ArcPAK.cs:57-67 | Legacy/PenguinWorks/ArcDAT.cs:52-61 — 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 `ArcFormats/Leaf/ArcA.cs:70` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7–11 lines × 2) · ×1
  • Duplicated block (7–11 lines × 2) Legacy/Pearl/ImagePL4.cs:175 — Legacy/Pearl/ImagePL4.cs:175-181 | Legacy/Pearl/ImagePL4.cs:282-292 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (9–10 lines × 9) · ×1
  • Duplicated block (9–10 lines × 9) ArcFormats/Aims/ArcPACK.cs:67 — ArcFormats/Aims/ArcPACK.cs:67-76 | ArcFormats/ArcARCX.cs:48-57 | ArcFormats/Basil/ArcMIF.cs:43-52 | ArcFormats/Bishop/ArcPK.cs:43-52 | ArcFormats/Cadath/ArcKAR.cs:48-57 | ArcFormats/Leaf/ArcLAC.cs:46-55 | ArcFormats/NitroPlus/ArcNPP.cs:43-51 | ArcFormats/RealLive/ArcSEEN.cs:49-58 | ArcFormats/SoftwareHouseParsley/ArcPAC.cs:43-52 — before extracting anything, compare `ArcFormats/Aims/ArcPACK.cs` and `ArcFormats/Basil/ArcMIF.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Aims/ArcPACK.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Leaf/ArcLAC.cs:56` calls `IsNullOrEmpty` and `ArcFormats/ArcARCX.cs:58` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–10 lines × 7) · ×1
  • Duplicated block (9–10 lines × 7) ArcFormats/Cyberworks/ArcP8.cs:42 — ArcFormats/Cyberworks/ArcP8.cs:42-51 | ArcFormats/EntExec/ArcCAB.cs:42-51 | ArcFormats/Kitsunemimi/ArcPAK.cs:43-52 | ArcFormats/Nexas/ArcTPF.cs:51-60 | ArcFormats/Slg/ArcSZS.cs:45-54 | ArcFormats/Taskforce/ArcDAT.cs:44-53 | ArcFormats/Youkai/ArcDAT.cs:138-146 — before extracting anything, compare `ArcFormats/Cyberworks/ArcP8.cs` and `ArcFormats/EntExec/ArcCAB.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Cyberworks/ArcP8.cs:42` 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 5) · ×1
  • Duplicated block (9–10 lines × 5) ArcFormats/Aims/ArcPACK.cs:68 — ArcFormats/Aims/ArcPACK.cs:68-77 | ArcFormats/Carriere/ArcARC.cs:47-55 | ArcFormats/Ipac/ArcIPAC.cs:44-53 | ArcFormats/RealLive/ArcSEEN.cs:50-59 | ArcFormats/Taskforce/ArcDAT.cs:46-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Aims/ArcPACK.cs:68` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/Carriere/ArcARC.cs:45` calls `ReadUInt32` and `ArcFormats/RealLive/ArcSEEN.cs:49` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–10 lines × 4) · ×1
  • Duplicated block (9–10 lines × 4) Legacy/AdvS/ArcDAT.cs:43 — Legacy/AdvS/ArcDAT.cs:43-52 | Legacy/Jupiter/ArcLB5.cs:50-58 | Legacy/Logg/ArcARF.cs:46-55 | Legacy/Witch/ArcDAT.cs:41-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/AdvS/ArcDAT.cs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) Legacy/Asura/ArcPAK.cs:49 — Legacy/Asura/ArcPAK.cs:49-59 | Legacy/Harvest/ArcDAT.cs:44-53 | Legacy/Sogna/ArcSGS.cs:46-56 | Legacy/Yaneurao/ArcDAT.cs:111-120 — before extracting anything, compare `Legacy/Asura/ArcPAK.cs` and `Legacy/Yaneurao/ArcDAT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Asura/ArcPAK.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9–10 lines × 3) · ×1
  • Duplicated block (9–10 lines × 3) Legacy/AdvS/ArcDAT.cs:44 — Legacy/AdvS/ArcDAT.cs:44-53 | Legacy/Jupiter/ArcLB5.cs:51-59 | Legacy/Nyoken/ArcZLK.cs:47-56 — 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 `Legacy/AdvS/ArcDAT.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Nyoken/ArcZLK.cs:44` calls `ReadInt32` and `Legacy/AdvS/ArcDAT.cs:43` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×1
  • Duplicated block (8–10 lines × 2) ArcFormats/Crowd/ImageGAX.cs:131 — ArcFormats/Crowd/ImageGAX.cs:131-140 | ArcFormats/Crowd/ImageGAX.cs:147-154 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (5 lines × 25) · ×1
  • Duplicated block (5 lines × 25) ArcFormats/Aims/ArcPACK.cs:80 — ArcFormats/Aims/ArcPACK.cs:80-84 | ArcFormats/Basil/ArcMIF.cs:56-60 | ArcFormats/BlueGale/ArcSNN.cs:65-69 | ArcFormats/Circus/ArcPCK.cs:70-74 | ArcFormats/Favorite/ArcFVP.cs:67-71 | ArcFormats/Ffa/ArcBlackPackage.cs:68-72 | ArcFormats/Ffa/ArcFFA.cs:76-80 | ArcFormats/Ipac/ArcIPAC.cs:56-60 | ArcFormats/Irrlicht/ArcARK.cs:66-70 | ArcFormats/MangaGamer/ArcSHA.cs:55-59 | ArcFormats/Silky/ArcAWF.cs:67-71 | ArcFormats/Silky/ArcIFL.cs:60-64 | ArcFormats/SoftwareHouseParsley/ArcCG.cs:75-79 | ArcFormats/SoftwareHouseParsley/ArcPAC.cs:56-60 | ArcFormats/Sohfu/ArcSKA.cs:67-71 | ArcFormats/Ucom/ArcDATA.cs:74-78 | ArcFormats/Ucom/ArcUK.cs:63-67 | Legacy/Brownie/ArcNAF.cs:61-65 | Legacy/Gsx/ArcK5.cs:62-66 | Legacy/Harvest/ArcDAT.cs:57-61 | Legacy/Iris/ArcFPACK.cs:64-68 | Legacy/Mink/ArcMINK.cs:67-71 | Legacy/Mutation/ArcDPF.cs:58-62 | Legacy/PenguinWorks/ArcPAC.cs:72-76 | Legacy/Unison/ArcVCT.cs:71-75 — before extracting anything, compare `ArcFormats/Aims/ArcPACK.cs` and `ArcFormats/Basil/ArcMIF.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Aims/ArcPACK.cs:80` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7 lines × 25) · ×1
  • Duplicated block (7 lines × 25) ArcFormats/Basil/ArcMIF.cs:56 — ArcFormats/Basil/ArcMIF.cs:56-62 | ArcFormats/BlueGale/ArcSNN.cs:65-71 | ArcFormats/Circus/ArcPCK.cs:70-76 | ArcFormats/Favorite/ArcFVP.cs:67-73 | ArcFormats/Ffa/ArcBlackPackage.cs:68-74 | ArcFormats/Ffa/ArcFFA.cs:76-82 | ArcFormats/Ipac/ArcIPAC.cs:56-62 | ArcFormats/Irrlicht/ArcARK.cs:66-72 | ArcFormats/MangaGamer/ArcSHA.cs:55-61 | ArcFormats/Silky/ArcAWF.cs:67-73 | ArcFormats/Silky/ArcIFL.cs:60-66 | ArcFormats/SoftwareHouseParsley/ArcCG.cs:75-81 | ArcFormats/SoftwareHouseParsley/ArcPAC.cs:56-62 | ArcFormats/Sohfu/ArcSKA.cs:67-73 | ArcFormats/Ucom/ArcDATA.cs:74-80 | ArcFormats/Ucom/ArcUK.cs:63-69 | Legacy/Brownie/ArcNAF.cs:61-67 | Legacy/Gsx/ArcK5.cs:62-68 | Legacy/Harvest/ArcDAT.cs:57-63 | Legacy/Iris/ArcFPACK.cs:64-70 | Legacy/Mink/ArcBINZ.cs:60-66 | Legacy/Mink/ArcMINK.cs:67-73 | Legacy/Mutation/ArcDPF.cs:58-64 | Legacy/PenguinWorks/ArcPAC.cs:72-78 | Legacy/Unison/ArcVCT.cs:71-77 — before extracting anything, compare `ArcFormats/Basil/ArcMIF.cs` and `ArcFormats/SoftwareHouseParsley/ArcPAC.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Basil/ArcMIF.cs:56` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Mink/ArcBINZ.cs:57` calls `ReadUInt32` and `ArcFormats/Circus/ArcPCK.cs:67` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–9 lines × 9) · ×1
  • Duplicated block (8–9 lines × 9) ArcFormats/AdvSys/ArcAdvSysT.cs:57 — ArcFormats/AdvSys/ArcAdvSysT.cs:57-64 | ArcFormats/AdvSys/ArcGR2.cs:54-62 | ArcFormats/Basil/ArcMIF.cs:46-54 | ArcFormats/Cadath/ArcKAR.cs:51-59 | ArcFormats/Circus/ArcValkyrieComplex.cs:304-312 | ArcFormats/FC01/ArcMRG0.cs:47-54 | ArcFormats/Maika/ArcMIK01.cs:54-61 | ArcFormats/Ucom/ArcDATA.cs:64-72 | ArcFormats/Ucom/ArcUK.cs:53-61 — before extracting anything, compare `ArcFormats/Basil/ArcMIF.cs` and `ArcFormats/Cadath/ArcKAR.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/AdvSys/ArcAdvSysT.cs:57` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/AdvSys/ArcGR2.cs:54` calls `HasExtension` and `ArcFormats/FC01/ArcMRG0.cs:47` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–9 lines × 8) · ×1
  • Duplicated block (8–9 lines × 8) Legacy/Asura/ArcPAK.cs:51 — Legacy/Asura/ArcPAK.cs:51-59 | Legacy/Harvest/ArcDAT.cs:46-53 | Legacy/Iris/ArcFPACK.cs:50-58 | Legacy/Mink/ArcBINZ.cs:45-53 | Legacy/Mutation/ArcDPF.cs:46-54 | Legacy/Sogna/ArcSGS.cs:48-56 | Legacy/Yaneurao/ArcDAT.cs:63-70 | Legacy/Yaneurao/ArcDAT.cs:113-120 — before extracting anything, compare `Legacy/Asura/ArcPAK.cs` and `Legacy/Yaneurao/ArcDAT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Asura/ArcPAK.cs:51` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Asura/ArcPAK.cs:49` calls `AsciiEqual` and `Legacy/Mink/ArcBINZ.cs:44` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–9 lines × 6) · ×1
  • Duplicated block (8–9 lines × 6) Legacy/Asura/ArcPAK.cs:51 — Legacy/Asura/ArcPAK.cs:51-59 | Legacy/Harvest/ArcDAT.cs:46-53 | Legacy/Mink/ArcBINZ.cs:45-53 | Legacy/Rhss/ArcCRG.cs:44-51 | Legacy/Sogna/ArcSGS.cs:48-56 | Legacy/Yaneurao/ArcDAT.cs:113-120 — before extracting anything, compare `Legacy/Asura/ArcPAK.cs` and `Legacy/Yaneurao/ArcDAT.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Asura/ArcPAK.cs:51` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Asura/ArcPAK.cs:49` calls `AsciiEqual` and `Legacy/Mink/ArcBINZ.cs:44` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–9 lines × 5) · ×1
  • Duplicated block (8–9 lines × 5) Legacy/AdvS/ArcDAT.cs:44 — Legacy/AdvS/ArcDAT.cs:44-52 | Legacy/Jupiter/ArcLB5.cs:51-58 | Legacy/Logg/ArcARF.cs:47-55 | Legacy/Nyoken/ArcZLK.cs:47-55 | Legacy/Witch/ArcDAT.cs:42-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/AdvS/ArcDAT.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Nyoken/ArcZLK.cs:44` calls `ReadInt32` and `Legacy/AdvS/ArcDAT.cs:43` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–9 lines × 4) · ×1
  • Duplicated block (8–9 lines × 4) Legacy/Dice/ArcRLZ.cs:46 — Legacy/Dice/ArcRLZ.cs:46-54 | Legacy/Gsx/ArcK3.cs:46-53 | Legacy/Tigerman/ArcPAC.cs:50-58 | Legacy/Uran/ArcPHS.cs:44-52 — before extracting anything, compare `Legacy/Tigerman/ArcPAC.cs` and `Legacy/Uran/ArcPHS.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Legacy/Dice/ArcRLZ.cs:46` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Gsx/ArcK3.cs:44` calls `AsciiEqual` and `Legacy/Dice/ArcRLZ.cs:45` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 29) · ×1
  • Duplicated block (5 lines × 29) ArcFormats/Abogado/ArcPAK.cs:69 — ArcFormats/Abogado/ArcPAK.cs:69-73 | ArcFormats/Aims/ArcPACK.cs:80-84 | ArcFormats/AnimeGameSystem/ArcDAT.cs:65-69 | ArcFormats/Basil/ArcMIF.cs:56-60 | ArcFormats/BlueGale/ArcSNN.cs:65-69 | ArcFormats/Circus/ArcPCK.cs:70-74 | ArcFormats/Favorite/ArcFVP.cs:67-71 | ArcFormats/Ffa/ArcBlackPackage.cs:68-72 | ArcFormats/Ffa/ArcFFA.cs:76-80 | ArcFormats/Ikura/ArcDRS.cs:157-161 | ArcFormats/Ipac/ArcIPAC.cs:56-60 | ArcFormats/Irrlicht/ArcARK.cs:66-70 | ArcFormats/MangaGamer/ArcSHA.cs:55-59 | ArcFormats/Silky/ArcAWF.cs:67-71 | ArcFormats/Silky/ArcIFL.cs:60-64 | ArcFormats/SoftwareHouseParsley/ArcCG.cs:75-79 | ArcFormats/SoftwareHouseParsley/ArcPAC.cs:56-60 | ArcFormats/Sohfu/ArcSKA.cs:67-71 | ArcFormats/Ucom/ArcDATA.cs:74-78 | ArcFormats/Ucom/ArcUK.cs:63-67 | Legacy/Brownie/ArcNAF.cs:61-65 | Legacy/DMotion/ArcDM.cs:80-84 | Legacy/Gsx/ArcK5.cs:62-66 | Legacy/Harvest/ArcDAT.cs:57-61 | Legacy/Iris/ArcFPACK.cs:64-68 | Legacy/Mink/ArcMINK.cs:67-71 | Legacy/Mutation/ArcDPF.cs:58-62 | Legacy/PenguinWorks/ArcPAC.cs:72-76 | Legacy/Unison/ArcVCT.cs:71-75 — before extracting anything, compare `ArcFormats/Aims/ArcPACK.cs` and `ArcFormats/Basil/ArcMIF.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/Abogado/ArcPAK.cs:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ArcFormats/Abogado/ArcPAK.cs:75` calls `Fs8Archive` and `ArcFormats/Basil/ArcMIF.cs:61` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7–8 lines × 10) · ×1
  • Duplicated block (7–8 lines × 10) ArcFormats/AnimeGameSystem/ArcDAT.cs:56 — ArcFormats/AnimeGameSystem/ArcDAT.cs:56-63 | ArcFormats/Basil/ArcMIF.cs:48-54 | ArcFormats/BlueGale/ArcSNN.cs:57-63 | ArcFormats/FC01/ArcMRG0.cs:48-54 | ArcFormats/Ffa/ArcFFA.cs:68-74 | ArcFormats/Maika/ArcMIK01.cs:55-61 | ArcFormats/Pandora/ArcPBX.cs:51-57 | ArcFormats/SysD/ArcDPK.cs:51-57 | ArcFormats/Ucom/ArcDATA.cs:66-72 | ArcFormats/Ucom/ArcUK.cs:55-61 — before extracting anything, compare `ArcFormats/Basil/ArcMIF.cs` and `ArcFormats/Ucom/ArcDATA.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/AnimeGameSystem/ArcDAT.cs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/AnimeGameSystem/ArcDAT.cs:55` calls `Reserve` and `ArcFormats/Basil/ArcMIF.cs:48` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 7) · ×1
  • Duplicated block (5 lines × 7) ArcFormats/DigitalWorks/ArcPAC.cs:65 — ArcFormats/DigitalWorks/ArcPAC.cs:65-69 | ArcFormats/HSP/ArcDPM.cs:83-87 | ArcFormats/SoftwareHouseParsley/ArcScn.cs:53-57 | ArcFormats/Tail/ArcCAF.cs:78-82 | Legacy/Tigerman/ArcPAC.cs:63-67 | Legacy/Uran/ArcPHS.cs:57-61 | Legacy/Zone/ArcPKD.cs:62-66 — before extracting anything, compare `Legacy/Tigerman/ArcPAC.cs` and `Legacy/Uran/ArcPHS.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/DigitalWorks/ArcPAC.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7–8 lines × 3) · ×1
  • Duplicated block (7–8 lines × 3) ArcFormats/Favorite/ArcFVP.cs:59 — ArcFormats/Favorite/ArcFVP.cs:59-65 | ArcFormats/Ffa/ArcBlackPackage.cs:124-131 | ArcFormats/FlyingShine/ArcPD.cs:68-74 — 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 `ArcFormats/Favorite/ArcFVP.cs:59` 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.
D4 · Code Duplication · Duplicated block (6–8 lines × 2) · ×1
  • Duplicated block (6–8 lines × 2) ArcFormats/Entis/ErisaMatrix.cs:151 — ArcFormats/Entis/ErisaMatrix.cs:151-156 | ArcFormats/Entis/ErisaMatrix.cs:167-174 — 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 `ArcFormats/Entis/ErisaMatrix.cs:151` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) Legacy/Pinpai/ArcARC.cs:51 — Legacy/Pinpai/ArcARC.cs:51-57 | Legacy/Sogna/ArcSGS.cs:50-57 — 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 `Legacy/Pinpai/ArcARC.cs:51` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Legacy/Pinpai/ArcARC.cs:50` calls `GetFileNameWithoutExtension`, `ToLowerInvariant` and `Legacy/Sogna/ArcSGS.cs:50` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 9) · ×1
  • Duplicated block (5 lines × 9) ArcFormats/AdvSys/ArcAdvSysT.cs:59 — ArcFormats/AdvSys/ArcAdvSysT.cs:59-63 | ArcFormats/AdvSys/ArcGR2.cs:57-61 | ArcFormats/Basil/ArcMIF.cs:49-53 | ArcFormats/Cadath/ArcKAR.cs:54-58 | ArcFormats/FC01/ArcMRG0.cs:49-53 | ArcFormats/Maika/ArcMIK01.cs:56-60 | ArcFormats/Pandora/ArcPBX.cs:52-56 | ArcFormats/Ucom/ArcDATA.cs:67-71 | ArcFormats/Ucom/ArcUK.cs:56-60 — before extracting anything, compare `ArcFormats/Basil/ArcMIF.cs` and `ArcFormats/Cadath/ArcKAR.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ArcFormats/AdvSys/ArcAdvSysT.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ArcFormats/FC01/ArcMRG0.cs:47` calls `ReadUInt32` and `ArcFormats/Basil/ArcMIF.cs:46` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 7) · ×1
  • Duplicated block (7 lines × 7) ArcFormats/Abel/ArcFPK.cs:64 — ArcFormats/Abel/ArcFPK.cs:64-70 | ArcFormats/Bishop/ArcPK.cs:54-60 | ArcFormats/Eternity/ArcGLNK.cs:65-71 | ArcFormats/Gpk2/ArcGPK2.cs:62-68 | ArcFormats/Palette/ArcPAK2.cs:68-74 | ArcFormats/WildBug/ArcWBP.cs:76-82 | Legacy/HyperWorks/ArcPAK.cs:60-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×1
  • Duplicated block (6 lines × 5) ArcFormats/Aoi/ArcVFS.cs:69 — ArcFormats/Aoi/ArcVFS.cs:69-74 | ArcFormats/Aoi/ArcVFS.cs:100-105 | ArcFormats/DenSDK/ArcDAF.cs:65-70 | ArcFormats/RealLive/ArcSEEN.cs:58-63 | ArcFormats/Scoop/ArcGX.cs:67-72 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. 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.
D4 · Code Duplication · Duplicated block (3–5 lines × 6) · ×1
  • Duplicated block (3–5 lines × 6) ArcFormats/Camellia.cs:80 — ArcFormats/Camellia.cs:80-85 | ArcFormats/Camellia.cs:87-91 | ArcFormats/Camellia.cs:93-95 | ArcFormats/Camellia.cs:97-100 | ArcFormats/Camellia.cs:101-105 | ArcFormats/Camellia.cs:107-109 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: GameRes GameRes/GameRes.csproj:1 — GameRes: abstractness 0.21, instability 0.00, distance 0.79 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
IC1 · Incompleteness & stubs · Both branches are identical · ×1
  • Both branches are identical — the condition decides nothing ArcFormats/Macromedia/ImageBITD.cs:73 — Both arms of `info.DepthType == 0x87 // i have no clue what this is || info.DepthType == 0x8A ? … : …` are `PixelFormats.Bgra32`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
S1 · Cryptographic Hygiene · Obsolete TLS/SSL protocol version enabled · ×1
  • Obsolete TLS/SSL protocol version enabled REDACTED:47 — `SecurityProtocol` explicitly selects `SecurityProtocolType.Tls11`, a protocol version that is broken (SSL 2.0/3.0) or withdrawn (TLS 1.0/1.1, RFC 8996). Offering an obsolete version does not merely permit it — it is what a downgrade attack negotiates, so the weakest version on the list is the one that decides the connection's strength. Stop pinning versions here: leave the protocol unset (`SecurityProtocolType.SystemDefault`, or simply do not assign it) so the connection uses the OS policy and picks up TLS 1.3 and future versions without a code change. Where a version must be named explicitly, name `Tls12` and `Tls13` only.
S1 · Cryptographic Hygiene · Ciphertext is encrypted but not authenticated · ×1
  • Ciphertext is encrypted but not authenticated ArcFormats/NitroPlus/ArcNPK.cs:301 — This type encrypts through `SymmetricAlgorithm`, whose every cipher mode (CBC/ECB/OFB/CFB/CTS) is unauthenticated, and no keyed MAC or AEAD cipher appears anywhere in it — so nothing establishes that the ciphertext it produced is the ciphertext it later reads back. Encryption alone provides confidentiality, not integrity: unauthenticated CBC is MALLEABLE, and an attacker who can modify stored or transmitted ciphertext can flip chosen plaintext bits in the following block by flipping ciphertext bits in the preceding one, without ever knowing the key. Where the decrypt path reports failure differently for a padding error than for a downstream one — a broad `catch` that returns null is the usual spelling — the same construction also answers the attacker's questions, which is the padding-oracle shape that recovers plaintext outright. Prefer an AEAD cipher: `AesGcm` or `ChaCha20Poly1305` authenticate the ciphertext as part of encrypting it, and give you an associated-data slot for the surrounding context. Where the format cannot change, MAC it with encrypt-then-MAC — HMAC-SHA256 over the IV and the ciphertext together, with a key derived separately from the encryption key — and verify that tag with `CryptographicOperations.FixedTimeEquals` BEFORE decrypting anything.
X1 · Async correctness · async void method · ×1
  • async void method: StartFormatsDownload REDACTED:222 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
X29 · Per-element action decided by a fixed element · Per-element action decided by a fixed element · ×1
  • Per-element action decided by a fixed element ArcFormats/DirectDraw/DxtDecoder.cs:96 — This loop runs once per element of `m_dxt_buffer`, and the statement it guards acts on the element it is on — `m_dxt_buffer[i]`. The test deciding whether that statement runs does not: `has_alpha` reads `m_dxt_buffer[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 91, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out.
Minor — 1183 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×1065
  • Orphaned file GUI/MainWindow.xaml.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Macromedia/Palettes.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Circus/AudioPCM.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/KiriKiri/ArcXP3.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/WildBug/ImageWBM.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/rUGP/ImageRIP.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file GUI/ProgressDialog/ProgressDialog.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Cmvs/ImagePB3.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Primel/Encryption.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Legacy/Weapon/ArcDAT.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Emote/ArcPSB.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/KogadoCocotte.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file GameRes/FileSystem.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Unity/Vorbis.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/GameSystem/AudioADP4.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/RenPy/ArcRPA.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Macromedia/DirectorFile.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Legacy/Nekotaro/ImageGCmp.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/ScrPlayer/ImageIMG.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Ethornell/ImageCBG.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Cmvs/AudioMV.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Legacy/PineSoft/ArcCMB.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/StudioJikkenshitsu/SjTransform.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Camellia.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ArcFormats/Majiro/ImageRCT.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 1040 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate ArcFormats/DenSDK/ArcDAF.cs:53 — `!IsSaneCount (count) || index_offset >= file.MaxOffset` appears character-identically in 3 files — ArcFormats/DenSDK/ArcDAF.cs, ArcFormats/Yox/ArcYOX.cs, Legacy/Tsd/ArcMCD.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/TamaSoft/ArcEPK.cs:78 — `!IsSaneCount (count) || index_size >= file.MaxOffset` appears character-identically in 2 files — ArcFormats/TamaSoft/ArcEPK.cs, ArcFormats/Tanaka/ArcWSM.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/FrontierWorks/ArcPCARC.cs:72 — `!string.IsNullOrEmpty (path) && !path.EndsWith ("/")` appears character-identically in 2 files — ArcFormats/Edoire/ArcARC.cs, ArcFormats/FrontierWorks/ArcPCARC.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/RealLive/ArcSCENE.cs:220 — `!string.IsNullOrEmpty (title) && KnownKeys.ContainsKey (title)` appears character-identically in 3 files — ArcFormats/Marble/ArcMBL.cs, ArcFormats/Qlie/ArcQLIE.cs, ArcFormats/RealLive/ArcSCENE.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/Cyberworks/ArcDAT.cs:352 — `!string.IsNullOrEmpty (title) && KnownSchemes.ContainsKey (title)` appears character-identically in 5 files — ArcFormats/CatSystem/ArcINT.cs, ArcFormats/Cyberworks/ArcDAT.cs, ArcFormats/DxLib/ArcMED.cs, ArcFormats/Lucifen/ArcLPK.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/Dogenzaka/ArcBIN.cs:138 — `0 == entry.Size || !entry.CheckPlacement (file.MaxOffset)` appears character-identically in 2 files — ArcFormats/Dogenzaka/ArcBIN.cs, ArcFormats/Yox/ArcYOX.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate GameRes/ImagePNG.cs:60 — `0 == image.OffsetX && 0 == image.OffsetY` appears character-identically in 2 files — GUI/GarExtract.cs, GameRes/ImagePNG.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/Cri/AudioADX.cs:171 — `0 == m_format.Channels || m_format.Channels > 16` appears character-identically in 2 files — ArcFormats/Cri/AudioADX.cs, ArcFormats/Cri/AudioHCA.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/LiveMaker/ArcVF.cs:164 — `0 == name_length || name_length > name_buffer.Length` appears character-identically in 2 files — ArcFormats/LiveMaker/ArcVF.cs, ArcFormats/NitroPlus/ArcNPK.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Legacy/Desire/ImageDES.cs:51 — `0 == width || 0 == height || (width & 7) != 0 || width > 640 || height > 400` appears character-identically in 2 files — Legacy/Desire/ImageDES.cs, Legacy/System98/ImageG.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Legacy/Broccoli/ImageT32.cs:84 — `0 == width || 0 == height || width > 0x4000 || height > 0x4000 || parts < 0` appears character-identically in 2 files — Legacy/Broccoli/ImageT32.cs, Legacy/Broccoli/ImageTbm.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/Artdink/ImageAGI.cs:72 — `0 == width || 0 == height || width > 16384 || height > 16384` appears character-identically in 3 files — ArcFormats/Artdink/ImageAGI.cs, ArcFormats/Artdink/ImageFAC.cs, ArcFormats/Artdink/ImageTEX.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/FC01/ImageWM2.cs:44 — `0 == width || width > 0x8000 || 0 == height || height > 0x8000` appears character-identically in 7 files — ArcFormats/FC01/ImageWM2.cs, ArcFormats/GameSystem/ImageBGD.cs, ArcFormats/GameSystem/ImageCGD.cs, ArcFormats/MnoViolet/ImageGRA.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/DDSystem/ArcDDP.cs:106 — `0x020000 == signature || 0x0A0000 == signature` appears character-identically in 3 files — ArcFormats/DDSystem/ArcDDP.cs, ArcFormats/SHSystem/ArcHXP.cs, ArcFormats/SuperNekoX/ArcGPC.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/WildBug/AudioWWA.cs:47 — `1 != header[0xC] || 0 == count || 0 == dir_size` appears character-identically in 2 files — ArcFormats/WildBug/AudioWWA.cs, ArcFormats/WildBug/ImageWBM.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/Crowd/ImageCWP.cs:58 — `bpp != 1 && bpp != 2 && bpp != 4 && bpp != 8 && bpp != 16` appears character-identically in 2 files — ArcFormats/Crowd/ImageCWP.cs, GameRes/ImagePNG.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/Cmvs/ArcCPZ.cs:249 — `data.Length > 0x30 && Binary.AsciiEqual (data, 0, "PS2A")` appears character-identically in 2 files — ArcFormats/Cmvs/ArcCPZ.cs, ArcFormats/Cmvs/ArcCPZ3.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/Cmvs/ArcCPZ.cs:251 — `data.Length > 0x40 && Binary.AsciiEqual (data, 0, "PB3B")` appears character-identically in 2 files — ArcFormats/Cmvs/ArcCPZ.cs, ArcFormats/Cmvs/ArcCPZ3.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/StudioEgo/ArcPAK0.cs:59 — `data_offset <= 0x14 || data_offset >= file.MaxOffset` appears character-identically in 2 files — ArcFormats/StudioEgo/ArcEGO.cs, ArcFormats/StudioEgo/ArcPAK0.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Legacy/Mmfass/ArcSDA.cs:52 — `data_offset <= 8 || data_offset >= file.MaxOffset` appears character-identically in 2 files — Legacy/Mmfass/ArcSDA.cs, Legacy/SquadraD/ArcSDA.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/DxLib/ArcDX8.cs:293 — `dir.DirOffset != -1 && dir.ParentDirOffset != -1` appears character-identically in 2 files — ArcFormats/DxLib/ArcDX.cs, ArcFormats/DxLib/ArcDX8.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Legacy/Hdl/ImageHOT.cs:56 — `dst < pixels.Length && file.PeekByte() != -1` appears character-identically in 2 files — Legacy/Hdl/ImageHOT.cs, Legacy/Ocarina/ImageRED.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/CDPA/ArcPACK.cs:61 — `entry.Offset < data_offset || !entry.CheckPlacement (file.MaxOffset)` appears character-identically in 15 files — ArcFormats/AdvSys/ArcAdvSysT.cs, ArcFormats/AdvSys/ArcGR2.cs, ArcFormats/ArcIKS.cs, ArcFormats/BlackRainbow/ArcGSP.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/NekoSDK/ArcDAT.cs:75 — `entry.Offset < first_offset || !entry.CheckPlacement (file.MaxOffset)` appears character-identically in 3 files — ArcFormats/NekoSDK/ArcDAT.cs, Legacy/Electriciteit/ArcDAT.cs, Legacy/Lune/ArcPACK.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate ArcFormats/Marble/ArcMBL.cs:254 — `entry.Offset < index_size || !entry.CheckPlacement (file.MaxOffset)` appears character-identically in 3 files — ArcFormats/Crowd/ArcPCK.cs, ArcFormats/FC01/ArcMRG.cs, ArcFormats/Marble/ArcMBL.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • + 15 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×39
  • redundant comment ArcFormats/DxLib/HuffmanDecoder.cs:108 — "check if compressedSize and src size match." repeats the code it sits on: 4 of its 5 words (check, compressed, size, src) are already in `if (srcSize!=(compressedSize+headerSize))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment ArcFormats/Entis/MioDecoder.cs:438 — "within m_ptrLastDCT" repeats the code it sits on: 3 of its 3 words (ptr, last, dct) are already in `m_ptrLastDCTBuf = nChannelStep; // within m_ptrLastDCT`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment ArcFormats/Entis/MioDecoder.cs:493 — "within m_ptrLastDCT" repeats the code it sits on: 3 of its 3 words (ptr, last, dct) are already in `m_ptrLastDCTBuf = nChannelStep; // within m_ptrLastDCT`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment ArcFormats/KiriKiri/ImageTLG.cs:323 — "read bit length" repeats the code it sits on: 3 of its 3 words (read, bit, length) are already in `int bit_length = src.ReadInt32();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment ArcFormats/Properties/AssemblyInfo.cs:5 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment ArcFormats/Properties/AssemblyInfo.cs:17 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment ArcFormats/Properties/AssemblyInfo.cs:22 — "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment ArcFormats/Properties/AssemblyInfo.cs:25 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment ArcFormats/Unity/Vorbis.cs:731 — "codec_setup_info" repeats the code it sits on: 3 of its 3 words (codec, setup, info) are already in `class CodecSetupInfo`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Console/Properties/AssemblyInfo.cs:5 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Console/Properties/AssemblyInfo.cs:17 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Console/Properties/AssemblyInfo.cs:22 — "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Console/Properties/AssemblyInfo.cs:25 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Experimental/Properties/AssemblyInfo.cs:5 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Experimental/Properties/AssemblyInfo.cs:17 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Experimental/Properties/AssemblyInfo.cs:22 — "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Experimental/Properties/AssemblyInfo.cs:25 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment GUI/Properties/AssemblyInfo.cs:7 — 8 comments in this file only repeat the code they sit on (lines 7, 19, 24, 35, 36, 38, 39, 44), for example "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:100 — "Create the CompositionContainer with the parts in the catalog" repeats the code it sits on: 4 of its 5 words (create, composition, container, catalog) are already in `using (var container = new CompositionContainer (catalog))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment GameRes/Properties/AssemblyInfo.cs:5 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment GameRes/Properties/AssemblyInfo.cs:17 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment GameRes/Properties/AssemblyInfo.cs:22 — "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment GameRes/Properties/AssemblyInfo.cs:25 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Image.Convert/Properties/AssemblyInfo.cs:5 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Image.Convert/Properties/AssemblyInfo.cs:17 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • + 14 more in this group — see findings.md.
X7 · Silent fallback defaults · Silent fallback default in catch · ×7
  • Silent fallback default in catch ArcFormats/Actgs/ArcDAT.cs:202 — `Read` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch ArcFormats/LightVN/ArcMCDAT.cs:150 — `TryOpen` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch ArcFormats/Marble/ArcMBL.cs:160 — `ReadIndex` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Legacy/Broccoli/ArcP00.cs:134 — `DetectEntryType` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Legacy/Broccoli/ArcP00.cs:271 — `DetectEntryType` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Legacy/Broccoli/BroccoliGrp.cs:138 — `DecompressData` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Legacy/Nekotaro/ImageGCmp.cs:390 — `RetrievePalette` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
D16 · Bus Factor · Off-boarding risk · ×4
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 56 significant file(s) lose their only recent owner: Legacy/Giga/ArcBBWAV.cs, ArcFormats/rUGP/ArcRIO.cs, ArcFormats/NitroPlus/ArcNPA.cs, ArcFormats/NitroPlus/ArcNPK.cs, ArcFormats/ExeFile.cs, ArcFormats/Sas5/ArcSec5.cs, ArcFormats/Musica/ArcPAZ.cs, ArcFormats/Littlewitch/ArcDAT.cs (+48 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 23 significant file(s) lose their only recent owner: ArcFormats/Leaf/ImageLFB.cs, ArcFormats/GsPack/ArcGsPack.cs, ArcFormats/Artdink/ArcDAT.cs, ArcFormats/Succubus/ImageGH.cs, Legacy/Nekotaro/ImageNCG.cs, Legacy/Broccoli/ImageT32.cs, ArcFormats/Artdink/ImageTAG.cs, ArcFormats/GsPack/ImageGS.cs (+15 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 7 significant file(s) lose their only recent owner: ArcFormats/NekoNyan/ArcDAT.cs, ArcFormats/Entergram/QuickLZ.cs, ArcFormats/CatSystem/ArcBinV1.cs, ArcFormats/LightVN/ArcMCDAT.cs, ArcFormats/Entergram/ArcPacV1.cs, ArcFormats/NekoNovel/ArcNKPACK.cs, ArcFormats/CatSystem/ArcPidaV1.cs. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 6 significant file(s) lose their only recent owner: ArcFormats/KiriKiri/ImageTLG.cs, ArcFormats/KiriKiri/HxCrypt.cs, GameRes/Utility.cs, ArcFormats/ImageKTX.cs, ArcFormats/KiriKiri/ArcTLG.cs, ArcFormats/Edoire/ArcARC.cs. Pair on, review, or document these before any departure.
D19 · Documentation Quality · Documentation · ×3
  • Documentation: no build, run or usage example README.md:1 — the repository holds project manifests and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Console/README.md:1 — `Console` is an executable (`OutputType Exe`) and neither `Console/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Image.Convert/README.md:1 — `Image.Convert` is an executable (`OutputType Exe`) and neither `Image.Convert/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file Legacy/Giga/ArcALL.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file Legacy/Koei/YkTables.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file ArcFormats/Cri/AudioHCA.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×3
  • Silent fallback default on parse failure ArcFormats/FC01/WidgetMCG.xaml.cs:44 — `StringToByte` returns `0` when `byte.TryParse (s, NumberStyles.HexNumber, CultureInfo.InvariantCulture, out key)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure ArcFormats/elf/ArcHED.cs:175 — `ReadMap` returns `false` when `match.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure ArcFormats/RenPy/ArcRPA.cs:687 — `LoadInt` returns `false` when `long.TryParse (num, NumberStyles.Integer, CultureInfo.InvariantCulture, out n)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×2
  • Projects may be oversized for their cohesion ArcFormats/ArcFormats.csproj:1 — `ArcFormats` overshoots its size bounds (176227 LoC, 1378 public types across 291 namespaces). 2 of 9 project(s) overshoot their size bounds, lowering Project Cohesion to 5.6/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Legacy/Legacy.csproj:1 — `Legacy` overshoots its size bounds (44576 LoC, 327 public types across 160 namespaces). 2 of 9 project(s) overshoot their size bounds, lowering Project Cohesion to 5.6/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IBinaryStream (25 members) GameRes/BinaryStream.cs:35 — `IBinaryStream` declares 25 members: `Name`, `Signature`, `AsStream`, `CanSeek`, `Length`, `Position`, `Seek`, `Read`, `ReadByte`, `PeekByte`, `ReadInt8`, `ReadUInt8`, `ReadInt16`, `ReadUInt16`, `ReadInt24`, `ReadInt32`, `ReadUInt32`, `ReadInt64`, `ReadUInt64`, `ReadHeader`, `ReadCString`, `ReadCString`, `ReadCString`, `ReadCString`, `ReadBytes`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 25 declarations carry 22 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 22 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 6 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (99 single-owned of 446 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 446 of the 1328 production source files in this repository met that bar). They are anonymized user #5 (2 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)), anonymized user #8 (1 file(s)), anonymized user #9 (1 file(s)), anonymized user #10 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: ArcFormats/Leaf/ArcLAC.cs, ArcFormats/Leaf/LeafCompression.cs, ArcFormats/Kaguya/ArcLINK.cs, ArcFormats/ExHibit/ImageGYU.cs, ArcFormats/Silky/ImageAKB.cs, ArcFormats/Circus/ArcCircus.cs, ArcFormats/CatSystem/ArcDAT.cs.
D17 · Explicit Debt · ObsoleteWithoutCallers · ×1
  • ObsoleteWithoutCallers ArcFormats/ArcCommon.cs:210 — [Obsolete] TgaStream
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found Console/GARbro.Console.csproj:8 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `Console/GARbro.Console.csproj` makes this repository a deployable product (line 8).
D21 · Naming Consistency · `CreateINTWidget` spells `INT` where 23 names in the project spell it `Int` · ×1
  • `CreateINTWidget` spells `INT` where 23 names in the project spell it `Int` ArcFormats/CatSystem/CreateINTWidget.xaml.cs:8 — 23 of 25 names in project ArcFormats spell the token `Int` (23 of 25; unit: names in project ArcFormats containing `Int`). Peers: GecReader.GetInt (ArcFormats/Banana/ImageGEC.cs:307); Camellia.CopyBytesToUInt (ArcFormats/Camellia.cs:240); Camellia.CopyUIntToBytes (ArcFormats/Camellia.cs:248); AImageReader.GetInt (ArcFormats/Cyberworks/ImageTINK.cs:447); ERISADecodeContext.m_nIntBufCount (REDACTED:414). Rename to `CreateIntWidget`. [rule N6]
D21 · Naming Consistency · `WidgetINT` spells `INT` where 23 names in the project spell it `Int` · ×1
  • `WidgetINT` spells `INT` where 23 names in the project spell it `Int` ArcFormats/CatSystem/WidgetINT.xaml.cs:43 — 23 of 25 names in project ArcFormats spell the token `Int` (23 of 25; unit: names in project ArcFormats containing `Int`). Peers: GecReader.GetInt (ArcFormats/Banana/ImageGEC.cs:307); Camellia.CopyBytesToUInt (ArcFormats/Camellia.cs:240); Camellia.CopyUIntToBytes (ArcFormats/Camellia.cs:248); AImageReader.GetInt (ArcFormats/Cyberworks/ImageTINK.cs:447); ERISADecodeContext.m_nIntBufCount (REDACTED:414). Rename to `WidgetInt`. [rule N6]
D21 · Naming Consistency · `CoderPropID` spells `ID` where 20 names in the project spell it `Id` · ×1
  • `CoderPropID` spells `ID` where 20 names in the project spell it `Id` ArcFormats/Lzma/ICoder.cs:81 — 20 of 21 names in project ArcFormats spell the token `Id` (20 of 21; unit: names in project ArcFormats containing `Id`). Peers: IndexReader.GetEntryById (ArcFormats/Cri/ArcCPK.cs:237); SenrenCxCrypt.NamesSectionId (ArcFormats/KiriKiri/YuzCrypt.cs:41); CabbageCxCrypt.NamesSectionId (ArcFormats/KiriKiri/YuzCrypt.cs:85); NanaCxCrypt.NamesSectionId (ArcFormats/KiriKiri/YuzCrypt.cs:102); RiddleCxCrypt.NamesSectionId (ArcFormats/KiriKiri/YuzCrypt.cs:129). Rename to `CoderPropId`. [rule N6]
D26 · Project Cohesion · Split ArcFormats · ×1
  • Split ArcFormats ArcFormats/ArcFormats.csproj:1 — `ArcFormats` overshoots its size bounds (176227 LoC, 1378 public types across 291 namespaces). These parts reach the rest of the project only through its shared core (`(root)`, `Borland`, `DirectDraw`, `Lucifen`, `NonColor`, `Properties`, `QoiCodec`, `SHSystem`, `Vorbis`), so they are the cleanest seams: `GameRes.Formats.Kaguya` (53 types in 13 files): 0 of 279 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 26 times; `GameRes.Formats.ShiinaRio` (48 types in 7 files): 4 of 201 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 13 times; `GameRes.Formats.Leaf` (47 types in 18 files): 1 of 212 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 36 times. Extract each into its own project.
D26 · Project Cohesion · Split Legacy · ×1
  • Split Legacy Legacy/Legacy.csproj:1 — `Legacy` overshoots its size bounds (44576 LoC, 327 public types across 160 namespaces). These parts reach the rest of the project only through its shared core (`System98`, `UMeSoft`), so they are the cleanest seams: `GameRes.Formats.Adviz` (13 types in 4 files): 0 of 38 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 0 times; `GameRes.Formats.Broccoli` (13 types in 5 files): 0 of 73 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 0 times; `GameRes.Formats.KApp` (12 types in 3 files): 0 of 55 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 0 times. Extract each into its own project.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Concentrated knowledge decay · ×1
  • Concentrated knowledge decay — 1068 of 1219 significant files have no living knowledge, while the repository is still being changed at a low rate (66 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 1068 separate risks. Counted over 1219 of the 1328 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:2 — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation REDACTED:3 — `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Minor — 4 finding(s)
D24 · Comment Value · doc comments repeat the names · ×4
  • doc comments repeat the names ArcFormats/AZSys/FastMersenneTwister.cs:179 — 1 of 40 documented parameters and 0 of 201 summaries in `ArcFormats` only repeat the member or parameter name (e.g. "the shift value" for `shift`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names Experimental/Artemis/ShiftReduceParserCode.cs:789 — 1 of 25 documented parameters and 0 of 49 summaries in `Experimental` only repeat the member or parameter name (e.g. "The default action" for `defaultAction`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names GUI/Shell.cs:113 — 0 of 19 documented parameters and 1 of 131 summaries in `GARbro.GUI` only repeat the member or parameter name (e.g. "Rename the object(s)" for `FO_RENAME`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names GameRes/ArchiveFormat.cs:86 — 3 of 6 documented parameters and 1 of 107 summaries in `GameRes` only repeat the member or parameter name (e.g. "Open" for `OpenImage`). Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-d91e9c0e67e74009ba6e03370f16610d/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-d91e9c0e67e74009ba6e03370f16610d/history-1.json --exit-code 0 --source .33artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=2087" --report-format json --report-path /tmp/watchdog-gitleaks-d91e9c0e67e74009ba6e03370f16610d/history-2.json --exit-code 0 --source .1artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=3087 --max-count=645" --report-format json --report-path /tmp/watchdog-gitleaks-d91e9c0e67e74009ba6e03370f16610d/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d91e9c0e67e74009ba6e03370f16610d/tree.json --exit-code 0 --source .2artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .11artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a REDACTED / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan0—
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .2artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .1artifacts/raw/semgrep-gdpr.json
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1eace-f4c3-7382-8a97-1c83f08d79f3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 1 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Name — 1 field(s)
  • StxEntry.FullName ArcFormats/Glib2/ImagePGX.cs:139

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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