Public report of linebender/vello, published 14 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, 14 November 2026, 20:45 UTC · Survey ID cd_06fe124ee084463da2a1125481231c2a
linebender/vello
Measured 14 November 2026, 20:42 UTC, at code version b238d10
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 scoreStrong
CriticalWeakAdequateStrongExemplary
Up 4 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: 76,421 lines of product code in 13 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Production Readiness, 69
Findings by how serious they are
74 critical545 serious56 minor
11 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
14 November 2026, 20:42 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.
641of 675 findings point to an exact file and line, so you can open each one in the code. The other 34 concern the repository as a whole, such as missing documentation.
47dimensions across 7 lenses, read from 76,421 lines of product code in 13 projects.
linebender/vello meets our standard for a preview release. It scores 73 out of 100 and is rated Strong, and 58 of its 74 critical findings are security problems in the build pipeline.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is recording design decisions, worth about 3 points. Having someone learn and document the two files no active contributor knows comes next, worth about 2 points.
Fifty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step installs packages that can change without warning, and eight sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, pinning what the pipeline installs and making the hidden dependencies explicit would close these risks. The five pages that don't say their language need their language set.
The product code is 76,421 lines, about €150,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.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Code composition: what the lines of code are
Product code 74%Tests 26%
New since the last survey: 139 findings
These 139 critical or serious findings weren't in the previous survey, on 28 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: 81 findings
These 81 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one.
A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €150,000 · Estimate
Cost to rebuild
€49,000 to €250,000, for 814 to 2,584 hours of work, about 1.0 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
×1.1 at a score of 73. 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: 76,421 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 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
Raises the score by about 3 points · Low effort · ADR Quality
2
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with flatten.rs, render.rs.
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.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 1 ADR 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 6.9 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 6% on every change. The history of the code shows how much it changes: about 65,155 lines over the last 90 days, which is about 264,240 lines a year. At that pace, the extra work comes to an estimated 18.5 to 111 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.
228 modules, with 567 dependencies between them. 10 loops run through 41 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 188 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
vello.scene uses vello_encoding.config, so a change to vello_encoding.config can break vello.scene, while a change to vello.scene can't break vello_encoding.config.
Position
Below the diagonal: vello.scene uses a module listed above it, which is the healthy direction.
vello.scene uses vello_encoding.encoding, so a change to vello_encoding.encoding can break vello.scene, while a change to vello.scene can't break vello_encoding.encoding.
Position
Below the diagonal: vello.scene uses a module listed above it, which is the healthy direction.
vello_common.filter uses vello_common.filter_effects, so a change to vello_common.filter_effects can break vello_common.filter, while a change to vello_common.filter can't break vello_common.filter_effects.
Position
Below the diagonal: vello_common.filter uses a module listed above it, which is the healthy direction.
vello_common.filter uses vello_common.geometry, so a change to vello_common.geometry can break vello_common.filter, while a change to vello_common.filter can't break vello_common.geometry.
Position
Below the diagonal: vello_common.filter uses a module listed above it, which is the healthy direction.
vello_common.flatten uses vello_common.geometry, so a change to vello_common.geometry can break vello_common.flatten, while a change to vello_common.flatten can't break vello_common.geometry.
Position
Below the diagonal: vello_common.flatten uses a module listed above it, which is the healthy direction.
vello_common.mask uses vello_common.pixmap, so a change to vello_common.pixmap can break vello_common.mask, while a change to vello_common.mask can't break vello_common.pixmap.
Position
Below the diagonal: vello_common.mask uses a module listed above it, which is the healthy direction.
vello_common.paint uses vello_common.pixmap, so a change to vello_common.pixmap can break vello_common.paint, while a change to vello_common.paint can't break vello_common.pixmap.
Position
Below the diagonal: vello_common.paint uses a module listed above it, which is the healthy direction.
vello_common.strip uses vello_common.geometry, so a change to vello_common.geometry can break vello_common.strip, while a change to vello_common.strip can't break vello_common.geometry.
Position
Below the diagonal: vello_common.strip uses a module listed above it, which is the healthy direction.
vello_gpu.render.common uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.render.common, while a change to vello_gpu.render.common can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.render.common uses a module listed above it, which is the healthy direction.
vello_gpu.schedule.round uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.schedule.round, while a change to vello_gpu.schedule.round can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.schedule.round uses a module listed above it, which is the healthy direction.
13→20 vello_gpu.schedule.round uses vello_gpu.filterpart of a loop✕
Connections
2 pairs of types, where a type in vello_gpu.schedule.round uses a type in vello_gpu.filter.
vello_gpu.schedule.round uses vello_gpu.filter, so a change to vello_gpu.filter can break vello_gpu.schedule.round, while a change to vello_gpu.schedule.round can't break vello_gpu.filter.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→31 vello_gpu.schedule.round uses vello_gpu.schedulepart of a loop✕
Connections
4 pairs of types, where a type in vello_gpu.schedule.round uses a type in vello_gpu.schedule.
vello_gpu.schedule.round uses vello_gpu.schedule, so a change to vello_gpu.schedule can break vello_gpu.schedule.round, while a change to vello_gpu.schedule.round can't break vello_gpu.schedule.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→32 vello_gpu.schedule.round uses vello_gpu.targetpart of a loop✕
Connections
15 pairs of types, where a type in vello_gpu.schedule.round uses a type in vello_gpu.target.
vello_gpu.schedule.round uses vello_gpu.target, so a change to vello_gpu.target can break vello_gpu.schedule.round, while a change to vello_gpu.schedule.round can't break vello_gpu.target.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→33 vello_gpu.schedule.round uses vello_gpu.drawpart of a loop✕
Connections
3 pairs of types, where a type in vello_gpu.schedule.round uses a type in vello_gpu.draw.
vello_gpu.schedule.round uses vello_gpu.draw, so a change to vello_gpu.draw can break vello_gpu.schedule.round, while a change to vello_gpu.schedule.round can't break vello_gpu.draw.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
glifo.atlas.region uses vello_common.paint, so a change to vello_common.paint can break glifo.atlas.region, while a change to glifo.atlas.region can't break vello_common.paint.
Position
Below the diagonal: glifo.atlas.region uses a module listed above it, which is the healthy direction.
vello.render uses vello_encoding.config, so a change to vello_encoding.config can break vello.render, while a change to vello.render can't break vello_encoding.config.
Position
Below the diagonal: vello.render uses a module listed above it, which is the healthy direction.
vello.render uses vello_encoding.encoding, so a change to vello_encoding.encoding can break vello.render, while a change to vello.render can't break vello_encoding.encoding.
Position
Below the diagonal: vello.render uses a module listed above it, which is the healthy direction.
vello_common.encode uses vello_common.flatten, so a change to vello_common.flatten can break vello_common.encode, while a change to vello_common.encode can't break vello_common.flatten.
Position
Below the diagonal: vello_common.encode uses a module listed above it, which is the healthy direction.
vello_common.encode uses vello_common.paint, so a change to vello_common.paint can break vello_common.encode, while a change to vello_common.encode can't break vello_common.paint.
Position
Below the diagonal: vello_common.encode uses a module listed above it, which is the healthy direction.
vello_common.image_cache uses vello_common.paint, so a change to vello_common.paint can break vello_common.image_cache, while a change to vello_common.image_cache can't break vello_common.paint.
Position
Below the diagonal: vello_common.image_cache uses a module listed above it, which is the healthy direction.
vello_common.record uses vello_common.geometry, so a change to vello_common.geometry can break vello_common.record, while a change to vello_common.record can't break vello_common.geometry.
Position
Below the diagonal: vello_common.record uses a module listed above it, which is the healthy direction.
vello_common.record uses vello_common.filter, so a change to vello_common.filter can break vello_common.record, while a change to vello_common.record can't break vello_common.filter.
Position
Below the diagonal: vello_common.record uses a module listed above it, which is the healthy direction.
vello_common.record uses vello_common.mask, so a change to vello_common.mask can break vello_common.record, while a change to vello_common.record can't break vello_common.mask.
Position
Below the diagonal: vello_common.record uses a module listed above it, which is the healthy direction.
vello_common.strip_generator uses vello_common.flatten, so a change to vello_common.flatten can break vello_common.strip_generator, while a change to vello_common.strip_generator can't break vello_common.flatten.
Position
Below the diagonal: vello_common.strip_generator uses a module listed above it, which is the healthy direction.
vello_common.strip_generator uses vello_common.strip, so a change to vello_common.strip can break vello_common.strip_generator, while a change to vello_common.strip_generator can't break vello_common.strip.
Position
Below the diagonal: vello_common.strip_generator uses a module listed above it, which is the healthy direction.
19→23 vello_common.strip_generator uses vello_common.clippart of a loop✕
Connections
4 pairs of types, where a type in vello_common.strip_generator uses a type in vello_common.clip.
vello_common.strip_generator uses vello_common.clip, so a change to vello_common.clip can break vello_common.strip_generator, while a change to vello_common.strip_generator can't break vello_common.clip.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vello_gpu.filter uses vello_common.filter_effects, so a change to vello_common.filter_effects can break vello_gpu.filter, while a change to vello_gpu.filter can't break vello_common.filter_effects.
Position
Below the diagonal: vello_gpu.filter uses a module listed above it, which is the healthy direction.
vello_gpu.filter uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.filter, while a change to vello_gpu.filter can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.filter uses a module listed above it, which is the healthy direction.
vello_gpu.filter uses vello_common.filter, so a change to vello_common.filter can break vello_gpu.filter, while a change to vello_gpu.filter can't break vello_common.filter.
Position
Below the diagonal: vello_gpu.filter uses a module listed above it, which is the healthy direction.
vello_gpu.filter uses vello_gpu.schedule.round, so a change to vello_gpu.schedule.round can break vello_gpu.filter, while a change to vello_gpu.filter can't break vello_gpu.schedule.round.
Position
Below the diagonal: vello_gpu.filter uses a module listed above it, which is the healthy direction.
glifo.atlas.cache uses vello_common.pixmap, so a change to vello_common.pixmap can break glifo.atlas.cache, while a change to glifo.atlas.cache can't break vello_common.pixmap.
Position
Below the diagonal: glifo.atlas.cache uses a module listed above it, which is the healthy direction.
glifo.atlas.cache uses vello_common.paint, so a change to vello_common.paint can break glifo.atlas.cache, while a change to glifo.atlas.cache can't break vello_common.paint.
Position
Below the diagonal: glifo.atlas.cache uses a module listed above it, which is the healthy direction.
glifo.atlas.cache uses glifo.atlas.region, so a change to glifo.atlas.region can break glifo.atlas.cache, while a change to glifo.atlas.cache can't break glifo.atlas.region.
Position
Below the diagonal: glifo.atlas.cache uses a module listed above it, which is the healthy direction.
glifo.atlas.cache uses vello_common.image_cache, so a change to vello_common.image_cache can break glifo.atlas.cache, while a change to glifo.atlas.cache can't break vello_common.image_cache.
Position
Below the diagonal: glifo.atlas.cache uses a module listed above it, which is the healthy direction.
vello_common.clip uses vello_common.geometry, so a change to vello_common.geometry can break vello_common.clip, while a change to vello_common.clip can't break vello_common.geometry.
Position
Below the diagonal: vello_common.clip uses a module listed above it, which is the healthy direction.
vello_common.clip uses vello_common.strip, so a change to vello_common.strip can break vello_common.clip, while a change to vello_common.clip can't break vello_common.strip.
Position
Below the diagonal: vello_common.clip uses a module listed above it, which is the healthy direction.
vello_common.clip uses vello_common.strip_generator, so a change to vello_common.strip_generator can break vello_common.clip, while a change to vello_common.clip can't break vello_common.strip_generator.
Position
Below the diagonal: vello_common.clip uses a module listed above it, which is the healthy direction.
vello_cpu.coarse.bucketer uses vello_common.geometry, so a change to vello_common.geometry can break vello_cpu.coarse.bucketer, while a change to vello_cpu.coarse.bucketer can't break vello_common.geometry.
Position
Below the diagonal: vello_cpu.coarse.bucketer uses a module listed above it, which is the healthy direction.
vello_cpu.coarse.bucketer uses vello_common.pixmap, so a change to vello_common.pixmap can break vello_cpu.coarse.bucketer, while a change to vello_cpu.coarse.bucketer can't break vello_common.pixmap.
Position
Below the diagonal: vello_cpu.coarse.bucketer uses a module listed above it, which is the healthy direction.
vello_cpu.coarse.bucketer uses vello_common.filter, so a change to vello_common.filter can break vello_cpu.coarse.bucketer, while a change to vello_cpu.coarse.bucketer can't break vello_common.filter.
Position
Below the diagonal: vello_cpu.coarse.bucketer uses a module listed above it, which is the healthy direction.
vello_cpu.coarse.bucketer uses vello_common.mask, so a change to vello_common.mask can break vello_cpu.coarse.bucketer, while a change to vello_cpu.coarse.bucketer can't break vello_common.mask.
Position
Below the diagonal: vello_cpu.coarse.bucketer uses a module listed above it, which is the healthy direction.
vello_cpu.coarse.bucketer uses vello_common.encode, so a change to vello_common.encode can break vello_cpu.coarse.bucketer, while a change to vello_cpu.coarse.bucketer can't break vello_common.encode.
Position
Below the diagonal: vello_cpu.coarse.bucketer uses a module listed above it, which is the healthy direction.
vello_cpu.coarse.bucketer uses vello_common.record, so a change to vello_common.record can break vello_cpu.coarse.bucketer, while a change to vello_cpu.coarse.bucketer can't break vello_common.record.
Position
Below the diagonal: vello_cpu.coarse.bucketer uses a module listed above it, which is the healthy direction.
glifo.glyph uses vello_common.pixmap, so a change to vello_common.pixmap can break glifo.glyph, while a change to glifo.glyph can't break vello_common.pixmap.
Position
Below the diagonal: glifo.glyph uses a module listed above it, which is the healthy direction.
glifo.glyph uses glifo.atlas.region, so a change to glifo.atlas.region can break glifo.glyph, while a change to glifo.glyph can't break glifo.atlas.region.
Position
Below the diagonal: glifo.glyph uses a module listed above it, which is the healthy direction.
glifo.glyph uses vello_common.image_cache, so a change to vello_common.image_cache can break glifo.glyph, while a change to glifo.glyph can't break vello_common.image_cache.
Position
Below the diagonal: glifo.glyph uses a module listed above it, which is the healthy direction.
glifo.glyph uses glifo.atlas.cache, so a change to glifo.atlas.cache can break glifo.glyph, while a change to glifo.glyph can't break glifo.atlas.cache.
Position
Below the diagonal: glifo.glyph uses a module listed above it, which is the healthy direction.
vello_cpu.fine uses vello_common.filter_effects, so a change to vello_common.filter_effects can break vello_cpu.fine, while a change to vello_cpu.fine can't break vello_common.filter_effects.
Position
Below the diagonal: vello_cpu.fine uses a module listed above it, which is the healthy direction.
vello_cpu.fine uses vello_common.pixmap, so a change to vello_common.pixmap can break vello_cpu.fine, while a change to vello_cpu.fine can't break vello_common.pixmap.
Position
Below the diagonal: vello_cpu.fine uses a module listed above it, which is the healthy direction.
vello_cpu.fine uses vello_common.mask, so a change to vello_common.mask can break vello_cpu.fine, while a change to vello_cpu.fine can't break vello_common.mask.
Position
Below the diagonal: vello_cpu.fine uses a module listed above it, which is the healthy direction.
vello_cpu.fine uses vello_common.paint, so a change to vello_common.paint can break vello_cpu.fine, while a change to vello_cpu.fine can't break vello_common.paint.
Position
Below the diagonal: vello_cpu.fine uses a module listed above it, which is the healthy direction.
vello_cpu.fine uses vello_common.encode, so a change to vello_common.encode can break vello_cpu.fine, while a change to vello_cpu.fine can't break vello_common.encode.
Position
Below the diagonal: vello_cpu.fine uses a module listed above it, which is the healthy direction.
vello_cpu.fine uses vello_cpu.coarse.bucketer, so a change to vello_cpu.coarse.bucketer can break vello_cpu.fine, while a change to vello_cpu.fine can't break vello_cpu.coarse.bucketer.
Position
Below the diagonal: vello_cpu.fine uses a module listed above it, which is the healthy direction.
vello_cpu.render uses vello_common.filter_effects, so a change to vello_common.filter_effects can break vello_cpu.render, while a change to vello_cpu.render can't break vello_common.filter_effects.
Position
Below the diagonal: vello_cpu.render uses a module listed above it, which is the healthy direction.
vello_cpu.render uses vello_common.pixmap, so a change to vello_common.pixmap can break vello_cpu.render, while a change to vello_cpu.render can't break vello_common.pixmap.
Position
Below the diagonal: vello_cpu.render uses a module listed above it, which is the healthy direction.
vello_cpu.render uses vello_common.mask, so a change to vello_common.mask can break vello_cpu.render, while a change to vello_cpu.render can't break vello_common.mask.
Position
Below the diagonal: vello_cpu.render uses a module listed above it, which is the healthy direction.
vello_cpu.render uses vello_common.paint, so a change to vello_common.paint can break vello_cpu.render, while a change to vello_cpu.render can't break vello_common.paint.
Position
Below the diagonal: vello_cpu.render uses a module listed above it, which is the healthy direction.
vello_cpu.render uses glifo.atlas.region, so a change to glifo.atlas.region can break vello_cpu.render, while a change to vello_cpu.render can't break glifo.atlas.region.
Position
Below the diagonal: vello_cpu.render uses a module listed above it, which is the healthy direction.
vello_cpu.render uses vello_common.encode, so a change to vello_common.encode can break vello_cpu.render, while a change to vello_cpu.render can't break vello_common.encode.
Position
Below the diagonal: vello_cpu.render uses a module listed above it, which is the healthy direction.
vello_gpu.scene uses vello_common.filter_effects, so a change to vello_common.filter_effects can break vello_gpu.scene, while a change to vello_gpu.scene can't break vello_common.filter_effects.
Position
Below the diagonal: vello_gpu.scene uses a module listed above it, which is the healthy direction.
vello_gpu.scene uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.scene, while a change to vello_gpu.scene can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.scene uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in vello_gpu.scene uses a type in vello_common.mask.
The types involved
vello_gpu.scene.Scene → vello_common.mask.Mask
Direction
vello_gpu.scene uses vello_common.mask, so a change to vello_common.mask can break vello_gpu.scene, while a change to vello_gpu.scene can't break vello_common.mask.
Position
Below the diagonal: vello_gpu.scene uses a module listed above it, which is the healthy direction.
vello_gpu.scene uses vello_common.paint, so a change to vello_common.paint can break vello_gpu.scene, while a change to vello_gpu.scene can't break vello_common.paint.
Position
Below the diagonal: vello_gpu.scene uses a module listed above it, which is the healthy direction.
vello_gpu.scene uses vello_gpu.render.common, so a change to vello_gpu.render.common can break vello_gpu.scene, while a change to vello_gpu.scene can't break vello_gpu.render.common.
Position
Below the diagonal: vello_gpu.scene uses a module listed above it, which is the healthy direction.
vello_gpu.scene uses glifo.atlas.region, so a change to glifo.atlas.region can break vello_gpu.scene, while a change to vello_gpu.scene can't break glifo.atlas.region.
Position
Below the diagonal: vello_gpu.scene uses a module listed above it, which is the healthy direction.
vello_gpu.scene uses vello_common.encode, so a change to vello_common.encode can break vello_gpu.scene, while a change to vello_gpu.scene can't break vello_common.encode.
Position
Below the diagonal: vello_gpu.scene uses a module listed above it, which is the healthy direction.
vello_gpu.scene uses vello_common.record, so a change to vello_common.record can break vello_gpu.scene, while a change to vello_gpu.scene can't break vello_common.record.
Position
Below the diagonal: vello_gpu.scene uses a module listed above it, which is the healthy direction.
vello_gpu.scene uses vello_common.strip_generator, so a change to vello_common.strip_generator can break vello_gpu.scene, while a change to vello_gpu.scene can't break vello_common.strip_generator.
Position
Below the diagonal: vello_gpu.scene uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_common.geometry, so a change to vello_common.geometry can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_common.geometry.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_common.pixmap, so a change to vello_common.pixmap can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_common.pixmap.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_common.filter, so a change to vello_common.filter can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_common.filter.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_common.mask, so a change to vello_common.mask can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_common.mask.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_common.paint, so a change to vello_common.paint can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_common.paint.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_common.strip, so a change to vello_common.strip can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_common.strip.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_common.record, so a change to vello_common.record can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_common.record.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_common.strip_generator, so a change to vello_common.strip_generator can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_common.strip_generator.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_common.clip, so a change to vello_common.clip can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_common.clip.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_cpu.coarse.bucketer, so a change to vello_cpu.coarse.bucketer can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_cpu.coarse.bucketer.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.multi_threaded uses vello_cpu.render, so a change to vello_cpu.render can break vello_cpu.dispatch.multi_threaded, while a change to vello_cpu.dispatch.multi_threaded can't break vello_cpu.render.
Position
Below the diagonal: vello_cpu.dispatch.multi_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.single_threaded uses vello_common.geometry, so a change to vello_common.geometry can break vello_cpu.dispatch.single_threaded, while a change to vello_cpu.dispatch.single_threaded can't break vello_common.geometry.
Position
Below the diagonal: vello_cpu.dispatch.single_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.single_threaded uses vello_common.pixmap, so a change to vello_common.pixmap can break vello_cpu.dispatch.single_threaded, while a change to vello_cpu.dispatch.single_threaded can't break vello_common.pixmap.
Position
Below the diagonal: vello_cpu.dispatch.single_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.single_threaded uses vello_common.filter, so a change to vello_common.filter can break vello_cpu.dispatch.single_threaded, while a change to vello_cpu.dispatch.single_threaded can't break vello_common.filter.
Position
Below the diagonal: vello_cpu.dispatch.single_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.single_threaded uses vello_common.mask, so a change to vello_common.mask can break vello_cpu.dispatch.single_threaded, while a change to vello_cpu.dispatch.single_threaded can't break vello_common.mask.
Position
Below the diagonal: vello_cpu.dispatch.single_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.single_threaded uses vello_common.paint, so a change to vello_common.paint can break vello_cpu.dispatch.single_threaded, while a change to vello_cpu.dispatch.single_threaded can't break vello_common.paint.
Position
Below the diagonal: vello_cpu.dispatch.single_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.single_threaded uses vello_common.record, so a change to vello_common.record can break vello_cpu.dispatch.single_threaded, while a change to vello_cpu.dispatch.single_threaded can't break vello_common.record.
Position
Below the diagonal: vello_cpu.dispatch.single_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.single_threaded uses vello_common.strip_generator, so a change to vello_common.strip_generator can break vello_cpu.dispatch.single_threaded, while a change to vello_cpu.dispatch.single_threaded can't break vello_common.strip_generator.
Position
Below the diagonal: vello_cpu.dispatch.single_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.single_threaded uses vello_cpu.coarse.bucketer, so a change to vello_cpu.coarse.bucketer can break vello_cpu.dispatch.single_threaded, while a change to vello_cpu.dispatch.single_threaded can't break vello_cpu.coarse.bucketer.
Position
Below the diagonal: vello_cpu.dispatch.single_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.single_threaded uses vello_cpu.fine, so a change to vello_cpu.fine can break vello_cpu.dispatch.single_threaded, while a change to vello_cpu.dispatch.single_threaded can't break vello_cpu.fine.
Position
Below the diagonal: vello_cpu.dispatch.single_threaded uses a module listed above it, which is the healthy direction.
vello_cpu.dispatch.single_threaded uses vello_cpu.render, so a change to vello_cpu.render can break vello_cpu.dispatch.single_threaded, while a change to vello_cpu.dispatch.single_threaded can't break vello_cpu.render.
Position
Below the diagonal: vello_cpu.dispatch.single_threaded uses a module listed above it, which is the healthy direction.
vello_gpu.schedule uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.schedule, while a change to vello_gpu.schedule can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.schedule uses a module listed above it, which is the healthy direction.
vello_gpu.schedule uses vello_common.filter, so a change to vello_common.filter can break vello_gpu.schedule, while a change to vello_gpu.schedule can't break vello_common.filter.
Position
Below the diagonal: vello_gpu.schedule uses a module listed above it, which is the healthy direction.
vello_gpu.schedule uses vello_gpu.schedule.round, so a change to vello_gpu.schedule.round can break vello_gpu.schedule, while a change to vello_gpu.schedule can't break vello_gpu.schedule.round.
Position
Below the diagonal: vello_gpu.schedule uses a module listed above it, which is the healthy direction.
vello_gpu.schedule uses vello_common.record, so a change to vello_common.record can break vello_gpu.schedule, while a change to vello_gpu.schedule can't break vello_common.record.
Position
Below the diagonal: vello_gpu.schedule uses a module listed above it, which is the healthy direction.
vello_gpu.schedule uses vello_common.strip_generator, so a change to vello_common.strip_generator can break vello_gpu.schedule, while a change to vello_gpu.schedule can't break vello_common.strip_generator.
Position
Below the diagonal: vello_gpu.schedule uses a module listed above it, which is the healthy direction.
vello_gpu.schedule uses vello_gpu.filter, so a change to vello_gpu.filter can break vello_gpu.schedule, while a change to vello_gpu.schedule can't break vello_gpu.filter.
Position
Below the diagonal: vello_gpu.schedule uses a module listed above it, which is the healthy direction.
vello_gpu.schedule uses vello_gpu.scene, so a change to vello_gpu.scene can break vello_gpu.schedule, while a change to vello_gpu.schedule can't break vello_gpu.scene.
Position
Below the diagonal: vello_gpu.schedule uses a module listed above it, which is the healthy direction.
31→32 vello_gpu.schedule uses vello_gpu.targetpart of a loop✕
Connections
9 pairs of types, where a type in vello_gpu.schedule uses a type in vello_gpu.target.
vello_gpu.schedule uses vello_gpu.target, so a change to vello_gpu.target can break vello_gpu.schedule, while a change to vello_gpu.schedule can't break vello_gpu.target.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→33 vello_gpu.schedule uses vello_gpu.drawpart of a loop✕
Connections
3 pairs of types, where a type in vello_gpu.schedule uses a type in vello_gpu.draw.
vello_gpu.schedule uses vello_gpu.draw, so a change to vello_gpu.draw can break vello_gpu.schedule, while a change to vello_gpu.schedule can't break vello_gpu.draw.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vello_gpu.target uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.target, while a change to vello_gpu.target can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.target uses a module listed above it, which is the healthy direction.
vello_gpu.target uses vello_gpu.schedule.round, so a change to vello_gpu.schedule.round can break vello_gpu.target, while a change to vello_gpu.target can't break vello_gpu.schedule.round.
Position
Below the diagonal: vello_gpu.target uses a module listed above it, which is the healthy direction.
vello_gpu.target uses vello_gpu.schedule, so a change to vello_gpu.schedule can break vello_gpu.target, while a change to vello_gpu.target can't break vello_gpu.schedule.
Position
Below the diagonal: vello_gpu.target uses a module listed above it, which is the healthy direction.
32→33 vello_gpu.target uses vello_gpu.drawpart of a loop✕
Connections
2 pairs of types, where a type in vello_gpu.target uses a type in vello_gpu.draw.
vello_gpu.target uses vello_gpu.draw, so a change to vello_gpu.draw can break vello_gpu.target, while a change to vello_gpu.target can't break vello_gpu.draw.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vello_gpu.draw uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.draw, while a change to vello_gpu.draw can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.draw uses a module listed above it, which is the healthy direction.
vello_gpu.draw uses vello_common.paint, so a change to vello_common.paint can break vello_gpu.draw, while a change to vello_gpu.draw can't break vello_common.paint.
Position
Below the diagonal: vello_gpu.draw uses a module listed above it, which is the healthy direction.
vello_gpu.draw uses vello_common.strip, so a change to vello_common.strip can break vello_gpu.draw, while a change to vello_gpu.draw can't break vello_common.strip.
Position
Below the diagonal: vello_gpu.draw uses a module listed above it, which is the healthy direction.
vello_gpu.draw uses vello_gpu.render.common, so a change to vello_gpu.render.common can break vello_gpu.draw, while a change to vello_gpu.draw can't break vello_gpu.render.common.
Position
Below the diagonal: vello_gpu.draw uses a module listed above it, which is the healthy direction.
vello_gpu.draw uses vello_common.record, so a change to vello_common.record can break vello_gpu.draw, while a change to vello_gpu.draw can't break vello_common.record.
Position
Below the diagonal: vello_gpu.draw uses a module listed above it, which is the healthy direction.
vello_gpu.draw uses vello_common.strip_generator, so a change to vello_common.strip_generator can break vello_gpu.draw, while a change to vello_gpu.draw can't break vello_common.strip_generator.
Position
Below the diagonal: vello_gpu.draw uses a module listed above it, which is the healthy direction.
vello_gpu.draw uses vello_gpu.scene, so a change to vello_gpu.scene can break vello_gpu.draw, while a change to vello_gpu.draw can't break vello_gpu.scene.
Position
Below the diagonal: vello_gpu.draw uses a module listed above it, which is the healthy direction.
vello_gpu.draw uses vello_gpu.target, so a change to vello_gpu.target can break vello_gpu.draw, while a change to vello_gpu.draw can't break vello_gpu.target.
Position
Below the diagonal: vello_gpu.draw uses a module listed above it, which is the healthy direction.
vello_gpu.render.common.scene_preparer uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.render.common.scene_preparer, while a change to vello_gpu.render.common.scene_preparer can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.render.common.scene_preparer uses a module listed above it, which is the healthy direction.
vello_gpu.render.common.scene_preparer uses vello_gpu.render.common, so a change to vello_gpu.render.common can break vello_gpu.render.common.scene_preparer, while a change to vello_gpu.render.common.scene_preparer can't break vello_gpu.render.common.
Position
Below the diagonal: vello_gpu.render.common.scene_preparer uses a module listed above it, which is the healthy direction.
vello_gpu.render.common.scene_preparer uses vello_common.image_cache, so a change to vello_common.image_cache can break vello_gpu.render.common.scene_preparer, while a change to vello_gpu.render.common.scene_preparer can't break vello_common.image_cache.
Position
Below the diagonal: vello_gpu.render.common.scene_preparer uses a module listed above it, which is the healthy direction.
vello_gpu.render.common.scene_preparer uses vello_gpu.scene, so a change to vello_gpu.scene can break vello_gpu.render.common.scene_preparer, while a change to vello_gpu.render.common.scene_preparer can't break vello_gpu.scene.
Position
Below the diagonal: vello_gpu.render.common.scene_preparer uses a module listed above it, which is the healthy direction.
vello_gpu.render.common.scene_preparer uses vello_gpu.schedule, so a change to vello_gpu.schedule can break vello_gpu.render.common.scene_preparer, while a change to vello_gpu.render.common.scene_preparer can't break vello_gpu.schedule.
Position
Below the diagonal: vello_gpu.render.common.scene_preparer uses a module listed above it, which is the healthy direction.
vello_gpu.render.common.scene_preparer uses vello_gpu.target, so a change to vello_gpu.target can break vello_gpu.render.common.scene_preparer, while a change to vello_gpu.render.common.scene_preparer can't break vello_gpu.target.
Position
Below the diagonal: vello_gpu.render.common.scene_preparer uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.resources uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.render.webgl.resources, while a change to vello_gpu.render.webgl.resources can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.render.webgl.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.resources uses vello_gpu.render.common, so a change to vello_gpu.render.common can break vello_gpu.render.webgl.resources, while a change to vello_gpu.render.webgl.resources can't break vello_gpu.render.common.
Position
Below the diagonal: vello_gpu.render.webgl.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.resources uses vello_common.image_cache, so a change to vello_common.image_cache can break vello_gpu.render.webgl.resources, while a change to vello_gpu.render.webgl.resources can't break vello_common.image_cache.
Position
Below the diagonal: vello_gpu.render.webgl.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.resources uses vello_gpu.filter, so a change to vello_gpu.filter can break vello_gpu.render.webgl.resources, while a change to vello_gpu.render.webgl.resources can't break vello_gpu.filter.
Position
Below the diagonal: vello_gpu.render.webgl.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.resources uses vello_gpu.scene, so a change to vello_gpu.scene can break vello_gpu.render.webgl.resources, while a change to vello_gpu.render.webgl.resources can't break vello_gpu.scene.
Position
Below the diagonal: vello_gpu.render.webgl.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.resources uses vello_gpu.schedule, so a change to vello_gpu.schedule can break vello_gpu.render.webgl.resources, while a change to vello_gpu.render.webgl.resources can't break vello_gpu.schedule.
Position
Below the diagonal: vello_gpu.render.webgl.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.resources uses vello_gpu.target, so a change to vello_gpu.target can break vello_gpu.render.webgl.resources, while a change to vello_gpu.render.webgl.resources can't break vello_gpu.target.
Position
Below the diagonal: vello_gpu.render.webgl.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.resources uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.render.wgpu.resources, while a change to vello_gpu.render.wgpu.resources can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.render.wgpu.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.resources uses vello_gpu.render.common, so a change to vello_gpu.render.common can break vello_gpu.render.wgpu.resources, while a change to vello_gpu.render.wgpu.resources can't break vello_gpu.render.common.
Position
Below the diagonal: vello_gpu.render.wgpu.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.resources uses vello_common.image_cache, so a change to vello_common.image_cache can break vello_gpu.render.wgpu.resources, while a change to vello_gpu.render.wgpu.resources can't break vello_common.image_cache.
Position
Below the diagonal: vello_gpu.render.wgpu.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.resources uses vello_gpu.filter, so a change to vello_gpu.filter can break vello_gpu.render.wgpu.resources, while a change to vello_gpu.render.wgpu.resources can't break vello_gpu.filter.
Position
Below the diagonal: vello_gpu.render.wgpu.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.resources uses vello_gpu.scene, so a change to vello_gpu.scene can break vello_gpu.render.wgpu.resources, while a change to vello_gpu.render.wgpu.resources can't break vello_gpu.scene.
Position
Below the diagonal: vello_gpu.render.wgpu.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.resources uses vello_gpu.schedule, so a change to vello_gpu.schedule can break vello_gpu.render.wgpu.resources, while a change to vello_gpu.render.wgpu.resources can't break vello_gpu.schedule.
Position
Below the diagonal: vello_gpu.render.wgpu.resources uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.resources uses vello_gpu.target, so a change to vello_gpu.target can break vello_gpu.render.wgpu.resources, while a change to vello_gpu.render.wgpu.resources can't break vello_gpu.target.
Position
Below the diagonal: vello_gpu.render.wgpu.resources uses a module listed above it, which is the healthy direction.
36→38 vello_gpu.render.wgpu.resources uses vello_gpu.render.wgpu.passespart of a loop✕
Connections
1 pair of types, where a type in vello_gpu.render.wgpu.resources uses a type in vello_gpu.render.wgpu.passes.
vello_gpu.render.wgpu.resources uses vello_gpu.render.wgpu.passes, so a change to vello_gpu.render.wgpu.passes can break vello_gpu.render.wgpu.resources, while a change to vello_gpu.render.wgpu.resources can't break vello_gpu.render.wgpu.passes.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vello_gpu.render.webgl.passes uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.render.webgl.passes, while a change to vello_gpu.render.webgl.passes can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.render.webgl.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.passes uses vello_gpu.render.common, so a change to vello_gpu.render.common can break vello_gpu.render.webgl.passes, while a change to vello_gpu.render.webgl.passes can't break vello_gpu.render.common.
Position
Below the diagonal: vello_gpu.render.webgl.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.passes uses vello_gpu.filter, so a change to vello_gpu.filter can break vello_gpu.render.webgl.passes, while a change to vello_gpu.render.webgl.passes can't break vello_gpu.filter.
Position
Below the diagonal: vello_gpu.render.webgl.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.passes uses vello_gpu.target, so a change to vello_gpu.target can break vello_gpu.render.webgl.passes, while a change to vello_gpu.render.webgl.passes can't break vello_gpu.target.
Position
Below the diagonal: vello_gpu.render.webgl.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.passes uses vello_gpu.draw, so a change to vello_gpu.draw can break vello_gpu.render.webgl.passes, while a change to vello_gpu.render.webgl.passes can't break vello_gpu.draw.
Position
Below the diagonal: vello_gpu.render.webgl.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl.passes uses vello_gpu.render.webgl.resources, so a change to vello_gpu.render.webgl.resources can break vello_gpu.render.webgl.passes, while a change to vello_gpu.render.webgl.passes can't break vello_gpu.render.webgl.resources.
Position
Below the diagonal: vello_gpu.render.webgl.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.passes uses vello_common.geometry, so a change to vello_common.geometry can break vello_gpu.render.wgpu.passes, while a change to vello_gpu.render.wgpu.passes can't break vello_common.geometry.
Position
Below the diagonal: vello_gpu.render.wgpu.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.passes uses vello_gpu.render.common, so a change to vello_gpu.render.common can break vello_gpu.render.wgpu.passes, while a change to vello_gpu.render.wgpu.passes can't break vello_gpu.render.common.
Position
Below the diagonal: vello_gpu.render.wgpu.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.passes uses vello_gpu.filter, so a change to vello_gpu.filter can break vello_gpu.render.wgpu.passes, while a change to vello_gpu.render.wgpu.passes can't break vello_gpu.filter.
Position
Below the diagonal: vello_gpu.render.wgpu.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.passes uses vello_gpu.target, so a change to vello_gpu.target can break vello_gpu.render.wgpu.passes, while a change to vello_gpu.render.wgpu.passes can't break vello_gpu.target.
Position
Below the diagonal: vello_gpu.render.wgpu.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.passes uses vello_gpu.draw, so a change to vello_gpu.draw can break vello_gpu.render.wgpu.passes, while a change to vello_gpu.render.wgpu.passes can't break vello_gpu.draw.
Position
Below the diagonal: vello_gpu.render.wgpu.passes uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu.passes uses vello_gpu.render.wgpu.resources, so a change to vello_gpu.render.wgpu.resources can break vello_gpu.render.wgpu.passes, while a change to vello_gpu.render.wgpu.passes can't break vello_gpu.render.wgpu.resources.
Position
Below the diagonal: vello_gpu.render.wgpu.passes uses a module listed above it, which is the healthy direction.
38→40 vello_gpu.render.wgpu.passes uses vello_gpu.render.wgpupart of a loop✕
Connections
1 pair of types, where a type in vello_gpu.render.wgpu.passes uses a type in vello_gpu.render.wgpu.
vello_gpu.render.wgpu.passes uses vello_gpu.render.wgpu, so a change to vello_gpu.render.wgpu can break vello_gpu.render.wgpu.passes, while a change to vello_gpu.render.wgpu.passes can't break vello_gpu.render.wgpu.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
vello_gpu.render.webgl uses vello_common.pixmap, so a change to vello_common.pixmap can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break vello_common.pixmap.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl uses vello_common.paint, so a change to vello_common.paint can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break vello_common.paint.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl uses vello_gpu.render.common, so a change to vello_gpu.render.common can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break vello_gpu.render.common.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl uses vello_common.image_cache, so a change to vello_common.image_cache can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break vello_common.image_cache.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl uses glifo.atlas.cache, so a change to glifo.atlas.cache can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break glifo.atlas.cache.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl uses vello_gpu.scene, so a change to vello_gpu.scene can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break vello_gpu.scene.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl uses vello_gpu.schedule, so a change to vello_gpu.schedule can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break vello_gpu.schedule.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl uses vello_gpu.target, so a change to vello_gpu.target can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break vello_gpu.target.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl uses vello_gpu.render.common.scene_preparer, so a change to vello_gpu.render.common.scene_preparer can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break vello_gpu.render.common.scene_preparer.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl uses vello_gpu.render.webgl.resources, so a change to vello_gpu.render.webgl.resources can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break vello_gpu.render.webgl.resources.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.webgl uses vello_gpu.render.webgl.passes, so a change to vello_gpu.render.webgl.passes can break vello_gpu.render.webgl, while a change to vello_gpu.render.webgl can't break vello_gpu.render.webgl.passes.
Position
Below the diagonal: vello_gpu.render.webgl uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses vello_common.pixmap, so a change to vello_common.pixmap can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break vello_common.pixmap.
Position
Below the diagonal: vello_gpu.render.wgpu uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses vello_common.paint, so a change to vello_common.paint can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break vello_common.paint.
Position
Below the diagonal: vello_gpu.render.wgpu uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses vello_gpu.render.common, so a change to vello_gpu.render.common can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break vello_gpu.render.common.
Position
Below the diagonal: vello_gpu.render.wgpu uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses vello_common.image_cache, so a change to vello_common.image_cache can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break vello_common.image_cache.
Position
Below the diagonal: vello_gpu.render.wgpu uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses glifo.atlas.cache, so a change to glifo.atlas.cache can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break glifo.atlas.cache.
Position
Below the diagonal: vello_gpu.render.wgpu uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses vello_gpu.scene, so a change to vello_gpu.scene can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break vello_gpu.scene.
Position
Below the diagonal: vello_gpu.render.wgpu uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses vello_gpu.schedule, so a change to vello_gpu.schedule can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break vello_gpu.schedule.
Position
Below the diagonal: vello_gpu.render.wgpu uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses vello_gpu.target, so a change to vello_gpu.target can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break vello_gpu.target.
Position
Below the diagonal: vello_gpu.render.wgpu uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses vello_gpu.render.common.scene_preparer, so a change to vello_gpu.render.common.scene_preparer can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break vello_gpu.render.common.scene_preparer.
Position
Below the diagonal: vello_gpu.render.wgpu uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses vello_gpu.render.wgpu.resources, so a change to vello_gpu.render.wgpu.resources can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break vello_gpu.render.wgpu.resources.
Position
Below the diagonal: vello_gpu.render.wgpu uses a module listed above it, which is the healthy direction.
vello_gpu.render.wgpu uses vello_gpu.render.wgpu.passes, so a change to vello_gpu.render.wgpu.passes can break vello_gpu.render.wgpu, while a change to vello_gpu.render.wgpu can't break vello_gpu.render.wgpu.passes.
Position
Below the diagonal: vello_gpu.render.wgpu 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
A05:2025 — Injection
58
High / Critical
A03:2025 — Software Supply Chain Failures
8
Medium
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; 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; Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
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.
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Dependency Vulnerabilities: Medium advisory (unsound): REDACTED
vello_common/src/tile.rs
6.0
Mixed
Explicit Debt: TodoComment
research/vello_encoding/src/resolve.rs
6.0
Mixed
Explicit Debt: TodoComment
research/vello_research/src/wgpu_engine.rs
6.0
Mixed
Explicit Debt: TodoComment
vello_common/src/strip.rs
6.0
Mixed
Explicit Debt: TodoComment
research/vello_shaders/src/cpu/coarse.rs
6.0
Mixed
Explicit Debt: TodoComment
vello_common/src/flatten_simd.rs
6.0
Mixed
Explicit Debt: TodoComment
research/vello_shaders/src/cpu/flatten.rs
6.0
Mixed
Explicit Debt: TodoComment
glifo/src/glyph.rs
6.0
Mixed
Explicit Debt: TodoComment
research/vello_research/src/scene.rs
6.0
Mixed
Explicit Debt: TodoComment
research/vello_research/src/render.rs
6.0
Mixed
Explicit Debt: HackComment
research/vello_shaders/src/compile/mod.rs
6.0
Mixed
Explicit Debt: TodoComment
vello_common/src/pico_svg.rs
6.0
Mixed
Explicit Debt: TodoComment
research/vello_shaders/src/cpu/fine.rs
6.0
Mixed
Explicit Debt: TodoComment
vello_cpu/src/fine/highp/mod.rs
6.0
Mixed
Explicit Debt: TodoComment
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 74
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 — 545
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 — 56
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
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, 641 of 675 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 Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. 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 (.rs) and this repository declares a Cargo test suite (repository root, 91 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (6.885 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
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 — 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. 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.
D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
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. `vello_gpu_shaders/src/webgl_bootstrap.d.ts` 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.
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.
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, Rust 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, Rust 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.
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.
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 Python, Rust 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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
20 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Tiles::make_tiles_msaa at 144. A further 2 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 glifo::colr::convert_composite_mode at 29 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: glifo/src/colr.rs (glifo::colr::convert_composite_mode at 29), vello_gpu/src/blend.rs (vello_gpu::blend::pack_mix at 16). 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.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with Tiles::make_tiles_msaa (cyclomatic 144). — Refactoring it lifts Cyclomatic Complexity from 6.0 to about 6.9/10.
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.
+ 14 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 240 down to 240 or less in Cognitive Complexity — start with Tiles::make_tiles_msaa (cognitive 660). — Refactoring it lifts Cognitive Complexity from 4.0 to about 5.1/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.2 / 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 16 MethodTooLong finding(s) in God Classes — start with strip.rs (3), wgpu_engine.rs (2), tile.rs (2). — One of this dimension's main actionable groups (16 warning-level).
Resolve the 13 FileTooLong finding(s) in God Classes — start with mod.rs (2), scene.rs (2), resources.rs (2). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 10 FunctionTooLong finding(s) in God Classes — start with flatten.rs (2), strip.rs, shaders.rs. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
119 duplicated block group(s) detected. 6.2 % of the production lines (4,718 of 76,421) are in a reported copy. A further 79 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 41 of the 198 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 88 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with glyph_cache.rs (2), multi_atlas.rs, render.rs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 8 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with mod.rs (3), image.rs (2), mask.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), encoding.rs, filter_effects.rs. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.7 / 10Strong✓ 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.
12 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 11 of the 12 (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).
Off the main sequence: vello_gpu_shaders · ×2
Off the main sequence: vello_common
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with resources.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
23 outdated, 0 yanked direct Cargo dependencies. 74 of 77 direct crates were graded against crates.io (0 not published there, 3 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: anyhow · ×23
Detailed fixes: d12_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 572 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 3 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under Apache-2.0 OR MIT, which is its own choice and is not judged here.
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 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs, glyph.rs, test.rs. — One of this dimension's main actionable groups (7 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 Factor8.2 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
35 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is vello_cpu/src/coarse/bucketer.rs. Counted over 200 of the 260 production source files in this repository: 55 are under the ~2,400-byte size floor this dimension measures over, and the remaining 5 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×2
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
206 deducted task-comment markers across 76421 LoC (0.3/KLoC) → score 9.5. 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 200 TodoComment finding(s) in Explicit Debt — start with scene.rs (26), lib.rs (18), mod.rs (16). — One of this dimension's main actionable groups (200 warning-level).
Resolve the 5 HackComment finding(s) in Explicit Debt — start with render.rs (2), scene.rs, resolve.rs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with clip.rs. — 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.
1 of 1 documentation facets pass in full. 28 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 13 build units (Cargo) 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: 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).
58 finding(s): 0 critical, 58 high, 0 medium, 0 low. 57 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 1 file(s) — `vello_gpu_shaders/src/webgl_bootstrap.d.ts` (line 7) — 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 57 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 (57 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.
Resolve the 4 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d30_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.
24 of 205 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is research/vello_shaders/src/cpu/flatten.rs. Counted over 205 of the 260 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 flatten.rs, render.rs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 22 Orphaned file finding(s) in Knowledge Freshness — start with estimate.rs, euler.rs, mod.rs. — One of this dimension's main actionable groups (22 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 8 Boundary-crossing change coupling finding(s) in Change Coupling — start with data.rs (2), scene.rs (2), mod.rs. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 5 Change coupling finding(s) in Change Coupling — start with worker.rs (2), multi_threaded.rs, mod.rs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with gradient_cache.rs. — 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.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Do you agree with this assessment?
AC3 · Page structure3.5 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×5) — .github/web-demo/native-webgl.html:1, .github/web-demo/research.html:1, .github/web-demo/vello-cpu.html:1, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×5) — .github/web-demo/native-webgl.html:1, .github/web-demo/research.html:1, .github/web-demo/vello-cpu.html:1, …
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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 isolation7.5 / 10Strong✓ 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.
`vello_bench` (production) references the test project `vello_dev_macros`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
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.
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.
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 · Observability5.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 5/10 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `research/xtask`, `vello_gpu_shaders`, `vello_tests`, `vello_toy`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
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
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 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.
X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 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 image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
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; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
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. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — 5 markup documents under demonstration, documentation or developer-tool trees (or modules the build marks non-production) but none in the product; no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — those pages are demos or docs for the code, not something this tier can boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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 field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~27472 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
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.
D21 Naming Consistency — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust 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"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .py, .rs source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 1 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.
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 — Rust suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (95 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner 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, Rust 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
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.
S1 Web-Security Posture — No web surface: 197 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
X12 Unreachable branch — X12 reached only 0% of this repository's production lines — rust (76,147 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
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.
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
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
X3 Exception handling — 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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
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.
Boundary-crossing change coupling: data.rs ↔ strip_generator.rs vello_bench/src/data.rs:1— `vello_bench/src/data.rs` (context vello_bench) and `vello_common/src/strip_generator.rs` (context vello_common) sit in DIFFERENT parts of the tree yet change together 83% of the time (15 of the 18 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `00b1f968` vello_cpu: Make `RenderContext` resizable (#1705) (at that commit the files were still `sparse_strips/vello_bench/src/data.rs` and `sparse_strips/vello_common/src/strip_generator.rs`); `1b24e77b` Add early culling for lines fully left of the viewport. (#1368) (at that commit the files were still `sparse_strips/vello_bench/src/data.rs` and `sparse_strips/vello_common/src/strip_generator.rs`); `d8b85aef` Add `RectU16` type for AABBs (#1559) (at that commit the files were still `sparse_strips/vello_bench/src/data.rs` and `sparse_strips/vello_common/src/strip_generator.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: data.rs ↔ debug.rs vello_bench/src/data.rs:1— `vello_bench/src/data.rs` (context vello_bench) and `vello_toy/src/debug.rs` (context vello_toy) sit in DIFFERENT parts of the tree yet change together 78% of the time (14 of the 18 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `00b1f968` vello_cpu: Make `RenderContext` resizable (#1705) (at that commit the files were still `sparse_strips/vello_bench/src/data.rs` and `sparse_strips/vello_toy/src/debug.rs`); `1b24e77b` Add early culling for lines fully left of the viewport. (#1368) (at that commit the files were still `sparse_strips/vello_bench/src/data.rs` and `sparse_strips/vello_toy/src/debug.rs`); `d8b85aef` Add `RectU16` type for AABBs (#1559) (at that commit the files were still `sparse_strips/vello_bench/src/data.rs` and `sparse_strips/vello_toy/src/debug.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: mod.rs ↔ scene.rs vello_cpu/src/dispatch/mod.rs:1— `vello_cpu/src/dispatch/mod.rs` (context vello_cpu) and `vello_gpu/src/scene.rs` (context vello_gpu) sit in DIFFERENT parts of the tree yet change together 64% of the time (14 of the 22 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `4714328a` sparse_strips: Add a `push_clip_rect` method (#1916); `00b1f968` vello_cpu: Make `RenderContext` resizable (#1705) (at that commit the files were still `sparse_strips/vello_cpu/src/dispatch/mod.rs` and `sparse_strips/vello_hybrid/src/scene.rs`); `39ec8632` Remove recordings from sparse strips renderers (#1611) (at that commit the files were still `sparse_strips/vello_cpu/src/dispatch/mod.rs` and `sparse_strips/vello_hybrid/src/scene.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: scene.rs ↔ svg.rs vello_gpu/src/scene.rs:1— `vello_gpu/src/scene.rs` (context vello_gpu) and `vello_tests/vello_example_scenes/src/svg.rs` (context vello_tests) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `39ec8632` Remove recordings from sparse strips renderers (#1611) (at that commit the files were still `sparse_strips/vello_hybrid/src/scene.rs` and `sparse_strips/vello_example_scenes/src/svg.rs`); `b7aac65f` [`vello_hybrid`]: Multiple image atlases support (#1252) (at that commit the files were still `sparse_strips/vello_hybrid/src/scene.rs` and `sparse_strips/vello_example_scenes/src/svg.rs`); `537f7d1d` fix transform handling in sparse_strips recording API (#1217) (at that commit the files were still `sparse_strips/vello_hybrid/src/scene.rs` and `sparse_strips/vello_hybrid/examples/scenes/src/svg.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: worker.rs ↔ scene.rs vello_cpu/src/dispatch/multi_threaded/worker.rs:1— `vello_cpu/src/dispatch/multi_threaded/worker.rs` (context vello_cpu) and `vello_gpu/src/scene.rs` (context vello_gpu) sit in DIFFERENT parts of the tree yet change together 59% of the time (10 of the 17 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `60618fc3` sparse_strips: optimize drawing rectangles with active rectangular cl…; `00b1f968` vello_cpu: Make `RenderContext` resizable (#1705) (at that commit the files were still `sparse_strips/vello_cpu/src/dispatch/multi_threaded/worker.rs` and `sparse_strips/vello_hybrid/src/scene.rs`); `39ec8632` Remove recordings from sparse strips renderers (#1611) (at that commit the files were still `sparse_strips/vello_cpu/src/dispatch/multi_threaded/worker.rs` and `sparse_strips/vello_hybrid/src/scene.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: scene.rs ↔ debug.rs vello_gpu/src/scene.rs:1— `vello_gpu/src/scene.rs` (context vello_gpu) and `vello_toy/src/debug.rs` (context vello_toy) sit in DIFFERENT parts of the tree yet change together 57% of the time (16 of the 28 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `00b1f968` vello_cpu: Make `RenderContext` resizable (#1705) (at that commit the files were still `sparse_strips/vello_hybrid/src/scene.rs` and `sparse_strips/vello_toy/src/debug.rs`); `d8b85aef` Add `RectU16` type for AABBs (#1559) (at that commit the files were still `sparse_strips/vello_hybrid/src/scene.rs` and `sparse_strips/vello_toy/src/debug.rs`); `1e44c057` perf: eliminate overdraw for opaque image fills (#1327) (at that commit the files were still `sparse_strips/vello_hybrid/src/scene.rs` and `sparse_strips/vello_toy/src/debug.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: strip_generator.rs ↔ debug.rs vello_common/src/strip_generator.rs:1— `vello_common/src/strip_generator.rs` (context vello_common) and `vello_toy/src/debug.rs` (context vello_toy) sit in DIFFERENT parts of the tree yet change together 54% of the time (15 of the 28 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `00b1f968` vello_cpu: Make `RenderContext` resizable (#1705) (at that commit the files were still `sparse_strips/vello_common/src/strip_generator.rs` and `sparse_strips/vello_toy/src/debug.rs`); `1b24e77b` Add early culling for lines fully left of the viewport. (#1368) (at that commit the files were still `sparse_strips/vello_common/src/strip_generator.rs` and `sparse_strips/vello_toy/src/debug.rs`); `d8b85aef` Add `RectU16` type for AABBs (#1559) (at that commit the files were still `sparse_strips/vello_common/src/strip_generator.rs` and `sparse_strips/vello_toy/src/debug.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: strip.rs ↔ single_threaded.rs vello_bench/src/strip.rs:1— `vello_bench/src/strip.rs` (context vello_bench) and `vello_cpu/src/dispatch/single_threaded.rs` (context vello_cpu) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `00b1f968` vello_cpu: Make `RenderContext` resizable (#1705) (at that commit the files were still `sparse_strips/vello_bench/src/strip.rs` and `sparse_strips/vello_cpu/src/dispatch/single_threaded.rs`); `b1ca1097` vello_sparse_strips: Optimize pixel-aligned rect filling by bypassing… (at that commit the files were still `sparse_strips/vello_bench/src/strip.rs` and `sparse_strips/vello_cpu/src/dispatch/single_threaded.rs`); `8d1bfe97` Make the aliasing threshold configurable (#1188) (at that commit the files were still `sparse_strips/vello_bench/src/strip.rs` and `sparse_strips/vello_cpu/src/dispatch/single_threaded.rs`) — run `git show` on any of them.
<html> without a lang .github/web-demo/native-webgl.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang .github/web-demo/research.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang .github/web-demo/vello-cpu.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang .github/web-demo/wgpu-webgl.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang .github/web-demo/wgpu-webgpu.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
Orphaned knowledge research/vello_shaders/src/cpu/flatten.rs: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 research/vello_research/src/render.rs: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.
AX8 · Test isolation· Production project references a test project · ×1
Production project references a test project: vello_bench → vello_dev_macros — `vello_bench` (production) references the test project `vello_dev_macros`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
TodoComment vello_toy/src/debug.rs:237— // TODO: Account for even-odd? — 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 vello_toy/src/debug.rs:266— // TODO: Account for even-odd? — 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 vello_toy/src/svg.rs:252— // TODO: It's possible that it should be kx first and then ky — 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 vello_tests/vello_example_scenes/src/random_text.rs:53— // TODO: Create a single pseudo-random number generator in `lib.rs` and use that for all scenes. — 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 vello_tests/vello_dev_macros/src/test.rs:725— // TODO: Tests with the same names in different modules can clash, see — 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 vello_tests/tests/filter.rs:23— // TODO: Update this test to use non-wide tile dimensions. — 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 vello_tests/tests/filter.rs:1474— // TODO: Change these tests back to 100x100 once edge modes are properly supported. — 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 vello_tests/tests/glyph.rs:562— // TODO: There seems to be a mismatch when using `Medium` here between GPU and CPU, — 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 vello_tests/tests/glyph.rs:696— // TODO: The cached versions of COLR glyphs seem to have a slight shift, investigate. — 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 vello_tests/tests/mask.rs:18— // TODO: Would be nice to take the settings from the current test context. — 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 vello_tests/tests/shrink.rs:22— // TODO: Add tests so we can actually measure the memory consumption too. — 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 vello_gpu_shaders/build.rs:65— // TODO: Format the generated code via `rustfmt`. — 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 vello_gpu_shaders/build.rs:66— // TODO: Use `quote` instead of string concatenation to generate 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 vello_gpu_shaders/src/types.rs:19— // TODO: It may make sense to pass through the sampler type. E.g. `sampler2D` or `usampler2D`. — 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 vello_gpu/src/filter.rs:610— // TODO: From my experiments, it would very much be worth it to add 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 vello_gpu/src/gradient_cache.rs:278— // TODO: Consider adding a method that generates LUT data directly into output buffer — 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 vello_gpu/src/scene.rs:85— // TODO: The bbox trait should take a reference to _all_ strips, and then we select — 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 vello_gpu/src/scene.rs:88— // TODO: We also should just compute the bbox during strip generation instead of — 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 vello_gpu/src/scene.rs:520— // TODO: Use a temporary storage for rect paths, like in `vello_cpu`. — 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 vello_gpu/src/scene.rs:557— // TODO: Maybe support rotated rectangles (https://github.com/linebender/vello/pull/1482#discussion_r2881223621)
TodoComment vello_gpu/src/scene.rs:878— // TODO: This API is not final. Supporting images from a pixmap is explicitly out of scope. — 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 vello_gpu/src/scene.rs:1063— // TODO: Consider validating paint/tint support at draw time so otherwise valid state updates — 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 vello_gpu/src/text.rs:58— // TODO: Use a config optionally provided by the user! — 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 vello_gpu/src/text.rs:119— // TODO: An upload error drops all remaining pending uploads. — 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.
MethodTooLong: Render.render_encoding_coarse research/vello_research/src/render.rs:135— MethodTooLong — render_encoding_coarse runs 325 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 225 over it, 3.25× 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: WgpuEngine.run_recording research/vello_research/src/wgpu_engine.rs:380— MethodTooLong — run_recording runs 310 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 210 over it, 3.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Tiles.make_tiles_analytic_aa_impl vello_common/src/tile.rs:530— MethodTooLong — make_tiles_analytic_aa_impl runs 259 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GlyphRunRenderer.draw_glyphs glifo/src/glyph.rs:433— MethodTooLong — draw_glyphs runs 239 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 139 over it, 2.39× 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: Tiles.make_tiles_msaa vello_common/src/tile.rs:958— MethodTooLong — make_tiles_msaa runs 223 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DrawGlyphs.try_draw_colr research/vello_research/src/scene.rs:665— MethodTooLong — try_draw_colr runs 153 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× 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: Fine.indexed_fill vello_cpu/src/fine/mod.rs:929— MethodTooLong — indexed_fill runs 153 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× 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: Resolver.resolve research/vello_encoding/src/resolve.rs:183— MethodTooLong — resolve runs 152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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: Worker.run_render_task vello_cpu/src/dispatch/multi_threaded/worker.rs:45— MethodTooLong — run_render_task runs 149 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: StripPipelines.new vello_gpu/src/render/wgpu/passes/strip.rs:46— MethodTooLong — new runs 148 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DebugRenderer.new research/vello_research/src/debug/renderer.rs:29— MethodTooLong — new runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebGlRendererContext.strip_pass_inner vello_gpu/src/render/webgl/passes/strip.rs:311— MethodTooLong — strip_pass_inner runs 126 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× 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: RendererContext.strip_pass_inner vello_gpu/src/render/wgpu/passes/strip.rs:436— MethodTooLong — strip_pass_inner runs 124 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: GpuResources.new vello_gpu/src/render/wgpu/resources.rs:298— MethodTooLong — new runs 109 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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: Renderer.probe vello_gpu/src/render/wgpu/probe.rs:84— MethodTooLong — probe runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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: TransientBindMap.create_bind_group research/vello_research/src/wgpu_engine.rs:1081— MethodTooLong — create_bind_group runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
vello_shaders::cpu::path_count::path_count_main (cognitive 91) research/vello_shaders/src/cpu/path_count.rs:13— vello_shaders::cpu::path_count::path_count_main has cognitive complexity 91 (threshold 15). Drivers by points: if/else 36 (83 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 49). 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.
vello_shaders::cpu::coarse::coarse_main (cognitive 88) research/vello_shaders/src/cpu/coarse.rs:183— vello_shaders::cpu::coarse::coarse_main has cognitive complexity 88 (threshold 15). Drivers by points: if/else 13 (50 pts), loops 8 (24 pts), match/switch 2 (11 pts), boolean chains 3 (nesting depth added 62). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vello_shaders::cpu::path_tiling::path_tiling_main (cognitive 62) research/vello_shaders/src/cpu/path_tiling.rs:15— vello_shaders::cpu::path_tiling::path_tiling_main has cognitive complexity 62 (threshold 15). Drivers by points: if/else 32 (59 pts), boolean chains 2, loops 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vello_shaders::compile::preprocess::preprocess (cognitive 57) research/vello_shaders/src/compile/preprocess.rs:37— vello_shaders::compile::preprocess::preprocess has cognitive complexity 57 (threshold 15). Drivers by points: if/else 14 (46 pts), match/switch 2 (6 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vello_shaders::cpu::flatten::flatten_main (cognitive 52) research/vello_shaders/src/cpu/flatten.rs:666— vello_shaders::cpu::flatten::flatten_main has cognitive complexity 52 (threshold 15). Drivers by points: if/else 19 (49 pts), boolean chains 2, loops 1 (nesting depth added 30). 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.
vello_shaders::cpu::flatten::flatten_euler (cognitive 48) research/vello_shaders/src/cpu/flatten.rs:203— vello_shaders::cpu::flatten::flatten_euler has cognitive complexity 48 (threshold 15). Drivers by points: if/else 20 (36 pts), match/switch 1 (5 pts), loops 2 (4 pts), boolean chains 3 (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.
vello_shaders::cpu::draw_leaf::draw_leaf_main (cognitive 43) research/vello_shaders/src/cpu/draw_leaf.rs:14— vello_shaders::cpu::draw_leaf::draw_leaf_main has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (35 pts), match/switch 1 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vello_shaders::cpu::binning::binning_main (cognitive 33) research/vello_shaders/src/cpu/binning.rs:25— vello_shaders::cpu::binning::binning_main has cognitive complexity 33 (threshold 15). Drivers by points: loops 8 (21 pts), if/else 3 (11 pts), boolean chains 1 (nesting depth added 21). 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.
vello_shaders::cpu::flatten::draw_join (cognitive 26) research/vello_shaders/src/cpu/flatten.rs:427— vello_shaders::cpu::flatten::draw_join has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 2, match/switch 1 (nesting depth added 11). 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.
vello_shaders::cpu::fine::fine_main (cognitive 23) research/vello_shaders/src/cpu/fine.rs:112— vello_shaders::cpu::fine::fine_main has cognitive complexity 23 (threshold 15). Drivers by points: loops 6 (17 pts), if/else 1 (3 pts), match/switch 1 (3 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
vello_shaders::cpu::fine::fill_path (cognitive 22) research/vello_shaders/src/cpu/fine.rs:51— vello_shaders::cpu::fine::fill_path has cognitive complexity 22 (threshold 15). Drivers by points: loops 7 (16 pts), if/else 4 (6 pts) (nesting depth added 11). 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.
vello_shaders::compile::permutations::parse (cognitive 18) research/vello_shaders/src/compile/permutations.rs:14— vello_shaders::compile::permutations::parse has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 1, 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.
vello_shaders::cpu::flatten::read_path_segment (cognitive 17) research/vello_shaders/src/cpu/flatten.rs:581— vello_shaders::cpu::flatten::read_path_segment has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2 (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.
FileTooLong: src/glyph.rs glifo/src/glyph.rs— FileTooLong — 1310 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 810 over it, 2.62× 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: src/wgpu_engine.rs research/vello_research/src/wgpu_engine.rs— FileTooLong — 896 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 63% of them inside a single declaration: WgpuEngine (2 blocks, 31-882). The bar is 500 significant lines; this is 396 over it, 1.79× 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: fine/mod.rs vello_cpu/src/fine/mod.rs— FileTooLong — 765 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 265 over it, 1.53× 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: src/tile.rs vello_common/src/tile.rs— FileTooLong — 734 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 74% of them inside a single declaration: Tiles (2 blocks, 425-1293). The bar is 500 significant lines; this is 234 over it, 1.47× 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: src/scene.rs research/vello_research/src/scene.rs— FileTooLong — 732 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 232 over it, 1.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/encode.rs vello_common/src/encode.rs— FileTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 179 over it, 1.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: wgpu/resources.rs vello_gpu/src/render/wgpu/resources.rs— FileTooLong — 660 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 75% of them inside a single declaration: GpuResources (3 blocks, 240-924). The bar is 500 significant lines; this is 160 over it, 1.32× 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: cpu/flatten.rs research/vello_shaders/src/cpu/flatten.rs— FileTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 131 over it, 1.26× 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: webgl/resources.rs vello_gpu/src/render/webgl/resources.rs— FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 115 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: dispatch/multi_threaded.rs vello_cpu/src/dispatch/multi_threaded.rs— FileTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: MultiThreadedDispatcher (5 blocks, 56-729). The bar is 500 significant lines; this is 107 over it, 1.21× 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: src/scene.rs vello_gpu/src/scene.rs— FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 78% of them inside a single declaration: Scene (3 blocks, 247-1061). The bar is 500 significant lines; this is 53 over it, 1.11× 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: schedule/mod.rs vello_gpu/src/schedule/mod.rs— FileTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 32 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/render.rs vello_cpu/src/render.rs— FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: RenderContext (2 blocks, 126-989). The bar is 500 significant lines; this is 14 over it, 1.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.
Duplicated block (6 lines × 2) research/vello_encoding/src/glyph_cache.rs:294— research/vello_encoding/src/glyph_cache.rs:294-299 | research/vello_research/src/scene.rs:1108-1113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) vello_common/src/multi_atlas.rs:255— vello_common/src/multi_atlas.rs:255-260 | vello_common/src/multi_atlas.rs:367-372 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vello_common/src/multi_atlas.rs:255` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) vello_cpu/src/render.rs:557— vello_cpu/src/render.rs:557-566 | vello_gpu/src/scene.rs:758-763 — before extracting anything, compare `vello_cpu/src/render.rs` and `vello_gpu/src/scene.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vello_cpu/src/render.rs:557` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) vello_gpu/src/render/webgl/passes/blend.rs:163— vello_gpu/src/render/webgl/passes/blend.rs:163-168 | vello_gpu/src/render/webgl/passes/filter.rs:182-187 — 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 `vello_gpu/src/render/webgl/passes/blend.rs:163` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) research/vello_shaders/src/cpu/path_count.rs:71— research/vello_shaders/src/cpu/path_count.rs:71-76 | research/vello_shaders/src/cpu/path_count.rs:79-84 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `research/vello_shaders/src/cpu/path_count.rs:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) vello_bench/src/allocator.rs:30— vello_bench/src/allocator.rs:30-35 | vello_bench/src/allocator.rs:66-71 — both copies are in the same file, so extract the 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) research/vello_encoding/src/glyph_cache.rs:286— research/vello_encoding/src/glyph_cache.rs:286-291 | research/vello_research/src/scene.rs:1100-1105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) vello_gpu/src/render/webgl/mod.rs:314— vello_gpu/src/render/webgl/mod.rs:314-319 | vello_gpu/src/render/wgpu/mod.rs:385-390 — `vello_gpu/src/render/webgl/mod.rs` and `vello_gpu/src/render/wgpu/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) research/vello_shaders/src/cpu/draw_reduce.rs:27— research/vello_shaders/src/cpu/draw_reduce.rs:27-32 | research/vello_shaders/src/cpu/pathtag_reduce.rs:27-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) research/vello_shaders/src/cpu/path_count_setup.rs:10— research/vello_shaders/src/cpu/path_count_setup.rs:10-15 | research/vello_shaders/src/cpu/path_tiling_setup.rs:10-15 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) vello_common/src/pico_svg.rs:248— vello_common/src/pico_svg.rs:248-253 | vello_common/src/pico_svg.rs:262-267 — both copies are in the same file, so extract the 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 `vello_common/src/pico_svg.rs:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) vello_tests/vello_example_scenes/src/filter.rs:491— vello_tests/vello_example_scenes/src/filter.rs:491-496 | vello_tests/vello_example_scenes/src/filter.rs:499-504 — both copies are in the same file, so extract the 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 `vello_tests/vello_example_scenes/src/filter.rs:491` 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.
FunctionTooLong: vello_common::strip::render_impl vello_common/src/strip.rs:331— FunctionTooLong — vello_common::strip::render_impl runs 208 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: vello::shaders::full_shaders research/vello_research/src/shaders.rs:48— FunctionTooLong — vello::shaders::full_shaders runs 178 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: vello_shaders::cpu::coarse::coarse_main research/vello_shaders/src/cpu/coarse.rs:183— FunctionTooLong — vello_shaders::cpu::coarse::coarse_main runs 164 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× 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: vello_shaders::cpu::draw_leaf::draw_leaf_main research/vello_shaders/src/cpu/draw_leaf.rs:14— FunctionTooLong — vello_shaders::cpu::draw_leaf::draw_leaf_main runs 164 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× 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: vello_shaders::cpu::flatten::flatten_main research/vello_shaders/src/cpu/flatten.rs:666— FunctionTooLong — vello_shaders::cpu::flatten::flatten_main runs 140 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 40 over it, 1.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.
FunctionTooLong: vello_shaders::cpu::flatten::flatten_euler research/vello_shaders/src/cpu/flatten.rs:203— FunctionTooLong — vello_shaders::cpu::flatten::flatten_euler runs 135 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
FunctionTooLong: vello_shaders::cpu::path_tiling::path_tiling_main research/vello_shaders/src/cpu/path_tiling.rs:15— FunctionTooLong — vello_shaders::cpu::path_tiling::path_tiling_main runs 120 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: vello_gpu::render::webgl::resources::create_webgl_resources vello_gpu/src/render/webgl/resources.rs:596— FunctionTooLong — vello_gpu::render::webgl::resources::create_webgl_resources runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: vello_shaders::cpu::path_count::path_count_main research/vello_shaders/src/cpu/path_count.rs:13— FunctionTooLong — vello_shaders::cpu::path_count::path_count_main runs 114 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 14 over it, 1.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.
FunctionTooLong: vello_shaders::compile::preprocess::preprocess research/vello_shaders/src/compile/preprocess.rs:37— FunctionTooLong — vello_shaders::compile::preprocess::preprocess runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
ClassTooLong: WgpuEngine research/vello_research/src/wgpu_engine.rs:31— ClassTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 2 blocks, lines 31-882. The bar is 400 significant lines; this is 162 over it, 1.41× 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: Tiles vello_common/src/tile.rs:425— ClassTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 12 methods, 2 blocks, lines 425-1293. The bar is 400 significant lines; this is 140 over it, 1.35× 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: GpuResources vello_gpu/src/render/wgpu/resources.rs:240— ClassTooLong — 495 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 28 methods, 3 blocks, lines 240-924. The bar is 400 significant lines; this is 95 over it, 1.24× 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: MultiThreadedDispatcher vello_cpu/src/dispatch/multi_threaded.rs:56— ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 11 methods, 5 blocks, lines 56-729. The bar is 400 significant lines; this is 37 over it, 1.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: Scene vello_gpu/src/scene.rs:247— ClassTooLong — 429 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 56 methods, 3 blocks, lines 247-1061. The bar is 400 significant lines; this is 29 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RenderContext vello_cpu/src/render.rs:126— ClassTooLong — 415 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 61 methods, 2 blocks, lines 126-989. The bar is 400 significant lines; this is 15 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Render research/vello_research/src/render.rs:23— ClassTooLong — 414 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 4 blocks, lines 23-653. The bar is 400 significant lines; this is 14 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Fine vello_cpu/src/fine/mod.rs:518— ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 16 methods, 2 blocks, lines 518-1152. The bar is 400 significant lines; this is 10 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (11 lines × 2) research/vello_encoding/src/mask.rs:19— research/vello_encoding/src/mask.rs:19-29 | research/vello_encoding/src/mask.rs:66-76 — both copies are in the same file, so extract the 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 `research/vello_encoding/src/mask.rs:19` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) vello_cpu/src/dispatch/multi_threaded/worker.rs:96— vello_cpu/src/dispatch/multi_threaded/worker.rs:96-106 | vello_cpu/src/dispatch/multi_threaded/worker.rs:132-142 — both copies are in the same file, so extract the 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 `vello_cpu/src/dispatch/multi_threaded/worker.rs:96` 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 (11 lines × 2) vello_cpu/src/fine/mod.rs:143— vello_cpu/src/fine/mod.rs:143-153 | vello_cpu/src/fine/mod.rs:156-166 — both copies are in the same file, so extract the 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) vello_gpu/src/render/wgpu/passes/clear.rs:71— vello_gpu/src/render/wgpu/passes/clear.rs:71-81 | vello_gpu/src/render/wgpu/passes/mod.rs:148-159 — 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 `vello_gpu/src/render/wgpu/passes/clear.rs:71` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 lines × 2) vello_cpu/src/fine/highp/mod.rs:255— vello_cpu/src/fine/highp/mod.rs:255-265 | vello_cpu/src/fine/lowp/mod.rs:280-290 — 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 `vello_cpu/src/fine/highp/mod.rs:255` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) vello_gpu/src/render/webgl/passes/mod.rs:173— vello_gpu/src/render/webgl/passes/mod.rs:173-183 | vello_gpu/src/render/wgpu/passes/mod.rs:265-275 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) vello_bench/src/fine/image.rs:153— vello_bench/src/fine/image.rs:153-163 | vello_bench/src/fine/image.rs:168-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vello_bench/src/fine/image.rs:153` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) vello_tests/vello_example_scenes/src/image.rs:117— vello_tests/vello_example_scenes/src/image.rs:117-127 | vello_tests/vello_example_scenes/src/image.rs:130-140 — both copies are in the same file, so extract the 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 `vello_tests/vello_example_scenes/src/image.rs:117` 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) research/vello_encoding/src/encoding.rs:389— research/vello_encoding/src/encoding.rs:389-395 | research/vello_encoding/src/encoding.rs:414-420 — both copies are in the same file, so extract the 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 `research/vello_encoding/src/encoding.rs:389` 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) vello_common/src/filter_effects.rs:617— vello_common/src/filter_effects.rs:617-623 | vello_common/src/filter_effects.rs:651-657 — both copies are in the same file, so extract the 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 `vello_common/src/filter_effects.rs:617` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) vello_gpu/src/render/wgpu/passes/clear.rs:54— vello_gpu/src/render/wgpu/passes/clear.rs:54-60 | vello_gpu/src/render/wgpu/passes/strip.rs:163-169 — 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 `vello_gpu/src/render/wgpu/passes/clear.rs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) research/vello_shaders/src/cpu/path_count.rs:26— research/vello_shaders/src/cpu/path_count.rs:26-32 | research/vello_shaders/src/cpu/path_tiling.rs:35-41 — 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 (7 lines × 2) vello_cpu/src/fine/common/gradient/mod.rs:107— vello_cpu/src/fine/common/gradient/mod.rs:107-113 | vello_cpu/src/fine/common/gradient/mod.rs:118-124 — both copies are in the same file, so extract the 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 `vello_cpu/src/fine/common/gradient/mod.rs:107` 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) vello_cpu/src/fine/mod.rs:716— vello_cpu/src/fine/mod.rs:716-722 | vello_cpu/src/fine/mod.rs:748-754 — both copies are in the same file, so extract the 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 `vello_cpu/src/fine/mod.rs:716` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) research/vello_shaders/src/cpu/binning.rs:64— research/vello_shaders/src/cpu/binning.rs:64-70 | research/vello_shaders/src/cpu/tile_alloc.rs:32-38 — 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 `research/vello_shaders/src/cpu/binning.rs:64` 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) vello_cpu/src/text.rs:448— vello_cpu/src/text.rs:448-454 | vello_gpu/src/text.rs:349-355 — 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.
Hotspot: vello_cpu/src/fine/mod.rs vello_cpu/src/fine/mod.rs:929— vello_cpu/src/fine/mod.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Fine::indexed_fill at line 929. 1 of those changes was a fix/bug commit, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:27:11 +00:00' --until='2026-11-13 17:27:11 +00:00' --full-history --no-merges -- vello_cpu/src/fine/mod.rs`: 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: glifo/src/glyph.rs glifo/src/glyph.rs:433— glifo/src/glyph.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in GlyphRunRenderer::draw_glyphs at line 433. 1 of those changes was a fix/bug commit, and the other 8 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:27:11 +00:00' --until='2026-11-13 17:27:11 +00:00' --full-history --no-merges -- glifo/src/glyph.rs`: 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: vello_tests/vello_dev_macros/src/test.rs vello_tests/vello_dev_macros/src/test.rs:738— vello_tests/vello_dev_macros/src/test.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in vello_dev_macros::test::parse_args at line 738. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:27:11 +00:00' --until='2026-11-13 17:27:11 +00:00' --full-history --no-merges -- vello_tests/vello_dev_macros/src/test.rs`: 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: research/vello_research/src/scene.rs research/vello_research/src/scene.rs:665— research/vello_research/src/scene.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in DrawGlyphs::try_draw_colr at line 665. 2 of those changes were fix/bug commits, and the other 2 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:27:11 +00:00' --until='2026-11-13 17:27:11 +00:00' --full-history --no-merges -- research/vello_research/src/scene.rs`: 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: vello_common/src/flatten_simd.rs vello_common/src/flatten_simd.rs:49— vello_common/src/flatten_simd.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in vello_common::flatten_simd::flatten at line 49. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:27:11 +00:00' --until='2026-11-13 17:27:11 +00:00' --full-history --no-merges -- vello_common/src/flatten_simd.rs`: 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: vello_common/src/clip.rs vello_common/src/clip.rs:414— vello_common/src/clip.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in vello_common::clip::intersect_impl at line 414. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:27:11 +00:00' --until='2026-11-13 17:27:11 +00:00' --full-history --no-merges -- vello_common/src/clip.rs`: 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: vello_gpu/src/render/wgpu/passes/strip.rs vello_gpu/src/render/wgpu/passes/strip.rs:436— vello_gpu/src/render/wgpu/passes/strip.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in RendererContext::strip_pass_inner at line 436. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:27:11 +00:00' --until='2026-11-13 17:27:11 +00:00' --full-history --no-merges -- vello_gpu/src/render/wgpu/passes/strip.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (8 lines × 2) research/vello_encoding/src/estimate.rs:102— research/vello_encoding/src/estimate.rs:102-109 | research/vello_encoding/src/estimate.rs:120-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) research/vello_research/src/wgpu_engine.rs:958— research/vello_research/src/wgpu_engine.rs:958-966 | research/vello_research/src/wgpu_engine.rs:1147-1154 — both copies are in the same file, so extract the 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 `research/vello_research/src/wgpu_engine.rs:958` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `proxy` to `ImageProxy` in one and `&ImageProxy` 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 (8 lines × 2) glifo/src/colr.rs:609— glifo/src/colr.rs:609-616 | vello_tests/vello_example_scenes/src/emoji_grid.rs:274-281 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) glifo/src/glyph.rs:152— glifo/src/glyph.rs:152-159 | research/vello_encoding/src/glyph.rs:66-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) vello_tests/vello_example_scenes/src/filter.rs:112— vello_tests/vello_example_scenes/src/filter.rs:112-119 | vello_tests/vello_example_scenes/src/filter.rs:454-461 — both copies are in the same file, so extract the 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 `vello_tests/vello_example_scenes/src/filter.rs:112` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) vello_tests/vello_example_scenes/src/filter_elements.rs:259— vello_tests/vello_example_scenes/src/filter_elements.rs:259-266 | vello_tests/vello_example_scenes/src/multi_image.rs:146-153 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) research/vello_research_tests/src/compare.rs:126— research/vello_research_tests/src/compare.rs:126-133 | research/vello_research_tests/src/snapshot.rs:315-322 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) vello_common/src/clip.rs:491— vello_common/src/clip.rs:491-495 | vello_common/src/clip.rs:504-508 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) vello_cpu/src/fine/highp/blend.rs:245— vello_cpu/src/fine/highp/blend.rs:245-249 | vello_cpu/src/fine/highp/blend.rs:250-254 — both copies are in the same file, so extract the 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) vello_cpu/src/text.rs:298— vello_cpu/src/text.rs:298-302 | vello_gpu/src/text.rs:310-314 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) research/vello_shaders/src/cpu/binning.rs:111— research/vello_shaders/src/cpu/binning.rs:111-115 | research/vello_shaders/src/cpu/draw_leaf.rs:212-216 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `research/vello_shaders/src/cpu/binning.rs:116` calls `as_typed_mut` and `research/vello_shaders/src/cpu/draw_leaf.rs:217` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) vello_bench/src/fine/pack.rs:23— vello_bench/src/fine/pack.rs:23-27 | vello_bench/src/fine/pack.rs:36-40 — both copies are in the same file, so extract the 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 `vello_bench/src/fine/pack.rs:23` 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) vello_tests/vello_example_scenes/src/path.rs:74— vello_tests/vello_example_scenes/src/path.rs:74-78 | vello_tests/vello_example_scenes/src/path.rs:399-403 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) vello_tests/vello_example_scenes/src/path.rs:400— vello_tests/vello_example_scenes/src/path.rs:400-404 | vello_tests/vello_example_scenes/src/path.rs:509-513 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
vello_shaders::cpu::path_count::path_count_main (cyclomatic 33) research/vello_shaders/src/cpu/path_count.rs:13— vello_shaders::cpu::path_count::path_count_main 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.
vello_shaders::cpu::coarse::coarse_main (cyclomatic 31) research/vello_shaders/src/cpu/coarse.rs:183— vello_shaders::cpu::coarse::coarse_main has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vello_shaders::cpu::path_tiling::path_tiling_main (cyclomatic 25) research/vello_shaders/src/cpu/path_tiling.rs:15— vello_shaders::cpu::path_tiling::path_tiling_main 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.
vello_shaders::compile::preprocess::preprocess (cyclomatic 24) research/vello_shaders/src/compile/preprocess.rs:37— vello_shaders::compile::preprocess::preprocess has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vello_shaders::cpu::flatten::flatten_euler (cyclomatic 21) research/vello_shaders/src/cpu/flatten.rs:203— vello_shaders::cpu::flatten::flatten_euler 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.
vello_shaders::cpu::draw_leaf::draw_leaf_main (cyclomatic 19) research/vello_shaders/src/cpu/draw_leaf.rs:14— vello_shaders::cpu::draw_leaf::draw_leaf_main 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.
vello_common::strip::render_impl (cognitive 67) vello_common/src/strip.rs:331— vello_common::strip::render_impl has cognitive complexity 67 (threshold 15). Drivers by points: if/else 21 (38 pts), loops 6 (18 pts), boolean chains 7, match/switch 2 (4 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vello_common::flatten_simd::flatten (cognitive 44) vello_common/src/flatten_simd.rs:49— vello_common::flatten_simd::flatten has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (28 pts), loops 3 (9 pts), boolean chains 5, match/switch 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vello_common::clip::intersect_impl (cognitive 38) vello_common/src/clip.rs:414— vello_common::clip::intersect_impl has cognitive complexity 38 (threshold 15). Drivers by points: match/switch 4 (15 pts), if/else 6 (14 pts), loops 3 (8 pts), boolean chains 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.
vello_common::pico_svg::parse_transform (cognitive 27) vello_common/src/pico_svg.rs:234— vello_common::pico_svg::parse_transform has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (18 pts), match/switch 2 (8 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.
vello_common::encode::validate (cognitive 22) vello_common/src/encode.rs:244— vello_common::encode::validate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, loops 1, 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.
vello_common::rect::render_impl (cognitive 22) vello_common/src/rect.rs:46— vello_common::rect::render_impl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, loops 2 (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.
Duplicated block (13 lines × 2) glifo/src/glyph.rs:1993— glifo/src/glyph.rs:1993-2006 | research/vello_encoding/src/glyph_cache.rs:100-112 — before extracting anything, compare `glifo/src/glyph.rs` and `research/vello_encoding/src/glyph_cache.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `&mut` in one and `crate) fn maintain(&mut` 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 (13 lines × 2) glifo/src/glyph.rs:2307— glifo/src/glyph.rs:2307-2319 | vello_common/src/encode.rs:463-475 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) research/vello_shaders/src/compile/mod.rs:200— research/vello_shaders/src/compile/mod.rs:200-212 | research/vello_shaders/src/compile/preprocess.rs:11-23 — 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 `research/vello_shaders/src/compile/mod.rs:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) vello_cpu/src/fine/common/image.rs:181— vello_cpu/src/fine/common/image.rs:181-193 | vello_cpu/src/fine/lowp/image.rs:40-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) research/vello_research/src/debug/renderer.rs:122— research/vello_research/src/debug/renderer.rs:122-134 | research/vello_research/src/debug/renderer.rs:161-174 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `research/vello_research/src/debug/renderer.rs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) vello_tests/vello_example_scenes/src/filter.rs:193— vello_tests/vello_example_scenes/src/filter.rs:193-205 | vello_tests/vello_example_scenes/src/filter.rs:310-323 — both copies are in the same file, so extract the 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 `vello_tests/vello_example_scenes/src/filter.rs:193` 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) research/vello_research/src/wgpu_engine.rs:330— research/vello_research/src/wgpu_engine.rs:330-338 | research/vello_research/src/wgpu_engine.rs:856-865 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) vello_common/src/probe.rs:445— vello_common/src/probe.rs:445-453 | vello_common/src/probe.rs:468-476 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) vello_cpu/src/text.rs:277— vello_cpu/src/text.rs:277-285 | vello_gpu/src/text.rs:289-297 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) vello_cpu/src/render.rs:793— vello_cpu/src/render.rs:793-801 | vello_gpu/src/scene.rs:406-414 — before extracting anything, compare `vello_cpu/src/render.rs` and `vello_gpu/src/scene.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) vello_tests/vello_example_scenes/src/path.rs:337— vello_tests/vello_example_scenes/src/path.rs:337-345 | vello_tests/vello_example_scenes/src/path.rs:364-372 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) vello_tests/vello_example_scenes/src/filter.rs:69— vello_tests/vello_example_scenes/src/filter.rs:69-77 | vello_tests/vello_example_scenes/src/filter.rs:385-393 — both copies are in the same file, so extract the 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 `vello_tests/vello_example_scenes/src/filter.rs:69` 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.
AC3 · Page structure· Page without a main landmark · ×5
Page without a main landmark .github/web-demo/native-webgl.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .github/web-demo/research.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .github/web-demo/vello-cpu.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .github/web-demo/wgpu-webgl.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .github/web-demo/wgpu-webgpu.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
HackComment research/vello_research/src/render.rs:206— // HACK: The coarse workgroup counts is the number of active bins. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment research/vello_research/src/render.rs:223— // HACK: wgpu doesn't allow empty buffers, so we make sure that the scene buffer we upload — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment research/vello_research/src/scene.rs:949— // Hack: If we don't have a clip box, we guess a rectangle we hope is big enough — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment research/vello_encoding/src/resolve.rs:468— // HACK: We pretend that the encoding was empty. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment research/examples/scenes/src/test_scenes.rs:2300— // HACK: Porter-Duff "over" the base color, restoring full alpha — 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.
Change coupling: multi_threaded.rs ↔ single_threaded.rs vello_cpu/src/dispatch/multi_threaded.rs:1— `vello_cpu/src/dispatch/multi_threaded.rs` and `vello_cpu/src/dispatch/single_threaded.rs` change together 79% of the time (34 of the 43 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) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 34 shared commits counted here, the most recent 3 are `60618fc3` sparse_strips: optimize drawing rectangles with active rectangular cl…; `4714328a` sparse_strips: Add a `push_clip_rect` method (#1916); `885d97d2` vello_cpu: Support configurable target clears (#1866) — run `git show` on any of them.
Change coupling: mod.rs ↔ mod.rs vello_cpu/src/fine/highp/mod.rs:1— `vello_cpu/src/fine/highp/mod.rs` and `vello_cpu/src/fine/lowp/mod.rs` change together 73% of the time (8 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `72de42f7` vello_cpu: Support negative render offsets (#2028); `200cb28d` vello_cpu: Make `paint_*` methods consume `self` (#1730) (at that commit the files were still `sparse_strips/vello_cpu/src/fine/highp/mod.rs` and `sparse_strips/vello_cpu/src/fine/lowp/mod.rs`); `7a689541` spare_strips: Add image tinting support (#1460) (at that commit the files were still `sparse_strips/vello_cpu/src/fine/highp/mod.rs` and `sparse_strips/vello_cpu/src/fine/lowp/mod.rs`) — run `git show` on any of them.
Change coupling: worker.rs ↔ single_threaded.rs vello_cpu/src/dispatch/multi_threaded/worker.rs:1— `vello_cpu/src/dispatch/multi_threaded/worker.rs` and `vello_cpu/src/dispatch/single_threaded.rs` change together 71% of the time (12 of the 17 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `60618fc3` sparse_strips: optimize drawing rectangles with active rectangular cl…; `af32d531` sparse_strips: Introduce `Padding` type and streamline clip handling … (at that commit the files were still `sparse_strips/vello_cpu/src/dispatch/multi_threaded/worker.rs` and `sparse_strips/vello_cpu/src/dispatch/single_threaded.rs`); `00b1f968` vello_cpu: Make `RenderContext` resizable (#1705) (at that commit the files were still `sparse_strips/vello_cpu/src/dispatch/multi_threaded/worker.rs` and `sparse_strips/vello_cpu/src/dispatch/single_threaded.rs`) — run `git show` on any of them.
Change coupling: worker.rs ↔ render.rs vello_cpu/src/dispatch/multi_threaded/worker.rs:1— `vello_cpu/src/dispatch/multi_threaded/worker.rs` and `vello_cpu/src/render.rs` change together 65% of the time (11 of the 17 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `00b1f968` vello_cpu: Make `RenderContext` resizable (#1705) (at that commit the files were still `sparse_strips/vello_cpu/src/dispatch/multi_threaded/worker.rs` and `sparse_strips/vello_cpu/src/render.rs`); `39ec8632` Remove recordings from sparse strips renderers (#1611) (at that commit the files were still `sparse_strips/vello_cpu/src/dispatch/multi_threaded/worker.rs` and `sparse_strips/vello_cpu/src/render.rs`); `56820883` Add support for non-isolated masks (#1237) (at that commit the files were still `sparse_strips/vello_cpu/src/dispatch/multi_threaded/worker.rs` and `sparse_strips/vello_cpu/src/render.rs`) — run `git show` on any of them.
Change coupling: renderer.rs ↔ lib.rs vello_tests/src/renderer.rs:1— `vello_tests/src/renderer.rs` and `vello_tests/vello_example_scenes/src/lib.rs` change together 53% of the time (8 of the 15 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `4714328a` sparse_strips: Add a `push_clip_rect` method (#1916) (at that commit the file was still `vello_tests/tests/renderer.rs`); `354661ad` vello_hybrid: Integrate external textures into the existing `set_pain… (at that commit the files were still `sparse_strips/vello_sparse_tests/tests/renderer.rs` and `sparse_strips/vello_example_scenes/src/lib.rs`); `08576de9` vello_hybrid: Support extend modes for external texture rects (#1813) (at that commit the files were still `sparse_strips/vello_sparse_tests/tests/renderer.rs` and `sparse_strips/vello_example_scenes/src/lib.rs`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×5
Edited copy of a member (16 corresponding lines) research/vello_encoding/src/encoding.rs:385— research/vello_encoding/src/encoding.rs:385-401 | research/vello_encoding/src/encoding.rs:411-426 — 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) vello_bench/src/allocations/tiger.rs:49— vello_bench/src/allocations/tiger.rs:49-66 | vello_bench/src/allocations/tiger.rs:68-83 — 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) vello_cpu/src/coarse/depth.rs:250— vello_cpu/src/coarse/depth.rs:250-268 | vello_cpu/src/coarse/depth.rs:277-292 — 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) vello_cpu/src/render.rs:493— vello_cpu/src/render.rs:493-512 | vello_gpu/src/scene.rs:703-718 — 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) vello_common/src/filter/drop_shadow.rs:68— vello_common/src/filter/drop_shadow.rs:68-83 | vello_common/src/filter/gaussian_blur.rs:147-162 — 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 (17 corresponding lines) · ×5
Edited copy of a member (17 corresponding lines) research/vello_research/src/scene.rs:975— research/vello_research/src/scene.rs:975-991 | research/vello_research/src/scene.rs:1063-1086 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) research/vello_encoding/src/mask.rs:13— research/vello_encoding/src/mask.rs:13-29 | research/vello_encoding/src/mask.rs:60-76 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) vello_bench/src/fine/gradient.rs:160— vello_bench/src/fine/gradient.rs:160-176 | vello_bench/src/fine/gradient.rs:182-201 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) vello_gpu/src/scene.rs:362— vello_gpu/src/scene.rs:362-379 | vello_gpu/src/scene.rs:436-452 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) research/vello_research_tests/src/compare.rs:46— research/vello_research_tests/src/compare.rs:46-62 | research/vello_research_tests/src/snapshot.rs:62-80 — 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 copy of a member (9 corresponding lines) · ×5
Edited copy of a member (9 corresponding lines) vello_cpu/src/fine/lowp/mod.rs:364— vello_cpu/src/fine/lowp/mod.rs:364-377 | vello_cpu/src/fine/lowp/mod.rs:436-444 — 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) research/vello_shaders/src/cpu.rs:106— research/vello_shaders/src/cpu.rs:106-114 | research/vello_shaders/src/cpu.rs:128-136 — 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) vello_cpu/src/render.rs:804— vello_cpu/src/render.rs:804-818 | vello_gpu/src/scene.rs:417-425 — 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) fuzz/fuzz_targets/cpu_gpu_differential/scene.rs:177— fuzz/fuzz_targets/cpu_gpu_differential/scene.rs:177-185 | fuzz/fuzz_targets/cpu_gpu_differential/scene.rs:548-560 — 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) vello_tests/vello_example_scenes/src/random_text.rs:268— vello_tests/vello_example_scenes/src/random_text.rs:268-284 | vello_tests/vello_example_scenes/src/text.rs:111-119 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×5
Edited copy of a member (8 corresponding lines) vello_cpu/src/fine/highp/mod.rs:357— vello_cpu/src/fine/highp/mod.rs:357-364 | vello_cpu/src/fine/highp/mod.rs:444-454 — 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) vello_cpu/src/fine/highp/mod.rs:406— vello_cpu/src/fine/highp/mod.rs:406-414 | vello_cpu/src/fine/lowp/mod.rs:584-591 — 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) research/vello_shaders/src/cpu/euler.rs:223— research/vello_shaders/src/cpu/euler.rs:223-230 | research/vello_shaders/src/cpu/euler.rs:234-241 — 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) glifo/src/colr.rs:596— glifo/src/colr.rs:596-603 | research/vello_research/src/scene.rs:1214-1222 — 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) vello_gpu/src/render/webgl/passes/filter.rs:33— vello_gpu/src/render/webgl/passes/filter.rs:33-40 | vello_gpu/src/render/webgl/resources.rs:304-311 — 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 (12 lines × 2) research/vello_research/src/wgpu_engine.rs:436— research/vello_research/src/wgpu_engine.rs:436-447 | research/vello_research/src/wgpu_engine.rs:1133-1144 — both copies are in the same file, so extract the 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 `research/vello_research/src/wgpu_engine.rs:436` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) vello_cpu/src/dispatch/single_threaded.rs:301— vello_cpu/src/dispatch/single_threaded.rs:301-312 | vello_cpu/src/dispatch/single_threaded.rs:375-386 — both copies are in the same file, so extract the 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 `vello_cpu/src/dispatch/single_threaded.rs:301` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) vello_cpu/src/filter/gaussian_blur.rs:211— vello_cpu/src/filter/gaussian_blur.rs:211-222 | vello_cpu/src/filter/gaussian_blur.rs:260-271 — both copies are in the same file, so extract the 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 `vello_cpu/src/filter/gaussian_blur.rs:211` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) vello_cpu/src/fine/highp/blend.rs:182— vello_cpu/src/fine/highp/blend.rs:182-193 | vello_cpu/src/fine/highp/blend.rs:199-210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vello_cpu/src/fine/highp/blend.rs:182` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) vello_cpu/src/render.rs:520— vello_cpu/src/render.rs:520-531 | vello_gpu/src/scene.rs:726-737 — before extracting anything, compare `vello_cpu/src/render.rs` and `vello_gpu/src/scene.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vello_cpu/src/render.rs:520` 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.
vello_common::strip::render_impl (cyclomatic 33) vello_common/src/strip.rs:331— vello_common::strip::render_impl 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.
vello_common::flatten_simd::flatten (cyclomatic 24) vello_common/src/flatten_simd.rs:49— vello_common::flatten_simd::flatten has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vello_common::encode::validate (cyclomatic 17) vello_common/src/encode.rs:244— vello_common::encode::validate 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.
vello_common::clip::intersect_impl (cyclomatic 16) vello_common/src/clip.rs:414— vello_common::clip::intersect_impl has cyclomatic complexity 16 (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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×4
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×4
Edited copy of a member (10 corresponding lines) vello_cpu/src/render.rs:778— vello_cpu/src/render.rs:778-787 | vello_gpu/src/scene.rs:980-989 — 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) vello_cpu/src/fine/highp/mod.rs:425— vello_cpu/src/fine/highp/mod.rs:425-434 | vello_cpu/src/fine/lowp/mod.rs:603-612 — 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) vello_gpu/src/render/wgpu/passes/copy.rs:79— vello_gpu/src/render/wgpu/passes/copy.rs:79-88 | vello_gpu/src/render/wgpu/passes/filter.rs:336-345 — 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) research/vello_shaders/src/cpu/draw_leaf.rs:238— research/vello_shaders/src/cpu/draw_leaf.rs:238-247 | vello_common/src/encode.rs:1027-1036 — 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 (11–12 lines × 2) research/vello_research/src/scene.rs:976— research/vello_research/src/scene.rs:976-987 | research/vello_research/src/scene.rs:1064-1074 — both copies are in the same file, so extract the 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 (11–12 lines × 2) vello_common/src/tile.rs:688— vello_common/src/tile.rs:688-699 | vello_common/src/tile.rs:1024-1034 — both copies are in the same file, so extract the 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 `vello_common/src/tile.rs:688` 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–12 lines × 2) vello_common/src/tile.rs:714— vello_common/src/tile.rs:714-725 | vello_common/src/tile.rs:1073-1083 — both copies are in the same file, so extract the 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 `vello_common/src/tile.rs:714` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) vello_gpu/src/render/webgl/mod.rs:336— vello_gpu/src/render/webgl/mod.rs:336-347 | vello_gpu/src/render/wgpu/mod.rs:408-418 — `vello_gpu/src/render/webgl/mod.rs` and `vello_gpu/src/render/wgpu/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vello_gpu/src/render/webgl/mod.rs:336` 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.
Resolver::resolve (cognitive 76) research/vello_encoding/src/resolve.rs:183— Resolver::resolve has cognitive complexity 76 (threshold 15). Drivers by points: if/else 22 (50 pts), loops 12 (24 pts), match/switch 1 (2 pts) (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Resolver::resolve_pending_images (cognitive 20) research/vello_encoding/src/resolve.rs:509— Resolver::resolve_pending_images has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (6 pts), boolean chains 1 (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.
Resolver::resolve_patches (cognitive 18) research/vello_encoding/src/resolve.rs:401— Resolver::resolve_patches has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (4 pts), match/switch 1 (2 pts), 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.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×3
Edited copy of a member (24 corresponding lines) vello_cpu/src/fine/highp/mod.rs:104— vello_cpu/src/fine/highp/mod.rs:104-127 | vello_cpu/src/fine/lowp/mod.rs:145-170 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) vello_gpu/src/render/webgl/resources.rs:339— vello_gpu/src/render/webgl/resources.rs:339-372 | vello_gpu/src/render/wgpu/resources.rs:842-865 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) vello_gpu/src/render/webgl/resources.rs:829— vello_gpu/src/render/webgl/resources.rs:829-852 | vello_gpu/src/render/webgl/resources.rs:864-909 — 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 (20 corresponding lines) · ×3
Edited copy of a member (20 corresponding lines) glifo/src/glyph.rs:2232— glifo/src/glyph.rs:2232-2256 | research/vello_encoding/src/glyph_cache.rs:362-381 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) vello_bench/src/fine/gradient.rs:327— vello_bench/src/fine/gradient.rs:327-346 | vello_bench/src/fine/gradient.rs:348-367 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) vello_cpu/src/fine/lowp/mod.rs:304— vello_cpu/src/fine/lowp/mod.rs:304-323 | vello_cpu/src/fine/lowp/mod.rs:380-399 — 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 copy of a member (13 corresponding lines) · ×3
Edited copy of a member (13 corresponding lines) research/vello_encoding/src/path.rs:771— research/vello_encoding/src/path.rs:771-783 | research/vello_encoding/src/path.rs:800-816 — 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) research/vello_encoding/src/mask.rs:36— research/vello_encoding/src/mask.rs:36-48 | research/vello_encoding/src/mask.rs:83-98 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) glifo/src/colr.rs:116— glifo/src/colr.rs:116-128 | glifo/src/colr.rs:292-304 — 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 (23 corresponding lines) · ×3
Edited copy of a member (23 corresponding lines) vello_cpu/src/filter/gaussian_blur.rs:324— vello_cpu/src/filter/gaussian_blur.rs:324-346 | vello_cpu/src/filter/gaussian_blur.rs:358-380 — 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) vello_cpu/src/text.rs:226— vello_cpu/src/text.rs:226-249 | vello_gpu/src/text.rs:234-256 — 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) glifo/src/renderer.rs:261— glifo/src/renderer.rs:261-287 | glifo/src/renderer.rs:367-389 — 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 (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) vello_cpu/src/filter/gaussian_blur.rs:579— vello_cpu/src/filter/gaussian_blur.rs:579-585 | vello_cpu/src/filter/gaussian_blur.rs:593-599 — 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) research/vello_shaders/src/cpu/backdrop.rs:25— research/vello_shaders/src/cpu/backdrop.rs:25-31 | research/vello_shaders/src/cpu/pathtag_scan.rs:31-37 — 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) research/vello_encoding/src/glyph_cache.rs:293— research/vello_encoding/src/glyph_cache.rs:293-299 | research/vello_research/src/scene.rs:1107-1113 — 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 (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) vello_cpu/src/fine/highp/mod.rs:139— vello_cpu/src/fine/highp/mod.rs:139-150 | vello_cpu/src/fine/lowp/mod.rs:182-193 — 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) vello_cpu/src/fine/mod.rs:664— vello_cpu/src/fine/mod.rs:664-675 | vello_cpu/src/fine/mod.rs:681-692 — 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) vello_common/src/clip.rs:99— vello_common/src/clip.rs:99-111 | vello_gpu/src/scene.rs:389-400 — 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 (6 corresponding lines) · ×3
Edited copy of a member (6 corresponding lines) vello_cpu/src/fine/lowp/mod.rs:509— vello_cpu/src/fine/lowp/mod.rs:509-516 | vello_cpu/src/fine/highp/mod.rs:343-348 — 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) vello_bench/src/fine/fill.rs:23— vello_bench/src/fine/fill.rs:23-28 | vello_bench/src/fine/strip.rs:34-39 — 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) vello_bench/src/fine/fill.rs:31— vello_bench/src/fine/fill.rs:31-36 | vello_bench/src/fine/strip.rs:42-47 — 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.
Duplicated block (20 lines × 2) research/vello_research/src/wgpu_engine.rs:566— research/vello_research/src/wgpu_engine.rs:566-585 | research/vello_research/src/wgpu_engine.rs:624-643 — both copies are in the same file, so extract the 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 `research/vello_research/src/wgpu_engine.rs:566` 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 (20 lines × 2) vello_cpu/src/filter/gaussian_blur.rs:225— vello_cpu/src/filter/gaussian_blur.rs:225-244 | vello_cpu/src/filter/gaussian_blur.rs:274-293 — both copies are in the same file, so extract the 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 `vello_cpu/src/filter/gaussian_blur.rs:225` 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 (20 lines × 2) vello_tests/vello_example_scenes/src/filter.rs:172— vello_tests/vello_example_scenes/src/filter.rs:172-191 | vello_tests/vello_example_scenes/src/filter.rs:349-368 — both copies are in the same file, so extract the 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 `vello_tests/vello_example_scenes/src/filter.rs:172` 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 (14 lines × 2) vello_common/src/tile.rs:629— vello_common/src/tile.rs:629-642 | vello_common/src/tile.rs:780-793 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) vello_gpu/src/render/common/paint.rs:378— vello_gpu/src/render/common/paint.rs:378-391 | vello_gpu/src/render/common/paint.rs:413-426 — both copies are in the same file, so extract the 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 `vello_gpu/src/render/common/paint.rs:378` 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) research/vello_shaders/src/cpu/path_count.rs:39— research/vello_shaders/src/cpu/path_count.rs:39-52 | research/vello_shaders/src/cpu/path_tiling.rs:42-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `research/vello_shaders/src/cpu/path_tiling.rs:56` calls `floor` and `research/vello_shaders/src/cpu/path_count.rs:54` 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.
Tiles::make_tiles_msaa (cyclomatic 144) vello_common/src/tile.rs:958— Tiles::make_tiles_msaa has cyclomatic complexity 144 (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 file is where this pass's cyclomatic complexity CONCENTRATES: vello_common/src/tile.rs holds 2 of the 20 functions over the threshold — including the worst — and 157 of the 335 points over it (47%), 6.8× the next-largest file (assets/sbix/generate.py at 23). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Tiles::make_tiles_analytic_aa_impl (cyclomatic 43) vello_common/src/tile.rs:530— Tiles::make_tiles_analytic_aa_impl has cyclomatic complexity 43 (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 file is where this pass's cyclomatic complexity CONCENTRATES: vello_common/src/tile.rs holds 2 of the 20 functions over the threshold — including the worst — and 157 of the 335 points over it (47%), 6.8× the next-largest file (assets/sbix/generate.py at 23). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Tiles::make_tiles_msaa (cognitive 660) vello_common/src/tile.rs:958— Tiles::make_tiles_msaa has cognitive complexity 660 (threshold 15). Drivers by points: if/else 135 (526 pts), loops 15 (91 pts), boolean chains 43 (nesting depth added 467). 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 file is where this pass's cognitive complexity CONCENTRATES: vello_common/src/tile.rs holds 2 of the 40 functions over the threshold — including the worst — and 796 of the 1632 points over it (49%), 9.6× the next-largest file (research/vello_shaders/src/cpu/flatten.rs at 83). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Tiles::make_tiles_analytic_aa_impl (cognitive 166) vello_common/src/tile.rs:530— Tiles::make_tiles_analytic_aa_impl has cognitive complexity 166 (threshold 15). Drivers by points: if/else 46 (137 pts), loops 6 (24 pts), boolean chains 5 (nesting depth added 109). 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 file is where this pass's cognitive complexity CONCENTRATES: vello_common/src/tile.rs holds 2 of the 40 functions over the threshold — including the worst — and 796 of the 1632 points over it (49%), 9.6× the next-largest file (research/vello_shaders/src/cpu/flatten.rs at 83). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ShaderInfo::from_dir (cognitive 31) research/vello_shaders/src/compile/mod.rs:186— ShaderInfo::from_dir has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (11 pts), loops 2 (6 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ShaderInfo::new (cognitive 24) research/vello_shaders/src/compile/mod.rs:92— ShaderInfo::new has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 3 (9 pts), boolean chains 1, 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.
TooManyMethods: RenderContext vello_cpu/src/render.rs:126— TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Scene vello_gpu/src/scene.rs:247— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×2
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) vello_gpu/src/render/wgpu/passes/copy.rs:99— vello_gpu/src/render/wgpu/passes/copy.rs:99-125 | vello_gpu/src/render/wgpu/passes/filter.rs:277-308 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) vello_gpu/src/render/webgl/resources.rs:176— vello_gpu/src/render/webgl/resources.rs:176-202 | vello_gpu/src/render/wgpu/resources.rs:736-762 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) vello_cpu/src/filter/gaussian_blur.rs:419— vello_cpu/src/filter/gaussian_blur.rs:419-443 | vello_cpu/src/filter/gaussian_blur.rs:451-475 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) vello_tests/vello_example_scenes/src/random_text.rs:294— vello_tests/vello_example_scenes/src/random_text.rs:294-318 | vello_tests/vello_example_scenes/src/text.rs:126-154 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) vello_bench/src/fine/pack.rs:22— vello_bench/src/fine/pack.rs:22-32 | vello_bench/src/fine/pack.rs:35-45 — 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) research/vello_shaders/src/cpu.rs:116— research/vello_shaders/src/cpu.rs:116-126 | research/vello_shaders/src/cpu.rs:138-148 — 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 copies of one member (3 members, 9+ corresponding lines) · ×2
Edited copies of one member (3 members, 9+ corresponding lines) research/vello_shaders/src/cpu/clip_leaf.rs:75— research/vello_shaders/src/cpu/clip_leaf.rs:75-88 | research/vello_shaders/src/cpu/path_count.rs:156-164 | research/vello_shaders/src/cpu/tile_alloc.rs:57-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) vello_cpu/src/dispatch/single_threaded.rs:300— vello_cpu/src/dispatch/single_threaded.rs:300-315 | vello_cpu/src/dispatch/single_threaded.rs:326-341 | vello_cpu/src/dispatch/single_threaded.rs:349-357 — 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 copy of a member (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) vello_common/src/strip_generator.rs:128— vello_common/src/strip_generator.rs:128-142 | vello_common/src/strip_generator.rs:153-168 — 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) vello_gpu/src/render/wgpu/passes/mod.rs:89— vello_gpu/src/render/wgpu/passes/mod.rs:89-103 | vello_gpu/src/render/wgpu/passes/mod.rs:105-119 — 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 copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) vello_cpu/src/dispatch/multi_threaded.rs:475— vello_cpu/src/dispatch/multi_threaded.rs:475-488 | vello_cpu/src/dispatch/multi_threaded.rs:499-512 — 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) vello_bench/src/fine/image.rs:150— vello_bench/src/fine/image.rs:150-163 | vello_bench/src/fine/image.rs:165-178 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (1 corresponding lines) · ×2
Edited copy of a member (1 corresponding lines) vello_cpu/src/fine/common/image.rs:85— vello_cpu/src/fine/common/image.rs:85-85 | vello_cpu/src/fine/lowp/image.rs:111-111 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (1 corresponding lines) vello_cpu/src/fine/common/image.rs:145— vello_cpu/src/fine/common/image.rs:145-145 | vello_cpu/src/fine/lowp/image.rs:241-241 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) vello_cpu/src/dispatch/multi_threaded.rs:171— vello_cpu/src/dispatch/multi_threaded.rs:171-174 | vello_cpu/src/dispatch/single_threaded.rs:76-80 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) vello_cpu/src/dispatch/multi_threaded.rs:185— vello_cpu/src/dispatch/multi_threaded.rs:185-188 | vello_cpu/src/dispatch/single_threaded.rs:95-99 — 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 (23–24 lines × 2) glifo/src/glyph.rs:2281— glifo/src/glyph.rs:2281-2304 | research/vello_encoding/src/glyph_cache.rs:398-420 — before extracting anything, compare `glifo/src/glyph.rs` and `research/vello_encoding/src/glyph_cache.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `glifo/src/glyph.rs:2281` 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 (23–24 lines × 2) vello_cpu/src/dispatch/multi_threaded.rs:636— vello_cpu/src/dispatch/multi_threaded.rs:636-658 | vello_cpu/src/dispatch/single_threaded.rs:439-462 — 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 (16–17 lines × 2) vello_gpu/src/render/webgl/passes/blend.rs:88— vello_gpu/src/render/webgl/passes/blend.rs:88-103 | vello_gpu/src/render/wgpu/passes/blend.rs:168-184 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16–17 lines × 2) research/vello_research_tests/src/compare.rs:141— research/vello_research_tests/src/compare.rs:141-157 | research/vello_research_tests/src/snapshot.rs:321-336 — 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 `research/vello_research_tests/src/compare.rs:141` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) research/vello_shaders/src/cpu/path_tiling.rs:80— research/vello_shaders/src/cpu/path_tiling.rs:80-96 | research/vello_shaders/src/cpu/path_tiling.rs:99-115 — both copies are in the same file, so extract the 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 `research/vello_shaders/src/cpu/path_tiling.rs:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) vello_tests/vello_example_scenes/src/gradient.rs:43— vello_tests/vello_example_scenes/src/gradient.rs:43-59 | vello_tests/vello_example_scenes/src/gradient.rs:162-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) vello_cpu/src/fine/common/gradient/mod.rs:127— vello_cpu/src/fine/common/gradient/mod.rs:127-136 | vello_cpu/src/fine/common/gradient/mod.rs:181-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vello_cpu/src/fine/common/gradient/mod.rs:127` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `buf` to `&mut [u8]` in one and `&mut [f32]` 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 (10 lines × 2) vello_bench/src/data.rs:254— vello_bench/src/data.rs:254-263 | vello_toy/src/svg.rs:249-259 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 3) research/vello_encoding/src/path.rs:526— research/vello_encoding/src/path.rs:526-535 | research/vello_encoding/src/path.rs:556-563 | research/vello_encoding/src/path.rs:584-591 — 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 `research/vello_encoding/src/path.rs:526` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) vello_tests/vello_example_scenes/src/image.rs:116— vello_tests/vello_example_scenes/src/image.rs:116-123 | vello_tests/vello_example_scenes/src/image.rs:129-136 | vello_tests/vello_example_scenes/src/image.rs:142-149 — 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 `vello_tests/vello_example_scenes/src/image.rs:116` 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 × 3) vello_tests/vello_example_scenes/src/filter.rs:82— vello_tests/vello_example_scenes/src/filter.rs:82-91 | vello_tests/vello_example_scenes/src/filter.rs:128-137 | vello_tests/vello_example_scenes/src/filter.rs:436-445 — 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 `vello_tests/vello_example_scenes/src/filter.rs:82` 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, `vello_tests/vello_example_scenes/src/filter.rs:92` calls `pop_layer` and `vello_tests/vello_example_scenes/src/filter.rs:141` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) vello_tests/vello_example_scenes/src/image.rs:98— vello_tests/vello_example_scenes/src/image.rs:98-107 | vello_tests/vello_example_scenes/src/image.rs:112-121 | vello_tests/vello_example_scenes/src/image.rs:169-178 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vello_tests/vello_example_scenes/src/image.rs:108` calls `pop_layer` and `vello_tests/vello_example_scenes/src/image.rs:123` 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.
Off the main sequence: vello_gpu_shaders — vello_gpu_shaders: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: vello_encoding — vello_encoding: abstractness 0.02, instability 0.00, distance 0.98 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
generate.build_font (cyclomatic 38) assets/sbix/generate.py:102— generate.build_font has cyclomatic complexity 38 (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.
Resolver::resolve (cyclomatic 35) research/vello_encoding/src/resolve.rs:183— Resolver::resolve 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.
WgpuEngine::run_recording (cyclomatic 34) research/vello_research/src/wgpu_engine.rs:380— WgpuEngine::run_recording 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.
Fine::indexed_fill (cyclomatic 21) vello_cpu/src/fine/mod.rs:929— Fine::indexed_fill 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.
GlyphRunRenderer::draw_glyphs (cyclomatic 20) glifo/src/glyph.rs:433— GlyphRunRenderer::draw_glyphs has cyclomatic complexity 20 (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.
DrawGlyphs::try_draw_colr (cyclomatic 20) research/vello_research/src/scene.rs:665— DrawGlyphs::try_draw_colr 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.
Render::render_encoding_coarse (cyclomatic 19) research/vello_research/src/render.rs:135— Render::render_encoding_coarse 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.
RendererContext::strip_pass_inner (cyclomatic 18) vello_gpu/src/render/wgpu/passes/strip.rs:436— RendererContext::strip_pass_inner has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FixmeComment vello_tests/tests/clip.rs:162— // FIXME: make const once MSRV >= 1.90 — 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.
WgpuEngine::run_recording (cognitive 68) research/vello_research/src/wgpu_engine.rs:380— WgpuEngine::run_recording has cognitive complexity 68 (threshold 15). Drivers by points: if/else 16 (47 pts), match/switch 5 (15 pts), boolean chains 3, loops 3 (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generate.build_font (cognitive 68) assets/sbix/generate.py:102— generate.build_font has cognitive complexity 68 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 11 (20 pts), loops 8 (19 pts), boolean chains 9 (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.
DrawGlyphs::try_draw_colr (cognitive 50) research/vello_research/src/scene.rs:665— DrawGlyphs::try_draw_colr has cognitive complexity 50 (threshold 15). Drivers by points: if/else 11 (34 pts), match/switch 5 (13 pts), boolean chains 2, loops 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Fine::indexed_fill (cognitive 32) vello_cpu/src/fine/mod.rs:929— Fine::indexed_fill has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (23 pts), match/switch 4 (7 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.
GlyphRunRenderer::draw_glyphs (cognitive 31) glifo/src/glyph.rs:433— GlyphRunRenderer::draw_glyphs has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 6 (11 pts), boolean chains 5, 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.
RendererContext::strip_pass_inner (cognitive 26) vello_gpu/src/render/wgpu/passes/strip.rs:436— RendererContext::strip_pass_inner has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (19 pts), match/switch 3, boolean chains 2, loops 2 (nesting depth added 4). 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.
TransientBindMap::create_bind_group (cognitive 23) research/vello_research/src/wgpu_engine.rs:1081— TransientBindMap::create_bind_group has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (13 pts), match/switch 5 (9 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.
vello_cpu::filter::shift::offset_pixels (cognitive 23) vello_cpu/src/filter/shift.rs:18— vello_cpu::filter::shift::offset_pixels has cognitive complexity 23 (threshold 15). Drivers by points: loops 8 (20 pts), boolean chains 1, if/else 1, match/switch 1 (nesting depth added 12). 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.
Render::render_encoding_coarse (cognitive 22) research/vello_research/src/render.rs:135— Render::render_encoding_coarse has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 3, loops 1, match/switch 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.
Parser::rec_parse (cognitive 22) vello_common/src/pico_svg.rs:171— Parser::rec_parse has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (3 pts), match/switch 1 (2 pts), boolean chains 1 (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.
F32Kernel::blend (cognitive 20) vello_cpu/src/fine/highp/mod.rs:189— F32Kernel::blend has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BumpEstimator::count_path (cognitive 18) research/vello_encoding/src/estimate.rs:54— BumpEstimator::count_path has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 1 (2 pts), 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.
MultiThreadedDispatcher::record_finished_commands (cognitive 18) vello_cpu/src/dispatch/multi_threaded.rs:302— MultiThreadedDispatcher::record_finished_commands has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 3 (11 pts), loops 2 (4 pts), if/else 2 (3 pts) (nesting depth added 11). 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.
Rounds::execute (cognitive 16) vello_gpu/src/schedule/execute.rs:111— Rounds::execute has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (5 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.
TooManyFields: WebGlResources vello_gpu/src/render/webgl/resources.rs:36— TooManyFields — 33 stored fields beside 22 methods. The bar is 30 stored fields; this is 3 over it, 1.10× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFunctions: vello_bench::fine::blend vello_bench/src/fine/blend.rs:13— TooManyFunctions — 31 free functions. The bar is 30 free functions; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling clique: gradient_cache.rs, mod.rs, mod.rs vello_gpu/src/gradient_cache.rs— 3 files — `vello_gpu/src/gradient_cache.rs`, `vello_gpu/src/render/webgl/mod.rs`, `vello_gpu/src/render/wgpu/mod.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) vello_cpu/src/filter/gaussian_blur.rs:210— vello_cpu/src/filter/gaussian_blur.rs:210-244 | vello_cpu/src/filter/gaussian_blur.rs:259-293 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) glifo/src/glyph.rs:1987— glifo/src/glyph.rs:1987-2038 | research/vello_encoding/src/glyph_cache.rs:94-138 — 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 (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) vello_gpu/src/render/wgpu/passes/blend.rs:30— vello_gpu/src/render/wgpu/passes/blend.rs:30-104 | vello_gpu/src/render/wgpu/passes/copy.rs:24-71 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) glifo/src/glyph.rs:2274— glifo/src/glyph.rs:2274-2304 | research/vello_encoding/src/glyph_cache.rs:391-420 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 26+ corresponding lines) · ×1
Edited copies of one member (3 members, 26+ corresponding lines) research/vello_encoding/src/path.rs:525— research/vello_encoding/src/path.rs:525-552 | research/vello_encoding/src/path.rs:555-580 | research/vello_encoding/src/path.rs:583-608 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) vello_gpu/src/scene.rs:491— vello_gpu/src/scene.rs:491-530 | vello_gpu/src/scene.rs:588-633 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) vello_cpu/src/dispatch/multi_threaded.rs:632— vello_cpu/src/dispatch/multi_threaded.rs:632-684 | vello_cpu/src/dispatch/single_threaded.rs:437-504 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) vello_gpu/src/render/webgl/mod.rs:267— vello_gpu/src/render/webgl/mod.rs:267-298 | vello_gpu/src/render/wgpu/mod.rs:341-383 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) vello_common/src/multi_atlas.rs:277— vello_common/src/multi_atlas.rs:277-306 | vello_common/src/multi_atlas.rs:313-338 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) research/vello_encoding/src/estimate.rs:190— research/vello_encoding/src/estimate.rs:190-208 | research/vello_encoding/src/estimate.rs:210-232 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) research/vello_shaders/src/cpu/binning.rs:110— research/vello_shaders/src/cpu/binning.rs:110-130 | research/vello_shaders/src/cpu/coarse.rs:392-413 | research/vello_shaders/src/cpu/draw_leaf.rs:211-229 | research/vello_shaders/src/cpu/flatten.rs:847-863 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) vello_cpu/src/render.rs:265— vello_cpu/src/render.rs:265-289 | vello_cpu/src/render.rs:292-314 | vello_cpu/src/render.rs:359-382 — 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 (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) vello_cpu/src/filter/mod.rs:66— vello_cpu/src/filter/mod.rs:66-83 | vello_cpu/src/filter/mod.rs:104-121 — 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 (6 members, 1+ corresponding lines) · ×1
Edited copies of one member (6 members, 1+ corresponding lines) vello_cpu/src/fine/common/image.rs:85— vello_cpu/src/fine/common/image.rs:85-85 | vello_cpu/src/fine/common/image.rs:145-145 | vello_cpu/src/fine/common/image.rs:337-337 | vello_cpu/src/fine/common/image.rs:339-339 | vello_cpu/src/fine/lowp/image.rs:111-111 | vello_cpu/src/fine/lowp/image.rs:241-241 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 1 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 (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) vello_gpu/src/render/wgpu/mod.rs:203— vello_gpu/src/render/wgpu/mod.rs:203-220 | vello_gpu/src/render/wgpu/resources.rs:450-467 | vello_gpu/src/render/wgpu/resources.rs:682-698 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) vello_gpu/src/render/webgl/passes/blend.rs:58— vello_gpu/src/render/webgl/passes/blend.rs:58-72 | vello_gpu/src/render/webgl/passes/copy.rs:50-64 | vello_gpu/src/render/webgl/passes/filter.rs:93-107 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) vello_gpu/src/render/wgpu/passes/filter.rs:165— vello_gpu/src/render/wgpu/passes/filter.rs:165-182 | vello_gpu/src/render/wgpu/resources.rs:796-813 | vello_gpu/src/render/wgpu/resources.rs:821-833 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) research/vello_shaders/src/cpu/bbox_clear.rs:17— research/vello_shaders/src/cpu/bbox_clear.rs:17-21 | research/vello_shaders/src/cpu/path_count_setup.rs:17-21 | research/vello_shaders/src/cpu/path_tiling_setup.rs:17-22 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (36–38 lines × 2) vello_common/src/tile.rs:558— vello_common/src/tile.rs:558-595 | vello_common/src/tile.rs:975-1010 — both copies are in the same file, so extract the 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 `vello_common/src/tile.rs:558` 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 (22–24 lines × 2) glifo/src/glyph.rs:594— glifo/src/glyph.rs:594-617 | glifo/src/glyph.rs:693-714 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `glifo/src/glyph.rs:594` 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 (22 lines × 2) vello_cpu/src/dispatch/multi_threaded.rs:662— vello_cpu/src/dispatch/multi_threaded.rs:662-683 | vello_cpu/src/dispatch/single_threaded.rs:466-489 — 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 (20–21 lines × 2) vello_cpu/src/dispatch/multi_threaded/worker.rs:110— vello_cpu/src/dispatch/multi_threaded/worker.rs:110-130 | vello_cpu/src/dispatch/multi_threaded/worker.rs:147-166 — both copies are in the same file, so extract the 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 `vello_cpu/src/dispatch/multi_threaded/worker.rs:110` 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–19 lines × 2) vello_cpu/src/fine/common/image.rs:258— vello_cpu/src/fine/common/image.rs:258-270 | vello_cpu/src/fine/common/image.rs:292-310 — both copies are in the same file, so extract the 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 `vello_cpu/src/fine/common/image.rs:292` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 2) vello_gpu/src/render/webgl/mod.rs:185— vello_gpu/src/render/webgl/mod.rs:185-202 | vello_gpu/src/render/wgpu/mod.rs:267-283 — `vello_gpu/src/render/webgl/mod.rs` and `vello_gpu/src/render/wgpu/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `vello_gpu/src/render/webgl/mod.rs: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–16 lines × 2) glifo/src/glyph.rs:2233— glifo/src/glyph.rs:2233-2248 | research/vello_encoding/src/glyph_cache.rs:363-376 — before extracting anything, compare `glifo/src/glyph.rs` and `research/vello_encoding/src/glyph_cache.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `glifo/src/glyph.rs:2233` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–15 lines × 2) glifo/src/renderer.rs:271— glifo/src/renderer.rs:271-284 | glifo/src/renderer.rs:374-388 — both copies are in the same file, so extract the 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 × 3) vello_gpu/src/render/wgpu/passes/clear.rs:182— vello_gpu/src/render/wgpu/passes/clear.rs:182-195 | vello_gpu/src/render/wgpu/passes/copy.rs:109-121 | vello_gpu/src/render/wgpu/passes/filter.rs:290-302 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `vello_gpu/src/render/wgpu/passes/clear.rs:182` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vello_gpu/src/render/wgpu/passes/filter.rs:303` calls `set_bind_group`, `texture` and `vello_gpu/src/render/wgpu/passes/copy.rs:122` 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 (13–14 lines × 2) vello_cpu/src/dispatch/multi_threaded/worker.rs:104— vello_cpu/src/dispatch/multi_threaded/worker.rs:104-116 | vello_cpu/src/dispatch/multi_threaded/worker.rs:176-189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `vello_cpu/src/dispatch/multi_threaded/worker.rs:175` calls `Some` and `vello_cpu/src/dispatch/multi_threaded/worker.rs:103` 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 (24 lines × 2) vello_bench/src/data.rs:266— vello_bench/src/data.rs:266-289 | vello_toy/src/svg.rs:262-285 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12–13 lines × 2) vello_cpu/src/dispatch/single_threaded.rs:384— vello_cpu/src/dispatch/single_threaded.rs:384-396 | vello_gpu/src/scene.rs:782-793 — 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 `vello_cpu/src/dispatch/single_threaded.rs:384` 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 (4–9 lines × 3) research/vello_encoding/src/path.rs:789— research/vello_encoding/src/path.rs:789-797 | research/vello_encoding/src/path.rs:803-806 | research/vello_encoding/src/path.rs:808-816 — 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 `research/vello_encoding/src/path.rs:789` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–8 lines × 2) glifo/src/glyph.rs:441— glifo/src/glyph.rs:441-446 | research/vello_research/src/scene.rs:674-681 — 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 `research/vello_research/src/scene.rs:674` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–7 lines × 2) vello_common/src/pixmap.rs:572— vello_common/src/pixmap.rs:572-577 | vello_common/src/pixmap.rs:600-606 — both copies are in the same file, so extract the 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 `vello_common/src/pixmap.rs:572` 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–6 lines × 4) vello_cpu/src/fine/common/image.rs:455— vello_cpu/src/fine/common/image.rs:455-460 | vello_cpu/src/fine/common/image.rs:462-467 | vello_cpu/src/fine/common/image.rs:469-474 | vello_cpu/src/fine/common/image.rs:476-479 — 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 `vello_cpu/src/fine/common/image.rs:455` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 3) vello_gpu/src/render/webgl/passes/blend.rs:30— vello_gpu/src/render/webgl/passes/blend.rs:30-40 | vello_gpu/src/render/webgl/passes/copy.rs:24-34 | vello_gpu/src/render/webgl/passes/filter.rs:60-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `vello_gpu/src/render/webgl/passes/copy.rs:24` 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 first that the copies are not typed on the same thing: the declarations holding them bind `instances` to `&[GpuBlendInstance]` in one and `&[GpuCopyInstance]` 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 (21–38 lines × 2) vello_tests/vello_example_scenes/src/gradient.rs:229— vello_tests/vello_example_scenes/src/gradient.rs:229-249 | vello_tests/vello_example_scenes/src/gradient.rs:258-295 — both copies are in the same file, so extract the 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 `vello_tests/vello_example_scenes/src/gradient.rs:258` 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 (21 lines × 4) vello_tests/vello_example_scenes/src/gradient.rs:236— vello_tests/vello_example_scenes/src/gradient.rs:236-256 | vello_tests/vello_example_scenes/src/gradient.rs:259-279 | vello_tests/vello_example_scenes/src/gradient.rs:282-302 | vello_tests/vello_example_scenes/src/gradient.rs:306-326 — 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 `vello_tests/vello_example_scenes/src/gradient.rs:236` 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 (19–21 lines × 2) vello_tests/vello_example_scenes/src/filter.rs:84— vello_tests/vello_example_scenes/src/filter.rs:84-104 | vello_tests/vello_example_scenes/src/filter.rs:130-148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vello_tests/vello_example_scenes/src/filter.rs:84` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18–19 lines × 2) vello_tests/vello_example_scenes/src/blend.rs:64— vello_tests/vello_example_scenes/src/blend.rs:64-81 | vello_tests/vello_example_scenes/src/blend.rs:135-153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vello_tests/vello_example_scenes/src/blend.rs:64` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (19 lines × 2) vello_tests/vello_example_scenes/src/filter.rs:231— vello_tests/vello_example_scenes/src/filter.rs:231-249 | vello_tests/vello_example_scenes/src/filter.rs:291-309 — both copies are in the same file, so extract the 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 `vello_tests/vello_example_scenes/src/filter.rs:231` 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–19 lines × 3) vello_tests/vello_example_scenes/src/navigation.rs:134— vello_tests/vello_example_scenes/src/navigation.rs:134-152 | vello_tests/vello_example_scenes/src/navigation.rs:158-176 | vello_tests/vello_example_scenes/src/navigation.rs:181-186 — 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 `vello_tests/vello_example_scenes/src/navigation.rs:134` 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. 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 (15 lines × 4) vello_tests/vello_example_scenes/src/filter.rs:170— vello_tests/vello_example_scenes/src/filter.rs:170-184 | vello_tests/vello_example_scenes/src/filter.rs:229-243 | vello_tests/vello_example_scenes/src/filter.rs:289-303 | vello_tests/vello_example_scenes/src/filter.rs:347-361 — 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 `vello_tests/vello_example_scenes/src/filter.rs:170` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–15 lines × 2) vello_tests/src/renderer.rs:538— vello_tests/src/renderer.rs:538-552 | vello_tests/src/renderer.rs:1052-1064 — both copies are in the same file, so extract the 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 (14 lines × 5) vello_tests/vello_example_scenes/src/filter.rs:171— vello_tests/vello_example_scenes/src/filter.rs:171-184 | vello_tests/vello_example_scenes/src/filter.rs:230-243 | vello_tests/vello_example_scenes/src/filter.rs:290-303 | vello_tests/vello_example_scenes/src/filter.rs:348-361 | vello_tests/vello_example_scenes/src/filter.rs:508-521 — 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 `vello_tests/vello_example_scenes/src/filter.rs:171` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–14 lines × 2) vello_tests/vello_example_scenes/src/image.rs:55— vello_tests/vello_example_scenes/src/image.rs:55-68 | vello_tests/vello_example_scenes/src/image.rs:71-81 — both copies are in the same file, so extract the 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 `vello_tests/vello_example_scenes/src/image.rs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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, `vello_tests/vello_example_scenes/src/image.rs:54` calls `set_paint_transform`, `translate`, `set_paint` and `vello_tests/vello_example_scenes/src/image.rs:71` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) vello_tests/vello_example_scenes/src/path.rs:426— vello_tests/vello_example_scenes/src/path.rs:426-440 | vello_tests/vello_example_scenes/src/path.rs:445-459 — both copies are in the same file, so extract the 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 `vello_tests/vello_example_scenes/src/path.rs:426` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 5) vello_tests/vello_example_scenes/src/filter.rs:168— vello_tests/vello_example_scenes/src/filter.rs:168-180 | vello_tests/vello_example_scenes/src/filter.rs:227-239 | vello_tests/vello_example_scenes/src/filter.rs:287-299 | vello_tests/vello_example_scenes/src/filter.rs:345-357 | vello_tests/vello_example_scenes/src/filter.rs:396-408 — 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 `vello_tests/vello_example_scenes/src/filter.rs:168` 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 × 3) vello_tests/vello_example_scenes/src/path.rs:105— vello_tests/vello_example_scenes/src/path.rs:105-117 | vello_tests/vello_example_scenes/src/path.rs:125-137 | vello_tests/vello_example_scenes/src/path.rs:142-154 — 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 `vello_tests/vello_example_scenes/src/path.rs:105` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) vello_tests/vello_example_scenes/src/filter.rs:198— vello_tests/vello_example_scenes/src/filter.rs:198-209 | vello_tests/vello_example_scenes/src/filter.rs:258-269 | vello_tests/vello_example_scenes/src/filter.rs:316-327 — 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 `vello_tests/vello_example_scenes/src/filter.rs:198` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 6) vello_tests/vello_example_scenes/src/filter.rs:58— vello_tests/vello_example_scenes/src/filter.rs:58-66 | vello_tests/vello_example_scenes/src/filter.rs:146-154 | vello_tests/vello_example_scenes/src/filter.rs:204-213 | vello_tests/vello_example_scenes/src/filter.rs:264-273 | vello_tests/vello_example_scenes/src/filter.rs:322-331 | vello_tests/vello_example_scenes/src/filter.rs:420-428 — 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 `vello_tests/vello_example_scenes/src/filter.rs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–10 lines × 2) vello_tests/vello_example_scenes/src/path.rs:499— vello_tests/vello_example_scenes/src/path.rs:499-508 | vello_tests/vello_example_scenes/src/path.rs:532-539 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vello_tests/vello_example_scenes/src/path.rs:508` calls `close_path` and `vello_tests/vello_example_scenes/src/path.rs:539` 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 (9 lines × 5) vello_tests/vello_example_scenes/src/path.rs:103— vello_tests/vello_example_scenes/src/path.rs:103-111 | vello_tests/vello_example_scenes/src/path.rs:123-131 | vello_tests/vello_example_scenes/src/path.rs:140-148 | vello_tests/vello_example_scenes/src/path.rs:159-167 | vello_tests/vello_example_scenes/src/path.rs:176-184 — 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 `vello_tests/vello_example_scenes/src/path.rs:103` 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 × 7) vello_tests/vello_example_scenes/src/filter.rs:122— vello_tests/vello_example_scenes/src/filter.rs:122-129 | vello_tests/vello_example_scenes/src/filter.rs:162-169 | vello_tests/vello_example_scenes/src/filter.rs:221-228 | vello_tests/vello_example_scenes/src/filter.rs:281-288 | vello_tests/vello_example_scenes/src/filter.rs:339-346 | vello_tests/vello_example_scenes/src/filter.rs:390-397 | vello_tests/vello_example_scenes/src/filter.rs:430-437 — 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 `vello_tests/vello_example_scenes/src/filter.rs:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 7) vello_tests/vello_example_scenes/src/filter.rs:62— vello_tests/vello_example_scenes/src/filter.rs:62-67 | vello_tests/vello_example_scenes/src/filter.rs:106-111 | vello_tests/vello_example_scenes/src/filter.rs:150-155 | vello_tests/vello_example_scenes/src/filter.rs:209-214 | vello_tests/vello_example_scenes/src/filter.rs:269-274 | vello_tests/vello_example_scenes/src/filter.rs:327-332 | vello_tests/vello_example_scenes/src/filter.rs:424-429 — 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 `vello_tests/vello_example_scenes/src/filter.rs:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) vello_tests/vello_example_scenes/src/path.rs:500— vello_tests/vello_example_scenes/src/path.rs:500-505 | vello_tests/vello_example_scenes/src/path.rs:514-519 | vello_tests/vello_example_scenes/src/path.rs:535-540 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `vello_tests/vello_example_scenes/src/path.rs:507` calls `line_to` and `vello_tests/vello_example_scenes/src/path.rs:521` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 6) vello_tests/vello_example_scenes/src/filter.rs:68— vello_tests/vello_example_scenes/src/filter.rs:68-72 | vello_tests/vello_example_scenes/src/filter.rs:156-160 | vello_tests/vello_example_scenes/src/filter.rs:215-219 | vello_tests/vello_example_scenes/src/filter.rs:275-279 | vello_tests/vello_example_scenes/src/filter.rs:333-337 | vello_tests/vello_example_scenes/src/filter.rs:384-388 — 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 `vello_tests/vello_example_scenes/src/filter.rs:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: WebGlResources (LCOM4 7) vello_gpu/src/render/webgl/resources.rs:36— WebGlResources'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.
Orphaned file research/vello_encoding/src/estimate.rs: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 research/vello_shaders/src/cpu/euler.rs: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 research/vello_shaders/src/compile/mod.rs: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 research/vello_research/src/recording.rs: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 research/vello_encoding/src/math.rs: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 research/vello_shaders/src/compile/preprocess.rs: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 vello_cpu/src/filter/shift.rs: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 research/vello_research/src/shaders.rs: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 research/vello_shaders/src/cpu/path_tiling.rs: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 research/vello_shaders/src/cpu/path_count.rs: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 vello_tests/vello_example_scenes/src/blend.rs: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 research/vello_shaders/src/cpu/fine.rs: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 research/vello_shaders/src/cpu/util.rs: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 research/vello_shaders/src/cpu.rs: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 research/vello_shaders/src/lib.rs: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 research/vello_shaders/src/cpu/binning.rs: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 research/vello_research/src/debug.rs: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 research/vello_encoding/src/mask.rs: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 research/vello_encoding/src/glyph.rs: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 research/vello_shaders/src/cpu/clip_leaf.rs: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 vello_tests/vello_example_scenes/src/blurred_rounded_rect.rs: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 research/vello_shaders/src/cpu/tile_alloc.rs: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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 28 significant file(s) lose their only recent owner: vello_cpu/src/coarse/bucketer.rs, vello_gpu/src/draw.rs, glifo/src/renderer.rs, glifo/src/atlas/cache.rs, glifo/src/colr.rs, vello_common/src/util.rs, vello_cpu/src/text.rs, vello_cpu/src/coarse/depth.rs (+20 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 7 significant file(s) lose their only recent owner: vello_tests/vello_example_scenes/src/performance.rs, vello_gpu_shaders/src/minify.rs, vello_tests/vello_example_scenes/src/navigation.rs, vello_bench/src/allocations/report.rs, vello_bench/src/allocations/counter.rs, vello_bench/src/allocations/mod.rs, vello_bench/src/allocations/tiger.rs. Pair on, review, or document these before any departure.
Duplicated predicate vello_gpu/src/render/webgl/resources.rs:250— `(self.scratch_texture.is_some() && size_changed) || (self.scratch_texture.is_none() && scratch_required)` appears character-identically in 2 files — vello_gpu/src/render/webgl/resources.rs, vello_gpu/src/render/wgpu/resources.rs. 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 glifo/src/glyph.rs:2001— `serial - self.last_prune_serial < PRUNE_FREQUENCY && self.cached_count < CACHED_COUNT_THRESHOLD` appears character-identically in 2 files — glifo/src/glyph.rs, research/vello_encoding/src/glyph_cache.rs. 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.
No ADRs found vello_toy/Cargo.toml:20— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `vello_toy/Cargo.toml` makes this repository a deployable product (line 20).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 13 project(s) overshoot their size bounds, lowering Project Cohesion to 8.5/10. The most over is `vello_common` (14296 LoC, 146 module-visible types across 2 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) — 22 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: research/vello_encoding/src/estimate.rs, research/vello_shaders/src/cpu/euler.rs, research/vello_shaders/src/compile/mod.rs, research/vello_research/src/recording.rs, research/vello_encoding/src/math.rs, research/vello_shaders/src/compile/preprocess.rs, vello_cpu/src/filter/shift.rs, research/vello_research/src/shaders.rs (and 14 more) (24 orphaned of 205 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; 205 of the 260 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.
Logging is not universal — Only 5/10 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `research/xtask`, `vello_gpu_shaders`, `vello_tests`, `vello_toy`.
Outdated: anyhow — `anyhow` is locked at 1.0.102 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1.0.102"` requirement declared in research/vello_research_tests/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
Outdated: bytemuck — `bytemuck` is locked at 1.25.0 but 1.25.2 is the current stable release on crates.io, and it already satisfies the `"1.25.0"` requirement declared in glifo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytemuck` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.6.1 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4.6.1"` requirement declared in vello_toy/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: console_log — `console_log` is locked at 1.0.0 but 1.1.0 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in vello_tests/vello_example_scenes/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p console_log` and commit the updated REDACTED.
Outdated: crossbeam-channel — `crossbeam-channel` is locked at 0.5.15 but 0.5.17 is the current stable release on crates.io, and it already satisfies the `"0.5.15"` requirement declared in vello_cpu/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam-channel` and commit the updated REDACTED.
Outdated: env_logger — `env_logger` is locked at 0.11.10 but 0.11.11 is the current stable release on crates.io, and it already satisfies the `"0.11.10"` requirement declared in research/examples/headless/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p env_logger` and commit the updated REDACTED.
Outdated: fearless_simd — `fearless_simd` is locked at 1.1.0 but 1.2.0 is the current stable release on crates.io, and it already satisfies the `"1.1.0"` requirement declared in vello_common/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p fearless_simd` and commit the updated REDACTED.
Outdated: js-sys — `js-sys` is locked at 0.3.92 but 0.3.107 is the current stable release on crates.io, and it already satisfies the `"0.3.92"` requirement declared in vello_gpu/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p js-sys` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.29 but 0.4.35 is the current stable release on crates.io, and it already satisfies the `"0.4.29"` requirement declared in glifo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: naga — `naga` is locked at 30.0.0 but 30.0.2 is the current stable release on crates.io, and it already satisfies the `"30.0.0"` requirement declared in vello_gpu_shaders/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p naga` and commit the updated REDACTED.
Outdated: objc2 — `objc2` is locked at 0.6.4 but 0.6.5 is the current stable release on crates.io, and it already satisfies the `"0.6"` requirement declared in vello_gpu/examples/wgpu_video/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p objc2` and commit the updated REDACTED.
Outdated: oxipng — `oxipng` is locked at 10.1.1 but 10.2.1 is the current stable release on crates.io, and it already satisfies the `"10.1.1"` requirement declared in vello_tests/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p oxipng` and commit the updated REDACTED.
Outdated: proc-macro2 — `proc-macro2` is locked at 1.0.106 but 1.0.107 is the current stable release on crates.io, and it already satisfies the `"1.0.106"` requirement declared in vello_tests/vello_dev_macros/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p proc-macro2` and commit the updated REDACTED.
Outdated: quote — `quote` is locked at 1.0.45 but 1.0.47 is the current stable release on crates.io, and it already satisfies the `"1.0.45"` requirement declared in vello_tests/vello_dev_macros/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p quote` and commit the updated REDACTED.
Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1.0.228"` requirement declared in vello_tests/test_support/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.149 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0.149"` requirement declared in vello_tests/test_support/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: smallvec — `smallvec` is locked at 1.15.1 but 1.16.5 is the current stable release on crates.io, and it already satisfies the `"1.15.1"` requirement declared in glifo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smallvec` and commit the updated REDACTED.
Outdated: thread_local — `thread_local` is locked at 1.1.9 but 1.1.10 is the current stable release on crates.io, and it already satisfies the `"1.1.9"` requirement declared in vello_cpu/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p thread_local` and commit the updated REDACTED.
Outdated: wasm-bindgen — `wasm-bindgen` is locked at 0.2.115 but 0.2.130 is the current stable release on crates.io, and it already satisfies the `"0.2.115"` requirement declared in vello_gpu/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen` and commit the updated REDACTED.
Outdated: wasm-bindgen-futures — `wasm-bindgen-futures` is locked at 0.4.65 but 0.4.80 is the current stable release on crates.io, and it already satisfies the `"0.4.64"` requirement declared in vello_tests/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen-futures` and commit the updated REDACTED.
Outdated: wasm-bindgen-test — `wasm-bindgen-test` is locked at 0.3.65 but 0.3.80 is the current stable release on crates.io, and it already satisfies the `"0.3.64"` requirement declared in vello_tests/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen-test` and commit the updated REDACTED.
Outdated: web-sys — `web-sys` is locked at 0.3.92 but 0.3.107 is the current stable release on crates.io, and it already satisfies the `"0.3.92"` requirement declared in vello_gpu/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p web-sys` and commit the updated REDACTED.
Outdated: wgpu — `wgpu` is locked at 30.0.0 but 30.0.2 is the current stable release on crates.io, and it already satisfies the `"30.0.0"` requirement declared in vello_gpu/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wgpu` and commit the updated REDACTED.
Off the main sequence: vello_common — vello_common: abstractness 0.14, instability 0.00, distance 0.86 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `vello_gpu_shaders/src/webgl_bootstrap.d.ts` — 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 01a1dbcc-45cc-7e9d-928a-1affdf33af4e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 74 · Warnings: 545 · Recommendations: 32 · Info: 24 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 20:42 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.