Public report of szdytom/markview, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive 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, 17 November 2026, 06:24 UTC · Survey ID cd_62d1d1d4fbb941c1acf47a4bcc625330
szdytom/markview
Measured 17 November 2026, 06:24 UTC, at code version 2b8c2fb
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).
CAI scoreStrong
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 175,961 lines of product code in 26 projects, tests not counted · Estimated rebuild effort: about 2.0 person-years · Weakest lens: Security and Compliance, 65.3
Findings by how serious they are
141 critical646 serious33 minor
8 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
17 November 2026, 06:24 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 ▸
70of 70 dimensions measured by tools.
799of 820 findings point to an exact file and line, so you can open each one in the code. The other 21 concern the repository as a whole, such as missing documentation.
70dimensions across 7 lenses, read from 175,961 lines of product code in 26 projects.
szdytom/markview meets our standard for a preview release, though it has pipeline tools referenced by a changeable name. It scores 70.5 out of 100 and is rated Strong, and 139 of its 141 critical findings are security problems.
Security and Compliance, at 65.3, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 1.4 points. Fixing the three pipeline steps that run downloads without checking them would lift Security and Compliance itself, worth about 1.3 points. Raising Security and Compliance to 68 would lift the score to about 71.7.
124 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five pipeline steps run downloads nobody checks, and five secrets can leak from the build pipeline. Pinning each tool to an exact version, checking each download against a checksum and limiting each secret to its own step would close these risks. Fixing the weaknesses the scanner points to would fix the three security weaknesses in the code, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The loop of files that import each other needs breaking.
The product code is 175,961 lines, about €300,000 to rebuild.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 65.3 to 68, the lowest score rated Strong, the score would rise from 70.5 to about 71.7.
Code composition: what the lines of code are
Product code 79%Tests 21%
Rebuild cost: about €300,000 · Estimate
Cost to rebuild
€99,000 to €500,000, for 1,644 to 5,215 hours of work, about 2.0 person-years for 1 to 4 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.0 at a score of 71. 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
Large: 175,961 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 1.4 points · Low effort · ADR Quality
2
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED.
Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 119 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
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 1.4 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
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.
307 modules, with 1041 dependencies between them. 8 loops run through 73 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 267 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.
markview.app.search uses markview.lang, so a change to markview.lang can break markview.app.search, while a change to markview.app.search can't break markview.lang.
Position
Below the diagonal: markview.app.search uses a module listed above it, which is the healthy direction.
8→14 markview.app.search uses markview.app.folder.observepart of a loop✕
Connections
1 pair of types, where a type in markview.app.search uses a type in markview.app.folder.observe.
markview.app.search uses markview.app.folder.observe, so a change to markview.app.folder.observe can break markview.app.search, while a change to markview.app.search can't break markview.app.folder.observe.
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.
9→27 markview.app.widgets uses markview.app.font_panelpart of a loop✕
Connections
1 pair of types, where a type in markview.app.widgets uses a type in markview.app.font_panel.
markview.app.widgets uses markview.app.font_panel, so a change to markview.app.font_panel can break markview.app.widgets, while a change to markview.app.widgets can't break markview.app.font_panel.
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.
9→35 markview.app.widgets uses markview.statepart of a loop✕
Connections
1 pair of types, where a type in markview.app.widgets uses a type in markview.state.
markview.app.widgets uses markview.state, so a change to markview.state can break markview.app.widgets, while a change to markview.app.widgets can't break markview.state.
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.
9→37 markview.app.widgets uses markview.app.chrome.componentspart of a loop✕
Connections
1 pair of types, where a type in markview.app.widgets uses a type in markview.app.chrome.components.
markview.app.widgets uses markview.app.chrome.components, so a change to markview.app.chrome.components can break markview.app.widgets, while a change to markview.app.widgets can't break markview.app.chrome.components.
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.
9→39 markview.app.widgets uses markview.apppart of a loop✕
Connections
1 pair of types, where a type in markview.app.widgets uses a type in markview.app.
markview.app.widgets uses markview.app, so a change to markview.app can break markview.app.widgets, while a change to markview.app.widgets can't break markview.app.
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.
markview_document uses markview_document.ids, so a change to markview_document.ids can break markview_document, while a change to markview_document can't break markview_document.ids.
Position
Below the diagonal: markview_document uses a module listed above it, which is the healthy direction.
markview.app.folder uses markview_geometry, so a change to markview_geometry can break markview.app.folder, while a change to markview.app.folder can't break markview_geometry.
Position
Below the diagonal: markview.app.folder uses a module listed above it, which is the healthy direction.
markview.app.folder uses markview_interaction.surface, so a change to markview_interaction.surface can break markview.app.folder, while a change to markview.app.folder can't break markview_interaction.surface.
Position
Below the diagonal: markview.app.folder uses a module listed above it, which is the healthy direction.
markview.app.folder uses markview.app.search, so a change to markview.app.search can break markview.app.folder, while a change to markview.app.folder can't break markview.app.search.
Position
Below the diagonal: markview.app.folder uses a module listed above it, which is the healthy direction.
11→14 markview.app.folder uses markview.app.folder.observepart of a loop✕
Connections
2 pairs of types, where a type in markview.app.folder uses a type in markview.app.folder.observe.
markview.app.folder uses markview.app.folder.observe, so a change to markview.app.folder.observe can break markview.app.folder, while a change to markview.app.folder can't break markview.app.folder.observe.
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.
11→37 markview.app.folder uses markview.app.chrome.componentspart of a loop✕
Connections
1 pair of types, where a type in markview.app.folder uses a type in markview.app.chrome.components.
markview.app.folder uses markview.app.chrome.components, so a change to markview.app.chrome.components can break markview.app.folder, while a change to markview.app.folder can't break markview.app.chrome.components.
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.
markview.security uses markview.app.search, so a change to markview.app.search can break markview.security, while a change to markview.security can't break markview.app.search.
Position
Below the diagonal: markview.security uses a module listed above it, which is the healthy direction.
markview_document.source uses markview_document.ids, so a change to markview_document.ids can break markview_document.source, while a change to markview_document.source can't break markview_document.ids.
Position
Below the diagonal: markview_document.source uses a module listed above it, which is the healthy direction.
markview_document.source uses markview_document, so a change to markview_document can break markview_document.source, while a change to markview_document.source can't break markview_document.
Position
Below the diagonal: markview_document.source uses a module listed above it, which is the healthy direction.
markview.app.folder.observe uses markview.app.search, so a change to markview.app.search can break markview.app.folder.observe, while a change to markview.app.folder.observe can't break markview.app.search.
Position
Below the diagonal: markview.app.folder.observe uses a module listed above it, which is the healthy direction.
markview.app.folder.observe uses markview.app.folder, so a change to markview.app.folder can break markview.app.folder.observe, while a change to markview.app.folder.observe can't break markview.app.folder.
Position
Below the diagonal: markview.app.folder.observe uses a module listed above it, which is the healthy direction.
14→39 markview.app.folder.observe uses markview.apppart of a loop✕
Connections
1 pair of types, where a type in markview.app.folder.observe uses a type in markview.app.
markview.app.folder.observe uses markview.app, so a change to markview.app can break markview.app.folder.observe, while a change to markview.app.folder.observe can't break markview.app.
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.
markview_commonmark.parse uses markview_document.ids, so a change to markview_document.ids can break markview_commonmark.parse, while a change to markview_commonmark.parse can't break markview_document.ids.
Position
Below the diagonal: markview_commonmark.parse uses a module listed above it, which is the healthy direction.
markview_commonmark.parse uses markview_document, so a change to markview_document can break markview_commonmark.parse, while a change to markview_commonmark.parse can't break markview_document.
Position
Below the diagonal: markview_commonmark.parse uses a module listed above it, which is the healthy direction.
markview_commonmark.parse uses markview_document.source, so a change to markview_document.source can break markview_commonmark.parse, while a change to markview_commonmark.parse can't break markview_document.source.
Position
Below the diagonal: markview_commonmark.parse uses a module listed above it, which is the healthy direction.
markview_layout.text uses markview_document.ids, so a change to markview_document.ids can break markview_layout.text, while a change to markview_layout.text can't break markview_document.ids.
Position
Below the diagonal: markview_layout.text uses a module listed above it, which is the healthy direction.
markview_layout.text uses markview_geometry, so a change to markview_geometry can break markview_layout.text, while a change to markview_layout.text can't break markview_geometry.
Position
Below the diagonal: markview_layout.text uses a module listed above it, which is the healthy direction.
markview_layout.text uses markview_document.source, so a change to markview_document.source can break markview_layout.text, while a change to markview_layout.text can't break markview_document.source.
Position
Below the diagonal: markview_layout.text uses a module listed above it, which is the healthy direction.
16→17 markview_layout.text uses markview_layout.scenepart of a loop✕
Connections
3 pairs of types, where a type in markview_layout.text uses a type in markview_layout.scene.
markview_layout.text uses markview_layout.scene, so a change to markview_layout.scene can break markview_layout.text, while a change to markview_layout.text can't break markview_layout.scene.
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.
markview_layout.scene uses markview_document.ids, so a change to markview_document.ids can break markview_layout.scene, while a change to markview_layout.scene can't break markview_document.ids.
Position
Below the diagonal: markview_layout.scene uses a module listed above it, which is the healthy direction.
markview_layout.scene uses markview_geometry, so a change to markview_geometry can break markview_layout.scene, while a change to markview_layout.scene can't break markview_geometry.
Position
Below the diagonal: markview_layout.scene uses a module listed above it, which is the healthy direction.
markview_layout.scene uses markview_layout.image, so a change to markview_layout.image can break markview_layout.scene, while a change to markview_layout.scene can't break markview_layout.image.
Position
Below the diagonal: markview_layout.scene uses a module listed above it, which is the healthy direction.
markview_layout.scene uses markview_layout.style.types, so a change to markview_layout.style.types can break markview_layout.scene, while a change to markview_layout.scene can't break markview_layout.style.types.
Position
Below the diagonal: markview_layout.scene uses a module listed above it, which is the healthy direction.
markview_layout.scene uses markview_document, so a change to markview_document can break markview_layout.scene, while a change to markview_layout.scene can't break markview_document.
Position
Below the diagonal: markview_layout.scene uses a module listed above it, which is the healthy direction.
markview_layout.scene uses markview_document.source, so a change to markview_document.source can break markview_layout.scene, while a change to markview_layout.scene can't break markview_document.source.
Position
Below the diagonal: markview_layout.scene uses a module listed above it, which is the healthy direction.
markview_layout.scene uses markview_layout.text, so a change to markview_layout.text can break markview_layout.scene, while a change to markview_layout.scene can't break markview_layout.text.
Position
Below the diagonal: markview_layout.scene uses a module listed above it, which is the healthy direction.
markview_layout.style uses markview_layout.style.types, so a change to markview_layout.style.types can break markview_layout.style, while a change to markview_layout.style can't break markview_layout.style.types.
Position
Below the diagonal: markview_layout.style uses a module listed above it, which is the healthy direction.
markview_layout.style uses markview_document, so a change to markview_document can break markview_layout.style, while a change to markview_layout.style can't break markview_document.
Position
Below the diagonal: markview_layout.style uses a module listed above it, which is the healthy direction.
markview_layout.style uses markview_layout.scene, so a change to markview_layout.scene can break markview_layout.style, while a change to markview_layout.style can't break markview_layout.scene.
Position
Below the diagonal: markview_layout.style uses a module listed above it, which is the healthy direction.
markview.app.settings_load uses markview.lang, so a change to markview.lang can break markview.app.settings_load, while a change to markview.app.settings_load can't break markview.lang.
Position
Below the diagonal: markview.app.settings_load uses a module listed above it, which is the healthy direction.
markview.app.settings_load uses markview_layout.fonts, so a change to markview_layout.fonts can break markview.app.settings_load, while a change to markview.app.settings_load can't break markview_layout.fonts.
Position
Below the diagonal: markview.app.settings_load uses a module listed above it, which is the healthy direction.
markview.app.settings_load uses markview.app.search, so a change to markview.app.search can break markview.app.settings_load, while a change to markview.app.settings_load can't break markview.app.search.
Position
Below the diagonal: markview.app.settings_load uses a module listed above it, which is the healthy direction.
markview.app.settings_load uses markview.app.folder, so a change to markview.app.folder can break markview.app.settings_load, while a change to markview.app.settings_load can't break markview.app.folder.
Position
Below the diagonal: markview.app.settings_load uses a module listed above it, which is the healthy direction.
markview.app.settings_load uses markview_layout.style, so a change to markview_layout.style can break markview.app.settings_load, while a change to markview.app.settings_load can't break markview_layout.style.
Position
Below the diagonal: markview.app.settings_load uses a module listed above it, which is the healthy direction.
19→39 markview.app.settings_load uses markview.apppart of a loop✕
Connections
1 pair of types, where a type in markview.app.settings_load uses a type in markview.app.
markview.app.settings_load uses markview.app, so a change to markview.app can break markview.app.settings_load, while a change to markview.app.settings_load can't break markview.app.
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.
markview_layout.shaping uses markview_layout.fonts, so a change to markview_layout.fonts can break markview_layout.shaping, while a change to markview_layout.shaping can't break markview_layout.fonts.
Position
Below the diagonal: markview_layout.shaping uses a module listed above it, which is the healthy direction.
markview_layout.shaping uses markview_layout.style.types, so a change to markview_layout.style.types can break markview_layout.shaping, while a change to markview_layout.shaping can't break markview_layout.style.types.
Position
Below the diagonal: markview_layout.shaping uses a module listed above it, which is the healthy direction.
markview_layout.shaping uses markview_document, so a change to markview_document can break markview_layout.shaping, while a change to markview_layout.shaping can't break markview_document.
Position
Below the diagonal: markview_layout.shaping uses a module listed above it, which is the healthy direction.
markview_layout.shaping uses markview_layout.scene, so a change to markview_layout.scene can break markview_layout.shaping, while a change to markview_layout.shaping can't break markview_layout.scene.
Position
Below the diagonal: markview_layout.shaping uses a module listed above it, which is the healthy direction.
markview_layout.shaping uses markview_layout.style, so a change to markview_layout.style can break markview_layout.shaping, while a change to markview_layout.shaping can't break markview_layout.style.
Position
Below the diagonal: markview_layout.shaping uses a module listed above it, which is the healthy direction.
markview.app.chrome.empty uses markview.lang, so a change to markview.lang can break markview.app.chrome.empty, while a change to markview.app.chrome.empty can't break markview.lang.
Position
Below the diagonal: markview.app.chrome.empty uses a module listed above it, which is the healthy direction.
markview.app.chrome.empty uses markview_geometry, so a change to markview_geometry can break markview.app.chrome.empty, while a change to markview.app.chrome.empty can't break markview_geometry.
Position
Below the diagonal: markview.app.chrome.empty uses a module listed above it, which is the healthy direction.
markview.app.chrome.empty uses markview.app.widgets, so a change to markview.app.widgets can break markview.app.chrome.empty, while a change to markview.app.chrome.empty can't break markview.app.widgets.
Position
Below the diagonal: markview.app.chrome.empty uses a module listed above it, which is the healthy direction.
markview.app.chrome.empty uses markview.app.folder, so a change to markview.app.folder can break markview.app.chrome.empty, while a change to markview.app.chrome.empty can't break markview.app.folder.
Position
Below the diagonal: markview.app.chrome.empty uses a module listed above it, which is the healthy direction.
markview.app.chrome.empty uses markview_layout.scene, so a change to markview_layout.scene can break markview.app.chrome.empty, while a change to markview.app.chrome.empty can't break markview_layout.scene.
Position
Below the diagonal: markview.app.chrome.empty uses a module listed above it, which is the healthy direction.
markview.app.chrome.empty uses markview_layout.shaping, so a change to markview_layout.shaping can break markview.app.chrome.empty, while a change to markview.app.chrome.empty can't break markview_layout.shaping.
Position
Below the diagonal: markview.app.chrome.empty uses a module listed above it, which is the healthy direction.
21→39 markview.app.chrome.empty uses markview.apppart of a loop✕
Connections
1 pair of types, where a type in markview.app.chrome.empty uses a type in markview.app.
markview.app.chrome.empty uses markview.app, so a change to markview.app can break markview.app.chrome.empty, while a change to markview.app.chrome.empty can't break markview.app.
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.
markview_layout.layout uses markview_document.ids, so a change to markview_document.ids can break markview_layout.layout, while a change to markview_layout.layout can't break markview_document.ids.
Position
Below the diagonal: markview_layout.layout uses a module listed above it, which is the healthy direction.
markview_layout.layout uses markview_geometry, so a change to markview_geometry can break markview_layout.layout, while a change to markview_layout.layout can't break markview_geometry.
Position
Below the diagonal: markview_layout.layout uses a module listed above it, which is the healthy direction.
markview_layout.layout uses markview_layout.fonts, so a change to markview_layout.fonts can break markview_layout.layout, while a change to markview_layout.layout can't break markview_layout.fonts.
Position
Below the diagonal: markview_layout.layout uses a module listed above it, which is the healthy direction.
markview_layout.layout uses markview_layout.image, so a change to markview_layout.image can break markview_layout.layout, while a change to markview_layout.layout can't break markview_layout.image.
Position
Below the diagonal: markview_layout.layout uses a module listed above it, which is the healthy direction.
markview_layout.layout uses markview_document, so a change to markview_document can break markview_layout.layout, while a change to markview_layout.layout can't break markview_document.
Position
Below the diagonal: markview_layout.layout uses a module listed above it, which is the healthy direction.
markview_layout.layout uses markview_layout.text, so a change to markview_layout.text can break markview_layout.layout, while a change to markview_layout.layout can't break markview_layout.text.
Position
Below the diagonal: markview_layout.layout uses a module listed above it, which is the healthy direction.
markview_layout.layout uses markview_layout.scene, so a change to markview_layout.scene can break markview_layout.layout, while a change to markview_layout.layout can't break markview_layout.scene.
Position
Below the diagonal: markview_layout.layout uses a module listed above it, which is the healthy direction.
markview_layout.layout uses markview_layout.style, so a change to markview_layout.style can break markview_layout.layout, while a change to markview_layout.layout can't break markview_layout.style.
Position
Below the diagonal: markview_layout.layout uses a module listed above it, which is the healthy direction.
markview_layout.layout uses markview_layout.shaping, so a change to markview_layout.shaping can break markview_layout.layout, while a change to markview_layout.layout can't break markview_layout.shaping.
Position
Below the diagonal: markview_layout.layout uses a module listed above it, which is the healthy direction.
markview_pdf.paint uses markview_geometry, so a change to markview_geometry can break markview_pdf.paint, while a change to markview_pdf.paint can't break markview_geometry.
Position
Below the diagonal: markview_pdf.paint uses a module listed above it, which is the healthy direction.
markview_pdf.paint uses markview_layout.style.types, so a change to markview_layout.style.types can break markview_pdf.paint, while a change to markview_pdf.paint can't break markview_layout.style.types.
Position
Below the diagonal: markview_pdf.paint uses a module listed above it, which is the healthy direction.
markview_pdf.paint uses markview_layout.scene, so a change to markview_layout.scene can break markview_pdf.paint, while a change to markview_pdf.paint can't break markview_layout.scene.
Position
Below the diagonal: markview_pdf.paint uses a module listed above it, which is the healthy direction.
markview_pdf.paint uses markview_layout.style, so a change to markview_layout.style can break markview_pdf.paint, while a change to markview_pdf.paint can't break markview_layout.style.
Position
Below the diagonal: markview_pdf.paint uses a module listed above it, which is the healthy direction.
markview_pdf.paint uses markview_layout.shaping, so a change to markview_layout.shaping can break markview_pdf.paint, while a change to markview_pdf.paint can't break markview_layout.shaping.
Position
Below the diagonal: markview_pdf.paint uses a module listed above it, which is the healthy direction.
markview_render uses markview_geometry, so a change to markview_geometry can break markview_render, while a change to markview_render can't break markview_geometry.
Position
Below the diagonal: markview_render uses a module listed above it, which is the healthy direction.
markview_render uses markview_layout.fonts, so a change to markview_layout.fonts can break markview_render, while a change to markview_render can't break markview_layout.fonts.
Position
Below the diagonal: markview_render uses a module listed above it, which is the healthy direction.
markview_render uses markview_layout.scene, so a change to markview_layout.scene can break markview_render, while a change to markview_render can't break markview_layout.scene.
Position
Below the diagonal: markview_render uses a module listed above it, which is the healthy direction.
markview_render uses markview_layout.style, so a change to markview_layout.style can break markview_render, while a change to markview_render can't break markview_layout.style.
Position
Below the diagonal: markview_render uses a module listed above it, which is the healthy direction.
markview_render uses markview_layout.shaping, so a change to markview_layout.shaping can break markview_render, while a change to markview_render can't break markview_layout.shaping.
Position
Below the diagonal: markview_render uses a module listed above it, which is the healthy direction.
markview.settings uses markview.lang, so a change to markview.lang can break markview.settings, while a change to markview.settings can't break markview.lang.
Position
Below the diagonal: markview.settings uses a module listed above it, which is the healthy direction.
markview.settings uses markview_layout.fonts, so a change to markview_layout.fonts can break markview.settings, while a change to markview.settings can't break markview_layout.fonts.
Position
Below the diagonal: markview.settings uses a module listed above it, which is the healthy direction.
markview.settings uses markview_layout.style.types, so a change to markview_layout.style.types can break markview.settings, while a change to markview.settings can't break markview_layout.style.types.
Position
Below the diagonal: markview.settings uses a module listed above it, which is the healthy direction.
markview.settings uses markview.app.search, so a change to markview.app.search can break markview.settings, while a change to markview.settings can't break markview.app.search.
Position
Below the diagonal: markview.settings uses a module listed above it, which is the healthy direction.
markview.settings uses markview.app.folder.observe, so a change to markview.app.folder.observe can break markview.settings, while a change to markview.settings can't break markview.app.folder.observe.
Position
Below the diagonal: markview.settings uses a module listed above it, which is the healthy direction.
markview.settings uses markview_layout.style, so a change to markview_layout.style can break markview.settings, while a change to markview.settings can't break markview_layout.style.
Position
Below the diagonal: markview.settings uses a module listed above it, which is the healthy direction.
markview.settings uses markview_layout.layout, so a change to markview_layout.layout can break markview.settings, while a change to markview.settings can't break markview_layout.layout.
Position
Below the diagonal: markview.settings uses a module listed above it, which is the healthy direction.
markview.settings uses markview_render, so a change to markview_render can break markview.settings, while a change to markview.settings can't break markview_render.
Position
Below the diagonal: markview.settings uses a module listed above it, which is the healthy direction.
25→36 markview.settings uses markview.app.dropdownpart of a loop✕
Connections
1 pair of types, where a type in markview.settings uses a type in markview.app.dropdown.
markview.settings uses markview.app.dropdown, so a change to markview.app.dropdown can break markview.settings, while a change to markview.settings can't break markview.app.dropdown.
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.
markview_web.api uses markview_layout.fonts, so a change to markview_layout.fonts can break markview_web.api, while a change to markview_web.api can't break markview_layout.fonts.
Position
Below the diagonal: markview_web.api uses a module listed above it, which is the healthy direction.
markview_web.api uses markview_document, so a change to markview_document can break markview_web.api, while a change to markview_web.api can't break markview_document.
Position
Below the diagonal: markview_web.api uses a module listed above it, which is the healthy direction.
markview_web.api uses markview_commonmark.parse, so a change to markview_commonmark.parse can break markview_web.api, while a change to markview_web.api can't break markview_commonmark.parse.
Position
Below the diagonal: markview_web.api uses a module listed above it, which is the healthy direction.
markview_web.api uses markview_layout.scene, so a change to markview_layout.scene can break markview_web.api, while a change to markview_web.api can't break markview_layout.scene.
Position
Below the diagonal: markview_web.api uses a module listed above it, which is the healthy direction.
markview_web.api uses markview_layout.style, so a change to markview_layout.style can break markview_web.api, while a change to markview_web.api can't break markview_layout.style.
Position
Below the diagonal: markview_web.api uses a module listed above it, which is the healthy direction.
markview_web.api uses markview_layout.layout, so a change to markview_layout.layout can break markview_web.api, while a change to markview_web.api can't break markview_layout.layout.
Position
Below the diagonal: markview_web.api uses a module listed above it, which is the healthy direction.
markview_web.api uses markview_render, so a change to markview_render can break markview_web.api, while a change to markview_web.api can't break markview_render.
Position
Below the diagonal: markview_web.api uses a module listed above it, which is the healthy direction.
markview.app.font_panel uses markview_interaction.surface, so a change to markview_interaction.surface can break markview.app.font_panel, while a change to markview.app.font_panel can't break markview_interaction.surface.
Position
Below the diagonal: markview.app.font_panel uses a module listed above it, which is the healthy direction.
markview.app.font_panel uses markview_layout.fonts, so a change to markview_layout.fonts can break markview.app.font_panel, while a change to markview.app.font_panel can't break markview_layout.fonts.
Position
Below the diagonal: markview.app.font_panel uses a module listed above it, which is the healthy direction.
markview.app.font_panel uses markview.app.folder.observe, so a change to markview.app.folder.observe can break markview.app.font_panel, while a change to markview.app.font_panel can't break markview.app.folder.observe.
Position
Below the diagonal: markview.app.font_panel uses a module listed above it, which is the healthy direction.
markview.app.font_panel uses markview.app.chrome.empty, so a change to markview.app.chrome.empty can break markview.app.font_panel, while a change to markview.app.font_panel can't break markview.app.chrome.empty.
Position
Below the diagonal: markview.app.font_panel uses a module listed above it, which is the healthy direction.
markview.app.font_panel uses markview.settings, so a change to markview.settings can break markview.app.font_panel, while a change to markview.app.font_panel can't break markview.settings.
Position
Below the diagonal: markview.app.font_panel uses a module listed above it, which is the healthy direction.
27→36 markview.app.font_panel uses markview.app.dropdownpart of a loop✕
Connections
1 pair of types, where a type in markview.app.font_panel uses a type in markview.app.dropdown.
markview.app.font_panel uses markview.app.dropdown, so a change to markview.app.dropdown can break markview.app.font_panel, while a change to markview.app.font_panel can't break markview.app.dropdown.
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.
markview.services uses markview.app.search, so a change to markview.app.search can break markview.services, while a change to markview.services can't break markview.app.search.
Position
Below the diagonal: markview.services uses a module listed above it, which is the healthy direction.
markview.services uses markview.settings, so a change to markview.settings can break markview.services, while a change to markview.services can't break markview.settings.
Position
Below the diagonal: markview.services uses a module listed above it, which is the healthy direction.
markview.export uses markview.lang, so a change to markview.lang can break markview.export, while a change to markview.export can't break markview.lang.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview_layout.style.types, so a change to markview_layout.style.types can break markview.export, while a change to markview.export can't break markview_layout.style.types.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview.app.search, so a change to markview.app.search can break markview.export, while a change to markview.export can't break markview.app.search.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview_document, so a change to markview_document can break markview.export, while a change to markview.export can't break markview_document.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview.security, so a change to markview.security can break markview.export, while a change to markview.export can't break markview.security.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview_layout.scene, so a change to markview_layout.scene can break markview.export, while a change to markview.export can't break markview_layout.scene.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview_layout.style, so a change to markview_layout.style can break markview.export, while a change to markview.export can't break markview_layout.style.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview_layout.layout, so a change to markview_layout.layout can break markview.export, while a change to markview.export can't break markview_layout.layout.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview_pdf.paint, so a change to markview_pdf.paint can break markview.export, while a change to markview.export can't break markview_pdf.paint.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview_render, so a change to markview_render can break markview.export, while a change to markview.export can't break markview_render.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview.settings, so a change to markview.settings can break markview.export, while a change to markview.export can't break markview.settings.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.export uses markview.services, so a change to markview.services can break markview.export, while a change to markview.export can't break markview.services.
Position
Below the diagonal: markview.export uses a module listed above it, which is the healthy direction.
markview.images uses markview_layout.fonts, so a change to markview_layout.fonts can break markview.images, while a change to markview.images can't break markview_layout.fonts.
Position
Below the diagonal: markview.images uses a module listed above it, which is the healthy direction.
markview.images uses markview_layout.image, so a change to markview_layout.image can break markview.images, while a change to markview.images can't break markview_layout.image.
Position
Below the diagonal: markview.images uses a module listed above it, which is the healthy direction.
markview.images uses markview.app.search, so a change to markview.app.search can break markview.images, while a change to markview.images can't break markview.app.search.
Position
Below the diagonal: markview.images uses a module listed above it, which is the healthy direction.
markview.images uses markview_document, so a change to markview_document can break markview.images, while a change to markview.images can't break markview_document.
Position
Below the diagonal: markview.images uses a module listed above it, which is the healthy direction.
markview.images uses markview.app.folder, so a change to markview.app.folder can break markview.images, while a change to markview.images can't break markview.app.folder.
Position
Below the diagonal: markview.images uses a module listed above it, which is the healthy direction.
markview.images uses markview.security, so a change to markview.security can break markview.images, while a change to markview.images can't break markview.security.
Position
Below the diagonal: markview.images uses a module listed above it, which is the healthy direction.
markview.images uses markview_layout.style, so a change to markview_layout.style can break markview.images, while a change to markview.images can't break markview_layout.style.
Position
Below the diagonal: markview.images uses a module listed above it, which is the healthy direction.
markview.images uses markview.app.settings_load, so a change to markview.app.settings_load can break markview.images, while a change to markview.images can't break markview.app.settings_load.
Position
Below the diagonal: markview.images uses a module listed above it, which is the healthy direction.
markview.images uses markview.services, so a change to markview.services can break markview.images, while a change to markview.images can't break markview.services.
Position
Below the diagonal: markview.images uses a module listed above it, which is the healthy direction.
30→32 markview.images uses markview.app.preview.workpart of a loop✕
Connections
5 pairs of types, where a type in markview.images uses a type in markview.app.preview.work.
markview.images uses markview.app.preview.work, so a change to markview.app.preview.work can break markview.images, while a change to markview.images can't break markview.app.preview.work.
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.
markview.worker uses markview_layout.fonts, so a change to markview_layout.fonts can break markview.worker, while a change to markview.worker can't break markview_layout.fonts.
Position
Below the diagonal: markview.worker uses a module listed above it, which is the healthy direction.
markview.worker uses markview.app.search, so a change to markview.app.search can break markview.worker, while a change to markview.worker can't break markview.app.search.
Position
Below the diagonal: markview.worker uses a module listed above it, which is the healthy direction.
markview.worker uses markview.security, so a change to markview.security can break markview.worker, while a change to markview.worker can't break markview.security.
Position
Below the diagonal: markview.worker uses a module listed above it, which is the healthy direction.
markview.worker uses markview.app.folder.observe, so a change to markview.app.folder.observe can break markview.worker, while a change to markview.worker can't break markview.app.folder.observe.
Position
Below the diagonal: markview.worker uses a module listed above it, which is the healthy direction.
markview.worker uses markview_layout.text, so a change to markview_layout.text can break markview.worker, while a change to markview.worker can't break markview_layout.text.
Position
Below the diagonal: markview.worker uses a module listed above it, which is the healthy direction.
markview.worker uses markview_layout.scene, so a change to markview_layout.scene can break markview.worker, while a change to markview.worker can't break markview_layout.scene.
Position
Below the diagonal: markview.worker uses a module listed above it, which is the healthy direction.
markview.worker uses markview_layout.layout, so a change to markview_layout.layout can break markview.worker, while a change to markview.worker can't break markview_layout.layout.
Position
Below the diagonal: markview.worker uses a module listed above it, which is the healthy direction.
markview.worker uses markview.services, so a change to markview.services can break markview.worker, while a change to markview.worker can't break markview.services.
Position
Below the diagonal: markview.worker uses a module listed above it, which is the healthy direction.
markview.app.preview.work uses markview_document.ids, so a change to markview_document.ids can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview_document.ids.
Position
Below the diagonal: markview.app.preview.work uses a module listed above it, which is the healthy direction.
markview.app.preview.work uses markview_geometry, so a change to markview_geometry can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview_geometry.
Position
Below the diagonal: markview.app.preview.work uses a module listed above it, which is the healthy direction.
markview.app.preview.work uses markview_layout.image, so a change to markview_layout.image can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview_layout.image.
Position
Below the diagonal: markview.app.preview.work uses a module listed above it, which is the healthy direction.
markview.app.preview.work uses markview_document, so a change to markview_document can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview_document.
Position
Below the diagonal: markview.app.preview.work uses a module listed above it, which is the healthy direction.
markview.app.preview.work uses markview.security, so a change to markview.security can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview.security.
Position
Below the diagonal: markview.app.preview.work uses a module listed above it, which is the healthy direction.
markview.app.preview.work uses markview_layout.scene, so a change to markview_layout.scene can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview_layout.scene.
Position
Below the diagonal: markview.app.preview.work uses a module listed above it, which is the healthy direction.
markview.app.preview.work uses markview_layout.layout, so a change to markview_layout.layout can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview_layout.layout.
Position
Below the diagonal: markview.app.preview.work uses a module listed above it, which is the healthy direction.
markview.app.preview.work uses markview.services, so a change to markview.services can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview.services.
Position
Below the diagonal: markview.app.preview.work uses a module listed above it, which is the healthy direction.
markview.app.preview.work uses markview.images, so a change to markview.images can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview.images.
Position
Below the diagonal: markview.app.preview.work uses a module listed above it, which is the healthy direction.
32→34 markview.app.preview.work uses markview.app.previewpart of a loop✕
Connections
1 pair of types, where a type in markview.app.preview.work uses a type in markview.app.preview.
markview.app.preview.work uses markview.app.preview, so a change to markview.app.preview can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview.app.preview.
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.
32→39 markview.app.preview.work uses markview.apppart of a loop✕
Connections
1 pair of types, where a type in markview.app.preview.work uses a type in markview.app.
markview.app.preview.work uses markview.app, so a change to markview.app can break markview.app.preview.work, while a change to markview.app.preview.work can't break markview.app.
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.
markview.cli uses markview_layout.style.types, so a change to markview_layout.style.types can break markview.cli, while a change to markview.cli can't break markview_layout.style.types.
Position
Below the diagonal: markview.cli uses a module listed above it, which is the healthy direction.
markview.cli uses markview.app.search, so a change to markview.app.search can break markview.cli, while a change to markview.cli can't break markview.app.search.
Position
Below the diagonal: markview.cli uses a module listed above it, which is the healthy direction.
markview.cli uses markview.security, so a change to markview.security can break markview.cli, while a change to markview.cli can't break markview.security.
Position
Below the diagonal: markview.cli uses a module listed above it, which is the healthy direction.
markview.cli uses markview_layout.layout, so a change to markview_layout.layout can break markview.cli, while a change to markview.cli can't break markview_layout.layout.
Position
Below the diagonal: markview.cli uses a module listed above it, which is the healthy direction.
markview.cli uses markview.settings, so a change to markview.settings can break markview.cli, while a change to markview.cli can't break markview.settings.
Position
Below the diagonal: markview.cli uses a module listed above it, which is the healthy direction.
markview.cli uses markview.app.font_panel, so a change to markview.app.font_panel can break markview.cli, while a change to markview.cli can't break markview.app.font_panel.
Position
Below the diagonal: markview.cli uses a module listed above it, which is the healthy direction.
markview.app.preview uses markview_document.ids, so a change to markview_document.ids can break markview.app.preview, while a change to markview.app.preview can't break markview_document.ids.
Position
Below the diagonal: markview.app.preview uses a module listed above it, which is the healthy direction.
markview.app.preview uses markview_geometry, so a change to markview_geometry can break markview.app.preview, while a change to markview.app.preview can't break markview_geometry.
Position
Below the diagonal: markview.app.preview uses a module listed above it, which is the healthy direction.
markview.app.preview uses markview_interaction.surface, so a change to markview_interaction.surface can break markview.app.preview, while a change to markview.app.preview can't break markview_interaction.surface.
Position
Below the diagonal: markview.app.preview uses a module listed above it, which is the healthy direction.
markview.app.preview uses markview_layout.image, so a change to markview_layout.image can break markview.app.preview, while a change to markview.app.preview can't break markview_layout.image.
Position
Below the diagonal: markview.app.preview uses a module listed above it, which is the healthy direction.
markview.app.preview uses markview_document, so a change to markview_document can break markview.app.preview, while a change to markview.app.preview can't break markview_document.
Position
Below the diagonal: markview.app.preview uses a module listed above it, which is the healthy direction.
markview.app.preview uses markview_layout.scene, so a change to markview_layout.scene can break markview.app.preview, while a change to markview.app.preview can't break markview_layout.scene.
Position
Below the diagonal: markview.app.preview uses a module listed above it, which is the healthy direction.
markview.app.preview uses markview_layout.style, so a change to markview_layout.style can break markview.app.preview, while a change to markview.app.preview can't break markview_layout.style.
Position
Below the diagonal: markview.app.preview uses a module listed above it, which is the healthy direction.
markview.app.preview uses markview_layout.layout, so a change to markview_layout.layout can break markview.app.preview, while a change to markview.app.preview can't break markview_layout.layout.
Position
Below the diagonal: markview.app.preview uses a module listed above it, which is the healthy direction.
markview.app.preview uses markview_render, so a change to markview_render can break markview.app.preview, while a change to markview.app.preview can't break markview_render.
Position
Below the diagonal: markview.app.preview uses a module listed above it, which is the healthy direction.
markview.app.preview uses markview.app.preview.work, so a change to markview.app.preview.work can break markview.app.preview, while a change to markview.app.preview can't break markview.app.preview.work.
Position
Below the diagonal: markview.app.preview uses a module listed above it, which is the healthy direction.
34→35 markview.app.preview uses markview.statepart of a loop✕
Connections
1 pair of types, where a type in markview.app.preview uses a type in markview.state.
markview.app.preview uses markview.state, so a change to markview.state can break markview.app.preview, while a change to markview.app.preview can't break markview.state.
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.
markview.state uses markview_document.ids, so a change to markview_document.ids can break markview.state, while a change to markview.state can't break markview_document.ids.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
markview.state uses markview.app.search, so a change to markview.app.search can break markview.state, while a change to markview.state can't break markview.app.search.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
markview.state uses markview_document, so a change to markview_document can break markview.state, while a change to markview.state can't break markview_document.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
markview.state uses markview.security, so a change to markview.security can break markview.state, while a change to markview.state can't break markview.security.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
markview.state uses markview.app.folder.observe, so a change to markview.app.folder.observe can break markview.state, while a change to markview.state can't break markview.app.folder.observe.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
markview.state uses markview_layout.text, so a change to markview_layout.text can break markview.state, while a change to markview.state can't break markview_layout.text.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
markview.state uses markview_layout.layout, so a change to markview_layout.layout can break markview.state, while a change to markview.state can't break markview_layout.layout.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
markview.state uses markview.app.font_panel, so a change to markview.app.font_panel can break markview.state, while a change to markview.state can't break markview.app.font_panel.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
markview.state uses markview.images, so a change to markview.images can break markview.state, while a change to markview.state can't break markview.images.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
markview.state uses markview.worker, so a change to markview.worker can break markview.state, while a change to markview.state can't break markview.worker.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
markview.state uses markview.app.preview, so a change to markview.app.preview can break markview.state, while a change to markview.state can't break markview.app.preview.
Position
Below the diagonal: markview.state uses a module listed above it, which is the healthy direction.
35→36 markview.state uses markview.app.dropdownpart of a loop✕
Connections
1 pair of types, where a type in markview.state uses a type in markview.app.dropdown.
markview.state uses markview.app.dropdown, so a change to markview.app.dropdown can break markview.state, while a change to markview.state can't break markview.app.dropdown.
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.
markview.app.dropdown uses markview.app.folder.observe, so a change to markview.app.folder.observe can break markview.app.dropdown, while a change to markview.app.dropdown can't break markview.app.folder.observe.
Position
Below the diagonal: markview.app.dropdown uses a module listed above it, which is the healthy direction.
markview.app.dropdown uses markview.state, so a change to markview.state can break markview.app.dropdown, while a change to markview.app.dropdown can't break markview.state.
Position
Below the diagonal: markview.app.dropdown uses a module listed above it, which is the healthy direction.
markview.app.chrome.components uses markview.lang, so a change to markview.lang can break markview.app.chrome.components, while a change to markview.app.chrome.components can't break markview.lang.
Position
Below the diagonal: markview.app.chrome.components uses a module listed above it, which is the healthy direction.
markview.app.chrome.components uses markview_geometry, so a change to markview_geometry can break markview.app.chrome.components, while a change to markview.app.chrome.components can't break markview_geometry.
Position
Below the diagonal: markview.app.chrome.components uses a module listed above it, which is the healthy direction.
markview.app.chrome.components uses markview_layout.style.types, so a change to markview_layout.style.types can break markview.app.chrome.components, while a change to markview.app.chrome.components can't break markview_layout.style.types.
Position
Below the diagonal: markview.app.chrome.components uses a module listed above it, which is the healthy direction.
markview.app.chrome.components uses markview.app.widgets, so a change to markview.app.widgets can break markview.app.chrome.components, while a change to markview.app.chrome.components can't break markview.app.widgets.
Position
Below the diagonal: markview.app.chrome.components uses a module listed above it, which is the healthy direction.
markview.app.chrome.components uses markview_layout.scene, so a change to markview_layout.scene can break markview.app.chrome.components, while a change to markview.app.chrome.components can't break markview_layout.scene.
Position
Below the diagonal: markview.app.chrome.components uses a module listed above it, which is the healthy direction.
markview.app.chrome.components uses markview_layout.shaping, so a change to markview_layout.shaping can break markview.app.chrome.components, while a change to markview.app.chrome.components can't break markview_layout.shaping.
Position
Below the diagonal: markview.app.chrome.components uses a module listed above it, which is the healthy direction.
markview.app.chrome.components uses markview.app.font_panel, so a change to markview.app.font_panel can break markview.app.chrome.components, while a change to markview.app.chrome.components can't break markview.app.font_panel.
Position
Below the diagonal: markview.app.chrome.components uses a module listed above it, which is the healthy direction.
markview.app.chrome.components uses markview.state, so a change to markview.state can break markview.app.chrome.components, while a change to markview.app.chrome.components can't break markview.state.
Position
Below the diagonal: markview.app.chrome.components uses a module listed above it, which is the healthy direction.
markview.app.chrome.components uses markview.app.dropdown, so a change to markview.app.dropdown can break markview.app.chrome.components, while a change to markview.app.chrome.components can't break markview.app.dropdown.
Position
Below the diagonal: markview.app.chrome.components uses a module listed above it, which is the healthy direction.
37→39 markview.app.chrome.components uses markview.apppart of a loop✕
Connections
5 pairs of types, where a type in markview.app.chrome.components uses a type in markview.app.
markview.app.chrome.components uses markview.app, so a change to markview.app can break markview.app.chrome.components, while a change to markview.app.chrome.components can't break markview.app.
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.
markview.app.chrome uses markview.lang, so a change to markview.lang can break markview.app.chrome, while a change to markview.app.chrome can't break markview.lang.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
markview.app.chrome uses markview_geometry, so a change to markview_geometry can break markview.app.chrome, while a change to markview.app.chrome can't break markview_geometry.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
markview.app.chrome uses markview.app.widgets, so a change to markview.app.widgets can break markview.app.chrome, while a change to markview.app.chrome can't break markview.app.widgets.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
markview.app.chrome uses markview_layout.scene, so a change to markview_layout.scene can break markview.app.chrome, while a change to markview.app.chrome can't break markview_layout.scene.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
markview.app.chrome uses markview_layout.style, so a change to markview_layout.style can break markview.app.chrome, while a change to markview.app.chrome can't break markview_layout.style.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
markview.app.chrome uses markview_layout.shaping, so a change to markview_layout.shaping can break markview.app.chrome, while a change to markview.app.chrome can't break markview_layout.shaping.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
markview.app.chrome uses markview.app.chrome.empty, so a change to markview.app.chrome.empty can break markview.app.chrome, while a change to markview.app.chrome can't break markview.app.chrome.empty.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
markview.app.chrome uses markview.app.preview, so a change to markview.app.preview can break markview.app.chrome, while a change to markview.app.chrome can't break markview.app.preview.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
markview.app.chrome uses markview.state, so a change to markview.state can break markview.app.chrome, while a change to markview.app.chrome can't break markview.state.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
markview.app.chrome uses markview.app.dropdown, so a change to markview.app.dropdown can break markview.app.chrome, while a change to markview.app.chrome can't break markview.app.dropdown.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
markview.app.chrome uses markview.app.chrome.components, so a change to markview.app.chrome.components can break markview.app.chrome, while a change to markview.app.chrome can't break markview.app.chrome.components.
Position
Below the diagonal: markview.app.chrome uses a module listed above it, which is the healthy direction.
38→39 markview.app.chrome uses markview.apppart of a loop✕
Connections
2 pairs of types, where a type in markview.app.chrome uses a type in markview.app.
markview.app.chrome uses markview.app, so a change to markview.app can break markview.app.chrome, while a change to markview.app.chrome can't break markview.app.
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.
1 pair of types, where a type in markview.app uses a type in markview_document.ids.
The types involved
markview.app.App → markview_document.ids.BlockId
Direction
markview.app uses markview_document.ids, so a change to markview_document.ids can break markview.app, while a change to markview.app can't break markview_document.ids.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in markview.app uses a type in markview_geometry.
The types involved
markview.app.App → markview_geometry.Rect
markview.app.Button → markview_geometry.Rect
Direction
markview.app uses markview_geometry, so a change to markview_geometry can break markview.app, while a change to markview.app can't break markview_geometry.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview_interaction.surface, so a change to markview_interaction.surface can break markview.app, while a change to markview.app can't break markview_interaction.surface.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview_layout.fonts, so a change to markview_layout.fonts can break markview.app, while a change to markview.app can't break markview_layout.fonts.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview_layout.image, so a change to markview_layout.image can break markview.app, while a change to markview.app can't break markview_layout.image.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview.app.search, so a change to markview.app.search can break markview.app, while a change to markview.app can't break markview.app.search.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in markview.app uses a type in markview.app.widgets.
The types involved
markview.app.App → markview.app.widgets.UiLayout
Direction
markview.app uses markview.app.widgets, so a change to markview.app.widgets can break markview.app, while a change to markview.app can't break markview.app.widgets.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in markview.app uses a type in markview_document.
The types involved
markview.app.App → markview_document.AnchorId
markview.app.App → markview_document.FootnoteId
Direction
markview.app uses markview_document, so a change to markview_document can break markview.app, while a change to markview.app can't break markview_document.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in markview.app uses a type in markview.app.folder.
The types involved
markview.app.App → markview.app.folder.Browser
Direction
markview.app uses markview.app.folder, so a change to markview.app.folder can break markview.app, while a change to markview.app can't break markview.app.folder.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview.security, so a change to markview.security can break markview.app, while a change to markview.app can't break markview.security.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview_document.source, so a change to markview_document.source can break markview.app, while a change to markview.app can't break markview_document.source.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview.app.folder.observe, so a change to markview.app.folder.observe can break markview.app, while a change to markview.app can't break markview.app.folder.observe.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview_layout.scene, so a change to markview_layout.scene can break markview.app, while a change to markview.app can't break markview_layout.scene.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview_layout.style, so a change to markview_layout.style can break markview.app, while a change to markview.app can't break markview_layout.style.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview.app.settings_load, so a change to markview.app.settings_load can break markview.app, while a change to markview.app can't break markview.app.settings_load.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview_layout.shaping, so a change to markview_layout.shaping can break markview.app, while a change to markview.app can't break markview_layout.shaping.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview.app.chrome.empty, so a change to markview.app.chrome.empty can break markview.app, while a change to markview.app can't break markview.app.chrome.empty.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview_layout.layout, so a change to markview_layout.layout can break markview.app, while a change to markview.app can't break markview_layout.layout.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in markview.app uses a type in markview_pdf.paint.
The types involved
markview.app.App → markview_pdf.paint.Renderer
Direction
markview.app uses markview_pdf.paint, so a change to markview_pdf.paint can break markview.app, while a change to markview.app can't break markview_pdf.paint.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview.settings, so a change to markview.settings can break markview.app, while a change to markview.app can't break markview.settings.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview.app.font_panel, so a change to markview.app.font_panel can break markview.app, while a change to markview.app can't break markview.app.font_panel.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in markview.app uses a type in markview.services.
The types involved
markview.app.App → markview.services.Services
Direction
markview.app uses markview.services, so a change to markview.services can break markview.app, while a change to markview.app can't break markview.services.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview.app.preview.work, so a change to markview.app.preview.work can break markview.app, while a change to markview.app can't break markview.app.preview.work.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in markview.app uses a type in markview.app.preview.
The types involved
markview.app.App → markview.app.preview.Preview
markview.app.App → markview.app.preview.Target
markview.app.Button → markview.app.preview.Target
Direction
markview.app uses markview.app.preview, so a change to markview.app.preview can break markview.app, while a change to markview.app can't break markview.app.preview.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in markview.app uses a type in markview.app.dropdown.
The types involved
markview.app.App → markview.app.dropdown.Dropdown
markview.app.App → markview.app.dropdown.Message
Direction
markview.app uses markview.app.dropdown, so a change to markview.app.dropdown can break markview.app, while a change to markview.app can't break markview.app.dropdown.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app uses markview.app.chrome.components, so a change to markview.app.chrome.components can break markview.app, while a change to markview.app can't break markview.app.chrome.components.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in markview.app uses a type in markview.app.chrome.
The types involved
markview.app.App → markview.app.chrome.Chrome
Direction
markview.app uses markview.app.chrome, so a change to markview.app.chrome can break markview.app, while a change to markview.app can't break markview.app.chrome.
Position
Below the diagonal: markview.app uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview.lang, so a change to markview.lang can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview.lang.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview_geometry, so a change to markview_geometry can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview_geometry.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview_layout.fonts, so a change to markview_layout.fonts can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview_layout.fonts.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview.app.widgets, so a change to markview.app.widgets can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview.app.widgets.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview.app.folder.observe, so a change to markview.app.folder.observe can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview.app.folder.observe.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview_layout.scene, so a change to markview_layout.scene can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview_layout.scene.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview.app.settings_load, so a change to markview.app.settings_load can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview.app.settings_load.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview_layout.shaping, so a change to markview_layout.shaping can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview_layout.shaping.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview.app.chrome.empty, so a change to markview.app.chrome.empty can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview.app.chrome.empty.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview.settings, so a change to markview.settings can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview.settings.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview.app.font_panel, so a change to markview.app.font_panel can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview.app.font_panel.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview.app.dropdown, so a change to markview.app.dropdown can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview.app.dropdown.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview.app.chrome.components, so a change to markview.app.chrome.components can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview.app.chrome.components.
Position
Below the diagonal: markview.app.font_panel.view uses a module listed above it, which is the healthy direction.
markview.app.font_panel.view uses markview.app, so a change to markview.app can break markview.app.font_panel.view, while a change to markview.app.font_panel.view can't break markview.app.
Position
Below the diagonal: markview.app.font_panel.view 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
151
High / Critical
A03:2025 — Software Supply Chain Failures
12
Medium
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED; Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 119 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
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.
Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 119 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
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 — 141
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 — 646
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 — 33
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
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 70 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 70 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, 799 of 820 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.
D10 Test 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. The 142 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 214 test source file(s) (.rs, .py, .java) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
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 reliability NOT SCORED: this repository's production source includes .rs, and the rust executor ran against the .rs half and did not finish re-running within its tier budget — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in web/app/vsc-ext/; node:test via `pnpm install --frozen-lockfile --ignore-scripts` in web/packages/scroll-sync/ (1 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
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 reliability for the node:test suite in web/app/vsc-ext/ was NOT MEASURED: the node:test run in web/app/vsc-ext/ produced no per-test report (✘ [ERROR] Could not resolve "../wasm/markview_web.js"). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 842 commit(s) sampled, automation and bot accounts excluded). One of them holds 94% of the history; the other 4 hold 1.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (web/packages/web/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
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.
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'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.
AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run serve`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (serve). the dev server (`npm run serve`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
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.
X3 Exception handling — 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 — 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. 222 further occurrence(s) are not listed individually; the score already reflects all 262.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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.
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.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
55 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was App::handle_user_event at 66. A further 5 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 Condition::chain at 34 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/settings/schema.rs (ReaderSettings::copy_field at 20). 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.
+ 27 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 App::handle_user_event (cyclomatic 66). — Refactoring it lifts Cyclomatic Complexity from 6.4 to about 6.5/10.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 54 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with Lower::table (cognitive 128), Renderer::draw (cognitive 89), TextShaper::shape (cognitive 88). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 4.5 to about 5.7/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 37 FileTooLong finding(s) in God Classes — start with parse.rs (2), lower.rs, api.rs. — One of this dimension's main actionable groups (37 warning-level).
Resolve the 28 MethodTooLong finding(s) in God Classes — start with paint.rs (3), table.rs (2), parse.rs (2). — One of this dimension's main actionable groups (28 warning-level).
Resolve the 13 TooManyMethods finding(s) in God Classes — start with layout.rs (2), app.rs, api.rs. — One of this dimension's main actionable groups (13 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.
59 duplicated block group(s) detected. 1.6 % of the production lines (2,773 of 175,961) are in a reported copy. A further 45 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 27 of the 104 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.
+ 51 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with search.rs, export.rs, decode.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with lib.rs, decode.rs, draws.rs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with clusters.rs, folder.rs, benchmark.rs. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.1 / 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.
25 production modules (Cargo+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 6 module(s) off the main sequence, with abstractness counted on 21 of the 25 (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: @markview/scroll-sync · ×6
What to do
Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 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 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with components.rs, complexity.rs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.5 / 10Stronggated by 5 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 5 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 142 tests. Measured on the JavaScript/TypeScript suite only — at least 214 test source file(s) (.rs, .py, .java) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: the initial document has blocks > 0 and contentHeight > 0 · ×5web/tests/demo.spec.mjs:118
What to do
Resolve the 5 No assertions finding(s) in Test Quality — start with demo.spec.mjs (4), editor.spec.mjs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d10_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.
5 outdated, 0 yanked direct Cargo dependencies. 86 of 88 direct crates were graded against crates.io (0 not published there, 2 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: clap · ×5
✓ On the Gold path — maintain.
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 614 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 14 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 MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
Top hotspots: src/app/lifecycle.rs (76×66=5016); src/app/window.rs (81×34=2754); crates/markview-layout/src/style/types.rs (42×53=2226) Repeated repair below the complexity floor: scripts/generate_test_fonts.py (3 of 5 changes were fixes); crates/markview-pdf/src/image.rs (3 of 5 changes were fixes)
Resolve the 40 Hotspot finding(s) in Churn × Complexity Hotspots — start with parse.rs (2), paint.rs (2), lifecycle.rs. — One of this dimension's main actionable groups (40 warning-level).
Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with generate_test_fonts.py, image.rs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
2 deducted task-comment markers across 178341 LoC (0.0/KLoC) → score 10.0. 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.
TodoComment · ×2src/app/window.rs:115
What to do
Resolve the 2 TodoComment finding(s) in Explicit Debt — start with window.rs (2). — One of this dimension's main actionable groups (2 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.
2 of 2 documentation facets pass in full. 74 document(s) read across 11 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.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
2 of 26 build units (Cargo, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×2Cargo.toml:1
What to do
Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Cargo.toml (2). — One of this dimension's main actionable groups (2 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).
151 finding(s): 0 critical, 139 high, 12 medium, 0 low. 119 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 4 file(s) — `crates/markview-render/src/gpu.rs` (line 184, line 463, line 526, …), `docs/screenshots/source/showcase/zh/web.html`, `fuzz/scripts/campaign.sh` (line 13, line 14), `fuzz/scripts/rsscap.sh` (line 20) — 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 7 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 119 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (124 issue-level, 5 of them charged here).
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
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 5 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 349 of the 445 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with controls.rs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with interaction.rs, state.rs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Change coupling finding(s) in Change Coupling — start with controls.rs, export.rs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Other · Code Health — Unreviewed-generation residue in this repository's Rust: functions whose whole body is still `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Rust: functions whose body is `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, match arms and branches left as `todo!()`, functions that take inputs and return a constant (`Ok(())`, `None`, `Default::default()`, an empty `Vec`) or do nothing, and impls most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`warm_fonts` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/markview-layout/src/shaping.rs:367
`validate` does real work, but one of its branches is `bail!` with a "not implemented" message — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. (×2) — crates/markview-layout/src/style/types.rs:1252, src/export/config.rs:234
`call_string` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/markview-platform/src/android_stub.rs:4
`impl DirectManipulation` has 4 unfinished methods out of 7 — a scaffolded type that was never implemented. — crates/markview-platform/src/dm.rs:494
`new` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — crates/markview-platform/src/dm.rs:495, crates/markview-platform/src/window.rs:27
`contact` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/markview-platform/src/dm.rs:498
`resize` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/markview-platform/src/dm.rs:502
`deadline` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/markview-platform/src/dm.rs:507
`impl NativeFrame` has 2 unfinished methods out of 4 — a scaffolded type that was never implemented. — crates/markview-platform/src/window.rs:26
`set_fullscreen` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/markview-platform/src/window.rs:34
`remove` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/images/cache.rs:269
`report` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/logging.rs:18
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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 4/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `fuzz/fuzzlib`, `web`, `xtask`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
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.
`web/app/vsc-ext/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — web/app/vsc-ext/package.json:13
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.
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.
Do you agree with this assessment?
R1 · Type Safety4.9 / 10Adequate✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
20 typed · 21 plain JS — the untyped files are web/build.mjs, REDACTED, REDACTED, web/packages/build-package.mjs, web/packages/scroll-sync/tests/scroll-sync.test.mjs, web/scripts/wasm.mjs (+15 more).
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
REDACTED:112 · REDACTED:23 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:112
web/packages/fonts/src/index.ts:94 · web/packages/markview/src/fonts.ts:10 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — web/packages/fonts/src/index.ts:94
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
decodePng has cyclomatic complexity 26 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/tests/png.mjs:7
#frame has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/packages/markview/src/viewer.ts:247
(anonymous) has cyclomatic complexity 14 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/packages/markview/src/reader.ts:265
#scrollMap has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/packages/editor/src/index.ts:302
Do you agree with this assessment?
R3 · Large Files8.5 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
web/packages/editor/src/index.ts has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/packages/editor/src/index.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage7.0 / 10Strong✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×7) — web/packages/editor/src/index.ts:1, REDACTED:1, REDACTED:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
12 file(s) (~2351 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — web/app/vsc-ext
11 file(s) (~1483 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: web/packages/markview/src/index.ts imports '../wasm/markview_web.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — web/packages/markview
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
web/packages/markview/src/font-set.ts → web/packages/markview/src/index.ts → web/packages/markview/src/font-set.ts (one verified cycle inside a mutually-dependent group of 3 files) — web/packages/markview/src/font-set.ts:2
What to do
Break each cycle by extracting the shared piece into a module both sides can import.
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 any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document1.4 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`widget_id` is public and takes a `Command` as its receiver from its caller, and it calls itself at line 182 with a piece of the document (and at line 183, line 184, line 185, line 186) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `widget_id` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/state/command.rs:182
`contact` is public and takes a `DirectManipulation` as its receiver from its caller, and it calls itself at line 110 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `contact` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/dm.rs:110
`resize` is public and takes a `DirectManipulation` as its receiver from its caller, and it calls itself at line 113 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `resize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/dm.rs:113
`abandon` is public and takes a `DirectManipulation` as its receiver from its caller, and it calls itself at line 116 with a piece of the document (and at line 118) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `abandon` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/dm.rs:116
`deadline` is public and takes a `DirectManipulation` as its receiver from its caller, and it calls itself at line 124 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `deadline` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/dm.rs:124
`pump` is public and takes a `DirectManipulation` as its receiver from its caller, and it calls itself at line 127 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `pump` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/dm.rs:127
`toggle` is public, takes a document from its caller (line 351) and hands it to `remove`, which calls itself at line 254 with a piece of the document (and at line 255, line 256, line 257, line 259) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `remove` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/folder.rs:254
`toggle` is public, takes a document from its caller (line 351) and hands it to `insert`, which calls itself at line 324 with a piece of the document (and at line 325) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `insert` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/folder.rs:324
`take` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 94 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `take` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/modal.rs:94
`animating` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 189 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `animating` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/outline.rs:189
`reset` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 43 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `reset` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/quick_open.rs:43
`take` is public and takes a `State` as its receiver from its caller, and it calls itself at line 32 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `take` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/sidebar.rs:32
`view` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 44 with a piece of the document (and at line 45) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `view` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/ui_model.rs:44
`update` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 51 with a piece of the document (and at line 54, line 57) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `update` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/ui_model.rs:51
`refresh` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 376 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `refresh` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/viewer.rs:376
`cancel_press` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 383 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `cancel_press` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/viewer.rs:383
`cancel` is public and takes a `Worker` as its receiver from its caller, and it calls itself at line 210 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `cancel` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/app/preview/work.rs:210
`translate` is public and takes a `Draw` as its receiver from its caller, and it calls itself at line 228 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `translate` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene.rs:228
`len` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 82 with a piece of the document (and at line 84) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `len` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:82
`capacity` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 93 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `capacity` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:93
`iter_mut` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 178 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `iter_mut` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:178
`push` is public and takes a `DrawBuffer` as its receiver from its caller, and it recurses at line 184 through `tail_mut` and back with a piece of the document (and at line 195) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `push` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:184
`reserve` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 181 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `reserve` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:181
`extend` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 187 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `extend` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:187
`independent_range` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 254 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `independent_range` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:254
`seal` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 296 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `seal` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:296
`shrink_to_fit` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 288 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `shrink_to_fit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:288
`storage_bytes` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 434 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `storage_bytes` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:434
`heap_bytes` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 411 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `heap_bytes` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:411
`packed_counts` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 457 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `packed_counts` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:457
`visit_storage` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 593 with a piece of the document (and at line 595, line 597) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `visit_storage` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/draws.rs:593
`heap_bytes` is public and takes a `Draw` as its receiver from its caller, and it calls itself at line 13 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `heap_bytes` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-layout/src/scene/memory.rs:13
`hash` is public and takes a `Block` as its receiver from its caller, and it calls itself at line 519 with a piece of the document (and at line 520) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `hash` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-document/src/lib.rs:519
`images` is public and takes a `Block` as its receiver from its caller, and it calls itself at line 817 with a piece of the document (and at line 822, line 830, line 837, line 846, line 856, line 866) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `images` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-document/src/lib.rs:817
`for_each_code_block` is public and takes a `Block` as its receiver from its caller, and it calls itself at line 898 with a piece of the document (and at line 904, line 910, line 917, line 924) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `for_each_code_block` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-document/src/lib.rs:898
`details_declared` is public and takes a `Block` as its receiver from its caller, and it calls itself at line 950 with a piece of the document (and at line 954, line 957, line 960, line 964, line 968) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `details_declared` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-document/src/lib.rs:950
`visit_fields` is public, takes a document from its caller (line 34) and hands it to `walk`, which calls itself at line 76 with a piece of the document (and at line 89, line 96, line 108, line 115, line 129, line 135, line 141) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `walk` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-document/src/visit.rs:76
`visit_blocks` is public and takes `block: &Block` from its caller, and it calls itself at line 158 with a piece of the document (and at line 164, line 170, line 177, line 184) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `visit_blocks` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/markview-document/src/visit.rs:158
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`image.into_raw()` (line 56) gives up ownership in exchange for a raw handle — the value's `Drop` will no longer run — and nothing in the crate's code ever reclaims a `image` from a raw pointer (`image::from_raw`). The memory or descriptor stays allocated until the process ends, once per call. Pair the hand-out with its reclaim (a `free` function that rebuilds the owner with `from_raw` and drops it), or keep the owning value. — crates/markview-platform/src/icon.rs:56
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 1/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`loadFontSources` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — web/packages/markview/src/fonts.ts:5
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
`MermaidStyle.primary_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1291
`MermaidStyle.primary_text_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1292
`MermaidStyle.primary_border_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1293
`MermaidStyle.line_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1294
`MermaidStyle.secondary_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1295
`MermaidStyle.tertiary_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1296
`MermaidStyle.edge_label_background` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1297
`MermaidStyle.cluster_background` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1298
`MermaidStyle.cluster_border` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1299
`MermaidStyle.sequence_actor_fill` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1301
`MermaidStyle.sequence_actor_border` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1302
`MermaidStyle.sequence_actor_line` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1303
`MermaidStyle.sequence_note_fill` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1304
`MermaidStyle.sequence_note_border` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1305
`MermaidStyle.sequence_activation_fill` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1306
`MermaidStyle.sequence_activation_border` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1307
`MermaidStyle.text_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1308
`MermaidStyle.git_colors` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1309
`MermaidStyle.git_inv_colors` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1310
`MermaidStyle.git_branch_label_colors` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1311
`MermaidStyle.git_commit_label_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1312
`MermaidStyle.git_commit_label_background` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1313
`MermaidStyle.git_tag_label_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1314
`MermaidStyle.git_tag_label_background` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1315
`MermaidStyle.git_tag_label_border` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1316
`MermaidStyle.pie_colors` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1317
`MermaidStyle.pie_title_text_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1319
`MermaidStyle.pie_section_text_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1321
`MermaidStyle.pie_legend_text_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1323
`MermaidStyle.pie_stroke_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1324
`MermaidStyle.pie_outer_stroke_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/markview-layout/src/style/types.rs:1327
What to do
Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. 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?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
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.
Other · Code Health — Whether Rust's absent values are handled rather than forced — `Option` and `Result` make absence a value the caller must handle in every crate, and each `.unwrap()` or `.expect()` that no guard on its path proves present is a panic the first time the value is `None` or `Err`.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
`value.parse::<u64>()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `build_metadata` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — build.rs:72
`std::time::SystemTime::now().duration_since(std::time::UNIX_EPOCH)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_metadata` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — build.rs:77
`metadata["metadata"]["lint"]["cyclomatic-complexity-threshold"].as_u64()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `audit` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/complexity.rs:73
`PathBuf::from(env!("CARGO_MANIFEST_DIR")).parent()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `workspace_root` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/complexity.rs:131
`path.parent()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `external_module` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/complexity.rs:221
`metadata["packages"].as_array()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/complexity.rs:306
`package["targets"].as_array()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/complexity.rs:307
`target["kind"].as_array()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/complexity.rs:308
`target["src_path"].as_str()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/complexity.rs:313
`path.parent()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/complexity.rs:314
`list.parse_args_with(Punctuated::<Meta,Token![,]>::parse_terminated,)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `requires_test` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/complexity.rs:346
`self.scores.pop()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `function` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/complexity.rs:385
`self.functions.pop()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `measure` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/coupling.rs:515
`path.file_stem()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `callout_icons` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/icons.rs:117
`path.file_stem().unwrap().to_str()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `callout_icons` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — xtask/src/icons.rs:117
`markview_platform::tempdir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/app.rs:559
`times.last()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `percentiles` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/benchmark.rs:43
`self.entries.get_mut(&source)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `schedule_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/images.rs:864
`self.document.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `export_source` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/pdf.rs:266
`write!(hex,"{byte:02x}")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `hex_digest` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/security.rs:17
`serde_json::to_value(grant)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `cache_key` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/security.rs:228
`serde_json::to_vec(&key)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `cache_key` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/security.rs:237
`tokio::runtime::Builder::new_current_thread().max_blocking_threads(4).enable_all().build()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/services.rs:41
`thread::Builder::new().name("markview-network".into()).spawn(move||{let runtime=tokio::runtime::Builder::new_current_thread().max_blocking_threads(4).enable_all().build().expect("start I/O runtime");runtime.block_on(async move{let mut running=tokio::task::JoinSet::new();loop{tokio::select!{biased;_=stop.cancelled()=>break,Some(operation)=recv.recv()=>{running.spawn(operation);},Some(result)=running.join_next(),if!running.is_empty()=>{if let Err(error)=result{log::warn!("I/O operation failed: {error}");}}}}recv.close();while let Ok(operation)=recv.try_recv(){running.spawn(operation);}let drain=async{while let Some(result)=running.join_next().await{if let Err(error)=result{log::warn!("I/O operation failed: {error}");}}};if tokio::time::timeout(SHUTDOWN_GRACE,drain).await.is_err(){log::warn!("I/O shutdown abandoned work inside a blocking call");}drop(running);});runtime.shutdown_timeout(Duration::ZERO);})` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/services.rs:72
`crate::net::browser_headers(&crate::settings::ReaderSettings::default(),)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/services.rs:86
`crate::net::browser_headers(settings)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `configure_http` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/services.rs:107
`source.page.paper_mm()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `load_over` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/stylesheet.rs:191
`content_type.unwrap_or("").split(';').next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `is_markdown` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/web_page.rs:74
`thread::Builder::new().name("markview-layout".into()).stack_size(8*1024*1024).spawn(move||{crate::layout::TextShaper::warm_fonts(&fonts);let wake:markview_layout::background::Wake=Arc::new({let inbox=thread_inbox.clone();move||{let(lock,signal)=&*inbox;Inbox::lock(lock).background_ready=true;signal.notify_one();}});let mut engine=LayoutEngine::with_executor(io.cpu.clone(),wake.clone());engine.set_auto_parallelism();let mut images=crate::images::Images::with_services(offline,crate::images::cache_directory(),fonts.clone(),io,None,wake,);let mut last:Option<Request>=None;let mut completed_version=0;let mut counted:Option<(u64,markview_layout::text::TextCounts,)>=None;let mut cached:Option<(PathBuf,u64,markview_commonmark::Dialect,Arc<markview_commonmark::MarkdownParse>,)>=None;loop{let Some((request,release))=wait_for_request(&thread_inbox,images.poll_deadline())else{break;};if release{cached=None;last=None;counted=None;engine.release_document();images.release();continue;}let Some(request)=request else{let changed=images.poll();let highlights=last.is_some()&&engine.poll_highlights();if changed||highlights{let(lock,_)=&*thread_inbox;let mut inbox=Inbox::lock(lock);if inbox.pending.is_none()&&!inbox.stopped&&!inbox.release{inbox.pending=last.clone();}}continue;};let mut request=request;if last.as_ref().is_some_and(|last|last.options!=request.options){counted=None;}last=Some(request.clone());images.set_workspace(request.workspace.clone());images.set_standalone_image(crate::file::is_picture(&request.path).then(||request.path.clone()),);engine.set_parallel_start(request.coverage);let rendered=rendered.clone();let version=request.version;engine.set_parallel_ready(Arc::new(move||rendered.load(Ordering::Relaxed)==version));let mut update=Update{version:request.version,path:request.path.clone(),requested:request.requested,result:None,read_ms:0.0,parse_ms:0.0,layout_ms:0.0,counts:None,};update.result=Some((||->Result<ReaderSnapshot,String>{let dialect=markview_commonmark::Dialect{hard_breaks:request.options.hard_breaks,highlight_marks:request.options.highlight_marks,ofm:request.options.ofm,grid_tables:request.options.grid_tables,};let document=if let Some(loaded)=&request.loaded{loaded.with_dialect(dialect)}else if let Some((path,revision,cached_dialect,doc,))=&cached&&(path,revision,cached_dialect)==(&request.path,&request.content_version,&dialect){request.security=request.security.for_content(&doc.source);crate::loaded::LoadedDocument::markdown(doc.clone(),)}else{let start=Instant::now();let text=read_markdown(&request.path).map_err(|e|format!("{e:#}"))?;request.security=request.security.for_content(&text);update.read_ms=start.elapsed().as_secs_f64()*1000.0;let start=Instant::now();let source:Arc<str>=text.into();let previous=cached.as_ref().filter(|(path,_,cached_dialect,_)|{path==&request.path&&*cached_dialect==dialect}).map(|(_,_,_,doc)|doc.clone());let doc=match previous{Some(previous)=>{Arc::new(markview_commonmark::reparse_with(&previous,source.clone(),dialect,),)}None=>{let prefix_start=Instant::now();if current.sequence.load(Ordering::Relaxed)==request.version&&let Some(prefix)=markview_commonmark::parse_prefix_with(&source,PREFIX_BYTES,dialect,){let prefix_parse=prefix_start.elapsed().as_secs_f64()*1000.0;engine.validate_stylesheet(&request.options.stylesheet,).map_err(|e|{format!("Fonts: {e:#}")})?;images.set_security(request.security.clone(),);images.set_requested_image(request.requested_image.clone());images.set_initial_width(request.options.width,);images.prepare(&prefix,&request.path,request.content_version,request.load_all_images,&request.options.stylesheet,&request.options.fonts,);let layout_start=Instant::now();let wanted=f32::from_bits(target.coverage.load(Ordering::Relaxed),);let mut shown=None;engine.layout_progressive_cancellable(&prefix,&request.options,&images.snapshot,|snapshot|{if!snapshot.blocks.is_empty()&&snapshot.height>=wanted{shown=Some(snapshot.clone(),);return false;}true},||{current.sequence.load(Ordering::Relaxed)!=request.version},);if let Some(layout)=shown{let mut partial=update.clone();partial.parse_ms=prefix_parse;partial.layout_ms=layout_start.elapsed().as_secs_f64()*1000.0;partial.result=Some(Ok(ReaderSnapshot{blocked_images:images.blocked.clone(),document:crate::loaded::LoadedDocument::markdown(Arc::new(prefix),),layout,content_version:request.content_version,complete:false,parse_complete:false,remote_deferred:images.deferred_remote(),}));done(partial);}}Arc::new(markview_commonmark::parse_with(source.clone(),dialect,),)}};update.parse_ms=start.elapsed().as_secs_f64()*1000.0;if cached.as_ref().is_some_and(|(path,_,_,_)|path!=&request.path,){engine.release_document();}cached=Some((request.path.clone(),request.content_version,dialect,doc.clone(),));crate::loaded::LoadedDocument::markdown(doc)};if current.sequence.load(Ordering::Relaxed)!=request.version{return Err("Superseded".into());}parsed(request.path.clone(),request.content_version,document.clone(),);let start=Instant::now();engine.validate_stylesheet(&request.options.stylesheet,).map_err(|e|format!("Fonts: {e:#}"))?;images.set_security(request.security.clone());images.set_requested_image(request.requested_image.clone());images.set_initial_width(request.options.width);images.prepare(&document,&request.path,request.content_version,request.load_all_images,&request.options.stylesheet,&request.options.fonts,);let size=document.size();engine.set_parallel_start(if size<32*1024{f32::INFINITY}else{request.coverage});let mut publication=PrefixPublication::new(size);let layout=engine.layout_progressive_cancellable(&document,&request.options,&images.snapshot,|prefix|{if current.sequence.load(Ordering::Relaxed)!=request.version{return false;}let wanted=f32::from_bits(target.coverage.load(Ordering::Relaxed),);if request.version!=completed_version&&publication.publish(prefix.blocks.len(),prefix.height,wanted,start.elapsed(),){let mut partial=update.clone();partial.layout_ms=start.elapsed().as_secs_f64()*1000.;partial.result=Some(Ok(ReaderSnapshot{blocked_images:images.blocked.clone(),document:document.clone(),layout:prefix.clone(),content_version:request.content_version,complete:false,parse_complete:true,remote_deferred:images.deferred_remote(),}));done(partial);}true},||{current.sequence.load(Ordering::Relaxed)!=request.version},).ok_or_else(||"Superseded".to_string())?;update.layout_ms=start.elapsed().as_secs_f64()*1000.0;Ok(ReaderSnapshot{blocked_images:images.blocked.clone(),document:document.clone(),layout,content_version:request.content_version,complete:true,parse_complete:true,remote_deferred:images.deferred_remote(),})})());if current.sequence.load(Ordering::Relaxed)==request.version{if update.result.as_ref().is_some_and(|r|r.is_ok()){completed_version=request.version;}let next=match&update.result{Some(Ok(reader))if reader.complete=>{let restored=*restored_counts.lock().unwrap();let id=reader.document.document().content_key().get();match counted.filter(|(key,_)|*key==id).or(restored){Some((id,counts))if id==reader.document.document().content_key().get()=>{Some(counts)}_=>{let pending={let(lock,_)=&*thread_inbox;Inbox::lock(lock).pending.is_some()};(!pending).then(||{let counts=markview_layout::text::TextCounts::of(&reader.layout.full_reading_text());counted=Some((reader.document.document().content_key().get(),counts,));counts})}}}_=>None,};update.counts=next;done(update);}}engine.release_document();images.release();})` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `with_services_and_parsed` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/worker.rs:594
`fs::write(path,text)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/settings/store/proptests.rs:117
`self.session.folder` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `buttons_for` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/app/chrome.rs:437
`form` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `buttons_for` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/app/chrome.rs:490, src/app/chrome.rs:515
`self.session.folder` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `draw_layer` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/app/chrome.rs:778
`form` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `draw_panel_overlay` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/app/chrome.rs:1235, src/app/chrome.rs:1274
`output` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `spawn_export` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/app/export.rs:364
`path.file_name()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/app/file_search.rs:45, src/app/file_search.rs:52
`path.strip_prefix(root)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/app/file_search.rs:47
What to do
Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 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.
X10 Duplicated predicate — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 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 — 57 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 — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — Not applicable: this repository's Java 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 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; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. 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 — AX6 reached only 7% of this repository's production lines — rust (167,126 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run serve`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — 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.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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 case and prefix conventions rows: 1 candidate(s) found and not reported.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
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. Aggregate roots were found in only one source directory (markview-platform), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
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) — 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.
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: the JavaScript/TypeScript half could not be measured — the node:test suite in web/app/vsc-ext/ ran and not one test passed (✘ [ERROR] Could not resolve "../wasm/markview_web.js"), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 61 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
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
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 JVM, 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
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
S1 Web-Security Posture — No web surface: 281 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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
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
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
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
X3 Exception handling — X3 reached only 7% of this repository's production lines — rust (167,126 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Boundary-crossing change coupling: controls.rs ↔ store.rs src/app/chrome/controls.rs:1— `src/app/chrome/controls.rs` (context chrome) and `src/settings/store.rs` (context settings) sit in DIFFERENT parts of the tree yet change together 83% of the time (10 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — 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 `b55a9821` feat: restore browsing sessions across launches; `186c8f8e` fix: move tab style to user settings and default to underline; `b30c8836` feat: add optional single-instance window reuse — run `git show` on any of them.
Hotspot: src/app/lifecycle.rs src/app/lifecycle.rs:180— src/app/lifecycle.rs changed 76 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in App::handle_user_event at line 180. 13 of those changes were fix/bug commits, and the other 63 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- src/app/lifecycle.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: src/app/window.rs src/app/window.rs:616— src/app/window.rs changed 81 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in App::dispatch_key at line 616. 18 of those changes were fix/bug commits, and the other 63 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- src/app/window.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: crates/markview-layout/src/style/types.rs crates/markview-layout/src/style/types.rs:937— crates/markview-layout/src/style/types.rs changed 42 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in Rule::overlay at line 937. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-layout/src/style/types.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: crates/markview-commonmark/src/parse.rs crates/markview-commonmark/src/parse.rs:1043— crates/markview-commonmark/src/parse.rs changed 52 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in Reader::child_block at line 1043. 4 of those changes were fix/bug commits, and the other 48 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-commonmark/src/parse.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: crates/markview-layout/src/shaping.rs crates/markview-layout/src/shaping.rs:903— crates/markview-layout/src/shaping.rs changed 40 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in TextShaper::shape at line 903. 1 of those changes was a fix/bug commit, and the other 39 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-layout/src/shaping.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: src/worker.rs src/worker.rs:150— src/worker.rs changed 36 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in Worker::with_services_and_parsed at line 150. 7 of those changes were fix/bug commits, and the other 29 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- src/worker.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: crates/markview-document/src/lib.rs crates/markview-document/src/lib.rs:789— crates/markview-document/src/lib.rs changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in Block::images at line 789. 3 of those changes were fix/bug commits, and the other 38 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-document/src/lib.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: crates/markview-pdf/src/paint.rs crates/markview-pdf/src/paint.rs:659— crates/markview-pdf/src/paint.rs changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in Painter::draw at line 659. 5 of those changes were fix/bug commits, and the other 20 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-pdf/src/paint.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: src/app/painting.rs src/app/painting.rs:29— src/app/painting.rs changed 35 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in App::render at line 29. 4 of those changes were fix/bug commits, and the other 31 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- src/app/painting.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: crates/markview-render/src/paint.rs crates/markview-render/src/paint.rs:128— crates/markview-render/src/paint.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in Renderer::draw at line 128. 6 of those changes were fix/bug commits, and the other 17 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-render/src/paint.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: fuzz/fuzzlib/src/seam.rs fuzz/fuzzlib/src/seam.rs:279— fuzz/fuzzlib/src/seam.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in mvfuzz::seam::definition_scan at line 279. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- fuzz/fuzzlib/src/seam.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: crates/markview-layout/src/style/parse.rs crates/markview-layout/src/style/parse.rs:457— crates/markview-layout/src/style/parse.rs changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in markview_layout::style::parse::validate_numbers at line 457. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-layout/src/style/parse.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: src/app/settings_panel.rs src/app/settings_panel.rs:152— src/app/settings_panel.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in Model::update at line 152. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- src/app/settings_panel.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: crates/markview-layout/src/layout/paragraph.rs crates/markview-layout/src/layout/paragraph.rs:329— crates/markview-layout/src/layout/paragraph.rs changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in BlockContext::paragraph_bounded at line 329. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-layout/src/layout/paragraph.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: crates/markview-layout/src/layout/table.rs crates/markview-layout/src/layout/table.rs:79— crates/markview-layout/src/layout/table.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in BlockContext::table at line 79. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-layout/src/layout/table.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: src/app/search.rs src/app/search.rs:531— src/app/search.rs changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in App::apply_search_navigation at line 531. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- src/app/search.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: crates/markview-render/src/frame.rs crates/markview-render/src/frame.rs:78— crates/markview-render/src/frame.rs changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Renderer::prepare at line 78. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-render/src/frame.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: REDACTED REDACTED:137— REDACTED changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in test.main at line 137. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- REDACTED`: 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: crates/markview-webpage/src/lower.rs crates/markview-webpage/src/lower.rs:792— crates/markview-webpage/src/lower.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in Lower::table at line 792. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-webpage/src/lower.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: src/images/diagram.rs src/images/diagram.rs:101— src/images/diagram.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in markview::images::diagram::resolve at line 101. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- src/images/diagram.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: android/java/io/github/szdytom/markview/MarkviewActivity.java android/java/io/github/szdytom/markview/MarkviewActivity.java:265— android/java/io/github/szdytom/markview/MarkviewActivity.java changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in MarkviewActivity.receiveResult at line 265. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- android/java/io/github/szdytom/markview/MarkviewActivity.java`: 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: crates/markview-layout/src/scene/flow.rs crates/markview-layout/src/scene/flow.rs:356— crates/markview-layout/src/scene/flow.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in BlockLayout::seal_scene at line 356. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-layout/src/scene/flow.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: fuzz/fuzzlib/src/oracle.rs fuzz/fuzzlib/src/oracle.rs:73— fuzz/fuzzlib/src/oracle.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in mvfuzz::oracle::document at line 73. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- fuzz/fuzzlib/src/oracle.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: crates/markview-layout/src/paginate.rs crates/markview-layout/src/paginate.rs:179— crates/markview-layout/src/paginate.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in markview_layout::paginate::bands at line 179. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-layout/src/paginate.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: crates/markview-layout/src/layout/cache.rs crates/markview-layout/src/layout/cache.rs:186— crates/markview-layout/src/layout/cache.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in markview_layout::layout::cache::block_link_origins at line 186. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-layout/src/layout/cache.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.
+ 15 more in this group — see findings.md.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×40
Symbol treated as nullable, then dereferenced unguarded build.rs:72— `value.parse::<u64>()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `build_metadata` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded build.rs:77— `std::time::SystemTime::now().duration_since(std::time::UNIX_EPOCH)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build_metadata` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/complexity.rs:73— `metadata["metadata"]["lint"]["cyclomatic-complexity-threshold"].as_u64()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `audit` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/complexity.rs:131— `PathBuf::from(env!("CARGO_MANIFEST_DIR")).parent()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `workspace_root` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/complexity.rs:221— `path.parent()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `external_module` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/complexity.rs:306— `metadata["packages"].as_array()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/complexity.rs:307— `package["targets"].as_array()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/complexity.rs:308— `target["kind"].as_array()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/complexity.rs:313— `target["src_path"].as_str()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/complexity.rs:314— `path.parent()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/complexity.rs:346— `list.parse_args_with(Punctuated::<Meta,Token![,]>::parse_terminated,)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `requires_test` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/complexity.rs:385— `self.scores.pop()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `function` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/coupling.rs:515— `self.functions.pop()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `measure` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/icons.rs:117— `path.file_stem()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `callout_icons` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded xtask/src/icons.rs:117— `path.file_stem().unwrap().to_str()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `callout_icons` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded src/app.rs:559— `markview_platform::tempdir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded src/benchmark.rs:43— `times.last()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `percentiles` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded src/images.rs:864— `self.entries.get_mut(&source)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `schedule_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded src/pdf.rs:266— `self.document.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `export_source` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded src/security.rs:17— `write!(hex,"{byte:02x}")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `hex_digest` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded src/security.rs:228— `serde_json::to_value(grant)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `cache_key` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded src/security.rs:237— `serde_json::to_vec(&key)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `cache_key` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded src/services.rs:41— `tokio::runtime::Builder::new_current_thread().max_blocking_threads(4).enable_all().build()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded src/services.rs:72— `thread::Builder::new().name("markview-network".into()).spawn(move||{let runtime=tokio::runtime::Builder::new_current_thread().max_blocking_threads(4).enable_all().build().expect("start I/O runtime");runtime.block_on(async move{let mut running=tokio::task::JoinSet::new();loop{tokio::select!{biased;_=stop.cancelled()=>break,Some(operation)=recv.recv()=>{running.spawn(operation);},Some(result)=running.join_next(),if!running.is_empty()=>{if let Err(error)=result{log::warn!("I/O operation failed: {error}");}}}}recv.close();while let Ok(operation)=recv.try_recv(){running.spawn(operation);}let drain=async{while let Some(result)=running.join_next().await{if let Err(error)=result{log::warn!("I/O operation failed: {error}");}}};if tokio::time::timeout(SHUTDOWN_GRACE,drain).await.is_err(){log::warn!("I/O shutdown abandoned work inside a blocking call");}drop(running);});runtime.shutdown_timeout(Duration::ZERO);})` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded src/services.rs:86— `crate::net::browser_headers(&crate::settings::ReaderSettings::default(),)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
+ 15 more in this group — see findings.md.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×38
Recursive walk over a caller-supplied document has no depth cap src/state/command.rs:182— `widget_id` is public and takes a `Command` as its receiver from its caller, and it calls itself at line 182 with a piece of the document (and at line 183, line 184, line 185, line 186) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `widget_id` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/dm.rs:110— `contact` is public and takes a `DirectManipulation` as its receiver from its caller, and it calls itself at line 110 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `contact` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/dm.rs:113— `resize` is public and takes a `DirectManipulation` as its receiver from its caller, and it calls itself at line 113 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `resize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/dm.rs:116— `abandon` is public and takes a `DirectManipulation` as its receiver from its caller, and it calls itself at line 116 with a piece of the document (and at line 118) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `abandon` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/dm.rs:124— `deadline` is public and takes a `DirectManipulation` as its receiver from its caller, and it calls itself at line 124 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `deadline` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/dm.rs:127— `pump` is public and takes a `DirectManipulation` as its receiver from its caller, and it calls itself at line 127 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `pump` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/folder.rs:254— `toggle` is public, takes a document from its caller (line 351) and hands it to `remove`, which calls itself at line 254 with a piece of the document (and at line 255, line 256, line 257, line 259) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `remove` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/folder.rs:324— `toggle` is public, takes a document from its caller (line 351) and hands it to `insert`, which calls itself at line 324 with a piece of the document (and at line 325) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `insert` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/modal.rs:94— `take` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 94 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `take` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/outline.rs:189— `animating` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 189 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `animating` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/quick_open.rs:43— `reset` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 43 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `reset` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/sidebar.rs:32— `take` is public and takes a `State` as its receiver from its caller, and it calls itself at line 32 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `take` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/ui_model.rs:44— `view` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 44 with a piece of the document (and at line 45) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `view` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/ui_model.rs:51— `update` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 51 with a piece of the document (and at line 54, line 57) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `update` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/viewer.rs:376— `refresh` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 376 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `refresh` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/viewer.rs:383— `cancel_press` is public and takes a `Model` as its receiver from its caller, and it calls itself at line 383 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `cancel_press` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/app/preview/work.rs:210— `cancel` is public and takes a `Worker` as its receiver from its caller, and it calls itself at line 210 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `cancel` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/markview-layout/src/scene.rs:228— `translate` is public and takes a `Draw` as its receiver from its caller, and it calls itself at line 228 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `translate` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/markview-layout/src/scene/draws.rs:82— `len` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 82 with a piece of the document (and at line 84) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `len` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/markview-layout/src/scene/draws.rs:93— `capacity` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 93 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `capacity` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/markview-layout/src/scene/draws.rs:178— `iter_mut` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 178 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `iter_mut` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/markview-layout/src/scene/draws.rs:184— `push` is public and takes a `DrawBuffer` as its receiver from its caller, and it recurses at line 184 through `tail_mut` and back with a piece of the document (and at line 195) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `push` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/markview-layout/src/scene/draws.rs:181— `reserve` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 181 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `reserve` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/markview-layout/src/scene/draws.rs:187— `extend` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 187 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `extend` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/markview-layout/src/scene/draws.rs:254— `independent_range` is public and takes a `DrawBuffer` as its receiver from its caller, and it calls itself at line 254 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `independent_range` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
FileTooLong: src/parse.rs crates/markview-commonmark/src/parse.rs— FileTooLong — 1639 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: Reader (3 blocks, 170-1611). The bar is 500 significant lines; this is 1139 over it, 3.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lower.rs crates/markview-webpage/src/lower.rs— FileTooLong — 1371 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 68% of them inside a single declaration: Lower (2 blocks, 45-1283), declaring 33 free functions. The bar is 500 significant lines; this is 871 over it, 2.74× 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/api.rs crates/markview-web/src/api.rs— FileTooLong — 1178 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: Markview (3 blocks, 184-1463). The bar is 500 significant lines; this is 678 over it, 2.36× 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: chrome/components.rs src/app/chrome/components.rs— FileTooLong — 1142 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 642 over it, 2.28× 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: layout/blocks.rs crates/markview-layout/src/layout/blocks.rs— FileTooLong — 1069 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: BlockContext (333-1292). The bar is 500 significant lines; this is 569 over it, 2.14× 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: style/types.rs crates/markview-layout/src/style/types.rs— FileTooLong — 1065 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 565 over it, 2.13× 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/paint.rs crates/markview-pdf/src/paint.rs— FileTooLong — 1053 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: Painter (2 blocks, 146-1259). The bar is 500 significant lines; this is 553 over it, 2.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: app/chrome.rs src/app/chrome.rs— FileTooLong — 1038 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: Chrome (2 blocks, 232-1410). The bar is 500 significant lines; this is 538 over it, 2.08× 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: app/folder.rs src/app/folder.rs— FileTooLong — 977 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 477 over it, 1.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/shaping.rs crates/markview-layout/src/shaping.rs— FileTooLong — 952 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: TextShaper (3 blocks, 149-1410). The bar is 500 significant lines; this is 452 over it, 1.90× 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: scene/flow.rs crates/markview-layout/src/scene/flow.rs— FileTooLong — 904 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 404 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/images.rs src/images.rs— FileTooLong — 904 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 76% of them inside a single declaration: Images (2 blocks, 335-1355). The bar is 500 significant lines; this is 404 over it, 1.81× 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: app/pointer.rs src/app/pointer.rs— FileTooLong — 882 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: App (284-1323). The bar is 500 significant lines; this is 382 over it, 1.76× 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: app/preview.rs src/app/preview.rs— FileTooLong — 838 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 338 over it, 1.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/cli.rs src/cli.rs— FileTooLong — 810 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 310 over it, 1.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: font_panel/view.rs src/app/font_panel/view.rs— FileTooLong — 771 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 271 over it, 1.54× 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: app/text_input.rs src/app/text_input.rs— FileTooLong — 760 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: App (250-1030). The bar is 500 significant lines; this is 260 over it, 1.52× 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: app/window.rs src/app/window.rs— FileTooLong — 719 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: App (77-1061). The bar is 500 significant lines; this is 219 over it, 1.44× 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/html.rs crates/markview-commonmark/src/html.rs— FileTooLong — 701 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 32 free functions. The bar is 500 significant lines; this is 201 over it, 1.40× 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/style.rs crates/markview-layout/src/style.rs— FileTooLong — 696 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: Stylesheet (4 blocks, 103-940). The bar is 500 significant lines; this is 196 over it, 1.39× 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/lib.rs crates/markview-document/src/lib.rs— FileTooLong — 671 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 171 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: app/search.rs src/app/search.rs— FileTooLong — 650 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: App (217-845). The bar is 500 significant lines; this is 150 over it, 1.30× 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/state.rs src/state.rs— FileTooLong — 644 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 144 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/scene.rs crates/markview-layout/src/scene.rs— FileTooLong — 625 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 125 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: app/gestures.rs src/app/gestures.rs— FileTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: App (94-820). The bar is 500 significant lines; this is 86 over it, 1.17× 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.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1291— `MermaidStyle.primary_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1292— `MermaidStyle.primary_text_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1293— `MermaidStyle.primary_border_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1294— `MermaidStyle.line_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1295— `MermaidStyle.secondary_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1296— `MermaidStyle.tertiary_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1297— `MermaidStyle.edge_label_background` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1298— `MermaidStyle.cluster_background` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1299— `MermaidStyle.cluster_border` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1301— `MermaidStyle.sequence_actor_fill` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1302— `MermaidStyle.sequence_actor_border` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1303— `MermaidStyle.sequence_actor_line` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1304— `MermaidStyle.sequence_note_fill` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1305— `MermaidStyle.sequence_note_border` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1306— `MermaidStyle.sequence_activation_fill` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1307— `MermaidStyle.sequence_activation_border` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1308— `MermaidStyle.text_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1309— `MermaidStyle.git_colors` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1310— `MermaidStyle.git_inv_colors` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1311— `MermaidStyle.git_branch_label_colors` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1312— `MermaidStyle.git_commit_label_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1313— `MermaidStyle.git_commit_label_background` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1314— `MermaidStyle.git_tag_label_color` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1315— `MermaidStyle.git_tag_label_background` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/markview-layout/src/style/types.rs:1316— `MermaidStyle.git_tag_label_border` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
MethodTooLong: Worker.with_services_and_parsed src/worker.rs:150— MethodTooLong — with_services_and_parsed runs 352 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 252 over it, 3.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: Renderer.draw crates/markview-render/src/paint.rs:128— MethodTooLong — draw runs 326 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 226 over it, 3.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: App.handle_user_event src/app/lifecycle.rs:180— MethodTooLong — handle_user_event runs 257 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 157 over it, 2.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BlockContext.table crates/markview-layout/src/layout/table.rs:79— MethodTooLong — table runs 241 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 141 over it, 2.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Reader.child_block crates/markview-commonmark/src/parse.rs:1043— MethodTooLong — child_block runs 227 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 127 over it, 2.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Lower.table crates/markview-webpage/src/lower.rs:792— MethodTooLong — table runs 196 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 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Painter.draw crates/markview-pdf/src/paint.rs:659— MethodTooLong — draw runs 173 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 73 over it, 1.73× 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: TextShaper.shape crates/markview-layout/src/shaping.rs:903— MethodTooLong — shape runs 161 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 61 over it, 1.61× 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: BlockContext.code crates/markview-layout/src/layout/code.rs:17— MethodTooLong — code runs 151 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 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BlockContext.prepare crates/markview-layout/src/layout/inline.rs:48— MethodTooLong — prepare 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: App.render src/app/painting.rs:29— MethodTooLong — render runs 145 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 45 over it, 1.45× 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: BlockContext.paragraph_bounded crates/markview-layout/src/layout/paragraph.rs:329— MethodTooLong — paragraph_bounded 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.
MethodTooLong: Painter.math crates/markview-pdf/src/paint.rs:915— MethodTooLong — math 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.
MethodTooLong: BlockContext.block_inner crates/markview-layout/src/layout/blocks.rs:710— MethodTooLong — block_inner runs 136 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 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LayoutEngine.begin_layout_root crates/markview-layout/src/layout/progressive.rs:127— MethodTooLong — begin_layout_root 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: Renderer.prepare crates/markview-render/src/frame.rs:78— MethodTooLong — prepare runs 133 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 33 over it, 1.33× 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: TextShaper.build_layout crates/markview-layout/src/shaping.rs:718— MethodTooLong — build_layout runs 132 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 32 over it, 1.32× 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: Form.new src/app/chrome/components.rs:797— MethodTooLong — new runs 119 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 19 over it, 1.19× 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: Model.update src/app/settings_panel.rs:152— MethodTooLong — update runs 119 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 19 over it, 1.19× 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: Images.start src/images.rs:941— MethodTooLong — start 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.
MethodTooLong: BlockContext.measured_block crates/markview-layout/src/layout/blocks.rs:563— MethodTooLong — measured_block 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.
MethodTooLong: App.new src/app.rs:439— MethodTooLong — new runs 112 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 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TextInput.draw crates/markview-layout/src/text_input.rs:400— MethodTooLong — draw runs 110 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 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Geometry.decorated_base crates/markview-render/src/geometry.rs:51— MethodTooLong — decorated_base 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: Reader.inline_step crates/markview-commonmark/src/parse.rs:427— MethodTooLong — inline_step 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.
markview::fonts::report::merge_progress (cognitive 44) src/fonts/report.rs:213— markview::fonts::report::merge_progress has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (32 pts), match/switch 3 (8 pts), loops 2 (4 pts) (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview::images::diagram::resolve (cognitive 40) src/images/diagram.rs:101— markview::images::diagram::resolve has cognitive complexity 40 (threshold 15). Drivers by points: if/else 40. 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.
markview::app::chrome::frame::caption_paint (cognitive 31) src/app/chrome/frame.rs:77— markview::app::chrome::frame::caption_paint has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18 (28 pts), match/switch 1 (3 pts) (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.
markview::app::chrome::styles::style_rows (cognitive 25) src/app/chrome/styles.rs:241— markview::app::chrome::styles::style_rows has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (4 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview::app::font_panel::view::fonts_controls (cognitive 25) src/app/font_panel/view.rs:381— markview::app::font_panel::view::fonts_controls has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 2, loops 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.
markview::app::preview::fit_scene (cognitive 25) src/app/preview.rs:338— markview::app::preview::fit_scene has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 4 (7 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview::app::chrome::outline::draw_with_rows (cognitive 24) src/app/chrome/outline.rs:305— markview::app::chrome::outline::draw_with_rows has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 2, loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview::app::font_panel::view::draw_font_body (cognitive 23) src/app/font_panel/view.rs:763— markview::app::font_panel::view::draw_font_body has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (7 pts), boolean chains 4 (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.
markview::stylesheet::catalog_for (cognitive 22) src/stylesheet.rs:230— markview::stylesheet::catalog_for has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, loops 2 (3 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview::app::chrome::empty::geometry (cognitive 20) src/app/chrome/empty.rs:46— markview::app::chrome::empty::geometry has cognitive complexity 20 (threshold 15). Drivers by points: if/else 18, boolean chains 2. 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.
markview::app::file_search::find (cognitive 20) src/app/file_search.rs:151— markview::app::file_search::find has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (6 pts), boolean chains 1 (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.
markview::app::chrome::styles::draw_styles (cognitive 19) src/app/chrome/styles.rs:347— markview::app::chrome::styles::draw_styles has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 4, boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
markview::fonts::catalog::install (cognitive 19) src/fonts/catalog.rs:416— markview::fonts::catalog::install has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (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.
markview::app::chrome::controls::wrap (cognitive 18) src/app/chrome/controls.rs:492— markview::app::chrome::controls::wrap has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview::app::chrome::empty::draw_row (cognitive 17) src/app/chrome/empty.rs:479— markview::app::chrome::empty::draw_row has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 1, match/switch 1 (nesting depth added 2). 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.
markview::app::chrome::empty::buttons (cognitive 16) src/app/chrome/empty.rs:127— markview::app::chrome::empty::buttons has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview::app::chrome::outline::buttons_with_rows (cognitive 16) src/app/chrome/outline.rs:180— markview::app::chrome::outline::buttons_with_rows has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview::app::font_panel::view::download_control_rect (cognitive 16) src/app/font_panel/view.rs:301— markview::app::font_panel::view::download_control_rect has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4 (nesting depth added 2). 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.
markview::app::font_panel::view::draw_fonts (cognitive 16) src/app/font_panel/view.rs:622— markview::app::font_panel::view::draw_fonts has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), loops 3 (nesting depth added 2). 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.
markview::latency::edit_scenario (cognitive 16) src/latency.rs:302— markview::latency::edit_scenario has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (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.
markview_layout::linebreak::optimize (cognitive 66) crates/markview-layout/src/linebreak.rs:225— markview_layout::linebreak::optimize has cognitive complexity 66 (threshold 15). Drivers by points: if/else 23 (51 pts), boolean chains 8, loops 4 (7 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.
markview_layout::layout::cache::block_link_origins::walk (cognitive 30) crates/markview-layout/src/layout/cache.rs:212— markview_layout::layout::cache::block_link_origins::walk has cognitive complexity 30 (threshold 15). Drivers by points: loops 10 (25 pts), if/else 2 (4 pts), match/switch 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
markview_layout::layout::table::borders::rectangles (cognitive 30) crates/markview-layout/src/layout/table/borders.rs:151— markview_layout::layout::table::borders::rectangles has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (26 pts), loops 3, 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.
markview_layout::paginate::paginate (cognitive 29) crates/markview-layout/src/paginate.rs:397— markview_layout::paginate::paginate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (3 pts) (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.
markview_layout::layout::anchor::anchored_scroll (cognitive 27) crates/markview-layout/src/layout/anchor.rs:37— markview_layout::layout::anchor::anchored_scroll has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (7 pts), boolean chains 3 (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.
markview_layout::linebreak::greedy_with_first (cognitive 26) crates/markview-layout/src/linebreak.rs:375— markview_layout::linebreak::greedy_with_first has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 4, loops 2 (3 pts) (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.
markview_layout::layout::inline::hyphenation_candidates (cognitive 25) crates/markview-layout/src/layout/inline.rs:715— markview_layout::layout::inline::hyphenation_candidates has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (7 pts), boolean chains 3 (nesting depth added 15). 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.
markview_layout::layout::table::borders::collapse_borders (cognitive 25) crates/markview-layout/src/layout/table/borders.rs:57— markview_layout::layout::table::borders::collapse_borders has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 8, loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_layout::text::text_position (cognitive 24) crates/markview-layout/src/text.rs:177— markview_layout::text::text_position has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (3 pts), boolean chains 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.
markview_layout::paginate::furniture::page_furniture (cognitive 23) crates/markview-layout/src/paginate/furniture.rs:123— markview_layout::paginate::furniture::page_furniture has cognitive complexity 23 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 3 (7 pts), match/switch 2 (7 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_layout::style::parse::validate_numbers (cognitive 22) crates/markview-layout/src/style/parse.rs:457— markview_layout::style::parse::validate_numbers has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, loops 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_layout::style::parse::split_rule (cognitive 19) crates/markview-layout/src/style/parse.rs:392— markview_layout::style::parse::split_rule has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_layout::text::word_range (cognitive 19) crates/markview-layout/src/text.rs:31— markview_layout::text::word_range has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, loops 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_layout::microtype::space_mixed_scripts (cognitive 18) crates/markview-layout/src/microtype.rs:468— markview_layout::microtype::space_mixed_scripts has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (8 pts), boolean chains 5, loops 2 (5 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.
markview_layout::paginate::collect_anchors (cognitive 18) crates/markview-layout/src/paginate.rs:532— markview_layout::paginate::collect_anchors has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_layout::linebreak::line_score (cognitive 17) crates/markview-layout/src/linebreak.rs:160— markview_layout::linebreak::line_score has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 2 (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.
markview_layout::paginate::apply_page_constraints (cognitive 17) crates/markview-layout/src/paginate.rs:358— markview_layout::paginate::apply_page_constraints has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_layout::microtype::adjust (cognitive 16) crates/markview-layout/src/microtype.rs:265— markview_layout::microtype::adjust has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
markview_layout::paginate::bands (cognitive 16) crates/markview-layout/src/paginate.rs:179— markview_layout::paginate::bands has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 5 (7 pts), boolean chains 1, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App::handle_user_event (cognitive 74) src/app/lifecycle.rs:180— App::handle_user_event has cognitive complexity 74 (threshold 15). Drivers by points: if/else 27 (63 pts), boolean chains 8, match/switch 2 (3 pts) (nesting depth added 37). 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.
App::scroll_event (cognitive 40) src/app/window.rs:382— App::scroll_event has cognitive complexity 40 (threshold 15). Drivers by points: if/else 23 (32 pts), boolean chains 4, match/switch 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App::render (cognitive 32) src/app/painting.rs:29— App::render has cognitive complexity 32 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 6, match/switch 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.
App::apply_search_navigation (cognitive 29) src/app/search.rs:531— App::apply_search_navigation has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 5, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App::dispatch_key (cognitive 26) src/app/window.rs:616— App::dispatch_key has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 6, match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App::page_command (cognitive 22) src/app/ui.rs:77— App::page_command has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (18 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App::touch_surface (cognitive 19) src/app/gestures.rs:209— App::touch_surface has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (15 pts), loops 2 (3 pts), boolean chains 1 (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.
App::pointer_moved (cognitive 19) src/app/pointer.rs:285— App::pointer_moved has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4 (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.
App::folder_loaded (cognitive 18) src/app/folder.rs:787— App::folder_loaded has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App::trackpad_scroll (cognitive 17) src/app/gestures.rs:601— App::trackpad_scroll has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1, 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.
App::refresh_settings_resources (cognitive 17) src/app/settings_load.rs:262— App::refresh_settings_resources has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 2, match/switch 2 (nesting depth added 2). 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.
App::frame_press (cognitive 16) src/app/frame.rs:421— App::frame_press has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3 (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.
App::open_web_page (cognitive 16) src/app/web_page.rs:26— App::open_web_page has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyMethods: App src/app.rs:357— TooManyMethods — 433 methods, declared across 37 files: app/pointer.rs (44), app/folder.rs (34), app/ui.rs (34), app/text_input.rs (29), +33 more file(s). The bar is 30 methods; this is 403 over it, 14.43× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Markview crates/markview-web/src/api.rs:184— TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Stylesheet crates/markview-layout/src/style.rs:103— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MarkviewActivity android/java/io/github/szdytom/markview/MarkviewActivity.java:33— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Tabs src/app/tabs.rs:65— TooManyMethods — 42 methods, declared across 2 files: app/tabs.rs (39), app/session.rs (3). The bar is 30 methods; this is 12 over it, 1.40× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BlockContext crates/markview-layout/src/layout.rs:290— TooManyMethods — 41 methods, declared across 9 files: layout/blocks.rs (15), layout/inline.rs (7), layout/images.rs (5), layout/table.rs (5), +5 more file(s). The bar is 30 methods; this is 11 over it, 1.37× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Markview web/packages/markview/src/markview.ts:19— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Chrome src/app/chrome.rs:232— TooManyMethods — 39 methods, declared across 2 files: app/chrome.rs (37), chrome/codeblock.rs (2). The bar is 30 methods; this is 9 over it, 1.30× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LayoutSnapshot crates/markview-layout/src/scene.rs:389— TooManyMethods — 38 methods, declared across 8 files: text/semantic.rs (13), src/scene.rs (7), text/geometry.rs (6), text/selection.rs (5), +4 more file(s). The bar is 30 methods; this is 8 over it, 1.27× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Renderer crates/markview-render/src/lib.rs:132— TooManyMethods — 38 methods, declared across 3 files: src/lib.rs (24), src/frame.rs (11), src/paint.rs (3). The bar is 30 methods; this is 8 over it, 1.27× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LayoutEngine crates/markview-layout/src/layout.rs:307— TooManyMethods — 34 methods, declared across 5 files: src/layout.rs (21), layout/progressive.rs (6), layout/subtree.rs (4), progressive/parallel.rs (2), +1 more file(s). The bar is 30 methods; this is 4 over it, 1.13× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RasterCache crates/markview-render/src/raster.rs:107— TooManyMethods — 33 methods, declared across 2 files: src/raster.rs (28), raster/path.rs (5). The bar is 30 methods; this is 3 over it, 1.10× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: State src/app/pointer.rs:25— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FunctionTooLong: extension.activate web/app/vsc-ext/vscode/src/preview/extension.ts:10— FunctionTooLong — activate runs 263 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 163 over it, 2.63× 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: markview::app::chrome::controls::rows src/app/chrome/controls.rs:55— FunctionTooLong — markview::app::chrome::controls::rows runs 227 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 127 over it, 2.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: markview::benchmark::run src/benchmark.rs:119— FunctionTooLong — markview::benchmark::run runs 158 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 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: markview::latency::run src/latency.rs:444— FunctionTooLong — markview::latency::run runs 142 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 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: markview::app::chrome::outline::draw_with_rows src/app/chrome/outline.rs:305— FunctionTooLong — markview::app::chrome::outline::draw_with_rows runs 123 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 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: markview_layout::linebreak::optimize crates/markview-layout/src/linebreak.rs:225— FunctionTooLong — markview_layout::linebreak::optimize runs 116 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 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: markview::app::font_panel::view::fonts_controls src/app/font_panel/view.rs:381— FunctionTooLong — markview::app::font_panel::view::fonts_controls runs 112 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 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: markview::app::font_panel::view::draw_fonts src/app/font_panel/view.rs:622— FunctionTooLong — markview::app::font_panel::view::draw_fonts runs 107 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 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: markview_document::semantic_key crates/markview-document/src/lib.rs:985— FunctionTooLong — markview_document::semantic_key runs 104 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 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: webview.update web/app/vsc-ext/vscode/src/preview/webview.ts:63— FunctionTooLong — update runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: markview::app::chrome::export::rows src/app/chrome/export.rs:14— FunctionTooLong — markview::app::chrome::export::rows 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.
FunctionTooLong: markview::app::chrome::styles::draw_styles src/app/chrome/styles.rs:347— FunctionTooLong — markview::app::chrome::styles::draw_styles 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.
markview_commonmark::make::walk_fields (cognitive 32) crates/markview-commonmark/src/make.rs:196— markview_commonmark::make::walk_fields has cognitive complexity 32 (threshold 15). Drivers by points: loops 11 (27 pts), if/else 2 (4 pts), match/switch 1 (nesting depth added 18). 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.
markview_commonmark::incremental::definitions (cognitive 26) crates/markview-commonmark/src/incremental.rs:367— markview_commonmark::incremental::definitions has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 3, 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.
markview_commonmark::make::rebase_links (cognitive 22) crates/markview-commonmark/src/make.rs:409— markview_commonmark::make::rebase_links has cognitive complexity 22 (threshold 15). Drivers by points: loops 6 (13 pts), if/else 4 (8 pts), match/switch 1 (nesting depth added 11). Of this number, 17 points are the body's own statements and 5 belong to one function item inside it that branches. 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.
markview_commonmark::make::build_map::nested (cognitive 21) crates/markview-commonmark/src/make.rs:330— markview_commonmark::make::build_map::nested has cognitive complexity 21 (threshold 15). Drivers by points: loops 8 (20 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
markview_commonmark::html::block_events (cognitive 20) crates/markview-commonmark/src/html.rs:260— markview_commonmark::html::block_events has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, match/switch 1 (3 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_commonmark::html::block_from (cognitive 20) crates/markview-commonmark/src/html.rs:462— markview_commonmark::html::block_from has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (3 pts), match/switch 1 (2 pts), boolean chains 1 (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.
markview_commonmark::html::normalize (cognitive 18) crates/markview-commonmark/src/html.rs:994— markview_commonmark::html::normalize has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_commonmark::incremental::parse_prefix_with (cognitive 18) crates/markview-commonmark/src/incremental.rs:170— markview_commonmark::incremental::parse_prefix_with has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 3 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_commonmark::incremental::parse_incremental (cognitive 17) crates/markview-commonmark/src/incremental.rs:22— markview_commonmark::incremental::parse_incremental has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 4, boolean chains 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_commonmark::html::classify (cognitive 16) crates/markview-commonmark/src/html.rs:593— markview_commonmark::html::classify has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 3 (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.
ClassTooLong: Reader crates/markview-commonmark/src/parse.rs:170— ClassTooLong — 1054 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 170-1611. The bar is 400 significant lines; this is 654 over it, 2.64× 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: Lower crates/markview-webpage/src/lower.rs:45— ClassTooLong — 937 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 29 methods, 2 blocks, lines 45-1283. The bar is 400 significant lines; this is 537 over it, 2.34× 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: Markview crates/markview-web/src/api.rs:184— ClassTooLong — 914 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 73 methods, 3 blocks, lines 184-1463. The bar is 400 significant lines; this is 514 over it, 2.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Chrome src/app/chrome.rs:232— ClassTooLong — 865 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 39 methods, 2 blocks, lines 232-1410. The bar is 400 significant lines; this is 465 over it, 2.16× 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: TextShaper crates/markview-layout/src/shaping.rs:149— ClassTooLong — 836 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 149-1410. The bar is 400 significant lines; this is 436 over it, 2.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Painter crates/markview-pdf/src/paint.rs:146— ClassTooLong — 762 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 18 methods, 2 blocks, lines 146-1259. The bar is 400 significant lines; this is 362 over it, 1.91× 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: Images src/images.rs:335— ClassTooLong — 688 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 30 methods, 2 blocks, lines 335-1355. The bar is 400 significant lines; this is 288 over it, 1.72× 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: Stylesheet crates/markview-layout/src/style.rs:103— ClassTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 50 methods, 4 blocks, lines 103-940. The bar is 400 significant lines; this is 139 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: Worker src/worker.rs:112— ClassTooLong — 425 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 4 blocks, lines 112-667. The bar is 400 significant lines; this is 25 over it, 1.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Form src/app/chrome/components.rs:778— ClassTooLong — 417 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, 3 blocks, lines 778-1362. The bar is 400 significant lines; this is 17 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.
LayoutSnapshot::geometry_selection_rects_in (cognitive 39) crates/markview-layout/src/text/geometry.rs:182— LayoutSnapshot::geometry_selection_rects_in has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (32 pts), loops 3 (6 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.
LayoutSnapshot::visit_search_clusters (cognitive 38) crates/markview-layout/src/search.rs:202— LayoutSnapshot::visit_search_clusters has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (27 pts), loops 4 (10 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutSnapshot::geometry_hit_test_text (cognitive 37) crates/markview-layout/src/text/geometry.rs:12— LayoutSnapshot::geometry_hit_test_text has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (31 pts), loops 3 (6 pts) (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.
LayoutSnapshot::geometry_extract_text (cognitive 28) crates/markview-layout/src/text.rs:547— LayoutSnapshot::geometry_extract_text has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutSnapshot::geometry_rebase_selection (cognitive 25) crates/markview-layout/src/text/selection.rs:24— LayoutSnapshot::geometry_rebase_selection has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutSnapshot::geometry_search_selection (cognitive 19) crates/markview-layout/src/search.rs:262— LayoutSnapshot::geometry_search_selection has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutSnapshot::image_at (cognitive 17) crates/markview-layout/src/scene.rs:471— LayoutSnapshot::image_at has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (3 pts), boolean chains 2 (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.
LayoutSnapshot::link_ref_at (cognitive 16) crates/markview-layout/src/scene.rs:516— LayoutSnapshot::link_ref_at has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (3 pts), boolean chains 1 (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.
BlockContext::table (cognitive 61) crates/markview-layout/src/layout/table.rs:79— BlockContext::table has cognitive complexity 61 (threshold 15). Drivers by points: if/else 23 (43 pts), loops 11 (18 pts) (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.
BlockContext::build_grid (cognitive 45) crates/markview-layout/src/layout/table.rs:492— BlockContext::build_grid has cognitive complexity 45 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 8 (21 pts), boolean chains 2 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlockContext::paragraph_bounded (cognitive 25) crates/markview-layout/src/layout/paragraph.rs:329— BlockContext::paragraph_bounded has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 5, loops 3 (4 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlockContext::code (cognitive 24) crates/markview-layout/src/layout/code.rs:17— BlockContext::code has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlockContext::prepare (cognitive 20) crates/markview-layout/src/layout/inline.rs:48— BlockContext::prepare has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (5 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.
BlockContext::units (cognitive 19) crates/markview-layout/src/layout/inline.rs:334— BlockContext::units has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 3, loops 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.
BlockContext::measured_block (cognitive 16) crates/markview-layout/src/layout/blocks.rs:563— BlockContext::measured_block has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 4, loops 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.
Duplicated block (10 lines × 2) crates/markview-layout/src/search.rs:217— crates/markview-layout/src/search.rs:217-226 | crates/markview-layout/src/source.rs:437-446 — 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 `crates/markview-layout/src/search.rs:217` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) src/app/export.rs:411— src/app/export.rs:411-420 | src/app/export.rs:613-622 — both copies are in the same file, so extract the 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 `src/app/export.rs:411` 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 `self` to `super) fn export_finished(&mut` in one and `&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 (10 lines × 2) crates/markview-image/src/decode.rs:447— crates/markview-image/src/decode.rs:447-456 | src/images/fonts.rs:227-236 — 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 `crates/markview-image/src/decode.rs:447` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/app/folder.rs:520— src/app/folder.rs:520-529 | src/app/outline.rs:192-201 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `super) fn advance_animation(&mut` in one and `crate) fn advance_animation(&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 (10 lines × 2) crates/markview-render/src/raster.rs:136— crates/markview-render/src/raster.rs:136-145 | crates/markview-render/src/raster/color.rs:35-44 — 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 `crates/markview-render/src/raster.rs:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) fuzz/fuzzlib/src/oracle.rs:383— fuzz/fuzzlib/src/oracle.rs:383-392 | fuzz/fuzzlib/src/oracle.rs:404-413 — both copies are in the same file, so extract the 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 `fuzz/fuzzlib/src/oracle.rs:383` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) fuzz/fuzzlib/src/bin/mathprobe.rs:564— fuzz/fuzzlib/src/bin/mathprobe.rs:564-573 | fuzz/fuzzlib/src/probe.rs:94-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
R4 · Test Coverage· No test reaches this file · ×7
No test reaches this file web/packages/editor/src/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/packages/fonts/src/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/build.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/packages/build-package.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/packages/editor/src/style.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
markview_layout::style::parse::generic_field_allowed (cyclomatic 31) crates/markview-layout/src/style/parse.rs:658— markview_layout::style::parse::generic_field_allowed has cyclomatic complexity 31 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
markview_layout::linebreak::optimize (cyclomatic 29) crates/markview-layout/src/linebreak.rs:225— markview_layout::linebreak::optimize has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
markview_layout::layout::cache::block_link_origins::walk (cyclomatic 22) crates/markview-layout/src/layout/cache.rs:212— markview_layout::layout::cache::block_link_origins::walk has cyclomatic complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
markview_layout::layout::table::borders::collapse_borders (cyclomatic 18) crates/markview-layout/src/layout/table/borders.rs:57— markview_layout::layout::table::borders::collapse_borders has cyclomatic complexity 18 (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.
markview_layout::paginate::bands (cyclomatic 17) crates/markview-layout/src/paginate.rs:179— markview_layout::paginate::bands has cyclomatic complexity 17 (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.
markview_layout::style::parse::validate_numbers (cyclomatic 17) crates/markview-layout/src/style/parse.rs:457— markview_layout::style::parse::validate_numbers 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.
TooManyFields: App src/app.rs:357— TooManyFields — 53 stored fields beside 433 methods. The bar is 30 stored fields; this is 23 over it, 1.77× 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.
TooManyFields: Rule crates/markview-layout/src/style/types.rs:829— TooManyFields — 52 stored fields beside 3 methods. The bar is 30 stored fields; this is 22 over it, 1.73× 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.
TooManyFields: MermaidStyle crates/markview-layout/src/style/types.rs:1283— TooManyFields — 41 stored fields beside 3 methods. The bar is 30 stored fields; this is 11 over it, 1.37× 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.
TooManyFields: Markview crates/markview-web/src/api.rs:184— TooManyFields — 36 stored fields beside 73 methods. The bar is 30 stored fields; this is 6 over it, 1.20× 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.
TooManyFields: ReaderSession src/state.rs:178— TooManyFields — 34 stored fields beside 30 methods. The bar is 30 stored fields; this is 4 over it, 1.13× 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.
TooManyFields: Images src/images.rs:335— TooManyFields — 32 stored fields beside 30 methods. The bar is 30 stored fields; this is 2 over it, 1.07× 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.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×6
Edited copy of a member (7 corresponding lines) crates/markview-geometry/src/lib.rs:13— crates/markview-geometry/src/lib.rs:13-19 | crates/markview-render/src/lib.rs:406-412 — 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) crates/markview-image/src/decode.rs:254— crates/markview-image/src/decode.rs:254-260 | src/images.rs:209-215 — 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) crates/markview-layout/src/scene/draws.rs:80— crates/markview-layout/src/scene/draws.rs:80-86 | crates/markview-layout/src/scene/draws.rs:91-97 — 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) src/file.rs:40— src/file.rs:40-46 | src/app/folder.rs:425-431 — 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) src/app/chrome/modal.rs:181— src/app/chrome/modal.rs:181-187 | src/app/chrome/preview.rs:110-116 — 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) src/app/font_panel/view.rs:371— src/app/font_panel/view.rs:371-377 | src/app/fonts_command.rs:138-146 — 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.
Duplicated block (7 lines × 2) crates/markview-layout/src/text/clusters.rs:155— crates/markview-layout/src/text/clusters.rs:155-161 | crates/markview-layout/src/text/clusters.rs:170-177 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/markview-layout/src/text/clusters.rs:155` it does not close everything it opens, so those 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) src/app/chrome/folder.rs:470— src/app/chrome/folder.rs:470-476 | src/app/chrome/outline.rs:426-432 — 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 `src/app/chrome/folder.rs:470` 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) src/benchmark.rs:39— src/benchmark.rs:39-45 | src/latency.rs:64-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/benchmark.rs:39` 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) crates/markview-commonmark/src/html.rs:120— crates/markview-commonmark/src/html.rs:120-126 | crates/markview-document/src/lib.rs:261-267 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) src/app/chrome/modal.rs:172— src/app/chrome/modal.rs:172-179 | src/app/chrome/preview.rs:70-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) src/app/chrome/footer.rs:7— src/app/chrome/footer.rs:7-14 | src/app/tab_metrics.rs:77-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/markview-layout/src/layout/code.rs:112— crates/markview-layout/src/layout/code.rs:112-117 | crates/markview-layout/src/layout/paragraph.rs:228-233 — 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 `crates/markview-layout/src/layout/code.rs:112` 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) src/images.rs:679— src/images.rs:679-684 | src/images.rs:1348-1353 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/images.rs:685` calls `into` and `src/images.rs:1354` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) crates/markview-image/src/decode.rs:255— crates/markview-image/src/decode.rs:255-260 | src/images.rs:210-215 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `column` to `f32) -> (u32` in one and `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 (6 lines × 2) src/app/chrome/modal.rs:296— src/app/chrome/modal.rs:296-301 | src/app/chrome/modal.rs:340-345 — both copies are in the same file, so extract the 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) fuzz/fuzzlib/src/bin/dump.rs:35— fuzz/fuzzlib/src/bin/dump.rs:35-40 | fuzz/fuzzlib/src/bin/dump.rs:51-56 — both copies are in the same file, so extract the 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 `fuzz/fuzzlib/src/bin/dump.rs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `fuzz/fuzzlib/src/bin/dump.rs:50` calls `blocks` and `fuzz/fuzzlib/src/bin/dump.rs:34` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) fuzz/fuzzlib/src/parallel.rs:135— fuzz/fuzzlib/src/parallel.rs:135-140 | fuzz/fuzzlib/src/parallel.rs:147-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fuzz/fuzzlib/src/parallel.rs:135` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Off the main sequence: @markview/scroll-sync — @markview/scroll-sync: 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: markview-font-archive — markview-font-archive: 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: markview-geometry — markview-geometry: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: markview-platform — markview-platform: 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: markview-document — markview-document: abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: markview-layout — markview-layout: abstractness 0.01, instability 0.25, distance 0.74 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
IC1 · Incompleteness & stubs· Empty method body · ×6
Empty method body — does nothing with its inputs crates/markview-layout/src/shaping.rs:367— `warm_fonts` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/markview-platform/src/dm.rs:498— `contact` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/markview-platform/src/dm.rs:502— `resize` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/markview-platform/src/window.rs:34— `set_fullscreen` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs src/images/cache.rs:269— `remove` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs src/logging.rs:18— `report` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
App::handle_user_event (cyclomatic 66) src/app/lifecycle.rs:180— App::handle_user_event has cyclomatic complexity 66 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
App::dispatch_key (cyclomatic 34) src/app/window.rs:616— App::dispatch_key has cyclomatic complexity 34 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
App::render (cyclomatic 27) src/app/painting.rs:29— App::render has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
App::scroll_event (cyclomatic 26) src/app/window.rs:382— App::scroll_event has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
App::apply_search_navigation (cyclomatic 19) src/app/search.rs:531— App::apply_search_navigation 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.
No assertions: the initial document has blocks > 0 and contentHeight > 0 web/tests/demo.spec.mjs:118— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: typing into #source re-renders the canvas web/tests/demo.spec.mjs:126— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: glyphs > 0 and frames > 0 after the rAF loop runs web/tests/demo.spec.mjs:145— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: a second edit reuses blocks and changes contentHeight web/tests/demo.spec.mjs:236— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: divider grip stays centered across layouts and host styles web/tests/editor.spec.mjs:648— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×5
Duplicated block (9 lines × 2) crates/markview-commonmark/src/incremental.rs:627— crates/markview-commonmark/src/incremental.rs:627-635 | fuzz/fuzzlib/src/seam.rs:653-661 — 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) crates/markview-pdf/src/paint.rs:999— crates/markview-pdf/src/paint.rs:999-1008 | crates/markview-pdf/src/paint.rs:1034-1042 — both copies are in the same file, so extract the 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 `crates/markview-pdf/src/paint.rs:999` 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) src/app/preview.rs:292— src/app/preview.rs:292-300 | src/app/session.rs:236-244 — 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 `src/app/session.rs:236` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) fuzz/fuzz_targets/reparse.rs:29— fuzz/fuzz_targets/reparse.rs:29-37 | fuzz/fuzzlib/src/reparse_sequence.rs:103-111 — 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 `fuzz/fuzz_targets/reparse.rs:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) fuzz/fuzzlib/src/web_layout.rs:90— fuzz/fuzzlib/src/web_layout.rs:90-98 | fuzz/fuzzlib/src/web_layout.rs:99-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
TextShaper::shape (cognitive 88) crates/markview-layout/src/shaping.rs:903— TextShaper::shape has cognitive complexity 88 (threshold 15). Drivers by points: if/else 20 (54 pts), loops 10 (28 pts), boolean chains 6 (nesting depth added 52). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextShaper::resolve_fonts (cognitive 49) crates/markview-layout/src/shaping.rs:407— TextShaper::resolve_fonts has cognitive complexity 49 (threshold 15). Drivers by points: if/else 12 (33 pts), match/switch 3 (8 pts), loops 2 (5 pts), boolean chains 3 (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.
TextShaper::scan_collection (cognitive 30) crates/markview-layout/src/shaping.rs:589— TextShaper::scan_collection has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (26 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextShaper::build_layout (cognitive 29) crates/markview-layout/src/shaping.rs:718— TextShaper::build_layout has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 6 (10 pts), boolean chains 4, match/switch 1 (3 pts) (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.
Duplicated block (8 lines × 2) crates/markview-commonmark/src/html.rs:376— crates/markview-commonmark/src/html.rs:376-383 | crates/markview-commonmark/src/html.rs:753-760 — both copies are in the same file, so extract the 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 `crates/markview-commonmark/src/html.rs:376` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) crates/markview-web/src/images.rs:233— crates/markview-web/src/images.rs:233-240 | crates/markview-web/src/images.rs:249-256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/markview-web/src/images.rs:233` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/app/search.rs:200— src/app/search.rs:200-207 | src/worker.rs:648-655 — 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 `src/app/search.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. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `super) fn shutdown(&mut` in one and `crate) fn shutdown(&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 (8 lines × 2) fuzz/fuzzlib/src/mutators.rs:423— fuzz/fuzzlib/src/mutators.rs:423-430 | fuzz/fuzzlib/src/mutators.rs:780-787 — both copies are in the same file, so extract the 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 `fuzz/fuzzlib/src/mutators.rs:423` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Hollow method — returns a constant without doing the work crates/markview-platform/src/android_stub.rs:4— `call_string` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/markview-platform/src/dm.rs:495— `new` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/markview-platform/src/dm.rs:507— `deadline` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/markview-platform/src/window.rs:27— `new` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Lower::table (cyclomatic 48) crates/markview-webpage/src/lower.rs:792— Lower::table has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Lower::lower_block (cyclomatic 22) crates/markview-webpage/src/lower.rs:221— Lower::lower_block has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Lower::inline_element (cyclomatic 18) crates/markview-webpage/src/lower.rs:1083— Lower::inline_element has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TextShaper::shape (cyclomatic 34) crates/markview-layout/src/shaping.rs:903— TextShaper::shape 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.
TextShaper::resolve_fonts (cyclomatic 21) crates/markview-layout/src/shaping.rs:407— TextShaper::resolve_fonts 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.
TextShaper::build_layout (cyclomatic 16) crates/markview-layout/src/shaping.rs:718— TextShaper::build_layout 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.
BlockContext::table (cyclomatic 30) crates/markview-layout/src/layout/table.rs:79— BlockContext::table has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BlockContext::build_grid (cyclomatic 18) crates/markview-layout/src/layout/table.rs:492— BlockContext::build_grid has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BlockContext::paragraph_bounded (cyclomatic 17) crates/markview-layout/src/layout/paragraph.rs:329— BlockContext::paragraph_bounded 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.
Lower::table (cognitive 128) crates/markview-webpage/src/lower.rs:792— Lower::table has cognitive complexity 128 (threshold 15). Drivers by points: if/else 22 (66 pts), loops 15 (43 pts), match/switch 5 (15 pts), boolean chains 4 (nesting depth added 82). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Lower::lower_block (cognitive 22) crates/markview-webpage/src/lower.rs:221— Lower::lower_block has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Lower::inline_element (cognitive 18) crates/markview-webpage/src/lower.rs:1083— Lower::inline_element has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, loops 1, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Painter::draw (cognitive 78) crates/markview-pdf/src/paint.rs:659— Painter::draw has cognitive complexity 78 (threshold 15). Drivers by points: if/else 30 (63 pts), loops 4 (10 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 40). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Painter::math (cognitive 38) crates/markview-pdf/src/paint.rs:915— Painter::math has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (31 pts), loops 2 (5 pts), match/switch 1 (2 pts) (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.
Painter::furniture (cognitive 28) crates/markview-pdf/src/paint.rs:465— Painter::furniture has cognitive complexity 28 (threshold 15). Drivers by points: if/else 3 (14 pts), loops 3 (7 pts), match/switch 2 (7 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.
Worker::with_services_and_parsed (cognitive 69) src/worker.rs:150— Worker::with_services_and_parsed has cognitive complexity 69 (threshold 15). Drivers by points: if/else 20 (50 pts), match/switch 3 (10 pts), boolean chains 8, loops 1 (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.
Worker::new (cognitive 22) src/app/search.rs:81— Worker::new has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Worker::submit (cognitive 21) src/app/preview/work.rs:231— Worker::submit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 2 (3 pts), loops 1 (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.
markview_document::visit::walk (cognitive 37) crates/markview-document/src/visit.rs:58— markview_document::visit::walk has cognitive complexity 37 (threshold 15). Drivers by points: loops 12 (29 pts), if/else 4 (7 pts), match/switch 1 (nesting depth added 20). 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.
markview_document::semantic_key (cognitive 29) crates/markview-document/src/lib.rs:985— markview_document::semantic_key has cognitive complexity 29 (threshold 15). Drivers by points: loops 9 (21 pts), if/else 4 (7 pts), match/switch 1 (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.
markview_document::visit::visit_blocks (cognitive 21) crates/markview-document/src/visit.rs:150— markview_document::visit::visit_blocks has cognitive complexity 21 (threshold 15). Drivers by points: loops 8 (20 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×3
Edited copy of a member (13 corresponding lines) crates/markview-layout/src/scene/draws.rs:514— crates/markview-layout/src/scene/draws.rs:514-528 | crates/markview-layout/src/scene/draws.rs:534-546 — 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) src/app/chrome/components.rs:1044— src/app/chrome/components.rs:1044-1056 | src/app/chrome/list.rs:143-155 — 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) fuzz/fuzzlib/src/highlight.rs:6— fuzz/fuzzlib/src/highlight.rs:6-18 | fuzz/fuzzlib/src/highlight_schedule.rs:66-78 — 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.
Duplicated block (14 lines × 3) crates/markview-document/src/index.rs:165— crates/markview-document/src/index.rs:165-178 | fuzz/fuzzlib/src/bin/webdump.rs:143-156 | fuzz/fuzzlib/src/webpage.rs:610-623 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (14 lines × 3) src/app/chrome/components.rs:1238— src/app/chrome/components.rs:1238-1251 | src/app/chrome/styles.rs:424-437 | src/app/font_panel/view.rs:704-717 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/chrome/components.rs:1238` 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 × 3) fuzz/fuzzlib/src/mutators.rs:392— fuzz/fuzzlib/src/mutators.rs:392-405 | fuzz/fuzzlib/src/mutators.rs:594-607 | fuzz/fuzzlib/src/mutators.rs:748-761 — 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 `fuzz/fuzzlib/src/mutators.rs:392` it does not close everything it opens, so those 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) crates/markview-layout/src/style/parse.rs:200— crates/markview-layout/src/style/parse.rs:200-204 | crates/markview-layout/src/style/parse.rs:253-257 — both copies are in the same file, so extract the 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 `crates/markview-layout/src/style/parse.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 (5 lines × 2) crates/markview-webpage/src/lower.rs:1778— crates/markview-webpage/src/lower.rs:1778-1782 | fuzz/fuzzlib/src/webpage.rs:1098-1102 — 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) src/app/launch.rs:207— src/app/launch.rs:207-211 | src/benchmark.rs:134-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
markview::images::diagram::resolve (cyclomatic 41) src/images/diagram.rs:101— markview::images::diagram::resolve has cyclomatic complexity 41 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
markview::fonts::report::merge_progress (cyclomatic 17) src/fonts/report.rs:213— markview::fonts::report::merge_progress 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.
Reader::child_block (cyclomatic 39) crates/markview-commonmark/src/parse.rs:1043— Reader::child_block has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Reader::inline_step (cyclomatic 25) crates/markview-commonmark/src/parse.rs:427— Reader::inline_step has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Painter::draw (cyclomatic 39) crates/markview-pdf/src/paint.rs:659— Painter::draw has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Painter::math (cyclomatic 16) crates/markview-pdf/src/paint.rs:915— Painter::math has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Renderer::draw (cyclomatic 37) crates/markview-render/src/paint.rs:128— Renderer::draw has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Renderer::prepare (cyclomatic 17) crates/markview-render/src/frame.rs:78— Renderer::prepare 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.
markview_document::visit::walk (cyclomatic 27) crates/markview-document/src/visit.rs:58— markview_document::visit::walk has cyclomatic complexity 27 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
markview_document::semantic_key (cyclomatic 23) crates/markview-document/src/lib.rs:985— markview_document::semantic_key has cyclomatic complexity 23 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
markview_commonmark::make::walk_fields (cyclomatic 22) crates/markview-commonmark/src/make.rs:196— markview_commonmark::make::walk_fields has cyclomatic complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
markview_commonmark::make::rebase_links (cyclomatic 18) crates/markview-commonmark/src/make.rs:409— markview_commonmark::make::rebase_links has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
BlockLayout::seal_scene (cyclomatic 17) crates/markview-layout/src/scene/flow.rs:356— BlockLayout::seal_scene has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
BlockLayout::resolve_flow (cyclomatic 17) crates/markview-layout/src/scene/flow.rs:619— BlockLayout::resolve_flow 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.
SourceIndex::scroll_anchors (cyclomatic 16) crates/markview-layout/src/source.rs:169— SourceIndex::scroll_anchors has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SourceIndex::visit (cyclomatic 16) crates/markview-layout/src/source.rs:392— SourceIndex::visit has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Repeated repair: scripts/generate_test_fonts.py scripts/generate_test_fonts.py:112— scripts/generate_test_fonts.py changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is generate_test_fonts.render_regional_fonts at line 112), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “test: expand rendering regression coverage”; “fix: pin fonts across all automated tests”; “fix: keep exported text complete and pin the fonts tests shape with”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- scripts/generate_test_fonts.py`: 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.
Repeated repair: crates/markview-pdf/src/image.rs crates/markview-pdf/src/image.rs:19— crates/markview-pdf/src/image.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is PreparedImage::new at line 19), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: use as_chunks to satisfy clippy in PDF image encoding”; “fix: compress PDF images with bounded loading and rayon”; “fix: recover poisoned mutexes in fonts, images, and worker state”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:58:37 +08:00' --until='2026-11-16 19:58:37 +08:00' --full-history --no-merges -- crates/markview-pdf/src/image.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.
TodoComment src/app/window.rs:115— // TODO: implement viewport zoom without changing the document layout. — 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 src/app/window.rs:464— // TODO: implement viewport zoom without changing the document layout. — 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.
Renderer::draw (cognitive 89) crates/markview-render/src/paint.rs:128— Renderer::draw has cognitive complexity 89 (threshold 15). Drivers by points: if/else 28 (68 pts), loops 5 (17 pts), match/switch 2 (4 pts) (nesting depth added 54). 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.
Renderer::prepare (cognitive 26) crates/markview-render/src/frame.rs:78— Renderer::prepare has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 7 (8 pts), match/switch 1 (3 pts), boolean chains 2 (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.
Reader::child_block (cognitive 60) crates/markview-commonmark/src/parse.rs:1043— Reader::child_block has cognitive complexity 60 (threshold 15). Drivers by points: if/else 16 (36 pts), match/switch 5 (14 pts), loops 2 (7 pts), boolean chains 3 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Reader::svg (cognitive 16) crates/markview-commonmark/src/parse.rs:788— Reader::svg has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MermaidStyle::overlay (cognitive 41) crates/markview-layout/src/style/types.rs:1343— MermaidStyle::overlay has cognitive complexity 41 (threshold 15). Drivers by points: if/else 41. 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.
MermaidStyle::validate (cognitive 17) crates/markview-layout/src/style/types.rs:1391— MermaidStyle::validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Block::images (cognitive 36) crates/markview-document/src/lib.rs:789— Block::images has cognitive complexity 36 (threshold 15). Drivers by points: loops 12 (28 pts), if/else 4 (7 pts), match/switch 1 (nesting depth added 19). Of this number, 32 points are the body's own statements and 4 belong to 2 function items inside it that branch. 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.
Block::for_each_code_block (cognitive 21) crates/markview-document/src/lib.rs:887— Block::for_each_code_block has cognitive complexity 21 (threshold 15). Drivers by points: loops 8 (20 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SourceIndex::visit (cognitive 36) crates/markview-layout/src/source.rs:392— SourceIndex::visit has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 4 (7 pts), boolean chains 1 (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.
SourceIndex::scroll_anchors (cognitive 23) crates/markview-layout/src/source.rs:169— SourceIndex::scroll_anchors has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 4, loops 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.
DisplayState::can_display (cognitive 35) src/state/display.rs:17— DisplayState::can_display has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (24 pts), boolean chains 6, loops 2 (5 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DisplayState::capture_images (cognitive 34) src/app/preview.rs:153— DisplayState::capture_images has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (31 pts), loops 2 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
xtask::complexity::exemption (cognitive 32) xtask/src/complexity.rs:249— xtask::complexity::exemption has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (27 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
xtask::coupling::check_baseline (cognitive 16) xtask/src/coupling.rs:757— xtask::coupling::check_baseline has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlockLayout::resolve_flow (cognitive 31) crates/markview-layout/src/scene/flow.rs:619— BlockLayout::resolve_flow has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 5 (8 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlockLayout::seal_scene (cognitive 29) crates/markview-layout/src/scene/flow.rs:356— BlockLayout::seal_scene has cognitive complexity 29 (threshold 15). Drivers by points: loops 11 (19 pts), if/else 5 (10 pts) (nesting depth added 13). Of this number, 27 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
Form::new (cognitive 31) src/app/chrome/components.rs:797— Form::new has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (27 pts), loops 2 (3 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.
Form::draw_rows (cognitive 31) src/app/chrome/components.rs:1143— Form::draw_rows has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 2, loops 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.
Images::prepare_sources (cognitive 29) src/images.rs:689— Images::prepare_sources has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (19 pts), boolean chains 5, match/switch 2 (4 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Images::prepare_blocks (cognitive 17) src/images.rs:563— Images::prepare_blocks has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 5 (8 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SpannedText::spans (cognitive 23) crates/markview-commonmark/src/rich.rs:278— SpannedText::spans has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (7 pts), loops 2 (3 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.
SpannedText::merged (cognitive 17) crates/markview-commonmark/src/rich.rs:90— SpannedText::merged has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SourceMap::validate (cognitive 22) crates/markview-document/src/source.rs:268— SourceMap::validate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SourceMap::semantic_to_source (cognitive 17) crates/markview-document/src/source.rs:176— SourceMap::semantic_to_source has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6, loops 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.
ButtonVisual::fill (cognitive 21) src/app/chrome/components.rs:436— ButtonVisual::fill has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 6 (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.
ButtonVisual::content (cognitive 19) src/app/chrome/components.rs:514— ButtonVisual::content has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 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.
markview_webpage::preserve_semantics (cognitive 20) crates/markview-webpage/src/lib.rs:346— markview_webpage::preserve_semantics has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, loops 2 (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.
markview_webpage::lower::apply_link (cognitive 20) crates/markview-webpage/src/lower.rs:1286— markview_webpage::lower::apply_link has cognitive complexity 20 (threshold 15). Drivers by points: loops 7 (14 pts), if/else 3 (5 pts), match/switch 1 (nesting depth added 9). Of this number, 15 points are the body's own statements and 5 belong to 3 function items inside it that branch. 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.
SettingsStore::encoded_settings (cognitive 20) src/settings/store.rs:388— SettingsStore::encoded_settings has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, loops 2, match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsStore::load (cognitive 17) src/settings/store.rs:156— SettingsStore::load has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 3 (8 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.
Chrome::buttons_for (cognitive 18) src/app/chrome.rs:422— Chrome::buttons_for has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 2). 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.
Chrome::draw_resource_feedback (cognitive 17) src/app/chrome.rs:1305— Chrome::draw_resource_feedback has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 7. 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.
Change-coupling hub: interaction.rs → controls.rs, icons.rs, preferences.rs, store.rs src/app/interaction.rs— `src/app/interaction.rs` changes together with 4 other files — `src/app/chrome/controls.rs`, `src/app/chrome/icons.rs`, `src/app/preferences.rs`, `src/settings/store.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: state.rs → icons.rs, preferences.rs, store.rs src/state.rs— `src/state.rs` changes together with 3 other files — `src/app/chrome/icons.rs`, `src/app/preferences.rs`, `src/settings/store.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change coupling: controls.rs ↔ preferences.rs src/app/chrome/controls.rs:1— `src/app/chrome/controls.rs` and `src/app/preferences.rs` change together 60% of the time (9 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 9 shared commits counted here, the most recent 3 are `b55a9821` feat: restore browsing sessions across launches; `e007a987` feat: reorganize settings and show restart hints; `186c8f8e` fix: move tab style to user settings and default to underline — run `git show` on any of them.
Change coupling: export.rs ↔ worker.rs src/export.rs:1— `src/export.rs` and `src/worker.rs` 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) 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 6 shared commits counted here, the most recent 3 are `428f78a8` feat: render raw markdown urls directly; `b7ff362c` feat: open and export standalone images; `3e0efdb5` feat: render obsidian wikilink image embeds — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) crates/markview-layout/src/text.rs:239— crates/markview-layout/src/text.rs:239-260 | crates/markview-layout/src/text.rs:266-287 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) fuzz/fuzz_targets/refdef.rs:307— fuzz/fuzz_targets/refdef.rs:307-329 | fuzz/fuzz_targets/refdef.rs:333-354 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) crates/markview-commonmark/src/incremental.rs:552— crates/markview-commonmark/src/incremental.rs:552-574 | fuzz/fuzzlib/src/seam.rs:628-648 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/markview-layout/src/style.rs:548— crates/markview-layout/src/style.rs:548-568 | crates/markview-layout/src/style/source.rs:43-90 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) crates/markview-layout/src/fonts/mod.rs:134— crates/markview-layout/src/fonts/mod.rs:134-147 | crates/markview-layout/src/fonts/mod.rs:156-170 — 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) fuzz/fuzzlib/src/mutators.rs:893— fuzz/fuzzlib/src/mutators.rs:893-906 | fuzz/fuzzlib/src/mutators.rs:915-928 — 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 (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) crates/markview-layout/src/layout/inline.rs:570— crates/markview-layout/src/layout/inline.rs:570-584 | crates/markview-layout/src/microtype.rs:504-523 — 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) src/app/tabs.rs:166— src/app/tabs.rs:166-182 | src/app/tabs.rs:191-205 — 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 (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) src/benchmark.rs:36— src/benchmark.rs:36-45 | src/latency.rs:57-70 — 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) crates/markview-layout/src/layout.rs:435— crates/markview-layout/src/layout.rs:435-444 | crates/markview-layout/src/layout.rs:450-459 — 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.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) src/app/folder.rs:1304— src/app/folder.rs:1304-1313 | src/app/folder.rs:1319-1327 — 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) crates/markview-pdf/src/paint.rs:358— crates/markview-pdf/src/paint.rs:358-366 | crates/markview-pdf/src/paint.rs:891-905 — 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 (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) crates/markview-image/src/decode.rs:407— crates/markview-image/src/decode.rs:407-423 | crates/markview-image/src/decode.rs:429-439 — 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) src/app/tabs.rs:347— src/app/tabs.rs:347-361 | src/app/tabs.rs:366-376 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) src/app/outline.rs:402— src/app/outline.rs:402-409 | src/app/outline.rs:415-422 — 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) crates/markview-commonmark/src/incremental.rs:603— crates/markview-commonmark/src/incremental.rs:603-610 | crates/markview-commonmark/src/incremental.rs:614-621 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) src/app/web_page.rs:6— src/app/web_page.rs:6-11 | src/fonts/download.rs:280-285 — 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) src/app/fonts_command.rs:496— src/app/fonts_command.rs:496-505 | src/export_cli.rs:66-71 — 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 (18 lines × 2) crates/markview-layout/src/text.rs:243— crates/markview-layout/src/text.rs:243-260 | crates/markview-layout/src/text.rs:270-287 — both copies are in the same file, so extract the 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 `crates/markview-layout/src/text.rs:243` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) fuzz/fuzzlib/src/seam.rs:114— fuzz/fuzzlib/src/seam.rs:114-131 | fuzz/fuzzlib/src/seam.rs:174-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fuzz/fuzzlib/src/seam.rs:114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/markview-web/src/api.rs:500— crates/markview-web/src/api.rs:500-513 | crates/markview-web/src/api.rs:1386-1399 — both copies are in the same file, so extract the 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) xtask/src/complexity.rs:184— xtask/src/complexity.rs:184-197 | xtask/src/complexity.rs:393-406 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) src/benchmark.rs:283— src/benchmark.rs:283-294 | src/latency.rs:664-675 — 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 `src/benchmark.rs:283` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) fuzz/fuzzlib/src/oracle.rs:338— fuzz/fuzzlib/src/oracle.rs:338-349 | fuzz/fuzzlib/src/oracle.rs:355-366 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fuzz/fuzzlib/src/oracle.rs:338` 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) src/app/chrome.rs:1100— src/app/chrome.rs:1100-1112 | src/app/chrome/folder.rs:178-188 — 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 `src/app/chrome.rs:1100` it does not close everything it opens, so those 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) fuzz/fuzzlib/src/web_layout.rs:50— fuzz/fuzzlib/src/web_layout.rs:50-62 | fuzz/fuzzlib/src/web_layout.rs:197-207 — both copies are in the same file, so extract the 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 `fuzz/fuzzlib/src/web_layout.rs:50` 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 (59 lines × 2) scripts/webpage_baseline.rs:122— scripts/webpage_baseline.rs:122-180 | scripts/webpage_baseline_rss.rs:66-124 — before extracting anything, compare `scripts/webpage_baseline.rs` and `scripts/webpage_baseline_rss.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (59 lines × 2) scripts/webpage_baseline.rs:184— scripts/webpage_baseline.rs:184-242 | scripts/webpage_baseline_rss.rs:128-186 — before extracting anything, compare `scripts/webpage_baseline.rs` and `scripts/webpage_baseline_rss.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Low cohesion: Row (LCOM4 4) src/app/chrome/components.rs:652— Row's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Check (LCOM4 4) xtask/src/complexity.rs:357— Check's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Unfinished branch — a todo!() / unimplemented!() arm in a real function crates/markview-layout/src/style/types.rs:1252— `validate` does real work, but one of its branches is `bail!` with a "not implemented" message — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled.
Unfinished branch — a todo!() / unimplemented!() arm in a real function src/export/config.rs:234— `validate` does real work, but one of its branches is `bail!` with a "not implemented" message — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled.
Skeleton type — most members are unfinished crates/markview-platform/src/dm.rs:494— `impl DirectManipulation` has 4 unfinished methods out of 7 — a scaffolded type that was never implemented.
Skeleton type — most members are unfinished crates/markview-platform/src/window.rs:26— `impl NativeFrame` has 2 unfinished methods out of 4 — a scaffolded type that was never implemented.
Rule::overlay (cyclomatic 53) crates/markview-layout/src/style/types.rs:937— Rule::overlay has cyclomatic complexity 53 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
extension.activate.open (cyclomatic 44) web/app/vsc-ext/vscode/src/preview/extension.ts:20— extension.activate.open has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 3 of the 44 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 135, publish, a function literal at line 210, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MermaidStyle::overlay (cyclomatic 42) crates/markview-layout/src/style/types.rs:1343— MermaidStyle::overlay has cyclomatic complexity 42 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Model::update (cyclomatic 34) src/app/settings_panel.rs:152— Model::update has cyclomatic complexity 34 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CanvasReader.bindInput (cyclomatic 33) web/packages/markview/src/reader.ts:214— CanvasReader.bindInput has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 265, 259, 235, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Worker::with_services_and_parsed (cyclomatic 31) src/worker.rs:150— Worker::with_services_and_parsed 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.
webview.update (cyclomatic 29) web/app/vsc-ext/vscode/src/preview/webview.ts:63— webview.update has cyclomatic complexity 29 (threshold 15). Of this number, 24 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
build.main (cyclomatic 28) REDACTED:42— build.main has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Block::images (cyclomatic 26) crates/markview-document/src/lib.rs:789— Block::images has cyclomatic complexity 26 (threshold 15). Of this number, 23 points are the body's own statements and 3 belong to 2 function items inside it that branch. 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.
MarkviewActivity.receiveResult (cyclomatic 25) android/java/io/github/szdytom/markview/MarkviewActivity.java:265— MarkviewActivity.receiveResult 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.
markview_platform::window_frame::subclass (cyclomatic 24) crates/markview-platform/src/window_frame.rs:152— markview_platform::window_frame::subclass has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
markview_webpage::lower::apply_link (cyclomatic 19) crates/markview-webpage/src/lower.rs:1286— markview_webpage::lower::apply_link has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to 3 function items inside it that branch. 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.
DisplayState::can_display (cyclomatic 18) src/state/display.rs:17— DisplayState::can_display has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FontPanel.handle (cyclomatic 18) web/app/vsc-ext/vscode/src/shared/font-panel.ts:113— FontPanel.handle has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 3 function literals inside it that branch. 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.
LayoutSnapshot::geometry_rebase_selection (cyclomatic 17) crates/markview-layout/src/text/selection.rs:24— LayoutSnapshot::geometry_rebase_selection 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.
ResourceEvents.replace (cyclomatic 17) web/packages/markview/src/resources.ts:67— ResourceEvents.replace has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 79, current, a function literal at line 101, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Viewer.#frame (cyclomatic 17) web/packages/markview/src/viewer.ts:247— Viewer.#frame has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SearchIndex::find_cancellable (cyclomatic 16) crates/markview-layout/src/search.rs:86— SearchIndex::find_cancellable has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
process.runNative (cyclomatic 16) web/app/vsc-ext/vscode/src/shared/process.ts:8— process.runNative has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 59, 21, 37, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
extension.activate.open (cognitive 53) web/app/vsc-ext/vscode/src/preview/extension.ts:20— extension.activate.open has cognitive complexity 53 (threshold 15). Drivers by points: if/else 27 (37 pts), boolean chains 9, ternaries 4, error handling 2 (3 pts) (nesting depth added 11). Most of this is not in the body itself: 2 of the 53 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 135, publish, a function literal at line 235, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Rule::overlay (cognitive 52) crates/markview-layout/src/style/types.rs:937— Rule::overlay has cognitive complexity 52 (threshold 15). Drivers by points: if/else 52. 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.
CanvasReader.bindInput (cognitive 47) web/packages/markview/src/reader.ts:214— CanvasReader.bindInput has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (20 pts), ternaries 8 (19 pts), boolean chains 8 (nesting depth added 14). None of this is in the body itself: all 47 points belong to 8 function literals inside it that branch (lines 265, 259, 235, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MarkviewActivity.receiveResult (cognitive 40) android/java/io/github/szdytom/markview/MarkviewActivity.java:265— MarkviewActivity.receiveResult has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (20 pts), ternaries 3 (7 pts), boolean chains 5, loops 2 (5 pts), error handling 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build.main (cognitive 38) REDACTED:42— build.main has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 9 (13 pts), loops 5 (6 pts), boolean chains 4 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SearchIndex::find_cancellable (cognitive 35) crates/markview-layout/src/search.rs:86— SearchIndex::find_cancellable has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (27 pts), loops 3 (7 pts), boolean chains 1 (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.
ContainerStack::consume (cognitive 31) crates/markview-commonmark/src/container.rs:262— ContainerStack::consume has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (28 pts), match/switch 1 (2 pts), loops 1 (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.
ImageTextures::prewarm (cognitive 31) crates/markview-render/src/images.rs:241— ImageTextures::prewarm has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (24 pts), loops 3 (6 pts), boolean chains 1 (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.
ThreadExecutor::try_submit (cognitive 28) crates/markview-layout/src/background.rs:108— ThreadExecutor::try_submit has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (13 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
webview.update (cognitive 28) web/app/vsc-ext/vscode/src/preview/webview.ts:63— webview.update has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 7, ternaries 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.
FileWatch::observe (cognitive 25) src/watch.rs:62— FileWatch::observe has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 3, loops 1 (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.
FontIndex.scan (cognitive 25) web/app/vsc-ext/vscode/src/shared/fonts.ts:35— FontIndex.scan has cognitive complexity 25 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 3 (8 pts), error handling 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (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.
Producer::remap_block (cognitive 22) crates/markview-commonmark/src/make.rs:100— Producer::remap_block has cognitive complexity 22 (threshold 15). Drivers by points: loops 8 (20 pts), 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.
Tabs::restore_session (cognitive 22) src/app/session.rs:548— Tabs::restore_session has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 1 (2 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.
TemplateSettings.resolve (cognitive 22) web/app/vsc-ext/vscode/src/shared/template-settings.ts:61— TemplateSettings.resolve has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScrollPhysics::advance_momentum (cognitive 21) crates/markview-interaction/src/scroll.rs:475— ScrollPhysics::advance_momentum has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 3 (nesting depth added 2). 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.
TextInput::draw (cognitive 20) crates/markview-layout/src/text_input.rs:400— TextInput::draw has cognitive complexity 20 (threshold 15). Drivers by points: loops 6 (11 pts), if/else 6 (8 pts), boolean chains 1 (nesting depth added 7). 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.
State::refresh (cognitive 20) src/app/folder/observe.rs:556— State::refresh has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (5 pts), boolean chains 4 (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.
Tree::patch (cognitive 20) src/app/folder.rs:264— Tree::patch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MarkviewActivity.receive (cognitive 20) android/java/io/github/szdytom/markview/MarkviewActivity.java:184— MarkviewActivity.receive has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markview_image::decode::decode_bitmap (cognitive 19) crates/markview-image/src/decode.rs:262— markview_image::decode::decode_bitmap has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (14 pts), if/else 3 (4 pts), boolean chains 1 (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.
ParagraphLayout::reshape_to_fit (cognitive 19) crates/markview-layout/src/layout/paragraph.rs:111— ParagraphLayout::reshape_to_fit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DrawBuffer::from_paint_iter (cognitive 19) crates/markview-layout/src/scene/draws.rs:306— DrawBuffer::from_paint_iter has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cache::evict (cognitive 19) src/images/cache.rs:301— Cache::evict has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MarkviewActivity.showError (cognitive 19) android/java/io/github/szdytom/markview/MarkviewActivity.java:482— MarkviewActivity.showError has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PreviewScrollSync.frame (cognitive 19) web/app/vsc-ext/vscode/src/preview/scroll-sync-webview.ts:142— PreviewScrollSync.frame has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (7 pts), boolean chains 1 (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.
PlacedBlock::flat_layout (cognitive 17) crates/markview-layout/src/scene/flow.rs:830— PlacedBlock::flat_layout has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 5 (8 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Geometry::decorated_base (cognitive 17) crates/markview-render/src/geometry.rs:51— Geometry::decorated_base has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Model::update (cognitive 17) src/app/settings_panel.rs:152— Model::update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, match/switch 2 (nesting depth added 5). 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.
WheelGesture::feed (cognitive 17) src/state.rs:414— WheelGesture::feed has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 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.
process.runNative (cognitive 17) web/app/vsc-ext/vscode/src/shared/process.ts:8— process.runNative has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, ternaries 5 (6 pts), boolean chains 3, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 59, 68, 21, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Editor.#scrollMap (cognitive 16) web/packages/editor/src/index.ts:302— Editor.#scrollMap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyFunctions: markview_commonmark::incremental crates/markview-commonmark/src/incremental.rs:22— TooManyFunctions — 38 free functions. The bar is 30 free functions; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) crates/markview-webpage/src/lower.rs:610— crates/markview-webpage/src/lower.rs:610-644 | crates/markview-webpage/src/lower.rs:650-681 — 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 (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) crates/markview-commonmark/src/html.rs:366— crates/markview-commonmark/src/html.rs:366-406 | crates/markview-commonmark/src/html.rs:743-785 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) src/fonts/download.rs:453— src/fonts/download.rs:453-495 | src/fonts/download.rs:503-553 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 42+ corresponding lines) · ×1
Edited copies of one member (3 members, 42+ corresponding lines) crates/markview-commonmark/src/make.rs:104— crates/markview-commonmark/src/make.rs:104-145 | crates/markview-document/src/lib.rs:890-931 | crates/markview-document/src/visit.rs:150-192 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) crates/markview-document/src/index.rs:163— crates/markview-document/src/index.rs:163-184 | fuzz/fuzzlib/src/bin/webdump.rs:141-159 | fuzz/fuzzlib/src/webpage.rs:608-629 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) crates/markview-render/src/raster.rs:135— crates/markview-render/src/raster.rs:135-174 | crates/markview-render/src/raster/color.rs:34-77 — 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 (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) src/app/start.rs:384— src/app/start.rs:384-401 | src/app/start.rs:402-426 — 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 copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) crates/markview-layout/src/scene/draws.rs:113— crates/markview-layout/src/scene/draws.rs:113-131 | crates/markview-layout/src/scene/draws.rs:136-158 — 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, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) crates/markview-layout/src/style/parse.rs:166— crates/markview-layout/src/style/parse.rs:166-181 | crates/markview-layout/src/style/parse.rs:338-351 | crates/markview-layout/src/style/parse.rs:355-370 | crates/markview-layout/src/style/parse.rs:374-389 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) crates/markview-webpage/src/metadata.rs:78— crates/markview-webpage/src/metadata.rs:78-93 | fuzz/fuzzlib/src/seam.rs:581-596 — 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) · ×1
Edited copy of a member (17 corresponding lines) src/app/chrome/styles.rs:109— src/app/chrome/styles.rs:109-125 | src/app/font_panel/view.rs:86-106 — 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 (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) crates/markview-platform/src/lib.rs:254— crates/markview-platform/src/lib.rs:254-268 | crates/markview-platform/src/lib.rs:281-292 — 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 copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) src/app/search.rs:197— src/app/search.rs:197-210 | src/app/start.rs:287-296 | src/worker.rs:646-660 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) src/fonts/mod.rs:48— src/fonts/mod.rs:48-51 | src/images/cache.rs:182-185 | src/stylesheet.rs:42-45 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) crates/markview-document/src/lib.rs:697— crates/markview-document/src/lib.rs:697-701 | src/app/widgets.rs:76-80 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (24–27 lines × 2) crates/markview-pdf/src/paint.rs:488— crates/markview-pdf/src/paint.rs:488-514 | crates/markview-pdf/src/paint.rs:1165-1188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/markview-pdf/src/paint.rs:515` calls `set_fill`, `Some`, `fill` and `crates/markview-pdf/src/paint.rs:1189` 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 (19 lines × 2) crates/markview-webpage/src/lower.rs:620— crates/markview-webpage/src/lower.rs:620-638 | crates/markview-webpage/src/lower.rs:661-679 — both copies are in the same file, so extract the 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 `crates/markview-webpage/src/lower.rs:620` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) crates/markview-commonmark/src/parse.rs:1059— crates/markview-commonmark/src/parse.rs:1059-1071 | crates/markview-commonmark/src/parse.rs:1649-1662 — both copies are in the same file, so extract the 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 `crates/markview-commonmark/src/parse.rs:1059` 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 (10–12 lines × 2) crates/markview-webpage/src/lower.rs:901— crates/markview-webpage/src/lower.rs:901-910 | fuzz/fuzzlib/src/webpage.rs:917-928 — 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 `crates/markview-webpage/src/lower.rs:901` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 3) scripts/webpage_baseline.rs:67— scripts/webpage_baseline.rs:67-77 | scripts/webpage_baseline_rss.rs:11-21 | src/paste.rs:10-19 — before extracting anything, compare `scripts/webpage_baseline.rs` and `scripts/webpage_baseline_rss.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8–11 lines × 2) crates/markview-layout/src/layout/inline.rs:571— crates/markview-layout/src/layout/inline.rs:571-578 | crates/markview-layout/src/microtype.rs:505-515 — 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 `crates/markview-layout/src/layout/inline.rs:571` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–9 lines × 2) crates/markview-layout/src/paginate.rs:198— crates/markview-layout/src/paginate.rs:198-204 | crates/markview-pdf/src/paint.rs:1313-1321 — 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 `crates/markview-layout/src/paginate.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.
D4 · Code Duplication· Near-duplicate member family (3 members, 38 shared lines) · ×1
Near-duplicate member family (3 members, 38 shared lines) fuzz/fuzzlib/src/mutators.rs:391— fuzz/fuzzlib/src/mutators.rs:391-462 | fuzz/fuzzlib/src/mutators.rs:593-648 | fuzz/fuzzlib/src/mutators.rs:747-810 — These 3 members are variants of one another: a block of 38 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) fuzz/fuzzlib/src/web_layout.rs:39— fuzz/fuzzlib/src/web_layout.rs:39-74 | fuzz/fuzzlib/src/web_layout.rs:185-220 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) fuzz/fuzzlib/src/behavior.rs:8— fuzz/fuzzlib/src/behavior.rs:8-10 | fuzz/fuzzlib/src/oracle.rs:561-563 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (39 lines × 2) scripts/webpage_baseline.rs:80— scripts/webpage_baseline.rs:80-118 | scripts/webpage_baseline_rss.rs:24-62 — before extracting anything, compare `scripts/webpage_baseline.rs` and `scripts/webpage_baseline_rss.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16–18 lines × 2) fuzz/fuzzlib/src/seam.rs:776— fuzz/fuzzlib/src/seam.rs:776-793 | fuzz/fuzzlib/src/seam.rs:873-888 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `fuzz/fuzzlib/src/seam.rs:776` it does not close everything it opens, so those 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–17 lines × 3) fuzz/fuzzlib/src/mutators.rs:446— fuzz/fuzzlib/src/mutators.rs:446-462 | fuzz/fuzzlib/src/mutators.rs:635-648 | fuzz/fuzzlib/src/mutators.rs:797-810 — 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 `fuzz/fuzzlib/src/mutators.rs:446` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–13 lines × 3) fuzz/fuzz_targets/details_structure.rs:55— fuzz/fuzz_targets/details_structure.rs:55-67 | fuzz/fuzz_targets/prefix.rs:22-31 | fuzz/fuzz_targets/sourcepos_content.rs:109-118 — 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.
Duplicated block (13 lines × 2) fuzz/fuzzlib/src/bin/webdump.rs:21— fuzz/fuzzlib/src/bin/webdump.rs:21-33 | fuzz/fuzzlib/src/bin/webdump.rs:45-57 — both copies are in the same file, so extract the 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 `fuzz/fuzzlib/src/bin/webdump.rs:21` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–12 lines × 3) fuzz/fuzzlib/src/mutators.rs:413— fuzz/fuzzlib/src/mutators.rs:413-424 | fuzz/fuzzlib/src/mutators.rs:616-625 | fuzz/fuzzlib/src/mutators.rs:764-775 — 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 `fuzz/fuzzlib/src/mutators.rs:413` 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–8 lines × 2) fuzz/fuzzlib/src/reading.rs:228— fuzz/fuzzlib/src/reading.rs:228-235 | fuzz/fuzzlib/src/reading.rs:343-348 — both copies are in the same file, so extract the 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 `fuzz/fuzzlib/src/reading.rs:228` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 5) fuzz/fuzzlib/src/bin/mathprobe.rs:119— fuzz/fuzzlib/src/bin/mathprobe.rs:119-123 | fuzz/fuzzlib/src/bin/mathprobe.rs:126-130 | fuzz/fuzzlib/src/bin/mathprobe.rs:133-137 | fuzz/fuzzlib/src/bin/mathprobe.rs:184-188 | fuzz/fuzzlib/src/bin/mathprobe.rs:191-195 — 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 `fuzz/fuzzlib/src/bin/mathprobe.rs:119` 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.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the node:test suite in web/app/vsc-ext/ ran and not one test passed (✘ [ERROR] Could not resolve "../wasm/markview_web.js"), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
Duplicated block (12 lines × 2 locations) REDACTED:112— REDACTED:112 · REDACTED:23 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (5 matched lines × 2 locations) · ×1
Duplicated block with local edits (5 matched lines × 2 locations) web/packages/fonts/src/index.ts:94— web/packages/fonts/src/index.ts:94 · web/packages/markview/src/fonts.ts:10 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Complex function decodePng (cyclomatic 26, cognitive 42) web/tests/png.mjs:7— decodePng has cyclomatic complexity 26 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function #frame (cyclomatic 18, cognitive 17) web/packages/markview/src/viewer.ts:247— #frame has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 21) web/packages/markview/src/reader.ts:265— (anonymous) has cyclomatic complexity 14 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function #scrollMap (cyclomatic 12, cognitive 16) web/packages/editor/src/index.ts:302— #scrollMap has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· web/packages/editor/src/index.ts · ×1
web/packages/editor/src/index.ts: 521 lines of code web/packages/editor/src/index.ts:1— web/packages/editor/src/index.ts has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
X18 · Disposal-pattern correctness· Raw handle taken from an owned value and never reclaimed · ×1
Raw handle taken from an owned value and never reclaimed crates/markview-platform/src/icon.rs:56— `image.into_raw()` (line 56) gives up ownership in exchange for a raw handle — the value's `Drop` will no longer run — and nothing in the crate's code ever reclaims a `image` from a raw pointer (`image::from_raw`). The memory or descriptor stays allocated until the process ends, once per call. Pair the hand-out with its reclaim (a `free` function that rebuilds the owner with `from_raw` and drops it), or keep the owning value.
X2 · Cancellation propagation· Async function without AbortSignal · ×1
Async function without AbortSignal: loadFontSources web/packages/markview/src/fonts.ts:5— `loadFontSources` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Duplicated predicate crates/markview-pdf/src/paint.rs:892— `color.r == 0.0 && color.g == 0.0 && color.b == 0.0` appears character-identically in 2 files — crates/markview-pdf/src/paint.rs, crates/markview-render/src/paint.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 crates/markview-layout/src/layout/inline.rs:574— `cursor < spans.len() && spans[cursor].range.end <= cluster.range.start` appears character-identically in 2 files — crates/markview-layout/src/layout/inline.rs, crates/markview-layout/src/microtype.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 src/app/search.rs:95— `inbox.pending.is_none() && !inbox.stopped && !inbox.release` appears character-identically in 2 files — src/app/search.rs, src/worker.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 crates/markview-layout/src/layout/paragraph.rs:140— `line.units.end > line.units.start && units[line.units.end - 1].discard` appears character-identically in 2 files — crates/markview-layout/src/layout/paragraph.rs, crates/markview-layout/src/layout/paragraph/tests.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 src/app/preview/input.rs:198— `modifiers.control_key() || modifiers.meta_key()` appears character-identically in 2 files — src/app/preview/input.rs, src/app/window.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 src/app/chrome/styles.rs:859— `panel.contains(b.rect.x, b.rect.y) && panel.contains(b.rect.x + b.rect.w, b.rect.y + b.rect.h)` appears character-identically in 2 files — src/app/chrome/styles.rs, src/app/font_panel/view.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 src/app/chrome/golden.rs:24— `renderer.adapter_name.starts_with("llvmpipe") && renderer.adapter_name.ends_with("(Vulkan, Cpu)")` appears character-identically in 4 files — src/app/chrome/golden.rs, src/app/chrome/tabs/tests.rs, src/app/search/tests.rs, src/images/golden.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 src/app/folder.rs:513— `self.animation.is_some() || self.rows.animating()` appears character-identically in 2 files — src/app/folder.rs, src/app/outline.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 src/app/android.rs:87— `self.folder.open || self.phone_folder_open()` appears character-identically in 2 files — src/app/android.rs, src/app/folder.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 src/app/gestures.rs:213— `self.interaction.overlays.modal_open() || self.interaction.overlays.quick_open.open()` appears character-identically in 2 files — src/app/gestures.rs, src/app/pointer.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 src/app/animation.rs:194— `self.interaction.pointer.drag().is_some() && self.interaction.pointer.dragged()` appears character-identically in 3 files — src/app/animation.rs, src/app/gestures.rs, src/app/interaction.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 src/app/gestures.rs:161— `self.pointer_in_outline() || self.pointer_in_folder()` appears character-identically in 2 files — src/app/gestures.rs, src/app/preview.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 src/app/start.rs:565— `self.readers.session.path.is_some() || !self.readers.session.display.snapshot.blocks.is_empty()` appears character-identically in 2 files — src/app/start.rs, src/app/text_input.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 src/app/export.rs:1182— `text.contains("Visible") && text.contains("%%CODEKEEP%%")` appears character-identically in 2 files — src/app/export.rs, src/export/tests.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 scripts/webpage_baseline_rss.rs:12— `text.is_empty() || text.len() > crate::file::MAX_FILE_BYTES as usize` appears character-identically in 2 files — scripts/webpage_baseline_rss.rs, src/paste.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.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×2
Projects may be oversized for their cohesion Cargo.toml:1— `(repository root)` (90176 LoC, 182 module-visible types across 15 directories) overshoots its size bounds. 2 of 26 build unit(s) (Cargo, npm) overshoot their size bounds, lowering Project Cohesion to 8.5/10. 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.
Projects may be oversized for their cohesion crates/markview-layout/Cargo.toml:1— `crates/markview-layout` (32604 LoC, 163 module-visible types across 11 directories) overshoots its size bounds. 2 of 26 build unit(s) (Cargo, npm) overshoot their size bounds, lowering Project Cohesion to 8.5/10. 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.
Silent fallback default on Err crates/markview-pdf/src/text.rs:95— `variation_settings` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err src/fonts/catalog.rs:53— `describe` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
No ADRs found Cargo.toml:239— 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 `Cargo.toml` makes this repository a deployable product (line 239).
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 4/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `fuzz/fuzzlib`, `web`, `xtask`.
No dependency-update automation web/app/vsc-ext/package.json:13— `web/app/vsc-ext/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 1/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Outdated: clap — `clap` is locked at 4.6.7 but 4.6.8 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: comrak — `comrak` is locked at 1.0.0-rc.2 but 1.0.0 is the current stable release on crates.io, and it already satisfies the `"=1.0.0-rc.2"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p comrak` and commit the updated REDACTED.
Outdated: wgpu — `wgpu` is locked at 30.0.1 but 30.0.2 is the current stable release on crates.io, and it already satisfies the `"30.0.1"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wgpu` and commit the updated REDACTED.
Outdated: zip — `zip` is locked at 9.5.1 but 9.6.1 is the current stable release on crates.io, and it already satisfies the `"9"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zip` and commit the updated REDACTED.
Outdated: zstd — `zstd` is locked at 0.14.3 but 0.14.4 is the current stable release on crates.io, and it already satisfies the `"0.14"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zstd` and commit the updated REDACTED.
doc comments repeat the names web/packages/markview/src/markview.ts:182— 0 of 0 documented parameters and 1 of 140 summaries in `@markview/viewer` only repeat the member or parameter name (e.g. "Clears the selection." for `clearSelection`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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.
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 01a1e82d-69e3-7948-afa5-dfb7ec37ae50 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 141 · Warnings: 646 · Recommendations: 27 · Info: 6 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 06:24 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.