Public report of googleprojectzero/fuzzilli, published 15 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 reportMeasured 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, 15 November 2026, 01:00 UTC · Survey ID cd_f15c462858f5413295ee2aad05d1f48c
googleprojectzero/fuzzilli
Measured 15 November 2026, 00:59 UTC, at code version a291c16
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 scoreAdequate
CriticalWeakAdequateStrongExemplary
Down 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 69,483 lines of product code in 9 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Code Health, 37
Findings by how serious they are
22 critical1001 serious66 minor
19 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 00:59 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 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 ▸
47of 47 dimensions measured by tools.
1079of 1089 findings point to an exact file and line, so you can open each one in the code. The other 10 concern the repository as a whole, such as missing documentation.
47dimensions across 5 lenses, read from 69,483 lines of product code in 9 projects.
googleprojectzero/fuzzilli falls short of our standard for a preview release, held back most by its Code Health lens, the quality of the code itself. It scores 49 out of 100 and is rated Adequate, and 19 of its 22 critical findings are security problems in its servers and containers and in the build pipeline.
Code Health, at 37, is the weakest lens and counts most in the score. The best first step for the work it takes is making the tests check their results, worth about 5 points. Adding type checking would lift Code Health itself, worth about 6 points. Raising Code Health to 67 would lift the score to about 58.
Fourteen settings leave the servers or containers unsafe. Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two pipeline steps install packages that can change without warning. Correcting the unsafe settings, pinning each tool to an exact version and pinning what the pipeline installs would close these risks. The two parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 69,483 lines, about €98,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Code Health rose from 37 to 67, the lowest score rated Strong, the score would rise from 49 to about 58.
Code composition: what the lines of code are
Product code 65%Tests 35%
New since the last survey: 113 findings
These 113 critical or serious findings weren't in the previous survey, on 29 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 37 findings
These 37 critical or serious findings were in the previous survey, on 29 October 2026, and are gone from this one.
Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) Sources/Fuzzilli/Base/ProgramBuilder.swift
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) Sources/Fuzzilli/Base/ProgramBuilder.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift
€33,000 to €160,000, for 544 to 1,726 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 69,483 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: 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. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with ProgramBuilderTest.swift.
Raises the score by about 5 points · Low effort · Test Quality
2
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 6 points · Medium effort · Type Safety
3
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Raises the score by about 6 points · Medium effort · Large Files
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €98,000 to build again, about 0.7 person-years of work. Its weakest lens is Code Health, at 37 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Assertions commented out finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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 5.8 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 13% on every change. The history of the code shows how much it changes: about 27,015 lines over the last 90 days, which is about 109,561 lines a year. At that pace, the extra work comes to an estimated 15.3 to 91.9 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.
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.
10 modules, with 5 dependencies between them. Every module uses only modules listed above it, so there are no loops.
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.
FuzzilliDetectMissingBuiltins uses Fuzzilli, so a change to Fuzzilli can break FuzzilliDetectMissingBuiltins, while a change to FuzzilliDetectMissingBuiltins can't break Fuzzilli.
Position
Below the diagonal: FuzzilliDetectMissingBuiltins uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A02:2025 — Security Misconfiguration
48
High / Critical
A05:2025 — Injection
5
High / Critical
Roadmap
Top priorities: Resolve the 218 No assertions finding(s) in Test Quality — start with WasmTests.swift (104), WasmGCTests.swift (38), MinimizerTest.swift (36); Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with ProgramBuilderTest.swift.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Bring the 3 bodies over 240 down to 240 or less in Cognitive Complexity — start with JavaScriptLifter.lift (cognitive 555), FuzzILLifter.lift (cognitive 301), JavaScriptCompiler.compileExpression (cognitive 243).
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 — 22
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 — 1001
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 — 66
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 19
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 47 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, 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 — 47 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1079 of 1089 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — 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. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — 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. Test source is present (.swift) and this repository declares a SwiftPM test suite (Fuzzilli), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — 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. This repository's 1 package.json manifest(s) WERE read and their pinning discipline assessed; what went unanswered is the currency half, because answering it needs a lockfile resolved to CONCRETE versions and this repository commits none — a package.json states version RANGES, and a range names no particular release to be behind. So registry.npmjs.org was never asked, and there was nothing here for it to grade. This is a true statement about the repository and NOT a gap on our side: no lockfile reader we could write would find anything here to read, so there is no capability behind this row to build.
D21 Naming Consistency — 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. 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 — 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. 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 — 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. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
D32 Data Compliance (PII/GDPR) — 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. `Sources/Fuzzilli/Base/ProgramBuilder.swift`, `Sources/Fuzzilli/CodeGen/BinaryenWasmGenerator.swift`, `Sources/Fuzzilli/CodeGen/CodeGenerator.swift`, `Sources/Fuzzilli/CodeGen/CodeGenerators.swift`, `Sources/Fuzzilli/CodeGen/WasmCodeGenerators.swift`, … (+19 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.
D43 Malicious Dependencies — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
D44 Platform End-of-Life — 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. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
AX6 Interface segregation — 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. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — 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. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 29 | # Add Fuzzilli binaries 30 | ADD FuzzilliBuilder/out/Fuzzilli Fuzzilli 31 | >>> ADD FuzzilliBuilder/out/REPRLRun REPRLRun 32 | 33 | RUN mkdir fuzz -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref d930347d-3ceb-4cb3-b0f6-ae71b1c80429::43peqki7r80qz3688tyfi9x0d: "/FuzzilliBuilder/out/REPRLRun": not found; runtime evidence skipped.
C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
GD1 Unfinished & placeholder code — 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. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — 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. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X12 Unreachable branch — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — 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. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X4 Structured logging — 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. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — 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. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Python, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
84 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FuzzILLifter.lift at 518. A further 4 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 Operation.isMatchingEnd at 68 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Sources/Fuzzilli/FuzzIL/Semantics.swift (Operation.isMatchingEnd at 68). 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.
+ 73 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 240 down to 240 or less in Cyclomatic Complexity — start with FuzzILLifter.lift (cyclomatic 518), Instruction.init (cyclomatic 423), JavaScriptLifter.lift (cyclomatic 411). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 3.8 to about 4.7/10, projected with the scoring formula itself and assuming each lands exactly at 240; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 98 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 240 down to 240 or less in Cognitive Complexity — start with JavaScriptLifter.lift (cognitive 555), FuzzILLifter.lift (cognitive 301), JavaScriptCompiler.compileExpression (cognitive 243). — 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 2.5 to about 3.8/10, projected with the scoring formula itself and assuming each lands exactly at 240; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 22 MethodTooLong finding(s) in God Classes — start with JSTyper.swift (3), Compiler.swift (3), Instruction.swift (2). — One of this dimension's main actionable groups (22 warning-level).
Resolve the 16 FileTooLong finding(s) in God Classes — start with ProgramBuilder.swift, JavaScriptEnvironment.swift, Instruction.swift. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 9 TooManyMethods finding(s) in God Classes — start with ProgramBuilder.swift (2), TypeSystem.swift, JSTyper.swift. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
84 duplicated block group(s) detected. 5.5 % of the production lines (3,844 of 69,483) are in a reported copy. A further 78 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 79 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with FuzzILLifter.swift (4), ProgramBuilder.swift (3), WasmLifter.swift (3). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 7 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with ProgramBuilder.swift (4), TypeSystem.swift, Compiler.swift. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with JavaScriptLifter.swift (3), JSTyper.swift, WasmLifter.swift. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
9 production modules (SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 6 of the 9 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 8 Low cohesion finding(s) in Cohesion (LCOM4) — start with TypeSystem.swift (2), Contributor.swift, Arguments.swift. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality6.2 / 10Adequate✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
8 skipped (8 with a documented reason), 219 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 880 tests.
Resolve the 218 No assertions finding(s) in Test Quality — start with WasmTests.swift (104), WasmGCTests.swift (38), MinimizerTest.swift (36). — One of this dimension's main actionable groups (218 warning-level).
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with ProgramBuilderTest.swift. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 3 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 0 of them read from the licence file the repository carries at the revision Package.resolved pins, and 3 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed Package.resolved pins, direct and transitive, and every declared dependency none pins. 3 of them are declared by a manifest that commits no Package.resolved (a library, whose resolution is its consumer's), so their own dependencies are resolved by whoever builds it and are not in this verdict.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 18 Hotspot finding(s) in Churn × Complexity Hotspots — start with FuzzILLifter.swift, JavaScriptLifter.swift, Instruction.swift. — One of this dimension's main actionable groups (18 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.4 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
6 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Sources/Fuzzilli/Corpus/RarityCorpus.swift. Counted over 106 of the 146 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
308 deducted task-comment markers across 69483 LoC (0.4/KLoC) → score 9.1. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 307 TodoComment finding(s) in Explicit Debt — start with ProgramBuilder.swift (59), WasmCodeGenerators.swift (30), JavaScriptEnvironment.swift (25). — One of this dimension's main actionable groups (307 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with WasmTests.swift. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
1 of 2 build units (SwiftPM, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
1 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
5 finding(s): 0 critical, 5 high, 0 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 6 file(s) — `Cloud/GCE/start.sh` (line 71, line 95, line 148, …), `Tests/FuzzilliTests/CompilerTests/advanced_loops.js` (line 317, line 322), `Tests/FuzzilliTests/CompilerTests/classes.js` (line 79, line 81, line 87), `Tests/FuzzilliTests/CompilerTests/explicit_resource_management.js` (line 3, line 11, line 29, …), `Tests/FuzzilliTests/CompilerTests/no_added_blocks.js` (line 58, line 60), … (+1 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
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.
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.
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
Resolve the 17 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (17). — One of this dimension's main actionable groups (17 warning-level).
Resolve the 17 Low IaC finding(s) in IaC & Container Security — start with REDACTED (17). — One of this dimension's main actionable groups (17 recommendation-level).
Resolve the 14 High IaC finding(s) in IaC & Container Security — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
18 of 106 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Sources/Fuzzilli/Modules/Sync.swift. Counted over 106 of the 146 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with Sync.swift, NetworkSync.swift. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 16 Orphaned file finding(s) in Knowledge Freshness — start with Oracle.swift, VariableSet.swift, ThreadSync.swift. — One of this dimension's main actionable groups (16 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 7 Change coupling finding(s) in Change Coupling — start with JSTyper.swift (2), Instruction.swift, Opcodes.swift. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with VariadicInputReducer.swift. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
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
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the 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.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Targets/README.md links to `../Sources/FuzzilliCli/Profiles/Profile.swift`, but `Sources/FuzzilliCli/Profiles/Profile.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Targets/README.md:59
Targets/README.md links to `../Sources/Fuzzilli/CodeGen/CodeGeneratorsWeights.swift`, but `Sources/Fuzzilli/CodeGen/CodeGeneratorsWeights.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Targets/README.md:71
What to do
Reconcile the README with reality: Targets/README.md links to `../Sources/FuzzilliCli/Profiles/Profile.swift`, but `Sources/FuzzilliCli/Profiles/Profile.swift` does not exist; Targets/README.md links to `../Sources/Fuzzilli/CodeGen/CodeGeneratorsWeights.swift`, but `Sources/Fuzzilli/CodeGen/CodeGeneratorsWeights.swift` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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 Swift pack (Swift/Xcode) (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:6
`Sources/Fuzzilli/Compiler/Parser/package.json` 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`. — Sources/Fuzzilli/Compiler/Parser/package.json:2
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — 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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 45 plain JS — the untyped files are Sources/Fuzzilli/Compiler/Parser/parser.js, Tests/FuzzilliTests/CompilerTests/advanced_loops.js, Tests/FuzzilliTests/CompilerTests/async_method.js, Tests/FuzzilliTests/CompilerTests/basic_control_flow.js, Tests/FuzzilliTests/CompilerTests/basic_delete.js, Tests/FuzzilliTests/CompilerTests/basic_expressions.js (+39 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
Sources/Fuzzilli/Compiler/Parser/parser.js:372 · Sources/Fuzzilli/Compiler/Parser/parser.js:725 — 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. — Sources/Fuzzilli/Compiler/Parser/parser.js:372
Sources/Fuzzilli/Compiler/Parser/parser.js:80 · Sources/Fuzzilli/Compiler/Parser/parser.js:544 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — Sources/Fuzzilli/Compiler/Parser/parser.js:80
Sources/Fuzzilli/Compiler/Parser/parser.js:306 · Sources/Fuzzilli/Compiler/Parser/parser.js:372 · Sources/Fuzzilli/Compiler/Parser/parser.js:725 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — Sources/Fuzzilli/Compiler/Parser/parser.js:306
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
visitExpression has cyclomatic complexity 54 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Sources/Fuzzilli/Compiler/Parser/parser.js:612
visitStatement has cyclomatic complexity 45 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Sources/Fuzzilli/Compiler/Parser/parser.js:353
(top-level) has cyclomatic complexity 20 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Tests/FuzzilliTests/CompilerTests/labels.js:1
visitClass has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Sources/Fuzzilli/Compiler/Parser/parser.js:271
runAsyncTests has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Tests/FuzzilliTests/CompilerTests/advanced_loops.js:209
parsePattern has cyclomatic complexity 16 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Sources/Fuzzilli/Compiler/Parser/parser.js:146
(top-level) has cyclomatic complexity 14 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Tests/FuzzilliTests/CompilerTests/basic_control_flow.js:1
Do you agree with this assessment?
R3 · Large Files0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
Sources/Fuzzilli/Compiler/Parser/parser.js has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Sources/Fuzzilli/Compiler/Parser/parser.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R6 · Tooling6.7 / 10Strong✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
50 file(s) (~3171 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. — Tests/FuzzilliTests/CompilerTests/private_properties.js:208
Nothing in its class reads or assigns this private accessor, and no string key or test reaches it by name. Remove it, or use it where it was meant to be used. (×2) — Tests/FuzzilliTests/CompilerTests/private_properties.js:209, Tests/FuzzilliTests/CompilerTests/private_properties.js:210
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
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.
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — Sources/Fuzzilli/FuzzIL/Code.swift:324, Sources/Fuzzilli/Compiler/JavaScriptParser.swift:46
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 3 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 — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 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.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 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 — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — 29 | # Add Fuzzilli binaries 30 | ADD FuzzilliBuilder/out/Fuzzilli Fuzzilli 31 | >>> ADD FuzzilliBuilder/out/REPRLRun REPRLRun 32 | 33 | RUN mkdir fuzz -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref d930347d-3ceb-4cb3-b0f6-ae71b1c80429::43peqki7r80qz3688tyfi9x0d: "/FuzzilliBuilder/out/REPRLRun": not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
D12 Dependency Hygiene — Dependency currency not established — this repository commits no lockfile to resolve
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 5 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling 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"]`.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 24 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Swift suite
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
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
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
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. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
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.
PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 50 test file(s) reach none of 1 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 2% of this repository's production lines — swift (69,110 lines), c (1,971 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — swift (69,110 lines), c (1,971 lines), python (373 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — X21 reached only 2% of this repository's production lines — swift (69,110 lines), c (1,971 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — 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 — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — 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.
Orphaned knowledge Sources/Fuzzilli/Modules/Sync.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge Sources/Fuzzilli/Modules/NetworkSync.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Assertions commented out: testShapeOfGeneratedCode2 Tests/FuzzilliTests/ProgramBuilderTest.swift:174— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
TodoComment Tests/FuzzilliTests/JSTyperTests.swift:421— // TODO: Technically, base3 used as a constructor would return |this|, so we'd have to use the type of |this| if the returned value is not an object in our type inference, but we don't currently do that. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tests/FuzzilliTests/LifterTest.swift:1630— // TODO: Lifting could be improved to remove some brackets. — 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 Tests/FuzzilliTests/LiveTests.swift:159— // TODO(manoskouk): Once we support wasm-gc types in signatures, we'll need — 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 Tests/FuzzilliTests/LiveTests.swift:161— // TODO(pawkra): support shared refs. — 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 Tests/FuzzilliTests/LiveTests.swift:186— // TODO(mliedtke): Figure out how to handle ref.cast and lower it. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tests/FuzzilliTests/MutatorTests.swift:1121— // TODO(rherouart): Find a way to make these tests deterministic — 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 Tests/FuzzilliTests/MutatorTests.swift:1221— // TODO: Add UpdateComputedSuperProperty once supported in FuzzIL. — 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 Tests/FuzzilliTests/ProgramBuilderTest.swift:77— // TODO: Do not rely on these numbers as we are testing a — 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 Tests/FuzzilliTests/ProgramBuilderTest.swift:207— // TODO: We need some robust testing that tests whether we emit code — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tests/FuzzilliTests/ProgramBuilderTest.swift:3389— // TODO(pawkra): check shared subtyping once we support more shared refs. — 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 Tests/FuzzilliTests/ProgramBuilderTest.swift:3895— // TODO: Hm I guess we're missing the block generator that produces a label in the CodeGenerator. — 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 Tests/FuzzilliTests/ProgramBuilderTest.swift:4025— // TODO(mliedtke): The mechanism needs to learn how to resolve nested input + — 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 Tests/FuzzilliTests/ProgramBuilderTest.swift:4191— // TODO: Fix these generators and remove them from this list. — 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 Tests/FuzzilliTests/TypeSystemTest.swift:1533— // TODO(pawkra): add shared variant. — 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 Sources/Fuzzilli/CodeGen/WasmCodeGenerators.swift:638— // TODO(pawkra): add shared variant. — 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 Sources/Fuzzilli/CodeGen/WasmCodeGenerators.swift:684— // TODO(pawkra): add shared variant. — 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 Sources/Fuzzilli/CodeGen/WasmCodeGenerators.swift:692— // TODO(pawkra): add shared variant. — 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 Sources/Fuzzilli/CodeGen/WasmCodeGenerators.swift:699— // TODO(pawkra): add shared variant. — 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 Sources/Fuzzilli/CodeGen/WasmCodeGenerators.swift:707— // TODO(pawkra): add shared variant. — 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 Sources/Fuzzilli/CodeGen/WasmCodeGenerators.swift:815— // TODO(pawkra): add shared variant. — 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 Tests/FuzzilliTests/TypeSystemTest.swift:2213— // TODO(cffsmith): Test and adjust types with a WasmTypeExtension. — 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 Tests/FuzzilliTests/WasmGCTests.swift:846— // TODO(pawkra): add shared ref variant. — 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 Tests/FuzzilliTests/WasmTests.swift:1272— // TODO(pawkra): add shared ref variant. — 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 Tests/FuzzilliTests/WasmTests.swift:1352— // TODO(pawkra): add shared ref variant. — 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 Tests/FuzzilliTests/WasmTests.swift:7100— // TODO(pawkra): add shared ref variant. — 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.
No assertions: testJSEnvironmentConsistency Tests/FuzzilliTests/EnvironmentTest.swift:21— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDynamicObjectGroupTypingOfWasmModules Tests/FuzzilliTests/JSTyperTests.swift:2392— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testFuzzILLifter Tests/FuzzilliTests/LifterTest.swift:41— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testLoadDisposableVariableLifting Tests/FuzzilliTests/LifterTest.swift:4797— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testCreateNamedDisposableVariableLifting Tests/FuzzilliTests/LifterTest.swift:4805— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testLoadAsyncDisposableVariableLifting Tests/FuzzilliTests/LifterTest.swift:4864— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testCreateNamedAsyncDisposableVariableLifting Tests/FuzzilliTests/LifterTest.swift:4872— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEndlessLoopTermination Tests/FuzzilliTests/LiveTests.swift:31— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testValueGeneration Tests/FuzzilliTests/LiveTests.swift:53— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testWasmCodeGenerationAndCompilation Tests/FuzzilliTests/LiveTests.swift:64— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testWasmCodeGenerationAndCompilationAndExecution Tests/FuzzilliTests/LiveTests.swift:110— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructuringSimplificationWithArrayRest Tests/FuzzilliTests/MinimizerTest.swift:1729— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructuringSimplificationOfUnknownIterable Tests/FuzzilliTests/MinimizerTest.swift:1739— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructuringSimplificationWithObjectRest Tests/FuzzilliTests/MinimizerTest.swift:1748— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructuringSimplificationWithDefaultValue Tests/FuzzilliTests/MinimizerTest.swift:1758— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructuringSimplificationOfNestedPattern Tests/FuzzilliTests/MinimizerTest.swift:1768— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructSimplificationOfArray Tests/FuzzilliTests/MinimizerTest.swift:1781— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructAndReassignSimplification Tests/FuzzilliTests/MinimizerTest.swift:1795— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructAndReassignSimplificationWithObjectRest Tests/FuzzilliTests/MinimizerTest.swift:1810— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructAndReassignSimplificationWithArrayRest Tests/FuzzilliTests/MinimizerTest.swift:1819— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructAndReassignSimplificationOfArray Tests/FuzzilliTests/MinimizerTest.swift:1828— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructAndReassignSimplificationOfNestedPattern Tests/FuzzilliTests/MinimizerTest.swift:1844— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructAndReassignSimplificationWithMemberTarget Tests/FuzzilliTests/MinimizerTest.swift:1860— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructAndReassignSimplificationWithComputedAndElementTargets Tests/FuzzilliTests/MinimizerTest.swift:1879— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDestructAndReassignSimplificationWithPrivateAndSuperTargets Tests/FuzzilliTests/MinimizerTest.swift:1900— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
MethodTooLong: FuzzILLifter.lift Sources/Fuzzilli/Lifting/FuzzILLifter.swift:26— MethodTooLong — lift runs 1399 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1299 over it, 13.99× 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: Instruction.asProtobuf Sources/Fuzzilli/FuzzIL/Instruction.swift:303— MethodTooLong — asProtobuf runs 1387 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1287 over it, 13.87× 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: Instruction.init Sources/Fuzzilli/FuzzIL/Instruction.swift:1984— MethodTooLong — init runs 1216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1116 over it, 12.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: OperationMutator.mutateOperation Sources/Fuzzilli/Mutators/OperationMutator.swift:61— MethodTooLong — mutateOperation runs 851 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 751 over it, 8.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: WasmLifter.lift Sources/Fuzzilli/Lifting/WasmLifter.swift:1776— MethodTooLong — lift runs 692 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 592 over it, 6.92× 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: JSTyper.processTypeChangesAfterScopeChanges Sources/Fuzzilli/FuzzIL/JSTyper.swift:1943— MethodTooLong — processTypeChangesAfterScopeChanges runs 658 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 558 over it, 6.58× 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: JavaScriptCompiler.compileExpression Sources/Fuzzilli/Compiler/Compiler.swift:1096— MethodTooLong — compileExpression runs 586 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 486 over it, 5.86× 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: JSTyper.analyzeWasmInstruction Sources/Fuzzilli/FuzzIL/JSTyper.swift:843— MethodTooLong — analyzeWasmInstruction runs 493 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 393 over it, 4.93× 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: JavaScriptCompiler.compileStatement Sources/Fuzzilli/Compiler/Compiler.swift:367— MethodTooLong — compileStatement runs 414 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 314 over it, 4.14× 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: JavaScriptEnvironment.init Sources/Fuzzilli/Environment/JavaScriptEnvironment.swift:362— MethodTooLong — init runs 375 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 275 over it, 3.75× 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: JSTyper.processScopeChanges Sources/Fuzzilli/FuzzIL/JSTyper.swift:1662— MethodTooLong — processScopeChanges runs 240 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 140 over it, 2.40× 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: JavaScriptCompiler.compileClass Sources/Fuzzilli/Compiler/Compiler.swift:89— MethodTooLong — compileClass runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× 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: Action.translateToFuzzIL Sources/Fuzzilli/Mutators/RuntimeAssistedMutator.swift:386— MethodTooLong — translateToFuzzIL runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ILType.format Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1548— MethodTooLong — format runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× 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: FixupMutator.instrument Sources/Fuzzilli/Mutators/FixupMutator.swift:61— MethodTooLong — instrument runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: InstructionSimplifier.simplifyMultiInstructions Sources/Fuzzilli/Minimization/InstructionSimplifier.swift:151— MethodTooLong — simplifyMultiInstructions runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: OperationMutator.extendVariadicOperationByOneInput Sources/Fuzzilli/Mutators/OperationMutator.swift:1015— MethodTooLong — extendVariadicOperationByOneInput runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: Operation.isMatchingEnd Sources/Fuzzilli/FuzzIL/Semantics.swift:129— MethodTooLong — isMatchingEnd runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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: Statistics.initialize Sources/Fuzzilli/Modules/Statistics.swift:227— MethodTooLong — initialize runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× 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: VariadicInputReducer.reduce Sources/Fuzzilli/Minimization/VariadicInputReducer.swift:17— MethodTooLong — reduce 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: Statistics.compute Sources/Fuzzilli/Modules/Statistics.swift:86— MethodTooLong — compute 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.
MethodTooLong: Fuzzer.runStartupTests Sources/Fuzzilli/Fuzzer.swift:1265— MethodTooLong — runStartupTests runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Hotspot: Sources/Fuzzilli/Lifting/FuzzILLifter.swift Sources/Fuzzilli/Lifting/FuzzILLifter.swift:26— Sources/Fuzzilli/Lifting/FuzzILLifter.swift changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 518 in FuzzILLifter.lift at line 26. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Lifting/FuzzILLifter.swift`: 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: Sources/Fuzzilli/Lifting/JavaScriptLifter.swift Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:127— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 411 in JavaScriptLifter.lift at line 127. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Lifting/JavaScriptLifter.swift`: 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: Sources/Fuzzilli/FuzzIL/Instruction.swift Sources/Fuzzilli/FuzzIL/Instruction.swift:1984— Sources/Fuzzilli/FuzzIL/Instruction.swift changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 497 in Instruction.init at line 1984. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/FuzzIL/Instruction.swift`: 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: Sources/Fuzzilli/Mutators/OperationMutator.swift Sources/Fuzzilli/Mutators/OperationMutator.swift:61— Sources/Fuzzilli/Mutators/OperationMutator.swift changed 32 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 180 in OperationMutator.mutateOperation at line 61. 2 of those changes were fix/bug commits, and the other 30 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Mutators/OperationMutator.swift`: 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: Sources/Fuzzilli/FuzzIL/JSTyper.swift Sources/Fuzzilli/FuzzIL/JSTyper.swift:1943— Sources/Fuzzilli/FuzzIL/JSTyper.swift changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 190 in JSTyper.processTypeChangesAfterScopeChanges at line 1943. 4 of those changes were fix/bug commits, and the other 25 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/FuzzIL/JSTyper.swift`: 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: Sources/Fuzzilli/Lifting/WasmLifter.swift Sources/Fuzzilli/Lifting/WasmLifter.swift:1776— Sources/Fuzzilli/Lifting/WasmLifter.swift changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 232 in WasmLifter.lift at line 1776. 2 of those changes were fix/bug commits, and the other 21 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Lifting/WasmLifter.swift`: 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: Sources/FuzzilliCli/main.swift Sources/FuzzilliCli/main.swift:21— Sources/FuzzilliCli/main.swift changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 148 in main.swift.top-level code at line 21. 2 of those changes were fix/bug commits, and the other 19 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/FuzzilliCli/main.swift`: 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: Sources/Fuzzilli/Base/ProgramBuilder.swift Sources/Fuzzilli/Base/ProgramBuilder.swift:8102— Sources/Fuzzilli/Base/ProgramBuilder.swift changed 46 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in ProgramBuilder.updateBuilderState at line 8102. 6 of those changes were fix/bug commits, and the other 40 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Base/ProgramBuilder.swift`: 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: Sources/Fuzzilli/Profiles/V8CommonProfile.swift Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1347— Sources/Fuzzilli/Profiles/V8CommonProfile.swift changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 96 in V8CommonProfile.swift.v8ProcessArgs at line 1347. 2 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Profiles/V8CommonProfile.swift`: 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: Sources/Fuzzilli/Compiler/Parser/parser.js Sources/Fuzzilli/Compiler/Parser/parser.js:43— Sources/Fuzzilli/Compiler/Parser/parser.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 167 in parser.parse at line 43. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Compiler/Parser/parser.js`: 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: Sources/Fuzzilli/Compiler/Compiler.swift Sources/Fuzzilli/Compiler/Compiler.swift:1096— Sources/Fuzzilli/Compiler/Compiler.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 156 in JavaScriptCompiler.compileExpression at line 1096. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Compiler/Compiler.swift`: 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: Sources/Fuzzilli/Minimization/InstructionSimplifier.swift Sources/Fuzzilli/Minimization/InstructionSimplifier.swift:151— Sources/Fuzzilli/Minimization/InstructionSimplifier.swift changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in InstructionSimplifier.simplifyMultiInstructions at line 151. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Minimization/InstructionSimplifier.swift`: 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: Sources/Fuzzilli/Fuzzer.swift Sources/Fuzzilli/Fuzzer.swift:675— Sources/Fuzzilli/Fuzzer.swift changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Fuzzer.importProgramWithFixup at line 675. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Fuzzer.swift`: 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: Sources/Fuzzilli/Minimization/MinimizationPostProcessor.swift Sources/Fuzzilli/Minimization/MinimizationPostProcessor.swift:24— Sources/Fuzzilli/Minimization/MinimizationPostProcessor.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in MinimizationPostProcessor.process at line 24. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Minimization/MinimizationPostProcessor.swift`: 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: Sources/Fuzzilli/Mutators/RuntimeAssistedMutator.swift Sources/Fuzzilli/Mutators/RuntimeAssistedMutator.swift:386— Sources/Fuzzilli/Mutators/RuntimeAssistedMutator.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in Action.translateToFuzzIL at line 386. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Mutators/RuntimeAssistedMutator.swift`: 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: Sources/Fuzzilli/Minimization/VariadicInputReducer.swift Sources/Fuzzilli/Minimization/VariadicInputReducer.swift:17— Sources/Fuzzilli/Minimization/VariadicInputReducer.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in VariadicInputReducer.reduce at line 17. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Minimization/VariadicInputReducer.swift`: 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: Sources/Fuzzilli/Mutators/FixupMutator.swift Sources/Fuzzilli/Mutators/FixupMutator.swift:61— Sources/Fuzzilli/Mutators/FixupMutator.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in FixupMutator.instrument at line 61. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Mutators/FixupMutator.swift`: 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: Sources/Fuzzilli/Minimization/DataFlowSimplifier.swift Sources/Fuzzilli/Minimization/DataFlowSimplifier.swift:33— Sources/Fuzzilli/Minimization/DataFlowSimplifier.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in DataFlowSimplifier.reduce at line 33. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 23:29:45 -08:00' --until='2026-11-10 23:29:45 -08:00' --full-history --no-merges -- Sources/Fuzzilli/Minimization/DataFlowSimplifier.swift`: 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.
FileTooLong: Base/ProgramBuilder.swift Sources/Fuzzilli/Base/ProgramBuilder.swift— FileTooLong — 5668 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 5168 over it, 11.34× 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: Environment/JavaScriptEnvironment.swift Sources/Fuzzilli/Environment/JavaScriptEnvironment.swift— FileTooLong — 3681 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3181 over it, 7.36× 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: FuzzIL/Instruction.swift Sources/Fuzzilli/FuzzIL/Instruction.swift— FileTooLong — 2909 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2409 over it, 5.82× 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: FuzzIL/JSTyper.swift Sources/Fuzzilli/FuzzIL/JSTyper.swift— FileTooLong — 2298 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: JSTyper (16-3388). The bar is 500 significant lines; this is 1798 over it, 4.60× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Lifting/JavaScriptLifter.swift Sources/Fuzzilli/Lifting/JavaScriptLifter.swift— FileTooLong — 2167 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1667 over it, 4.33× 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: FuzzIL/JsOperations.swift Sources/Fuzzilli/FuzzIL/JsOperations.swift— FileTooLong — 2111 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1611 over it, 4.22× 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: FuzzIL/WasmOperations.swift Sources/Fuzzilli/FuzzIL/WasmOperations.swift— FileTooLong — 1880 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1380 over it, 3.76× 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: Lifting/WasmLifter.swift Sources/Fuzzilli/Lifting/WasmLifter.swift— FileTooLong — 1753 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: WasmLifter (78-2537). The bar is 500 significant lines; this is 1253 over it, 3.51× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: FuzzIL/TypeSystem.swift Sources/Fuzzilli/FuzzIL/TypeSystem.swift— FileTooLong — 1747 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1247 over it, 3.49× 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: Compiler/Compiler.swift Sources/Fuzzilli/Compiler/Compiler.swift— FileTooLong — 1716 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: JavaScriptCompiler (18-2372). The bar is 500 significant lines; this is 1216 over it, 3.43× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Lifting/FuzzILLifter.swift Sources/Fuzzilli/Lifting/FuzzILLifter.swift— FileTooLong — 1517 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: FuzzILLifter (18-2084). The bar is 500 significant lines; this is 1017 over it, 3.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Mutators/OperationMutator.swift Sources/Fuzzilli/Mutators/OperationMutator.swift— FileTooLong — 1153 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: OperationMutator (16-1190). The bar is 500 significant lines; this is 653 over it, 2.31× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Profiles/V8CommonProfile.swift Sources/Fuzzilli/Profiles/V8CommonProfile.swift— FileTooLong — 1055 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 555 over it, 2.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Fuzzilli/Fuzzer.swift Sources/Fuzzilli/Fuzzer.swift— FileTooLong — 846 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: Fuzzer (34-1528). The bar is 500 significant lines; this is 346 over it, 1.69× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: FuzzilliCli/main.swift Sources/FuzzilliCli/main.swift— FileTooLong — 691 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 191 over it, 1.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: Parser/parser.js Sources/Fuzzilli/Compiler/Parser/parser.js— FileTooLong — 640 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: parse (43-834). The bar is 500 significant lines; this is 140 over it, 1.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Duplicated block (5 lines × 2) Sources/Fuzzilli/Base/ProgramBuilder.swift:5769— Sources/Fuzzilli/Base/ProgramBuilder.swift:5769-5773 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6229-6233 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:5769` 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 (5 lines × 2) Sources/Fuzzilli/Base/ProgramBuilder.swift:6816— Sources/Fuzzilli/Base/ProgramBuilder.swift:6816-6820 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6826-6830 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:6816` 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:7111— Sources/Fuzzilli/Base/ProgramBuilder.swift:7111-7115 | Sources/Fuzzilli/Base/ProgramBuilder.swift:7119-7123 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:7111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) Sources/Fuzzilli/FuzzIL/JSTyper.swift:553— Sources/Fuzzilli/FuzzIL/JSTyper.swift:553-558 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:616-620 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/Fuzzilli/FuzzIL/JSTyper.swift:553` 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) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1064— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1064-1068 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1221-1225 — 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 `Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1064` 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) Sources/Fuzzilli/Mutators/ExplorationMutator.swift:205— Sources/Fuzzilli/Mutators/ExplorationMutator.swift:205-209 | Sources/Fuzzilli/Mutators/FixupMutator.swift:340-344 — 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 (5 lines × 2) Sources/Fuzzilli/Base/Contributor.swift:125— Sources/Fuzzilli/Base/Contributor.swift:125-129 | Sources/Fuzzilli/Modules/Statistics.swift:567-571 — 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) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:183— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:183-187 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:299-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. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/Fuzzilli/Lifting/FuzzILLifter.swift:183` 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) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:384— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:384-388 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:395-399 — 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) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:591— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:591-595 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:758-762 — 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 `Sources/Fuzzilli/Lifting/FuzzILLifter.swift:591` 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 (5 lines × 2) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:599— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:599-603 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:766-770 — 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 `Sources/Fuzzilli/Lifting/FuzzILLifter.swift:599` 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 (5 lines × 2) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:488— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:488-492 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:505-509 — 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) Sources/Fuzzilli/Lifting/WasmLifter.swift:2029— Sources/Fuzzilli/Lifting/WasmLifter.swift:2029-2033 | Sources/Fuzzilli/Lifting/WasmLifter.swift:2035-2039 — 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 `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) Sources/Fuzzilli/Lifting/WasmLifter.swift:2414— Sources/Fuzzilli/Lifting/WasmLifter.swift:2414-2418 | Sources/Fuzzilli/Lifting/WasmLifter.swift:2438-2442 — 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 (5 lines × 2) Sources/Fuzzilli/Lifting/WasmLifter.swift:2420— Sources/Fuzzilli/Lifting/WasmLifter.swift:2420-2424 | Sources/Fuzzilli/Lifting/WasmLifter.swift:2444-2448 — 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.
TooManyMethods: ProgramBuilder Sources/Fuzzilli/Base/ProgramBuilder.swift:23— TooManyMethods — 335 methods. The bar is 30 methods; this is 305 over it, 11.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WasmFunction Sources/Fuzzilli/Base/ProgramBuilder.swift:4917— TooManyMethods — 174 methods. The bar is 30 methods; this is 144 over it, 5.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ILType Sources/Fuzzilli/FuzzIL/TypeSystem.swift:106— TooManyMethods — 95 methods, declared across 2 files: FuzzIL/TypeSystem.swift (83), Environment/JavaScriptEnvironment.swift (12). The bar is 30 methods; this is 65 over it, 3.17× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: JSTyper Sources/Fuzzilli/FuzzIL/JSTyper.swift:16— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WasmLifter Sources/Fuzzilli/Lifting/WasmLifter.swift:78— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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: Fuzzer Sources/Fuzzilli/Fuzzer.swift:34— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: JavaScriptCompiler Sources/Fuzzilli/Compiler/Compiler.swift:18— TooManyMethods — 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: JavaScriptEnvironment Sources/Fuzzilli/Environment/JavaScriptEnvironment.swift:17— TooManyMethods — 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: Code Sources/Fuzzilli/FuzzIL/Code.swift:16— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: JSTyper Sources/Fuzzilli/FuzzIL/JSTyper.swift:16— ClassTooLong — 2298 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 1898 over it, 5.75× 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: JavaScriptCompiler Sources/Fuzzilli/Compiler/Compiler.swift:18— ClassTooLong — 1715 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 1315 over it, 4.29× 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: WasmLifter Sources/Fuzzilli/Lifting/WasmLifter.swift:78— ClassTooLong — 1711 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 1311 over it, 4.28× 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: FuzzILLifter Sources/Fuzzilli/Lifting/FuzzILLifter.swift:18— ClassTooLong — 1516 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 1116 over it, 3.79× 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: OperationMutator Sources/Fuzzilli/Mutators/OperationMutator.swift:16— ClassTooLong — 1024 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 624 over it, 2.56× 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: Fuzzer Sources/Fuzzilli/Fuzzer.swift:34— ClassTooLong — 836 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 436 over it, 2.09× 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: ILType Sources/Fuzzilli/FuzzIL/TypeSystem.swift:106— ClassTooLong — 769 significant lines (blank, comment-only and punctuation-only lines excluded), 95 methods. The bar is 400 significant lines; this is 369 over it, 1.92× 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: JavaScriptEnvironment Sources/Fuzzilli/Environment/JavaScriptEnvironment.swift:17— ClassTooLong — 720 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 320 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Low cohesion: Contributor (LCOM4 10) Sources/Fuzzilli/Base/Contributor.swift:17— Contributor's methods fall into 10 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 10 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: Arguments (LCOM4 7) Sources/Fuzzilli/Util/Arguments.swift:16— Arguments's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ProgramBuilder (LCOM4 6) Sources/Fuzzilli/Base/ProgramBuilder.swift:23— ProgramBuilder's methods fall into 6 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 6 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: JavaScriptEnvironment (LCOM4 6) Sources/Fuzzilli/Environment/JavaScriptEnvironment.swift:17— JavaScriptEnvironment's methods fall into 6 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 6 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: WasmTypeDescription (LCOM4 5) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2945— WasmTypeDescription's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MockEvaluator (LCOM4 5) Sources/Fuzzilli/Util/MockFuzzer.swift:52— MockEvaluator's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WasmTypeDefinition (LCOM4 4) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2076— WasmTypeDefinition'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: Transport (LCOM4 4) Sources/Fuzzilli/Modules/ThreadSync.swift:31— Transport'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.
Change coupling: Instruction.swift ↔ Opcodes.swift Sources/Fuzzilli/FuzzIL/Instruction.swift:1— `Sources/Fuzzilli/FuzzIL/Instruction.swift` and `Sources/Fuzzilli/FuzzIL/Opcodes.swift` change together 95% of the time (79 of the 83 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 79 shared commits counted here, the most recent 3 are `9ed6e484` [wasm] Add missing SIMD instructions; `3f83d772` [wasm] Add support for array.new; `a32cbb56` [wasm] Add array.init_elem — run `git show` on any of them.
Change coupling: Opcodes.swift ↔ FuzzILLifter.swift Sources/Fuzzilli/FuzzIL/Opcodes.swift:1— `Sources/Fuzzilli/FuzzIL/Opcodes.swift` and `Sources/Fuzzilli/Lifting/FuzzILLifter.swift` change together 95% of the time (79 of the 83 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 79 shared commits counted here, the most recent 3 are `9ed6e484` [wasm] Add missing SIMD instructions; `3f83d772` [wasm] Add support for array.new; `a32cbb56` [wasm] Add array.init_elem — run `git show` on any of them.
Change coupling: JSTyper.swift ↔ FuzzILLifter.swift Sources/Fuzzilli/FuzzIL/JSTyper.swift:1— `Sources/Fuzzilli/FuzzIL/JSTyper.swift` and `Sources/Fuzzilli/Lifting/FuzzILLifter.swift` change together 66% of the time (121 of the 184 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 121 shared commits counted here, the most recent 3 are `9ed6e484` [wasm] Add missing SIMD instructions; `3f83d772` [wasm] Add support for array.new; `a32cbb56` [wasm] Add array.init_elem — run `git show` on any of them.
Change coupling: V8HoleFuzzingProfile.swift ↔ V8SandboxProfile.swift Sources/Fuzzilli/Profiles/V8HoleFuzzingProfile.swift:1— `Sources/Fuzzilli/Profiles/V8HoleFuzzingProfile.swift` and `Sources/Fuzzilli/Profiles/V8SandboxProfile.swift` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `0de3c573` [wasm] Add ForceWasmTurboFanCompilationGenerator to V8 profiles; `ca3a18b2` [v8] Align Worker and externalizeString builtins across V8 profiles; `8da32ef0` [js] Fix d8 typing in profiles — run `git show` on any of them.
Change coupling: Events.swift ↔ TerminalUI.swift Sources/Fuzzilli/Base/Events.swift:1— `Sources/Fuzzilli/Base/Events.swift` and `Sources/FuzzilliCli/TerminalUI.swift` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `2667ef2a` Track program import-acceptance rate between instances; `fbce4fc1` Track samples with poor coverage convergence; `42abfc5e` Track minimization overhead — run `git show` on any of them.
Change coupling: JSTyper.swift ↔ OperationMutator.swift Sources/Fuzzilli/FuzzIL/JSTyper.swift:1— `Sources/Fuzzilli/FuzzIL/JSTyper.swift` and `Sources/Fuzzilli/Mutators/OperationMutator.swift` change together 50% of the time (78 of the 156 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 78 shared commits counted here, the most recent 3 are `9ed6e484` [wasm] Add missing SIMD instructions; `3f83d772` [wasm] Add support for array.new; `a32cbb56` [wasm] Add array.init_elem — run `git show` on any of them.
Change coupling: ProgramBuilder.swift ↔ MinimizationPostProcessor.swift Sources/Fuzzilli/Base/ProgramBuilder.swift:1— `Sources/Fuzzilli/Base/ProgramBuilder.swift` and `Sources/Fuzzilli/Minimization/MinimizationPostProcessor.swift` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `989ac3f9` Infer CreateMap key/value types instead of annotating them; `c38d51e3` Infer CreateArray element types instead of annotating them; `f00d5955` [general] Add parameterizable jsArrays — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×7
Edited copy of a member (10 corresponding lines) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:139— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:139-148 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:151-160 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:6468— Sources/Fuzzilli/Base/ProgramBuilder.swift:6468-6477 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6500-6509 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:6595— Sources/Fuzzilli/Base/ProgramBuilder.swift:6595-6604 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6621-6632 — 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) Sources/Fuzzilli/Compiler/Compiler.swift:1957— Sources/Fuzzilli/Compiler/Compiler.swift:1957-1966 | Sources/Fuzzilli/Compiler/Compiler.swift:1968-1978 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:6489— Sources/Fuzzilli/Base/ProgramBuilder.swift:6489-6498 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6511-6520 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:4870— Sources/Fuzzilli/Base/ProgramBuilder.swift:4870-4880 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6985-6994 — 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) Sources/Fuzzilli/FuzzIL/JsOperations.swift:1782— Sources/Fuzzilli/FuzzIL/JsOperations.swift:1782-1791 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:1915-1926 — 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.
Duplicated block (6 lines × 2) Sources/Fuzzilli/FuzzIL/JSTyper.swift:2450— Sources/Fuzzilli/FuzzIL/JSTyper.swift:2450-2455 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:2459-2465 — 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) Sources/Fuzzilli/Lifting/WasmLifter.swift:1973— Sources/Fuzzilli/Lifting/WasmLifter.swift:1973-1978 | Sources/Fuzzilli/Lifting/WasmLifter.swift:1998-2003 — 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) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:259— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:259-264 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:361-366 — 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) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:499— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:499-504 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:659-664 — 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) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1131— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1131-1136 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1141-1146 — 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) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1322— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1322-1327 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1332-1337 — 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.
FunctionTooLong: parser.parse Sources/Fuzzilli/Compiler/Parser/parser.js:43— FunctionTooLong — parse runs 604 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 504 over it, 6.04× 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.
FunctionTooLong: main.swift.top-level code Sources/FuzzilliCli/main.swift:21— FunctionTooLong — top-level code runs 527 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 427 over it, 5.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.
FunctionTooLong: V8CommonProfile.swift.v8ProcessArgs Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1347— FunctionTooLong — v8ProcessArgs runs 242 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 142 over it, 2.42× 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.
FunctionTooLong: main.swift.makeFuzzer Sources/FuzzilliCli/main.swift:569— FunctionTooLong — makeFuzzer 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.
FunctionTooLong: main.swift.top-level code Sources/FuzzILTool/main.swift:18— FunctionTooLong — top-level code runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×5
Edited copy of a member (9 corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:6814— Sources/Fuzzilli/Base/ProgramBuilder.swift:6814-6822 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6824-6832 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:6001— Sources/Fuzzilli/Base/ProgramBuilder.swift:6001-6009 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6012-6020 — 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) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2470— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2470-2478 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2480-2488 — 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) Sources/Fuzzilli/Modules/NetworkSync.swift:332— Sources/Fuzzilli/Modules/NetworkSync.swift:332-340 | Sources/Fuzzilli/Modules/NetworkSync.swift:517-525 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:3827— Sources/Fuzzilli/Base/ProgramBuilder.swift:3827-3837 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4401-4409 — 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.
Duplicated block (9 lines × 2) Sources/Fuzzilli/Base/ProgramBuilder.swift:7470— Sources/Fuzzilli/Base/ProgramBuilder.swift:7470-7478 | Sources/Fuzzilli/Base/ProgramBuilder.swift:7856-7866 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:7470` 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 (9 lines × 2) Sources/Fuzzilli/Compiler/Compiler.swift:432— Sources/Fuzzilli/Compiler/Compiler.swift:432-440 | Sources/Fuzzilli/Compiler/Compiler.swift:447-455 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Sources/Fuzzilli/FuzzIL/JsOperations.swift:816— Sources/Fuzzilli/FuzzIL/JsOperations.swift:816-824 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:856-864 — 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) Sources/Fuzzilli/FuzzIL/JsOperations.swift:835— Sources/Fuzzilli/FuzzIL/JsOperations.swift:835-843 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:875-883 — 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) Sources/Fuzzilli/FuzzIL/JsOperations.swift:966— Sources/Fuzzilli/FuzzIL/JsOperations.swift:966-974 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:987-995 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Sources/Fuzzilli/Base/ProgramBuilder.swift:3337— Sources/Fuzzilli/Base/ProgramBuilder.swift:3337-3343 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3426-3432 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:3337` 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:3353— Sources/Fuzzilli/Base/ProgramBuilder.swift:3353-3359 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3442-3448 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:3353` 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:3495— Sources/Fuzzilli/Base/ProgramBuilder.swift:3495-3501 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3518-3524 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:3495` 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) Sources/Fuzzilli/FuzzIL/JSTyper.swift:2591— Sources/Fuzzilli/FuzzIL/JSTyper.swift:2591-2597 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:510-516 — 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 `Sources/Fuzzilli/FuzzIL/JSTyper.swift:2591` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1109— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1109-1115 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1120-1126 — 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· Edited copy of a member (12 corresponding lines) · ×4
Edited copy of a member (12 corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:5739— Sources/Fuzzilli/Base/ProgramBuilder.swift:5739-5750 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6207-6219 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:5799— Sources/Fuzzilli/Base/ProgramBuilder.swift:5799-5812 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5814-5825 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:8872— Sources/Fuzzilli/Base/ProgramBuilder.swift:8872-8883 | Sources/Fuzzilli/Base/ProgramBuilder.swift:8886-8899 — 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) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2178— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2178-2189 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2191-2202 — 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.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×4
Edited copy of a member (8 corresponding lines) Sources/Fuzzilli/Util/CInterop.swift:17— Sources/Fuzzilli/Util/CInterop.swift:17-28 | Sources/REPRLRun/main.swift:18-25 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:5394— Sources/Fuzzilli/Base/ProgramBuilder.swift:5394-5401 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5418-5429 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:5538— Sources/Fuzzilli/Base/ProgramBuilder.swift:5538-5549 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5619-5626 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:5447— Sources/Fuzzilli/Base/ProgramBuilder.swift:5447-5458 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5495-5502 — 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.
Duplicated block (11 lines × 2) Sources/Fuzzilli/Compiler/Compiler.swift:233— Sources/Fuzzilli/Compiler/Compiler.swift:233-243 | Sources/Fuzzilli/Compiler/Compiler.swift:1332-1342 — 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 `Sources/Fuzzilli/Compiler/Compiler.swift:233` 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) Sources/Fuzzilli/FuzzIL/JSTyper.swift:2216— Sources/Fuzzilli/FuzzIL/JSTyper.swift:2216-2226 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:2277-2287 — 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) Sources/Fuzzilli/FuzzIL/JsOperations.swift:1814— Sources/Fuzzilli/FuzzIL/JsOperations.swift:1814-1824 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:2305-2315 — 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 `Sources/Fuzzilli/FuzzIL/JsOperations.swift:1814` 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) Sources/Fuzzilli/Minimization/BlockReducer.swift:556— Sources/Fuzzilli/Minimization/BlockReducer.swift:556-566 | Sources/Fuzzilli/Minimization/BlockReducer.swift:586-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 `Sources/Fuzzilli/Minimization/BlockReducer.swift:556` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Sources/Fuzzilli/Base/ProgramBuilder.swift:5868— Sources/Fuzzilli/Base/ProgramBuilder.swift:5868-5877 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5921-5930 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:5868` 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 (10 lines × 2) Sources/Fuzzilli/Base/ProgramBuilder.swift:6108— Sources/Fuzzilli/Base/ProgramBuilder.swift:6108-6117 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6161-6170 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:6108` 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) Sources/Fuzzilli/FuzzIL/JSTyper.swift:2306— Sources/Fuzzilli/FuzzIL/JSTyper.swift:2306-2315 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:2318-2327 — 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) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2042— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2042-2051 | Sources/Fuzzilli/Mutators/OperationMutator.swift:899-908 — 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 `Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2042` 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:5887— Sources/Fuzzilli/Base/ProgramBuilder.swift:5887-5894 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5904-5911 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:5887` 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) Sources/Fuzzilli/Lifting/WasmLifter.swift:2291— Sources/Fuzzilli/Lifting/WasmLifter.swift:2291-2298 | Sources/Fuzzilli/Lifting/WasmLifter.swift:2307-2314 — 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 `Sources/Fuzzilli/Lifting/WasmLifter.swift:2291` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1440— Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1440-1453 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1660-1667 — 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 `Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1440` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Sources/FuzzilliCli/TerminalUI.swift:233— Sources/FuzzilliCli/TerminalUI.swift:233-240 | Sources/FuzzilliCli/TerminalUI.swift:243-250 — 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 `Sources/FuzzilliCli/TerminalUI.swift:233` 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.
parser.parse::visitExpression (cyclomatic 54) Sources/Fuzzilli/Compiler/Parser/parser.js:612— parser.parse::visitExpression has cyclomatic complexity 54 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (parser.parse::parsePattern, parser.parse::visitClass) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
parser.parse::visitClass (cyclomatic 20) Sources/Fuzzilli/Compiler/Parser/parser.js:271— parser.parse::visitClass 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. This shape REPEATS in the file: 2 other methods here (parser.parse::parsePattern, parser.parse::visitExpression) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
parser.parse::parsePattern (cyclomatic 16) Sources/Fuzzilli/Compiler/Parser/parser.js:146— parser.parse::parsePattern 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. This shape REPEATS in the file: 2 other methods here (parser.parse::visitClass, parser.parse::visitExpression) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
parser.parse::visitExpression (cognitive 48) Sources/Fuzzilli/Compiler/Parser/parser.js:612— parser.parse::visitExpression has cognitive complexity 48 (threshold 15). Drivers by points: if/else 21 (37 pts), boolean chains 4, loops 2 (4 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 19). 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. This shape REPEATS in the file: 2 other methods here (parser.parse::parsePattern, parser.parse::visitClass) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
parser.parse::parsePattern (cognitive 39) Sources/Fuzzilli/Compiler/Parser/parser.js:146— parser.parse::parsePattern has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (35 pts), loops 2 (4 pts) (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 2 other methods here (parser.parse::visitClass, parser.parse::visitExpression) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
parser.parse::visitClass (cognitive 30) Sources/Fuzzilli/Compiler/Parser/parser.js:271— parser.parse::visitClass has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 5, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent 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: 2 other methods here (parser.parse::parsePattern, parser.parse::visitExpression) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×3
Edited copy of a member (45 corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:6086— Sources/Fuzzilli/Base/ProgramBuilder.swift:6086-6130 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6135-6190 — 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.
Edited copy of a member (45 corresponding lines) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2350— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2350-2395 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2397-2441 — 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.
Edited copy of a member (45 corresponding lines) Sources/Fuzzilli/Minimization/BlockReducer.swift:374— Sources/Fuzzilli/Minimization/BlockReducer.swift:374-418 | Sources/Fuzzilli/Minimization/BlockReducer.swift:424-471 — 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 copy of a member (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:4596— Sources/Fuzzilli/Base/ProgramBuilder.swift:4596-4611 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4637-4656 — 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) Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:220— Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:220-235 | Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:237-252 — 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) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2100— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2100-2115 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2117-2133 — 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 (13 corresponding lines) · ×3
Edited copy of a member (13 corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:5582— Sources/Fuzzilli/Base/ProgramBuilder.swift:5582-5594 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5596-5609 — 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) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1956— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1956-1968 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2408-2421 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:8651— Sources/Fuzzilli/Base/ProgramBuilder.swift:8651-8663 | Sources/Fuzzilli/Base/ProgramBuilder.swift:8716-8731 — 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 (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) Sources/Fuzzilli/FuzzIL/JsOperations.swift:3249— Sources/Fuzzilli/FuzzIL/JsOperations.swift:3249-3265 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:3274-3287 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:4107— Sources/Fuzzilli/Base/ProgramBuilder.swift:4107-4122 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4134-4147 — 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) Sources/Fuzzilli/Environment/JavaScriptEnvironment.swift:1138— Sources/Fuzzilli/Environment/JavaScriptEnvironment.swift:1138-1154 | Sources/Fuzzilli/Environment/JavaScriptEnvironment.swift:1156-1169 — 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.
Duplicated block (13–14 lines × 2) Sources/Fuzzilli/Compiler/Compiler.swift:196— Sources/Fuzzilli/Compiler/Compiler.swift:196-208 | Sources/Fuzzilli/Compiler/Compiler.swift:1298-1311 — 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 `Sources/Fuzzilli/Compiler/Compiler.swift:196` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) Sources/Fuzzilli/FuzzIL/JSTyper.swift:1297— Sources/Fuzzilli/FuzzIL/JSTyper.swift:1297-1309 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:1325-1338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13–14 lines × 2) Sources/Fuzzilli/Lifting/WasmLifter.swift:847— Sources/Fuzzilli/Lifting/WasmLifter.swift:847-860 | Sources/Fuzzilli/Lifting/WasmLifter.swift:1258-1270 — 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 `Sources/Fuzzilli/Lifting/WasmLifter.swift:847` 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 × 4) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1393— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1393-1399 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1419-1426 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1437-1443 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1459-1465 — 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 `Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1393` 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 × 4) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:605— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:605-611 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:615-621 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:625-631 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:716-722 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `op` to `instr.innerOutput(0)) case .beginObjectLiteralSetter(let` in one and `instr.innerOutput(0)) case .beginClassComputedSetter(let` 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 (7 lines × 4) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1343— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1343-1349 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1352-1358 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1361-1367 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1494-1500 — 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1385— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1385-1399 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1407-1426 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1429-1443 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1451-1465 — 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) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:127— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:127-2210 | Sources/Fuzzilli/Lifting/WasmLifter.swift:1502-1638 | Sources/Fuzzilli/Lifting/WasmLifter.swift:1776-2536 | Sources/Fuzzilli/Mutators/OperationMutator.swift:61-1004 — 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 (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) Sources/Fuzzilli/Compiler/Compiler.swift:2150— Sources/Fuzzilli/Compiler/Compiler.swift:2150-2176 | Sources/Fuzzilli/Compiler/Compiler.swift:2178-2200 — 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) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:2039— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:2039-2061 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2278-2300 — 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 (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:5431— Sources/Fuzzilli/Base/ProgramBuilder.swift:5431-5445 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5504-5514 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:5460— Sources/Fuzzilli/Base/ProgramBuilder.swift:5460-5474 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5483-5493 — 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.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1988— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1988-2002 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2481-2495 — 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) Sources/Fuzzilli/CodeGen/CodeGenerator.swift:276— Sources/Fuzzilli/CodeGen/CodeGenerator.swift:276-290 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:295-309 — 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· Edited copies of one member (4 members, 11+ corresponding lines) · ×2
Edited copies of one member (4 members, 11+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:3302— Sources/Fuzzilli/Base/ProgramBuilder.swift:3302-3312 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3965-3977 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4009-4021 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4039-4051 — 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.
Edited copies of one member (4 members, 11+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:4092— Sources/Fuzzilli/Base/ProgramBuilder.swift:4092-4102 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4153-4165 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4206-4218 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4425-4436 — 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 copy of a member (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:303— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:303-309 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:311-317 — 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) Sources/Fuzzilli/FuzzIL/WasmOperations.swift:3036— Sources/Fuzzilli/FuzzIL/WasmOperations.swift:3036-3042 | Sources/Fuzzilli/FuzzIL/WasmOperations.swift:3054-3060 — 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· Edited copy of a member (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:201— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:201-206 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:209-215 — 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:3373— Sources/Fuzzilli/Base/ProgramBuilder.swift:3373-3379 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3462-3467 — 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· Edited copy of a member (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) Sources/Fuzzilli/FuzzIL/JsOperations.swift:1621— Sources/Fuzzilli/FuzzIL/JsOperations.swift:1621-1628 | Sources/Fuzzilli/FuzzIL/WasmOperations.swift:2410-2413 — 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) Sources/Fuzzilli/FuzzIL/JsOperations.swift:3143— Sources/Fuzzilli/FuzzIL/JsOperations.swift:3143-3147 | Sources/Fuzzilli/FuzzIL/WasmOperations.swift:38-41 — 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.
Duplicated block (17 lines × 2) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1970— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1970-1986 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2463-2479 — 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 (17 lines × 2) Sources/Fuzzilli/Minimization/BlockReducer.swift:377— Sources/Fuzzilli/Minimization/BlockReducer.swift:377-393 | Sources/Fuzzilli/Minimization/BlockReducer.swift:427-443 — 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 `Sources/Fuzzilli/Minimization/BlockReducer.swift:377` 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) Sources/Fuzzilli/Compiler/Compiler.swift:2010— Sources/Fuzzilli/Compiler/Compiler.swift:2010-2024 | Sources/Fuzzilli/Compiler/Compiler.swift:2042-2055 — 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 `Sources/Fuzzilli/Compiler/Compiler.swift:2010` 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) Sources/Fuzzilli/FuzzIL/JsOperations.swift:761— Sources/Fuzzilli/FuzzIL/JsOperations.swift:761-774 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:936-950 — 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 `Sources/Fuzzilli/FuzzIL/JsOperations.swift:761` 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:8669— Sources/Fuzzilli/Base/ProgramBuilder.swift:8669-8682 | Sources/Fuzzilli/Base/ProgramBuilder.swift:8687-8700 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:8669` 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) Sources/Fuzzilli/Lifting/WasmLifter.swift:885— Sources/Fuzzilli/Lifting/WasmLifter.swift:885-898 | Sources/Fuzzilli/Lifting/WasmLifter.swift:1230-1243 — 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 `Sources/Fuzzilli/Lifting/WasmLifter.swift:885` 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) Sources/Fuzzilli/Mutators/ExplorationMutator.swift:185— Sources/Fuzzilli/Mutators/ExplorationMutator.swift:185-197 | Sources/Fuzzilli/Mutators/FixupMutator.swift:313-325 — 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 `Sources/Fuzzilli/Mutators/ExplorationMutator.swift:185` 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) Sources/FuzzilliCli/main.swift:937— Sources/FuzzilliCli/main.swift:937-949 | Sources/FuzzilliCli/main.swift:970-982 — 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 `Sources/FuzzilliCli/main.swift:937` 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 after the matched lines, `Sources/FuzzilliCli/main.swift:952` calls `interestingOnly`, `has` and `Sources/FuzzilliCli/main.swift:984` 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:8667— Sources/Fuzzilli/Base/ProgramBuilder.swift:8667-8675 | Sources/Fuzzilli/Base/ProgramBuilder.swift:8685-8693 | Sources/Fuzzilli/Base/ProgramBuilder.swift:8704-8711 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:8667` 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, `Sources/Fuzzilli/Base/ProgramBuilder.swift:8676` calls `random`, `randomVariable` and `Sources/Fuzzilli/Base/ProgramBuilder.swift:8712` 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) Sources/Fuzzilli/FuzzIL/JSTyper.swift:1268— Sources/Fuzzilli/FuzzIL/JSTyper.swift:1268-1275 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:1295-1302 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:1323-1331 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) Sources/Fuzzilli/Lifting/WasmLifter.swift:768— Sources/Fuzzilli/Lifting/WasmLifter.swift:768-774 | Sources/Fuzzilli/Lifting/WasmLifter.swift:781-786 | Sources/Fuzzilli/Lifting/WasmLifter.swift:1226-1231 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:650— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:650-655 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:665-670 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:732-737 — 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 first that the copies are not typed on the same thing: the declarations holding them bind `op` to `instr.innerOutput(0)) case .beginClassComputedMethod(let` in one and `instr.innerOutput(0)) case .beginClassComputedSetter(let` 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.
Swallowed exception (caught, then discarded) Sources/Fuzzilli/FuzzIL/Code.swift:324— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Sources/Fuzzilli/Compiler/JavaScriptParser.swift:46— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
FuzzILLifter.lift (cyclomatic 518) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:26— FuzzILLifter.lift has cyclomatic complexity 518 (threshold 15). Of this number, 508 points are the body's own statements and 10 belong to 4 function items inside it that branch. 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.
Instruction.init (cyclomatic 423) Sources/Fuzzilli/FuzzIL/Instruction.swift:1984— Instruction.init has cyclomatic complexity 423 (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.
JavaScriptLifter.lift (cyclomatic 411) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:127— JavaScriptLifter.lift has cyclomatic complexity 411 (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.
Instruction.asProtobuf (cyclomatic 407) Sources/Fuzzilli/FuzzIL/Instruction.swift:303— Instruction.asProtobuf has cyclomatic complexity 407 (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. This shape REPEATS in the file: one other method here (Instruction.asProtobuf::ILTypeToWasmTypeEnum) 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.
WasmLifter.lift (cyclomatic 232) Sources/Fuzzilli/Lifting/WasmLifter.swift:1776— WasmLifter.lift has cyclomatic complexity 232 (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.
JSTyper.processTypeChangesAfterScopeChanges (cyclomatic 190) Sources/Fuzzilli/FuzzIL/JSTyper.swift:1943— JSTyper.processTypeChangesAfterScopeChanges has cyclomatic complexity 190 (threshold 15). Of this number, 180 points are the body's own statements and 10 belong to 3 function items inside it that branch. 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.
OperationMutator.mutateOperation (cyclomatic 180) Sources/Fuzzilli/Mutators/OperationMutator.swift:61— OperationMutator.mutateOperation has cyclomatic complexity 180 (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.
JavaScriptCompiler.compileExpression (cyclomatic 156) Sources/Fuzzilli/Compiler/Compiler.swift:1096— JavaScriptCompiler.compileExpression has cyclomatic complexity 156 (threshold 15). Of this number, 155 points are the body's own statements and 1 belongs to one function item 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.
main.swift.top-level code (cyclomatic 148) Sources/FuzzilliCli/main.swift:21— main.swift.top-level code has cyclomatic complexity 148 (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.
JSTyper.analyzeWasmInstruction (cyclomatic 146) Sources/Fuzzilli/FuzzIL/JSTyper.swift:843— JSTyper.analyzeWasmInstruction has cyclomatic complexity 146 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
JavaScriptCompiler.compileStatement (cyclomatic 101) Sources/Fuzzilli/Compiler/Compiler.swift:367— JavaScriptCompiler.compileStatement has cyclomatic complexity 101 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
V8CommonProfile.swift.v8ProcessArgs (cyclomatic 96) Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1347— V8CommonProfile.swift.v8ProcessArgs has cyclomatic complexity 96 (threshold 15). Of this number, 95 points are the body's own statements and 1 belongs to one function item 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.
ILType.format (cyclomatic 78) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1548— ILType.format has cyclomatic complexity 78 (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.
ProgramBuilder.updateBuilderState (cyclomatic 64) Sources/Fuzzilli/Base/ProgramBuilder.swift:8102— ProgramBuilder.updateBuilderState has cyclomatic complexity 64 (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.
JavaScriptCompiler.compileClass (cyclomatic 58) Sources/Fuzzilli/Compiler/Compiler.swift:89— JavaScriptCompiler.compileClass has cyclomatic complexity 58 (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.
Action.translateToFuzzIL (cyclomatic 53) Sources/Fuzzilli/Mutators/RuntimeAssistedMutator.swift:386— Action.translateToFuzzIL has cyclomatic complexity 53 (threshold 15). Of this number, 51 points are the body's own statements and 2 belong to 2 function items inside it that branch. 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.
ProgramBuilder.splice (cyclomatic 50) Sources/Fuzzilli/Base/ProgramBuilder.swift:1773— ProgramBuilder.splice has cyclomatic complexity 50 (threshold 15). Of this number, 36 points are the body's own statements and 14 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JSTyper.processScopeChanges (cyclomatic 47) Sources/Fuzzilli/FuzzIL/JSTyper.swift:1662— JSTyper.processScopeChanges has cyclomatic complexity 47 (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.
parse::visitStatement (cyclomatic 45) Sources/Fuzzilli/Compiler/Parser/parser.js:353— parse::visitStatement 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.
InstructionSimplifier.simplifyMultiInstructions (cyclomatic 44) Sources/Fuzzilli/Minimization/InstructionSimplifier.swift:151— InstructionSimplifier.simplifyMultiInstructions has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 11 of the 44 points are its own statements and the rest belongs to 5 function items inside it that branch (lower::assign, canBeLowered, lower, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ProgramBuilder.generateTypeInternal (cyclomatic 39) Sources/Fuzzilli/Base/ProgramBuilder.swift:809— ProgramBuilder.generateTypeInternal has cyclomatic complexity 39 (threshold 15). Of this number, 33 points are the body's own statements and 6 belong to 2 function items inside it that branch. 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.
ILType.subsumes (cyclomatic 37) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:538— ILType.subsumes has cyclomatic complexity 37 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WasmSimd128IntegerBinOpKind.isValidForShape (cyclomatic 36) Sources/Fuzzilli/FuzzIL/WasmOperations.swift:2182— WasmSimd128IntegerBinOpKind.isValidForShape has cyclomatic complexity 36 (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.
ProgramBuilder.createTemporalFieldsObject (cyclomatic 35) Sources/Fuzzilli/Base/ProgramBuilder.swift:8433— ProgramBuilder.createTemporalFieldsObject 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.
ILType.intersection (cyclomatic 35) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1108— ILType.intersection has cyclomatic complexity 35 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OperationMutator.mutateDestructuringPattern (cyclomatic 35) Sources/Fuzzilli/Mutators/OperationMutator.swift:1193— OperationMutator.mutateDestructuringPattern 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.
ProgramBuilder.generateSubtype (cyclomatic 34) Sources/Fuzzilli/Base/ProgramBuilder.swift:7687— ProgramBuilder.generateSubtype 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.
MinimizationPostProcessor.process (cyclomatic 33) Sources/Fuzzilli/Minimization/MinimizationPostProcessor.swift:24— MinimizationPostProcessor.process has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WasmLifter.importAnalysis (cyclomatic 32) Sources/Fuzzilli/Lifting/WasmLifter.swift:1502— WasmLifter.importAnalysis has cyclomatic complexity 32 (threshold 15). Of this number, 30 points are the body's own statements and 2 belong to one function item 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.
Signature.subsumes (cyclomatic 30) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2791— Signature.subsumes 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.
VariadicInputReducer.reduce (cyclomatic 30) Sources/Fuzzilli/Minimization/VariadicInputReducer.swift:17— VariadicInputReducer.reduce 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.
ILType.union (cyclomatic 29) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:989— ILType.union 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.
FixupMutator.instrument (cyclomatic 29) Sources/Fuzzilli/Mutators/FixupMutator.swift:61— FixupMutator.instrument has cyclomatic complexity 29 (threshold 15). Of this number, 21 points are the body's own statements and 8 belong to 3 function items inside it that branch. 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.
OperationMutator.extendVariadicOperationByOneInput (cyclomatic 29) Sources/Fuzzilli/Mutators/OperationMutator.swift:1015— OperationMutator.extendVariadicOperationByOneInput has cyclomatic complexity 29 (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.
Instruction.asProtobuf::ILTypeToWasmTypeEnum (cyclomatic 28) Sources/Fuzzilli/FuzzIL/Instruction.swift:323— Instruction.asProtobuf::ILTypeToWasmTypeEnum has cyclomatic complexity 28 (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. This shape REPEATS in the file: one other method here (Instruction.asProtobuf) 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. This is NOT this file's highest cyclomatic complexity: Instruction.init::WasmTypeEnumToILType (cyclomatic 31) 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.
WasmFunction.generateRandomWasmVar (cyclomatic 26) Sources/Fuzzilli/Base/ProgramBuilder.swift:6240— WasmFunction.generateRandomWasmVar 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.
FixupMutator.process (cyclomatic 25) Sources/Fuzzilli/Mutators/FixupMutator.swift:280— FixupMutator.process 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.
Code.check (cyclomatic 24) Sources/Fuzzilli/FuzzIL/Code.swift:211— Code.check has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function item 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.
ILType.canMerge (cyclomatic 23) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1274— ILType.canMerge has cyclomatic complexity 23 (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.
WasmLifter.buildImportSection (cyclomatic 23) Sources/Fuzzilli/Lifting/WasmLifter.swift:727— WasmLifter.buildImportSection 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. This is NOT this file's highest cyclomatic complexity: WasmLifter.updateLifterState (cyclomatic 26) 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.
WasmTypeGroupReducer.reduce (cyclomatic 23) Sources/Fuzzilli/Minimization/WasmTypeGroupReducer.swift:31— WasmTypeGroupReducer.reduce has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ProgramBuilder.build (cyclomatic 22) Sources/Fuzzilli/Base/ProgramBuilder.swift:2239— ProgramBuilder.build 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.
JavaScriptCompiler.emitReassignment (cyclomatic 22) Sources/Fuzzilli/Compiler/Compiler.swift:978— JavaScriptCompiler.emitReassignment 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.
Kind.intersection (cyclomatic 22) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2397— Kind.intersection 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.
BlockReducer.reduce (cyclomatic 22) Sources/Fuzzilli/Minimization/BlockReducer.swift:17— BlockReducer.reduce has cyclomatic complexity 22 (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.
BlockReducer.reduceWasmIfElse (cyclomatic 22) Sources/Fuzzilli/Minimization/BlockReducer.swift:482— BlockReducer.reduceWasmIfElse 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.
ExplorationMutator.process (cyclomatic 22) Sources/Fuzzilli/Mutators/ExplorationMutator.swift:164— ExplorationMutator.process 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.
main.swift.makeFuzzer (cyclomatic 22) Sources/FuzzilliCli/main.swift:569— main.swift.makeFuzzer 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.
main.swift.top-level code (cyclomatic 21) Sources/FuzzILTool/main.swift:18— main.swift.top-level code 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.
Kind.union (cyclomatic 21) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2350— Kind.union 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.
Fuzzer.importProgramWithFixup (cyclomatic 20) Sources/Fuzzilli/Fuzzer.swift:675— Fuzzer.importProgramWithFixup 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.
JSTyper.processTypeChangesBeforeScopeChanges (cyclomatic 20) Sources/Fuzzilli/FuzzIL/JSTyper.swift:1569— JSTyper.processTypeChangesBeforeScopeChanges 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.
JSTyper.processDestructuring (cyclomatic 20) Sources/Fuzzilli/FuzzIL/JSTyper.swift:2895— JSTyper.processDestructuring 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.
WasmLifter.buildGlobalSection (cyclomatic 20) Sources/Fuzzilli/Lifting/WasmLifter.swift:1130— WasmLifter.buildGlobalSection 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. This is NOT this file's highest cyclomatic complexity: WasmLifter.updateLifterState (cyclomatic 26) 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.
Context.description (cyclomatic 19) Sources/Fuzzilli/FuzzIL/Context.swift:94— Context.description 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.
WasmModuleInterface.record (cyclomatic 19) Sources/Fuzzilli/FuzzIL/WasmModuleInterface.swift:91— WasmModuleInterface.record 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.
main.swift.checkNode (cyclomatic 19) Sources/FuzzilliDetectMissingBuiltins/main.swift:160— main.swift.checkNode 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.
Fuzzer.fuzzOne (cyclomatic 18) Sources/Fuzzilli/Fuzzer.swift:1082— Fuzzer.fuzzOne 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.
Constraint.fulfilled (cyclomatic 18) Sources/Fuzzilli/CodeGen/CodeGenerator.swift:93— Constraint.fulfilled 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.
InliningReducer.inline (cyclomatic 18) Sources/Fuzzilli/Minimization/InliningReducer.swift:153— InliningReducer.inline 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.
InstructionSimplifier.simplifyWasmInstructions (cyclomatic 18) Sources/Fuzzilli/Minimization/InstructionSimplifier.swift:370— InstructionSimplifier.simplifyWasmInstructions 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.
ExplorationMutator.instrument (cyclomatic 18) Sources/Fuzzilli/Mutators/ExplorationMutator.swift:70— ExplorationMutator.instrument 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.
Fuzzer.processMaybeInteresting (cyclomatic 17) Sources/Fuzzilli/Fuzzer.swift:858— Fuzzer.processMaybeInteresting has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to one function item 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.
Fuzzer.runStartupTests (cyclomatic 17) Sources/Fuzzilli/Fuzzer.swift:1265— Fuzzer.runStartupTests 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.
JavaScriptCompiler.compileObjectPattern (cyclomatic 17) Sources/Fuzzilli/Compiler/Compiler.swift:2220— JavaScriptCompiler.compileObjectPattern 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.
WasmLifter.buildTypeEntry (cyclomatic 17) Sources/Fuzzilli/Lifting/WasmLifter.swift:604— WasmLifter.buildTypeEntry 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. This is NOT this file's highest cyclomatic complexity: WasmLifter.updateLifterState (cyclomatic 26) 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.
DataFlowSimplifier.reduce (cyclomatic 17) Sources/Fuzzilli/Minimization/DataFlowSimplifier.swift:33— DataFlowSimplifier.reduce 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.
LoopSimplifier.tryMergeNestedRepeatLoops (cyclomatic 17) Sources/Fuzzilli/Minimization/LoopSimplifier.swift:352— LoopSimplifier.tryMergeNestedRepeatLoops 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.
Fuzzer.importProgram (cyclomatic 16) Sources/Fuzzilli/Fuzzer.swift:515— Fuzzer.importProgram 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.
ProgramBuilder.randomWasmFunctionSignatureTypeDef (cyclomatic 16) Sources/Fuzzilli/Base/ProgramBuilder.swift:7165— ProgramBuilder.randomWasmFunctionSignatureTypeDef 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.
ProgramBuilder.generateSubtypeStruct (cyclomatic 16) Sources/Fuzzilli/Base/ProgramBuilder.swift:7614— ProgramBuilder.generateSubtypeStruct 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.
MarkovCorpus.regenProgramList (cyclomatic 16) Sources/Fuzzilli/Corpus/MarkovCorpus.swift:112— MarkovCorpus.regenProgramList 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.
JSTyper.analyze (cyclomatic 16) Sources/Fuzzilli/FuzzIL/JSTyper.swift:772— JSTyper.analyze has cyclomatic complexity 16 (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.
DestructuringPattern.lift (cyclomatic 16) Sources/Fuzzilli/Lifting/Lifter.swift:42— DestructuringPattern.lift 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.
DestructAndReassign.init (cyclomatic 16) Sources/Fuzzilli/FuzzIL/JsOperations.swift:3797— DestructAndReassign.init has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function items inside it that branch (traverse, traverse::traverseTarget). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ProbingMutator.instrument (cyclomatic 16) Sources/Fuzzilli/Mutators/ProbingMutator.swift:68— ProbingMutator.instrument 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.
PropertyAccessorMutator.mutateProperty (cyclomatic 16) Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:154— PropertyAccessorMutator.mutateProperty 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.
HackComment Tests/FuzzilliTests/WasmTests.swift:4143— // hack to not confuse JS code extracting the result, as it always expects an array — 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.
JavaScriptLifter.lift (cognitive 555) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:127— JavaScriptLifter.lift has cognitive complexity 555 (threshold 15). Drivers by points: if/else 121 (267 pts), ternaries 62 (195 pts), loops 14 (41 pts), boolean chains 24, match/switch 6 (18 pts), error handling 3 (10 pts) (nesting depth added 325). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FuzzILLifter.lift (cognitive 301) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:26— FuzzILLifter.lift has cognitive complexity 301 (threshold 15). Drivers by points: ternaries 85 (168 pts), if/else 81 (120 pts), match/switch 4 (7 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 127). Of this number, 289 points are the body's own statements and 12 belong to 4 function items 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.
JavaScriptCompiler.compileExpression (cognitive 243) Sources/Fuzzilli/Compiler/Compiler.swift:1096— JavaScriptCompiler.compileExpression has cognitive complexity 243 (threshold 15). Drivers by points: if/else 79 (164 pts), match/switch 17 (50 pts), loops 7 (20 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 133). Of this number, 241 points are the body's own statements and 2 belong to one function item 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.
main.swift.top-level code (cognitive 182) Sources/FuzzilliCli/main.swift:21— main.swift.top-level code has cognitive complexity 182 (threshold 15). Drivers by points: if/else 94 (121 pts), boolean chains 48, ternaries 4 (6 pts), loops 4, error handling 1 (3 pts) (nesting depth added 31). 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.
JSTyper.processTypeChangesAfterScopeChanges (cognitive 158) Sources/Fuzzilli/FuzzIL/JSTyper.swift:1943— JSTyper.processTypeChangesAfterScopeChanges has cognitive complexity 158 (threshold 15). Drivers by points: if/else 59 (96 pts), ternaries 14 (29 pts), loops 10 (19 pts), boolean chains 7, match/switch 4 (7 pts) (nesting depth added 64). Of this number, 147 points are the body's own statements and 11 belong to 3 function items 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.
JavaScriptCompiler.compileStatement (cognitive 151) Sources/Fuzzilli/Compiler/Compiler.swift:367— JavaScriptCompiler.compileStatement has cognitive complexity 151 (threshold 15). Drivers by points: if/else 35 (75 pts), loops 15 (43 pts), match/switch 11 (28 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 86). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
V8CommonProfile.swift.v8ProcessArgs (cognitive 138) Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1347— V8CommonProfile.swift.v8ProcessArgs has cognitive complexity 138 (threshold 15). Drivers by points: if/else 83 (122 pts), ternaries 5 (9 pts), boolean chains 7 (nesting depth added 43). Of this number, 136 points are the body's own statements and 2 belong to one function item 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.
JSTyper.analyzeWasmInstruction (cognitive 123) Sources/Fuzzilli/FuzzIL/JSTyper.swift:843— JSTyper.analyzeWasmInstruction has cognitive complexity 123 (threshold 15). Drivers by points: if/else 41 (66 pts), loops 15 (31 pts), boolean chains 21, ternaries 2 (4 pts), match/switch 1 (nesting depth added 43). 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.
OperationMutator.mutateDestructuringPattern (cognitive 108) Sources/Fuzzilli/Mutators/OperationMutator.swift:1193— OperationMutator.mutateDestructuringPattern has cognitive complexity 108 (threshold 15). Drivers by points: if/else 30 (84 pts), loops 5 (14 pts), match/switch 3 (6 pts), boolean chains 4 (nesting depth added 66). 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.
WasmLifter.lift (cognitive 105) Sources/Fuzzilli/Lifting/WasmLifter.swift:1776— WasmLifter.lift has cognitive complexity 105 (threshold 15). Drivers by points: if/else 40 (58 pts), match/switch 11 (25 pts), ternaries 11 (22 pts) (nesting depth added 43). 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.
ILType.format (cognitive 100) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1548— ILType.format has cognitive complexity 100 (threshold 15). Drivers by points: if/else 42 (76 pts), ternaries 3 (8 pts), boolean chains 7, loops 3 (6 pts), match/switch 2 (3 pts) (nesting depth added 43). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OperationMutator.mutateOperation (cognitive 94) Sources/Fuzzilli/Mutators/OperationMutator.swift:61— OperationMutator.mutateOperation has cognitive complexity 94 (threshold 15). Drivers by points: if/else 36 (62 pts), boolean chains 12, match/switch 5 (10 pts), ternaries 3 (6 pts), loops 2 (4 pts) (nesting depth added 36). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Instruction.init (cognitive 84) Sources/Fuzzilli/FuzzIL/Instruction.swift:1984— Instruction.init has cognitive complexity 84 (threshold 15). Drivers by points: if/else 25 (40 pts), ternaries 13 (26 pts), match/switch 11 (16 pts), boolean chains 1, loops 1 (nesting depth added 33). Of this number, 65 points are the body's own statements and 19 belong to 7 function items 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.
ProgramBuilder.splice (cognitive 83) Sources/Fuzzilli/Base/ProgramBuilder.swift:1773— ProgramBuilder.splice has cognitive complexity 83 (threshold 15). Drivers by points: if/else 30 (56 pts), boolean chains 16, loops 7 (11 pts) (nesting depth added 30). Of this number, 66 points are the body's own statements and 17 belong to 5 function items 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.
ProgramBuilder.generateSubtype (cognitive 74) Sources/Fuzzilli/Base/ProgramBuilder.swift:7687— ProgramBuilder.generateSubtype has cognitive complexity 74 (threshold 15). Drivers by points: if/else 18 (52 pts), boolean chains 12, match/switch 3 (7 pts), ternaries 1 (3 pts) (nesting depth added 40). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
JavaScriptCompiler.compileClass (cognitive 70) Sources/Fuzzilli/Compiler/Compiler.swift:89— JavaScriptCompiler.compileClass has cognitive complexity 70 (threshold 15). Drivers by points: if/else 11 (25 pts), match/switch 9 (25 pts), loops 7 (17 pts), boolean chains 3 (nesting depth added 40). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasmFunction.generateRandomWasmVar (cognitive 62) Sources/Fuzzilli/Base/ProgramBuilder.swift:6240— WasmFunction.generateRandomWasmVar has cognitive complexity 62 (threshold 15). Drivers by points: if/else 13 (48 pts), boolean chains 5, loops 1 (5 pts), match/switch 2 (4 pts) (nesting depth added 41). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
WasmLifter.importAnalysis (cognitive 62) Sources/Fuzzilli/Lifting/WasmLifter.swift:1502— WasmLifter.importAnalysis has cognitive complexity 62 (threshold 15). Drivers by points: if/else 16 (40 pts), loops 6 (11 pts), match/switch 2 (6 pts), boolean chains 5 (nesting depth added 33). Of this number, 60 points are the body's own statements and 2 belong to one function item 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.
ProgramBuilder.build (cognitive 56) Sources/Fuzzilli/Base/ProgramBuilder.swift:2239— ProgramBuilder.build has cognitive complexity 56 (threshold 15). Drivers by points: if/else 17 (44 pts), boolean chains 5, loops 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Code.check (cognitive 56) Sources/Fuzzilli/FuzzIL/Code.swift:211— Code.check has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (46 pts), loops 4 (7 pts), ternaries 1 (3 pts) (nesting depth added 32). Of this number, 52 points are the body's own statements and 4 belong to one function item 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.
JSTyper.processScopeChanges (cognitive 54) Sources/Fuzzilli/FuzzIL/JSTyper.swift:1662— JSTyper.processScopeChanges has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (28 pts), ternaries 5 (19 pts), match/switch 3 (7 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProgramBuilder.generateTypeInternal (cognitive 51) Sources/Fuzzilli/Base/ProgramBuilder.swift:809— ProgramBuilder.generateTypeInternal has cognitive complexity 51 (threshold 15). Drivers by points: if/else 32 (41 pts), boolean chains 9, loops 1 (nesting depth added 9). Of this number, 39 points are the body's own statements and 12 belong to 2 function items inside it that branch. 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.
FixupMutator.process (cognitive 51) Sources/Fuzzilli/Mutators/FixupMutator.swift:280— FixupMutator.process has cognitive complexity 51 (threshold 15). Drivers by points: if/else 18 (39 pts), error handling 2 (6 pts), boolean chains 3, loops 3 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProgramBuilder.createTemporalFieldsObject (cognitive 50) Sources/Fuzzilli/Base/ProgramBuilder.swift:8433— ProgramBuilder.createTemporalFieldsObject has cognitive complexity 50 (threshold 15). Drivers by points: if/else 22 (40 pts), ternaries 2 (4 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MinimizationPostProcessor.process (cognitive 49) Sources/Fuzzilli/Minimization/MinimizationPostProcessor.swift:24— MinimizationPostProcessor.process has cognitive complexity 49 (threshold 15). Drivers by points: if/else 13 (33 pts), boolean chains 12, loops 2, match/switch 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExplorationMutator.process (cognitive 48) Sources/Fuzzilli/Mutators/ExplorationMutator.swift:164— ExplorationMutator.process has cognitive complexity 48 (threshold 15). Drivers by points: if/else 15 (34 pts), error handling 2 (8 pts), boolean chains 3, loops 3 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parse::visitStatement (cognitive 48) Sources/Fuzzilli/Compiler/Parser/parser.js:353— parse::visitStatement has cognitive complexity 48 (threshold 15). Drivers by points: if/else 23 (42 pts), error handling 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 21). 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.
InstructionSimplifier.simplifyMultiInstructions (cognitive 47) Sources/Fuzzilli/Minimization/InstructionSimplifier.swift:151— InstructionSimplifier.simplifyMultiInstructions has cognitive complexity 47 (threshold 15). Drivers by points: if/else 15 (28 pts), match/switch 6 (9 pts), boolean chains 5, loops 3 (5 pts) (nesting depth added 18). Of this number, 19 points are the body's own statements and 28 belong to 5 function items 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.
JavaScriptCompiler.emitReassignment (cognitive 43) Sources/Fuzzilli/Compiler/Compiler.swift:978— JavaScriptCompiler.emitReassignment has cognitive complexity 43 (threshold 15). Drivers by points: if/else 18 (37 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 21). 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.
Signature.subsumes (cognitive 43) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2791— Signature.subsumes has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 8, loops 4 (5 pts), match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataFlowSimplifier.reduce (cognitive 43) Sources/Fuzzilli/Minimization/DataFlowSimplifier.swift:33— DataFlowSimplifier.reduce has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (30 pts), loops 6 (13 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ILType.subsumes (cognitive 42) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:538— ILType.subsumes has cognitive complexity 42 (threshold 15). Drivers by points: if/else 22 (27 pts), boolean chains 14, loops 1 (nesting depth added 5). 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.
ILType.intersection (cognitive 42) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1108— ILType.intersection has cognitive complexity 42 (threshold 15). Drivers by points: if/else 22 (25 pts), boolean chains 14, loops 2, ternaries 1 (nesting depth added 3). 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.
ProgramBuilder.updateBuilderState (cognitive 41) Sources/Fuzzilli/Base/ProgramBuilder.swift:8102— ProgramBuilder.updateBuilderState has cognitive complexity 41 (threshold 15). Drivers by points: if/else 27 (40 pts), match/switch 1 (nesting depth added 13). 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.
JSTyper.processDestructuring (cognitive 41) Sources/Fuzzilli/FuzzIL/JSTyper.swift:2895— JSTyper.processDestructuring has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (31 pts), boolean chains 5, loops 2 (4 pts), match/switch 1 (nesting depth added 22). 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.
BlockReducer.reduceWasmIfElse (cognitive 39) Sources/Fuzzilli/Minimization/BlockReducer.swift:482— BlockReducer.reduceWasmIfElse has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 8, loops 3 (8 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Kind.intersection (cognitive 38) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2397— Kind.intersection has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (26 pts), boolean chains 7, match/switch 3 (5 pts) (nesting depth added 20). 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.
WasmLifter.buildImportSection (cognitive 38) Sources/Fuzzilli/Lifting/WasmLifter.swift:727— WasmLifter.buildImportSection has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 6 (18 pts), if/else 5 (10 pts), loops 4 (5 pts), match/switch 2 (5 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VariadicInputReducer.reduce (cognitive 37) Sources/Fuzzilli/Minimization/VariadicInputReducer.swift:17— VariadicInputReducer.reduce has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (31 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InstructionSimplifier.simplifyWasmInstructions (cognitive 36) Sources/Fuzzilli/Minimization/InstructionSimplifier.swift:370— InstructionSimplifier.simplifyWasmInstructions has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (25 pts), loops 3 (5 pts), ternaries 1 (3 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LoopSimplifier.tryMergeNestedRepeatLoops (cognitive 34) Sources/Fuzzilli/Minimization/LoopSimplifier.swift:352— LoopSimplifier.tryMergeNestedRepeatLoops has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 4 (14 pts), if/else 7 (12 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.swift.top-level code (cognitive 33) Sources/FuzzILTool/main.swift:18— main.swift.top-level code has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (17 pts), error handling 6 (14 pts), boolean chains 2 (nesting depth added 11). 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.
WasmTypeGroupReducer.reduce (cognitive 33) Sources/Fuzzilli/Minimization/WasmTypeGroupReducer.swift:31— WasmTypeGroupReducer.reduce has cognitive complexity 33 (threshold 15). Drivers by points: loops 7 (14 pts), if/else 9 (13 pts), boolean chains 6 (nesting depth added 11). Of this number, 31 points are the body's own statements and 2 belong to one function item 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.
Instruction.asProtobuf (cognitive 32) Sources/Fuzzilli/FuzzIL/Instruction.swift:303— Instruction.asProtobuf has cognitive complexity 32 (threshold 15). Drivers by points: if/else 19 (33 pts), match/switch 10 (17 pts), ternaries 1 (4 pts), loops 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent 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 (Instruction.asProtobuf::ILTypeToWasmTypeEnum) 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.
DestructuringPattern.lift (cognitive 32) Sources/Fuzzilli/Lifting/Lifter.swift:42— DestructuringPattern.lift has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 2 (4 pts), match/switch 2 (4 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 17). 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.
ProbingMutator.instrument (cognitive 32) Sources/Fuzzilli/Mutators/ProbingMutator.swift:68— ProbingMutator.instrument has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Kind.union (cognitive 31) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:2350— Kind.union has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (18 pts), boolean chains 8, match/switch 3 (5 pts) (nesting depth added 14). 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.
WasmLifter.buildGlobalSection (cognitive 31) Sources/Fuzzilli/Lifting/WasmLifter.swift:1130— WasmLifter.buildGlobalSection has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 3 (12 pts), if/else 6 (9 pts), match/switch 2 (7 pts), loops 2 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InliningReducer.inline (cognitive 31) Sources/Fuzzilli/Minimization/InliningReducer.swift:153— InliningReducer.inline has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 6, ternaries 1 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExplorationMutator.instrument (cognitive 31) Sources/Fuzzilli/Mutators/ExplorationMutator.swift:70— ExplorationMutator.instrument has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 5 (8 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ILType.union (cognitive 30) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:989— ILType.union has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 11, ternaries 5, loops 1 (nesting depth added 1). 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.
JavaScriptCompiler.compileObjectPattern (cognitive 29) Sources/Fuzzilli/Compiler/Compiler.swift:2220— JavaScriptCompiler.compileObjectPattern has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (22 pts), match/switch 3 (6 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JavaScriptEnvironment.registerObjectGroup (cognitive 29) Sources/Fuzzilli/Environment/JavaScriptEnvironment.swift:990— JavaScriptEnvironment.registerObjectGroup has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 6 (14 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Fuzzer.importProgramWithFixup (cognitive 28) Sources/Fuzzilli/Fuzzer.swift:675— Fuzzer.importProgramWithFixup has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 2 (3 pts), match/switch 3, boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JavaScriptCompiler.convertParameterDestructuringPattern (cognitive 28) Sources/Fuzzilli/Compiler/Compiler.swift:1992— JavaScriptCompiler.convertParameterDestructuringPattern has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 4 (10 pts), loops 2 (4 pts) (nesting depth added 13). 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.
DeduplicatingReducer.reduce (cognitive 28) Sources/Fuzzilli/Minimization/DeduplicatingReducer.swift:17— DeduplicatingReducer.reduce has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProgramBuilder.generateSubtypeStruct (cognitive 27) Sources/Fuzzilli/Base/ProgramBuilder.swift:7614— ProgramBuilder.generateSubtypeStruct has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (16 pts), boolean chains 7, match/switch 1 (3 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasmLifter.buildTypeEntry (cognitive 27) Sources/Fuzzilli/Lifting/WasmLifter.swift:604— WasmLifter.buildTypeEntry has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 4 (9 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalUI.printWarnings (cognitive 27) Sources/FuzzilliCli/TerminalUI.swift:197— TerminalUI.printWarnings has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Fuzzer.processMaybeInteresting (cognitive 26) Sources/Fuzzilli/Fuzzer.swift:858— Fuzzer.processMaybeInteresting has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 3, ternaries 2 (3 pts), loops 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 10 belong to one function item 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.
WasmModuleInterface.record (cognitive 26) Sources/Fuzzilli/FuzzIL/WasmModuleInterface.swift:91— WasmModuleInterface.record has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 2 (4 pts), match/switch 2, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Statistics.initialize (cognitive 26) Sources/Fuzzilli/Modules/Statistics.swift:227— Statistics.initialize has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 4 (10 pts), ternaries 1 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Fuzzer.removeCallsTo (cognitive 25) Sources/Fuzzilli/Fuzzer.swift:616— Fuzzer.removeCallsTo has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 1 (3 pts), loops 2, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 11). Of this number, 15 points are the body's own statements and 10 belong to one function item 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.
Constraint.fulfilled (cognitive 25) Sources/Fuzzilli/CodeGen/CodeGenerator.swift:93— Constraint.fulfilled has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (24 pts), match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InliningReducer.identifyInlineableFunctions (cognitive 24) Sources/Fuzzilli/Minimization/InliningReducer.swift:33— InliningReducer.identifyInlineableFunctions has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (4 pts), ternaries 1 (3 pts), loops 2, boolean chains 1 (nesting depth added 12). Of this number, 23 points are the body's own statements and 1 belongs to one function item 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.
Action.translateToFuzzIL (cognitive 24) Sources/Fuzzilli/Mutators/RuntimeAssistedMutator.swift:386— Action.translateToFuzzIL has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 7 (13 pts), if/else 9 (10 pts), boolean chains 1 (nesting depth added 7). Of this number, 22 points are the body's own statements and 2 belong to 2 function items inside it that branch. 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.
main.swift.checkNode (cognitive 24) Sources/FuzzilliDetectMissingBuiltins/main.swift:160— main.swift.checkNode has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 8, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
REPRL.run (cognitive 22) Sources/Fuzzilli/Execution/REPRL.swift:91— REPRL.run has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (18 pts), ternaries 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ILType.canMerge (cognitive 22) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1274— ILType.canMerge has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 14, if/else 8. 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.
Fuzzer.runStartupTests (cognitive 21) Sources/Fuzzilli/Fuzzer.swift:1265— Fuzzer.runStartupTests has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 2, match/switch 1 (2 pts), error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProgramBuilder.complete (cognitive 21) Sources/Fuzzilli/Base/ProgramBuilder.swift:2488— ProgramBuilder.complete has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 5 (7 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DestructuringPattern.numExtraInputs (cognitive 21) Sources/Fuzzilli/FuzzIL/JsOperations.swift:3694— DestructuringPattern.numExtraInputs has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (4 pts), match/switch 2 (nesting depth added 11). Of this number, 19 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
DestructAndReassign.init::traverse (cognitive 21) Sources/Fuzzilli/FuzzIL/JsOperations.swift:3802— DestructAndReassign.init::traverse has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 12). 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.
main.swift.makeFuzzer (cognitive 21) Sources/FuzzilliCli/main.swift:569— main.swift.makeFuzzer has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (16 pts), match/switch 2, boolean chains 1, loops 1, ternaries 1 (nesting depth added 1). 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.
MarkovCorpus.regenProgramList (cognitive 20) Sources/Fuzzilli/Corpus/MarkovCorpus.swift:112— MarkovCorpus.regenProgramList has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, loops 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasmLifter.buildCodeSection (cognitive 20) Sources/Fuzzilli/Lifting/WasmLifter.swift:992— WasmLifter.buildCodeSection has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 4 (8 pts), ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PropertyAccessorMutator.mutate (cognitive 20) Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:95— PropertyAccessorMutator.mutate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 3, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PropertyAccessorMutator.mutateProperty (cognitive 20) Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:154— PropertyAccessorMutator.mutateProperty has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 5 (6 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 7). 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.
Fuzzer.fuzzOne (cognitive 19) Sources/Fuzzilli/Fuzzer.swift:1082— Fuzzer.fuzzOne has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 2, boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProgramBuilder.createRequiredInputVariables (cognitive 19) Sources/Fuzzilli/Base/ProgramBuilder.swift:2720— ProgramBuilder.createRequiredInputVariables has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContextGraph.getShortestPath (cognitive 18) Sources/Fuzzilli/Base/ContextGraph.swift:143— ContextGraph.getShortestPath has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProgramBuilder.assertWasmCustomDescriptorsSubtypingRules (cognitive 18) Sources/Fuzzilli/Base/ProgramBuilder.swift:7404— ProgramBuilder.assertWasmCustomDescriptorsSubtypingRules has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Context.description (cognitive 18) Sources/Fuzzilli/FuzzIL/Context.swift:94— Context.description has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17, ternaries 1. 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.
Instruction.asProtobuf::ILTypeToWasmTypeEnum (cognitive 18) Sources/Fuzzilli/FuzzIL/Instruction.swift:323— Instruction.asProtobuf::ILTypeToWasmTypeEnum has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 5 (6 pts), ternaries 1 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent 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 (Instruction.asProtobuf) 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.
DestructuringPattern.numBindings (cognitive 18) Sources/Fuzzilli/FuzzIL/JsOperations.swift:3728— DestructuringPattern.numBindings has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (9 pts), if/else 4 (5 pts), loops 2 (4 pts) (nesting depth added 8). 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.
ReassignmentReducer.reduce (cognitive 18) Sources/Fuzzilli/Minimization/ReassignReducer.swift:45— ReassignmentReducer.reduce has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DistributedFuzzingNode.synchronizeState (cognitive 18) Sources/Fuzzilli/Modules/Sync.swift:157— DistributedFuzzingNode.synchronizeState has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 4 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DistributedFuzzingParentNode.onMessageReceived (cognitive 18) Sources/Fuzzilli/Modules/Sync.swift:256— DistributedFuzzingParentNode.onMessageReceived has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 2 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 7). 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.
ProbingMutator.process (cognitive 18) Sources/Fuzzilli/Mutators/ProbingMutator.swift:125— ProbingMutator.process has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SandboxFuzzingPostProcessor.process::corruptSomething (cognitive 18) Sources/Fuzzilli/Profiles/V8SandboxProfile.swift:30— SandboxFuzzingPostProcessor.process::corruptSomething has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (6 pts), ternaries 2 (6 pts), match/switch 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Fuzzer.importProgram (cognitive 17) Sources/Fuzzilli/Fuzzer.swift:515— Fuzzer.importProgram has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, match/switch 1, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasmLifter.buildTypeSection (cognitive 17) Sources/Fuzzilli/Lifting/WasmLifter.swift:647— WasmLifter.buildTypeSection has cognitive complexity 17 (threshold 15). Drivers by points: loops 8 (12 pts), if/else 4 (5 pts) (nesting depth added 5). 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.
WasmLifter.buildElementSection (cognitive 17) Sources/Fuzzilli/Lifting/WasmLifter.swift:919— WasmLifter.buildElementSection has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (8 pts), if/else 5 (6 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DistributedFuzzingChildNode.onMessageReceived (cognitive 17) Sources/Fuzzilli/Modules/Sync.swift:443— DistributedFuzzingChildNode.onMessageReceived has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 2 (4 pts), match/switch 1 (nesting depth added 8). 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.
Instruction.swift.decodeDestructuringPattern (cognitive 17) Sources/Fuzzilli/FuzzIL/Instruction.swift:3460— Instruction.swift.decodeDestructuringPattern has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (4 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 7). 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.
JavaScriptEnvironment.removeProducersThatCannotBeProduced (cognitive 16) Sources/Fuzzilli/Environment/JavaScriptEnvironment.swift:822— JavaScriptEnvironment.removeProducersThatCannotBeProduced has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 6 (7 pts), boolean chains 2 (nesting depth added 5). Of this number, 12 points are the body's own statements and 4 belong to 2 function items 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.
AnalyzerState.computeVariableTypes (cognitive 16) Sources/Fuzzilli/FuzzIL/JSTyper.swift:3329— AnalyzerState.computeVariableTypes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Statistics.compute (cognitive 16) Sources/Fuzzilli/Modules/Statistics.swift:86— Statistics.compute has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (5 pts), loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodeGenMutator.mutate (cognitive 16) Sources/Fuzzilli/Mutators/CodeGenMutator.swift:53— CodeGenMutator.mutate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 6, ternaries 1 (2 pts), match/switch 1 (nesting depth added 4). 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.
FixupMutator.instrument (cognitive 16) Sources/Fuzzilli/Mutators/FixupMutator.swift:61— FixupMutator.instrument has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (fixup, maybeFixup, fixupIfGuarded). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
OperationMutator.extendVariadicOperationByOneInput (cognitive 16) Sources/Fuzzilli/Mutators/OperationMutator.swift:1015— OperationMutator.extendVariadicOperationByOneInput has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 3 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Instruction.swift.encodeDestructuringPattern (cognitive 16) Sources/Fuzzilli/FuzzIL/Instruction.swift:3404— Instruction.swift.encodeDestructuringPattern has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 7). 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.
Change-coupling hub: VariadicInputReducer.swift → ProgramBuilder.swift, JSTyper.swift, FuzzILLifter.swift, OperationMutator.swift Sources/Fuzzilli/Minimization/VariadicInputReducer.swift— `Sources/Fuzzilli/Minimization/VariadicInputReducer.swift` changes together with 4 other files — `Sources/Fuzzilli/Base/ProgramBuilder.swift`, `Sources/Fuzzilli/FuzzIL/JSTyper.swift`, `Sources/Fuzzilli/Lifting/FuzzILLifter.swift`, `Sources/Fuzzilli/Mutators/OperationMutator.swift` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) Sources/Fuzzilli/Base/ProgramBuilder.swift:3079— Sources/Fuzzilli/Base/ProgramBuilder.swift:3079-3093 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3095-3108 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3335-3349 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3351-3365 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3424-3438 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3440-3454 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3493-3507 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3516-3530 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) Sources/Fuzzilli/Base/ProgramBuilder.swift:3933— Sources/Fuzzilli/Base/ProgramBuilder.swift:3933-3946 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3948-3963 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3979-3992 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3994-4007 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4023-4037 — 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 (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:5945— Sources/Fuzzilli/Base/ProgramBuilder.swift:5945-5968 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5972-5999 — 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 copy of a member (49 corresponding lines) · ×1
Edited copy of a member (49 corresponding lines) Sources/Fuzzilli/Minimization/LoopSimplifier.swift:145— Sources/Fuzzilli/Minimization/LoopSimplifier.swift:145-193 | Sources/Fuzzilli/Minimization/LoopSimplifier.swift:195-243 — 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 (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) Sources/Fuzzilli/Lifting/WasmLifter.swift:862— Sources/Fuzzilli/Lifting/WasmLifter.swift:862-898 | Sources/Fuzzilli/Lifting/WasmLifter.swift:1210-1243 — 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 (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:300— Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:300-327 | Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:329-359 — 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 copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:3646— Sources/Fuzzilli/Base/ProgramBuilder.swift:3646-3668 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3711-3733 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3772-3794 — 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 copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) Sources/Fuzzilli/Lifting/WasmLifter.swift:833— Sources/Fuzzilli/Lifting/WasmLifter.swift:833-860 | Sources/Fuzzilli/Lifting/WasmLifter.swift:1245-1270 — 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 copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:5761— Sources/Fuzzilli/Base/ProgramBuilder.swift:5761-5778 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6022-6036 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6221-6238 — 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 copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:2063— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:2063-2083 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2542-2564 — 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 copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:4171— Sources/Fuzzilli/Base/ProgramBuilder.swift:4171-4189 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4224-4242 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4463-4485 — 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, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:5628— Sources/Fuzzilli/Base/ProgramBuilder.swift:5628-5643 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5681-5699 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5701-5717 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 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, 16+ corresponding lines) · ×1
Edited copies of one member (4 members, 16+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:5866— Sources/Fuzzilli/Base/ProgramBuilder.swift:5866-5883 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5885-5900 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5902-5917 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5919-5936 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 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, 13+ corresponding lines) · ×1
Edited copies of one member (5 members, 13+ corresponding lines) Sources/Fuzzilli/FuzzIL/JsOperations.swift:496— Sources/Fuzzilli/FuzzIL/JsOperations.swift:496-510 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:524-536 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:761-777 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:790-803 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:936-953 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:3254— Sources/Fuzzilli/Base/ProgramBuilder.swift:3254-3273 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3275-3294 — 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, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1467— Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1467-1479 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1482-1496 | Sources/Fuzzilli/FuzzIL/TypeSystem.swift:1504-1518 — 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 (8 members, 10+ corresponding lines) · ×1
Edited copies of one member (8 members, 10+ corresponding lines) Sources/Fuzzilli/CodeGen/CodeGenerator.swift:389— Sources/Fuzzilli/CodeGen/CodeGenerator.swift:389-398 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:400-409 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:411-420 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:422-431 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:542-557 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:575-590 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:592-607 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:609-624 — These 8 members are one piece of code written 8 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 8 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:6556— Sources/Fuzzilli/Base/ProgramBuilder.swift:6556-6566 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6568-6580 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6582-6593 — 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 (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:6634— Sources/Fuzzilli/Base/ProgramBuilder.swift:6634-6646 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6671-6682 | Sources/Fuzzilli/Base/ProgramBuilder.swift:6684-6696 — 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 copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) Sources/Fuzzilli/FuzzIL/JSTyper.swift:1455— Sources/Fuzzilli/FuzzIL/JSTyper.swift:1455-1471 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:1479-1514 — 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· Edited copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) Sources/Fuzzilli/CodeGen/CodeGenerator.swift:371— Sources/Fuzzilli/CodeGen/CodeGenerator.swift:371-378 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:380-387 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:511-524 | Sources/Fuzzilli/CodeGen/CodeGenerator.swift:526-540 — 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, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:8665— Sources/Fuzzilli/Base/ProgramBuilder.swift:8665-8682 | Sources/Fuzzilli/Base/ProgramBuilder.swift:8683-8700 | Sources/Fuzzilli/Base/ProgramBuilder.swift:8702-8715 | Sources/Fuzzilli/Base/ProgramBuilder.swift:8733-8747 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:5645— Sources/Fuzzilli/Base/ProgramBuilder.swift:5645-5652 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5654-5668 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5719-5731 — 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 copies of one member (6 members, 11+ corresponding lines) · ×1
Edited copies of one member (6 members, 11+ corresponding lines) Sources/Fuzzilli/FuzzIL/JsOperations.swift:1724— Sources/Fuzzilli/FuzzIL/JsOperations.swift:1724-1734 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:1814-1826 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:1863-1878 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:1962-1976 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:2305-2318 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:2355-2369 — These 6 members are one piece of code written 6 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 6 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) Sources/Fuzzilli/Base/ProgramBuilder.swift:3122— Sources/Fuzzilli/Base/ProgramBuilder.swift:3122-3127 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3129-3135 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3381-3387 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3389-3395 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3469-3475 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3477-3483 — 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 copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) Sources/Fuzzilli/Mutators/CodeGenMutator.swift:34— Sources/Fuzzilli/Mutators/CodeGenMutator.swift:34-51 | Sources/Fuzzilli/Mutators/SpliceMutator.swift:27-44 — 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· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:4334— Sources/Fuzzilli/Base/ProgramBuilder.swift:4334-4343 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4345-4355 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:2727-2736 — 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 (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) Sources/Fuzzilli/Base/ProgramBuilder.swift:5109— Sources/Fuzzilli/Base/ProgramBuilder.swift:5109-5117 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5151-5159 | Sources/Fuzzilli/Base/ProgramBuilder.swift:5185-5193 — 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 (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) Sources/Fuzzilli/FuzzIL/JsOperations.swift:2225— Sources/Fuzzilli/FuzzIL/JsOperations.swift:2225-2234 | Sources/Fuzzilli/FuzzIL/WasmOperations.swift:2926-2935 | Sources/Fuzzilli/FuzzIL/WasmOperations.swift:2950-2959 | Sources/Fuzzilli/FuzzIL/WasmOperations.swift:2969-2978 | Sources/Fuzzilli/FuzzIL/WasmOperations.swift:3020-3029 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) Sources/Fuzzilli/FuzzIL/JsOperations.swift:3156— Sources/Fuzzilli/FuzzIL/JsOperations.swift:3156-3159 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:3169-3174 | Sources/Fuzzilli/FuzzIL/WasmOperations.swift:1077-1080 — 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.
Duplicated block (36 lines × 2) Sources/Fuzzilli/Engines/HybridEngine.swift:173— Sources/Fuzzilli/Engines/HybridEngine.swift:173-208 | Sources/Fuzzilli/Engines/MutationEngine.swift:52-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 `Sources/Fuzzilli/Engines/HybridEngine.swift:173` 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–28 lines × 6) Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1391— Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1391-1407 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1420-1440 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1444-1471 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1484-1495 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1525-1542 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1615-1630 — 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 `Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1391` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1444` calls `probability` and `Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1484` 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 (12–23 lines × 7) Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1391— Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1391-1405 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1420-1438 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1444-1466 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1483-1494 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1528-1542 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1601-1612 | Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1615-1632 — all 7 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 `Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1420` 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, `Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1613` calls `contains`, `probability` and `Sources/Fuzzilli/Profiles/V8CommonProfile.swift:1407` 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 (22 lines × 2) Sources/Fuzzilli/Compiler/Compiler.swift:745— Sources/Fuzzilli/Compiler/Compiler.swift:745-766 | Sources/Fuzzilli/Compiler/Compiler.swift:776-797 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 3) Sources/Fuzzilli/Compiler/Compiler.swift:2242— Sources/Fuzzilli/Compiler/Compiler.swift:2242-2259 | Sources/Fuzzilli/Compiler/Compiler.swift:2314-2331 | Sources/Fuzzilli/Compiler/Compiler.swift:2349-2366 — 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 `Sources/Fuzzilli/Compiler/Compiler.swift:2242` 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 (18 lines × 2) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:2044— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:2044-2061 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2283-2300 — 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 `Sources/Fuzzilli/Lifting/FuzzILLifter.swift:2044` 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 (3–16 lines × 4) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2015— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2015-2030 | Sources/Fuzzilli/Lifting/WasmLifter.swift:1602-1605 | Sources/Fuzzilli/Lifting/WasmLifter.swift:2526-2528 | Sources/Fuzzilli/Mutators/OperationMutator.swift:882-897 — there are 4 copies across 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2015` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2088— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2088-2103 | Sources/Fuzzilli/Mutators/OperationMutator.swift:915-930 — 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 `Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2088` 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 before the matched lines, `Sources/Fuzzilli/Mutators/OperationMutator.swift:913` calls `wasmTableSize`, `wasmTableGrow` and `Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:2087` 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 (14–16 lines × 2) Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:306— Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:306-319 | Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift:336-351 — 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–12 lines × 3) Sources/Fuzzilli/Lifting/WasmLifter.swift:2244— Sources/Fuzzilli/Lifting/WasmLifter.swift:2244-2252 | Sources/Fuzzilli/Lifting/WasmLifter.swift:2257-2266 | Sources/Fuzzilli/Lifting/WasmLifter.swift:2271-2282 — 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 `Sources/Fuzzilli/Lifting/WasmLifter.swift:2244` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. 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) Sources/Fuzzilli/Compiler/Compiler.swift:307— Sources/Fuzzilli/Compiler/Compiler.swift:307-318 | Sources/Fuzzilli/Compiler/Compiler.swift:1401-1411 — 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 `Sources/Fuzzilli/Compiler/Compiler.swift: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 (4–10 lines × 4) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1551— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1551-1560 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1570-1573 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1581-1584 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1588-1597 — 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 `Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1551` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 4) Sources/Fuzzilli/FuzzIL/JSTyper.swift:1267— Sources/Fuzzilli/FuzzIL/JSTyper.swift:1267-1274 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:1294-1301 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:1322-1329 | Sources/Fuzzilli/FuzzIL/JSTyper.swift:1352-1359 — 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 (8 lines × 3) Sources/Fuzzilli/FuzzIL/JsOperations.swift:766— Sources/Fuzzilli/FuzzIL/JsOperations.swift:766-773 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:791-798 | Sources/Fuzzilli/FuzzIL/JsOperations.swift:941-949 — 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 `Sources/Fuzzilli/FuzzIL/JsOperations.swift:766` 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–8 lines × 2) Sources/Fuzzilli/Minimization/BlockReducer.swift:283— Sources/Fuzzilli/Minimization/BlockReducer.swift:283-289 | Sources/Fuzzilli/Minimization/BlockReducer.swift:512-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.
Duplicated block (6 lines × 8) Sources/Fuzzilli/Base/ProgramBuilder.swift:3081— Sources/Fuzzilli/Base/ProgramBuilder.swift:3081-3086 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3097-3102 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3337-3342 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3353-3358 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3426-3431 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3442-3447 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3495-3500 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3518-3523 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:3081` 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 (6 lines × 5) Sources/Fuzzilli/Base/ProgramBuilder.swift:3935— Sources/Fuzzilli/Base/ProgramBuilder.swift:3935-3940 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3950-3956 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3981-3986 | Sources/Fuzzilli/Base/ProgramBuilder.swift:3996-4001 | Sources/Fuzzilli/Base/ProgramBuilder.swift:4025-4030 — 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 `Sources/Fuzzilli/Base/ProgramBuilder.swift:3935` 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 × 5) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1390— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1390-1397 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1407-1414 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1436-1443 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1468-1475 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1631-1638 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1085— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1085-1090 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1124-1128 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1335-1339 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (4–5 lines × 3) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:170— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:170-173 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:287-291 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:373-377 — 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 `Sources/Fuzzilli/Lifting/FuzzILLifter.swift: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/Fuzzilli/Lifting/FuzzILLifter.swift:173` calls `emit` and `Sources/Fuzzilli/Lifting/FuzzILLifter.swift:291` 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 (4–5 lines × 5) Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:483— Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:483-487 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:590-593 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:645-649 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:726-729 | Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:1029-1032 — 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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `op` to `instr.innerOutput(0)) case .beginObjectLiteralSetter(let` in one and `instr.innerOutput(0)) case .beginClassComputedSetter(let` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:483` calls `enumerated` and `Sources/Fuzzilli/Lifting/JavaScriptLifter.swift:590` 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 (3–5 lines × 3) Sources/Fuzzilli/Minimization/BlockReducer.swift:357— Sources/Fuzzilli/Minimization/BlockReducer.swift:357-359 | Sources/Fuzzilli/Minimization/BlockReducer.swift:550-554 | Sources/Fuzzilli/Minimization/BlockReducer.swift:580-584 — 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 `Sources/Fuzzilli/Minimization/BlockReducer.swift:357` 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 × 4) Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1383— Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1383-1387 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1400-1404 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1446-1450 | Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1624-1628 — 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 (15 lines × 2 locations) Sources/Fuzzilli/Compiler/Parser/parser.js:372— Sources/Fuzzilli/Compiler/Parser/parser.js:372 · Sources/Fuzzilli/Compiler/Parser/parser.js:725 — 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 locations) Sources/Fuzzilli/Compiler/Parser/parser.js:80— Sources/Fuzzilli/Compiler/Parser/parser.js:80 · Sources/Fuzzilli/Compiler/Parser/parser.js:544 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 3 locations) Sources/Fuzzilli/Compiler/Parser/parser.js:306— Sources/Fuzzilli/Compiler/Parser/parser.js:306 · Sources/Fuzzilli/Compiler/Parser/parser.js:372 · Sources/Fuzzilli/Compiler/Parser/parser.js:725 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Complex function visitExpression (cyclomatic 54, cognitive 48) Sources/Fuzzilli/Compiler/Parser/parser.js:612— visitExpression has cyclomatic complexity 54 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function visitStatement (cyclomatic 45, cognitive 48) Sources/Fuzzilli/Compiler/Parser/parser.js:353— visitStatement has cyclomatic complexity 45 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (top-level) (cyclomatic 20, cognitive 35) Tests/FuzzilliTests/CompilerTests/labels.js:1— (top-level) has cyclomatic complexity 20 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function visitClass (cyclomatic 20, cognitive 30) Sources/Fuzzilli/Compiler/Parser/parser.js:271— visitClass has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function runAsyncTests (cyclomatic 18, cognitive 17) Tests/FuzzilliTests/CompilerTests/advanced_loops.js:209— runAsyncTests has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parsePattern (cyclomatic 16, cognitive 39) Sources/Fuzzilli/Compiler/Parser/parser.js:146— parsePattern has cyclomatic complexity 16 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (top-level) (cyclomatic 14, cognitive 15) Tests/FuzzilliTests/CompilerTests/basic_control_flow.js:1— (top-level) has cyclomatic complexity 14 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· Sources/Fuzzilli/Compiler/Parser/parser.js · ×1
Sources/Fuzzilli/Compiler/Parser/parser.js: 795 lines of code Sources/Fuzzilli/Compiler/Parser/parser.js:1— Sources/Fuzzilli/Compiler/Parser/parser.js has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked Sources/Fuzzilli/Compiler/Parser/package.json:2— Sources/Fuzzilli/Compiler/Parser/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
Orphaned file Sources/Fuzzilli/DumplingDiffOracle/Oracle.swift: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 Sources/Fuzzilli/Util/VariableSet.swift: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 Sources/Fuzzilli/Modules/ThreadSync.swift: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 Sources/Fuzzilli/Protobuf/ProtoUtils.swift: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 Sources/Fuzzilli/FuzzIL/Blocks.swift: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 Sources/Fuzzilli/Execution/Execution.swift: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 Sources/Fuzzilli/Util/VariableMap.swift: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 Sources/Fuzzilli/Util/Arguments.swift: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 Sources/Fuzzilli/Lifting/Expression.swift: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 Sources/Fuzzilli/Util/Random.swift: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 Sources/Fuzzilli/Lifting/JSExpressions.swift: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 Sources/RelateTool/main.swift: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 Sources/Fuzzilli/Compiler/JavaScriptParser.swift: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 Sources/Fuzzilli/Base/Timers.swift: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 Sources/Fuzzilli/Base/ProgramOrigin.swift: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 Sources/Fuzzilli/Base/Logging.swift: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.
Duplicated predicate Sources/Fuzzilli/Corpus/RarityCorpus.swift:93— `!ageExponent.isFinite || ageExponent < 0.0` appears character-identically in 2 files — Sources/Fuzzilli/Corpus/RarityCorpus.swift, Sources/FuzzilliCli/main.swift. 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 Sources/Fuzzilli/Corpus/RarityCorpus.swift:99— `!rarityExponent.isFinite || rarityExponent < 0.0` appears character-identically in 2 files — Sources/Fuzzilli/Corpus/RarityCorpus.swift, Sources/FuzzilliCli/main.swift. 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 Sources/Fuzzilli/Corpus/RarityCorpus.swift:96— `!sizeExponent.isFinite || sizeExponent < 0.0` appears character-identically in 2 files — Sources/Fuzzilli/Corpus/RarityCorpus.swift, Sources/FuzzilliCli/main.swift. 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 Sources/Fuzzilli/Mutators/CodeGenMutator.swift:42— `(instr.op.requiredContext.contains(.wasmTypeGroup) && !(instr.op is WasmEndTypeGroup)) || (instr.op is WasmBeginTypeGroup)` appears character-identically in 2 files — Sources/Fuzzilli/Mutators/CodeGenMutator.swift, Sources/Fuzzilli/Mutators/SpliceMutator.swift. 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 Sources/FuzzILTool/main.swift:101— `args["-h"] != nil || args["--help"] != nil || args.numPositionalArguments != 1` appears character-identically in 2 files — Sources/FuzzILTool/main.swift, Sources/FuzzilliCli/main.swift. 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 Sources/Fuzzilli/Lifting/FuzzILLifter.swift:1981— `index == indices.last! && hasRestElement` appears character-identically in 2 files — Sources/Fuzzilli/Lifting/FuzzILLifter.swift, Sources/Fuzzilli/Lifting/JavaScriptLifter.swift. 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 Sources/Fuzzilli/Mutators/ExplorationMutator.swift:84— `instr.op is WasmOperation || instr.op is WasmTypeOperation` appears character-identically in 2 files — Sources/Fuzzilli/Mutators/ExplorationMutator.swift, Sources/Fuzzilli/Mutators/ProbingMutator.swift. 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 Sources/Fuzzilli/Lifting/FuzzILLifter.swift:76— `parameters.hasRestParameter && i == parameters.count - 1` appears character-identically in 2 files — Sources/Fuzzilli/Lifting/FuzzILLifter.swift, Sources/Fuzzilli/Lifting/JavaScriptLifter.swift. 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 Sources/Fuzzilli/Base/ProgramBuilder.swift:3235— `probability(0.5) && b.hasVisibleJsVariables` appears character-identically in 2 files — Sources/Fuzzilli/Base/ProgramBuilder.swift, Sources/Fuzzilli/CodeGen/CodeGenerators.swift. 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 Sources/Fuzzilli/Corpus/RarityCorpus.swift:90— `rareEdgeLimit < 1 || rareEdgeLimit >= Int(UInt8.max)` appears character-identically in 2 files — Sources/Fuzzilli/Corpus/RarityCorpus.swift, Sources/FuzzilliCli/main.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
README/code drift Targets/README.md:59— Targets/README.md links to `../Sources/FuzzilliCli/Profiles/Profile.swift`, but `Sources/FuzzilliCli/Profiles/Profile.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Targets/README.md:71— Targets/README.md links to `../Sources/Fuzzilli/CodeGen/CodeGeneratorsWeights.swift`, but `Sources/Fuzzilli/CodeGen/CodeGeneratorsWeights.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: Sources/Fuzzilli/Corpus/RarityCorpus.swift, Tools/transpile_tests/setup_test262.py. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 3 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 (6 single-owned of 106 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; 106 of the 146 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (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: Sources/Fuzzilli/Mutators/PropertyAccessorMutator.swift, Sources/Fuzzilli/Lifting/ScriptWriter.swift, Sources/Fuzzilli/DumplingDiffOracle/Oracle.swift, Sources/REPRLRun/main.swift.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (69483 LoC, 728 module-visible types across 26 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 16 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: Sources/Fuzzilli/DumplingDiffOracle/Oracle.swift, Sources/Fuzzilli/Util/VariableSet.swift, Sources/Fuzzilli/Modules/ThreadSync.swift, Sources/Fuzzilli/Protobuf/ProtoUtils.swift, Sources/Fuzzilli/FuzzIL/Blocks.swift, Sources/Fuzzilli/Execution/Execution.swift, Sources/Fuzzilli/Util/VariableMap.swift, Sources/Fuzzilli/Util/Arguments.swift (and 8 more) (18 orphaned of 106 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; 106 of the 146 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
No SAST REDACTED:6— No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (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.
No dependency-update automation Sources/Fuzzilli/Compiler/Parser/package.json:2— `Sources/Fuzzilli/Compiler/Parser/package.json` 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`.
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.)
R7 · Dead Code· Unused private field '#field' · ×1
Unused private field '#field' Tests/FuzzilliTests/CompilerTests/private_properties.js:208— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code· Unused private accessor '#getter' · ×1
Unused private accessor '#getter' Tests/FuzzilliTests/CompilerTests/private_properties.js:209— Nothing in its class reads or assigns this private accessor, and no string key or test reaches it by name. Remove it, or use it where it was meant to be used.
R7 · Dead Code· Unused private accessor '#setter' · ×1
Unused private accessor '#setter' Tests/FuzzilliTests/CompilerTests/private_properties.js:210— Nothing in its class reads or assigns this private accessor, and no string key or test reaches it by name. Remove it, or use it where it was meant to be used.
Skipped (documented): testBinaryenWasmGenerator Tests/FuzzilliTests/LifterTest.swift:6084— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): testBinaryenWasmCodeGenerationAndCompilation Tests/FuzzilliTests/LiveTests.swift:191— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): testBinaryenWasmCodeGenerationAndCompilationAndExecution Tests/FuzzilliTests/LiveTests.swift:210— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): testBinaryenWasmMutator Tests/FuzzilliTests/LiveTests.swift:230— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): testOptionsBagAnySubset Tests/FuzzilliTests/ProgramBuilderTest.swift:760— Skipped with a documented reason — a deferral, not lazy debt: Skipping due to https://crbug.com/515494290
Skipped (documented): testOnlyInstrumentedProgramCrashesAndIsMinimized Tests/FuzzilliTests/RuntimeAssistedMutatorTests.swift:102— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): testRoundtripTranspilationHandlesLargeArrayGracefully Tests/FuzzilliTests/RuntimeAssistedMutatorTests.swift:334— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): testJavaScriptExecutorLargeOutput Tests/FuzzilliTests/TestUtils.swift:195— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (no committed lockfile, so no resolved version to grade) — This repository's npm dependencies were read for PINNING discipline: 2 production declaration(s) plus 0 development one(s) across 1 package.json (1 of them the product — the rest are example, documentation or fixture manifests, which are read and counted but screened off the rules below, because both prescribe a MOVE and "align your example apps" is not a remedy), against 0 committed lockfile(s). No pinning defect was found. That is only PART of dependency hygiene, so this dimension is NOT SCORED: whether any of these packages has a newer, deprecated or abandoned release is the dependency-CURRENCY question, and answering it needs a lockfile resolved to concrete versions, which this repository does not commit: a package.json states version RANGES, and a range names no particular release to be behind. So there was nothing here for the registry to grade — that is a fact about the repository, not a reader we are missing, and no lockfile reader we could write would change it. A clean pinning pass is NOT an all-clear for these dependencies, and it is not a finding that they are all USED. Note also what is deliberately NOT charged here: a workspace legitimately carries ONE lockfile for many manifests, so no row is raised off the lockfile count, only reported. Known CVEs in the same dependency graph are a separate question again, reported under D30 wherever the manifest is OSV-readable.
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.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 24 file(s) — `Sources/Fuzzilli/Base/ProgramBuilder.swift`, `Sources/Fuzzilli/CodeGen/BinaryenWasmGenerator.swift`, `Sources/Fuzzilli/CodeGen/CodeGenerator.swift`, `Sources/Fuzzilli/CodeGen/CodeGenerators.swift`, `Sources/Fuzzilli/CodeGen/WasmCodeGenerators.swift`, … (+19 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1dcb7-aec1-747d-b9e2-c21de241922d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 22 · Warnings: 1001 · Recommendations: 57 · Info: 9 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 15-11-2026 @ 00:59 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.