Public report of mermaid-js/mermaid, published 26 October 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.10.5). Watchdog 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, 26 October 2026, 11:40 UTC · Survey ID cd_ae656c9c520045168c7e27d7bd400b23
mermaid-js/mermaid
Measured 26 October 2026, 11:38 UTC, at code version f784532
Regression: 1 dimension fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskDown 5 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 105,362 lines of product code in 7 projects, tests not counted · Estimated rebuild effort: about 1.2 person-years · Weakest lens: Accessibility, 41
Findings by how serious they are
94 critical1091 serious204 minor
7 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 11:38 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 Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸
80of 80 dimensions measured by tools.
1349of 1389 findings point to an exact file and line, so you can open each one in the code. The other 40 concern the repository as a whole, such as missing documentation.
80dimensions across 7 lenses, read from 105,362 lines of product code in 7 projects.
mermaid-js/mermaid is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 51 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 41, is the weakest lens and counts most in the score. The best first steps are structuring the pages and automating accessibility checks, each worth about 4 points. Raising Accessibility to 70 would lift the score to about 59.
Sixty-five known security holes in the packages the code depends on can be used by attackers. Four passwords or keys in the code's history and one in the code are open to anyone who can read the repository, and four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages, replacing each exposed password or key and pinning each tool to an exact version would close these risks. Setting a waiting period for automatic updates would fix the three automatic dependency updates that take new releases at once, and limiting each secret to its own step would deal with the two secrets exposed to more of the pipeline than needed. The four form fields without a label need a label.
The product code is 105,362 lines, about €170,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
God Classes · FunctionTooLong: layoutCore.layoutContainer packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts
Test Quality · Skipped test: markdownToLines - No auto wrapping packages/mermaid/src/rendering-util/handle-markdown-text.spec.ts
Test Quality · Skipped test: continues reroute scanning against current edge points after each fix packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/__tests__/postProcessing.spec.ts
Test Quality · Skipped test: should handle if statements packages/mermaid/src/diagrams/state/stateDiagram.spec.js
Test Quality · Skipped test: should reset a branch packages/mermaid/src/diagrams/git/gitGraph.spec.ts
Test Quality · Skipped test: reset can take an argument packages/mermaid/src/diagrams/git/gitGraph.spec.ts
Test Quality · Skipped test: should handle fast forwardable merges packages/mermaid/src/diagrams/git/gitGraph.spec.ts
Test Quality · Skipped test: should handle ff merge when history walk has two parents (merge commit) packages/mermaid/src/diagrams/git/gitGraph.spec.ts
Test Quality · Skipped test: it should handle huge diagrams packages/mermaid/src/diagrams/flowchart/parser/flow-huge.spec.js
Test Quality · Skipped test: should be possible to use @ syntax to add labels with trail spaces packages/mermaid/src/diagrams/flowchart/parser/flow-node-data.spec.js
Test Quality · Skipped test: should handle subgraph without id and space in title packages/mermaid/src/diagrams/flowchart/parser/subgraph.spec.js
Test Quality · Skipped test: [skipped test] can contain àáâäæãåā packages/mermaid/src/diagrams/er/parser/erDiagram.spec.js
Test Quality · Skipped test: should handle a leading newline packages/mermaid/src/diagrams/class/classDiagram.spec.ts
Test Quality · Skipped test: should handle arrowMarkerAbsolute explicitly set to "false" as false e2e/other/pr-check/configuration.spec.js
Test Quality · Skipped test: (unnamed test) e2e/other/pr-check/dev-explorer-compare.spec.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs packages/mermaid/src/logger.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs packages/mermaid/src/logger.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs packages/mermaid/src/logger.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs packages/mermaid/src/logger.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs packages/mermaid/src/logger.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs packages/mermaid/src/logger.ts
Incompleteness & stubs · Both branches are identical — the condition decides nothing packages/mermaid/src/rendering-util/rendering-elements/clusters.js
Incompleteness & stubs · Both branches are identical — the condition decides nothing packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts
Incompleteness & stubs · Both branches are identical — the condition decides nothing packages/mermaid/src/rendering-util/rendering-elements/shapes/trapezoid.ts
Incompleteness & stubs · Both branches are identical — the condition decides nothing packages/mermaid/src/utils.ts
Visual & motion safety · Focus outline removed in CSS without a :focus replacement packages/mermaid/src/docs/.vitepress/theme/Mermaid.vue
Visual & motion safety · Focus outline removed in CSS without a :focus replacement .esbuild/dev-explorer/public/styles.css
Visual & motion safety · Animation without a prefers-reduced-motion guard packages/mermaid-local-editor/static/styles.css
Visual & motion safety · Animation without a prefers-reduced-motion guard packages/mermaid/src/docs/.vitepress/theme/Tooltip.vue
Visual & motion safety · Animation without a prefers-reduced-motion guard packages/mermaid/src/docs/.vitepress/theme/Tooltip.vue
Visual & motion safety · Animation without a prefers-reduced-motion guard .esbuild/dev-explorer/public/styles.css
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 512 findings
These 512 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.
€56,000 to €280,000, for 926 to 2,939 hours of work, about 1.2 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 51. 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: 105,362 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: Watchdog prices 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
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 4 points · Medium effort · Page structure
2
Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Raises the score by about 4 points · Medium effort · A11y enforcement
3
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Raises the score by about 4 points · Medium effort · Forms & labels
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Files that change often carry extra risk · Combined risk
3 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (40 files) · Code Coverage (82 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: REDACTED, tiltedCylinder.ts and cylinder.ts
What to do: Add tests to these files and have a second person review every change to them, starting with REDACTED, tiltedCylinder.ts and cylinder.ts.
Where the investment is most exposed · Value at risk
This code would cost about €170,000 to build again, about 1.2 person-years of work. Its weakest lens is Accessibility, at 41 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.7 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 8% to 19% on every change. The history of the code shows how much it changes: about 132,752 lines over the last 90 days, which is about 538,383 lines a year. At that pace, the extra work comes to an estimated 112.2 to 673 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
318 modules, with 354 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 278 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.
mermaid.src.diagram-api.types uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagram-api.types, while a change to mermaid.src.diagram-api.types can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagram-api.types uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.cynefin uses mermaid.src.Diagram, so a change to mermaid.src.Diagram can break mermaid.src.diagrams.cynefin, while a change to mermaid.src.diagrams.cynefin can't break mermaid.src.Diagram.
Position
Below the diagonal: mermaid.src.diagrams.cynefin uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.cynefin uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagrams.cynefin, while a change to mermaid.src.diagrams.cynefin can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagrams.cynefin uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.sequence.types uses mermaid.src.rendering-util.layout-algorithms.elk.render, so a change to mermaid.src.rendering-util.layout-algorithms.elk.render can break mermaid.src.diagrams.sequence.types, while a change to mermaid.src.diagrams.sequence.types can't break mermaid.src.rendering-util.layout-algorithms.elk.render.
Position
Below the diagonal: mermaid.src.diagrams.sequence.types uses a module listed above it, which is the healthy direction.
mermaid.src.types uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.types, while a change to mermaid.src.types can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.types uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.agentflow.agentflowDb uses mermaid.src.diagrams.requirement.types, so a change to mermaid.src.diagrams.requirement.types can break mermaid.src.diagrams.agentflow.agentflowDb, while a change to mermaid.src.diagrams.agentflow.agentflowDb can't break mermaid.src.diagrams.requirement.types.
Position
Below the diagonal: mermaid.src.diagrams.agentflow.agentflowDb uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.agentflow.agentflowDb uses mermaid.src.diagram-api.types, so a change to mermaid.src.diagram-api.types can break mermaid.src.diagrams.agentflow.agentflowDb, while a change to mermaid.src.diagrams.agentflow.agentflowDb can't break mermaid.src.diagram-api.types.
Position
Below the diagonal: mermaid.src.diagrams.agentflow.agentflowDb uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.state.stateDb uses mermaid.src.diagrams.requirement.types, so a change to mermaid.src.diagrams.requirement.types can break mermaid.src.diagrams.state.stateDb, while a change to mermaid.src.diagrams.state.stateDb can't break mermaid.src.diagrams.requirement.types.
Position
Below the diagonal: mermaid.src.diagrams.state.stateDb uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.state.stateDb uses mermaid.src.diagrams.sequence.types, so a change to mermaid.src.diagrams.sequence.types can break mermaid.src.diagrams.state.stateDb, while a change to mermaid.src.diagrams.state.stateDb can't break mermaid.src.diagrams.sequence.types.
Position
Below the diagonal: mermaid.src.diagrams.state.stateDb uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.usecaseTypes uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagrams.usecase.usecaseTypes, while a change to mermaid.src.diagrams.usecase.usecaseTypes can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagrams.usecase.usecaseTypes uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.usecaseTypes uses mermaid.src.diagrams.block.blockTypes, so a change to mermaid.src.diagrams.block.blockTypes can break mermaid.src.diagrams.usecase.usecaseTypes, while a change to mermaid.src.diagrams.usecase.usecaseTypes can't break mermaid.src.diagrams.block.blockTypes.
Position
Below the diagonal: mermaid.src.diagrams.usecase.usecaseTypes uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.usecaseTypes uses mermaid.src.diagrams.requirement.types, so a change to mermaid.src.diagrams.requirement.types can break mermaid.src.diagrams.usecase.usecaseTypes, while a change to mermaid.src.diagrams.usecase.usecaseTypes can't break mermaid.src.diagrams.requirement.types.
Position
Below the diagonal: mermaid.src.diagrams.usecase.usecaseTypes uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.usecaseTypes uses mermaid.src.diagrams.sequence.types, so a change to mermaid.src.diagrams.sequence.types can break mermaid.src.diagrams.usecase.usecaseTypes, while a change to mermaid.src.diagrams.usecase.usecaseTypes can't break mermaid.src.diagrams.sequence.types.
Position
Below the diagonal: mermaid.src.diagrams.usecase.usecaseTypes uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.xychart.chartBuilder.interfaces uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagrams.xychart.chartBuilder.interfaces, while a change to mermaid.src.diagrams.xychart.chartBuilder.interfaces can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.interfaces uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.xychart.chartBuilder.interfaces uses mermaid.src.types, so a change to mermaid.src.types can break mermaid.src.diagrams.xychart.chartBuilder.interfaces, while a change to mermaid.src.diagrams.xychart.chartBuilder.interfaces can't break mermaid.src.types.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.interfaces uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.layout-algorithms.layout-utils.validateLayout uses mermaid.src.types, so a change to mermaid.src.types can break mermaid.src.rendering-util.layout-algorithms.layout-utils.validateLayout, while a change to mermaid.src.rendering-util.layout-algorithms.layout-utils.validateLayout can't break mermaid.src.types.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.layout-utils.validateLayout uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.types uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.rendering-util.types, while a change to mermaid.src.rendering-util.types can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.rendering-util.types uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.types uses mermaid.src.types, so a change to mermaid.src.types can break mermaid.src.rendering-util.types, while a change to mermaid.src.rendering-util.types can't break mermaid.src.types.
Position
Below the diagonal: mermaid.src.rendering-util.types uses a module listed above it, which is the healthy direction.
mermaid-layout-tidy-tree.src.types uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid-layout-tidy-tree.src.types, while a change to mermaid-layout-tidy-tree.src.types can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid-layout-tidy-tree.src.types uses a module listed above it, which is the healthy direction.
mermaid.src uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src, while a change to mermaid.src can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src uses a module listed above it, which is the healthy direction.
mermaid.src uses mermaid.src.diagrams.requirement.types, so a change to mermaid.src.diagrams.requirement.types can break mermaid.src, while a change to mermaid.src can't break mermaid.src.diagrams.requirement.types.
Position
Below the diagonal: mermaid.src uses a module listed above it, which is the healthy direction.
mermaid.src uses mermaid.src.types, so a change to mermaid.src.types can break mermaid.src, while a change to mermaid.src can't break mermaid.src.types.
Position
Below the diagonal: mermaid.src uses a module listed above it, which is the healthy direction.
mermaid.src uses mermaid.src.diagrams.state.stateDb, so a change to mermaid.src.diagrams.state.stateDb can break mermaid.src, while a change to mermaid.src can't break mermaid.src.diagrams.state.stateDb.
Position
Below the diagonal: mermaid.src uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.agentflow uses mermaid.src.diagram-api.types, so a change to mermaid.src.diagram-api.types can break mermaid.src.diagrams.agentflow, while a change to mermaid.src.diagrams.agentflow can't break mermaid.src.diagram-api.types.
Position
Below the diagonal: mermaid.src.diagrams.agentflow uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.agentflow uses mermaid.src.diagrams.agentflow.agentflowDb, so a change to mermaid.src.diagrams.agentflow.agentflowDb can break mermaid.src.diagrams.agentflow, while a change to mermaid.src.diagrams.agentflow can't break mermaid.src.diagrams.agentflow.agentflowDb.
Position
Below the diagonal: mermaid.src.diagrams.agentflow uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.agentflow uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.diagrams.agentflow, while a change to mermaid.src.diagrams.agentflow can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.diagrams.agentflow uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.c4 uses mermaid.src.Diagram, so a change to mermaid.src.Diagram can break mermaid.src.diagrams.c4, while a change to mermaid.src.diagrams.c4 can't break mermaid.src.Diagram.
Position
Below the diagonal: mermaid.src.diagrams.c4 uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.c4 uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagrams.c4, while a change to mermaid.src.diagrams.c4 can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagrams.c4 uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.c4 uses mermaid.src.types, so a change to mermaid.src.types can break mermaid.src.diagrams.c4, while a change to mermaid.src.diagrams.c4 can't break mermaid.src.types.
Position
Below the diagonal: mermaid.src.diagrams.c4 uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.c4 uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.diagrams.c4, while a change to mermaid.src.diagrams.c4 can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.diagrams.c4 uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.treeView uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagrams.treeView, while a change to mermaid.src.diagrams.treeView can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagrams.treeView uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.treeView uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.diagrams.treeView, while a change to mermaid.src.diagrams.treeView can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.diagrams.treeView uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.usecaseAst uses mermaid.src.diagrams.block.blockTypes, so a change to mermaid.src.diagrams.block.blockTypes can break mermaid.src.diagrams.usecase.usecaseAst, while a change to mermaid.src.diagrams.usecase.usecaseAst can't break mermaid.src.diagrams.block.blockTypes.
Position
Below the diagonal: mermaid.src.diagrams.usecase.usecaseAst uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.usecaseAst uses mermaid.src.diagrams.sequence.types, so a change to mermaid.src.diagrams.sequence.types can break mermaid.src.diagrams.usecase.usecaseAst, while a change to mermaid.src.diagrams.usecase.usecaseAst can't break mermaid.src.diagrams.sequence.types.
Position
Below the diagonal: mermaid.src.diagrams.usecase.usecaseAst uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.usecaseAst uses mermaid.src.diagrams.usecase.usecaseTypes, so a change to mermaid.src.diagrams.usecase.usecaseTypes can break mermaid.src.diagrams.usecase.usecaseAst, while a change to mermaid.src.diagrams.usecase.usecaseAst can't break mermaid.src.diagrams.usecase.usecaseTypes.
Position
Below the diagonal: mermaid.src.diagrams.usecase.usecaseAst uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator uses a type in mermaid.src.diagrams.xychart.chartBuilder.interfaces.
mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator uses mermaid.src.diagrams.xychart.chartBuilder.interfaces, so a change to mermaid.src.diagrams.xychart.chartBuilder.interfaces can break mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator, while a change to mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator can't break mermaid.src.diagrams.xychart.chartBuilder.interfaces.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.layout-algorithms.ddlt uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.rendering-util.layout-algorithms.ddlt, while a change to mermaid.src.rendering-util.layout-algorithms.ddlt can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.ddlt uses a module listed above it, which is the healthy direction.
9 pairs of types, where a type in mermaid.src.rendering-util.layout-algorithms.elk uses a type in mermaid.src.rendering-util.layout-algorithms.elk.render.
mermaid.src.rendering-util.layout-algorithms.elk uses mermaid.src.rendering-util.layout-algorithms.elk.render, so a change to mermaid.src.rendering-util.layout-algorithms.elk.render can break mermaid.src.rendering-util.layout-algorithms.elk, while a change to mermaid.src.rendering-util.layout-algorithms.elk can't break mermaid.src.rendering-util.layout-algorithms.elk.render.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.elk uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.layout-algorithms.elk uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.rendering-util.layout-algorithms.elk, while a change to mermaid.src.rendering-util.layout-algorithms.elk can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.elk uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.layout-algorithms.layout-utils uses mermaid.src.types, so a change to mermaid.src.types can break mermaid.src.rendering-util.layout-algorithms.layout-utils, while a change to mermaid.src.rendering-util.layout-algorithms.layout-utils can't break mermaid.src.types.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.layout-utils uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in mermaid.src.rendering-util.layout-algorithms.layout-utils uses a type in mermaid.src.rendering-util.layout-algorithms.layout-utils.validateLayout.
mermaid.src.rendering-util.layout-algorithms.layout-utils uses mermaid.src.rendering-util.layout-algorithms.layout-utils.validateLayout, so a change to mermaid.src.rendering-util.layout-algorithms.layout-utils.validateLayout can break mermaid.src.rendering-util.layout-algorithms.layout-utils, while a change to mermaid.src.rendering-util.layout-algorithms.layout-utils can't break mermaid.src.rendering-util.layout-algorithms.layout-utils.validateLayout.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.layout-utils uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.layout-algorithms.layout-utils uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.rendering-util.layout-algorithms.layout-utils, while a change to mermaid.src.rendering-util.layout-algorithms.layout-utils can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.layout-utils uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in mermaid.src.rendering-util.layout-algorithms.swimlanes.direction uses a type in mermaid.src.diagrams.block.blockTypes.
mermaid.src.rendering-util.layout-algorithms.swimlanes.direction uses mermaid.src.diagrams.block.blockTypes, so a change to mermaid.src.diagrams.block.blockTypes can break mermaid.src.rendering-util.layout-algorithms.swimlanes.direction, while a change to mermaid.src.rendering-util.layout-algorithms.swimlanes.direction can't break mermaid.src.diagrams.block.blockTypes.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.swimlanes.direction uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in mermaid.src.rendering-util.layout-algorithms.swimlanes.direction uses a type in mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform.
mermaid.src.rendering-util.layout-algorithms.swimlanes.direction uses mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform, so a change to mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform can break mermaid.src.rendering-util.layout-algorithms.swimlanes.direction, while a change to mermaid.src.rendering-util.layout-algorithms.swimlanes.direction can't break mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.swimlanes.direction uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.layout-algorithms.swimlanes.direction uses mermaid.src.types, so a change to mermaid.src.types can break mermaid.src.rendering-util.layout-algorithms.swimlanes.direction, while a change to mermaid.src.rendering-util.layout-algorithms.swimlanes.direction can't break mermaid.src.types.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.swimlanes.direction uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.layout-algorithms.swimlanes.direction uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.rendering-util.layout-algorithms.swimlanes.direction, while a change to mermaid.src.rendering-util.layout-algorithms.swimlanes.direction can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.swimlanes.direction uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.render uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.rendering-util.render, while a change to mermaid.src.rendering-util.render can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.rendering-util.render uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.rendering-elements.shapes uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.rendering-util.rendering-elements.shapes, while a change to mermaid.src.rendering-util.rendering-elements.shapes can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.rendering-util.rendering-elements.shapes uses a module listed above it, which is the healthy direction.
101 pairs of types, where a type in mermaid.src.rendering-util.rendering-elements.shapes uses a type in mermaid.src.rendering-util.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
mermaid.src.rendering-util.rendering-elements.shapes uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.rendering-util.rendering-elements.shapes, while a change to mermaid.src.rendering-util.rendering-elements.shapes can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.rendering-util.rendering-elements.shapes uses a module listed above it, which is the healthy direction.
mermaid-layout-tidy-tree.src uses mermaid.src.types, so a change to mermaid.src.types can break mermaid-layout-tidy-tree.src, while a change to mermaid-layout-tidy-tree.src can't break mermaid.src.types.
Position
Below the diagonal: mermaid-layout-tidy-tree.src uses a module listed above it, which is the healthy direction.
mermaid-layout-tidy-tree.src uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid-layout-tidy-tree.src, while a change to mermaid-layout-tidy-tree.src can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid-layout-tidy-tree.src uses a module listed above it, which is the healthy direction.
mermaid-layout-tidy-tree.src uses mermaid-layout-tidy-tree.src.types, so a change to mermaid-layout-tidy-tree.src.types can break mermaid-layout-tidy-tree.src, while a change to mermaid-layout-tidy-tree.src can't break mermaid-layout-tidy-tree.src.types.
Position
Below the diagonal: mermaid-layout-tidy-tree.src uses a module listed above it, which is the healthy direction.
mermaid-layout-tidy-tree.src uses mermaid.src.rendering-util.render, so a change to mermaid.src.rendering-util.render can break mermaid-layout-tidy-tree.src, while a change to mermaid-layout-tidy-tree.src can't break mermaid.src.rendering-util.render.
Position
Below the diagonal: mermaid-layout-tidy-tree.src uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagrams.usecase, while a change to mermaid.src.diagrams.usecase can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagrams.usecase uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase uses mermaid.src.diagrams.block.blockTypes, so a change to mermaid.src.diagrams.block.blockTypes can break mermaid.src.diagrams.usecase, while a change to mermaid.src.diagrams.usecase can't break mermaid.src.diagrams.block.blockTypes.
Position
Below the diagonal: mermaid.src.diagrams.usecase uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase uses mermaid.src.diagrams.sequence.types, so a change to mermaid.src.diagrams.sequence.types can break mermaid.src.diagrams.usecase, while a change to mermaid.src.diagrams.usecase can't break mermaid.src.diagrams.sequence.types.
Position
Below the diagonal: mermaid.src.diagrams.usecase uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase uses mermaid.src.diagrams.usecase.usecaseTypes, so a change to mermaid.src.diagrams.usecase.usecaseTypes can break mermaid.src.diagrams.usecase, while a change to mermaid.src.diagrams.usecase can't break mermaid.src.diagrams.usecase.usecaseTypes.
Position
Below the diagonal: mermaid.src.diagrams.usecase uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase uses mermaid.src.diagrams.usecase.usecaseAst, so a change to mermaid.src.diagrams.usecase.usecaseAst can break mermaid.src.diagrams.usecase, while a change to mermaid.src.diagrams.usecase can't break mermaid.src.diagrams.usecase.usecaseAst.
Position
Below the diagonal: mermaid.src.diagrams.usecase uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.parser.usecaseModelBuilder uses mermaid.src.diagrams.block.blockTypes, so a change to mermaid.src.diagrams.block.blockTypes can break mermaid.src.diagrams.usecase.parser.usecaseModelBuilder, while a change to mermaid.src.diagrams.usecase.parser.usecaseModelBuilder can't break mermaid.src.diagrams.block.blockTypes.
Position
Below the diagonal: mermaid.src.diagrams.usecase.parser.usecaseModelBuilder uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.parser.usecaseModelBuilder uses mermaid.src.diagrams.requirement.types, so a change to mermaid.src.diagrams.requirement.types can break mermaid.src.diagrams.usecase.parser.usecaseModelBuilder, while a change to mermaid.src.diagrams.usecase.parser.usecaseModelBuilder can't break mermaid.src.diagrams.requirement.types.
Position
Below the diagonal: mermaid.src.diagrams.usecase.parser.usecaseModelBuilder uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.parser.usecaseModelBuilder uses mermaid.src.diagrams.sequence.types, so a change to mermaid.src.diagrams.sequence.types can break mermaid.src.diagrams.usecase.parser.usecaseModelBuilder, while a change to mermaid.src.diagrams.usecase.parser.usecaseModelBuilder can't break mermaid.src.diagrams.sequence.types.
Position
Below the diagonal: mermaid.src.diagrams.usecase.parser.usecaseModelBuilder uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.parser.usecaseModelBuilder uses mermaid.src.diagrams.usecase.usecaseTypes, so a change to mermaid.src.diagrams.usecase.usecaseTypes can break mermaid.src.diagrams.usecase.parser.usecaseModelBuilder, while a change to mermaid.src.diagrams.usecase.parser.usecaseModelBuilder can't break mermaid.src.diagrams.usecase.usecaseTypes.
Position
Below the diagonal: mermaid.src.diagrams.usecase.parser.usecaseModelBuilder uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.usecase.parser.usecaseModelBuilder uses mermaid.src.diagrams.usecase.usecaseAst, so a change to mermaid.src.diagrams.usecase.usecaseAst can break mermaid.src.diagrams.usecase.parser.usecaseModelBuilder, while a change to mermaid.src.diagrams.usecase.parser.usecaseModelBuilder can't break mermaid.src.diagrams.usecase.usecaseAst.
Position
Below the diagonal: mermaid.src.diagrams.usecase.parser.usecaseModelBuilder uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses a type in mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform.
mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform, so a change to mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform can break mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis can't break mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses mermaid.src.types, so a change to mermaid.src.types can break mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis can't break mermaid.src.types.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses a type in mermaid.src.diagrams.xychart.chartBuilder.interfaces.
mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses mermaid.src.diagrams.xychart.chartBuilder.interfaces, so a change to mermaid.src.diagrams.xychart.chartBuilder.interfaces can break mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis can't break mermaid.src.diagrams.xychart.chartBuilder.interfaces.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses a type in mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator.
mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator, so a change to mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator can break mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis can't break mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.axis.baseAxis uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle uses mermaid.src.types, so a change to mermaid.src.types can break mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle can't break mermaid.src.types.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle uses a type in mermaid.src.diagrams.xychart.chartBuilder.interfaces.
mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle uses mermaid.src.diagrams.xychart.chartBuilder.interfaces, so a change to mermaid.src.diagrams.xychart.chartBuilder.interfaces can break mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle can't break mermaid.src.diagrams.xychart.chartBuilder.interfaces.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle uses a type in mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator.
mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle uses mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator, so a change to mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator can break mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle can't break mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.xychart.chartBuilder.components.legend uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagrams.xychart.chartBuilder.components.legend, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.legend can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.legend uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.xychart.chartBuilder.components.legend uses mermaid.src.types, so a change to mermaid.src.types can break mermaid.src.diagrams.xychart.chartBuilder.components.legend, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.legend can't break mermaid.src.types.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.legend uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components.legend uses a type in mermaid.src.diagrams.xychart.chartBuilder.interfaces.
mermaid.src.diagrams.xychart.chartBuilder.components.legend uses mermaid.src.diagrams.xychart.chartBuilder.interfaces, so a change to mermaid.src.diagrams.xychart.chartBuilder.interfaces can break mermaid.src.diagrams.xychart.chartBuilder.components.legend, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.legend can't break mermaid.src.diagrams.xychart.chartBuilder.interfaces.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.legend uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components.legend uses a type in mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator.
mermaid.src.diagrams.xychart.chartBuilder.components.legend uses mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator, so a change to mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator can break mermaid.src.diagrams.xychart.chartBuilder.components.legend, while a change to mermaid.src.diagrams.xychart.chartBuilder.components.legend can't break mermaid.src.diagrams.xychart.chartBuilder.textDimensionCalculator.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components.legend uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.rendering-util, while a change to mermaid.src.rendering-util can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.rendering-util uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.rendering-util, while a change to mermaid.src.rendering-util can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.rendering-util uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util uses mermaid.src.rendering-util.render, so a change to mermaid.src.rendering-util.render can break mermaid.src.rendering-util, while a change to mermaid.src.rendering-util can't break mermaid.src.rendering-util.render.
Position
Below the diagonal: mermaid.src.rendering-util uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.layout-algorithms.swimlanes uses mermaid.src.rendering-util.types, so a change to mermaid.src.rendering-util.types can break mermaid.src.rendering-util.layout-algorithms.swimlanes, while a change to mermaid.src.rendering-util.layout-algorithms.swimlanes can't break mermaid.src.rendering-util.types.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.swimlanes uses a module listed above it, which is the healthy direction.
mermaid.src.rendering-util.layout-algorithms.swimlanes uses mermaid-layout-tidy-tree.src.types, so a change to mermaid-layout-tidy-tree.src.types can break mermaid.src.rendering-util.layout-algorithms.swimlanes, while a change to mermaid.src.rendering-util.layout-algorithms.swimlanes can't break mermaid-layout-tidy-tree.src.types.
Position
Below the diagonal: mermaid.src.rendering-util.layout-algorithms.swimlanes uses a module listed above it, which is the healthy direction.
mermaid.src.diagrams.xychart.chartBuilder.components uses mermaid.src.config_type, so a change to mermaid.src.config_type can break mermaid.src.diagrams.xychart.chartBuilder.components, while a change to mermaid.src.diagrams.xychart.chartBuilder.components can't break mermaid.src.config_type.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components uses a type in mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform.
mermaid.src.diagrams.xychart.chartBuilder.components uses mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform, so a change to mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform can break mermaid.src.diagrams.xychart.chartBuilder.components, while a change to mermaid.src.diagrams.xychart.chartBuilder.components can't break mermaid.src.rendering-util.layout-algorithms.swimlanes.direction.lrTransform.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components uses a type in mermaid.src.diagrams.xychart.chartBuilder.interfaces.
mermaid.src.diagrams.xychart.chartBuilder.components uses mermaid.src.diagrams.xychart.chartBuilder.interfaces, so a change to mermaid.src.diagrams.xychart.chartBuilder.interfaces can break mermaid.src.diagrams.xychart.chartBuilder.components, while a change to mermaid.src.diagrams.xychart.chartBuilder.components can't break mermaid.src.diagrams.xychart.chartBuilder.interfaces.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components uses a type in mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle.
mermaid.src.diagrams.xychart.chartBuilder.components uses mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle, so a change to mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle can break mermaid.src.diagrams.xychart.chartBuilder.components, while a change to mermaid.src.diagrams.xychart.chartBuilder.components can't break mermaid.src.diagrams.xychart.chartBuilder.components.chartTitle.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in mermaid.src.diagrams.xychart.chartBuilder.components uses a type in mermaid.src.diagrams.xychart.chartBuilder.components.legend.
mermaid.src.diagrams.xychart.chartBuilder.components uses mermaid.src.diagrams.xychart.chartBuilder.components.legend, so a change to mermaid.src.diagrams.xychart.chartBuilder.components.legend can break mermaid.src.diagrams.xychart.chartBuilder.components, while a change to mermaid.src.diagrams.xychart.chartBuilder.components can't break mermaid.src.diagrams.xychart.chartBuilder.components.legend.
Position
Below the diagonal: mermaid.src.diagrams.xychart.chartBuilder.components uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 57% · Adequate · gated by D1, D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
91
High / Critical
A05:2025 — Injection
27
High / Critical
A07:2025 — Authentication Failures
6
High / Critical
A02:2025 — Security Misconfiguration
2
High / Critical
Roadmap
First, establish a solid page structure by defining language, title, and main landmarks while ensuring proper heading order and disabling meta-refresh. Next, enforce accessibility standards across the toolchain by integrating linting and CI gates, and immediately fix all unlabeled form controls and buttons. Finally, ensure visual safety by maintaining visible focus styles, respecting reduced motion preferences, correcting low-contrast colors, and resolving the leaked secret in the lock file.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
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 — 94
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 — 1091
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 — 204
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
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
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 80 of 80 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 80 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, 1349 of 1389 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 — Watchdog measured this, but not all of it. What it 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 — Watchdog 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog 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 the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `.build/common.ts`, `packages/mermaid/src/diagrams/git/gitGraphAst.ts`, `packages/mermaid/src/diagrams/kanban/kanbanDb.ts`, `packages/mermaid/src/diagrams/state/stateDb.ts`, `packages/mermaid/src/docs/.vitepress/config.ts`, … (+4 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
AXR1 Runtime accessibility — not measured this run — Watchdog 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 DockerCompose (docker-compose.yml). compose up failed (exit 15 — the compose project is invalid) — time="2026-10-26T11:38:43Z" level=warning msg="The \"MERMAID_PORT\" variable is not set. Defaulting to a blank string." time="2026-10-26T11:38:43Z" level=warning msg="The \"MERMAID_PORT\" variable is not set. Defaulting to a blank string." no port specified: :<empty>; runtime evidence skipped.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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). 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.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 468 further occurrence(s) are not listed individually; the score already reflects all 508.
R3 Large Files — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 28 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
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.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
172 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was updateColors at 289. 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 renderHelpers.getNodeFromBlock at 26 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/mermaid/src/diagrams/block/renderHelpers.ts (renderHelpers.getNodeFromBlock at 26), packages/mermaid/src/diagrams/state/styles.js (getStyles at 22), packages/mermaid/src/rendering-util/rendering-elements/shapes/handDrawnShapeStyles.ts (handDrawnShapeStyles.isLabelStyle at 18). 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.
+ 140 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 35 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with updateColors (cyclomatic 289), Theme.updateColors (cyclomatic 279), router.routeEdgesOrthogonal (cyclomatic 224). — 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 35 together lifts Cyclomatic Complexity from 2.0 to about 4.7/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 215 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 96 bodies over 30 down to 30 or less in Cognitive Complexity — start with router.routeEdgesOrthogonal (cognitive 493), validateLayout.validateLayout (cognitive 405), updateColors (cognitive 295). — 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 96 together lifts Cognitive Complexity from 2.0 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes6.3 / 10Adequate✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 63 FunctionTooLong finding(s) in God Classes — start with materializedGeometry.ts (7), styles.ts (4), sequenceRenderer.ts (3). — One of this dimension's main actionable groups (63 warning-level).
Resolve the 23 FileTooLong finding(s) in God Classes — start with materializedGeometry.ts, render.ts, REDACTED. — One of this dimension's main actionable groups (23 warning-level).
Resolve the 17 MethodTooLong finding(s) in God Classes — start with theme-default.js (2), usecase.parser.ts, theme-base.js. — One of this dimension's main actionable groups (17 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.7 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
6 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 4 of the 6 (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: @mermaid-js/parser
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 76.4% — 86 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root).
Resolve the 86 Low coverage finding(s) in Code Coverage — start with db.ts (3), svgDraw.ts (2), REDACTED (2). — One of this dimension's main actionable groups (86 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution9.1 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
3994 test methods: 3728 unit, 0 integration, 0 BDD, 266 e2e. The JavaScript/TypeScript suite contributes 3994 `it`/`test` case(s) across 364 test file(s) declaring at least one; its tier split is read from package names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.5 / 10Adequategated by 2 critical 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.
16 skipped (2 with a documented reason), 121 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3994 tests.
No assertions (empty test): should limit the number of relationships between the same two entities · ×2packages/mermaid/src/diagrams/er/parser/erDiagram.spec.js:575
No assertions: should add to mermaid · ×119packages/mermaid-layout-elk/src/plugin.spec.ts:13
Skipped test: markdownToLines - No auto wrapping · ×14packages/mermaid/src/rendering-util/handle-markdown-text.spec.ts:207
Test project verifies nothing: packages/mermaid-example-diagrampackages/mermaid-example-diagram/src/exampleDiagram.spec.js:22
Mock-dominated test: calls setDiagramId with the svg element id · ×2packages/mermaid/src/diagrams/flowchart/flowRenderer-v3-unified.spec.ts:27
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with erDiagram.spec.js (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 119 No assertions finding(s) in Test Quality — start with classDiagram.spec.ts (39), stateDiagram.spec.js (24), stateDiagram-v2.spec.js (21). — One of this dimension's main actionable groups (119 warning-level).
Resolve the 14 Skipped test finding(s) in Test Quality — start with gitGraph.spec.ts (4), handle-markdown-text.spec.ts, postProcessing.spec.ts. — One of this dimension's main actionable groups (14 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
16 outdated direct production npm dependency(ies) of 32 graded, 0 pinning defect(s), across 11 package.json (7 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 4 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Resolve the 14 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (14). — One of this dimension's main actionable groups (14 recommendation-level).
Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with package.json (5). — One of this dimension's main actionable groups (5 warning-level).
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.
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 32 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 32 production dependency(ies) this repository's committed lockfile resolves, across 7 product package.json manifest(s). Its 153 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: packages/mermaid/src/themes/theme-redux-color.js (10×195=1950); packages/mermaid/src/themes/theme-redux-dark-color.js (8×192=1536); packages/mermaid/src/themes/theme-neo.js (4×213=852) Repeated repair below the complexity floor: packages/mermaid/src/rendering-util/layout-algorithms/common/index.ts (6 of 6 changes were fixes); packages/mermaid/src/diagrams/flowchart/styles.ts (5 of 8 changes were fixes); packages/mermaid/src/diagrams/er/styles.ts (5 of 5 changes were fixes)
Resolve the 29 Hotspot finding(s) in Churn × Complexity Hotspots — start with theme-redux-color.js, theme-redux-dark-color.js, theme-neo.js. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 14 Repeated repair finding(s) in Churn × Complexity Hotspots — start with styles.ts (4), index.ts, usecaseActor.ts. — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor7.9 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
64 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts. Counted over 311 of the 628 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×5
Further sole-owners (lower concentration)
What to do
Resolve the 5 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (5 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
93 deducted task-comment markers across 85167 LoC (0.1/KLoC) → score 9.8. 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 · ×82scripts/tsc-check.ts:63
TodoComment repeated across 10 filespackages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts:48
Resolve the 82 TodoComment finding(s) in Explicit Debt — start with styles.ts (6), REDACTED (5), mermaidAPI.spec.ts (4). — One of this dimension's main actionable groups (82 warning-level).
Resolve the 1 TodoComment repeated across 10 files finding(s) in Explicit Debt — start with classBox.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with architectureRenderer.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
1 domain type(s) cross context boundaries across 7 contexts.
Cross-context type DiagramAST (parser → mermaid)packages/mermaid/src/diagrams/common/populateCommonDb.ts:4
What to do
Resolve the 1 Cross-context type DiagramAST (parser → mermaid) finding(s) in Boundary Type-Coupling — start with populateCommonDb.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 7 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
27 finding(s): 0 critical, 12 high, 15 medium, 0 low. 1 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 98 file(s) — `.build/common.ts` (line 48), `demos/block.html` (lines 16–26, lines 33–35, lines 43–47, …), `demos/classchart.html` (lines 27–49, lines 56–70, lines 96–109, …), `demos/dataflowchart.html` (line 21), `demos/error.html` (line 28), … (+93 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 1 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (1 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 55 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (55). — One of this dimension's main actionable groups (55 issue-level).
Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
48 of 311 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/mermaid/src/diagrams/er/erRenderer.js. Counted over 311 of the 628 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with erRenderer.js, sequenceDb.ts, quadrantBuilder.ts. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 45 Orphaned file finding(s) in Knowledge Freshness — start with swimlanes-size.ts, ishikawaRenderer.ts, REDACTED. — One of this dimension's main actionable groups (45 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 6 Change coupling finding(s) in Change Coupling — start with chartTitle.ts, index.ts, linePlot.ts. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with textDimensionCalculator.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
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).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored 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. SCORED, not informational.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels4.2 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — .esbuild/dev-explorer/diagram-viewer.ts:1644, packages/mermaid-local-editor/static/index.html:17, packages/mermaid-local-editor/static/index.html:27
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — packages/mermaid-local-editor/static/index.html:18
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — .esbuild/dev-explorer/public/compare-pane.html:2, packages/mermaid-local-editor/static/index.html:2, scripts/verify-diagram/verify.mjs:113
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <dev-explorer-app>, so there is no content here to wrap — render the <main> from the component mounted into it. — .esbuild/dev-explorer/public/index.html:2
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — scripts/verify-diagram/verify.mjs:113
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — scripts/verify-diagram/verify.mjs:113
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.editable-code:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/mermaid/src/docs/.vitepress/theme/Mermaid.vue:108
`dev-explorer-app .cm-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — .esbuild/dev-explorer/public/styles.css:479
`#toolbar` moves (`transition: transform 0.25s ease,
opacity 0.2s ease,
height 0.25s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/mermaid-local-editor/static/styles.css:16
`.mermaid-chart-tooltip.showing` moves (`animation: tooltipFadeIn 0.3s ease 0.4s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/mermaid/src/docs/.vitepress/theme/Tooltip.vue:84
`.mermaid-chart-tooltip.hiding` moves (`animation: tooltipFadeOut 0.3s ease forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/mermaid/src/docs/.vitepress/theme/Tooltip.vue:88
`dev-explorer-app button.card` moves (`transition: transform 0.2s ease,
box-shadow 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .esbuild/dev-explorer/public/styles.css:215
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 16 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`GitGraphDB` declares 17 required operations: `setDirection`, `setOptions`, `getOptions`, `commit`, `branch`, `merge`, `cherryPick`, `checkout`, `prettyPrint`, `clear`, `getBranchesAsObjArray`, `getBranches`, `getCommits`, `getCommitsArray`, `getCurrentBranch`, `getDirection`, `getHead`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/mermaid/src/diagrams/git/gitGraphTypes.ts:90
`ArchitectureDB` declares 16 required operations: `clear`, `addService`, `getServices`, `addJunction`, `getJunctions`, `getNodes`, `getNode`, `addGroup`, `getGroups`, `addEdge`, `getEdges`, `addLayoutHint`, `getLayoutHints`, `setElementForId`, `getElementById`, `getDataStructures`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/mermaid/src/diagrams/architecture/architectureTypes.ts:252
`UsecaseDB` declares 20 required operations: `getConfig`, `createModel`, `commit`, `getAST`, `getActors`, `getActor`, `getUseCases`, `getUseCase`, `getSystemBoundaries`, `getSystemBoundary`, `getRelationships`, `getNotes`, `getNote`, `getJsonNodes`, `getJsonNode`, `getClassDefs`, `getClassDef`, `getDirection`, `getData`, `clear`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/mermaid/src/diagrams/usecase/usecaseTypes.ts:304
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX 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 JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes 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.
`getStyles` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/mermaid/src/diagrams/eventmodeling/styles.js:1
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×4) — REDACTED:583, REDACTED:584, packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts:269, …
`parse` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/mermaid/src/diagrams/usecase/parser/usecase.chevrotain.ts:10
`trace` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/mermaid/src/logger.ts:19
`debug` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/mermaid/src/logger.ts:20
`info` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/mermaid/src/logger.ts:21
`warn` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/mermaid/src/logger.ts:22
`error` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/mermaid/src/logger.ts:23
`fatal` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/mermaid/src/logger.ts:24
`runDomusOrthogonalDdlt` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/mermaid/src/rendering-util/layout-algorithms/ddlt/backends.ts:35
The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. (×2) — packages/mermaid/src/rendering-util/rendering-elements/clusters.js:478, packages/mermaid/src/utils.ts:427
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×16) — e2e/other/pr-check/configuration.spec.js:55, e2e/other/pr-check/dev-explorer-compare.spec.ts:11, packages/mermaid/scripts/docs.spec.ts:166, …
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×4) — packages/mermaid/src/diagrams/quadrant-chart/quadrantRenderer.ts:1, packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1, packages/mermaid/src/diagrams/timeline/timelineRenderer.ts:1, …
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.
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
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.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 3 of 10 project(s) that lack one — worth up to 0.6 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no 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 README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & 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 model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
`packages/mermaid/src/assignWithDepth.ts` reports through `console.*` at line 17 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/assignWithDepth.ts:17
`packages/mermaid/src/mermaid.ts` reports through `console.*` at line 337 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/mermaid.ts:337
`packages/mermaid/src/mermaid.ts` reports through `console.*` at line 339 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/mermaid.ts:339
`packages/mermaid/src/mermaid.ts` reports through `console.*` at line 341 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/mermaid.ts:341
`packages/mermaid/src/mermaid.ts` reports through `console.*` at line 343 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/mermaid.ts:343
`packages/mermaid/src/profiler.ts` reports through `console.*` at line 304 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/profiler.ts:304
`packages/mermaid/src/utils/imperativeState.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/utils/imperativeState.ts:12
`packages/mermaid/src/utils/imperativeState.ts` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/utils/imperativeState.ts:14
`packages/mermaid/src/rendering-util/render.ts` reports through `console.*` at line 9 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/rendering-util/render.ts:9
`packages/mermaid/src/rendering-util/rendering-elements/shapes/drawRect.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/rendering-util/rendering-elements/shapes/drawRect.ts:18
`packages/mermaid/src/rendering-util/layout-algorithms/ddlt/discoverFixtures.ts` reports through `console.*` at line 100 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/rendering-util/layout-algorithms/ddlt/discoverFixtures.ts:100
`packages/mermaid/src/diagrams/state/stateRenderer-v3-unified.ts` reports through `console.*` at line 75 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/diagrams/state/stateRenderer-v3-unified.ts:75
`packages/mermaid/src/diagrams/state/shapes.js` reports through `console.*` at line 180 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/diagrams/state/shapes.js:180
`packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 27 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/diagrams/kanban/kanbanDb.ts:27
`packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/diagrams/kanban/kanbanDb.ts:35
`packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/diagrams/kanban/kanbanDb.ts:37
`packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 121 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/diagrams/kanban/kanbanDb.ts:121
`packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 123 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/diagrams/kanban/kanbanDb.ts:123
`packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 126 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/diagrams/kanban/kanbanDb.ts:126
`packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 130 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid/src/diagrams/kanban/kanbanDb.ts:130
`packages/mermaid-example-diagram/src/mermaidUtils.ts` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid-example-diagram/src/mermaidUtils.ts:5
`packages/mermaid-zenuml/src/mermaidUtils.ts` reports through `console.*` at line 6 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mermaid-zenuml/src/mermaidUtils.ts:6
What to do
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
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.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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 the language 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.
`existsSync` in `verifyArgosMetadataSidecars` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — e2e/helpers/argos-metadata.ts:288
`readFileSync` in `verifyArgosMetadataSidecars` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — e2e/helpers/argos-metadata.ts:293
`mkdirSync` in `verifyScreenshot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — e2e/helpers/util.ts:271, e2e/helpers/util.ts:287
`writeFileSync` in `verifyScreenshot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — e2e/helpers/util.ts:273, e2e/helpers/util.ts:289
`existsSync` in `verifyScreenshot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — e2e/helpers/util.ts:286
`rmSync` in `processDocs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/mermaid/scripts/docs.mts:623
`rmSync` in `on("unlink")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/mermaid/scripts/docs.mts:662
`rmdirSync` in `on("unlinkDir")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/mermaid/scripts/docs.mts:663
`readFileSync` in `parseMmdFileToLayoutData` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/mermaid/src/rendering-util/layout-algorithms/ddlt/parseToLayoutData.ts:21
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety8.6 / 10Strong✓ 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.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): 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. Deterministic.
100 duplicated blocks under packages/mermaid/src/diagrams/ have copies in at least two of the sibling directories agentflow, architecture, block, c4, class, common (+28 more sibling(s) not listed) — 81 of them are reported below, and 19 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 100 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 100 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 100 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/mermaid/src/diagrams/timeline/svgDraw.js:19
15 duplicated blocks under packages/mermaid/src/ have copies in at least two of the sibling directories diagrams, rendering-util — 11 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:1022
12 duplicated blocks under packages/parser/src/language/ have copies in at least two of the sibling directories architecture, cynefin, eventmodeling, gitGraph, info, packet (+8 more sibling(s) not listed) — 8 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/parser/src/language/railroad-peg/valueConverter.ts:5
10 duplicated blocks under packages/ have copies in at least two of the sibling directories mermaid, mermaid-example-diagram, mermaid-layout-tidy-tree, mermaid-zenuml — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/mermaid-layout-tidy-tree/src/render.ts:11
6 duplicated blocks under packages/mermaid/src/rendering-util/layout-algorithms/ have copies in at least two of the sibling directories ddlt, layout-utils, swimlanes — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/mermaid/src/rendering-util/layout-algorithms/ddlt/baselineDdltSpec.ts:137
packages/mermaid/src/themes/theme-neo-dark.js:1 · packages/mermaid/src/themes/theme-redux-dark.js:1 — these 2 files are line-for-line copies of one another — 291 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/mermaid/src/themes/theme-neo-dark.js:1
packages/mermaid/src/themes/theme-redux-dark-color.js:1 · packages/mermaid/src/themes/theme-redux-dark.js:1 — these 2 files are line-for-line copies of one another — 279 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/mermaid/src/themes/theme-redux-dark-color.js:1
packages/mermaid/src/diagrams/timeline/svgDraw.js:19 · packages/mermaid/src/diagrams/user-journey/svgDraw.js:5 — the two spans are one implementation copied and then locally edited — 1894 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. — packages/mermaid/src/diagrams/timeline/svgDraw.js:19
packages/mermaid/src/themes/theme-neo.js:1 · packages/mermaid/src/themes/theme-redux-color.js:1 · packages/mermaid/src/themes/theme-redux.js:1 — these 3 files are line-for-line copies of one another — 247 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/mermaid/src/themes/theme-neo.js:1
packages/mermaid/src/themes/theme-default.js:164 · packages/mermaid/src/themes/theme-forest.js:140 — the two spans are one implementation copied and then locally edited — 1875 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. — packages/mermaid/src/themes/theme-default.js:164
packages/mermaid/src/diagrams/timeline/timelineRenderer.ts:11 · packages/mermaid/src/diagrams/timeline/timelineRendererVertical.ts:11 — the two spans are one implementation copied and then locally edited — 857 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. — packages/mermaid/src/diagrams/timeline/timelineRenderer.ts:11
packages/mermaid/src/diagrams/c4/svgDraw.ts:215 · REDACTED:1633 — the two spans are one implementation copied and then locally edited — 645 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. — packages/mermaid/src/diagrams/c4/svgDraw.ts:215
packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:841 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:384 — 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. — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:841
packages/mermaid/src/rendering-util/rendering-elements/shapes/icon.ts:1 · packages/mermaid/src/rendering-util/rendering-elements/shapes/iconRounded.ts:1 · packages/mermaid/src/rendering-util/rendering-elements/shapes/iconSquare.ts:1 — these 3 files are line-for-line copies of one another — 91 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/mermaid/src/rendering-util/rendering-elements/shapes/icon.ts:1
packages/mermaid/src/diagrams/er/erDb.ts:39 · packages/mermaid/src/diagrams/requirement/requirementDb.ts:64 — the two spans are one implementation copied and then locally edited — 497 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. — packages/mermaid/src/diagrams/er/erDb.ts:39
packages/mermaid/src/rendering-util/rendering-elements/clusters.js:56 · packages/mermaid/src/rendering-util/rendering-elements/clusters.js:339 — the two spans are one implementation copied and then locally edited — 592 tokens are still identical, in the same order in both spans, 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. — packages/mermaid/src/rendering-util/rendering-elements/clusters.js:56
packages/mermaid-layout-tidy-tree/src/render.ts:11 · packages/mermaid/src/rendering-util/layout-algorithms/cose-bilkent/render.ts:13 — the two spans are one implementation copied and then locally edited — 549 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. — packages/mermaid-layout-tidy-tree/src/render.ts:11
packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:713 · packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:841 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:713
packages/mermaid/src/diagrams/xychart/chartBuilder/orchestrator.ts:63 · packages/mermaid/src/diagrams/xychart/chartBuilder/orchestrator.ts:133 — the two spans are one implementation copied and then locally edited — 478 tokens are still identical, in the same order in both spans, 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. — packages/mermaid/src/diagrams/xychart/chartBuilder/orchestrator.ts:63
packages/mermaid/src/rendering-util/rendering-elements/shapes/linedWaveEdgedRect.ts:25 · packages/mermaid/src/rendering-util/rendering-elements/shapes/waveEdgedRectangle.ts:28 — the two spans are one implementation copied and then locally edited — 487 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. — packages/mermaid/src/rendering-util/rendering-elements/shapes/linedWaveEdgedRect.ts:25
packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1585 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:1012 — 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. — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1585
packages/mermaid/src/diagrams/git/gitGraphAst.ts:112 · packages/mermaid/src/diagrams/git/gitGraphAst.ts:266 — the two spans are one implementation copied and then locally edited — 377 tokens are still identical, in the same order in both spans, 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. — packages/mermaid/src/diagrams/git/gitGraphAst.ts:112
packages/mermaid/src/utils/lineWithOffset.ts:60 · packages/mermaid/src/utils/lineWithOffset.ts:122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/mermaid/src/utils/lineWithOffset.ts:60
packages/parser/src/language/railroad-peg/valueConverter.ts:5 · packages/parser/src/language/railroad/valueConverter.ts:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/parser/src/language/railroad-peg/valueConverter.ts:5
packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:291 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:73 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:291
packages/mermaid/src/rendering-util/rendering-elements/shapes/browser.ts:10 · packages/mermaid/src/rendering-util/rendering-elements/shapes/console.ts:10 — the two spans are one implementation copied and then locally edited — 449 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. — packages/mermaid/src/rendering-util/rendering-elements/shapes/browser.ts:10
packages/parser/src/language/railroad-ebnf/valueConverter.ts:5 · packages/parser/src/language/railroad-peg/valueConverter.ts:5 · packages/parser/src/language/railroad/valueConverter.ts:5 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — packages/parser/src/language/railroad-ebnf/valueConverter.ts:5
packages/mermaid/src/rendering-util/rendering-elements/shapes/flippedTriangle.ts:10 · packages/mermaid/src/rendering-util/rendering-elements/shapes/triangle.ts:12 — the two spans are one implementation copied and then locally edited — 447 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. — packages/mermaid/src/rendering-util/rendering-elements/shapes/flippedTriangle.ts:10
packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:762 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:314 — 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. — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:762
packages/mermaid/src/diagrams/kanban/kanbanDb.ts:164 · packages/mermaid/src/diagrams/mindmap/mindmapDb.ts:115 — the two spans are one implementation copied and then locally edited — 246 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. — packages/mermaid/src/diagrams/kanban/kanbanDb.ts:164
packages/mermaid/src/diagrams/agentflow/types.ts:43 · packages/mermaid/src/diagrams/flowchart/types.ts:25 — the two spans are one implementation copied and then locally edited — 230 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. — packages/mermaid/src/diagrams/agentflow/types.ts:43
packages/mermaid/src/themes/theme-dark.js:166 · packages/mermaid/src/themes/theme-neutral.js:233 — the two spans are one implementation copied and then locally edited — 547 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. — packages/mermaid/src/themes/theme-dark.js:166
packages/mermaid-example-diagram/src/mermaidUtils.ts:2 · packages/mermaid-zenuml/src/mermaidUtils.ts:3 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/mermaid-example-diagram/src/mermaidUtils.ts:2
packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:471 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:188 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:471
packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1499 · packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1755 — the two spans are one implementation copied and then locally edited — 247 tokens are still identical, in the same order in both spans, 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. — packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1499
packages/mermaid/src/rendering-util/rendering-elements/shapes/cylinder.ts:9 · packages/mermaid/src/rendering-util/rendering-elements/shapes/document.ts:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/mermaid/src/rendering-util/rendering-elements/shapes/cylinder.ts:9
packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1183 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:681 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1183
packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:97 · packages/mermaid/src/diagrams/user-journey/journeyRenderer.ts:218 — the two spans are one implementation copied and then locally edited — 461 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. — packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:97
packages/mermaid/src/themes/theme-default.js:8 · packages/mermaid/src/themes/theme-neutral.js:11 — the two spans are one implementation copied and then locally edited — 321 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. — packages/mermaid/src/themes/theme-default.js:8
packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1320 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:770 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1320
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 · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
packages/mermaid/scripts/create-types-from-json-schema.mts:13 imports ajv/dist/2019.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/scripts/create-types-from-json-schema.mts:13
packages/mermaid/scripts/docs.mts:32 imports @adobe/jsonschema2md/lib/schemaProxy.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/scripts/docs.mts:32
packages/mermaid/scripts/docs.mts:34 imports @adobe/jsonschema2md/lib/traverseSchema.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/scripts/docs.mts:34
packages/mermaid/scripts/docs.mts:36 imports @adobe/jsonschema2md/lib/markdownBuilder.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/scripts/docs.mts:36
packages/mermaid/scripts/docs.mts:38 imports @adobe/jsonschema2md/lib/readmeBuilder.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/scripts/docs.mts:38
packages/mermaid/src/diagrams/block/renderHelpers.ts:1 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/diagrams/block/renderHelpers.ts:1
packages/mermaid/src/diagrams/class/classRenderer.js:2 imports dagre-d3-es/src/dagre/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/diagrams/class/classRenderer.js:2
packages/mermaid/src/diagrams/class/classRenderer.js:3 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/diagrams/class/classRenderer.js:3
packages/mermaid/src/diagrams/er/erRenderer.js:1 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/diagrams/er/erRenderer.js:1
packages/mermaid/src/diagrams/er/erRenderer.js:3 imports dagre-d3-es/src/dagre/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/diagrams/er/erRenderer.js:3
packages/mermaid/src/diagrams/flowchart/flowChartShapes.js:1 imports dagre-d3-es/src/dagre-js/intersect/intersect-polygon.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/diagrams/flowchart/flowChartShapes.js:1
packages/mermaid/src/diagrams/flowchart/flowChartShapes.js:2 imports dagre-d3-es/src/dagre-js/intersect/intersect-rect.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/diagrams/flowchart/flowChartShapes.js:2
packages/mermaid/src/diagrams/state/stateRenderer.js:2 imports dagre-d3-es/src/dagre/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/diagrams/state/stateRenderer.js:2
packages/mermaid/src/diagrams/state/stateRenderer.js:3 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/diagrams/state/stateRenderer.js:3
packages/mermaid/src/rendering-util/createGraph.ts:2 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/rendering-util/createGraph.ts:2
packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:2 imports dagre-d3-es/src/dagre/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:2
packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:3 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:3
packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:3 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:3
packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:10 imports elkjs/lib/elk.bundled.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:10
scripts/argos-upload-sheets.ts:15 imports e2e/helpers/argos-metadata.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/argos-upload-sheets.ts:15
scripts/screenshot-order.ts:20 imports e2e/helpers/argos-metadata.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/screenshot-order.ts:20
scripts/screenshot-sheets.ts:18 imports e2e/helpers/argos-metadata.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/screenshot-sheets.ts:18
What to do
Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (19 rows); move the shared test helper into a source directory production code may depend on (3 rows).
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.
updateColors has cyclomatic complexity 289 and cognitive complexity 295; 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. — packages/mermaid/src/themes/theme-base.js:32
routeEdgesOrthogonal has cyclomatic complexity 269 and cognitive complexity 539; 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. — packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts:122
updateColors has cyclomatic complexity 216 and cognitive complexity 221; 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. — packages/mermaid/src/themes/theme-redux-dark.js:76
updateColors has cyclomatic complexity 215 and cognitive complexity 220; 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. (×2) — packages/mermaid/src/themes/theme-neo-dark.js:68, packages/mermaid/src/themes/theme-neo.js:52
updateColors has cyclomatic complexity 205 and cognitive complexity 210; 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. — packages/mermaid/src/themes/theme-redux.js:58
updateColors has cyclomatic complexity 203 and cognitive complexity 204; 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. — packages/mermaid/src/themes/theme-default.js:146
updateColors has cyclomatic complexity 200 and cognitive complexity 200; 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. — packages/mermaid/src/themes/theme-forest.js:113
updateColors has cyclomatic complexity 199 and cognitive complexity 201; 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. — packages/mermaid/src/themes/theme-redux-color.js:106
updateColors has cyclomatic complexity 195 and cognitive complexity 197; 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. — packages/mermaid/src/themes/theme-redux-dark-color.js:108
updateColors has cyclomatic complexity 189 and cognitive complexity 188; 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. — packages/mermaid/src/themes/theme-dark.js:115
validateLayout has cyclomatic complexity 174 and cognitive complexity 388; 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. — packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:604
updateColors has cyclomatic complexity 173 and cognitive complexity 174; 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. — packages/mermaid/src/themes/theme-neutral.js:128
drawMessage has cyclomatic complexity 74 and cognitive complexity 90; 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. — packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:461
insertEdge has cyclomatic complexity 71 and cognitive complexity 76; 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. — packages/mermaid/src/rendering-util/rendering-elements/edges.js:624
classBox has cyclomatic complexity 55 and cognitive complexity 57; 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. — packages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts:14
layoutContainer has cyclomatic complexity 54 and cognitive complexity 72; 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. — packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts:61
draw has cyclomatic complexity 54 and cognitive complexity 38; 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. — packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1043
writeBackToLayoutData has cyclomatic complexity 49 and cognitive complexity 118; 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. — packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/helpers.ts:174
collapseShortTerminalStub has cyclomatic complexity 47 and cognitive complexity 101; 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. — packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/terminalStub.ts:44
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files6.1 / 10Adequate✓ 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.
packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts has 2798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1
packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts has 2564 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1
packages/mermaid/src/diagrams/agentflow/agentflowDb.ts has 2326 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1
packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts has 2070 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts:1
packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts has 1982 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1
REDACTED has 1954 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts has 1400 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:1
packages/mermaid/src/diagrams/git/gitGraphRenderer.ts has 1369 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:1
packages/mermaid/src/diagrams/flowchart/flowDb.ts has 1232 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/flowchart/flowDb.ts:1
packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts has 1040 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:1
packages/mermaid/src/rendering-util/rendering-elements/edges.js has 984 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/rendering-elements/edges.js:1
packages/mermaid/src/rendering-util/rendering-elements/markers.js has 973 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/rendering-elements/markers.js:1
packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts has 971 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts:1
packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts has 965 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts:1
packages/mermaid/src/utils.ts has 896 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/utils.ts:1
packages/mermaid/src/diagrams/gantt/ganttRenderer.js has 817 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/gantt/ganttRenderer.js:1
packages/mermaid/src/diagrams/gantt/ganttDb.js has 805 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/gantt/ganttDb.js:1
packages/mermaid/src/diagrams/class/classDb.ts has 796 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/class/classDb.ts:1
packages/mermaid/src/rendering-util/rendering-elements/clusters.js has 767 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/rendering-elements/clusters.js:1
packages/mermaid/src/diagrams/c4/c4Db.ts has 755 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/c4/c4Db.ts:1
packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js has 752 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:1
REDACTED has 717 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/mermaid/src/diagrams/state/stateDb.ts has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/state/stateDb.ts:1
packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts has 690 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts:1
scripts/screenshot-sheets.ts has 690 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/screenshot-sheets.ts:1
packages/mermaid/src/diagrams/sequence/sequenceDb.ts has 674 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/sequence/sequenceDb.ts:1
packages/mermaid/src/diagrams/usecase/parser/usecase.parser.ts has 646 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/usecase/parser/usecase.parser.ts:1
packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts has 625 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts:1
packages/mermaid/src/diagrams/eventmodeling/db.ts has 616 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/eventmodeling/db.ts:1
packages/mermaid/src/diagrams/er/erRenderer.js has 611 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/er/erRenderer.js:1
packages/mermaid/src/diagrams/architecture/architectureRenderer.ts has 598 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/architecture/architectureRenderer.ts:1
packages/mermaid/src/rendering-util/rendering-elements/shapes.ts has 593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/rendering-elements/shapes.ts:1
packages/mermaid/src/diagrams/c4/c4Renderer.ts has 583 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/c4/c4Renderer.ts:1
packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts has 571 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts:1
packages/mermaid-layout-tidy-tree/src/layout.ts has 570 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid-layout-tidy-tree/src/layout.ts:1
packages/mermaid/src/diagrams/timeline/svgDraw.js has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/timeline/svgDraw.js:1
packages/mermaid/src/diagrams/railroad/railroadRenderer.ts has 564 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/railroad/railroadRenderer.ts:1
packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts has 541 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:1
packages/mermaid/src/diagrams/usecase/usecaseDb.ts has 533 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/usecase/usecaseDb.ts:1
packages/mermaid/src/diagrams/git/gitGraphAst.ts has 492 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mermaid/src/diagrams/git/gitGraphAst.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 Coverage9.5 / 10Exemplary✓ 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.
e2e/platform/bundle-test.js:2 imports './mermaid.esm.mjs', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — e2e/platform/bundle-test.js:2
e2e/platform/viewer.js:1 imports './mermaid-example-diagram.esm.mjs', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (3 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — e2e/platform/viewer.js: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. (×26) — scripts/swimlanes-size.ts:1, scripts/tsc-check.ts:1, scripts/verify-diagram/verify.mjs:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
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.
This repository declares test tooling, and the ✓ above records that declaration — but e2e/platform/bundle-test.js and 1 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — e2e/platform/bundle-test.js:2
Do you agree with this assessment?
R7 · Dead Code9.4 / 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.
830 file(s) (~172386 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/mermaid/src/diagrams/radar/db.ts imports '../../../../parser/dist/src/language/generated/ast.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. — packages/mermaid
2 file(s) (~38 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/mermaid-layout-elk/src/plugin.spec.ts imports '../dist/mermaid-layout-elk.core.mjs', 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. — packages/mermaid-layout-elk
75 file(s) (~4535 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/parser/tests/eventmodeling.test.ts imports '../src/language/generated/ast.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. — packages/parser
Unreachable from the 886 application, 18 tooling and 383 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (886 application, 18 tooling, 383 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — vitest.workspace.js
Nothing ultimately consumes this binding: its only referrer is the re-export in packages/mermaid-layout-tidy-tree/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/mermaid-layout-tidy-tree/src/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — packages/mermaid-layout-tidy-tree/src/layouts.ts:13, packages/mermaid-layout-tidy-tree/src/types.ts:67
Nothing ultimately consumes this binding: its only referrer is the re-export in packages/parser/src/language/common/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/parser/src/language/common/index.ts in the same commit, or the barrel will import a name that no longer exists. — packages/parser/src/language/common/tokenBuilder.ts:31
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×7) — e2e/platform/bundle-test.js:10, packages/mermaid/src/diagrams/mindmap/mindmapRenderer.ts:15, packages/mermaid/src/diagrams/sequence/sequenceDiagram.spec.js:88, …
Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used. — packages/mermaid/src/diagrams/class/classDb.ts:514
Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. — packages/mermaid/src/diagrams/xychart/chartBuilder/components/plot/index.ts:27
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
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.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
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 document2.0 / 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.
`sanitize` is exported and takes `options: any` from its caller, and it calls itself at line 267 (`sanitize`) with a piece of `options` — and nowhere in `sanitize` is there a depth parameter, a descent counter, or any other cap. 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sanitize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/mermaid/src/config.ts:267
`sanitizeDirective` is exported and takes `args: any` from its caller, and it calls itself at line 48 (`sanitizeDirective`) with a piece of `args` (and at line 75) — and nowhere in `sanitizeDirective` is there a depth parameter, a descent counter, or any other cap. 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sanitizeDirective` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/mermaid/src/utils/sanitizeDirective.ts:48
`hasTextBesidesImages` is exported and takes `node: Node` from its caller, and it calls itself at line 72 (`hasTextBesidesImages`) with a piece of `node` — and nowhere in `hasTextBesidesImages` is there a depth parameter, a descent counter, or any other cap. 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `hasTextBesidesImages` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/mermaid/src/rendering-util/rendering-elements/shapes/labelImageUtils.ts:72
`collectDescendantIds` is exported and takes `elkNode: any` from its caller, and it calls itself at line 1380 (`collectDescendantIds`) with a piece of `elkNode` — and nowhere in `collectDescendantIds` is there a depth parameter, a descent counter, or any other cap. 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `collectDescendantIds` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1380
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.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
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/3 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.
`download` 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 })`. — packages/mermaid/src/docs/.vitepress/scripts/fetch-avatars.ts:12
`fetchContributors` 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 })`. — packages/mermaid/src/docs/.vitepress/scripts/fetch-contributors.ts:14
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 a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. 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.
`trace` at line 74 is called with an argument built by `JSON.stringify(node)` (line 74), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/rendering-util/rendering-elements/clusters.js:74
`trace` at line 357 is called with an argument built by `JSON.stringify(node)` (line 357), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/rendering-util/rendering-elements/clusters.js:357
`debug` at line 414 is called with an argument built by `JSON.stringify(outsidePoint)` (line 415), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/rendering-util/rendering-elements/edges.js:414
`debug` at line 714 is called with an argument built by `JSON.stringify(points, null, 2)` (line 717), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/rendering-util/rendering-elements/edges.js:714
`trace` at line 226 is called with an argument built by `JSON.stringify(node)` (line 226), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/rendering-util/rendering-elements/clusters/swimlane.js:226
`debug` at line 1496 is called with an argument built by `JSON.stringify(issues.slice(0, 50))` (line 1502), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:1496
`debug` at line 2491 is called with an argument built by `JSON.stringify(points)` (line 2493), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:2491
`debug` at line 2556 is called with an argument built by `JSON.stringify(clippedPoints)` (line 2556), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:2556
`debug` at line 269 is called with an argument built by `JSON.stringify(e)` (line 269), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:269
`debug` at line 270 is called with an argument built by `JSON.stringify(graph.edge(e))` (line 270), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:270
`debug` at line 265 is called with an argument built by `JSON.stringify(graph.node(v))` (line 265), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/state/stateRenderer.js:265
`debug` at line 273 is called with an argument built by `JSON.stringify(graph.edge(e))` (line 273), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/state/stateRenderer.js:273
`debug` at line 387 is called with an argument built by `JSON.stringify(message)` (line 387), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/sequence/sequenceDb.ts:387
`debug` at line 427 is called with an argument built by `label.join(' ')` (line 427), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/git/gitGraphAst.ts:427
`debug` at line 210 is called with an argument built by `JSON.stringify(classRelation)` (line 210), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/class/classDb.ts:210
`debug` at line 211 is called with an argument built by `JSON.stringify(note)` (line 211), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/class/classRenderer.js:211
`debug` at line 242 is called with an argument built by `JSON.stringify(g.node(v))` (line 242), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/class/classRenderer.js:242
`debug` at line 258 is called with an argument built by `JSON.stringify(g.edge(e))` (line 258), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/class/classRenderer.js:258
`debug` at line 89 is called with an argument built by `JSON.stringify(cardinality_1_point)` (line 89), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/class/svgDraw.js:89
`debug` at line 90 is called with an argument built by `JSON.stringify(cardinality_2_point)` (line 90), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/class/svgDraw.js:90
`debug` at line 578 is called with an argument built by `JSON.stringify(conf, null, 2)` (line 578), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/c4/c4Renderer.ts:578
`debug` at line 112 is called with an argument built by `JSON.stringify(child.size)` (line 113), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/block/layout.ts:112
`debug` at line 362 is called with an argument built by `JSON.stringify(root, null, 2)` (line 362), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/mermaid/src/diagrams/block/layout.ts:362
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped5.8 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`result.innerSvg` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/mermaid-zenuml/src/zenumlRenderer.ts:81
`svg` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/mermaid/src/mermaid.ts:186
`rules` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:606
`html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/mermaid/src/utils.ts:777
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
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.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — packages/mermaid/src/profiler.ts:198, packages/mermaid/src/profiler.ts:230, packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:711
What to do
Swallowed exception (empty catch)
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 strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
9/13 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~4.3 `!` null assertions per 1k TypeScript source lines — 391 assertion(s) across the 91890 source line(s) of the 567 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts (66), packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts (55), packages/mermaid/src/diagrams/c4/c4Renderer.ts (23). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 50 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's 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 — Not applicable: 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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — time="2026-10-26T11:38:43Z" level=warning msg="The \"MERMAID_PORT\" variable is not set. Defaulting to a blank string." time="2026-10-26T11:38:43Z" level=warning msg="The \"MERMAID_PORT\" variable is not set. Defaulting to a blank string." no port specified: :<empty>; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .mts, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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 (.html,.js,.mts,.ts), 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.
D32 Data Compliance (PII/GDPR) — 9 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.mts, .ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript 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 data present for 480 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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 applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Orphaned knowledge packages/mermaid/src/diagrams/er/erRenderer.js:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/mermaid/src/diagrams/sequence/sequenceDb.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC2 · Forms & labels· <input> without a programmatic label · ×2
<input> without a programmatic label .esbuild/dev-explorer/diagram-viewer.ts:1644— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label packages/mermaid-local-editor/static/index.html:18— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
D10 · Test Quality· No assertions (empty test) · ×2
No assertions (empty test): should limit the number of relationships between the same two entities packages/mermaid/src/diagrams/er/parser/erDiagram.spec.js:575— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should not allow multiple relationships between the same two entities unless the roles are different packages/mermaid/src/diagrams/er/parser/erDiagram.spec.js:579— Test method has an empty body — it asserts nothing and exercises no code.
AC2 · Forms & labels· <select> without a programmatic label · ×1
<select> without a programmatic label packages/mermaid-local-editor/static/index.html:17— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label packages/mermaid-local-editor/static/index.html:27— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<html> without a lang scripts/verify-diagram/verify.mjs:113— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> scripts/verify-diagram/verify.mjs:113— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
No assertions: should add to mermaid packages/mermaid-layout-elk/src/plugin.spec.ts:13— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: should handle an example-diagram definition packages/mermaid-example-diagram/src/exampleDiagram.spec.js:22— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: should return a valid style for an empty type packages/mermaid/src/styles.spec.ts:72— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: should return a valid style for diagram ${diagramId} and theme ${themeId} packages/mermaid/src/styles.spec.ts:109— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: (unnamed test) packages/mermaid/src/tests/util.ts:89— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: "${diagramId}" — two identical diagrams produce no duplicate element IDs packages/mermaid/src/rendering-util/multi-diagram-id-uniqueness.spec.ts:288— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: every registered diagram type has a uniqueness test or is explicitly excluded packages/mermaid/src/rendering-util/multi-diagram-id-uniqueness.spec.ts:350— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Level 2: validateLayout — quality breakdown is within reasonable thresholds packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/5-car-fun-sales-wide-tb.ddlt.spec.ts:200— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Level 2: validateLayout — quality breakdown baseline packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/6-legal-constr-sales.ddlt.spec.ts:114— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Level 2: validateLayout — quality breakdown is within reasonable thresholds packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/7-car-sales-constr.ddlt.spec.ts:87— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Level 2: validateLayout — quality breakdown is within reasonable thresholds packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/8-query-process-2.ddlt.spec.ts:233— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Level 2: validateLayout — quality breakdown is within reasonable thresholds packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/query-process.ddlt.spec.ts:173— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Level 2: validateLayout — quality breakdown is within reasonable thresholds packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/simple-2.ddlt.spec.ts:137— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: super simple packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:17— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: should handle relation definitions packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:61— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: hide empty description packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:74— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: handle "as" in state names packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:89— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: handle "as" in state names 1 packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:97— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: handle "as" in state names 2 packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:105— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: handle "as" in state names 3 packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:113— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: scale packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:144— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: description after second state packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:159— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: shall handle descriptions including minus signs packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:168— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: should handle state statements packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:177— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: should handle recursive state definitions packages/mermaid/src/diagrams/state/stateDiagram-v2.spec.js:189— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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.
TodoComment scripts/tsc-check.ts:63— // TODO: these don't import cleanly yet due to exotic tsconfig.json requirements — 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 packages/mermaid-zenuml/src/mermaidUtils.ts:4— // Todo remove debug code — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/mermaid-example-diagram/src/mermaidUtils.ts:3— // Todo remove debug code — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/mermaid-example-diagram/src/diagram-definition.ts:1— // @ts-ignore: TODO Fix ts errors — 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 packages/mermaid/src/diagrams/xychart/xychartRenderer.ts:40— // @ts-ignore: TODO Fix ts errors — 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 packages/mermaid/src/diagrams/quadrant-chart/quadrantRenderer.ts:56— // @ts-ignore: TODO Fix ts errors — 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 packages/mermaid/src/diagrams/quadrant-chart/quadrantRenderer.ts:58— // @ts-ignore: TODO Fix ts errors — 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 packages/mermaid/src/diagrams/quadrant-chart/quadrantRenderer.ts:61— // @ts-ignore: TODO Fix ts errors — 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 packages/mermaid/src/defaultConfig.ts:21— // TODO: Should we replace these with `null` so that they can go in the JSON Schema? — 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 packages/mermaid/src/mermaid.ts:198— // TODO: We should be throwing an error object. — 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 packages/mermaid/src/mermaidAPI.spec.ts:343— // @todo TODO Can't figure out how to spy on the cssImportantStyles method. — 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 packages/mermaid/src/mermaidAPI.spec.ts:383— // TODO Can't figure out how to spy on the cssImportantStyles method. That would be a much better approach than manually checking the result. — 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 packages/mermaid/src/mermaidAPI.spec.ts:412— // @todo TODO if a single function in the module can be mocked, do it for createCssStyles and mock the results. — 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 packages/mermaid/src/mermaidAPI.spec.ts:876— // { textDiagramType: 'C4Context', expectedType: 'c4' }, TODO : setAccTitle not called in C4 jison parser — 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 REDACTED:5— // @ts-ignore TODO: Investigate D3 issue — 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 packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:8— // @ts-ignore TODO: Investigate D3 issue — 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 REDACTED:151— // sanitized by the sanitize CSS function TODO where is this method? what should be used to replace it? refactor so that it's always sanitized — 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 REDACTED:169— // TODO make a constant — 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 REDACTED:170— // TODO make a constant — 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 REDACTED:722— // Todo merge with user options — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/mermaid/src/styles.spec.ts:48— // TODO: I'm pretty sure that even in SVG2, this isn't allowed to be a CSS — 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 packages/mermaid/src/utils.ts:236— // @ts-ignore TODO: Fix issue with curve type — 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 packages/mermaid/src/utils.ts:719— // @ts-ignore TODO: Fix D3 types — 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 packages/mermaid/src/utils.ts:721— // @ts-ignore TODO: Fix D3 types — 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 packages/mermaid/src/utils.ts:758— // TODO: Seed is only used for length? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FunctionTooLong: router.routeEdgesOrthogonal packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts:122— FunctionTooLong — routeEdgesOrthogonal runs 1264 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1164 over it, 12.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wardleyRenderer.draw packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts:67— FunctionTooLong — draw runs 759 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 659 over it, 7.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: materializedGeometry.resolveRenderedOrthogonalCrossings packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1835— FunctionTooLong — resolveRenderedOrthogonalCrossings runs 715 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 615 over it, 7.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: validateLayout.validateLayout packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:604— FunctionTooLong — validateLayout runs 550 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 450 over it, 5.50× 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: ganttRenderer.draw packages/mermaid/src/diagrams/gantt/ganttRenderer.js:85— FunctionTooLong — draw runs 519 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 419 over it, 5.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.
FunctionTooLong: renderer.draw packages/mermaid/src/diagrams/treemap/renderer.ts:24— FunctionTooLong — draw runs 362 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 262 over it, 3.62× 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: sequenceRenderer.draw packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1043— FunctionTooLong — draw runs 339 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 239 over it, 3.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: materializedGeometry.reassignCrossingExternalRailChannels packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1210— FunctionTooLong — reassignCrossingExternalRailChannels runs 268 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 168 over it, 2.68× 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: cynefinRenderer.draw packages/mermaid/src/diagrams/cynefin/cynefinRenderer.ts:71— FunctionTooLong — draw runs 265 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 165 over it, 2.65× 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: labelAnchoring.anchorLabelsToPolyline packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/labelAnchoring.ts:83— FunctionTooLong — anchorLabelsToPolyline runs 244 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 144 over it, 2.44× 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: edges.insertEdge packages/mermaid/src/rendering-util/rendering-elements/edges.js:624— FunctionTooLong — insertEdge runs 244 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 144 over it, 2.44× 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: erBox.erBox packages/mermaid/src/rendering-util/rendering-elements/shapes/erBox.ts:19— FunctionTooLong — erBox runs 230 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 130 over it, 2.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: materializedGeometry.separateSharedRenderedTerminalLanes packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:45— FunctionTooLong — separateSharedRenderedTerminalLanes runs 217 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 117 over it, 2.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sequenceRenderer.drawMessage packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:461— FunctionTooLong — drawMessage runs 215 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sharedTrackNudging.nudgeSharedInteriorSubpaths packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/sharedTrackNudging.ts:13— FunctionTooLong — nudgeSharedInteriorSubpaths runs 213 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× 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: usecaseDb.getData packages/mermaid/src/diagrams/usecase/usecaseDb.ts:295— FunctionTooLong — getData runs 188 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× 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: classBox.classBox packages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts:14— FunctionTooLong — classBox runs 188 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× 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: detourSimplification.simplifyDetouredEdges packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/detourSimplification.ts:20— FunctionTooLong — simplifyDetouredEdges runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× 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: materializedGeometry.shortcutRedundantOrthogonalJogs packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1587— FunctionTooLong — shortcutRedundantOrthogonalJogs runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: pieRenderer.draw packages/mermaid/src/diagrams/pie/pieRenderer.ts:33— FunctionTooLong — draw runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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: erRenderer.drawAttributes packages/mermaid/src/diagrams/er/erRenderer.js:45— FunctionTooLong — drawAttributes runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: timelineRenderer.draw packages/mermaid/src/diagrams/timeline/timelineRenderer.ts:29— FunctionTooLong — draw runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: layoutCore.layoutContainer packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts:61— FunctionTooLong — layoutContainer runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: vennRenderer.draw packages/mermaid/src/diagrams/venn/vennRenderer.ts:31— FunctionTooLong — draw runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: swimlane.swimlane packages/mermaid/src/rendering-util/rendering-elements/clusters/swimlane.js:16— FunctionTooLong — swimlane runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Hotspot: packages/mermaid/src/themes/theme-redux-color.js packages/mermaid/src/themes/theme-redux-color.js:106— packages/mermaid/src/themes/theme-redux-color.js changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 195 in Theme.updateColors at line 106. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/themes/theme-redux-color.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mermaid/src/themes/theme-redux-dark-color.js packages/mermaid/src/themes/theme-redux-dark-color.js:108— packages/mermaid/src/themes/theme-redux-dark-color.js changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 192 in Theme.updateColors at line 108. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/themes/theme-redux-dark-color.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mermaid/src/themes/theme-neo.js packages/mermaid/src/themes/theme-neo.js:52— packages/mermaid/src/themes/theme-neo.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 213 in Theme.updateColors at line 52. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/themes/theme-neo.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mermaid/src/themes/theme-redux.js packages/mermaid/src/themes/theme-redux.js:58— packages/mermaid/src/themes/theme-redux.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 202 in Theme.updateColors at line 58. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/themes/theme-redux.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mermaid/src/themes/theme-neo-dark.js packages/mermaid/src/themes/theme-neo-dark.js:68— packages/mermaid/src/themes/theme-neo-dark.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 213 in Theme.updateColors at line 68. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/themes/theme-neo-dark.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mermaid/src/themes/theme-redux-dark.js packages/mermaid/src/themes/theme-redux-dark.js:76— packages/mermaid/src/themes/theme-redux-dark.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 213 in Theme.updateColors at line 76. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/themes/theme-redux-dark.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1945— packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in render.applyElkEdgeLayout at line 1945. 17 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts`: 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: packages/mermaid/src/rendering-util/rendering-elements/edges.js packages/mermaid/src/rendering-util/rendering-elements/edges.js:624— packages/mermaid/src/rendering-util/rendering-elements/edges.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 70 in edges.insertEdge at line 624. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/rendering-elements/edges.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mermaid/src/diagrams/agentflow/agentflowDb.ts packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:347— packages/mermaid/src/diagrams/agentflow/agentflowDb.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in AgentFlowDB.addVertex at line 347. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/agentflow/agentflowDb.ts`: 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: packages/mermaid/src/diagrams/flowchart/flowDb.ts packages/mermaid/src/diagrams/flowchart/flowDb.ts:1110— packages/mermaid/src/diagrams/flowchart/flowDb.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in FlowDB.getData at line 1110. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/flowchart/flowDb.ts`: 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:477— REDACTED changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in mermaidAPI.renderDiagram at line 477. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00: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: REDACTED REDACTED:516— REDACTED changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in svgDraw.drawActorTypeCollections at line 516. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00: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: packages/mermaid/src/diagrams/usecase/usecaseDb.ts packages/mermaid/src/diagrams/usecase/usecaseDb.ts:295— packages/mermaid/src/diagrams/usecase/usecaseDb.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in usecaseDb.getData at line 295. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/usecase/usecaseDb.ts`: 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: packages/mermaid/src/rendering-util/rendering-elements/shapes/util.ts packages/mermaid/src/rendering-util/rendering-elements/shapes/util.ts:50— packages/mermaid/src/rendering-util/rendering-elements/shapes/util.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in util.labelHelper at line 50. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/rendering-elements/shapes/util.ts`: 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: packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:848— packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in materializedGeometry.shiftLeftLaneTitleBandsLeftOfRails at line 848. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts`: 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: packages/mermaid/src/diagrams/state/dataFetcher.ts packages/mermaid/src/diagrams/state/dataFetcher.ts:241— packages/mermaid/src/diagrams/state/dataFetcher.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in dataFetcher.dataFetcher at line 241. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/state/dataFetcher.ts`: 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: packages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts packages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts:14— packages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in classBox.classBox at line 14. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts`: 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: packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts:61— packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in layoutCore.layoutContainer at line 61. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts`: 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: packages/mermaid/src/diagrams/block/renderHelpers.ts packages/mermaid/src/diagrams/block/renderHelpers.ts:16— packages/mermaid/src/diagrams/block/renderHelpers.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in renderHelpers.getNodeFromBlock at line 16. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/block/renderHelpers.ts`: 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: packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts:646— packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in lineJump.applyLineJumpsToSvg at line 646. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts`: 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: scripts/e2e-diagram-scope.mjs scripts/e2e-diagram-scope.mjs:167— scripts/e2e-diagram-scope.mjs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in e2e-diagram-scope.detectScope at line 167. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- scripts/e2e-diagram-scope.mjs`: 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: packages/mermaid/src/diagrams/usecase/usecaseRenderer.ts packages/mermaid/src/diagrams/usecase/usecaseRenderer.ts:144— packages/mermaid/src/diagrams/usecase/usecaseRenderer.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in usecaseRenderer.annotateUsecaseElements at line 144. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/usecase/usecaseRenderer.ts`: 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: packages/mermaid/src/diagrams/c4/c4Db.ts packages/mermaid/src/diagrams/c4/c4Db.ts:86— packages/mermaid/src/diagrams/c4/c4Db.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in c4Db.addRel at line 86. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/c4/c4Db.ts`: 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: packages/mermaid/src/diagrams/venn/vennRenderer.ts packages/mermaid/src/diagrams/venn/vennRenderer.ts:31— packages/mermaid/src/diagrams/venn/vennRenderer.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in vennRenderer.draw at line 31. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/venn/vennRenderer.ts`: 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: packages/mermaid/src/diagrams/block/blockDB.ts packages/mermaid/src/diagrams/block/blockDB.ts:105— packages/mermaid/src/diagrams/block/blockDB.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in blockDB.populateBlockDatabase at line 105. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/block/blockDB.ts`: 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.
+ 4 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×26
No test reaches this file scripts/swimlanes-size.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 scripts/tsc-check.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 scripts/verify-diagram/verify.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 packages/mermaid-layout-tidy-tree/src/render.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 packages/mermaid-local-editor/static/js/ui.js: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 packages/mermaid-local-editor/static/js/navigation.js: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 scripts/size.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 packages/mermaid-local-editor/static/app.js: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 packages/mermaid-example-diagram/src/exampleDiagramRenderer.js: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 scripts/argos-upload-sheets.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 scripts/screenshot-order.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 packages/parser/scripts/prepack.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 scripts/run-e2e-scoped.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 packages/mermaid-local-editor/static/js/storage.js: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 scripts/jison/lint.mts: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 scripts/fixCSpell.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 packages/mermaid-example-diagram/src/styles.js: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 packages/mermaid-local-editor/static/js/config.js: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 packages/mermaid-example-diagram/src/detector.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 packages/mermaid-zenuml/src/detector.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 scripts/coverage.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 packages/mermaid-zenuml/src/zenuml-definition.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 packages/mermaid-layout-tidy-tree/src/layouts.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 packages/mermaid-zenuml/src/parser.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.
FileTooLong: direction/materializedGeometry.ts packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts— FileTooLong — 1996 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1496 over it, 3.99× 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: elk/render.ts packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts— FileTooLong — 1742 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1242 over it, 3.48× 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: REDACTED REDACTED— FileTooLong — 1528 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 1028 over it, 3.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: sequence/sequenceRenderer.ts packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts— FileTooLong — 1509 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1009 over it, 3.02× 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: agentflow/agentflowDb.ts packages/mermaid/src/diagrams/agentflow/agentflowDb.ts— FileTooLong — 1450 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: AgentFlowDB (213-2492). The bar is 500 significant lines; this is 950 over it, 2.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: orthogonalRouter/router.ts packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts— FileTooLong — 1334 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: routeEdgesOrthogonal (122-2283). The bar is 500 significant lines; this is 834 over it, 2.67× 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: git/gitGraphRenderer.ts packages/mermaid/src/diagrams/git/gitGraphRenderer.ts— FileTooLong — 1096 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 596 over it, 2.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: rendering-elements/markers.js packages/mermaid/src/rendering-util/rendering-elements/markers.js— FileTooLong — 939 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 439 over it, 1.88× 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-utils/validateLayout.ts packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts— FileTooLong — 896 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: validateLayout (604-1506). The bar is 500 significant lines; this is 396 over it, 1.79× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: flowchart/flowDb.ts packages/mermaid/src/diagrams/flowchart/flowDb.ts— FileTooLong — 850 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: FlowDB (38-1349). The bar is 500 significant lines; this is 350 over it, 1.70× 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: parser/usecaseModelBuilder.ts packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts— FileTooLong — 817 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: UsecaseModelBuilder (172-1050). The bar is 500 significant lines; this is 317 over it, 1.63× 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: wardley/wardleyRenderer.ts packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts— FileTooLong — 813 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: draw (67-1067). The bar is 500 significant lines; this is 313 over it, 1.63× 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: parser/usecase.visitor.ts packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts— FileTooLong — 774 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: UsecaseVisitor (68-975). The bar is 500 significant lines; this is 274 over it, 1.55× 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: rendering-elements/edges.js packages/mermaid/src/rendering-util/rendering-elements/edges.js— FileTooLong — 750 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 250 over it, 1.50× 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: dagre/index.js packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js— FileTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 78 over it, 1.16× 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: gantt/ganttRenderer.js packages/mermaid/src/diagrams/gantt/ganttRenderer.js— FileTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: draw (85-900). The bar is 500 significant lines; this is 78 over it, 1.16× 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: rendering-elements/clusters.js packages/mermaid/src/rendering-util/rendering-elements/clusters.js— FileTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 76 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: c4/c4Db.ts packages/mermaid/src/diagrams/c4/c4Db.ts— FileTooLong — 573 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 73 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: class/classDb.ts packages/mermaid/src/diagrams/class/classDb.ts— FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: ClassDB (37-884). The bar is 500 significant lines; this is 62 over it, 1.12× 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/utils.ts packages/mermaid/src/utils.ts— FileTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 44 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: sequence/sequenceDb.ts packages/mermaid/src/diagrams/sequence/sequenceDb.ts— FileTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: SequenceDB (115-729). The bar is 500 significant lines; this is 43 over it, 1.09× 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: gantt/ganttDb.js packages/mermaid/src/diagrams/gantt/ganttDb.js— FileTooLong — 541 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 41 over it, 1.08× 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: state/stateDb.ts packages/mermaid/src/diagrams/state/stateDb.ts— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), about 68% of them inside a single declaration: StateDB (211-790). The bar is 500 significant lines; this is 8 over it, 1.02× 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.
Boundary violation [package:third-party-deep-import] packages/mermaid/scripts/create-types-from-json-schema.mts:13— packages/mermaid/scripts/create-types-from-json-schema.mts:13 imports ajv/dist/2019.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/scripts/docs.mts:32— packages/mermaid/scripts/docs.mts:32 imports @adobe/jsonschema2md/lib/schemaProxy.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/scripts/docs.mts:34— packages/mermaid/scripts/docs.mts:34 imports @adobe/jsonschema2md/lib/traverseSchema.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/scripts/docs.mts:36— packages/mermaid/scripts/docs.mts:36 imports @adobe/jsonschema2md/lib/markdownBuilder.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/scripts/docs.mts:38— packages/mermaid/scripts/docs.mts:38 imports @adobe/jsonschema2md/lib/readmeBuilder.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/diagrams/block/renderHelpers.ts:1— packages/mermaid/src/diagrams/block/renderHelpers.ts:1 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/diagrams/class/classRenderer.js:2— packages/mermaid/src/diagrams/class/classRenderer.js:2 imports dagre-d3-es/src/dagre/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/diagrams/class/classRenderer.js:3— packages/mermaid/src/diagrams/class/classRenderer.js:3 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/diagrams/er/erRenderer.js:1— packages/mermaid/src/diagrams/er/erRenderer.js:1 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/diagrams/er/erRenderer.js:3— packages/mermaid/src/diagrams/er/erRenderer.js:3 imports dagre-d3-es/src/dagre/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/diagrams/flowchart/flowChartShapes.js:1— packages/mermaid/src/diagrams/flowchart/flowChartShapes.js:1 imports dagre-d3-es/src/dagre-js/intersect/intersect-polygon.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/diagrams/flowchart/flowChartShapes.js:2— packages/mermaid/src/diagrams/flowchart/flowChartShapes.js:2 imports dagre-d3-es/src/dagre-js/intersect/intersect-rect.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/diagrams/state/stateRenderer.js:2— packages/mermaid/src/diagrams/state/stateRenderer.js:2 imports dagre-d3-es/src/dagre/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/diagrams/state/stateRenderer.js:3— packages/mermaid/src/diagrams/state/stateRenderer.js:3 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/rendering-util/createGraph.ts:2— packages/mermaid/src/rendering-util/createGraph.ts:2 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:2— packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:2 imports dagre-d3-es/src/dagre/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:3— packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:3 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:3— packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:3 imports dagre-d3-es/src/graphlib/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:10— packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:10 imports elkjs/lib/elk.bundled.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:test-suite-dependency] scripts/argos-upload-sheets.ts:15— scripts/argos-upload-sheets.ts:15 imports e2e/helpers/argos-metadata.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] scripts/screenshot-order.ts:20— scripts/screenshot-order.ts:20 imports e2e/helpers/argos-metadata.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] scripts/screenshot-sheets.ts:18— scripts/screenshot-sheets.ts:18 imports e2e/helpers/argos-metadata.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
MethodTooLong: UsecaseParser.constructor packages/mermaid/src/diagrams/usecase/parser/usecase.parser.ts:134— MethodTooLong — constructor runs 340 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 240 over it, 3.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: Theme.updateColors packages/mermaid/src/themes/theme-base.js:32— MethodTooLong — updateColors runs 333 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 233 over it, 3.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: Theme.updateColors packages/mermaid/src/themes/theme-forest.js:113— MethodTooLong — updateColors runs 272 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 172 over it, 2.72× 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: Theme.updateColors packages/mermaid/src/themes/theme-default.js:146— MethodTooLong — updateColors runs 269 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 169 over it, 2.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Theme.updateColors packages/mermaid/src/themes/theme-redux-dark.js:76— MethodTooLong — updateColors runs 268 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 168 over it, 2.68× 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: Theme.updateColors packages/mermaid/src/themes/theme-neo.js:52— MethodTooLong — updateColors runs 261 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 161 over it, 2.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: Theme.updateColors packages/mermaid/src/themes/theme-dark.js:115— MethodTooLong — updateColors runs 259 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Theme.updateColors packages/mermaid/src/themes/theme-redux.js:58— MethodTooLong — updateColors runs 259 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Theme.updateColors packages/mermaid/src/themes/theme-neo-dark.js:68— MethodTooLong — updateColors runs 258 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 158 over it, 2.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Theme.updateColors packages/mermaid/src/themes/theme-redux-dark-color.js:108— MethodTooLong — updateColors runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.55× 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: Theme.updateColors packages/mermaid/src/themes/theme-neutral.js:128— MethodTooLong — updateColors runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× 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: Theme.updateColors packages/mermaid/src/themes/theme-redux-color.js:106— MethodTooLong — updateColors runs 246 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× 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: AgentFlowDB.getData packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1696— MethodTooLong — getData runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× 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: SequenceDB.apply packages/mermaid/src/diagrams/sequence/sequenceDb.ts:557— MethodTooLong — apply runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× 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: FlowDB.getData packages/mermaid/src/diagrams/flowchart/flowDb.ts:1110— MethodTooLong — getData runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: Theme.constructor packages/mermaid/src/themes/theme-default.js:9— MethodTooLong — constructor runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: ClassDB.getData packages/mermaid/src/diagrams/class/classDb.ts:748— MethodTooLong — getData runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Skipped test: markdownToLines - No auto wrapping packages/mermaid/src/rendering-util/handle-markdown-text.spec.ts:207— Skipped — switched off by test.skip
Skipped test: continues reroute scanning against current edge points after each fix packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/__tests__/postProcessing.spec.ts:83— Skipped — switched off by it.skip
Skipped test: should handle if statements packages/mermaid/src/diagrams/state/stateDiagram.spec.js:384— Skipped — switched off by it.skip
Skipped test: should reset a branch packages/mermaid/src/diagrams/git/gitGraph.spec.ts:92— Skipped — switched off by it.skip
Skipped test: reset can take an argument packages/mermaid/src/diagrams/git/gitGraph.spec.ts:111— Skipped — switched off by it.skip
Skipped test: should handle fast forwardable merges packages/mermaid/src/diagrams/git/gitGraph.spec.ts:131— Skipped — switched off by it.skip
Skipped test: should handle ff merge when history walk has two parents (merge commit) packages/mermaid/src/diagrams/git/gitGraph.spec.ts:191— Skipped — switched off by it.skip
Skipped test: it should handle huge diagrams packages/mermaid/src/diagrams/flowchart/parser/flow-huge.spec.js:17— Skipped — switched off by it.skip
Skipped test: should be possible to use @ syntax to add labels with trail spaces packages/mermaid/src/diagrams/flowchart/parser/flow-node-data.spec.js:403— Skipped — switched off by it.skip
Skipped test: should handle subgraph without id and space in title packages/mermaid/src/diagrams/flowchart/parser/subgraph.spec.js:64— Skipped — switched off by it.skip
Skipped test: [skipped test] can contain àáâäæãåā packages/mermaid/src/diagrams/er/parser/erDiagram.spec.js:124— Skipped — switched off by it.skip
Skipped test: should handle a leading newline packages/mermaid/src/diagrams/class/classDiagram.spec.ts:293— Skipped — switched off by it.skip
Skipped test: should handle arrowMarkerAbsolute explicitly set to "false" as false e2e/other/pr-check/configuration.spec.js:55— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/other/pr-check/dev-explorer-compare.spec.ts:11— Skipped — switched off by test.skip
Repeated repair: packages/mermaid/src/rendering-util/layout-algorithms/common/index.ts packages/mermaid/src/rendering-util/layout-algorithms/common/index.ts:108— packages/mermaid/src/rendering-util/layout-algorithms/common/index.ts changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is index.createCommonLayoutRenderer at line 108), 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 label overlap bug”; “fix(class): centre end cardinalities like start ones”; “fix(class): place cardinality labels beside their ends with the ELK layout”; “fix(rendering): clip an edge for the engine that drew it”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/layout-algorithms/common/index.ts`: 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: packages/mermaid/src/diagrams/flowchart/styles.ts packages/mermaid/src/diagrams/flowchart/styles.ts:49— packages/mermaid/src/diagrams/flowchart/styles.ts changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is styles.genColor at line 49), 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(themes): fill handDrawn lane bodies, and pin tsc-check's floating deps”; “fix(themes): emit a palette rule for every slot that can be stamped”; “fix(flowchart): give subgraph colour slots real source order, and close two seams”; “fix(themes): address review on class and flowchart palette”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/flowchart/styles.ts`: 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: packages/mermaid/src/diagrams/er/styles.ts packages/mermaid/src/diagrams/er/styles.ts:64— packages/mermaid/src/diagrams/er/styles.ts changed 5 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is styles.getStyles at line 64), 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: “refactor: hand the ER/requirement CSS-generation fixes to a standalone PR”; “fix(themes): validate look in the ER and requirement stylesheets”; “fix(themes): clear four pre-existing defects the default flip makes visible”; “fix(er): guard an empty border palette, and tighten the palette CSS spec”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/er/styles.ts`: 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: packages/mermaid/src/rendering-util/rendering-elements/shapes/usecaseActor.ts packages/mermaid/src/rendering-util/rendering-elements/shapes/usecaseActor.ts:154— packages/mermaid/src/rendering-util/rendering-elements/shapes/usecaseActor.ts changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is usecaseActor.renderUsecaseActor at line 154), 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(usecase): address PR review feedback”; “fix: render actor stereotypes once”; “fix: refine business diagram markers”; “fix: align use case HTML labels”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/rendering-elements/shapes/usecaseActor.ts`: 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: packages/mermaid/src/diagrams/common/colorThemeGate.ts packages/mermaid/src/diagrams/common/colorThemeGate.ts:86— packages/mermaid/src/diagrams/common/colorThemeGate.ts changed 6 times in last 90 days and 4 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 colorThemeGate.colorSlotCount at line 86), 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(themes): derive the slot count from the palette, not from a bound”; “fix(themes): keep colorSlotCount's result usable as a loop bound”; “fix(themes): emit a palette rule for every slot that can be stamped”; “fix(flowchart): give subgraph colour slots real source order, and close two seams”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/common/colorThemeGate.ts`: 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: packages/mermaid/src/rendering-util/createGraph.ts packages/mermaid/src/rendering-util/createGraph.ts:123— packages/mermaid/src/rendering-util/createGraph.ts changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is createGraph.createGraphWithElements at line 123), 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: orient fork/join bars by flow direction under ELK layout”; “fix: restore edgePaths class on the edge group (#8125)”; “fix(rendering-util): use the generated DOM id for container clusters, and let layouts ask how to measure cluster labels”; “fix(rendering-util): measure ELK cluster labels unwrapped”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/createGraph.ts`: 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: packages/mermaid/src/diagrams/block/styles.ts packages/mermaid/src/diagrams/block/styles.ts:41— packages/mermaid/src/diagrams/block/styles.ts changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is styles.genColor at line 41), 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(block): take the node border width from the theme”; “fix(block): colour composites only, matching the flowchart”; “fix(block): apply the redux colour palette to block diagrams”; “fix: restore edgePaths class on the edge group (#8125)”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/block/styles.ts`: 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: packages/mermaid/src/rendering-util/rendering-elements/shapes/question.ts packages/mermaid/src/rendering-util/rendering-elements/shapes/question.ts:20— packages/mermaid/src/rendering-util/rendering-elements/shapes/question.ts changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is question.question at line 20), 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(flowchart): size non-rectangular shapes from the label's height too”; “fix(flowchart): preserve stadium caps and exempt selected shapes from label wrapping”; “fix(elk): address review on #8152”; “fix(rendering): drop the half-pixel bias in intersectLine”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/rendering-elements/shapes/question.ts`: 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: packages/mermaid/src/diagrams/requirement/styles.js packages/mermaid/src/diagrams/requirement/styles.js:50— packages/mermaid/src/diagrams/requirement/styles.js changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is styles.getStyles at line 50), 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: “refactor: hand the ER/requirement CSS-generation fixes to a standalone PR”; “fix(themes): validate look in the ER and requirement stylesheets”; “fix(themes): clear four pre-existing defects the default flip makes visible”; “fix(er, requirement): stop emitting invalid CSS for the colour-theme palettes”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/requirement/styles.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/mermaid/src/rendering-util/rendering-elements/shapes/usecaseBusiness.ts packages/mermaid/src/rendering-util/rendering-elements/shapes/usecaseBusiness.ts:34— packages/mermaid/src/rendering-util/rendering-elements/shapes/usecaseBusiness.ts 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 9 (its worst body is usecaseBusiness.usecaseBusiness at line 34), 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(usecase): keep association markers apart on use-case ovals under ELK”; “fix(usecase): address PR review feedback”; “fix: refine business diagram markers”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/rendering-elements/shapes/usecaseBusiness.ts`: 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: packages/mermaid/src/diagrams/usecase/styles.ts packages/mermaid/src/diagrams/usecase/styles.ts:75— packages/mermaid/src/diagrams/usecase/styles.ts 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 styles.genColor at line 75), 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(usecase): stamp a rect colour slot only where one was assigned”; “fix(usecase): derive boundary colors from theme variables”; “fix: refine use case diagram rendering”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/diagrams/usecase/styles.ts`: 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: packages/mermaid/src/rendering-util/rendering-elements/clusters/swimlane.js packages/mermaid/src/rendering-util/rendering-elements/clusters/swimlane.js:16— packages/mermaid/src/rendering-util/rendering-elements/clusters/swimlane.js changed 4 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 12 (its worst body is swimlane.swimlane at line 16), 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(clusters): scope a swimlane's DOM id like every other cluster”; “fix(handdrawn): tighten the hachure fill so shapes read as filled, not striped”; “fix(themes): fill handDrawn lane bodies, and pin tsc-check's floating deps”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/rendering-elements/clusters/swimlane.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/mermaid/src/rendering-util/rendering-elements/shapes/circle.ts packages/mermaid/src/rendering-util/rendering-elements/shapes/circle.ts:10— packages/mermaid/src/rendering-util/rendering-elements/shapes/circle.ts changed 3 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 circle.circle at line 10), 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(flowchart): size circles from their label, not minNodeWidth”; “fix(flowchart): size non-rectangular shapes from the label's height too”; “fix(flowchart): preserve stadium caps and exempt selected shapes from label wrapping”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/rendering-elements/shapes/circle.ts`: 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: packages/mermaid/src/rendering-util/rendering-elements/shapes/doubleCircle.ts packages/mermaid/src/rendering-util/rendering-elements/shapes/doubleCircle.ts:10— packages/mermaid/src/rendering-util/rendering-elements/shapes/doubleCircle.ts changed 3 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 5 (its worst body is doubleCircle.doublecircle at line 10), 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(flowchart): size circles from their label, not minNodeWidth”; “fix(flowchart): size non-rectangular shapes from the label's height too”; “fix(flowchart): preserve stadium caps and exempt selected shapes from label wrapping”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:33:19 +00:00' --until='2026-10-26 10:33:19 +00:00' --full-history --no-merges -- packages/mermaid/src/rendering-util/rendering-elements/shapes/doubleCircle.ts`: 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×14
Sync-over-async blocking e2e/helpers/argos-metadata.ts:288— `existsSync` in `verifyArgosMetadataSidecars` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking e2e/helpers/argos-metadata.ts:293— `readFileSync` in `verifyArgosMetadataSidecars` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking e2e/helpers/util.ts:271— `mkdirSync` in `verifyScreenshot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking e2e/helpers/util.ts:273— `writeFileSync` in `verifyScreenshot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking e2e/helpers/util.ts:286— `existsSync` in `verifyScreenshot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking e2e/helpers/util.ts:287— `mkdirSync` in `verifyScreenshot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking e2e/helpers/util.ts:289— `writeFileSync` in `verifyScreenshot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/mermaid/scripts/docs.mts:623— `rmSync` in `processDocs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/mermaid/scripts/docs.mts:662— `rmSync` in `on("unlink")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/mermaid/scripts/docs.mts:663— `rmdirSync` in `on("unlinkDir")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/mermaid/src/rendering-util/layout-algorithms/ddlt/parseToLayoutData.ts:21— `readFileSync` in `parseMmdFileToLayoutData` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
ClassTooLong: AgentFlowDB packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:213— ClassTooLong — 1315 significant lines (blank, comment-only and punctuation-only lines excluded), 76 methods. The bar is 400 significant lines; this is 915 over it, 3.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: FlowDB packages/mermaid/src/diagrams/flowchart/flowDb.ts:38— ClassTooLong — 817 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 400 significant lines; this is 417 over it, 2.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UsecaseVisitor packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts:68— ClassTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded), 70 methods. The bar is 400 significant lines; this is 316 over it, 1.79× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UsecaseModelBuilder packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:172— ClassTooLong — 677 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 400 significant lines; this is 277 over it, 1.69× 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: validateLayout packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:1— ClassTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 150 over it, 1.38× 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: ClassDB packages/mermaid/src/diagrams/class/classDb.ts:37— ClassTooLong — 529 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 129 over it, 1.32× 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: SequenceDB packages/mermaid/src/diagrams/sequence/sequenceDb.ts:115— ClassTooLong — 441 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 41 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UsecaseParser packages/mermaid/src/diagrams/usecase/parser/usecase.parser.ts:84— ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 9 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AgentFlowDB packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:213— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× 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: UsecaseVisitor packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts:68— TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.33× 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: UsecaseModelBuilder packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:172— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FlowDB packages/mermaid/src/diagrams/flowchart/flowDb.ts:38— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× 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: ClassDB packages/mermaid/src/diagrams/class/classDb.ts:37— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StateDB packages/mermaid/src/diagrams/state/stateDb.ts:211— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SequenceDB packages/mermaid/src/diagrams/sequence/sequenceDb.ts:115— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling: chartTitle.ts ↔ index.ts packages/mermaid/src/diagrams/xychart/chartBuilder/components/chartTitle.ts:1— `packages/mermaid/src/diagrams/xychart/chartBuilder/components/chartTitle.ts` and `packages/mermaid/src/diagrams/xychart/chartBuilder/index.ts` change together 86% of the time (12 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `037ba2fa` chore: Rename Group to SVGGroup; `0d348b79` Updated code review changes; `7c7d5881` Fixed all review comment (at that commit the file was still `packages/mermaid/src/diagrams/xychart/chartBuilder/components/ChartTitle.ts`) — run `git show` on any of them.
Change coupling: index.ts ↔ chartTitle.ts packages/mermaid/src/diagrams/xychart/chartBuilder/components/axis/index.ts:1— `packages/mermaid/src/diagrams/xychart/chartBuilder/components/axis/index.ts` and `packages/mermaid/src/diagrams/xychart/chartBuilder/components/chartTitle.ts` change together 80% of the time (12 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `037ba2fa` chore: Rename Group to SVGGroup; `0d348b79` Updated code review changes; `7c7d5881` Fixed all review comment (at that commit the file was still `packages/mermaid/src/diagrams/xychart/chartBuilder/components/ChartTitle.ts`) — run `git show` on any of them.
Change coupling: linePlot.ts ↔ xychartDb.ts packages/mermaid/src/diagrams/xychart/chartBuilder/components/plot/linePlot.ts:1— `packages/mermaid/src/diagrams/xychart/chartBuilder/components/plot/linePlot.ts` and `packages/mermaid/src/diagrams/xychart/xychartDb.ts` change together 75% of the time (9 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `b9074fca` feat(xychart): add per-point text labels for line charts; `fae648c2` Added the file name changes; `7c7d5881` Fixed all review comment (at that commit the file was still `packages/mermaid/src/diagrams/xychart/chartBuilder/components/plot/LinePlot.ts`) — run `git show` on any of them.
Change coupling: kanbanDb.ts ↔ clusters.js packages/mermaid/src/diagrams/kanban/kanbanDb.ts:1— `packages/mermaid/src/diagrams/kanban/kanbanDb.ts` and `packages/mermaid/src/rendering-util/rendering-elements/clusters.js` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 6 shared commits counted here, the most recent 3 are `33c7c720` Merge pull request #7276 from mermaid-js/markdown-specific-changes; `0197c089` revert adding kanban section to shape; `dffaf9fa` fix for kanban section shape — run `git show` on any of them.
Change coupling: orchestrator.ts ↔ xychartDb.ts packages/mermaid/src/diagrams/xychart/chartBuilder/orchestrator.ts:1— `packages/mermaid/src/diagrams/xychart/chartBuilder/orchestrator.ts` and `packages/mermaid/src/diagrams/xychart/xychartDb.ts` change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `037ba2fa` chore: Rename Group to SVGGroup; `0d348b79` Updated code review changes; `fae648c2` Added the file name changes — run `git show` on any of them.
Change coupling: flowDb.ts ↔ imageSquare.ts packages/mermaid/src/diagrams/flowchart/flowDb.ts:1— `packages/mermaid/src/diagrams/flowchart/flowDb.ts` and `packages/mermaid/src/rendering-util/rendering-elements/shapes/imageSquare.ts` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 7 shared commits counted here, the most recent 3 are `6a649d34` updated imageSquare shape; `fd372941` updated constraint property for node shape; `c83fc753` implemented additional Image-node shape properties — run `git show` on any of them.
IC1 · Incompleteness & stubs· Both branches are identical · ×6
Both branches are identical — the condition decides nothing REDACTED:583— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing REDACTED:584— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing packages/mermaid/src/rendering-util/rendering-elements/clusters.js:478— The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts:269— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing packages/mermaid/src/rendering-util/rendering-elements/shapes/trapezoid.ts:13— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing packages/mermaid/src/utils.ts:427— The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
IC1 · Incompleteness & stubs· Empty method body · ×6
Empty method body — does nothing with its inputs packages/mermaid/src/logger.ts:19— `trace` 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 packages/mermaid/src/logger.ts:20— `debug` 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 packages/mermaid/src/logger.ts:21— `info` 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 packages/mermaid/src/logger.ts:22— `warn` 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 packages/mermaid/src/logger.ts:23— `error` 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 packages/mermaid/src/logger.ts:24— `fatal` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Deprecated: @types/rollup-plugin-visualizer package.json:121— @types/rollup-plugin-visualizer 5.0.3, declared in package.json, is marked deprecated by its publisher: "This is a stub types definition. rollup-plugin-visualizer provides its own type definitions, so you do not need this installed.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint package.json:136— eslint 9.35.0, declared in package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint-plugin-markdown package.json:144— eslint-plugin-markdown 5.1.0, declared in package.json, is marked deprecated by its publisher: "Please use @eslint/markdown instead". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: katex packages/mermaid-layout-elk/package.json:56— katex 0.18.11, declared in packages/mermaid-layout-elk/package.json, is marked deprecated by its publisher: "Accidentally published with breaking changes. Use 0.19.0 instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: katex packages/mermaid/package.json:90— katex 0.18.11, declared in packages/mermaid/package.json, is marked deprecated by its publisher: "Accidentally published with breaking changes. Use 0.19.0 instead.". Replace it with the package or version that message names, or record why this one must stay.
AC3 · Page structure· Page without a main landmark · ×4
Page without a main landmark .esbuild/dev-explorer/public/compare-pane.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .esbuild/dev-explorer/public/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <dev-explorer-app>, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark packages/mermaid-local-editor/static/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark scripts/verify-diagram/verify.mjs:113— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×4
Animation without a prefers-reduced-motion guard packages/mermaid-local-editor/static/styles.css:16— `#toolbar` moves (`transition: transform 0.25s ease,
opacity 0.2s ease,
height 0.25s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/mermaid/src/docs/.vitepress/theme/Tooltip.vue:84— `.mermaid-chart-tooltip.showing` moves (`animation: tooltipFadeIn 0.3s ease 0.4s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/mermaid/src/docs/.vitepress/theme/Tooltip.vue:88— `.mermaid-chart-tooltip.hiding` moves (`animation: tooltipFadeOut 0.3s ease forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard .esbuild/dev-explorer/public/styles.css:215— `dev-explorer-app button.card` moves (`transition: transform 0.2s ease,
box-shadow 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×4
Recursive walk over a caller-supplied document has no depth cap packages/mermaid/src/config.ts:267— `sanitize` is exported and takes `options: any` from its caller, and it calls itself at line 267 (`sanitize`) with a piece of `options` — and nowhere in `sanitize` is there a depth parameter, a descent counter, or any other cap. 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sanitize` 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 packages/mermaid/src/utils/sanitizeDirective.ts:48— `sanitizeDirective` is exported and takes `args: any` from its caller, and it calls itself at line 48 (`sanitizeDirective`) with a piece of `args` (and at line 75) — and nowhere in `sanitizeDirective` is there a depth parameter, a descent counter, or any other cap. 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sanitizeDirective` 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 packages/mermaid/src/rendering-util/rendering-elements/shapes/labelImageUtils.ts:72— `hasTextBesidesImages` is exported and takes `node: Node` from its caller, and it calls itself at line 72 (`hasTextBesidesImages`) with a piece of `node` — and nowhere in `hasTextBesidesImages` is there a depth parameter, a descent counter, or any other cap. 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `hasTextBesidesImages` 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 packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1380— `collectDescendantIds` is exported and takes `elkNode: any` from its caller, and it calls itself at line 1380 (`collectDescendantIds`) with a piece of `elkNode` — and nowhere in `collectDescendantIds` is there a depth parameter, a descent counter, or any other cap. 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `collectDescendantIds` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×4
Untrusted text written into markup unescaped packages/mermaid-zenuml/src/zenumlRenderer.ts:81— `result.innerSvg` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/mermaid/src/mermaid.ts:186— `svg` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:606— `rules` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/mermaid/src/utils.ts:777— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Swallowed exception (empty catch) packages/mermaid/src/profiler.ts:198— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/mermaid/src/profiler.ts:230— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:711— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×2
Focus outline removed in CSS without a :focus replacement packages/mermaid/src/docs/.vitepress/theme/Mermaid.vue:108— `.editable-code:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement .esbuild/dev-explorer/public/styles.css:479— `dev-explorer-app .cm-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
updateColors (cyclomatic 215) packages/mermaid/src/themes/theme-neo-dark.js:68— updateColors has cyclomatic complexity 215 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cyclomatic 215) packages/mermaid/src/themes/theme-neo.js:52— updateColors has cyclomatic complexity 215 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cognitive 220) packages/mermaid/src/themes/theme-neo-dark.js:68— updateColors has cognitive complexity 220 (threshold 15). Drivers by points: boolean chains 196, loops 6 (8 pts), if/else 6 (7 pts), ternaries 7, other 2 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cognitive 220) packages/mermaid/src/themes/theme-neo.js:52— updateColors has cognitive complexity 220 (threshold 15). Drivers by points: boolean chains 196, loops 6 (8 pts), if/else 6 (7 pts), ternaries 7, other 2 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
router.routeEdgesOrthogonal::crossingPenalty (cognitive 37) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts:278— router.routeEdgesOrthogonal::crossingPenalty has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 7, loops 2 (4 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (router.routeEdgesOrthogonal, router.routeEdgesOrthogonal::fixPipeCrossings) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
router.routeEdgesOrthogonal::fixPipeCrossings (cognitive 19) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts:1956— router.routeEdgesOrthogonal::fixPipeCrossings has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (11 pts), if/else 2 (8 pts) (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. This shape REPEATS in the file: 2 other methods here (router.routeEdgesOrthogonal, router.routeEdgesOrthogonal::crossingPenalty) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
materializedGeometry.reassignCrossingExternalRailChannels::candidateIsSafe (cognitive 28) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1494— materializedGeometry.reassignCrossingExternalRailChannels::candidateIsSafe has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 6 (13 pts), boolean chains 1 (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. This shape REPEATS in the file: 2 other methods here (materializedGeometry.reassignCrossingExternalRailChannels, materializedGeometry.reassignCrossingExternalRailChannels::externalRailForSegment) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
materializedGeometry.reassignCrossingExternalRailChannels::externalRailForSegment (cognitive 19) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1289— materializedGeometry.reassignCrossingExternalRailChannels::externalRailForSegment has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 6 (8 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. This shape REPEATS in the file: 2 other methods here (materializedGeometry.reassignCrossingExternalRailChannels, materializedGeometry.reassignCrossingExternalRailChannels::candidateIsSafe) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Fake-async — async method never awaits packages/mermaid/src/diagrams/usecase/parser/usecase.chevrotain.ts:10— `parse` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/mermaid/src/rendering-util/layout-algorithms/ddlt/backends.ts:35— `runDomusOrthogonalDdlt` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Duplicated block (56 lines × 2 locations) packages/mermaid/src/utils/lineWithOffset.ts:60— packages/mermaid/src/utils/lineWithOffset.ts:60 · packages/mermaid/src/utils/lineWithOffset.ts:122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (56 lines × 2 locations) packages/parser/src/language/railroad-peg/valueConverter.ts:5— packages/parser/src/language/railroad-peg/valueConverter.ts:5 · packages/parser/src/language/railroad/valueConverter.ts:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (43 matched lines × 2 locations) · ×2
Duplicated block with local edits (43 matched lines × 2 locations) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:97— packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:97 · packages/mermaid/src/diagrams/user-journey/journeyRenderer.ts:218 — the two spans are one implementation copied and then locally edited — 461 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.
Duplicated block with local edits (43 matched lines × 2 locations) packages/mermaid/src/themes/theme-default.js:8— packages/mermaid/src/themes/theme-default.js:8 · packages/mermaid/src/themes/theme-neutral.js:11 — the two spans are one implementation copied and then locally edited — 321 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 updateColors (cyclomatic 215, cognitive 220) packages/mermaid/src/themes/theme-neo-dark.js:68— updateColors has cyclomatic complexity 215 and cognitive complexity 220; 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 updateColors (cyclomatic 215, cognitive 220) packages/mermaid/src/themes/theme-neo.js:52— updateColors has cyclomatic complexity 215 and cognitive complexity 220; 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.
R4 · Test Coverage· This test file cannot be loaded · ×2
This test file cannot be loaded e2e/platform/bundle-test.js:2— e2e/platform/bundle-test.js:2 imports './mermaid.esm.mjs', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded e2e/platform/viewer.js:1— e2e/platform/viewer.js:1 imports './mermaid-example-diagram.esm.mjs', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (3 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
X2 · Cancellation propagation· Async function without AbortSignal · ×2
Async function without AbortSignal: download packages/mermaid/src/docs/.vitepress/scripts/fetch-avatars.ts:12— `download` 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 })`.
Async function without AbortSignal: fetchContributors packages/mermaid/src/docs/.vitepress/scripts/fetch-contributors.ts:14— `fetchContributors` 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 })`.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 16 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
updateColors (cyclomatic 289) packages/mermaid/src/themes/theme-base.js:32— updateColors has cyclomatic complexity 289 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
router.routeEdgesOrthogonal (cyclomatic 224) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts:122— router.routeEdgesOrthogonal has cyclomatic complexity 224 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (router.routeEdgesOrthogonal::crossingPenalty) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
updateColors (cyclomatic 216) packages/mermaid/src/themes/theme-redux-dark.js:76— updateColors has cyclomatic complexity 216 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cyclomatic 205) packages/mermaid/src/themes/theme-redux.js:58— updateColors has cyclomatic complexity 205 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cyclomatic 203) packages/mermaid/src/themes/theme-default.js:146— updateColors has cyclomatic complexity 203 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cyclomatic 200) packages/mermaid/src/themes/theme-forest.js:113— updateColors has cyclomatic complexity 200 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cyclomatic 199) packages/mermaid/src/themes/theme-redux-color.js:106— updateColors has cyclomatic complexity 199 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cyclomatic 196) packages/mermaid/src/themes/theme-redux-dark-color.js:108— updateColors has cyclomatic complexity 196 (threshold 15). Of this number, 195 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cyclomatic 189) packages/mermaid/src/themes/theme-dark.js:115— updateColors has cyclomatic complexity 189 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
validateLayout.validateLayout (cyclomatic 186) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:604— validateLayout.validateLayout has cyclomatic complexity 186 (threshold 15). Of this number, 169 points are the body's own statements and 17 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
updateColors (cyclomatic 173) packages/mermaid/src/themes/theme-neutral.js:128— updateColors has cyclomatic complexity 173 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
materializedGeometry.resolveRenderedOrthogonalCrossings (cyclomatic 153) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1835— materializedGeometry.resolveRenderedOrthogonalCrossings has cyclomatic complexity 153 (threshold 15). Of this number, 23 points are the body's own statements and 130 belong to 35 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
materializedGeometry.separateSharedRenderedTerminalLanes (cyclomatic 86) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:45— materializedGeometry.separateSharedRenderedTerminalLanes has cyclomatic complexity 86 (threshold 15). Of this number, 19 points are the body's own statements and 67 belong to 9 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
labelAnchoring.anchorLabelsToPolyline (cyclomatic 81) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/labelAnchoring.ts:83— labelAnchoring.anchorLabelsToPolyline has cyclomatic complexity 81 (threshold 15). Of this number, 34 points are the body's own statements and 47 belong to 13 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
materializedGeometry.reassignCrossingExternalRailChannels (cyclomatic 77) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1210— materializedGeometry.reassignCrossingExternalRailChannels has cyclomatic complexity 77 (threshold 15). Most of this is not in the body itself: 15 of the 77 points are its own statements and the rest belongs to 11 function items inside it that branch (externalRailForSegment, candidateIsSafe, connectedComponents, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
sequenceRenderer.drawMessage (cyclomatic 74) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:461— sequenceRenderer.drawMessage has cyclomatic complexity 74 (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.
renderer.draw (cyclomatic 73) packages/mermaid/src/diagrams/treemap/renderer.ts:24— renderer.draw has cyclomatic complexity 73 (threshold 15). Of this number, 24 points are the body's own statements and 49 belong to 18 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.
sharedTrackNudging.nudgeSharedInteriorSubpaths (cyclomatic 72) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/sharedTrackNudging.ts:13— sharedTrackNudging.nudgeSharedInteriorSubpaths has cyclomatic complexity 72 (threshold 15). Of this number, 16 points are the body's own statements and 56 belong to 9 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
insertEdge (cyclomatic 71) packages/mermaid/src/rendering-util/rendering-elements/edges.js:624— insertEdge has cyclomatic complexity 71 (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.
wardleyRenderer.draw (cyclomatic 66) packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts:67— wardleyRenderer.draw has cyclomatic complexity 66 (threshold 15). Of this number, 16 points are the body's own statements and 50 belong to 28 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
classBox.classBox (cyclomatic 62) packages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts:14— classBox.classBox has cyclomatic complexity 62 (threshold 15). Of this number, 46 points are the body's own statements and 16 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
sequenceRenderer.draw (cyclomatic 58) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1043— sequenceRenderer.draw has cyclomatic complexity 58 (threshold 15). Of this number, 54 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
materializedGeometry.shortcutRedundantOrthogonalJogs (cyclomatic 55) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1587— materializedGeometry.shortcutRedundantOrthogonalJogs has cyclomatic complexity 55 (threshold 15). Of this number, 16 points are the body's own statements and 39 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
phase2.crossCounts.computeSubtreeCrossCounts (cyclomatic 53) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase2.crossCounts.ts:12— phase2.crossCounts.computeSubtreeCrossCounts has cyclomatic complexity 53 (threshold 15). Of this number, 33 points are the body's own statements and 20 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
terminalStub.collapseShortTerminalStub (cyclomatic 51) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/terminalStub.ts:44— terminalStub.collapseShortTerminalStub has cyclomatic complexity 51 (threshold 15). Of this number, 43 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FlowDB.addVertex (cyclomatic 45) packages/mermaid/src/diagrams/flowchart/flowDb.ts:127— FlowDB.addVertex has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
geometry.buildOrthogonalPortPath (cyclomatic 45) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts:297— geometry.buildOrthogonalPortPath has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
materializedGeometry.shiftLeftLaneTitleBandsLeftOfRails (cyclomatic 43) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:848— materializedGeometry.shiftLeftLaneTitleBandsLeftOfRails has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 15 of the 43 points are its own statements and the rest belongs to 4 function items inside it that branch (validTitleRect, leftLaneTitleFor, verticalSegmentIntersectsTitle, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
AgentFlowDB.addVertex (cyclomatic 43) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:347— AgentFlowDB.addVertex has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
materializedGeometry.swapDestinationTerminalTailsToReduceCrossings (cyclomatic 42) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:986— materializedGeometry.swapDestinationTerminalTailsToReduceCrossings has cyclomatic complexity 42 (threshold 15). Of this number, 18 points are the body's own statements and 24 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SequenceDB.apply (cyclomatic 42) packages/mermaid/src/diagrams/sequence/sequenceDb.ts:557— SequenceDB.apply has cyclomatic complexity 42 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
erBox.erBox (cyclomatic 41) packages/mermaid/src/rendering-util/rendering-elements/shapes/erBox.ts:19— erBox.erBox has cyclomatic complexity 41 (threshold 15). Of this number, 36 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
materializedGeometry.liftTopLaneTitleBandsAboveRails (cyclomatic 41) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:720— materializedGeometry.liftTopLaneTitleBandsAboveRails has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 14 of the 41 points are its own statements and the rest belongs to 3 function items inside it that branch (topLaneTitleFor, validTitleRect, horizontalSegmentIntersectsTitle). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
siblingSharedFaceRouting.straightenCollinearSiblingDetours (cyclomatic 40) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/siblingSharedFaceRouting.ts:47— siblingSharedFaceRouting.straightenCollinearSiblingDetours has cyclomatic complexity 40 (threshold 15). Of this number, 29 points are the body's own statements and 11 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentFlowDB.getData (cyclomatic 40) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1696— AgentFlowDB.getData has cyclomatic complexity 40 (threshold 15). Of this number, 16 points are the body's own statements and 24 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
layoutCore.layoutContainer (cyclomatic 39) packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts:61— layoutCore.layoutContainer has cyclomatic complexity 39 (threshold 15). Of this number, 37 points are the body's own statements and 2 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.
materializedGeometry.liftObstacleHuggingSameSideRails (cyclomatic 38) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:511— materializedGeometry.liftObstacleHuggingSameSideRails has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 11 of the 38 points are its own statements and the rest belongs to 6 function items inside it that branch (candidateIsSafe, a function literal at line 594, strictCrossingCount, …). 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.
svgDraw.drawText (cyclomatic 38) REDACTED:192— svgDraw.drawText has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FlowDB.getData (cyclomatic 37) packages/mermaid/src/diagrams/flowchart/flowDb.ts:1110— FlowDB.getData has cyclomatic complexity 37 (threshold 15). Of this number, 20 points are the body's own statements and 17 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
materializedGeometry.collapseRedundantRectangularDoglegs::withoutDogleg (cyclomatic 37) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:417— materializedGeometry.collapseRedundantRectangularDoglegs::withoutDogleg has cyclomatic complexity 37 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentFlowDB.getSemanticModel (cyclomatic 37) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:2017— AgentFlowDB.getSemanticModel has cyclomatic complexity 37 (threshold 15). Of this number, 20 points are the body's own statements and 17 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.
gitGraphRenderer.drawArrow (cyclomatic 37) packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:653— gitGraphRenderer.drawArrow 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.
svgDraw.drawEdges (cyclomatic 36) packages/mermaid/src/diagrams/architecture/svgDraw.ts:25— svgDraw.drawEdges has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to one function literal inside it that branches (line 38). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
phase4.coordinates.assignCoordinates (cyclomatic 35) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase4.coordinates.ts:13— phase4.coordinates.assignCoordinates has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
helpers.writeBackToLayoutData (cyclomatic 34) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/helpers.ts:174— helpers.writeBackToLayoutData 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.
detourSimplification.simplifyDetouredEdges (cyclomatic 32) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/detourSimplification.ts:20— detourSimplification.simplifyDetouredEdges has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (detourSimplification.simplifyDetouredEdges::pathConflictCount) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
cynefinRenderer.draw (cyclomatic 31) packages/mermaid/src/diagrams/cynefin/cynefinRenderer.ts:71— cynefinRenderer.draw has cyclomatic complexity 31 (threshold 15). Of this number, 24 points are the body's own statements and 7 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.
draw::makeGrid (cyclomatic 31) packages/mermaid/src/diagrams/gantt/ganttRenderer.js:649— draw::makeGrid 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.
c4Db.updateElStyle (cyclomatic 30) packages/mermaid/src/diagrams/c4/c4Db.ts:494— c4Db.updateElStyle 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.
render.findCyclicEntryNodes (cyclomatic 30) packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:530— render.findCyclicEntryNodes has cyclomatic complexity 30 (threshold 15). Of this number, 26 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
portSwap.portSwapToLShape (cyclomatic 30) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/portSwap.ts:107— portSwap.portSwapToLShape 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.
sequenceRenderer.getMaxMessageWidthPerActor (cyclomatic 30) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1488— sequenceRenderer.getMaxMessageWidthPerActor 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.
xychartRenderer.draw (cyclomatic 29) packages/mermaid/src/diagrams/xychart/xychartRenderer.ts:13— xychartRenderer.draw has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 12 function items inside it that branch (getGroup, getTextAnchor, a function literal at line 127, …). 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.
lrTransform.applyLrDirectionTransform (cyclomatic 28) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/lrTransform.ts:150— lrTransform.applyLrDirectionTransform has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
sequenceRenderer.calculateLoopBounds (cyclomatic 28) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:2041— sequenceRenderer.calculateLoopBounds has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
render.applyElkEdgeLayout (cyclomatic 27) packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1945— render.applyElkEdgeLayout has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 8 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1998, 1967). 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.
validation.validateSwimlanesLayout (cyclomatic 27) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/validation.ts:54— validation.validateSwimlanesLayout 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.
agentflowDb.stripLineTrailingCommas (cyclomatic 27) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:150— agentflowDb.stripLineTrailingCommas 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.
vennRenderer.draw (cyclomatic 27) packages/mermaid/src/diagrams/venn/vennRenderer.ts:31— vennRenderer.draw has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 121, 173, 220). 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.
assignWithDepth.assignWithDepth (cyclomatic 25) packages/mermaid/src/assignWithDepth.ts:30— assignWithDepth.assignWithDepth has cyclomatic complexity 25 (threshold 15). Of this number, 16 points are the body's own statements and 9 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.
dataFetcher.dataFetcher (cyclomatic 25) packages/mermaid/src/diagrams/state/dataFetcher.ts:241— dataFetcher.dataFetcher 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.
boxDrawingPreprocessor.preprocessBoxDrawing (cyclomatic 25) packages/mermaid/src/diagrams/treeView/boxDrawingPreprocessor.ts:67— boxDrawingPreprocessor.preprocessBoxDrawing 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.
kanbanItem.kanbanItem (cyclomatic 24) packages/mermaid/src/rendering-util/rendering-elements/shapes/kanbanItem.ts:23— kanbanItem.kanbanItem has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
lineJump.applyLineJumpsToSvg (cyclomatic 24) packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts:646— lineJump.applyLineJumpsToSvg has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blockDB.populateBlockDatabase (cyclomatic 24) packages/mermaid/src/diagrams/block/blockDB.ts:105— blockDB.populateBlockDatabase has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
stateRenderer.renderDoc (cyclomatic 24) packages/mermaid/src/diagrams/state/stateRenderer.js:89— stateRenderer.renderDoc has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to 3 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.
placement.readGridConfig (cyclomatic 24) packages/mermaid/src/rendering-util/layout-algorithms/grid/placement.ts:96— placement.readGridConfig has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
phase2.gravity.assignLayers_Gravity (cyclomatic 23) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase2.gravity.ts:18— phase2.gravity.assignLayers_Gravity has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to 3 function items inside it that branch (relaxOrder, a function literal at line 30, clampFeasible). 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.
gitGraphRenderer.drawCommitBullet (cyclomatic 23) packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:226— gitGraphRenderer.drawCommitBullet has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
usecaseDb.getData (cyclomatic 23) packages/mermaid/src/diagrams/usecase/usecaseDb.ts:295— usecaseDb.getData has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PropertyOrderCollector.readString (cyclomatic 23) packages/mermaid/src/diagrams/usecase/parser/usecaseJson.ts:201— PropertyOrderCollector.readString has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UsecaseModelBuilder.applyMetadataAssignments (cyclomatic 23) packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:620— UsecaseModelBuilder.applyMetadataAssignments has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scoreLayout.computeNeighborhoodPreservation (cyclomatic 23) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:362— scoreLayout.computeNeighborhoodPreservation has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
requirementBox.requirementBox (cyclomatic 22) packages/mermaid/src/rendering-util/rendering-elements/shapes/requirementBox.ts:15— requirementBox.requirementBox has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
geometry.orthogonalSegmentsCross (cyclomatic 22) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts:483— geometry.orthogonalSegmentsCross has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
router.routeEdgesOrthogonal::crossingPenalty (cyclomatic 22) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts:278— router.routeEdgesOrthogonal::crossingPenalty 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. This shape REPEATS in the file: one other method here (router.routeEdgesOrthogonal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
UsecaseModelBuilder.collectElement (cyclomatic 22) packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:358— UsecaseModelBuilder.collectElement has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
groups.buildGridForest (cyclomatic 22) packages/mermaid/src/rendering-util/layout-algorithms/grid/groups.ts:21— groups.buildGridForest has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
util.labelHelper (cyclomatic 21) packages/mermaid/src/rendering-util/rendering-elements/shapes/util.ts:50— util.labelHelper has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
edges.insertEdgeLabel (cyclomatic 21) packages/mermaid/src/rendering-util/rendering-elements/edges.js:74— edges.insertEdgeLabel has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
mermaidAPI.renderDiagram (cyclomatic 21) REDACTED:477— mermaidAPI.renderDiagram has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AgentFlowDB.addSubGraph (cyclomatic 21) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1175— AgentFlowDB.addSubGraph has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 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.
QuadrantBuilder.getAxisLabels (cyclomatic 21) packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts:286— QuadrantBuilder.getAxisLabels 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.
styles.getStyles (cyclomatic 21) packages/mermaid/src/diagrams/state/styles.js:101— styles.getStyles has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
layout.setBlockSizes (cyclomatic 21) packages/mermaid/src/diagrams/block/layout.ts:72— layout.setBlockSizes 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.
drawActorTypeCollections (cyclomatic 21) REDACTED:516— drawActorTypeCollections has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
drawActorTypeDatabase (cyclomatic 21) REDACTED:999— drawActorTypeDatabase has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
render.straightenEdgeTerminals (cyclomatic 20) packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1888— render.straightenEdgeTerminals has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentFlowDB.rethrowMetadataYamlError (cyclomatic 20) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:611— AgentFlowDB.rethrowMetadataYamlError has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
gitGraphAst.merge (cyclomatic 20) packages/mermaid/src/diagrams/git/gitGraphAst.ts:152— gitGraphAst.merge has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
gitGraphAst.cherryPick (cyclomatic 20) packages/mermaid/src/diagrams/git/gitGraphAst.ts:261— gitGraphAst.cherryPick has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
gitGraphRenderer.drawBranches (cyclomatic 20) packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:867— gitGraphRenderer.drawBranches has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to one function literal inside it that branches (line 878). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
SequenceDB.addActor (cyclomatic 20) packages/mermaid/src/diagrams/sequence/sequenceDb.ts:155— SequenceDB.addActor has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PropertyOrderCollector.consumeNumber (cyclomatic 20) packages/mermaid/src/diagrams/usecase/parser/usecaseJson.ts:286— PropertyOrderCollector.consumeNumber has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
wardleyParser.populateDb (cyclomatic 20) packages/mermaid/src/diagrams/wardley/wardleyParser.ts:68— wardleyParser.populateDb has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 99, 148, 174, …). 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.
scoreLayout.scoreLayout (cyclomatic 20) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:503— scoreLayout.scoreLayout has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
layout.calculateEdgePositions (cyclomatic 19) packages/mermaid-layout-tidy-tree/src/layout.ts:455— layout.calculateEdgePositions has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 465). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ClassMember.parseMember (cyclomatic 19) packages/mermaid/src/diagrams/class/classTypes.ts:80— ClassMember.parseMember 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.
c4Db.addRel (cyclomatic 19) packages/mermaid/src/diagrams/c4/c4Db.ts:86— c4Db.addRel has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
mermaid-graphlib.adjustClustersAndEdges (cyclomatic 19) packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:200— mermaid-graphlib.adjustClustersAndEdges has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
lineJump.rewriteEdgePath (cyclomatic 19) packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts:416— lineJump.rewriteEdgePath 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.
render.sanitizeElkEdgePoints (cyclomatic 19) packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:2483— render.sanitizeElkEdgePoints has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
phase2.crossLaneAdjust.adjustCrossLaneSources (cyclomatic 19) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase2.crossLaneAdjust.ts:8— phase2.crossLaneAdjust.adjustCrossLaneSources has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
QuadrantBuilder.getDefaultConfig (cyclomatic 19) packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts:153— QuadrantBuilder.getDefaultConfig has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
sequenceRenderer.buildMessageModel (cyclomatic 19) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1867— sequenceRenderer.buildMessageModel has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
kanbanDb.addNode (cyclomatic 19) packages/mermaid/src/diagrams/kanban/kanbanDb.ts:99— kanbanDb.addNode 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.
db.calculateSwimlaneProps (cyclomatic 19) packages/mermaid/src/diagrams/eventmodeling/db.ts:233— db.calculateSwimlaneProps has cyclomatic complexity 19 (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.
getStyles (cyclomatic 19) packages/mermaid/src/diagrams/git/styles.js:118— getStyles has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
drawActorTypeParticipant (cyclomatic 19) REDACTED:391— drawActorTypeParticipant has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
sanitizeDirective.sanitizeDirective (cyclomatic 18) packages/mermaid/src/utils/sanitizeDirective.ts:38— sanitizeDirective.sanitizeDirective 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.
regexes.matchFrontMatter (cyclomatic 18) packages/mermaid/src/diagram-api/regexes.ts:135— regexes.matchFrontMatter has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
driving-tree.buildDrivingTree (cyclomatic 18) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/driving-tree.ts:34— driving-tree.buildDrivingTree has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
layout.layoutBlocks (cyclomatic 18) packages/mermaid/src/diagrams/block/layout.ts:209— layout.layoutBlocks 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.
UsecaseModelBuilder.applyActorProperty (cyclomatic 18) packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:721— UsecaseModelBuilder.applyActorProperty has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
svgDraw.drawEdge (cyclomatic 18) packages/mermaid/src/diagrams/class/svgDraw.js:7— svgDraw.drawEdge has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to one function item inside it that branches. 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.
geometry.segmentsCross (cyclomatic 18) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/geometry.ts:158— geometry.segmentsCross has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
drawActorTypeQueue (cyclomatic 18) REDACTED:641— drawActorTypeQueue has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
layout.intersection (cyclomatic 17) packages/mermaid-layout-tidy-tree/src/layout.ts:389— layout.intersection 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.
linedCylinder.linedCylinder (cyclomatic 17) packages/mermaid/src/rendering-util/rendering-elements/shapes/linedCylinder.ts:63— linedCylinder.linedCylinder has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
waveEdgedRectangle.waveEdgedRectangle (cyclomatic 17) packages/mermaid/src/rendering-util/rendering-elements/shapes/waveEdgedRectangle.ts:14— waveEdgedRectangle.waveEdgedRectangle 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.
render.straightenFront (cyclomatic 17) packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1710— render.straightenFront 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.
detourSimplification.simplifyDetouredEdges::pathConflictCount (cyclomatic 17) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/detourSimplification.ts:75— detourSimplification.simplifyDetouredEdges::pathConflictCount has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (detourSimplification.simplifyDetouredEdges) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
laneOrdering.buildWeightedLaneEdges (cyclomatic 17) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/laneOrdering.ts:74— laneOrdering.buildWeightedLaneEdges 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.
ClassDB.getData (cyclomatic 17) packages/mermaid/src/diagrams/class/classDb.ts:748— ClassDB.getData 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.
ArchitectureDB.addEdge (cyclomatic 17) packages/mermaid/src/diagrams/architecture/architectureDb.ts:192— ArchitectureDB.addEdge has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ArchitectureDB.getDataStructures (cyclomatic 17) packages/mermaid/src/diagrams/architecture/architectureDb.ts:293— ArchitectureDB.getDataStructures has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UsecaseModelBuilder.validateRelationship (cyclomatic 17) packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:897— UsecaseModelBuilder.validateRelationship 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, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
usecaseRenderer.annotateUsecaseElements (cyclomatic 17) packages/mermaid/src/diagrams/usecase/usecaseRenderer.ts:144— usecaseRenderer.annotateUsecaseElements has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
scoreLayout.hasDiagonalRenderedEndpoint (cyclomatic 17) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:180— scoreLayout.hasDiagonalRenderedEndpoint 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.
scoreLayout.computeRankFaithfulness (cyclomatic 17) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:275— scoreLayout.computeRankFaithfulness 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.
drawActorTypeEntity (cyclomatic 17) REDACTED:891— drawActorTypeEntity 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.
logger.setLogLevel (cyclomatic 16) packages/mermaid/src/logger.ts:32— logger.setLogLevel has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
utils.detectDirective (cyclomatic 16) packages/mermaid/src/utils.ts:159— utils.detectDirective 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.
tiltedCylinder.tiltedCylinder (cyclomatic 16) packages/mermaid/src/rendering-util/rendering-elements/shapes/tiltedCylinder.ts:57— tiltedCylinder.tiltedCylinder has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
lineWithOffset.getLineFunctionsWithOffset.x (cyclomatic 16) packages/mermaid/src/utils/lineWithOffset.ts:60— lineWithOffset.getLineFunctionsWithOffset.x has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (lineWithOffset.getLineFunctionsWithOffset.y) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
lineWithOffset.getLineFunctionsWithOffset.y (cyclomatic 16) packages/mermaid/src/utils/lineWithOffset.ts:122— lineWithOffset.getLineFunctionsWithOffset.y has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (lineWithOffset.getLineFunctionsWithOffset.x) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
mermaid-graphlib.extractor (cyclomatic 16) packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:311— mermaid-graphlib.extractor 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.
phase3.ordering.transposeImprove (cyclomatic 16) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase3.ordering.ts:185— phase3.ordering.transposeImprove has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ganttDb.getStartDate (cyclomatic 16) packages/mermaid/src/diagrams/gantt/ganttDb.js:305— ganttDb.getStartDate has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
styles.getStyles (cyclomatic 16) packages/mermaid/src/diagrams/user-journey/styles.js:3— styles.getStyles has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
timelineRenderer.draw (cyclomatic 16) packages/mermaid/src/diagrams/timeline/timelineRenderer.ts:29— timelineRenderer.draw has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
styles.genSections (cyclomatic 16) packages/mermaid/src/diagrams/mindmap/styles.ts:5— styles.genSections has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
sankeyRenderer.draw (cyclomatic 16) packages/mermaid/src/diagrams/sankey/sankeyRenderer.ts:67— sankeyRenderer.draw has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
runner.matchExpected (cyclomatic 16) packages/mermaid/src/diagrams/agentflow/conformance/runner.ts:193— runner.matchExpected 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.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: packages/mermaid-example-diagram packages/mermaid-example-diagram/src/exampleDiagram.spec.js:22— No conventional assertion call was detected in 1 of 1 tests in `packages/mermaid-example-diagram` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
TodoComment repeated across 10 files packages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts:48— The identical TodoComment appears in 10 files (10 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 10 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// @ts-ignore TODO: Fix rough typings". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
HackComment packages/mermaid/src/diagrams/architecture/architectureRenderer.ts:495— // Hacky fix for: https://github.com/iVis-at-Bilkent/cytoscape.js-fcose/issues/67 — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
router.routeEdgesOrthogonal (cognitive 493) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts:122— router.routeEdgesOrthogonal has cognitive complexity 493 (threshold 15). Drivers by points: if/else 179 (435 pts), ternaries 44 (116 pts), boolean chains 113, loops 54 (102 pts), match/switch 1 (nesting depth added 376). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 2 other methods here (router.routeEdgesOrthogonal::crossingPenalty, router.routeEdgesOrthogonal::fixPipeCrossings) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
validateLayout.validateLayout (cognitive 405) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:604— validateLayout.validateLayout has cognitive complexity 405 (threshold 15). Drivers by points: if/else 71 (217 pts), loops 39 (74 pts), ternaries 21 (71 pts), boolean chains 43 (nesting depth added 231). Of this number, 392 points are the body's own statements and 13 belong to 6 function items inside it that branch. 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.
updateColors (cognitive 295) packages/mermaid/src/themes/theme-base.js:32— updateColors has cognitive complexity 295 (threshold 15). Drivers by points: boolean chains 262, other 10, if/else 8 (9 pts), loops 6 (8 pts), ternaries 6 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cognitive 221) packages/mermaid/src/themes/theme-redux-dark.js:76— updateColors has cognitive complexity 221 (threshold 15). Drivers by points: boolean chains 196, loops 6 (8 pts), if/else 6 (7 pts), ternaries 7, other 3 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cognitive 210) packages/mermaid/src/themes/theme-redux.js:58— updateColors has cognitive complexity 210 (threshold 15). Drivers by points: boolean chains 184, loops 7 (9 pts), if/else 6 (7 pts), ternaries 7, other 3 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cognitive 204) packages/mermaid/src/themes/theme-default.js:146— updateColors has cognitive complexity 204 (threshold 15). Drivers by points: boolean chains 184, other 10, loops 4 (5 pts), if/else 3, ternaries 2 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cognitive 201) packages/mermaid/src/themes/theme-redux-color.js:106— updateColors has cognitive complexity 201 (threshold 15). Drivers by points: boolean chains 178, loops 7, ternaries 7, if/else 4 (5 pts), other 4 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cognitive 200) packages/mermaid/src/themes/theme-forest.js:113— updateColors has cognitive complexity 200 (threshold 15). Drivers by points: boolean chains 182, other 10, loops 4, if/else 2, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cognitive 198) packages/mermaid/src/themes/theme-redux-dark-color.js:108— updateColors has cognitive complexity 198 (threshold 15). Drivers by points: boolean chains 176, ternaries 7, loops 6, if/else 4 (5 pts), other 4 (nesting depth added 1). Of this number, 197 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cognitive 188) packages/mermaid/src/themes/theme-dark.js:115— updateColors has cognitive complexity 188 (threshold 15). Drivers by points: boolean chains 176, loops 6, other 3, ternaries 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
updateColors (cognitive 174) packages/mermaid/src/themes/theme-neutral.js:128— updateColors has cognitive complexity 174 (threshold 15). Drivers by points: boolean chains 160, loops 6, if/else 2 (3 pts), other 3, ternaries 2 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
materializedGeometry.separateSharedRenderedTerminalLanes (cognitive 110) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:45— materializedGeometry.separateSharedRenderedTerminalLanes has cognitive complexity 110 (threshold 15). Drivers by points: if/else 29 (52 pts), boolean chains 31, loops 5 (15 pts), ternaries 11 (12 pts) (nesting depth added 34). Of this number, 46 points are the body's own statements and 64 belong to 9 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
helpers.writeBackToLayoutData (cognitive 97) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/helpers.ts:174— helpers.writeBackToLayoutData has cognitive complexity 97 (threshold 15). Drivers by points: if/else 19 (52 pts), loops 12 (38 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 61). 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.
gitGraphRenderer.drawArrow (cognitive 94) packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:653— gitGraphRenderer.drawArrow has cognitive complexity 94 (threshold 15). Drivers by points: if/else 38 (82 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 46). 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.
renderer.draw (cognitive 93) packages/mermaid/src/diagrams/treemap/renderer.ts:24— renderer.draw has cognitive complexity 93 (threshold 15). Drivers by points: if/else 30 (45 pts), ternaries 21 (24 pts), boolean chains 19, loops 3 (4 pts), error handling 1 (nesting depth added 19). Of this number, 25 points are the body's own statements and 68 belong to 18 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
materializedGeometry.swapDestinationTerminalTailsToReduceCrossings (cognitive 91) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:986— materializedGeometry.swapDestinationTerminalTailsToReduceCrossings has cognitive complexity 91 (threshold 15). Drivers by points: if/else 19 (52 pts), loops 14 (30 pts), boolean chains 8, ternaries 1 (nesting depth added 49). Of this number, 46 points are the body's own statements and 45 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
terminalStub.collapseShortTerminalStub (cognitive 88) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/terminalStub.ts:44— terminalStub.collapseShortTerminalStub has cognitive complexity 88 (threshold 15). Drivers by points: if/else 29 (81 pts), loops 5 (13 pts), boolean chains 12, ternaries 2 (5 pts) (nesting depth added 63). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (terminalStub.collapseShortTerminalStub::segmentCrossesOtherEdge) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
wardleyRenderer.draw (cognitive 82) packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts:67— wardleyRenderer.draw has cognitive complexity 82 (threshold 15). Drivers by points: if/else 32 (43 pts), ternaries 19 (21 pts), boolean chains 11, loops 3 (7 pts) (nesting depth added 17). Of this number, 21 points are the body's own statements and 61 belong to 28 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
detourSimplification.simplifyDetouredEdges (cognitive 81) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/detourSimplification.ts:20— detourSimplification.simplifyDetouredEdges has cognitive complexity 81 (threshold 15). Drivers by points: if/else 32 (86 pts), loops 9 (18 pts), boolean chains 10 (nesting depth added 63). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (detourSimplification.simplifyDetouredEdges::pathConflictCount) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
insertEdge (cognitive 76) packages/mermaid/src/rendering-util/rendering-elements/edges.js:624— insertEdge has cognitive complexity 76 (threshold 15). Drivers by points: ternaries 15 (35 pts), if/else 19 (24 pts), boolean chains 12, match/switch 3, loops 1, other 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.
siblingSharedFaceRouting.straightenCollinearSiblingDetours (cognitive 70) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/siblingSharedFaceRouting.ts:47— siblingSharedFaceRouting.straightenCollinearSiblingDetours has cognitive complexity 70 (threshold 15). Drivers by points: if/else 24 (54 pts), ternaries 4 (6 pts), boolean chains 5, loops 4 (5 pts) (nesting depth added 33). Of this number, 55 points are the body's own statements and 15 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render.findCyclicEntryNodes (cognitive 68) packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:530— render.findCyclicEntryNodes has cognitive complexity 68 (threshold 15). Drivers by points: if/else 12 (35 pts), loops 11 (24 pts), ternaries 2 (6 pts), boolean chains 3 (nesting depth added 40). Of this number, 56 points are the body's own statements and 12 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentFlowDB.addVertex (cognitive 67) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:347— AgentFlowDB.addVertex has cognitive complexity 67 (threshold 15). Drivers by points: if/else 33 (49 pts), boolean chains 9, error handling 2 (6 pts), ternaries 1 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentFlowDB.getSemanticModel (cognitive 67) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:2017— AgentFlowDB.getSemanticModel has cognitive complexity 67 (threshold 15). Drivers by points: if/else 25 (49 pts), loops 4 (10 pts), boolean chains 6, ternaries 1 (2 pts) (nesting depth added 31). Of this number, 46 points are the body's own statements and 21 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sequenceRenderer.drawMessage (cognitive 67) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:461— sequenceRenderer.drawMessage has cognitive complexity 67 (threshold 15). Drivers by points: if/else 36 (46 pts), boolean chains 21 (nesting depth added 10). 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.
FlowDB.addVertex (cognitive 66) packages/mermaid/src/diagrams/flowchart/flowDb.ts:127— FlowDB.addVertex has cognitive complexity 66 (threshold 15). Drivers by points: if/else 35 (57 pts), boolean chains 9 (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.
xychartRenderer.draw (cognitive 65) packages/mermaid/src/diagrams/xychart/xychartRenderer.ts:13— xychartRenderer.draw has cognitive complexity 65 (threshold 15). Drivers by points: if/else 10 (26 pts), ternaries 6 (17 pts), loops 4 (12 pts), boolean chains 8, match/switch 1 (2 pts) (nesting depth added 36). Of this number, 23 points are the body's own statements and 42 belong to 12 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
portSwap.portSwapToLShape (cognitive 62) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/portSwap.ts:107— portSwap.portSwapToLShape has cognitive complexity 62 (threshold 15). Drivers by points: if/else 17 (41 pts), boolean chains 10, ternaries 2 (8 pts), loops 2 (3 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.
labelAnchoring.anchorLabelsToPolyline (cognitive 61) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/labelAnchoring.ts:83— labelAnchoring.anchorLabelsToPolyline has cognitive complexity 61 (threshold 15). Drivers by points: if/else 39 (95 pts), ternaries 9 (21 pts), loops 11 (17 pts), boolean chains 14 (nesting depth added 74). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (labelAnchoring.anchorLabelsToPolyline::tryPool) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
phase4.coordinates.assignCoordinates (cognitive 61) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase4.coordinates.ts:13— phase4.coordinates.assignCoordinates has cognitive complexity 61 (threshold 15). Drivers by points: if/else 14 (29 pts), loops 16 (27 pts), boolean chains 4, ternaries 1 (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.
classBox.classBox (cognitive 60) packages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts:14— classBox.classBox has cognitive complexity 60 (threshold 15). Drivers by points: if/else 25 (32 pts), boolean chains 19, ternaries 5 (9 pts) (nesting depth added 11). Of this number, 41 points are the body's own statements and 19 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
svgDraw.drawEdges (cognitive 59) packages/mermaid/src/diagrams/architecture/svgDraw.ts:25— svgDraw.drawEdges has cognitive complexity 59 (threshold 15). Drivers by points: if/else 23 (37 pts), ternaries 6 (19 pts), boolean chains 3 (nesting depth added 27). None of this is in the body itself: all 59 points belong to one function literal inside it that branches (line 38). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
layoutCore.layoutContainer (cognitive 58) packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts:61— layoutCore.layoutContainer has cognitive complexity 58 (threshold 15). Drivers by points: ternaries 21 (33 pts), if/else 8 (14 pts), loops 8 (10 pts), boolean chains 1 (nesting depth added 20). Of this number, 57 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
geometry.buildOrthogonalPortPath (cognitive 56) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts:297— geometry.buildOrthogonalPortPath has cognitive complexity 56 (threshold 15). Drivers by points: boolean chains 25, if/else 11 (22 pts), ternaries 4 (9 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blockDB.populateBlockDatabase (cognitive 54) packages/mermaid/src/diagrams/block/blockDB.ts:105— blockDB.populateBlockDatabase has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (48 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
erBox.erBox (cognitive 52) packages/mermaid/src/rendering-util/rendering-elements/shapes/erBox.ts:19— erBox.erBox has cognitive complexity 52 (threshold 15). Drivers by points: if/else 26 (35 pts), boolean chains 10, ternaries 2 (4 pts), loops 3 (nesting depth added 11). Of this number, 44 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlowDB.getData (cognitive 52) packages/mermaid/src/diagrams/flowchart/flowDb.ts:1110— FlowDB.getData has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (28 pts), loops 11 (14 pts), boolean chains 7, ternaries 3 (nesting depth added 16). Of this number, 35 points are the body's own statements and 17 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validation.validateSwimlanesLayout (cognitive 51) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/validation.ts:54— validation.validateSwimlanesLayout has cognitive complexity 51 (threshold 15). Drivers by points: if/else 11 (29 pts), loops 7 (13 pts), boolean chains 5, ternaries 1 (4 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.
phase2.crossCounts.computeSubtreeCrossCounts (cognitive 51) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase2.crossCounts.ts:12— phase2.crossCounts.computeSubtreeCrossCounts has cognitive complexity 51 (threshold 15). Drivers by points: if/else 26 (54 pts), loops 16 (19 pts), boolean chains 6, ternaries 2 (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. This shape REPEATS in the file: one other method here (phase2.crossCounts.computeSubtreeCrossCounts::lcaIndex) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AgentFlowDB.getData (cognitive 51) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1696— AgentFlowDB.getData has cognitive complexity 51 (threshold 15). Drivers by points: if/else 18 (29 pts), loops 9 (10 pts), boolean chains 8, ternaries 4 (nesting depth added 12). Of this number, 26 points are the body's own statements and 25 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArchitectureDB.getDataStructures (cognitive 50) packages/mermaid/src/diagrams/architecture/architectureDb.ts:293— ArchitectureDB.getDataStructures has cognitive complexity 50 (threshold 15). Drivers by points: if/else 11 (40 pts), loops 4 (9 pts), boolean chains 1 (nesting depth added 34). Of this number, 33 points are the body's own statements and 17 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cynefinRenderer.draw (cognitive 50) packages/mermaid/src/diagrams/cynefin/cynefinRenderer.ts:71— cynefinRenderer.draw has cognitive complexity 50 (threshold 15). Drivers by points: if/else 17 (32 pts), ternaries 4 (8 pts), boolean chains 5, loops 4 (5 pts) (nesting depth added 20). Of this number, 37 points are the body's own statements and 13 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dataFetcher.dataFetcher (cognitive 49) packages/mermaid/src/diagrams/state/dataFetcher.ts:241— dataFetcher.dataFetcher has cognitive complexity 49 (threshold 15). Drivers by points: if/else 22 (44 pts), boolean chains 5 (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.
c4Db.updateElStyle (cognitive 48) packages/mermaid/src/diagrams/c4/c4Db.ts:494— c4Db.updateElStyle has cognitive complexity 48 (threshold 15). Drivers by points: if/else 29 (39 pts), boolean chains 9 (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.
sequenceRenderer.getMaxMessageWidthPerActor (cognitive 48) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1488— sequenceRenderer.getMaxMessageWidthPerActor has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 14, ternaries 3 (9 pts), loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
renderDoc (cognitive 47) packages/mermaid/src/diagrams/state/stateRenderer.js:89— renderDoc has cognitive complexity 47 (threshold 15). Drivers by points: if/else 18 (31 pts), ternaries 7 (12 pts), boolean chains 2, loops 2 (nesting depth added 18). Of this number, 32 points are the body's own statements and 15 belong to 5 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
layout.setBlockSizes (cognitive 45) packages/mermaid/src/diagrams/block/layout.ts:72— layout.setBlockSizes has cognitive complexity 45 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 6 (15 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 25). 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.
scoreLayout.computeNeighborhoodPreservation (cognitive 45) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:362— scoreLayout.computeNeighborhoodPreservation has cognitive complexity 45 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 5 (10 pts), ternaries 3 (10 pts), boolean chains 4 (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.
sharedTrackNudging.nudgeSharedInteriorSubpaths (cognitive 43) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/sharedTrackNudging.ts:13— sharedTrackNudging.nudgeSharedInteriorSubpaths has cognitive complexity 43 (threshold 15). Drivers by points: if/else 27 (57 pts), loops 10 (23 pts), boolean chains 22, ternaries 8 (nesting depth added 43). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (sharedTrackNudging.nudgeSharedInteriorSubpaths::candidateIsSafe) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
sequenceRenderer.draw (cognitive 43) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1043— sequenceRenderer.draw has cognitive complexity 43 (threshold 15). Drivers by points: if/else 20 (26 pts), ternaries 5, boolean chains 4, error handling 1 (3 pts), loops 3, match/switch 1 (2 pts) (nesting depth added 9). Of this number, 38 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
UsecaseModelBuilder.applyMetadataAssignments (cognitive 42) packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:620— UsecaseModelBuilder.applyMetadataAssignments has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 5 (11 pts), boolean chains 6, ternaries 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
lrTransform.applyLrDirectionTransform (cognitive 40) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/lrTransform.ts:150— lrTransform.applyLrDirectionTransform has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (26 pts), loops 9 (10 pts), boolean chains 3, ternaries 1 (nesting depth added 11). Of this number, 39 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
materializedGeometry.resolveRenderedOrthogonalCrossings (cognitive 40) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1835— materializedGeometry.resolveRenderedOrthogonalCrossings has cognitive complexity 40 (threshold 15). Drivers by points: if/else 50 (102 pts), loops 56 (91 pts), boolean chains 31, ternaries 8 (10 pts), match/switch 1 (nesting depth added 89). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (materializedGeometry.resolveRenderedOrthogonalCrossings::bestPairedReplacement) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
agentflowDb.stripLineTrailingCommas (cognitive 40) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:150— agentflowDb.stripLineTrailingCommas has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 6, ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
genColor (cognitive 39) packages/mermaid/src/diagrams/git/styles.js:30— genColor has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 6 (22 pts), if/else 7 (11 pts), loops 3 (6 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phase2.crossLaneAdjust.adjustCrossLaneSources (cognitive 38) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase2.crossLaneAdjust.ts:8— phase2.crossLaneAdjust.adjustCrossLaneSources has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 4 (7 pts), boolean chains 4 (nesting depth added 18). Of this number, 37 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
svgDraw.drawText (cognitive 38) REDACTED:192— svgDraw.drawText has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 6, match/switch 2 (4 pts), loops 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.
boxDrawingPreprocessor.preprocessBoxDrawing (cognitive 38) packages/mermaid/src/diagrams/treeView/boxDrawingPreprocessor.ts:67— boxDrawingPreprocessor.preprocessBoxDrawing has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (25 pts), loops 6 (10 pts), boolean chains 3 (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.
groups.buildGridForest (cognitive 38) packages/mermaid/src/rendering-util/layout-algorithms/grid/groups.ts:21— groups.buildGridForest has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (33 pts), loops 5 (nesting depth added 17). Of this number, 25 points are the body's own statements and 13 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
draw::makeGrid (cognitive 38) packages/mermaid/src/diagrams/gantt/ganttRenderer.js:649— draw::makeGrid has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (22 pts), match/switch 2 (9 pts), boolean chains 6, other 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.
gitGraphRenderer.drawCommitBullet (cognitive 37) packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:226— gitGraphRenderer.drawCommitBullet has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 14 (30 pts), if/else 5 (7 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.
layout.layoutBlocks (cognitive 36) packages/mermaid/src/diagrams/block/layout.ts:209— layout.layoutBlocks has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (25 pts), loops 3 (6 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PropertyOrderCollector.readString (cognitive 36) packages/mermaid/src/diagrams/usecase/parser/usecaseJson.ts:201— PropertyOrderCollector.readString has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (33 pts), match/switch 1 (2 pts), loops 1 (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.
lineJump.rewriteEdgePath (cognitive 35) packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts:416— lineJump.rewriteEdgePath has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 4 (6 pts), ternaries 2 (4 pts), boolean chains 3 (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.
materializedGeometry.shiftLeftLaneTitleBandsLeftOfRails (cognitive 34) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:848— materializedGeometry.shiftLeftLaneTitleBandsLeftOfRails has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 7, loops 4 (7 pts) (nesting depth added 8). Of this number, 19 points are the body's own statements and 15 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fixCorners (cognitive 34) packages/mermaid/src/rendering-util/rendering-elements/edges.js:550— fixCorners has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 4 (20 pts), if/else 6 (12 pts), boolean chains 1, loops 1 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
assignWithDepth.assignWithDepth (cognitive 33) packages/mermaid/src/assignWithDepth.ts:30— assignWithDepth.assignWithDepth has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 5 (nesting depth added 13). Most of this is not in the body itself: 12 of the 33 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 57, 41). 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.
lineJump.applyLineJumpsToSvg (cognitive 33) packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts:646— lineJump.applyLineJumpsToSvg has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 5, boolean chains 4, ternaries 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.
vennRenderer.draw (cognitive 33) packages/mermaid/src/diagrams/venn/vennRenderer.ts:31— vennRenderer.draw has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 10, ternaries 4 (5 pts), loops 2 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 14 of the 33 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 121, 173, 220). 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.
lineJump.findEdgeIntersections (cognitive 32) packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts:205— lineJump.findEdgeIntersections has cognitive complexity 32 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 4 (10 pts), ternaries 1 (5 pts), boolean chains 1 (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.
render.applyElkEdgeLayout (cognitive 32) packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1945— render.applyElkEdgeLayout has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 5, loops 4 (5 pts) (nesting depth added 6). Most of this is not in the body itself: 12 of the 32 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1998, 1967). 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.
phase2.gravity.assignLayers_Gravity (cognitive 32) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase2.gravity.ts:18— phase2.gravity.assignLayers_Gravity has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 6 (7 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 11). Most of this is not in the body itself: 15 of the 32 points are its own statements and the rest belongs to 3 function items inside it that branch (relaxOrder, a function literal at line 30, clampFeasible). 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.
usecaseDb.getData (cognitive 32) packages/mermaid/src/diagrams/usecase/usecaseDb.ts:295— usecaseDb.getData has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 8 (16 pts), loops 8, boolean chains 4, if/else 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.
requirementBox.requirementBox (cognitive 31) packages/mermaid/src/rendering-util/rendering-elements/shapes/requirementBox.ts:15— requirementBox.requirementBox has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (15 pts), ternaries 7 (13 pts), boolean chains 3 (nesting depth added 8). Of this number, 26 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
edges.insertEdgeLabel (cognitive 31) packages/mermaid/src/rendering-util/rendering-elements/edges.js:74— edges.insertEdgeLabel has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 5, ternaries 1 (nesting depth added 9). Of this number, 27 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
subgraphFeedbackEdges.findSubgraphFeedbackEdges (cognitive 31) packages/mermaid/src/rendering-util/layout-algorithms/elk/subgraphFeedbackEdges.ts:42— subgraphFeedbackEdges.findSubgraphFeedbackEdges has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 5 (11 pts), boolean chains 2 (nesting depth added 17). Of this number, 27 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
materializedGeometry.liftTopLaneTitleBandsAboveRails (cognitive 31) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:720— materializedGeometry.liftTopLaneTitleBandsAboveRails has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 7, loops 4 (7 pts) (nesting depth added 8). Of this number, 18 points are the body's own statements and 13 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
layout.intersection (cognitive 30) packages/mermaid-layout-tidy-tree/src/layout.ts:389— layout.intersection has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (18 pts), ternaries 6 (11 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.
materializedGeometry.shortcutRedundantOrthogonalJogs (cognitive 30) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1587— materializedGeometry.shortcutRedundantOrthogonalJogs has cognitive complexity 30 (threshold 15). Drivers by points: if/else 18 (39 pts), loops 13 (28 pts), boolean chains 16, ternaries 5 (6 pts) (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. This shape REPEATS in the file: one other method here (materializedGeometry.shortcutRedundantOrthogonalJogs::candidateIsSafe) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
usecaseRenderer.annotateUsecaseElements (cognitive 30) packages/mermaid/src/diagrams/usecase/usecaseRenderer.ts:144— usecaseRenderer.annotateUsecaseElements has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 6 (17 pts), if/else 6 (9 pts), boolean chains 3, loops 1 (nesting depth added 14). Of this number, 26 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
svgDraw.drawRels (cognitive 29) packages/mermaid/src/diagrams/c4/svgDraw.ts:26— svgDraw.drawRels has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 4 (8 pts), boolean chains 3, loops 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.
mermaidAPI.renderDiagram (cognitive 29) REDACTED:477— mermaidAPI.renderDiagram has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (24 pts), error handling 2, ternaries 2, boolean chains 1 (nesting depth added 5). Of this number, 24 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
materializedGeometry.reassignCrossingExternalRailChannels (cognitive 29) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1210— materializedGeometry.reassignCrossingExternalRailChannels has cognitive complexity 29 (threshold 15). Drivers by points: if/else 28 (70 pts), loops 26 (49 pts), ternaries 10 (17 pts), boolean chains 11 (nesting depth added 72). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (materializedGeometry.reassignCrossingExternalRailChannels::externalRailForSegment, materializedGeometry.reassignCrossingExternalRailChannels::candidateIsSafe) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AgentFlowDB.addSubGraph (cognitive 29) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1175— AgentFlowDB.addSubGraph has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4, loops 2 (4 pts), ternaries 2 (4 pts) (nesting depth added 9). Of this number, 19 points are the body's own statements and 10 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
drawNode (cognitive 29) packages/mermaid/src/diagrams/timeline/svgDraw.js:498— drawNode has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 7 (19 pts), if/else 4 (7 pts), other 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.
edges.intersection (cognitive 28) packages/mermaid/src/rendering-util/rendering-elements/edges.js:413— edges.intersection has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 6 (11 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.
endpointClip.snapEndpointToBoundary (cognitive 28) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/endpointClip.ts:105— endpointClip.snapEndpointToBoundary has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (22 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scoreLayout.scoreLayout (cognitive 28) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:503— scoreLayout.scoreLayout has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 10 (15 pts), if/else 4 (8 pts), loops 4, 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.
drawActorTypeCollections (cognitive 28) REDACTED:516— drawActorTypeCollections has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (22 pts), ternaries 3, boolean chains 2, other 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
kanbanItem.kanbanItem (cognitive 27) packages/mermaid/src/rendering-util/rendering-elements/shapes/kanbanItem.ts:23— kanbanItem.kanbanItem has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 16, if/else 6 (7 pts), ternaries 2 (4 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
sharedTrackNudging.nudgeSharedInteriorSubpaths::candidateIsSafe (cognitive 27) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/sharedTrackNudging.ts:72— sharedTrackNudging.nudgeSharedInteriorSubpaths::candidateIsSafe has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 4 (7 pts), boolean chains 2, ternaries 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. This shape REPEATS in the file: one other method here (sharedTrackNudging.nudgeSharedInteriorSubpaths) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
renderHelpers.insertEdges (cognitive 27) packages/mermaid/src/diagrams/block/renderHelpers.ts:215— renderHelpers.insertEdges has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 3 (12 pts), if/else 4 (11 pts), boolean chains 2, loops 2 (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.
drawActorTypeDatabase (cognitive 27) REDACTED:999— drawActorTypeDatabase has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (18 pts), ternaries 5, boolean chains 2, other 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.
ClassMember.parseMember (cognitive 26) packages/mermaid/src/diagrams/class/classTypes.ts:80— ClassMember.parseMember has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (19 pts), ternaries 4 (7 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.
edges.positionEdgeLabel (cognitive 26) packages/mermaid/src/rendering-util/rendering-elements/edges.js:301— edges.positionEdgeLabel has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 5 (13 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.
materializedGeometry.collapseRedundantRectangularDoglegs::candidateIsSafe (cognitive 26) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:368— materializedGeometry.collapseRedundantRectangularDoglegs::candidateIsSafe has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 4 (7 pts), boolean chains 2 (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. This shape REPEATS in the file: one other method here (materializedGeometry.collapseRedundantRectangularDoglegs) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
gitGraphAst.cherryPick (cognitive 26) packages/mermaid/src/diagrams/git/gitGraphAst.ts:261— gitGraphAst.cherryPick has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 8, ternaries 3 (7 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.
journeyRenderer.drawActorLegend (cognitive 26) packages/mermaid/src/diagrams/user-journey/journeyRenderer.ts:19— journeyRenderer.drawActorLegend has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 1 (4 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 14). None of this is in the body itself: all 26 points belong to 3 function literals inside it that branch (lines 53, 25, 94). 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.
kanbanDb.addNode (cognitive 26) packages/mermaid/src/diagrams/kanban/kanbanDb.ts:99— kanbanDb.addNode has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 5, 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.
PropertyOrderCollector.consumeNumber (cognitive 26) packages/mermaid/src/diagrams/usecase/parser/usecaseJson.ts:286— PropertyOrderCollector.consumeNumber has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 8, loops 3 (6 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.
drawActorTypeParticipant (cognitive 26) REDACTED:391— drawActorTypeParticipant has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 2, other 1, ternaries 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
sanitizeDirective.sanitizeDirective (cognitive 25) packages/mermaid/src/utils/sanitizeDirective.ts:38— sanitizeDirective.sanitizeDirective has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (5 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.
render.internalEdgePoints (cognitive 25) packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1406— render.internalEdgePoints has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 3 (11 pts), if/else 2 (6 pts), loops 3 (6 pts), boolean chains 2 (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.
materializedGeometry.liftObstacleHuggingSameSideRails (cognitive 25) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:511— materializedGeometry.liftObstacleHuggingSameSideRails has cognitive complexity 25 (threshold 15). Drivers by points: if/else 18 (38 pts), loops 11 (23 pts), ternaries 3 (5 pts), boolean chains 4 (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. This shape REPEATS in the file: one other method here (materializedGeometry.liftObstacleHuggingSameSideRails::candidateIsSafe) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
phase3.ordering.transposeImprove (cognitive 25) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase3.ordering.ts:185— phase3.ordering.transposeImprove has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (5 pts), boolean chains 4, ternaries 3 (nesting depth added 9). Of this number, 21 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassDB.getData (cognitive 25) packages/mermaid/src/diagrams/class/classDb.ts:748— ClassDB.getData has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 7 (14 pts), loops 5, if/else 2 (4 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.
vennRenderer.renderTextNodes (cognitive 25) packages/mermaid/src/diagrams/venn/vennRenderer.ts:247— vennRenderer.renderTextNodes has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (4 pts), ternaries 2 (4 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.
drawActorTypeQueue (cognitive 25) REDACTED:641— drawActorTypeQueue has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 2, other 1, ternaries 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
createContainerGroup (cognitive 25) packages/mermaid/src/rendering-util/rendering-elements/clusters.js:524— createContainerGroup has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 3 (5 pts), boolean chains 1, other 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.
mermaid-graphlib.adjustClustersAndEdges (cognitive 24) packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:200— mermaid-graphlib.adjustClustersAndEdges has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 4, loops 1 (nesting depth added 7). Of this number, 13 points are the body's own statements and 11 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
geometry.intersection (cognitive 24) packages/mermaid/src/rendering-util/layout-algorithms/elk/geometry.ts:46— geometry.intersection has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 6 (11 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.
detourSimplification.simplifyDetouredEdges::pathConflictCount (cognitive 24) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/detourSimplification.ts:75— detourSimplification.simplifyDetouredEdges::pathConflictCount has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (6 pts), boolean chains 4 (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. This shape REPEATS in the file: one other method here (detourSimplification.simplifyDetouredEdges) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
driving-tree.buildDrivingTree (cognitive 24) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/driving-tree.ts:34— driving-tree.buildDrivingTree has cognitive complexity 24 (threshold 15). Drivers by points: loops 12 (13 pts), if/else 6 (11 pts) (nesting depth added 6). 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.
QuadrantBuilder.getAxisLabels (cognitive 24) packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts:286— QuadrantBuilder.getAxisLabels has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 8 (16 pts), boolean chains 4, if/else 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.
sequenceRenderer.calculateLoopBounds (cognitive 24) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:2041— sequenceRenderer.calculateLoopBounds has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 2 (6 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 13). Of this number, 19 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils.detectDirective (cognitive 23) packages/mermaid/src/utils.ts:159— utils.detectDirective has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 3 (5 pts), boolean chains 4, error handling 1, 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.
utils.calculatePoint (cognitive 23) packages/mermaid/src/utils.ts:333— utils.calculatePoint has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (21 pts), boolean chains 1, loops 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.
c4Renderer.drawInsideBoundary (cognitive 23) packages/mermaid/src/diagrams/c4/c4Renderer.ts:435— c4Renderer.drawInsideBoundary has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4, ternaries 1 (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.
render.straightenEdgeTerminals (cognitive 23) packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1888— render.straightenEdgeTerminals has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 8, loops 2 (3 pts), ternaries 2 (3 pts) (nesting depth added 7). Of this number, 18 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
phase3.ordering.reorderLayer (cognitive 23) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase3.ordering.ts:110— phase3.ordering.reorderLayer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 4 (8 pts), boolean chains 3 (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.
ganttRenderer.draw::drawExcludeDays (cognitive 23) packages/mermaid/src/diagrams/gantt/ganttRenderer.js:547— ganttRenderer.draw::drawExcludeDays has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, loops 2 (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. This shape REPEATS in the file: one other method here (ganttRenderer.draw) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
StateDB.addState (cognitive 23) packages/mermaid/src/diagrams/state/stateDb.ts:398— StateDB.addState has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 4 (8 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.
architectureRenderer.getAlignments (cognitive 23) packages/mermaid/src/diagrams/architecture/architectureRenderer.ts:155— architectureRenderer.getAlignments has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 23 points belong to 3 function items inside it that branch (flattenAlignments, a function literal at line 218, a function literal at line 274). 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.
usecaseDb.flattenJsonRows::visit (cognitive 23) packages/mermaid/src/diagrams/usecase/usecaseDb.ts:164— usecaseDb.flattenJsonRows::visit has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (7 pts), ternaries 2 (7 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.
c4Db.updateRelStyle (cognitive 22) packages/mermaid/src/diagrams/c4/c4Db.ts:593— c4Db.updateRelStyle has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 5 (nesting depth added 4). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
edgeLabelNodes.createEdgeLabelNodes (cognitive 22) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/edgeLabelNodes.ts:38— edgeLabelNodes.createEdgeLabelNodes has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 4 (8 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.
laneOrdering.buildWeightedLaneEdges (cognitive 22) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/laneOrdering.ts:74— laneOrdering.buildWeightedLaneEdges has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 3 (6 pts), boolean chains 3, 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.
AgentFlowDB.rethrowMetadataYamlError (cognitive 22) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:611— AgentFlowDB.rethrowMetadataYamlError has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, loops 2 (3 pts), ternaries 2, error handling 1 (nesting depth added 6). Of this number, 20 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gitGraphRenderer.drawBranches (cognitive 22) packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:867— gitGraphRenderer.drawBranches has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 8 (10 pts), boolean chains 1 (nesting depth added 4). None of this is in the body itself: all 22 points belong to one function literal inside it that branches (line 878). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ganttDb.getStartDate (cognitive 22) packages/mermaid/src/diagrams/gantt/ganttDb.js:305— ganttDb.getStartDate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 8). Of this number, 21 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SequenceDB.apply (cognitive 22) packages/mermaid/src/diagrams/sequence/sequenceDb.ts:557— SequenceDB.apply has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 1 (2 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.
sequenceRenderer.addActorRenderingData (cognitive 22) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:743— sequenceRenderer.addActorRenderingData has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 6, 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.
sequenceRenderer.buildMessageModel (cognitive 22) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1867— sequenceRenderer.buildMessageModel has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 4, boolean chains 3 (nesting depth added 5). Of this number, 21 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scoreLayout.computeRankFaithfulness (cognitive 22) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:275— scoreLayout.computeRankFaithfulness has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 8 (9 pts), boolean chains 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.
mermaid-graphlib.extractor (cognitive 21) packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:311— mermaid-graphlib.extractor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, loops 3, ternaries 1 (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.
materializedGeometry.resolveRenderedOrthogonalCrossings::bestPairedReplacement (cognitive 21) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:2699— materializedGeometry.resolveRenderedOrthogonalCrossings::bestPairedReplacement has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 5 (9 pts), boolean chains 1, ternaries 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. This shape REPEATS in the file: one other method here (materializedGeometry.resolveRenderedOrthogonalCrossings) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
phase2.longestPath.assignLayers_LongestPath (cognitive 21) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase2.longestPath.ts:12— phase2.longestPath.assignLayers_LongestPath has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 8). Of this number, 17 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ganttDb.getEndDate (cognitive 21) packages/mermaid/src/diagrams/gantt/ganttDb.js:409— ganttDb.getEndDate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 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.
SequenceDB.addActor (cognitive 21) packages/mermaid/src/diagrams/sequence/sequenceDb.ts:155— SequenceDB.addActor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 5 (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.
runner.matchExpected (cognitive 21) packages/mermaid/src/diagrams/agentflow/conformance/runner.ts:193— runner.matchExpected has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
runner.matchSemanticAssertions (cognitive 21) packages/mermaid/src/diagrams/agentflow/conformance/runner.ts:254— runner.matchSemanticAssertions has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scoreLayout.hasDiagonalRenderedEndpoint (cognitive 21) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:180— scoreLayout.hasDiagonalRenderedEndpoint has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (8 pts), boolean chains 7, if/else 5 (6 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.
regexes.matchFrontMatter (cognitive 20) packages/mermaid/src/diagram-api/regexes.ts:135— regexes.matchFrontMatter has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 5, boolean chains 3, ternaries 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
shapeUtil.addText (cognitive 20) packages/mermaid/src/diagrams/class/shapeUtil.ts:99— shapeUtil.addText has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 2, ternaries 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.
c4Db.addContainer (cognitive 20) packages/mermaid/src/diagrams/c4/c4Db.ts:199— c4Db.addContainer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 5 (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. This shape REPEATS in the file: 2 other methods here (c4Db.addComponent, c4Db.addDeploymentNode) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
c4Db.addComponent (cognitive 20) packages/mermaid/src/diagrams/c4/c4Db.ts:259— c4Db.addComponent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 5 (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. This shape REPEATS in the file: 2 other methods here (c4Db.addContainer, c4Db.addDeploymentNode) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
c4Db.addDeploymentNode (cognitive 20) packages/mermaid/src/diagrams/c4/c4Db.ts:421— c4Db.addDeploymentNode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 5 (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. This shape REPEATS in the file: 2 other methods here (c4Db.addContainer, c4Db.addComponent) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
gitGraphRenderer.drawCommitLabel (cognitive 20) packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:331— gitGraphRenderer.drawCommitLabel has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 5 (nesting depth added 8). 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.
styles.getStyles (cognitive 20) packages/mermaid/src/diagrams/state/styles.js:101— styles.getStyles has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 16, ternaries 4. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
architectureRenderer.getRelativeConstraints (cognitive 20) packages/mermaid/src/diagrams/architecture/architectureRenderer.ts:291— architectureRenderer.getRelativeConstraints has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2, boolean chains 1 (nesting depth added 11). None of this is in the body itself: all 20 points belong to 3 function literals inside it that branch (lines 324, 308, 345). 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.
vennRenderer.ensurePairwiseSubsets (cognitive 20) packages/mermaid/src/diagrams/venn/vennRenderer.ts:393— vennRenderer.ensurePairwiseSubsets has cognitive complexity 20 (threshold 15). Drivers by points: if/else 2 (6 pts), loops 3 (6 pts), ternaries 2 (6 pts), boolean chains 2 (nesting depth added 11). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UsecaseModelBuilder.collectElement (cognitive 20) packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:358— UsecaseModelBuilder.collectElement has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 7, if/else 7, ternaries 3 (6 pts) (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.
measureDagreGraph (cognitive 20) packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:259— measureDagreGraph has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), other 4, boolean chains 2 (nesting depth added 3). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 294, a function literal at line 377, processEdges). 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.
swimlane (cognitive 20) packages/mermaid/src/rendering-util/rendering-elements/clusters/swimlane.js:16— swimlane has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 3, other 2, 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.
createText.createText (cognitive 19) REDACTED:306— createText.createText has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 4 (8 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.
util.labelHelper (cognitive 19) packages/mermaid/src/rendering-util/rendering-elements/shapes/util.ts:50— util.labelHelper has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10, boolean chains 7, ternaries 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.
edgeMarker.addEdgeMarker (cognitive 19) packages/mermaid/src/rendering-util/rendering-elements/edgeMarker.ts:71— edgeMarker.addEdgeMarker has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, ternaries 2 (nesting depth added 6). Of this number, 15 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render.sanitizeElkEdgePoints (cognitive 19) packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:2483— render.sanitizeElkEdgePoints has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (9 pts), ternaries 1 (nesting depth added 2). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
geometry.orthogonalSegmentsCross (cognitive 19) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts:483— geometry.orthogonalSegmentsCross has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, if/else 3, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
materializedGeometry.collapseRedundantRectangularDoglegs (cognitive 19) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:357— materializedGeometry.collapseRedundantRectangularDoglegs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (33 pts), loops 7 (13 pts), boolean chains 9 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (materializedGeometry.collapseRedundantRectangularDoglegs::candidateIsSafe) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
materializedGeometry.shortcutRedundantOrthogonalJogs::candidateIsSafe (cognitive 19) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1747— materializedGeometry.shortcutRedundantOrthogonalJogs::candidateIsSafe has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 4 (7 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. This shape REPEATS in the file: one other method here (materializedGeometry.shortcutRedundantOrthogonalJogs) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ganttRenderer.draw (cognitive 19) packages/mermaid/src/diagrams/gantt/ganttRenderer.js:85— ganttRenderer.draw has cognitive complexity 19 (threshold 15). Drivers by points: if/else 85 (117 pts), loops 13 (17 pts), boolean chains 14, match/switch 2 (9 pts), ternaries 4 (5 pts) (nesting depth added 44). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ganttRenderer.draw::drawExcludeDays) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
quadrantDb.parseStyles (cognitive 19) packages/mermaid/src/diagrams/quadrant-chart/quadrantDb.ts:64— quadrantDb.parseStyles has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 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.
sequenceRenderer.adjustCreatedDestroyedData (cognitive 19) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:946— sequenceRenderer.adjustCreatedDestroyedData has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 3 (8 pts) (nesting depth added 7). Of this number, 15 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
timelineRenderer.draw (cognitive 19) packages/mermaid/src/diagrams/timeline/timelineRenderer.ts:29— timelineRenderer.draw has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 5). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
architectureRenderer.layoutArchitecture (cognitive 19) packages/mermaid/src/diagrams/architecture/architectureRenderer.ts:375— architectureRenderer.layoutArchitecture has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 3 (6 pts), boolean chains 2, match/switch 2, error handling 1, loops 1 (nesting depth added 7). None of this is in the body itself: all 19 points belong to 3 function literals inside it that branch (lines 513, 383, 514). 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.
UsecaseVisitor.entityName (cognitive 19) packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts:288— UsecaseVisitor.entityName has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (16 pts), boolean chains 2, if/else 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.
geometry.mergeCollinear (cognitive 19) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/geometry.ts:61— geometry.mergeCollinear has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 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.
drawAttributes (cognitive 19) packages/mermaid/src/diagrams/er/erRenderer.js:45— drawAttributes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 3 (5 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 71, 61, 204). 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.
layout.calculateEdgePositions (cognitive 18) packages/mermaid-layout-tidy-tree/src/layout.ts:455— layout.calculateEdgePositions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 4, boolean chains 1 (nesting depth added 2). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 465). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
tiltedCylinder.tiltedCylinder (cognitive 18) packages/mermaid/src/rendering-util/rendering-elements/shapes/tiltedCylinder.ts:57— tiltedCylinder.tiltedCylinder has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, ternaries 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.
docs.transformMarkdownAst (cognitive 18) packages/mermaid/scripts/docs.mts:310— docs.transformMarkdownAst has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 4). None of this is in the body itself: all 18 points belong to 2 function literals inside it that branch (lines 316, 317). 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.
materializedGeometry.liftObstacleHuggingSameSideRails::candidateIsSafe (cognitive 18) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:633— materializedGeometry.liftObstacleHuggingSameSideRails::candidateIsSafe has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (materializedGeometry.liftObstacleHuggingSameSideRails) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
labelAnchoring.anchorLabelsToPolyline::tryPool (cognitive 18) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/labelAnchoring.ts:386— labelAnchoring.anchorLabelsToPolyline::tryPool has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (3 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. This shape REPEATS in the file: one other method here (labelAnchoring.anchorLabelsToPolyline) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
phase2.crossOptimization.optimizeRanksByCrossings (cognitive 18) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase2.crossOptimization.ts:62— phase2.crossOptimization.optimizeRanksByCrossings has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
shapes.normaliseNodeShapes (cognitive 18) packages/mermaid/src/diagrams/agentflow/shapes.ts:114— shapes.normaliseNodeShapes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 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.
gitGraphAst.merge (cognitive 18) packages/mermaid/src/diagrams/git/gitGraphAst.ts:152— gitGraphAst.merge has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, boolean chains 5, ternaries 5. 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.
QuadrantBuilder.getDefaultConfig (cognitive 18) packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts:153— QuadrantBuilder.getDefaultConfig has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 18. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ishikawaRenderer.draw (cognitive 18) packages/mermaid/src/diagrams/ishikawa/ishikawaRenderer.ts:36— ishikawaRenderer.draw has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 2 (3 pts), ternaries 3 (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.
scoreLayout.evaluateThresholds (cognitive 18) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:461— scoreLayout.evaluateThresholds has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 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.
screenshot-sheets.byDeclaration (cognitive 18) scripts/screenshot-sheets.ts:309— screenshot-sheets.byDeclaration has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 4 (8 pts), boolean chains 2 (nesting depth added 7). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 310). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
getStyles (cognitive 18) packages/mermaid/src/diagrams/git/styles.js:118— getStyles has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 17, other 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.
drawActorTypeEntity (cognitive 18) REDACTED:891— drawActorTypeEntity has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, ternaries 7 (8 pts), other 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.
docs.processDocs (cognitive 17) packages/mermaid/scripts/docs.mts:601— docs.processDocs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 1, ternaries 1 (nesting depth added 4). Of this number, 11 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
c4Db.addRel (cognitive 17) packages/mermaid/src/diagrams/c4/c4Db.ts:86— c4Db.addRel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 4 (nesting depth added 2). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
FlowDB.addSubGraph (cognitive 17) packages/mermaid/src/diagrams/flowchart/flowDb.ts:674— FlowDB.addSubGraph has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, ternaries 2 (4 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 691). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
mermaid.runThrowsErrors (cognitive 17) packages/mermaid/src/mermaid.ts:130— mermaid.runThrowsErrors has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), error handling 1 (2 pts), loops 1, ternaries 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.
createGraph.createGraphWithElements (cognitive 17) packages/mermaid/src/rendering-util/createGraph.ts:123— createGraph.createGraphWithElements has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 6). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 161). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
geometry.segmentConflictsWithAnyEdge (cognitive 17) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts:544— geometry.segmentConflictsWithAnyEdge has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 4, loops 2 (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.
geometry.orthogonalizePolyline (cognitive 17) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts:652— geometry.orthogonalizePolyline has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 2 (4 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.
ClassDB.setClickFunc (cognitive 17) packages/mermaid/src/diagrams/class/classDb.ts:446— ClassDB.setClickFunc has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 8). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parser.populate (cognitive 17) packages/mermaid/src/diagrams/packet/parser.ts:11— parser.populate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 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.
UsecaseModelBuilder.applyActorProperty (cognitive 17) packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:721— UsecaseModelBuilder.applyActorProperty has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7 (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.
usecaseRenderer.prepareUsecaseLayoutData (cognitive 17) packages/mermaid/src/diagrams/usecase/usecaseRenderer.ts:100— usecaseRenderer.prepareUsecaseLayoutData has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 2 (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.
placement.readGridConfig (cognitive 17) packages/mermaid/src/rendering-util/layout-algorithms/grid/placement.ts:96— placement.readGridConfig has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 10, boolean chains 6, 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.
placement.resolveGridPlacements (cognitive 17) packages/mermaid/src/rendering-util/layout-algorithms/grid/placement.ts:255— placement.resolveGridPlacements has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2, ternaries 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.
drawLoop (cognitive 17) REDACTED:1519— drawLoop has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 2, loops 1 (2 pts), ternaries 2, other 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 1 belongs to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stateEnd.stateEnd (cognitive 16) packages/mermaid/src/rendering-util/rendering-elements/shapes/stateEnd.ts:8— stateEnd.stateEnd has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 2, ternaries 1 (2 pts) (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.
c4Renderer.drawRels (cognitive 16) packages/mermaid/src/diagrams/c4/c4Renderer.ts:387— c4Renderer.drawRels has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 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.
endpointClip.snapAndCollapseEndpoints (cognitive 16) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/endpointClip.ts:405— endpointClip.snapAndCollapseEndpoints has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 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.
terminalStub.collapseShortTerminalStub::segmentCrossesOtherEdge (cognitive 16) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/terminalStub.ts:159— terminalStub.collapseShortTerminalStub::segmentCrossesOtherEdge has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 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. This shape REPEATS in the file: one other method here (terminalStub.collapseShortTerminalStub) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
phase2.crossCounts.computeSubtreeCrossCounts::lcaIndex (cognitive 16) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase2.crossCounts.ts:95— phase2.crossCounts.computeSubtreeCrossCounts::lcaIndex has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, loops 2 (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. This shape REPEATS in the file: one other method here (phase2.crossCounts.computeSubtreeCrossCounts) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AgentFlowDB.addSingleLink (cognitive 16) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:728— AgentFlowDB.addSingleLink has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3 (nesting depth added 3). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
ErDB.addCssStyles (cognitive 16) packages/mermaid/src/diagrams/er/erDb.ts:182— ErDB.addCssStyles has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LinePlot.getDrawableElement (cognitive 16) packages/mermaid/src/diagrams/xychart/chartBuilder/components/plot/linePlot.ts:14— LinePlot.getDrawableElement has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 1 (2 pts), boolean chains 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.
sequenceRenderer.drawCentralConnection (cognitive 16) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:288— sequenceRenderer.drawCentralConnection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 2 (3 pts), ternaries 2 (nesting depth added 7). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sequenceRenderer.calculateActorMargins (cognitive 16) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1614— sequenceRenderer.calculateActorMargins has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2, ternaries 1 (2 pts), boolean chains 1 (nesting depth added 5). Of this number, 13 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ishikawaRenderer.drawBranch (cognitive 16) packages/mermaid/src/diagrams/ishikawa/ishikawaRenderer.ts:345— ishikawaRenderer.drawBranch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2, ternaries 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.
parser.populate (cognitive 16) packages/mermaid/src/diagrams/treemap/parser.ts:13— parser.populate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 3 (6 pts), loops 3, boolean chains 1 (nesting depth added 6). Of this number, 12 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UsecaseModelBuilder.validateAndRefreshElements (cognitive 16) packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:760— UsecaseModelBuilder.validateAndRefreshElements has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 4, ternaries 1 (2 pts), loops 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.
UsecaseModelBuilder.getStylable (cognitive 16) packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:871— UsecaseModelBuilder.getStylable has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 1 (nesting depth added 10). 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.
wardleyParser.populateDb (cognitive 16) packages/mermaid/src/diagrams/wardley/wardleyParser.ts:68— wardleyParser.populateDb has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, ternaries 4 (nesting depth added 1). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 174, 99, 138, …). 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.
geometry.segmentsCross (cognitive 16) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/geometry.ts:158— geometry.segmentsCross has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 4 (5 pts), ternaries 2 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
validateLayout.nearEndpointBandDistance (cognitive 16) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:563— validateLayout.nearEndpointBandDistance has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 4 (6 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.
layoutCore.materializeAbsoluteGeometry (cognitive 16) packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts:287— layoutCore.materializeAbsoluteGeometry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), 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.
usecaseSystemBoundary (cognitive 16) packages/mermaid/src/rendering-util/rendering-elements/clusters.js:688— usecaseSystemBoundary has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, ternaries 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.
getSelfLoopSide (cognitive 16) packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:61— getSelfLoopSide has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 2 (4 pts), boolean chains 2, other 1 (nesting depth added 3). Of this number, 8 points are the body's own statements and 8 belong to 5 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Cross-context type DiagramAST (parser → mermaid) packages/mermaid/src/diagrams/common/populateCommonDb.ts:4— DiagramAST (context parser) is exposed in mermaid's public surface via populateCommonDb.populateCommonDb — couples the contexts.
Change-coupling hub: textDimensionCalculator.ts → index.ts, orchestrator.ts, xychartDb.ts packages/mermaid/src/diagrams/xychart/chartBuilder/textDimensionCalculator.ts— `packages/mermaid/src/diagrams/xychart/chartBuilder/textDimensionCalculator.ts` changes together with 3 other files — `packages/mermaid/src/diagrams/xychart/chartBuilder/index.ts`, `packages/mermaid/src/diagrams/xychart/chartBuilder/orchestrator.ts`, `packages/mermaid/src/diagrams/xychart/xychartDb.ts` — 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.
Off the main sequence: @mermaid-js/parser — @mermaid-js/parser: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Hollow method — returns a constant without doing the work packages/mermaid/src/diagrams/eventmodeling/styles.js:1— `getStyles` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Duplication concentrated across 34 sibling directories (100 clone groups) packages/mermaid/src/diagrams/timeline/svgDraw.js:19— 100 duplicated blocks under packages/mermaid/src/diagrams/ have copies in at least two of the sibling directories agentflow, architecture, block, c4, class, common (+28 more sibling(s) not listed) — 81 of them are reported below, and 19 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 100 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 100 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 100 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (15 clone groups) packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:1022— 15 duplicated blocks under packages/mermaid/src/ have copies in at least two of the sibling directories diagrams, rendering-util — 11 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 14 sibling directories (12 clone groups) packages/parser/src/language/railroad-peg/valueConverter.ts:5— 12 duplicated blocks under packages/parser/src/language/ have copies in at least two of the sibling directories architecture, cynefin, eventmodeling, gitGraph, info, packet (+8 more sibling(s) not listed) — 8 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 4 sibling directories (10 clone groups) packages/mermaid-layout-tidy-tree/src/render.ts:11— 10 duplicated blocks under packages/ have copies in at least two of the sibling directories mermaid, mermaid-example-diagram, mermaid-layout-tidy-tree, mermaid-zenuml — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (6 clone groups) packages/mermaid/src/rendering-util/layout-algorithms/ddlt/baselineDdltSpec.ts:137— 6 duplicated blocks under packages/mermaid/src/rendering-util/layout-algorithms/ have copies in at least two of the sibling directories ddlt, layout-utils, swimlanes — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (291 identical lines × 2 files) packages/mermaid/src/themes/theme-neo-dark.js:1— packages/mermaid/src/themes/theme-neo-dark.js:1 · packages/mermaid/src/themes/theme-redux-dark.js:1 — these 2 files are line-for-line copies of one another — 291 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (279 identical lines × 2 files) packages/mermaid/src/themes/theme-redux-dark-color.js:1— packages/mermaid/src/themes/theme-redux-dark-color.js:1 · packages/mermaid/src/themes/theme-redux-dark.js:1 — these 2 files are line-for-line copies of one another — 279 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (278 matched lines × 2 locations) · ×1
Duplicated block with local edits (278 matched lines × 2 locations) packages/mermaid/src/diagrams/timeline/svgDraw.js:19— packages/mermaid/src/diagrams/timeline/svgDraw.js:19 · packages/mermaid/src/diagrams/user-journey/svgDraw.js:5 — the two spans are one implementation copied and then locally edited — 1894 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.
Wholesale file copy (247 identical lines × 3 files) packages/mermaid/src/themes/theme-neo.js:1— packages/mermaid/src/themes/theme-neo.js:1 · packages/mermaid/src/themes/theme-redux-color.js:1 · packages/mermaid/src/themes/theme-redux.js:1 — these 3 files are line-for-line copies of one another — 247 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (147 matched lines × 2 locations) · ×1
Duplicated block with local edits (147 matched lines × 2 locations) packages/mermaid/src/themes/theme-default.js:164— packages/mermaid/src/themes/theme-default.js:164 · packages/mermaid/src/themes/theme-forest.js:140 — the two spans are one implementation copied and then locally edited — 1875 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.
R10 · Code Duplication· Duplicated block with local edits (141 matched lines × 2 locations) · ×1
Duplicated block with local edits (141 matched lines × 2 locations) packages/mermaid/src/diagrams/timeline/timelineRenderer.ts:11— packages/mermaid/src/diagrams/timeline/timelineRenderer.ts:11 · packages/mermaid/src/diagrams/timeline/timelineRendererVertical.ts:11 — the two spans are one implementation copied and then locally edited — 857 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.
R10 · Code Duplication· Duplicated block with local edits (115 matched lines × 2 locations) · ×1
Duplicated block with local edits (115 matched lines × 2 locations) packages/mermaid/src/diagrams/c4/svgDraw.ts:215— packages/mermaid/src/diagrams/c4/svgDraw.ts:215 · REDACTED:1633 — the two spans are one implementation copied and then locally edited — 645 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.
Duplicated block (112 lines × 2 locations) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:841— packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:841 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:384 — 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.
Wholesale file copy (91 identical lines × 3 files) packages/mermaid/src/rendering-util/rendering-elements/shapes/icon.ts:1— packages/mermaid/src/rendering-util/rendering-elements/shapes/icon.ts:1 · packages/mermaid/src/rendering-util/rendering-elements/shapes/iconRounded.ts:1 · packages/mermaid/src/rendering-util/rendering-elements/shapes/iconSquare.ts:1 — these 3 files are line-for-line copies of one another — 91 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (76 matched lines × 2 locations) · ×1
Duplicated block with local edits (76 matched lines × 2 locations) packages/mermaid/src/diagrams/er/erDb.ts:39— packages/mermaid/src/diagrams/er/erDb.ts:39 · packages/mermaid/src/diagrams/requirement/requirementDb.ts:64 — the two spans are one implementation copied and then locally edited — 497 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.
R10 · Code Duplication· Duplicated block with local edits (71 matched lines × 2 locations) · ×1
Duplicated block with local edits (71 matched lines × 2 locations) packages/mermaid/src/rendering-util/rendering-elements/clusters.js:56— packages/mermaid/src/rendering-util/rendering-elements/clusters.js:56 · packages/mermaid/src/rendering-util/rendering-elements/clusters.js:339 — the two spans are one implementation copied and then locally edited — 592 tokens are still identical, in the same order in both spans, 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.
R10 · Code Duplication· Duplicated block with local edits (70 matched lines × 2 locations) · ×1
Duplicated block with local edits (70 matched lines × 2 locations) packages/mermaid-layout-tidy-tree/src/render.ts:11— packages/mermaid-layout-tidy-tree/src/render.ts:11 · packages/mermaid/src/rendering-util/layout-algorithms/cose-bilkent/render.ts:13 — the two spans are one implementation copied and then locally edited — 549 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.
Duplicated block (67 lines × 2 locations) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:713— packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:713 · packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:841 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (65 matched lines × 2 locations) · ×1
Duplicated block with local edits (65 matched lines × 2 locations) packages/mermaid/src/diagrams/xychart/chartBuilder/orchestrator.ts:63— packages/mermaid/src/diagrams/xychart/chartBuilder/orchestrator.ts:63 · packages/mermaid/src/diagrams/xychart/chartBuilder/orchestrator.ts:133 — the two spans are one implementation copied and then locally edited — 478 tokens are still identical, in the same order in both spans, 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.
R10 · Code Duplication· Duplicated block with local edits (58 matched lines × 2 locations) · ×1
Duplicated block with local edits (58 matched lines × 2 locations) packages/mermaid/src/rendering-util/rendering-elements/shapes/linedWaveEdgedRect.ts:25— packages/mermaid/src/rendering-util/rendering-elements/shapes/linedWaveEdgedRect.ts:25 · packages/mermaid/src/rendering-util/rendering-elements/shapes/waveEdgedRectangle.ts:28 — the two spans are one implementation copied and then locally edited — 487 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.
Duplicated block (57 lines × 2 locations) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1585— packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1585 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:1012 — 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 (57 matched lines × 2 locations) · ×1
Duplicated block with local edits (57 matched lines × 2 locations) packages/mermaid/src/diagrams/git/gitGraphAst.ts:112— packages/mermaid/src/diagrams/git/gitGraphAst.ts:112 · packages/mermaid/src/diagrams/git/gitGraphAst.ts:266 — the two spans are one implementation copied and then locally edited — 377 tokens are still identical, in the same order in both spans, 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.
Duplicated block (55 lines × 2 locations) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:291— packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:291 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:73 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (53 matched lines × 2 locations) · ×1
Duplicated block with local edits (53 matched lines × 2 locations) packages/mermaid/src/rendering-util/rendering-elements/shapes/browser.ts:10— packages/mermaid/src/rendering-util/rendering-elements/shapes/browser.ts:10 · packages/mermaid/src/rendering-util/rendering-elements/shapes/console.ts:10 — the two spans are one implementation copied and then locally edited — 449 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.
Duplicated block (53 lines × 3 locations) packages/parser/src/language/railroad-ebnf/valueConverter.ts:5— packages/parser/src/language/railroad-ebnf/valueConverter.ts:5 · packages/parser/src/language/railroad-peg/valueConverter.ts:5 · packages/parser/src/language/railroad/valueConverter.ts:5 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (52 matched lines × 2 locations) · ×1
Duplicated block with local edits (52 matched lines × 2 locations) packages/mermaid/src/rendering-util/rendering-elements/shapes/flippedTriangle.ts:10— packages/mermaid/src/rendering-util/rendering-elements/shapes/flippedTriangle.ts:10 · packages/mermaid/src/rendering-util/rendering-elements/shapes/triangle.ts:12 — the two spans are one implementation copied and then locally edited — 447 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.
Duplicated block (51 lines × 2 locations) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:762— packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:762 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:314 — 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 (51 matched lines × 2 locations) · ×1
Duplicated block with local edits (51 matched lines × 2 locations) packages/mermaid/src/diagrams/kanban/kanbanDb.ts:164— packages/mermaid/src/diagrams/kanban/kanbanDb.ts:164 · packages/mermaid/src/diagrams/mindmap/mindmapDb.ts:115 — the two spans are one implementation copied and then locally edited — 246 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.
R10 · Code Duplication· Duplicated block with local edits (49 matched lines × 2 locations) · ×1
Duplicated block with local edits (49 matched lines × 2 locations) packages/mermaid/src/diagrams/agentflow/types.ts:43— packages/mermaid/src/diagrams/agentflow/types.ts:43 · packages/mermaid/src/diagrams/flowchart/types.ts:25 — the two spans are one implementation copied and then locally edited — 230 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.
R10 · Code Duplication· Duplicated block with local edits (48 matched lines × 2 locations) · ×1
Duplicated block with local edits (48 matched lines × 2 locations) packages/mermaid/src/themes/theme-dark.js:166— packages/mermaid/src/themes/theme-dark.js:166 · packages/mermaid/src/themes/theme-neutral.js:233 — the two spans are one implementation copied and then locally edited — 547 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.
Duplicated block (47 lines × 2 locations) packages/mermaid-example-diagram/src/mermaidUtils.ts:2— packages/mermaid-example-diagram/src/mermaidUtils.ts:2 · packages/mermaid-zenuml/src/mermaidUtils.ts:3 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (45 lines × 2 locations) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:471— packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:471 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:188 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (45 matched lines × 2 locations) · ×1
Duplicated block with local edits (45 matched lines × 2 locations) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1499— packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1499 · packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1755 — the two spans are one implementation copied and then locally edited — 247 tokens are still identical, in the same order in both spans, 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.
Duplicated block (44 lines × 2 locations) packages/mermaid/src/rendering-util/rendering-elements/shapes/cylinder.ts:9— packages/mermaid/src/rendering-util/rendering-elements/shapes/cylinder.ts:9 · packages/mermaid/src/rendering-util/rendering-elements/shapes/document.ts:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (43 lines × 2 locations) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1183— packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1183 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:681 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (42 lines × 2 locations) packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1320— packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1320 · packages/mermaid/src/diagrams/flowchart/flowDb.ts:770 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Complex function updateColors (cyclomatic 289, cognitive 295) packages/mermaid/src/themes/theme-base.js:32— updateColors has cyclomatic complexity 289 and cognitive complexity 295; 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 routeEdgesOrthogonal (cyclomatic 269, cognitive 539) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts:122— routeEdgesOrthogonal has cyclomatic complexity 269 and cognitive complexity 539; 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 updateColors (cyclomatic 216, cognitive 221) packages/mermaid/src/themes/theme-redux-dark.js:76— updateColors has cyclomatic complexity 216 and cognitive complexity 221; 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 updateColors (cyclomatic 205, cognitive 210) packages/mermaid/src/themes/theme-redux.js:58— updateColors has cyclomatic complexity 205 and cognitive complexity 210; 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 updateColors (cyclomatic 203, cognitive 204) packages/mermaid/src/themes/theme-default.js:146— updateColors has cyclomatic complexity 203 and cognitive complexity 204; 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 updateColors (cyclomatic 200, cognitive 200) packages/mermaid/src/themes/theme-forest.js:113— updateColors has cyclomatic complexity 200 and cognitive complexity 200; 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 updateColors (cyclomatic 199, cognitive 201) packages/mermaid/src/themes/theme-redux-color.js:106— updateColors has cyclomatic complexity 199 and cognitive complexity 201; 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 updateColors (cyclomatic 195, cognitive 197) packages/mermaid/src/themes/theme-redux-dark-color.js:108— updateColors has cyclomatic complexity 195 and cognitive complexity 197; 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 updateColors (cyclomatic 189, cognitive 188) packages/mermaid/src/themes/theme-dark.js:115— updateColors has cyclomatic complexity 189 and cognitive complexity 188; 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 validateLayout (cyclomatic 174, cognitive 388) packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:604— validateLayout has cyclomatic complexity 174 and cognitive complexity 388; 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 updateColors (cyclomatic 173, cognitive 174) packages/mermaid/src/themes/theme-neutral.js:128— updateColors has cyclomatic complexity 173 and cognitive complexity 174; 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 drawMessage (cyclomatic 74, cognitive 90) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:461— drawMessage has cyclomatic complexity 74 and cognitive complexity 90; 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 insertEdge (cyclomatic 71, cognitive 76) packages/mermaid/src/rendering-util/rendering-elements/edges.js:624— insertEdge has cyclomatic complexity 71 and cognitive complexity 76; 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 classBox (cyclomatic 55, cognitive 57) packages/mermaid/src/rendering-util/rendering-elements/shapes/classBox.ts:14— classBox has cyclomatic complexity 55 and cognitive complexity 57; 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 layoutContainer (cyclomatic 54, cognitive 72) packages/mermaid/src/rendering-util/layout-algorithms/grid/layoutCore.ts:61— layoutContainer has cyclomatic complexity 54 and cognitive complexity 72; 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 draw (cyclomatic 54, cognitive 38) packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1043— draw has cyclomatic complexity 54 and cognitive complexity 38; 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 writeBackToLayoutData (cyclomatic 49, cognitive 118) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/helpers.ts:174— writeBackToLayoutData has cyclomatic complexity 49 and cognitive complexity 118; 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 collapseShortTerminalStub (cyclomatic 47, cognitive 101) packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/terminalStub.ts:44— collapseShortTerminalStub has cyclomatic complexity 47 and cognitive complexity 101; 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· packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts · ×1
packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts: 2798 lines of code packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:1— packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts has 2798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts · ×1
packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts: 2564 lines of code packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts:1— packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/materializedGeometry.ts has 2564 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/agentflow/agentflowDb.ts · ×1
packages/mermaid/src/diagrams/agentflow/agentflowDb.ts: 2326 lines of code packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1— packages/mermaid/src/diagrams/agentflow/agentflowDb.ts has 2326 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts · ×1
packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts: 2070 lines of code packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts:1— packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts has 2070 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts · ×1
packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts: 1982 lines of code packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1— packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts has 1982 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1954 lines of code REDACTED:1— REDACTED has 1954 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts · ×1
packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts: 1400 lines of code packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:1— packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts has 1400 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/git/gitGraphRenderer.ts · ×1
packages/mermaid/src/diagrams/git/gitGraphRenderer.ts: 1369 lines of code packages/mermaid/src/diagrams/git/gitGraphRenderer.ts:1— packages/mermaid/src/diagrams/git/gitGraphRenderer.ts has 1369 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/flowchart/flowDb.ts · ×1
packages/mermaid/src/diagrams/flowchart/flowDb.ts: 1232 lines of code packages/mermaid/src/diagrams/flowchart/flowDb.ts:1— packages/mermaid/src/diagrams/flowchart/flowDb.ts has 1232 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts · ×1
packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts: 1040 lines of code packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts:1— packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts has 1040 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/rendering-elements/edges.js · ×1
packages/mermaid/src/rendering-util/rendering-elements/edges.js: 984 lines of code packages/mermaid/src/rendering-util/rendering-elements/edges.js:1— packages/mermaid/src/rendering-util/rendering-elements/edges.js has 984 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/rendering-elements/markers.js · ×1
packages/mermaid/src/rendering-util/rendering-elements/markers.js: 973 lines of code packages/mermaid/src/rendering-util/rendering-elements/markers.js:1— packages/mermaid/src/rendering-util/rendering-elements/markers.js has 973 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts · ×1
packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts: 971 lines of code packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts:1— packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts has 971 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts · ×1
packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts: 965 lines of code packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts:1— packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts has 965 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/utils.ts · ×1
packages/mermaid/src/utils.ts: 896 lines of code packages/mermaid/src/utils.ts:1— packages/mermaid/src/utils.ts has 896 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/gantt/ganttRenderer.js · ×1
packages/mermaid/src/diagrams/gantt/ganttRenderer.js: 817 lines of code packages/mermaid/src/diagrams/gantt/ganttRenderer.js:1— packages/mermaid/src/diagrams/gantt/ganttRenderer.js has 817 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/gantt/ganttDb.js · ×1
packages/mermaid/src/diagrams/gantt/ganttDb.js: 805 lines of code packages/mermaid/src/diagrams/gantt/ganttDb.js:1— packages/mermaid/src/diagrams/gantt/ganttDb.js has 805 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/class/classDb.ts · ×1
packages/mermaid/src/diagrams/class/classDb.ts: 796 lines of code packages/mermaid/src/diagrams/class/classDb.ts:1— packages/mermaid/src/diagrams/class/classDb.ts has 796 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/rendering-elements/clusters.js · ×1
packages/mermaid/src/rendering-util/rendering-elements/clusters.js: 767 lines of code packages/mermaid/src/rendering-util/rendering-elements/clusters.js:1— packages/mermaid/src/rendering-util/rendering-elements/clusters.js has 767 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/c4/c4Db.ts · ×1
packages/mermaid/src/diagrams/c4/c4Db.ts: 755 lines of code packages/mermaid/src/diagrams/c4/c4Db.ts:1— packages/mermaid/src/diagrams/c4/c4Db.ts has 755 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js · ×1
packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js: 752 lines of code packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js:1— packages/mermaid/src/rendering-util/layout-algorithms/dagre/index.js has 752 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 717 lines of code REDACTED:1— REDACTED has 717 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/state/stateDb.ts · ×1
packages/mermaid/src/diagrams/state/stateDb.ts: 713 lines of code packages/mermaid/src/diagrams/state/stateDb.ts:1— packages/mermaid/src/diagrams/state/stateDb.ts has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts · ×1
packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts: 690 lines of code packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts:1— packages/mermaid/src/rendering-util/rendering-elements/lineJump.ts has 690 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· scripts/screenshot-sheets.ts · ×1
scripts/screenshot-sheets.ts: 690 lines of code scripts/screenshot-sheets.ts:1— scripts/screenshot-sheets.ts has 690 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/sequence/sequenceDb.ts · ×1
packages/mermaid/src/diagrams/sequence/sequenceDb.ts: 674 lines of code packages/mermaid/src/diagrams/sequence/sequenceDb.ts:1— packages/mermaid/src/diagrams/sequence/sequenceDb.ts has 674 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/usecase/parser/usecase.parser.ts · ×1
packages/mermaid/src/diagrams/usecase/parser/usecase.parser.ts: 646 lines of code packages/mermaid/src/diagrams/usecase/parser/usecase.parser.ts:1— packages/mermaid/src/diagrams/usecase/parser/usecase.parser.ts has 646 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts · ×1
packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts: 625 lines of code packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts:1— packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts has 625 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/eventmodeling/db.ts · ×1
packages/mermaid/src/diagrams/eventmodeling/db.ts: 616 lines of code packages/mermaid/src/diagrams/eventmodeling/db.ts:1— packages/mermaid/src/diagrams/eventmodeling/db.ts has 616 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/er/erRenderer.js · ×1
packages/mermaid/src/diagrams/er/erRenderer.js: 611 lines of code packages/mermaid/src/diagrams/er/erRenderer.js:1— packages/mermaid/src/diagrams/er/erRenderer.js has 611 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/architecture/architectureRenderer.ts · ×1
packages/mermaid/src/diagrams/architecture/architectureRenderer.ts: 598 lines of code packages/mermaid/src/diagrams/architecture/architectureRenderer.ts:1— packages/mermaid/src/diagrams/architecture/architectureRenderer.ts has 598 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/rendering-elements/shapes.ts · ×1
packages/mermaid/src/rendering-util/rendering-elements/shapes.ts: 593 lines of code packages/mermaid/src/rendering-util/rendering-elements/shapes.ts:1— packages/mermaid/src/rendering-util/rendering-elements/shapes.ts has 593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/c4/c4Renderer.ts · ×1
packages/mermaid/src/diagrams/c4/c4Renderer.ts: 583 lines of code packages/mermaid/src/diagrams/c4/c4Renderer.ts:1— packages/mermaid/src/diagrams/c4/c4Renderer.ts has 583 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts · ×1
packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts: 571 lines of code packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts:1— packages/mermaid/src/diagrams/quadrant-chart/quadrantBuilder.ts has 571 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid-layout-tidy-tree/src/layout.ts · ×1
packages/mermaid-layout-tidy-tree/src/layout.ts: 570 lines of code packages/mermaid-layout-tidy-tree/src/layout.ts:1— packages/mermaid-layout-tidy-tree/src/layout.ts has 570 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/timeline/svgDraw.js · ×1
packages/mermaid/src/diagrams/timeline/svgDraw.js: 566 lines of code packages/mermaid/src/diagrams/timeline/svgDraw.js:1— packages/mermaid/src/diagrams/timeline/svgDraw.js has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/railroad/railroadRenderer.ts · ×1
packages/mermaid/src/diagrams/railroad/railroadRenderer.ts: 564 lines of code packages/mermaid/src/diagrams/railroad/railroadRenderer.ts:1— packages/mermaid/src/diagrams/railroad/railroadRenderer.ts has 564 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts · ×1
packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts: 541 lines of code packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts:1— packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/scoreLayout.ts has 541 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/usecase/usecaseDb.ts · ×1
packages/mermaid/src/diagrams/usecase/usecaseDb.ts: 533 lines of code packages/mermaid/src/diagrams/usecase/usecaseDb.ts:1— packages/mermaid/src/diagrams/usecase/usecaseDb.ts has 533 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mermaid/src/diagrams/git/gitGraphAst.ts · ×1
packages/mermaid/src/diagrams/git/gitGraphAst.ts: 492 lines of code packages/mermaid/src/diagrams/git/gitGraphAst.ts:1— packages/mermaid/src/diagrams/git/gitGraphAst.ts has 492 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· The declared test suite includes a file that cannot be loaded · ×1
The declared test suite includes a file that cannot be loaded e2e/platform/bundle-test.js:2— This repository declares test tooling, and the ✓ above records that declaration — but e2e/platform/bundle-test.js and 1 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Dead file (~3 LoC) vitest.workspace.js— no import path from any entry point (886 application, 18 tooling, 383 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@fontsource/noto-sans-sc' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'path-browserify' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'start-server-and-test' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Orphaned file scripts/swimlanes-size.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/ishikawa/ishikawaRenderer.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/class/svgDraw.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/xychart/xychartRenderer.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/sankey/sankeyRenderer.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/flowchart/flowChartShapes.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/wardley/wardleyParser.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/git/gitGraphParser.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/quadrant-chart/quadrantRenderer.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/laneOrdering.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/rendering-elements/shapes/curlyBraces.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/eventmodeling/renderer.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/rendering-elements/shapes/bowTieRect.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/rendering-elements/shapes/iconRounded.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/rendering-elements/shapes/imageSquare.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/rendering-elements/shapes/iconSquare.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/rendering-elements/shapes/linedCylinder.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/rendering-elements/shapes/icon.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/er/erMarkers.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/rendering-elements/shapes/curlyBraceRight.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/common/svgDrawCommon.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/railroad/parser/ebnfParser.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/rendering-elements/shapes/curlyBraceLeft.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/diagrams/railroad/parser/pegParser.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mermaid/src/rendering-util/rendering-elements/shapes/multiRect.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate packages/mermaid/src/diagrams/gantt/ganttDb.js:173— `!allItemsProcessed && iterationCount < maxDepth` appears character-identically in 3 files — packages/mermaid/src/diagrams/gantt/ganttDb.js, packages/mermaid/src/diagrams/timeline/timelineDb.js, packages/mermaid/src/diagrams/user-journey/journeyDb.js. 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 packages/parser/src/language/railroad-abnf/valueConverter.ts:16— `(trimmedValue.startsWith('"') && trimmedValue.endsWith('"')) || (trimmedValue.startsWith("'") && trimmedValue.endsWith("'"))` appears character-identically in 4 files — packages/parser/src/language/railroad-abnf/valueConverter.ts, packages/parser/src/language/railroad-ebnf/valueConverter.ts, packages/parser/src/language/railroad-peg/valueConverter.ts, packages/parser/src/language/railroad/valueConverter.ts. 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 packages/mermaid/src/rendering-util/layout-algorithms/elk/lineHops.ts:51— `Array.isArray(edge.points) && edge.points.length >= 2` appears character-identically in 2 files — packages/mermaid/src/rendering-util/layout-algorithms/elk/lineHops.ts, packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/adjustLayout.ts. 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 packages/parser/src/language/railroad-ebnf/valueConverter.ts:11— `character === '\\' && index + 1 < content.length` appears character-identically in 3 files — packages/parser/src/language/railroad-ebnf/valueConverter.ts, packages/parser/src/language/railroad-peg/valueConverter.ts, packages/parser/src/language/railroad/valueConverter.ts. 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 packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:504— `classes !== undefined && classes !== null` appears character-identically in 2 files — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts, packages/mermaid/src/diagrams/flowchart/flowDb.ts. 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 packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1757— `current !== undefined && !seen.has(current)` appears character-identically in 2 files — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts, packages/mermaid/src/diagrams/flowchart/flowDb.ts. 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 packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:767— `e.start === edge.start && e.end === edge.end` appears character-identically in 2 files — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts, packages/mermaid/src/diagrams/flowchart/flowDb.ts. 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 packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:749— `edge.text.startsWith('"') && edge.text.endsWith('"')` appears character-identically in 2 files — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts, packages/mermaid/src/diagrams/flowchart/flowDb.ts. 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 packages/mermaid/src/diagrams/timeline/timelineRenderer.ts:334— `isWithoutSections && !conf.timeline?.disableMulticolor` appears character-identically in 2 files — packages/mermaid/src/diagrams/timeline/timelineRenderer.ts, packages/mermaid/src/diagrams/timeline/timelineRendererVertical.ts. 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 packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:971— `item.startsWith('"') && item.endsWith('"')` appears character-identically in 4 files — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts, packages/mermaid/src/diagrams/class/classDb.ts, packages/mermaid/src/diagrams/flowchart/flowDb.ts, packages/mermaid/src/diagrams/gantt/ganttDb.js. 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 packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/geometry.ts:195— `matchesHorizEndpoint && matchesVertEndpoint` appears character-identically in 2 files — packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/geometry.ts, packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/geometry.ts. 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 packages/mermaid/src/rendering-util/rendering-elements/shapes/stateEnd.ts:83— `node.width < 25 && nodeShadow && node.look !== 'handDrawn'` appears character-identically in 2 files — packages/mermaid/src/rendering-util/rendering-elements/shapes/stateEnd.ts, packages/mermaid/src/rendering-util/rendering-elements/shapes/stateStart.ts. 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 packages/mermaid/src/diagrams/kanban/styles.ts:10— `options['lineColor' + i] || options['cScaleInv' + i]` appears character-identically in 2 files — packages/mermaid/src/diagrams/kanban/styles.ts, packages/mermaid/src/diagrams/mindmap/styles.ts. 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 packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1894— `rawEdge.interpolate || this.edges.defaultInterpolate || config.flowchart?.curve` appears character-identically in 2 files — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts, packages/mermaid/src/diagrams/flowchart/flowDb.ts. 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 packages/mermaid/src/diagrams/agentflow/agentflowDb.ts:1879— `rawEdge?.stroke === 'invisible' || rawEdge?.type === 'arrow_open'` appears character-identically in 2 files — packages/mermaid/src/diagrams/agentflow/agentflowDb.ts, packages/mermaid/src/diagrams/flowchart/flowDb.ts. 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 packages/mermaid/src/diagrams/railroad/parser/abnfParser.ts:136— `result.lexerErrors.length > 0 || result.parserErrors.length > 0` appears character-identically in 5 files — packages/mermaid/src/diagrams/railroad/parser/abnfParser.ts, packages/mermaid/src/diagrams/railroad/parser/ebnfParser.ts, packages/mermaid/src/diagrams/railroad/parser/pegParser.ts, packages/mermaid/src/diagrams/railroad/parser/railroadParser.ts. 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 packages/parser/src/language/railroad-abnf/valueConverter.ts:13— `rule.name === 'TITLE' && typeof value === 'string'` appears character-identically in 4 files — packages/parser/src/language/railroad-abnf/valueConverter.ts, packages/parser/src/language/railroad-ebnf/valueConverter.ts, packages/parser/src/language/railroad-peg/valueConverter.ts, packages/parser/src/language/railroad/valueConverter.ts. 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 packages/mermaid/src/rendering-util/rendering-elements/clusters.js:648— `themeVariables.flowContainerStroke || themeVariables.secondaryBorderColor` appears character-identically in 2 files — packages/mermaid/src/rendering-util/rendering-elements/clusters.js, packages/mermaid/src/rendering-util/rendering-elements/shapes/collapsedGroup.ts. 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 packages/mermaid/src/themes/theme-base.js:76— `this. actorBorder || this.primaryBorderColor` appears character-identically in 5 files — packages/mermaid/src/themes/theme-base.js, packages/mermaid/src/themes/theme-neo-dark.js, packages/mermaid/src/themes/theme-neo.js, packages/mermaid/src/themes/theme-redux-color.js. 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 packages/mermaid/src/themes/theme-base.js:87— `this.activationBkgColor || this.secondaryColor` appears character-identically in 7 files — packages/mermaid/src/themes/theme-base.js, packages/mermaid/src/themes/theme-neo-dark.js, packages/mermaid/src/themes/theme-neo.js, packages/mermaid/src/themes/theme-redux-color.js. 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 packages/mermaid/src/themes/theme-base.js:86— `this.activationBorderColor || darken(this.secondaryColor, 10)` appears character-identically in 7 files — packages/mermaid/src/themes/theme-base.js, packages/mermaid/src/themes/theme-neo-dark.js, packages/mermaid/src/themes/theme-neo.js, packages/mermaid/src/themes/theme-redux-color.js. 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 packages/mermaid/src/themes/theme-neo.js:131— `this.activeTaskBkgColor || lighten(primaryColor, 23)` appears character-identically in 3 files — packages/mermaid/src/themes/theme-neo.js, packages/mermaid/src/themes/theme-redux-color.js, packages/mermaid/src/themes/theme-redux.js. 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 packages/mermaid/src/themes/theme-base.js:103— `this.activeTaskBkgColor || lighten(this.primaryColor, 23)` appears character-identically in 4 files — packages/mermaid/src/themes/theme-base.js, packages/mermaid/src/themes/theme-neo-dark.js, packages/mermaid/src/themes/theme-redux-dark-color.js, packages/mermaid/src/themes/theme-redux-dark.js. 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 packages/mermaid/src/themes/theme-neo.js:130— `this.activeTaskBorderColor || primaryColor` appears character-identically in 3 files — packages/mermaid/src/themes/theme-neo.js, packages/mermaid/src/themes/theme-redux-color.js, packages/mermaid/src/themes/theme-redux.js. 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 packages/mermaid/src/themes/theme-base.js:102— `this.activeTaskBorderColor || this.primaryColor` appears character-identically in 4 files — packages/mermaid/src/themes/theme-base.js, packages/mermaid/src/themes/theme-neo-dark.js, packages/mermaid/src/themes/theme-redux-dark-color.js, packages/mermaid/src/themes/theme-redux-dark.js. 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.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×23
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/rendering-util/rendering-elements/clusters.js:74— `trace` at line 74 is called with an argument built by `JSON.stringify(node)` (line 74), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/rendering-util/rendering-elements/clusters.js:357— `trace` at line 357 is called with an argument built by `JSON.stringify(node)` (line 357), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/rendering-util/rendering-elements/edges.js:414— `debug` at line 414 is called with an argument built by `JSON.stringify(outsidePoint)` (line 415), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/rendering-util/rendering-elements/edges.js:714— `debug` at line 714 is called with an argument built by `JSON.stringify(points, null, 2)` (line 717), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/rendering-util/rendering-elements/clusters/swimlane.js:226— `trace` at line 226 is called with an argument built by `JSON.stringify(node)` (line 226), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:1496— `debug` at line 1496 is called with an argument built by `JSON.stringify(issues.slice(0, 50))` (line 1502), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:2491— `debug` at line 2491 is called with an argument built by `JSON.stringify(points)` (line 2493), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts:2556— `debug` at line 2556 is called with an argument built by `JSON.stringify(clippedPoints)` (line 2556), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:269— `debug` at line 269 is called with an argument built by `JSON.stringify(e)` (line 269), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/rendering-util/layout-algorithms/dagre/mermaid-graphlib.js:270— `debug` at line 270 is called with an argument built by `JSON.stringify(graph.edge(e))` (line 270), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/state/stateRenderer.js:265— `debug` at line 265 is called with an argument built by `JSON.stringify(graph.node(v))` (line 265), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/state/stateRenderer.js:273— `debug` at line 273 is called with an argument built by `JSON.stringify(graph.edge(e))` (line 273), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/sequence/sequenceDb.ts:387— `debug` at line 387 is called with an argument built by `JSON.stringify(message)` (line 387), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/git/gitGraphAst.ts:427— `debug` at line 427 is called with an argument built by `label.join(' ')` (line 427), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/class/classDb.ts:210— `debug` at line 210 is called with an argument built by `JSON.stringify(classRelation)` (line 210), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/class/classRenderer.js:211— `debug` at line 211 is called with an argument built by `JSON.stringify(note)` (line 211), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/class/classRenderer.js:242— `debug` at line 242 is called with an argument built by `JSON.stringify(g.node(v))` (line 242), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/class/classRenderer.js:258— `debug` at line 258 is called with an argument built by `JSON.stringify(g.edge(e))` (line 258), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/class/svgDraw.js:89— `debug` at line 89 is called with an argument built by `JSON.stringify(cardinality_1_point)` (line 89), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/class/svgDraw.js:90— `debug` at line 90 is called with an argument built by `JSON.stringify(cardinality_2_point)` (line 90), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/c4/c4Renderer.ts:578— `debug` at line 578 is called with an argument built by `JSON.stringify(conf, null, 2)` (line 578), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/block/layout.ts:112— `debug` at line 112 is called with an argument built by `JSON.stringify(child.size)` (line 113), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/mermaid/src/diagrams/block/layout.ts:362— `debug` at line 362 is called with an argument built by `JSON.stringify(root, null, 2)` (line 362), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
P2 · Observability· Console output used as the logging channel · ×22
Console output used as the logging channel packages/mermaid/src/assignWithDepth.ts:17— `packages/mermaid/src/assignWithDepth.ts` reports through `console.*` at line 17 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/mermaid.ts:337— `packages/mermaid/src/mermaid.ts` reports through `console.*` at line 337 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/mermaid.ts:339— `packages/mermaid/src/mermaid.ts` reports through `console.*` at line 339 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/mermaid.ts:341— `packages/mermaid/src/mermaid.ts` reports through `console.*` at line 341 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/mermaid.ts:343— `packages/mermaid/src/mermaid.ts` reports through `console.*` at line 343 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/profiler.ts:304— `packages/mermaid/src/profiler.ts` reports through `console.*` at line 304 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/utils/imperativeState.ts:12— `packages/mermaid/src/utils/imperativeState.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/utils/imperativeState.ts:14— `packages/mermaid/src/utils/imperativeState.ts` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/rendering-util/render.ts:9— `packages/mermaid/src/rendering-util/render.ts` reports through `console.*` at line 9 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/rendering-util/rendering-elements/shapes/drawRect.ts:18— `packages/mermaid/src/rendering-util/rendering-elements/shapes/drawRect.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/rendering-util/layout-algorithms/ddlt/discoverFixtures.ts:100— `packages/mermaid/src/rendering-util/layout-algorithms/ddlt/discoverFixtures.ts` reports through `console.*` at line 100 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/diagrams/state/stateRenderer-v3-unified.ts:75— `packages/mermaid/src/diagrams/state/stateRenderer-v3-unified.ts` reports through `console.*` at line 75 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/diagrams/state/shapes.js:180— `packages/mermaid/src/diagrams/state/shapes.js` reports through `console.*` at line 180 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/diagrams/kanban/kanbanDb.ts:27— `packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 27 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/diagrams/kanban/kanbanDb.ts:35— `packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/diagrams/kanban/kanbanDb.ts:37— `packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/diagrams/kanban/kanbanDb.ts:121— `packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 121 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/diagrams/kanban/kanbanDb.ts:123— `packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 123 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/diagrams/kanban/kanbanDb.ts:126— `packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 126 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid/src/diagrams/kanban/kanbanDb.ts:130— `packages/mermaid/src/diagrams/kanban/kanbanDb.ts` reports through `console.*` at line 130 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid-example-diagram/src/mermaidUtils.ts:5— `packages/mermaid-example-diagram/src/mermaidUtils.ts` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mermaid-zenuml/src/mermaidUtils.ts:6— `packages/mermaid-zenuml/src/mermaidUtils.ts` reports through `console.*` at line 6 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Disabled test e2e/other/pr-check/configuration.spec.js:55— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/other/pr-check/dev-explorer-compare.spec.ts:11— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/scripts/docs.spec.ts:166— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/diagrams/class/classDiagram.spec.ts:293— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/diagrams/er/parser/erDiagram.spec.js:124— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/diagrams/flowchart/parser/flow-huge.spec.js:17— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/diagrams/flowchart/parser/flow-node-data.spec.js:403— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/diagrams/flowchart/parser/subgraph.spec.js:64— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/diagrams/git/gitGraph.spec.ts:92— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/diagrams/git/gitGraph.spec.ts:111— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/diagrams/git/gitGraph.spec.ts:131— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/diagrams/git/gitGraph.spec.ts:191— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/diagrams/state/stateDiagram.spec.js:384— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/rendering-util/handle-markdown-text.spec.ts:207— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/__tests__/postProcessing.spec.ts:83— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/__tests__/raykov.router.spec.ts:434— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Deprecated: @types/flexsearch REDACTED:4052— @types/flexsearch 0.7.42 is resolved in REDACTED and is marked deprecated by its publisher: "This is a stub types definition. flexsearch provides its own type definitions, so you do not need this installed.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @ungap/structured-clone REDACTED:4279— @ungap/structured-clone 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @xmldom/xmldom REDACTED:4745— @xmldom/xmldom 0.8.13 is resolved in REDACTED and is marked deprecated by its publisher: "this version has critical issues, please update to the latest version". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:6826— glob 10.4.5 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:6831— glob 11.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:6837— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:6841— glob 8.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:7091— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: nomnom REDACTED:8368— nomnom 1.5.2 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact support@npmjs.com for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: prebuild-install REDACTED:8831— prebuild-install 7.1.3 is resolved in REDACTED and is marked deprecated by its publisher: "No longer maintained. Please contact the author of the relevant native addon; alternatives are available.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:9162— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: sourcemap-codec REDACTED:9501— sourcemap-codec 1.4.8 is resolved in REDACTED and is marked deprecated by its publisher: "Please use @jridgewell/sourcemap-codec instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: uuid REDACTED:10232— uuid 8.3.2 is resolved in REDACTED and is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: whatwg-encoding REDACTED:10551— whatwg-encoding 3.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @exodus/bytes instead for a more spec-conformant and faster implementation". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 22 significant file(s) lose their only recent owner: packages/mermaid/src/diagrams/agentflow/agentflowDb.ts, packages/mermaid/src/diagrams/usecase/parser/usecaseModelBuilder.ts, packages/mermaid/src/diagrams/usecase/parser/usecase.visitor.ts, packages/mermaid/src/diagrams/usecase/parser/usecase.parser.ts, packages/mermaid/src/rendering-util/layout-algorithms/elk/elkOptionCatalogue.ts, packages/mermaid/src/diagrams/usecase/styles.ts, packages/mermaid/src/diagrams/agentflow/conformance/runner.ts, packages/mermaid/src/diagrams/usecase/parser/usecase.tokens.ts (+14 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 9 significant file(s) lose their only recent owner: packages/mermaid/src/diagrams/c4/c4Db.ts, packages/mermaid/src/diagrams/c4/c4ShapeAdapter.ts, packages/mermaid/src/rendering-util/layout-algorithms/elk/subgraphFeedbackEdges.ts, packages/mermaid/src/rendering-util/rendering-elements/shapes/person.ts, packages/mermaid/src/diagrams/c4/c4Types.ts, packages/mermaid/src/rendering-util/rendering-elements/shapes/bucket.ts, packages/mermaid/src/rendering-util/rendering-elements/shapes/browser.ts, packages/mermaid/src/rendering-util/rendering-elements/shapes/folder.ts (+1 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 8 significant file(s) lose their only recent owner: packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/orthogonalRouter/router.ts, packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts, packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/labelAnchoring.ts, packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/direction/sharedTrackNudging.ts, packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase4.coordinates.ts, packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/edgeLabelNodes.ts, packages/mermaid/src/rendering-util/layout-algorithms/ddlt/sizeCapture.ts, packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/phase2.gravity.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 5 significant file(s) lose their only recent owner: packages/mermaid/src/diagrams/railroad/railroadRenderer.ts, packages/mermaid/src/diagrams/railroad/styles.ts, packages/mermaid/src/diagrams/railroad/railroadTypes.ts, packages/mermaid/src/diagrams/railroad/railroadDb.ts, packages/mermaid/src/diagrams/railroad/parser/railroadParser.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 3 significant file(s) lose their only recent owner: packages/mermaid/src/diagrams/ishikawa/ishikawaRenderer.ts, packages/mermaid/src/diagrams/timeline/timelineRendererVertical.ts, packages/mermaid/src/diagrams/venn/vennDB.ts. Pair on, review, or document these before any departure.
Blanket warning suppression packages/mermaid/src/diagrams/quadrant-chart/quadrantRenderer.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/mermaid/src/diagrams/sequence/sequenceRenderer.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/mermaid/src/diagrams/timeline/timelineRenderer.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/mermaid/src/diagrams/user-journey/journeyRenderer.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Fat interface: GitGraphDB (17 required operations) packages/mermaid/src/diagrams/git/gitGraphTypes.ts:90— `GitGraphDB` declares 17 required operations: `setDirection`, `setOptions`, `getOptions`, `commit`, `branch`, `merge`, `cherryPick`, `checkout`, `prettyPrint`, `clear`, `getBranchesAsObjArray`, `getBranches`, `getCommits`, `getCommitsArray`, `getCurrentBranch`, `getDirection`, `getHead`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: ArchitectureDB (16 required operations) packages/mermaid/src/diagrams/architecture/architectureTypes.ts:252— `ArchitectureDB` declares 16 required operations: `clear`, `addService`, `getServices`, `addJunction`, `getJunctions`, `getNodes`, `getNode`, `addGroup`, `getGroups`, `addEdge`, `getEdges`, `addLayoutHint`, `getLayoutHints`, `setElementForId`, `getElementById`, `getDataStructures`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: UsecaseDB (20 required operations) packages/mermaid/src/diagrams/usecase/usecaseTypes.ts:304— `UsecaseDB` declares 20 required operations: `getConfig`, `createModel`, `commit`, `getAST`, `getActors`, `getActor`, `getUseCases`, `getUseCase`, `getSystemBoundaries`, `getSystemBoundary`, `getRelationships`, `getNotes`, `getNote`, `getJsonNodes`, `getJsonNode`, `getClassDefs`, `getClassDef`, `getDirection`, `getData`, `clear`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Mock-dominated test: calls setDiagramId with the svg element id packages/mermaid/src/diagrams/flowchart/flowRenderer-v3-unified.spec.ts:27— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: calls setDiagramId with the svg element id packages/mermaid/src/diagrams/agentflow/renderer.spec.ts:27— This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 11 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (64 single-owned of 311 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 311 of the 628 production source files in this repository met that bar). They are anonymized user #6 (2 file(s)), anonymized user #7 (2 file(s)), anonymized user #8 (2 file(s)), anonymized user #9 (2 file(s)), anonymized user #10 (2 file(s)), anonymized user #11 (1 file(s)) (+5 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/mermaid/src/diagrams/wardley/wardleyParser.ts, packages/mermaid/src/diagrams/wardley/wardleyBuilder.ts, packages/mermaid/src/diagrams/eventmodeling/renderer.ts, packages/mermaid/src/diagrams/eventmodeling/types.ts, REDACTED, packages/mermaid-local-editor/static/js/ui.js, packages/mermaid/src/diagrams/radar/db.ts, packages/mermaid/src/rendering-util/layout-algorithms/elk/lineHops.ts (+8 more).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 7 project(s) overshoot their size bounds, lowering Project Cohesion to 7.1/10. The most over is `packages/mermaid` (95154 LoC, 915 module-visible types across 67 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 45 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: scripts/swimlanes-size.ts, packages/mermaid/src/diagrams/ishikawa/ishikawaRenderer.ts, packages/mermaid/src/diagrams/class/svgDraw.js, packages/mermaid/src/diagrams/xychart/xychartRenderer.ts, packages/mermaid/src/diagrams/sankey/sankeyRenderer.ts, packages/mermaid/src/diagrams/flowchart/flowChartShapes.js, packages/mermaid/src/diagrams/wardley/wardleyParser.ts, packages/mermaid/src/diagrams/git/gitGraphParser.ts (and 37 more) (48 orphaned of 311 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 311 of the 628 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Unused export 'default' packages/mermaid-layout-tidy-tree/src/layouts.ts:13— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/mermaid-layout-tidy-tree/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/mermaid-layout-tidy-tree/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'TidyTreeLayoutConfig' · ×1
Unused export 'TidyTreeLayoutConfig' packages/mermaid-layout-tidy-tree/src/types.ts:67— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/mermaid-layout-tidy-tree/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/mermaid-layout-tidy-tree/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'CommonTokenBuilder' · ×1
Unused export 'CommonTokenBuilder' packages/parser/src/language/common/tokenBuilder.ts:31— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/parser/src/language/common/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/parser/src/language/common/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused module-local declaration 'code2' · ×1
Unused module-local declaration 'code2' e2e/platform/bundle-test.js:10— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused private method 'escapeHtml' · ×1
Unused private method 'escapeHtml' packages/mermaid/src/diagrams/class/classDb.ts:514— Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used.
R7 · Dead Code· Unused module-local declaration '_updateNodeDimensions' · ×1
Unused module-local declaration '_updateNodeDimensions' packages/mermaid/src/diagrams/mindmap/mindmapRenderer.ts:15— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'addConf' · ×1
Unused module-local declaration 'addConf' packages/mermaid/src/diagrams/sequence/sequenceDiagram.spec.js:88— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused private field 'chartThemeConfig' · ×1
Unused private field 'chartThemeConfig' packages/mermaid/src/diagrams/xychart/chartBuilder/components/plot/index.ts:27— Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code· Unused module-local declaration '_segmentLength' · ×1
Unused module-local declaration '_segmentLength' packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:313— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration '_polylineIsOrthogonal' · ×1
Unused module-local declaration '_polylineIsOrthogonal' packages/mermaid/src/rendering-util/layout-algorithms/layout-utils/validateLayout.ts:515— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'TestEdge' · ×1
Unused module-local declaration 'TestEdge' packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/__tests__/phase0.helpers.spec.ts:15— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'hasEarlyReturnToStartRow' · ×1
Unused module-local declaration 'hasEarlyReturnToStartRow' packages/mermaid/src/rendering-util/layout-algorithms/swimlanes/__tests__/pipeline.hoe.lr.spec.ts:187— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
No security response headers detected netlify.toml:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
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/3 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 9/13 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) reduce the strict null checking score — ~4.3 `!` null assertions per 1k TypeScript source lines — 391 assertion(s) across the 91890 source line(s) of the 567 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/mermaid/src/diagrams/wardley/wardleyRenderer.ts (66), packages/mermaid/src/rendering-util/layout-algorithms/elk/render.ts (55), packages/mermaid/src/diagrams/c4/c4Renderer.ts (23). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Outdated (npm): @iconify/utils — @iconify/utils is pinned at 3.0.2; registry.npmjs.org publishes 3.1.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @plausible-analytics/tracker — @plausible-analytics/tracker is pinned at 0.4.5; registry.npmjs.org publishes 0.4.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @vueuse/core — @vueuse/core is pinned at 13.9.0; registry.npmjs.org publishes 15.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @zenuml/core — @zenuml/core is pinned at 3.49.2; registry.npmjs.org publishes 4.11.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): cytoscape — cytoscape is pinned at 3.34.0; registry.npmjs.org publishes 3.34.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): dayjs — dayjs is pinned at 1.11.21; registry.npmjs.org publishes 1.11.23 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): dompurify — dompurify is pinned at 3.4.12; registry.npmjs.org publishes 3.4.17 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): elkjs — elkjs is pinned at 0.9.3; registry.npmjs.org publishes 0.12.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): es-toolkit — es-toolkit is pinned at 1.45.1; registry.npmjs.org publishes 1.53.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): jiti — jiti is pinned at 2.5.1; registry.npmjs.org publishes 2.7.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): katex — katex is pinned at 0.18.11; registry.npmjs.org publishes 0.19.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): marked — marked is pinned at 16.3.0; registry.npmjs.org publishes 18.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): stylis — stylis is pinned at 4.3.6; registry.npmjs.org publishes 4.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): ts-dedent — ts-dedent is pinned at 2.2.0; registry.npmjs.org publishes 2.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): uuid — uuid is pinned at 14.0.0; registry.npmjs.org publishes 14.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): vue — vue is pinned at 3.5.40; registry.npmjs.org publishes 3.5.44 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Skipped (documented): setConfig packages/mermaid/src/diagrams/pie/pie.spec.ts:180— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): resetConfig packages/mermaid/src/diagrams/pie/pie.spec.ts:192— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 9 file(s) — `.build/common.ts`, `packages/mermaid/src/diagrams/git/gitGraphAst.ts`, `packages/mermaid/src/diagrams/kanban/kanbanDb.ts`, `packages/mermaid/src/diagrams/state/stateDb.ts`, `packages/mermaid/src/docs/.vitepress/config.ts`, … (+4 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a17801-11ad-7042-98aa-95cd2d710c80 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 94 · Warnings: 1091 · Recommendations: 186 · Info: 18 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 11:38 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.