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

ueberdosis/tiptap

Measured 14 November 2026, 12:04 UTC, at code version 9357496

CAI score 58out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey

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

A large codebase: 109,245 lines of product code in 63 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Production Readiness, 50

Findings by how serious they are

38 critical 363 serious 226 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 12:04 UTC

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

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

64of 64 dimensions measured by tools.
559of 627 findings point to an exact file and line, so you can open each one in the code. The other 68 concern the repository as a whole, such as missing documentation.
64dimensions across 6 lenses, read from 109,245 lines of product code in 63 projects.
Chapters

Executive summary

ueberdosis/tiptap falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 58 out of 100 and is rated Adequate, and 35 of its 38 critical findings are security problems.

Production Readiness, at 50, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the two deprecated dependencies, worth about 3 points. Tidying the declared packages would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 64.

Twenty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Nine secrets can leak from the build pipeline, and three automatic updates take new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. Fixing the weaknesses the scanner points to would fix the two security weaknesses in the code. The two loops of files that import each other need breaking.

The product code is 109,245 lines, about €160,000 to rebuild.

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

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

If Production Readiness rose from 50 to 70, the lowest score rated Strong, the score would rise from 58 to about 64.

Code composition: what the lines of code are
Product code 70%Tests 30%
New since the last survey: 81 findings

These 81 critical or serious findings weren't in the previous survey, on 26 October 2026.

  • Cyclomatic Complexity · splitListItem.splitListItem.<returned closure> (cyclomatic 37) packages/core/src/commands/splitListItem.ts
  • Cyclomatic Complexity · toggleList.toggleList.<returned closure> (cyclomatic 37) packages/core/src/commands/toggleList.ts
  • Cyclomatic Complexity · insertContentAt.insertContentAt.<returned closure> (cyclomatic 35) packages/core/src/commands/insertContentAt.ts
  • Cyclomatic Complexity · splitBlock.splitBlock.<returned closure> (cyclomatic 29) packages/core/src/commands/splitBlock.ts
  • Cyclomatic Complexity · updateAttributes.updateAttributes.<returned closure> (cyclomatic 27) packages/core/src/commands/updateAttributes.ts
  • Cyclomatic Complexity · focus.focus.<returned closure> (cyclomatic 21) packages/core/src/commands/focus.ts
  • Cyclomatic Complexity · PasteRule.pasteRulesPlugin.plugins (cyclomatic 18) packages/core/src/PasteRule.ts
  • Cognitive Complexity · toggleList.toggleList.<returned closure> (cognitive 63) packages/core/src/commands/toggleList.ts
  • Cognitive Complexity · splitListItem.splitListItem.<returned closure> (cognitive 56) packages/core/src/commands/splitListItem.ts
  • Cognitive Complexity · updateAttributes.updateAttributes.<returned closure> (cognitive 47) packages/core/src/commands/updateAttributes.ts
  • Cognitive Complexity · insertContentAt.insertContentAt.<returned closure> (cognitive 46) packages/core/src/commands/insertContentAt.ts
  • Cognitive Complexity · splitBlock.splitBlock.<returned closure> (cognitive 36) packages/core/src/commands/splitBlock.ts
  • Cognitive Complexity · focus.focus.<returned closure> (cognitive 21) packages/core/src/commands/focus.ts
  • Cognitive Complexity · PasteRule.pasteRulesPlugin.plugins (cognitive 21) packages/core/src/PasteRule.ts
  • Cognitive Complexity · clearNodes.clearNodes.<returned closure> (cognitive 19) packages/core/src/commands/clearNodes.ts
  • Cognitive Complexity · undoInputRule.undoInputRule.<returned closure> (cognitive 16) packages/core/src/commands/undoInputRule.ts
  • God Classes · FunctionTooLong: yCursorPlugin.yCursorPlugin packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts
  • Churn × Complexity Hotspots · Hotspot: packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts
  • Churn × Complexity Hotspots · Hotspot: packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts
  • Churn × Complexity Hotspots · Hotspot: packages/y-tiptap/src/lib/plugins/ySyncPlugin.ts packages/y-tiptap/src/lib/plugins/ySyncPlugin.ts
  • Churn × Complexity Hotspots · Hotspot: packages/y-tiptap/src/lib/utils/conversion/createNodeFromYElement.ts packages/y-tiptap/src/lib/utils/conversion/createNodeFromYElement.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/y-tiptap/src/lib/plugins/yUndoPlugin.ts packages/y-tiptap/src/lib/plugins/yUndoPlugin.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/static-renderer/src/pm/html-string/html-string.ts packages/static-renderer/src/pm/html-string/html-string.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/core/src/InputRule.ts packages/core/src/InputRule.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/extension-collaboration/src/collaboration.ts packages/extension-collaboration/src/collaboration.ts
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Code Duplication · Duplicated block with local edits (80 matched lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu-plugin.ts
  • Cyclomatic Complexity · Complex function parseIndentedBlocks (cyclomatic 17, cognitive 40) packages/core/src/utilities/markdown/parseIndentedBlocks.ts
  • Cyclomatic Complexity · Complex function updateYFragment (cyclomatic 17, cognitive 28) packages/y-tiptap/src/lib/utils/reconciliation/updateYFragment.ts
  • Cyclomatic Complexity · Complex function handleKeyDown (cyclomatic 17, cognitive 19) packages/extension-emoji/src/emoji.ts
  • Cyclomatic Complexity · Complex function handler (cyclomatic 17, cognitive 17) packages/core/src/inputRules/wrappingInputRule.ts
  • Cyclomatic Complexity · Complex function MenuBar (cyclomatic 17, cognitive 16) demos/src/Examples/Book/React/index.jsx
  • Cyclomatic Complexity · Complex function MenuBar (cyclomatic 17, cognitive 16) demos/src/Examples/CSSModules/React/index.jsx
  • Cyclomatic Complexity · Complex function MenuBar (cyclomatic 17, cognitive 16) demos/src/Examples/StaticRendering/React/index.tsx
  • Cyclomatic Complexity · Complex function domOutputSpecToReactElement (cyclomatic 16, cognitive 37) packages/static-renderer/src/pm/react/react.ts
  • Cyclomatic Complexity · Complex function updateColumns (cyclomatic 16, cognitive 36) packages/extension-table/src/table/TableView.ts
  • Cyclomatic Complexity · Complex function replacePackageSpecifiers (cyclomatic 16, cognitive 27) codemods/tiptap-v4-migration/scripts/vue-sfc-imports.mjs
  • Cyclomatic Complexity · Complex function parseMarkdown (cyclomatic 16, cognitive 26) packages/extension-list/src/item/list-item.ts
  • Cyclomatic Complexity · Complex function middlewares (cyclomatic 16, cognitive 22) packages/extension-bubble-menu/src/bubble-menu-plugin.ts
  • Cyclomatic Complexity · Complex function middlewares (cyclomatic 16, cognitive 22) packages/extension-floating-menu/src/floating-menu-plugin.ts
  • Cyclomatic Complexity · Complex function menuBarStateSelector (cyclomatic 16, cognitive 15) demos/src/Examples/Book/React/index.jsx
  • Cyclomatic Complexity · Complex function menuBarStateSelector (cyclomatic 16, cognitive 15) demos/src/Examples/CSSModules/React/index.jsx
  • Cyclomatic Complexity · Complex function ignoreMutation (cyclomatic 16, cognitive 15) packages/core/src/NodeView.ts
  • Cyclomatic Complexity · Complex function findSuggestionMatch (cyclomatic 16, cognitive 14) REDACTED
  • Cyclomatic Complexity · Complex function _isDomSelectionInView (cyclomatic 16, cognitive 13) packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts
  • Cyclomatic Complexity · Complex function handleMobileEnter (cyclomatic 16, cognitive 12) packages/react/src/handleMobileEnter.ts
  • Cyclomatic Complexity · Complex function domOutputSpecToHTMLString (cyclomatic 15, cognitive 35) packages/static-renderer/src/pm/html-string/html-string.ts
  • Large Files · packages/extension-bubble-menu/src/bubble-menu-plugin.ts: 602 lines of code packages/extension-bubble-menu/src/bubble-menu-plugin.ts
  • Large Files · packages/extension-floating-menu/src/floating-menu-plugin.ts: 499 lines of code packages/extension-floating-menu/src/floating-menu-plugin.ts
  • Dependency Hygiene · Unused dependency 'pkg-pr-new'
  • Dependency Hygiene · Unused dependency 'tinyglobby'
  • Dependency Hygiene · Unused dependency 'tsconfig-paths'
  • Dependency Hygiene · Unused dependency '@lifeomic/attempt'
  • Dependency Hygiene · Unused dependency '@shikijs/core'
  • Dependency Hygiene · Unused dependency 'linkifyjs'
  • Dependency Hygiene · Unused dependency 'prosemirror-changeset'
  • Dependency Hygiene · Unused dependency 'prosemirror-collab'
  • Dependency Hygiene · Unused dependency 'prosemirror-commands'
  • Dependency Hygiene · Unused dependency 'prosemirror-dropcursor'
  • Dependency Hygiene · Unused dependency 'prosemirror-gapcursor'
  • Dependency Hygiene · Unused dependency 'prosemirror-history'
  • Dependency Hygiene · Unused dependency 'prosemirror-inputrules'
  • Dependency Hygiene · Unused dependency 'prosemirror-keymap'
  • Dependency Hygiene · Unused dependency 'prosemirror-markdown'
  • Dependency Hygiene · Unused dependency 'prosemirror-menu'
  • Dependency Hygiene · Unused dependency 'prosemirror-schema-basic'
  • Dependency Hygiene · Unused dependency 'prosemirror-schema-list'
  • Dependency Hygiene · Unused dependency 'prosemirror-tables'
  • Dependency Hygiene · Unused dependency 'prosemirror-trailing-node'
  • Dependency Hygiene · Unused dependency 'prosemirror-transform'
  • Dependency Hygiene · Unused dependency 'sass-embedded'
  • Dependency Hygiene · Unused dependency '@tiptap/extension-bullet-list'
  • Dependency Hygiene · Unused dependency '@tiptap/extension-ordered-list'
  • Exception handling · Swallowed exception (empty catch) packages/react/src/ReactRenderer.tsx
  • Exception handling · Swallowed exception (empty catch) packages/react/src/ReactRenderer.tsx
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) packages/core/src/NodeView.ts
  • Exception handling · Swallowed exception (empty catch) packages/core/src/NodeView.ts

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 495 findings

These 495 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one. The first 100 are listed here.

  • Cyclomatic Complexity · splitListItem.splitListItem (cyclomatic 37) packages/core/src/commands/splitListItem.ts
  • Cyclomatic Complexity · toggleList.toggleList (cyclomatic 37) packages/core/src/commands/toggleList.ts
  • Cyclomatic Complexity · insertContentAt.insertContentAt (cyclomatic 35) packages/core/src/commands/insertContentAt.ts
  • Cyclomatic Complexity · splitBlock.splitBlock (cyclomatic 29) packages/core/src/commands/splitBlock.ts
  • Cyclomatic Complexity · updateAttributes.updateAttributes (cyclomatic 27) packages/core/src/commands/updateAttributes.ts
  • Cyclomatic Complexity · PasteRule.pasteRulesPlugin (cyclomatic 27) packages/core/src/PasteRule.ts
  • Cyclomatic Complexity · focus.focus (cyclomatic 21) packages/core/src/commands/focus.ts
  • Cyclomatic Complexity · restorePositionHistory.restoreTransfers (cyclomatic 19) packages/y-tiptap/src/lib/utils/positions/migrations/restorePositionHistory.ts
  • Cyclomatic Complexity · restoreRelativeSelection.restoreRelativeSelection (cyclomatic 16) packages/y-tiptap/src/lib/utils/positions/restoreRelativeSelection.ts
  • Cyclomatic Complexity · yCursorPlugin.createDecorations (cyclomatic 16) packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts
  • Cognitive Complexity · toggleList.toggleList (cognitive 63) packages/core/src/commands/toggleList.ts
  • Cognitive Complexity · splitListItem.splitListItem (cognitive 56) packages/core/src/commands/splitListItem.ts
  • Cognitive Complexity · updateAttributes.updateAttributes (cognitive 47) packages/core/src/commands/updateAttributes.ts
  • Cognitive Complexity · insertContentAt.insertContentAt (cognitive 46) packages/core/src/commands/insertContentAt.ts
  • Cognitive Complexity · splitBlock.splitBlock (cognitive 36) packages/core/src/commands/splitBlock.ts
  • Cognitive Complexity · PasteRule.pasteRulesPlugin (cognitive 27) packages/core/src/PasteRule.ts
  • Cognitive Complexity · focus.focus (cognitive 21) packages/core/src/commands/focus.ts
  • Cognitive Complexity · restorePositionHistory.restoreTransfers (cognitive 21) packages/y-tiptap/src/lib/utils/positions/migrations/restorePositionHistory.ts
  • Cognitive Complexity · undoInputRule.undoInputRule (cognitive 16) packages/core/src/commands/undoInputRule.ts
  • Churn × Complexity Hotspots · Hotspot: packages/static-renderer/src/pm/html-string/html-string.ts packages/static-renderer/src/pm/html-string/html-string.ts
  • Churn × Complexity Hotspots · Hotspot: packages/core/src/commands/insertContentAt.ts packages/core/src/commands/insertContentAt.ts
  • Churn × Complexity Hotspots · Hotspot: packages/core/src/helpers/createNodeFromContent.ts packages/core/src/helpers/createNodeFromContent.ts
  • Churn × Complexity Hotspots · Hotspot: packages/static-renderer/src/pm/markdown/markdown.ts packages/static-renderer/src/pm/markdown/markdown.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/react/src/ReactNodeViewRenderer.tsx packages/react/src/ReactNodeViewRenderer.tsx
  • Churn × Complexity Hotspots · Repeated repair: packages/extension-list/src/task-item/task-item.ts packages/extension-list/src/task-item/task-item.ts
  • Boundary Type-Coupling · Cross-context type ResizableNodeViewDirection (core → extension-image) packages/extension-image/src/image.ts
  • Boundary Type-Coupling · Cross-context type Content (core → markdown) packages/markdown/src/utils.ts
  • Secrets (history) · High secret: WD-SECRET-0005 package-lock.json
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Code Duplication · Duplicated block with local edits (75 matched lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu-plugin.ts
  • Code Duplication · Duplicated block (18 lines × 5 locations) packages/extension-list/vite.config.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu-plugin.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/extension-twitch/src/utils.ts
  • Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) packages/core/src/PasteRule.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu-plugin.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/extension-list/src/bullet-list/bullet-list.ts
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) packages/extension-details/src/content/details-content.ts
  • Code Duplication · Duplicated block (15 lines × 4 locations) packages/extension-find-and-replace/src/find-and-replace.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/extension-list/src/bullet-list/bullet-list.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/static-renderer/src/json/renderer.ts
  • Code Duplication · Duplicated block (14 lines × 8 locations) packages/core/src/helpers/isProseMirrorAddMarkStep.ts
  • Code Duplication · Duplicated block (14 lines × 3 locations) packages/core/src/inputRules/markInputRule.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/extension-node-range/src/node-range.ts
  • Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/core/src/Editor.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/core/src/commands/lift.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/core/src/commands/liftListItem.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/core/src/commands/wrapIn.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu-plugin.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/extension-collaboration/src/collaboration.ts
  • Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/extension-drag-handle/src/helpers/findBestDragTarget.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/core/src/commands/toggleList.ts
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/core/src/helpers/findChildren.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/extension-code-block/src/code-block.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/extension-emoji/src/emoji.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/extension-list/src/keymap/list-keymap.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/extension-list/src/keymap/list-keymap.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/extension-table-of-contents/src/tableOfContents.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/core/src/helpers/getMarkType.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/extension-code-block/src/code-block.ts
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packages/extension-list/src/keymap/listHelpers/nextListIsDeeper.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/extension-strike/src/strike.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/markdown/src/Extension.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) codemods/tiptap-v4-migration/scripts/vue-sfc-imports.mjs
  • Code Duplication · Duplicated block (10 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/extension-details/src/content/details-content.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/extension-file-handler/src/FileHandlePlugin.ts
  • Code Duplication · Duplicated block (10 lines × 3 locations) packages/extension-table-of-contents/src/tableOfContents.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) codemods/tiptap-v4-migration/scripts/vue-sfc-imports.mjs
  • Code Duplication · Duplicated block (9 lines × 4 locations) packages/core/src/ExtensionManager.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/core/src/InputRule.ts
  • Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) packages/core/src/extensions/keymap.ts
  • Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) packages/extension-emoji/src/emoji.ts
  • Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) packages/extension-emoji/src/emoji.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/extension-link/src/helpers/markdownLink.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/extension-link/src/link.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/react/src/ReactNodeViewRenderer.tsx
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core/src/ExtensionManager.ts
  • Code Duplication · Duplicated block (8 lines × 5 locations) packages/core/src/ExtensionManager.ts
  • Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) packages/core/src/inputRules/wrappingInputRule.ts
  • Code Duplication · Duplicated block (8 lines × 3 locations) packages/core/src/lib/ResizableNodeView.ts
  • Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) packages/extension-collaboration/src/collaboration.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/extension-table-of-contents/src/tableOfContents.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/extension-table/src/table/table.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/extension-unique-id/src/unique-id.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/static-renderer/src/pm/react/react.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/vue/src/menus/BubbleMenu.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core/src/lib/ResizableNodeView.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core/src/utilities/removeDuplicates.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu-plugin.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/extension-code-block/src/code-block.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/react/src/ReactNodeViewRenderer.tsx
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/react/vite.config.ts
  • Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) packages/core/src/decorations/DecorationManager.ts
  • Code Duplication · Duplicated block (5 lines × 2 locations) packages/extension-table/src/table/TableView.ts
  • Large Files · packages/extension-bubble-menu/src/bubble-menu-plugin.ts: 587 lines of code packages/extension-bubble-menu/src/bubble-menu-plugin.ts
  • Large Files · packages/extension-floating-menu/src/floating-menu-plugin.ts: 485 lines of code packages/extension-floating-menu/src/floating-menu-plugin.ts
  • Test Coverage · No test reaches this file scripts/aggregate-changeset.js
  • Test Coverage · No test reaches this file scripts/check-package-exports.mjs
  • Dead Code · Dead file (~140 LoC) demos/src/Extensions/CollaborationMapPositions/React/index.tsx
Rebuild cost: about €160,000 · Estimate
Cost to rebuild€54,000 to €270,000, for 901 to 2,857 hours of work, about 1.1 person-years for 1 to 3 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 109,245 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2).
Raises the score by about 3 points · Low effort · Dependency Hygiene
2
Resolve the 2 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (2).
Raises the score by about 3 points · Low effort · Dependency Hygiene
3
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Raises the score by about 6 points · Medium effort · Dependency Hygiene

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Production Readiness, at 50 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 2 Dependency Hygiene findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 55,238 lines over the last 90 days, which is about 224,021 lines a year. At that pace, the extra work comes to an estimated 12.1 to 74.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch @tiptap/ai-toolkit ai-toolkit @tiptap/core core @tiptap/ai-toolkit->@tiptap/core @tiptap/pm pm @tiptap/ai-toolkit->@tiptap/pm @tiptap/y-tiptap y-tiptap @tiptap/ai-toolkit->@tiptap/y-tiptap @tiptap/core->@tiptap/pm @tiptap/extension-blockquote extension-blockquote @tiptap/extension-blockquote->@tiptap/core @tiptap/extension-blockquote->@tiptap/pm @tiptap/extension-bubble-menu extension-bubble-menu @tiptap/extension-bubble-menu->@tiptap/core @tiptap/extension-bubble-menu->@tiptap/pm @tiptap/extension-code-block extension-code-block @tiptap/extension-code-block->@tiptap/core @tiptap/extension-code-block->@tiptap/pm @tiptap/extension-code-block-lowlight extension-code-block-lowlight @tiptap/extension-code-block-lowlight->@tiptap/core @tiptap/extension-code-block-lowlight->@tiptap/extension-code-block @tiptap/extension-code-block-lowlight->@tiptap/pm @tiptap/extension-collaboration extension-collaboration @tiptap/extension-collaboration->@tiptap/core @tiptap/extension-collaboration->@tiptap/pm @tiptap/extension-collaboration->@tiptap/y-tiptap @tiptap/extension-collaboration-caret extension-collaboration-caret @tiptap/extension-collaboration-caret->@tiptap/core @tiptap/extension-collaboration-caret->@tiptap/pm @tiptap/extension-collaboration-caret->@tiptap/y-tiptap @tiptap/extension-details extension-details @tiptap/extension-details->@tiptap/core @tiptap/extension-text-style extension-text-style @tiptap/extension-details->@tiptap/extension-text-style @tiptap/extension-details->@tiptap/pm @tiptap/extension-drag-handle extension-drag-handle @tiptap/extension-drag-handle->@tiptap/core @tiptap/extension-drag-handle->@tiptap/extension-collaboration @tiptap/extension-drag-handle->@tiptap/pm @tiptap/extension-drag-handle->@tiptap/y-tiptap @tiptap/extension-drag-handle-react extension-drag-handle-react @tiptap/extension-drag-handle-react->@tiptap/extension-drag-handle @tiptap/extension-drag-handle-react->@tiptap/pm @tiptap/react react @tiptap/extension-drag-handle-react->@tiptap/react @tiptap/extension-floating-menu extension-floating-menu @tiptap/extension-floating-menu->@tiptap/core @tiptap/extension-floating-menu->@tiptap/pm @tiptap/extension-list extension-list @tiptap/extension-list->@tiptap/core @tiptap/extension-list->@tiptap/pm @tiptap/extension-text-style->@tiptap/core @tiptap/react->@tiptap/core @tiptap/react->@tiptap/extension-bubble-menu @tiptap/react->@tiptap/extension-floating-menu @tiptap/react->@tiptap/pm @tiptap/starter-kit starter-kit @tiptap/starter-kit->@tiptap/core @tiptap/starter-kit->@tiptap/extension-blockquote @tiptap/starter-kit->@tiptap/extension-code-block @tiptap/starter-kit->@tiptap/extension-list @tiptap/starter-kit->@tiptap/pm @tiptap/suggestion suggestion @tiptap/suggestion->@tiptap/core @tiptap/suggestion->@tiptap/pm @tiptap/vue vue @tiptap/vue->@tiptap/core @tiptap/vue->@tiptap/extension-bubble-menu @tiptap/vue->@tiptap/extension-floating-menu @tiptap/vue->@tiptap/pm __more__ +41 more projects

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.

349 modules, with 213 dependencies between them. 2 loops run through 6 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 core.src.Extendable2 core.src.decorations.Decoration3 core.src.helpers.MappablePosition4 core.src.jsx-runtime5 core.src.utilities.markdown6 extension-find-and-replace.src.search.types7 y-tiptap.src.types.ColorDef8 core.src.Mark9 core.src.Node10 extension-collaboration.src.helpers.CollaborationMappablePosition11 extension-find-and-replace.src.search12 extension-find-and-replace.src.utils13 core.src.types14 extension-collaboration.src.helpers15 y-tiptap.src.lib.utils.binding.ProsemirrorBinding16 core.src.ExtensionManager17 core.src.NodeView18 y-tiptap.src.lib.utils.positions19 y-tiptap.src.types.SyncPluginState20 core.src.Editor21 vue.src.VueNodeViewRenderer22 y-tiptap.src.lib.plugins23 ai-toolkit.src.schema-awareness24 core.src25 core.src.MarkView26 core.src.decorations27 core.src.decorations.types28 core.src.helpers29 extension-drag-handle.src.drag-handle-plugin30 extension-drag-handle.src.helpers31 extension-find-and-replace.src32 react.src.ReactRenderer33 suggestion.src.types34 core.src.decorations.helpers35 react.src.ReactMarkViewRenderer36 react.src.ReactNodeViewRenderer37 suggestion.src.plugin38 vue.src.VueMarkViewRenderer39 react.src40 vue.src
1 core.src.Extendable
2 core.src.decorations.Decoration
3 core.src.helpers.MappablePosition
4 core.src.jsx-runtime
5 core.src.utilities.markdown
6 extension-find-and-replace.src.search.types
7 y-tiptap.src.types.ColorDef
8 core.src.Mark1
9 core.src.Node1
10 extension-collaboration.src.helpers.CollaborationMappablePosition1
11 extension-find-and-replace.src.search2
12 extension-find-and-replace.src.utils19
13 core.src.types1122
14 extension-collaboration.src.helpers21
15 y-tiptap.src.lib.utils.binding.ProsemirrorBinding11
16 core.src.ExtensionManager11
17 core.src.NodeView1
18 y-tiptap.src.lib.utils.positions52
19 y-tiptap.src.types.SyncPluginState11
20 core.src.Editor11
21 vue.src.VueNodeViewRenderer11
22 y-tiptap.src.lib.plugins1
23 ai-toolkit.src.schema-awareness1
24 core.src111
25 core.src.MarkView111
26 core.src.decorations12
27 core.src.decorations.types2
28 core.src.helpers2153
29 extension-drag-handle.src.drag-handle-plugin1
30 extension-drag-handle.src.helpers31
31 extension-find-and-replace.src11
32 react.src.ReactRenderer1
33 suggestion.src.types2
34 core.src.decorations.helpers24
35 react.src.ReactMarkViewRenderer112
36 react.src.ReactNodeViewRenderer111
37 suggestion.src.plugin2
38 vue.src.VueMarkViewRenderer11
39 react.src112411
40 vue.src1211
Uses a module listed above itPart of a loopThe module itself
1 core.src.Extendable2 core.src.decorations.Decoration3 core.src.helpers.MappablePosition4 core.src.jsx-runtime5 core.src.utilities.markdown6 extension-find-and-replace.src.search.types7 y-tiptap.src.types.ColorDef8 core.src.Mark9 core.src.Node10 extension-collaboration.src.helpers.CollaborationMappablePosition11 extension-find-and-replace.src.search12 extension-find-and-replace.src.utils13 core.src.types14 extension-collaboration.src.helpers15 y-tiptap.src.lib.utils.binding.ProsemirrorBinding16 core.src.ExtensionManager17 core.src.NodeView18 y-tiptap.src.lib.utils.positions19 y-tiptap.src.types.SyncPluginState20 core.src.Editor21 vue.src.VueNodeViewRenderer22 y-tiptap.src.lib.plugins23 ai-toolkit.src.schema-awareness24 core.src25 core.src.MarkView26 core.src.decorations27 core.src.decorations.types28 core.src.helpers29 extension-drag-handle.src.drag-handle-plugin30 extension-drag-handle.src.helpers31 extension-find-and-replace.src32 react.src.ReactRenderer33 suggestion.src.types34 core.src.decorations.helpers35 react.src.ReactMarkViewRenderer36 react.src.ReactNodeViewRenderer37 suggestion.src.plugin38 vue.src.VueMarkViewRenderer39 react.src40 vue.srccore.src.Extendable1core.src.decorations.Decoration2core.src.helpers.MappablePosition3core.src.jsx-runtime4core.src.utilities.markdown5extension-find-and-replace.src.search.types6y-tiptap.src.types.ColorDef7core.src.Mark8core.src.Node9extension-collaboration.src.helpers.CollaborationMappablePosition10extension-find-and-replace.src.search11extension-find-and-replace.src.utils12core.src.types13extension-collaboration.src.helpers14y-tiptap.src.lib.utils.binding.ProsemirrorBinding15core.src.ExtensionManager16core.src.NodeView17y-tiptap.src.lib.utils.positions18y-tiptap.src.types.SyncPluginState19core.src.Editor20vue.src.VueNodeViewRenderer21y-tiptap.src.lib.plugins22ai-toolkit.src.schema-awareness23core.src24core.src.MarkView25core.src.decorations26core.src.decorations.types27core.src.helpers28extension-drag-handle.src.drag-handle-plugin29extension-drag-handle.src.helpers30extension-find-and-replace.src31react.src.ReactRenderer32suggestion.src.types33core.src.decorations.helpers34react.src.ReactMarkViewRenderer35react.src.ReactNodeViewRenderer36suggestion.src.plugin37vue.src.VueMarkViewRenderer38react.src39vue.src4011121911222111111521111111111111112221531311112241121112111124111211+309 more modules (most-connected shown)

At a glance — Code Health · 61% · Adequate · gated by R7 ·

At a glance — Architecture · 83% · Strong ·

At a glance — Maturity · 62% · Adequate · gated by M2 ·

At a glance — Readiness · 50% · Weak · gated by R8, P3 ·

At a glance — Security · 63% · Adequate · gated by D29 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection47High / Critical
A03:2025 — Software Supply Chain Failures5Medium

Roadmap

Top priorities: Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing; Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2).

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

Do thisHelpsEffortDimension
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2).+3.4 ptsLowDependency Hygiene
Resolve the 2 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (2).+3.4 ptsLowDependency Hygiene
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+6.0 ptsMediumDependency Hygiene
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.+4.8 ptsMediumSecurity & performance tooling
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json.+2.2 ptsLowADR Quality
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.+2.1 ptsMediumArchitecture documentation
Add tests that import the unreached modules (directly or through their public entry).+2.0 ptsMediumTest Coverage
Resolve the 56 Documentation finding(s) in Documentation Quality — start with README.md (56).+1.3 ptsMediumDocumentation Quality

File quality

Per-file score 0–10 — a quality signature. Of 154 files carrying findings, judged against the Production bar: 1% slop · 32% mixed · 67% near-clean.

FileScoreBandWorst signal
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
packages/extension-bubble-menu/src/bubble-menu-plugin.ts5.4MixedChange Coupling: Boundary-crossing change coupling: bubble-menu-plugin.ts ↔ floating-menu-plugin.ts
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
packages/extension-drag-handle/src/drag-handle-plugin.ts6.0MixedExplicit Debt: TodoComment
packages/static-renderer/src/pm/react/react.ts6.0MixedExplicit Debt: TodoComment
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.5MixedDependency Vulnerabilities: Medium vulnerability: REDACTED
packages/static-renderer/src/pm/html-string/html-string.ts6.7MixedExplicit Debt: TodoComment
packages/extension-drag-handle/src/helpers/findNextElementFromCursor.ts6.7MixedExplicit Debt: TodoComment
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
packages/extension-table/src/table/utilities/markdown.ts6.9MixedCyclomatic Complexity: markdown.renderTableToMarkdown (cyclomatic 26)
packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts7.2MixedCyclomatic Complexity: yCursorPlugin.yCursorPlugin (cyclomatic 30)
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED

How the grades work

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

Critical — 38

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 — 363

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 — 226

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

Could not be resolved — 8

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

Methodology & how to trust this report

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

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

What we checked — 64 dimensions across the health lenses
D1D2D3D5D6D8D10D11D12D13D14D15D16D17D19D20D23D24D26D28D29D30D34D35D36D37D43AX10AX3AX4AX6GD1IC1M1M2M3M4P1P10P3P4P6PF3R1R10R11R2R3R4R6R7R8R9X1X12X16X17X21X24X25X29X3X30X5

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

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1d9f1-e664-72cb-83bc-df656171b06b.

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

Run transparency — what happened this run

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

  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (packages/y-tiptap/package.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/core/jsx-dev-runtime/index.d.ts`, `packages/core/jsx-runtime/index.d.ts`, `packages/core/src/decorations/DecorationManager.ts`, `packages/core/src/helpers/getSchemaSpecByResolvedExtensions.ts`, `packages/core/src/index.ts`, … (+5 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> dev / > vp run start / ~/demos$ vp dev --host ⊘ cache disabled / 12:05:06 PM [vite-plugin-svelte] no Svelte config found at <repo>/demos - using default configuration. / 12:05:07 PM [vite+] (client) Forced re-optimization of dependencies / 12:05:08 PM [vite+] (ssr) [optimizer] bundling dependencies... / VITE+ v1.3.0 ready in 2137 ms / ➜ Local: http://localhost:3000/ / ➜ Network: http://172.31.7.9:3000/ eth0 / 12:05:08 PM [vite+] (client) [optimizer] bundling dependencies..." No runtime evidence was gathered.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> dev / > vp run start / ~/demos$ vp dev --host ⊘ cache disabled / 12:05:06 PM [vite-plugin-svelte] no Svelte config found at <repo>/demos - using default configuration. / 12:05:07 PM [vite+] (client) Forced re-optimization of dependencies / 12:05:08 PM [vite+] (ssr) [optimizer] bundling dependencies... / VITE+ v1.3.0 ready in 2137 ms / ➜ Local: http://localhost:3000/ / ➜ Network: http://172.31.7.9:3000/ eth0 / 12:05:08 PM [vite+] (client) [optimizer] bundling dependencies..." No runtime evidence was gathered.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 68 further occurrence(s) are not listed individually; the score already reflects all 108.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 51 further occurrence(s) are not listed individually; the score already reflects all 91.
  • R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 401 further occurrence(s) are not listed individually; the score already reflects all 441.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 782 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • 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 — we run 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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • 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.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

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

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

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

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

36 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was updateYFragment.updateYFragment at 47.

updateYFragment.updateYFragment (cyclomatic 47)packages/y-tiptap/src/lib/utils/reconciliation/updateYFragment.ts:19
absolutePositionToRelativePosition.absolutePositionToRelativePosition (cyclomatic 40)packages/y-tiptap/src/lib/utils/positions/absolutePositionToRelativePosition.ts:11
MarkdownManager.renderNodesWithMarkBoundaries (cyclomatic 39)REDACTED:1310
splitListItem.splitListItem.<returned closure> (cyclomatic 37)packages/core/src/commands/splitListItem.ts:29
toggleList.toggleList.<returned closure> (cyclomatic 37)packages/core/src/commands/toggleList.ts:133

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

What to do

  1. Bring the 36 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with updateYFragment.updateYFragment (cyclomatic 47), absolutePositionToRelativePosition.absolutePositionToRelativePosition (cyclomatic 40), MarkdownManager.renderNodesWithMarkBoundaries (cyclomatic 39). — 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 36 together lifts Cyclomatic Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

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

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

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

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

53 method(s) exceeded the cognitive complexity threshold of 15; the worst was absolutePositionToRelativePosition.absolutePositionToRelativePosition at 103.

absolutePositionToRelativePosition.absolutePositionToRelativePosition (cognitive 103)packages/y-tiptap/src/lib/utils/positions/absolutePositionToRelativePosition.ts:11
MarkdownManager.parseInlineTokens (cognitive 73)REDACTED:752
MarkdownManager.renderNodesWithMarkBoundaries (cognitive 72)REDACTED:1310
toggleList.toggleList.<returned closure> (cognitive 63)packages/core/src/commands/toggleList.ts:133
updateYFragment.updateYFragment (cognitive 60)packages/y-tiptap/src/lib/utils/reconciliation/updateYFragment.ts:19

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

What to do

  1. Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with absolutePositionToRelativePosition.absolutePositionToRelativePosition (cognitive 103), MarkdownManager.parseInlineTokens (cognitive 73), MarkdownManager.renderNodesWithMarkBoundaries (cognitive 72). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 4.7 to about 5.7/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes9.6 / 10Stronggated by 12 serious findings✓ Tool-verified

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

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

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

12 god class(es) detected.

FunctionTooLong: drag-handle-plugin.DragHandlePlugin · ×8packages/extension-drag-handle/src/drag-handle-plugin.ts:88
FileTooLong: REDACTED · ×2REDACTED
TooManyMethods: MarkdownManagerREDACTED:39
ClassTooLong: Editorpackages/core/src/Editor.ts:60

What to do

  1. Resolve the 8 FunctionTooLong finding(s) in God Classes — start with drag-handle-plugin.ts, view.ts, PasteRule.ts. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 2 FileTooLong finding(s) in God Classes — start with REDACTED, Editor.ts. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 TooManyMethods finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D5 · Coupling9.5 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

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

61 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 38 of the 61 (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: @tiptap/y-tiptap · ×4

What to do

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

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 34 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage9.7 / 10Exemplary✓ Tool-verified

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

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

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

Line coverage 71.6%. Measured from the JavaScript/TypeScript suite (node:test via `pnpm install --frozen-lockfile --ignore-scripts` in codemods/tiptap-v4-migration/).

✓ On the Gold path — maintain.

Detailed fixes: d8_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ 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.

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

2 skipped (2 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2570 tests.

Mock-dominated test: should respect shouldShow returning false · ×16packages/suggestion/tests/integration/suggestion.test.ts:9
Skipped (documented): (unnamed test) · ×2packages/y-tiptap/tests/integration/cache.test.ts:58

✓ On the Gold path — maintain.

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

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.

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

0 flaky across 1 measured tier(s). JavaScript/TypeScript (node:test via `pnpm install --frozen-lockfile --ignore-scripts` in codemods/tiptap-v4-migration/ (2 tests)): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene8.6 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

29 outdated direct production npm dependency(ies) of 47 graded, 0 pinning defect(s), across 64 package.json (63 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 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.

Deprecated: git-raw-commits · ×2REDACTED:4349
Outdated (npm): @shikijs/core · ×2demos/package.json:18
Outdated (npm): @hocuspocus/provider · ×27

What to do

  1. Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
  2. Resolve the 2 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (2). — One of this dimension's main actionable groups (2 recommendation-level).

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 235 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 235 package(s) this repository's committed lockfile installs for a consumer — its 47 production, optional and peer dependency(ies), across 63 product package.json manifest(s), and everything those install in turn. Its 208 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ 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. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 22 serious findings✓ Tool-verified

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

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

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

Top hotspots: packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts (16×30=480); packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts (10×20=200); REDACTED (5×39=195) Repeated repair below the complexity floor: packages/core/src/Editor.ts (5 of 6 changes were fixes); packages/y-tiptap/src/lib/plugins/yUndoPlugin.ts (5 of 5 changes were fixes); packages/static-renderer/src/pm/html-string/html-string.ts (3 of 5 changes were fixes)

Hotspot: packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts · ×12packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts:162
Repeated repair: packages/core/src/Editor.ts · ×10packages/core/src/Editor.ts:178

What to do

  1. Resolve the 12 Hotspot finding(s) in Churn × Complexity Hotspots — start with yCursorPlugin.ts, ProsemirrorBinding.ts, REDACTED. — One of this dimension's main actionable groups (12 warning-level).
  2. Resolve the 10 Repeated repair finding(s) in Churn × Complexity Hotspots — start with Editor.ts, yUndoPlugin.ts, html-string.ts. — One of this dimension's main actionable groups (10 warning-level).

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

D16 · Bus Factor8.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.

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

29 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/static-renderer/src/pm/extensionRenderer.ts. Counted over 275 of the 1174 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 · ×2
Further sole-owners (lower concentration)

What to do

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

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

D17 · Explicit Debt10.0 / 10Stronggated by 18 serious findings✓ Tool-verified

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

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

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

18 deducted task-comment markers across 81800 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×18packages/vue/src/menus/FloatingMenu.ts:14

What to do

  1. Resolve the 18 TodoComment finding(s) in Explicit Debt — start with drag-handle-plugin.ts (3), link.ts (2), FloatingMenu.ts. — One of this dimension's main actionable groups (18 warning-level).

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

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

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

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

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

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

Documentation: no build, run or usage example · ×56packages/ai-toolkit/README.md:1

What to do

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

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

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

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

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

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

No architecture decision records were found.

No ADRs foundpackage.json:9

What to do

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

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

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

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.

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

2 domain type(s) cross context boundaries across 55 contexts; they are measured and withheld (not published, not scored). Contexts: ai-toolkit, core, demos, extension-audio, extension-blockquote, extension-bold, extension-bubble-menu, extension-code, extension-code-block, extension-code-block-lowlight, extension-collaboration, extension-collaboration-caret and 43 more.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value8.4 8.2 / 10Strong✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 98% · ceiling Documented

24 of 1477 judged comments only repeat the code they sit on (1.6 %). 29 comment(s) in another language or script were not judged.

redundant comment · ×24packages/core/src/helpers/createNodeFromContent.ts:68
doc comments repeat the names · ×18packages/ai-toolkit/src/schema-awareness/get-editor-context.ts:12

What to do

  1. Resolve the 24 redundant comment finding(s) in Comment Value — start with task-item.test.ts (3), utils.ts (3), VueMarkViewRenderer.test.ts (3). — One of this dimension's main actionable groups (24 recommendation-level).

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

D26 · Project Cohesion9.7 / 10Exemplary✓ Tool-verified

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

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

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

1 of 63 build units (npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

✓ On the Gold path — maintain.

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

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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

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

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.3 / 10Critical✓ Tool-verified

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

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

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

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

47 finding(s): 0 critical, 35 high, 12 medium, 0 low. 19 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 10 file(s) — `packages/core/jsx-dev-runtime/index.d.ts` (line 1), `packages/core/jsx-runtime/index.d.ts` (line 1), `packages/core/src/decorations/DecorationManager.ts` (line 276, line 316), `packages/core/src/helpers/getSchemaSpecByResolvedExtensions.ts` (lines 235–239), `packages/core/src/index.ts` (line 2), … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (7 issue-level).
  2. Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 19 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (21 issue-level, 2 of them charged here).
  3. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).

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

D30 · Dependency Vulnerabilities9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

2 finding(s): 0 critical, 0 high, 1 medium, 1 low.

REDACTED
REDACTED

What to do

  1. Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D34 · Knowledge Freshness8.5 / 10Strong✓ Tool-verified

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

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

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

42 of 275 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is demos/src/Experiments/All/Vue/index.vue. Counted over 275 of the 1174 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×42demos/src/Experiments/All/Vue/index.vue:1
Orphaned files with no living knowledge

What to do

  1. Resolve the 42 Orphaned file finding(s) in Knowledge Freshness — start with index.vue (21), index.jsx (9), Demo.vue. — One of this dimension's main actionable groups (42 recommendation-level).
  2. Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.9 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

Strongest change-coupling: BubbleMenu.ts↔FloatingMenu.ts 82%; table-cell.ts↔table-row.ts 82%; table-cell.ts↔table-header.ts 80%

Boundary-crossing change coupling: bubble-menu-plugin.ts ↔ floating-menu-plugin.tspackages/extension-bubble-menu/src/bubble-menu-plugin.ts:1
Change coupling: BubbleMenu.ts ↔ FloatingMenu.ts · ×2packages/vue/src/menus/BubbleMenu.ts:1
Change-coupling hub: table-cell.ts → table-header.ts, table-row.ts, table.tspackages/extension-table/src/cell/table-cell.ts
Change coupling clique: Extension.ts, Mark.ts, Node.tspackages/core/src/Extension.ts

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with bubble-menu-plugin.ts. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 2 Change coupling finding(s) in Change Coupling — start with BubbleMenu.ts, clearContent.ts. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with table-cell.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.

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ Tool-verified

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.

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

2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. 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).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition7.4 / 10Strong✓ Tool-verified

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

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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

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

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

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.

  • The guard above `return key;` also returns `key`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — packages/react/src/menus/useMenuElementProps.ts:106

What to do

  • Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
M1 · Documentation (README)8.6 / 10Strong✓ Tool-verified

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

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

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

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

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:17
  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:5

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
  • Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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.

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

R1 · Type Safety9.9 / 10Exemplary✓ 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.

R10 · Code Duplication6.8 / 10Adequate✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 47 duplicated blocks under packages/ have copies in at least two of the sibling directories core, extension-audio, extension-blockquote, extension-bold, extension-bubble-menu, extension-code (+31 more sibling(s) not listed) — 35 of them are reported below, and 12 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 47 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 47 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 47 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/react/src/ReactNodeViewRenderer.tsx:142
  • packages/extension-mathematics/src/extensions/BlockMath.ts:8 · packages/extension-mathematics/src/extensions/InlineMath.ts:9 — the two spans are one implementation copied and then locally edited — 805 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/extension-mathematics/src/extensions/BlockMath.ts:8
  • packages/core/src/Mark.ts:8 · packages/core/src/Node.ts:8 — the two spans are one implementation copied and then locally edited — 650 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/core/src/Mark.ts:8
  • packages/react/src/ReactNodeViewRenderer.tsx:142 · packages/vue/src/VueNodeViewRenderer.ts:118 — the two spans are one implementation copied and then locally edited — 543 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/react/src/ReactNodeViewRenderer.tsx:142
  • packages/extension-bold/src/bold.tsx:4 · packages/extension-italic/src/italic.ts:3 — the two spans are one implementation copied and then locally edited — 355 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/extension-bold/src/bold.tsx:4
  • packages/react/src/menus/BubbleMenu.tsx:27 · packages/react/src/menus/FloatingMenu.tsx:29 — 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/react/src/menus/BubbleMenu.tsx:27
  • packages/extension-bubble-menu/src/bubble-menu-plugin.ts:555 · packages/extension-floating-menu/src/floating-menu-plugin.ts:333 — the two spans are one implementation copied and then locally edited — 463 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/extension-bubble-menu/src/bubble-menu-plugin.ts:555
  • packages/extension-subscript/src/subscript.ts:4 · packages/extension-superscript/src/superscript.ts:4 — 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/extension-subscript/src/subscript.ts:4
  • packages/extension-text-style/src/background-color/background-color.ts:5 · packages/extension-text-style/src/color/color.ts:5 — 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/extension-text-style/src/background-color/background-color.ts:5
  • packages/extension-table/src/cell/table-cell.ts:10 · packages/extension-table/src/header/table-header.ts:10 — 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/extension-table/src/cell/table-cell.ts:10
  • packages/extension-twitch/src/twitch.ts:216 · packages/extension-youtube/src/youtube.ts:292 — 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/extension-twitch/src/twitch.ts:216
  • REDACTED:1585 · REDACTED:1634 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:1585
  • packages/static-renderer/src/pm/extensionRenderer.ts:79 · packages/static-renderer/src/pm/extensionRenderer.ts:136 — 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/static-renderer/src/pm/extensionRenderer.ts:79
  • packages/core/src/helpers/getSchemaSpecByResolvedExtensions.ts:68 · packages/core/src/helpers/getSchemaSpecByResolvedExtensions.ts:166 — the two spans are one implementation copied and then locally edited — 293 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/core/src/helpers/getSchemaSpecByResolvedExtensions.ts:68
  • REDACTED:67 · REDACTED:70 — the two spans are one implementation copied and then locally edited — 197 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. — REDACTED:67
  • packages/extension-text-style/src/font-family/font-family.ts:52 · packages/extension-text-style/src/font-size/font-size.ts:52 · packages/extension-text-style/src/line-height/line-height.ts:52 — the 3 copies are spread across 3 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/extension-text-style/src/font-family/font-family.ts:52
  • packages/extension-bubble-menu/src/bubble-menu-plugin.ts:101 · packages/extension-floating-menu/src/floating-menu-plugin.ts:78 — the 2 copies are spread across 2 files, and the CITED SPAN is inside a TYPE DECLARATION, not executable code. There is no function to extract and no call site to call one from, so do not read this as an extract-a-helper row: the collapse a type offers is a generic — name the shape once, parameterised over the part that varies, and have each copy instantiate it. First check what actually differs between the copies: where they are a MATRIX of cases (one entry per input, differing precisely in the case each one pins), the repetition IS the enumeration and collapsing it would delete cases rather than de-duplicate anything — leave those alone. Reported because the copies that are not a matrix drift apart the first time only one of them is edited. — packages/extension-bubble-menu/src/bubble-menu-plugin.ts:101
  • packages/extension-bubble-menu/src/bubble-menu-plugin.ts:380 · packages/extension-floating-menu/src/floating-menu-plugin.ts:294 — 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/extension-bubble-menu/src/bubble-menu-plugin.ts:380
  • packages/extension-highlight/src/highlight.ts:158 · packages/extension-strike/src/strike.ts:101 — 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/extension-highlight/src/highlight.ts:158
  • packages/extension-table/src/table/table.ts:440 · packages/extension-table/src/table/table.ts:470 — both copies are in the same file, so extract the 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/extension-table/src/table/table.ts:440
  • packages/core/src/MarkView.ts:100 · packages/core/src/NodeView.ts:290 — 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/core/src/MarkView.ts:100
  • packages/extension-code/src/code.ts:167 · packages/extension-highlight/src/highlight.ts:158 · packages/extension-strike/src/strike.ts:101 — the 3 copies are spread across 3 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/extension-code/src/code.ts:167
  • packages/core/src/commands/joinItemBackward.ts:19 · packages/core/src/commands/joinItemForward.ts:19 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/core/src/commands/joinItemBackward.ts:19
  • packages/extension-list/src/task-list/task-list.ts:91 · packages/extension-list/src/task-list/task-list.ts:138 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/extension-list/src/task-list/task-list.ts:91
  • packages/extension-twitch/src/twitch.ts:178 · packages/extension-youtube/src/youtube.ts:262 — 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/extension-twitch/src/twitch.ts:178
  • packages/core/src/helpers/findParentNodeClosestToPos.ts:14 · packages/extension-details/src/helpers/findClosestVisibleNode.ts:6 — the two spans are one implementation copied and then locally edited — 94 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/core/src/helpers/findParentNodeClosestToPos.ts:14
  • packages/extension-bubble-menu/src/bubble-menu-plugin.ts:248 · packages/extension-floating-menu/src/floating-menu-plugin.ts:231 — 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/extension-bubble-menu/src/bubble-menu-plugin.ts:248
  • packages/extension-table-of-contents/src/plugin.ts:15 · packages/extension-table-of-contents/src/tableOfContents.ts:273 — the two spans are one implementation copied and then locally edited — 128 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/extension-table-of-contents/src/plugin.ts:15
  • packages/core/src/decorations/Decoration.ts:89 · packages/core/src/decorations/Decoration.ts:118 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/core/src/decorations/Decoration.ts:89
  • packages/extension-find-and-replace/src/style/create-style-tag.ts:1 · packages/extension-invisible-characters/src/plugin/utils/create-style-tag.ts:1 — 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/extension-find-and-replace/src/style/create-style-tag.ts:1
  • REDACTED:497 · REDACTED:666 — 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. — REDACTED:497
  • packages/core/src/Extension.ts:10 · packages/core/src/Node.ts:338 — 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/core/src/Extension.ts:10
  • packages/core/src/commands/setTextDirection.ts:20 · packages/core/src/commands/unsetTextDirection.ts:19 — 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/core/src/commands/setTextDirection.ts:20
  • packages/extension-audio/src/audio.ts:200 · packages/extension-twitch/src/twitch.ts:234 · packages/extension-youtube/src/youtube.ts:310 — 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/extension-audio/src/audio.ts:200
  • packages/core/src/commands/resetAttributes.ts:27 · packages/core/src/commands/updateAttributes.ts:34 — 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/core/src/commands/resetAttributes.ts:27
  • packages/core/src/inputRules/markInputRule.ts:37 · packages/core/src/pasteRules/markPasteRule.ts:37 — 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/core/src/inputRules/markInputRule.ts:37
  • packages/core/src/inputRules/textInputRule.ts:12 · packages/core/src/pasteRules/textPasteRule.ts:9 — 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/core/src/inputRules/textInputRule.ts:12
  • packages/extension-blockquote/src/blockquote.tsx:108 · packages/extension-bold/src/bold.tsx:111 · packages/extension-code/src/code.ts:157 · packages/extension-strike/src/strike.ts:91 · +3 more site(s) not listed — the 7 copies are spread across 7 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/extension-blockquote/src/blockquote.tsx:108
  • packages/extension-italic/src/italic.ts:90 · packages/extension-subscript/src/subscript.ts:72 · packages/extension-superscript/src/superscript.ts:72 — the 3 copies are spread across 3 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/extension-italic/src/italic.ts:90
  • packages/extension-bubble-menu/src/bubble-menu.ts:32 · packages/extension-floating-menu/src/floating-menu.ts:59 — 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/extension-bubble-menu/src/bubble-menu.ts:32

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.
R11 · Import Boundaries9.9 / 10Exemplary✓ Tool-verified

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/extension-code-block-lowlight/src/lowlight-plugin.ts:6 imports highlight.js/lib/core, 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/extension-code-block-lowlight/src/lowlight-plugin.ts:6

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity8.3 / 10Strong✓ Tool-verified

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.

  • absolutePositionToRelativePosition has cyclomatic complexity 42 and cognitive complexity 128; 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/y-tiptap/src/lib/utils/positions/absolutePositionToRelativePosition.ts:11
  • parseInlineTokens has cyclomatic complexity 39 and cognitive complexity 74; 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. — REDACTED:752
  • update has cyclomatic complexity 36 and cognitive complexity 43; 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/suggestion/src/plugin/view.ts:96
  • (anonymous) has cyclomatic complexity 34 and cognitive complexity 47; 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/core/src/commands/splitListItem.ts:29
  • stopEvent has cyclomatic complexity 33 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/core/src/NodeView.ts:166
  • (anonymous) has cyclomatic complexity 31 and cognitive complexity 36; 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/y-tiptap/src/lib/utils/reconciliation/updateYFragment.ts:109
  • (anonymous) has cyclomatic complexity 29 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/commands/insertContentAt.ts:66
  • (anonymous) has cyclomatic complexity 29 and cognitive complexity 40; 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/core/src/commands/splitBlock.ts:35
  • (anonymous) has cyclomatic complexity 29 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 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/core/src/commands/toggleList.ts:133
  • addInputRules has cyclomatic complexity 27 and cognitive complexity 32; 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/extension-typography/src/typography.ts:345
  • getEmbedUrlFromYoutubeUrl has cyclomatic complexity 26 and cognitive complexity 27; 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/extension-youtube/src/utils.ts:55
  • (anonymous) has cyclomatic complexity 24 and cognitive complexity 41; 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. — REDACTED:1322
  • menuBarStateSelector has cyclomatic complexity 24 and cognitive complexity 23; 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. — demos/src/Examples/Default/React/menuBarState.ts:8
  • apply has cyclomatic complexity 23 and cognitive complexity 33; 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/suggestion/src/plugin/state.ts:65
  • selector has cyclomatic complexity 23 and cognitive complexity 22; 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. (×2) — demos/src/Examples/StaticRendering/React/index.tsx:213, demos/src/Experiments/IsolatingClear/React/index.jsx:32
  • addExtensions has cyclomatic complexity 23 and cognitive complexity 22; 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/starter-kit/src/starter-kit.ts:180
  • MenuBar has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — demos/src/Examples/Default/React/MenuBar.tsx:7, demos/src/Experiments/IsolatingClear/React/index.jsx:29
  • selector has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — demos/src/Examples/Tables/React/index.jsx:57
  • parseIndentedBlocks has cyclomatic complexity 17 and cognitive complexity 40; 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/core/src/utilities/markdown/parseIndentedBlocks.ts:130
  • updateYFragment has cyclomatic complexity 17 and cognitive complexity 28; 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/y-tiptap/src/lib/utils/reconciliation/updateYFragment.ts:19
  • handleKeyDown has cyclomatic complexity 17 and cognitive complexity 19; 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/extension-emoji/src/emoji.ts:395
  • handler has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/core/src/inputRules/wrappingInputRule.ts:41
  • MenuBar has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. (×3) — demos/src/Examples/Book/React/index.jsx:27, demos/src/Examples/CSSModules/React/index.jsx:27, demos/src/Examples/StaticRendering/React/index.tsx:208
  • domOutputSpecToReactElement has cyclomatic complexity 16 and cognitive complexity 37; 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/static-renderer/src/pm/react/react.ts:64
  • updateColumns has cyclomatic complexity 16 and cognitive complexity 36; 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/extension-table/src/table/TableView.ts:6
  • replacePackageSpecifiers has cyclomatic complexity 16 and cognitive complexity 27; 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. — codemods/tiptap-v4-migration/scripts/vue-sfc-imports.mjs:142
  • parseMarkdown has cyclomatic complexity 16 and cognitive complexity 26; 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/extension-list/src/item/list-item.ts:97
  • middlewares has cyclomatic complexity 16 and cognitive complexity 22; 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/extension-bubble-menu/src/bubble-menu-plugin.ts:225, packages/extension-floating-menu/src/floating-menu-plugin.ts:208
  • menuBarStateSelector has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. (×2) — demos/src/Examples/Book/React/index.jsx:9, demos/src/Examples/CSSModules/React/index.jsx:9
  • ignoreMutation has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/core/src/NodeView.ts:271
  • findSuggestionMatch has cyclomatic complexity 16 and cognitive complexity 14; 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. — REDACTED:20
  • _isDomSelectionInView has cyclomatic complexity 16 and cognitive complexity 13; 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/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts:127
  • handleMobileEnter has cyclomatic complexity 16 and cognitive complexity 12; 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/react/src/handleMobileEnter.ts:9
  • domOutputSpecToHTMLString has cyclomatic complexity 15 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/static-renderer/src/pm/html-string/html-string.ts:43
R3 · Large Files9.2 / 10Exemplary✓ 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.

  • REDACTED has 1536 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/core/src/types.ts has 1048 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/core/src/types.ts:1
  • packages/core/src/lib/ResizableNodeView.ts has 923 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/core/src/lib/ResizableNodeView.ts:1
  • packages/core/src/Editor.ts has 804 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/core/src/Editor.ts:1
  • packages/core/src/Extendable.ts has 622 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/core/src/Extendable.ts:1
  • packages/extension-bubble-menu/src/bubble-menu-plugin.ts has 602 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/extension-bubble-menu/src/bubble-menu-plugin.ts:1
  • packages/extension-table/src/table/table.ts has 562 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/extension-table/src/table/table.ts:1
  • packages/extension-floating-menu/src/floating-menu-plugin.ts has 499 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/extension-floating-menu/src/floating-menu-plugin.ts:1
  • packages/extension-link/src/link.ts has 497 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/extension-link/src/link.ts:1
  • packages/core/src/ExtensionManager.ts has 489 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/core/src/ExtensionManager.ts:1
  • packages/extension-emoji/src/emoji.ts has 466 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/extension-emoji/src/emoji.ts:1
  • packages/extension-drag-handle/src/drag-handle-plugin.ts has 448 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/extension-drag-handle/src/drag-handle-plugin.ts:1
  • packages/static-renderer/src/pm/extensionRenderer.ts has 440 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/static-renderer/src/pm/extensionRenderer.ts:1
  • packages/extension-code-block/src/code-block.ts has 425 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/extension-code-block/src/code-block.ts:1
  • packages/extension-details/src/details.ts has 420 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/extension-details/src/details.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage6.1 / 10Adequate✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×24) — packages/extension-typography/src/typography.ts:1, demos/preview/Demo.vue:1, demos/preview/index.vue:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
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.

R7 · Dead Code2.9 / 10Weak✓ 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.

  • 348 file(s) (~32025 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/core/jsx-dev-runtime/index.js imports '../dist/jsx-runtime/jsx-runtime.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/core
  • Unreachable from the 131 application, 73 tooling and 375 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 (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×31) — demos/src/Experiments/CollaborationMappingPerformance/React/index.tsx, demos/src/Examples/StaticRendering/React/index.tsx, demos/src/Examples/NodePos/React/index.jsx, …
  • no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 5 in-repo import(s) from 4 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×7) — demos/src/Examples/Accessibility/React/MenuBar.tsx, demos/src/Experiments/Figure/Vue/figure.ts, demos/src/Experiments/GlobalDragHandle/Vue/DragHandle.js, …

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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. (×6)
  • Declared in demos/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. (×19)
  • Declared in packages/starter-kit/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. (×2)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports6.6 / 10Adequate✓ Tool-verified

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.

  • packages/extension-node-range/src/helpers/NodeRangeBookmark.ts → packages/extension-node-range/src/helpers/NodeRangeSelection.ts → packages/extension-node-range/src/helpers/NodeRangeBookmark.ts — packages/extension-node-range/src/helpers/NodeRangeBookmark.ts:4
  • packages/react/src/Tiptap.tsx → packages/react/src/index.ts → packages/react/src/Tiptap.tsx — packages/react/src/Tiptap.tsx:7

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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

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

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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

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

X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ 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.

  • `equalAttrs` is exported and takes `pattrs: Record<string, unknown>` from its caller, and it calls itself at line 10 (`equalAttrs`) with a piece of `pattrs` — and nowhere in `equalAttrs` 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 `equalAttrs` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/y-tiptap/src/lib/utils/reconciliation/equalAttrs.ts:10
  • `mergeDeep` is exported and takes `target: Record<string, any>` from its caller, and it calls itself at line 12 (`mergeDeep`) with a piece of `target` — and nowhere in `mergeDeep` 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 `mergeDeep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/core/src/utilities/mergeDeep.ts:12

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.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X24 · Document value interpolated into markup unescaped5.2 / 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.

  • `style` 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. (×2) — packages/core/src/utilities/createStyleTag.ts:17, packages/extension-invisible-characters/src/plugin/utils/create-style-tag.ts:17

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.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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

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

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.

X3 · Exception handling5.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×8) — packages/react/src/captureDOMSelection.ts:31, packages/react/src/ReactRenderer.tsx:99, packages/react/src/ReactRenderer.tsx:286, …
  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — packages/core/src/helpers/warnOnDuplicatedProseMirrorModel.ts:35

What to do

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

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

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

X5 · Nullable reference types9.9 / 10Exemplary✓ Tool-verified

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.

  • ~0.3 `!` null assertions per 1k TypeScript source lines — 25 assertion(s) across the 83949 source line(s) of the 777 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/core/src/Editor.ts (6), packages/extension-node-range/src/helpers/NodeRangeBookmark.ts (3), packages/vue/src/VueNodeViewRenderer.ts (3). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

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 `?`).

Reference — by lens

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

LensScoreRatingImpact
Code Health61%Adequate — gated by R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture83%StrongSolid.
Maturity62%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness50%Weak — gated by R8, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security63%Adequate — gated by D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 21 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • 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
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> dev / > vp run start / ~/demos$ vp dev --host ⊘ cache disabled / 12:05:06 PM [vite-plugin-svelte] no Svelte config found at <repo>/demos - using default configuration. / 12:05:07 PM [vite+] (client) Forced re-optimization of dependencies / 12:05:08 PM [vite+] (ssr) [optimizer] bundling dependencies... / VITE+ v1.3.0 ready in 2137 ms / ➜ Local: http://localhost:3000/ / ➜ Network: http://172.31.7.9:3000/ eth0 / 12:05:08 PM [vite+] (client) [optimizer] bundling dependencies..." No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, 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.
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 9 candidate(s) found and not reported.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 10 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D4 Code Duplication — This repository's production source (.ts, .tsx) 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 none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P2 Observability — This repository's JavaScript/TypeScript source (61 module(s), 786 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
  • 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 1 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • 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
  • S1 Web-Security Posture — Not assessed: 782 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and 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.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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.
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 38 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
R9 · Circular Imports · Import cycle (2 files) · ×2
  • Import cycle (2 files) packages/extension-node-range/src/helpers/NodeRangeBookmark.ts:4 — packages/extension-node-range/src/helpers/NodeRangeBookmark.ts → packages/extension-node-range/src/helpers/NodeRangeSelection.ts → packages/extension-node-range/src/helpers/NodeRangeBookmark.ts
  • Import cycle (2 files) packages/react/src/Tiptap.tsx:7 — packages/react/src/Tiptap.tsx → packages/react/src/index.ts → packages/react/src/Tiptap.tsx
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: bubble-menu-plugin.ts ↔ floating-menu-plugin.ts packages/extension-bubble-menu/src/bubble-menu-plugin.ts:1 — `packages/extension-bubble-menu/src/bubble-menu-plugin.ts` (context extension-bubble-menu) and `packages/extension-floating-menu/src/floating-menu-plugin.ts` (context extension-floating-menu) sit in DIFFERENT parts of the tree yet change together 60% of the time (27 of the 45 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 27 shared commits counted here, the most recent 3 are `22b1527f` Floating & Bubble Menu Show/Hide Events (#7171); `253ca1c8` fix: use instance-specific pluginKey as transaction meta key in Bubbl…; `3e446fb1` Fix BubbleMenu and FloatingMenu not supporting option updates after i… — run `git show` on any of them.
Serious — 363 finding(s)
R4 · Test Coverage · No test reaches this file · ×24
  • No test reaches this file packages/extension-typography/src/typography.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 demos/preview/Demo.vue: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 demos/preview/index.vue: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/extension-emoji/src/generate.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 demos/preview/Shiki.vue: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 demos/preview/index.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 demos/preview/DemoFrame.vue: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 demos/setup/helper.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 demos/setup/react.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 codemods/tiptap-v4-migration/scripts/vue-package-renames.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 demos/preview/shiki.worker.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/extension-drag-handle/src/helpers/getInnerCoords.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 demos/setup/vue.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 demos/setup/svelte.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 demos/setup/js.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/extension-emoji/src/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/extension-code-block-lowlight/src/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/extension-drag-handle-react/src/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/extension-drag-handle/src/helpers/getComputedStyle.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/extension-ruby-text/src/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/extension-subscript/src/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/extension-superscript/src/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/extension-typography/src/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/extension-drag-handle/src/helpers/minMax.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.
D17 · Explicit Debt · TodoComment · ×18
  • TodoComment packages/vue/src/menus/FloatingMenu.ts:14 — // TODO: TypeScript breaks :( — 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/static-renderer/src/pm/react/react.ts:148 — // TODO support DOM elements? How to handle them? — 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/static-renderer/src/pm/html-string/html-string.ts:103 — // TODO support DOM elements? How to handle them? — 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/extension-table/src/table/table.ts:277 — // TODO: fix — 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/extension-link/src/link.ts:229 — // TODO: v4 - remove validate option — 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/extension-link/src/link.ts:259 — // TODO (major) - default to true on next major version — 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/extension-drag-handle/src/drag-handle-plugin.ts:330 — // TODO: Remove — 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/extension-drag-handle/src/drag-handle-plugin.ts:413 — // TODO: needed? — 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/extension-drag-handle/src/drag-handle-plugin.ts:426 — // TODO: Kills even on hot reload — 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/extension-drag-handle/src/helpers/findNextElementFromCursor.ts:133 — // TODO — 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/extension-details/src/details.ts:355 — // TODO: this may break for some custom schemas — 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/core/src/types.ts:752 — // TODO this type is not technically correct, but it's the best we can do for now since prosemirror doesn't expose the type of decorations — 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/core/src/lib/ResizableNodeView.ts:778 — // TODO: Select the node in the editor — 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/core/src/helpers/getAttributesFromExtensions.ts:94 — // TODO: remove `as Attributes` — 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/core/src/commands/selectTextblockEnd.ts:2 — // TODO: add types to @types/prosemirror-commands — 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/core/src/commands/selectTextblockStart.ts:2 — // TODO: add types to @types/prosemirror-commands — 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/core/src/commands/setContent.ts:56 — // TODO remove this in the next major version — 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/core/src/commands/setNode.ts:33 — // TODO: use a fallback like insertContent? — 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×12
  • Hotspot: packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts:162 — packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in yCursorPlugin.yCursorPlugin at line 162. 14 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/y-tiptap/src/lib/plugins/yCursorPlugin.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/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts:264 — packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in ProsemirrorBinding._renderSnapshot at line 264. 10 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.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:1310 — REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in MarkdownManager.renderNodesWithMarkBoundaries at line 1310. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01: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/y-tiptap/src/lib/plugins/ySyncPlugin.ts packages/y-tiptap/src/lib/plugins/ySyncPlugin.ts:14 — packages/y-tiptap/src/lib/plugins/ySyncPlugin.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in ySyncPlugin.ySyncPlugin at line 14. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/y-tiptap/src/lib/plugins/ySyncPlugin.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/core/src/commands/splitListItem.ts packages/core/src/commands/splitListItem.ts:29 — packages/core/src/commands/splitListItem.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in splitListItem.splitListItem.<returned closure> at line 29. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/core/src/commands/splitListItem.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/extension-table/src/table/utilities/markdown.ts packages/extension-table/src/table/utilities/markdown.ts:101 — packages/extension-table/src/table/utilities/markdown.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in markdown.renderTableToMarkdown at line 101. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/extension-table/src/table/utilities/markdown.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/y-tiptap/src/lib/utils/conversion/createNodeFromYElement.ts packages/y-tiptap/src/lib/utils/conversion/createNodeFromYElement.ts:45 — packages/y-tiptap/src/lib/utils/conversion/createNodeFromYElement.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in createNodeFromYElement.createNodeFromYElement at line 45. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/y-tiptap/src/lib/utils/conversion/createNodeFromYElement.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/extension-link/src/helpers/autolink.ts packages/extension-link/src/helpers/autolink.ts:52 — packages/extension-link/src/helpers/autolink.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in autolink.autolink at line 52. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/extension-link/src/helpers/autolink.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/core/src/PasteRule.ts packages/core/src/PasteRule.ts:263 — packages/core/src/PasteRule.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in PasteRule.pasteRulesPlugin.plugins at line 263. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/core/src/PasteRule.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/extension-drag-handle/src/drag-handle-plugin.ts packages/extension-drag-handle/src/drag-handle-plugin.ts:88 — packages/extension-drag-handle/src/drag-handle-plugin.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in drag-handle-plugin.DragHandlePlugin at line 88. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/extension-drag-handle/src/drag-handle-plugin.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/core/src/utilities/markdown/parseIndentedBlocks.ts packages/core/src/utilities/markdown/parseIndentedBlocks.ts:130 — packages/core/src/utilities/markdown/parseIndentedBlocks.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in parseIndentedBlocks.parseIndentedBlocks at line 130. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/core/src/utilities/markdown/parseIndentedBlocks.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/core/src/NodeView.ts packages/core/src/NodeView.ts:271 — packages/core/src/NodeView.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in NodeView.ignoreMutation at line 271. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/core/src/NodeView.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.
D15 · Churn × Complexity Hotspots · Repeated repair · ×10
  • Repeated repair: packages/core/src/Editor.ts packages/core/src/Editor.ts:178 — packages/core/src/Editor.ts changed 6 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 13 (its worst body is Editor.mount at line 178), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): clarify editor lifecycle for V4 (#8535)”; “fix(core): separate runtime options from initial settings for v4 (#8534)”; “fix(core): keep role="textbox" on the editor element after setOptions (#8410)”; “fix: rename ProseMirrorNode to PMNode and remove duplicated imports”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/core/src/Editor.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/y-tiptap/src/lib/plugins/yUndoPlugin.ts packages/y-tiptap/src/lib/plugins/yUndoPlugin.ts:49 — packages/y-tiptap/src/lib/plugins/yUndoPlugin.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 8 (its worst body is yUndoPlugin.yUndoPlugin at line 49), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(y-tiptap): remove persistent position migrations (#8694)”; “fix(collaboration): keep invalid shared content when the content check is on”; “fix(y-tiptap): keep snapshot fixes from 3.0.10”; “fix(y-tiptap): repair content that does not fit the schema again”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/y-tiptap/src/lib/plugins/yUndoPlugin.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/static-renderer/src/pm/html-string/html-string.ts packages/static-renderer/src/pm/html-string/html-string.ts:43 — packages/static-renderer/src/pm/html-string/html-string.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 15 (its worst body is html-string.domOutputSpecToHTMLString at line 43), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(static-renderer): join nested child specs without commas”; “fix(static-renderer): close audio and video specs without attributes too”; “fix(static-renderer): close audio and video tags instead of self-closing them”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/static-renderer/src/pm/html-string/html-string.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/core/src/types.ts packages/core/src/types.ts:34 — packages/core/src/types.ts 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 2 (its worst body is (anonymous) at line 34), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): separate runtime options from initial settings for v4 (#8534)”; “fix(markdown): keep task list continuations in one paragraph (#8426)”; “fix: rename ProseMirrorNode to PMNode and remove duplicated imports”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/core/src/types.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/ai-toolkit/src/hash-extension/server-ai-toolkit-hash-extension.ts packages/ai-toolkit/src/hash-extension/server-ai-toolkit-hash-extension.ts:30 — packages/ai-toolkit/src/hash-extension/server-ai-toolkit-hash-extension.ts 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 4 (its worst body is server-ai-toolkit-hash-extension.isInlineNode at line 30), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Integrate y-tiptap and fix structural relative positions (#8475)”; “fix(ai-toolkit): keep the static group check when inline needs the editor”; “fix(ai-toolkit): stop adding _hash to inline nodes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/ai-toolkit/src/hash-extension/server-ai-toolkit-hash-extension.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/core/src/InputRule.ts packages/core/src/InputRule.ts:260 — packages/core/src/InputRule.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 12 (its worst body is InputRule.inputRulesPlugin at line 260), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): preserve input rule undo with appended transactions (#8769)”; “fix(collaboration): restore input rule markers on undo (#8415)”; “fix: rename ProseMirrorNode to PMNode and remove duplicated imports”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/core/src/InputRule.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/extension-collaboration/src/collaboration.ts packages/extension-collaboration/src/collaboration.ts:254 — packages/extension-collaboration/src/collaboration.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 filterTransaction at line 254), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(collaboration): keep invalid shared content when the content check is on”; “Integrate y-tiptap and fix structural relative positions (#8475)”; “fix(collaboration): restore input rule markers on undo (#8415)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/extension-collaboration/src/collaboration.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/react/src/EditorContent.tsx packages/react/src/EditorContent.tsx:125 — packages/react/src/EditorContent.tsx 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 4 (its worst body is PureEditorContent.init at line 125), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): clarify editor lifecycle for V4 (#8535)”; “fix(core): separate runtime options from initial settings for v4 (#8534)”; “fix(react): handle mobile Enter in node views”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/react/src/EditorContent.tsx`: 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/extension-table/src/table/table.ts packages/extension-table/src/table/table.ts:376 — packages/extension-table/src/table/table.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 8 (its worst body is tokenize at line 376), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(extension-table): apply custom attributes when resizing (#8449)”; “fix: keep table CellSelection when opening the context menu”; “fix: rename ProseMirrorNode to PMNode and remove duplicated imports”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/extension-table/src/table/table.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/core/src/utilities/htmlEntities.ts packages/core/src/utilities/htmlEntities.ts:56 — packages/core/src/utilities/htmlEntities.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 htmlEntities.decodeCodePoint at line 56), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): make numeric HTML entity decoding CommonMark-conformant”; “fix(core): decode HTML entities in a single pass”; “fix(core): decode numeric HTML entities when parsing markdown”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 14:06:39 +01:00' --until='2026-11-13 14:06:39 +01:00' --full-history --no-merges -- packages/core/src/utilities/htmlEntities.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.
D29 · Static Analysis (SAST) · REDACTED · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FunctionTooLong · ×8
  • FunctionTooLong: drag-handle-plugin.DragHandlePlugin packages/extension-drag-handle/src/drag-handle-plugin.ts:88 — FunctionTooLong — DragHandlePlugin runs 254 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 154 over it, 2.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.
  • FunctionTooLong: view.createSuggestionView packages/suggestion/src/plugin/view.ts:46 — FunctionTooLong — createSuggestionView runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: PasteRule.pasteRulesPlugin packages/core/src/PasteRule.ts:200 — FunctionTooLong — pasteRulesPlugin runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: yCursorPlugin.yCursorPlugin packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts:162 — FunctionTooLong — yCursorPlugin runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: updateYFragment.updateYFragment packages/y-tiptap/src/lib/utils/reconciliation/updateYFragment.ts:19 — FunctionTooLong — updateYFragment runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ySyncPlugin.ySyncPlugin packages/y-tiptap/src/lib/plugins/ySyncPlugin.ts:14 — FunctionTooLong — ySyncPlugin runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: markdown.renderToMarkdown packages/static-renderer/src/pm/markdown/markdown.ts:18 — FunctionTooLong — renderToMarkdown runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: state.createSuggestionState packages/suggestion/src/plugin/state.ts:34 — FunctionTooLong — createSuggestionState 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×8
  • Swallowed exception (empty catch) packages/react/src/captureDOMSelection.ts:31 — 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/react/src/ReactRenderer.tsx:99 — 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/react/src/ReactRenderer.tsx:286 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:1078 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:1144 — 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/extension-node-range/src/helpers/NodeRangeSelection.ts:143 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/core/src/NodeView.ts:120 — 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/core/src/NodeView.ts:146 — 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.
D5 · Coupling · Off the main sequence · ×4
  • Off the main sequence: @tiptap/y-tiptap — @tiptap/y-tiptap: abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
  • Off the main sequence: @tiptap/core — @tiptap/core: abstractness 0.08, instability 0.02, distance 0.90 — zone of pain — concrete and depended on by 52 project(s), so it's rigid to change.
  • Off the main sequence: @tiptap/extension-text-style — @tiptap/extension-text-style: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
  • Off the main sequence: @tiptap/extension-ruby-text — @tiptap/extension-ruby-text: abstractness 0.75, instability 1.00, distance 0.75 — zone of uselessness — abstract and unstable, so it's likely unused.
R10 · Code Duplication · Duplicated block (45 lines × 2 locations) · ×4
  • Duplicated block (45 lines × 2 locations) packages/extension-table/src/cell/table-cell.ts:10 — packages/extension-table/src/cell/table-cell.ts:10 · packages/extension-table/src/header/table-header.ts:10 — 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/extension-twitch/src/twitch.ts:216 — packages/extension-twitch/src/twitch.ts:216 · packages/extension-youtube/src/youtube.ts:292 — 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.
  • Duplicated block (45 lines × 2 locations) REDACTED:1585 — REDACTED:1585 · REDACTED:1634 — both copies are in the same file, so extract the 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 (45 lines × 2 locations) packages/static-renderer/src/pm/extensionRenderer.ts:79 — packages/static-renderer/src/pm/extensionRenderer.ts:79 · packages/static-renderer/src/pm/extensionRenderer.ts:136 — 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 (24 lines × 2 locations) · ×3
  • Duplicated block (24 lines × 2 locations) packages/core/src/commands/joinItemBackward.ts:19 — packages/core/src/commands/joinItemBackward.ts:19 · packages/core/src/commands/joinItemForward.ts:19 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (24 lines × 2 locations) packages/extension-list/src/task-list/task-list.ts:91 — packages/extension-list/src/task-list/task-list.ts:91 · packages/extension-list/src/task-list/task-list.ts:138 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (24 lines × 2 locations) packages/extension-twitch/src/twitch.ts:178 — packages/extension-twitch/src/twitch.ts:178 · packages/extension-youtube/src/youtube.ts:262 — 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 (21 lines × 2 locations) · ×3
  • Duplicated block (21 lines × 2 locations) packages/core/src/decorations/Decoration.ts:89 — packages/core/src/decorations/Decoration.ts:89 · packages/core/src/decorations/Decoration.ts:118 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (21 lines × 2 locations) packages/extension-find-and-replace/src/style/create-style-tag.ts:1 — packages/extension-find-and-replace/src/style/create-style-tag.ts:1 · packages/extension-invisible-characters/src/plugin/utils/create-style-tag.ts:1 — 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 (21 lines × 2 locations) REDACTED:497 — REDACTED:497 · REDACTED:666 — 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 (19 lines × 2 locations) · ×3
  • Duplicated block (19 lines × 2 locations) packages/core/src/commands/resetAttributes.ts:27 — packages/core/src/commands/resetAttributes.ts:27 · packages/core/src/commands/updateAttributes.ts:34 — 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.
  • Duplicated block (19 lines × 2 locations) packages/core/src/inputRules/markInputRule.ts:37 — packages/core/src/inputRules/markInputRule.ts:37 · packages/core/src/pasteRules/markPasteRule.ts:37 — 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.
  • Duplicated block (19 lines × 2 locations) packages/core/src/inputRules/textInputRule.ts:12 — packages/core/src/inputRules/textInputRule.ts:12 · packages/core/src/pasteRules/textPasteRule.ts:9 — 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.
R2 · Cyclomatic Complexity · Complex function MenuBar (cyclomatic 17, cognitive 16) · ×3
  • Complex function MenuBar (cyclomatic 17, cognitive 16) demos/src/Examples/Book/React/index.jsx:27 — MenuBar has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 MenuBar (cyclomatic 17, cognitive 16) demos/src/Examples/CSSModules/React/index.jsx:27 — MenuBar has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 MenuBar (cyclomatic 17, cognitive 16) demos/src/Examples/StaticRendering/React/index.tsx:208 — MenuBar has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
R7 · Dead Code · Dead file (~162 LoC) · ×3
  • Dead file (~162 LoC) demos/src/Examples/Formatting/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~162 LoC) demos/src/Extensions/Mathematics/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~162 LoC) demos/src/Nodes/Audio/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: REDACTED REDACTED — FileTooLong — 928 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 428 over it, 1.86× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/Editor.ts packages/core/src/Editor.ts — FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: Editor (60-944). The bar is 500 significant lines; this is 9 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.
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: BubbleMenu.ts ↔ FloatingMenu.ts packages/vue/src/menus/BubbleMenu.ts:1 — `packages/vue/src/menus/BubbleMenu.ts` and `packages/vue/src/menus/FloatingMenu.ts` change together 82% of the time (14 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `f4f6be28` fix(menus): forward HTML props and auto-generate unique menu keys (#7… (at that commit the files were still `packages/vue-3/src/menus/BubbleMenu.ts` and `packages/vue-3/src/menus/FloatingMenu.ts`); `7d5ce728` fix(vue): accept Function type for appendTo prop in Menus (#7394) (at that commit the files were still `packages/vue-3/src/menus/BubbleMenu.ts` and `packages/vue-3/src/menus/FloatingMenu.ts`); `78ac8675` fix: remove unnecessary Teleport in menus and fix attribute forwardin… (at that commit the files were still `packages/vue-3/src/menus/BubbleMenu.ts` and `packages/vue-3/src/menus/FloatingMenu.ts`) — run `git show` on any of them.
  • Change coupling: clearContent.ts ↔ setContent.ts packages/core/src/commands/clearContent.ts:1 — `packages/core/src/commands/clearContent.ts` and `packages/core/src/commands/setContent.ts` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `062afaf3` refactor(core): update setContent command signature for better defaul…; `9a40c17b` fix: set correct type for emitUpdate; `f6270c0e` add more commands — run `git show` on any of them.
R10 · Code Duplication · Duplicated block (35 lines × 2 locations) · ×2
  • Duplicated block (35 lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu-plugin.ts:101 — packages/extension-bubble-menu/src/bubble-menu-plugin.ts:101 · packages/extension-floating-menu/src/floating-menu-plugin.ts:78 — the 2 copies are spread across 2 files, and the CITED SPAN is inside a TYPE DECLARATION, not executable code. There is no function to extract and no call site to call one from, so do not read this as an extract-a-helper row: the collapse a type offers is a generic — name the shape once, parameterised over the part that varies, and have each copy instantiate it. First check what actually differs between the copies: where they are a MATRIX of cases (one entry per input, differing precisely in the case each one pins), the repetition IS the enumeration and collapsing it would delete cases rather than de-duplicate anything — leave those alone. Reported because the copies that are not a matrix drift apart the first time only one of them is edited.
  • Duplicated block (35 lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu-plugin.ts:380 — packages/extension-bubble-menu/src/bubble-menu-plugin.ts:380 · packages/extension-floating-menu/src/floating-menu-plugin.ts:294 — 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 (23 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (23 matched lines × 2 locations) packages/core/src/helpers/findParentNodeClosestToPos.ts:14 — packages/core/src/helpers/findParentNodeClosestToPos.ts:14 · packages/extension-details/src/helpers/findClosestVisibleNode.ts:6 — the two spans are one implementation copied and then locally edited — 94 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 (23 matched lines × 2 locations) packages/extension-table-of-contents/src/plugin.ts:15 — packages/extension-table-of-contents/src/plugin.ts:15 · packages/extension-table-of-contents/src/tableOfContents.ts:273 — the two spans are one implementation copied and then locally edited — 128 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 (20 lines × 2 locations) · ×2
  • Duplicated block (20 lines × 2 locations) packages/core/src/Extension.ts:10 — packages/core/src/Extension.ts:10 · packages/core/src/Node.ts:338 — 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.
  • Duplicated block (20 lines × 2 locations) packages/core/src/commands/setTextDirection.ts:20 — packages/core/src/commands/setTextDirection.ts:20 · packages/core/src/commands/unsetTextDirection.ts:19 — 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.
R2 · Cyclomatic Complexity · Complex function selector (cyclomatic 23, cognitive 22) · ×2
  • Complex function selector (cyclomatic 23, cognitive 22) demos/src/Examples/StaticRendering/React/index.tsx:213 — selector has cyclomatic complexity 23 and cognitive complexity 22; 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 selector (cyclomatic 23, cognitive 22) demos/src/Experiments/IsolatingClear/React/index.jsx:32 — selector has cyclomatic complexity 23 and cognitive complexity 22; 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.
R2 · Cyclomatic Complexity · Complex function MenuBar (cyclomatic 18, cognitive 17) · ×2
  • Complex function MenuBar (cyclomatic 18, cognitive 17) demos/src/Examples/Default/React/MenuBar.tsx:7 — MenuBar has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function MenuBar (cyclomatic 18, cognitive 17) demos/src/Experiments/IsolatingClear/React/index.jsx:29 — MenuBar has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function middlewares (cyclomatic 16, cognitive 22) · ×2
  • Complex function middlewares (cyclomatic 16, cognitive 22) packages/extension-bubble-menu/src/bubble-menu-plugin.ts:225 — middlewares has cyclomatic complexity 16 and cognitive complexity 22; 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 middlewares (cyclomatic 16, cognitive 22) packages/extension-floating-menu/src/floating-menu-plugin.ts:208 — middlewares has cyclomatic complexity 16 and cognitive complexity 22; 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.
R2 · Cyclomatic Complexity · Complex function menuBarStateSelector (cyclomatic 16, cognitive 15) · ×2
  • Complex function menuBarStateSelector (cyclomatic 16, cognitive 15) demos/src/Examples/Book/React/index.jsx:9 — menuBarStateSelector has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 menuBarStateSelector (cyclomatic 16, cognitive 15) demos/src/Examples/CSSModules/React/index.jsx:9 — menuBarStateSelector has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
R7 · Dead Code · Dead file (~199 LoC) · ×2
  • Dead file (~199 LoC) demos/src/Experiments/Figure/Vue/figure.ts — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 5 in-repo import(s) from 4 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~199 LoC) demos/src/Experiments/IsolatingClear/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~169 LoC) · ×2
  • Dead file (~169 LoC) demos/src/Examples/CollaborativeEditing/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~169 LoC) demos/src/Examples/MultiMention/Vue/suggestions.js — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 5 in-repo import(s) from 4 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~160 LoC) · ×2
  • Dead file (~160 LoC) demos/src/Examples/CSSModules/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~160 LoC) demos/src/Examples/MultiMention/React/suggestions.js — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 5 in-repo import(s) from 4 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~155 LoC) · ×2
  • Dead file (~155 LoC) demos/src/Examples/CollaborativeEditing/React/MenuBar.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 5 in-repo import(s) from 4 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~155 LoC) demos/src/Examples/CollaborativeEditing/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~150 LoC) · ×2
  • Dead file (~150 LoC) demos/src/Experiments/MultipleEditors/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~150 LoC) demos/src/Extensions/Mathematics/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~146 LoC) · ×2
  • Dead file (~146 LoC) demos/src/Examples/CollaborativeEditing/Vue/MenuBar.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 5 in-repo import(s) from 4 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~146 LoC) demos/src/Extensions/FindAndReplace/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~141 LoC) · ×2
  • Dead file (~141 LoC) demos/src/Examples/Formatting/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~141 LoC) demos/src/Examples/Performance/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×2
  • Recursive walk over a caller-supplied document has no depth cap packages/y-tiptap/src/lib/utils/reconciliation/equalAttrs.ts:10 — `equalAttrs` is exported and takes `pattrs: Record<string, unknown>` from its caller, and it calls itself at line 10 (`equalAttrs`) with a piece of `pattrs` — and nowhere in `equalAttrs` 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 `equalAttrs` 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/core/src/utilities/mergeDeep.ts:12 — `mergeDeep` is exported and takes `target: Record<string, any>` from its caller, and it calls itself at line 12 (`mergeDeep`) with a piece of `target` — and nowhere in `mergeDeep` 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 `mergeDeep` 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 · ×2
  • Untrusted text written into markup unescaped packages/core/src/utilities/createStyleTag.ts:17 — `style` 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/extension-invisible-characters/src/plugin/utils/create-style-tag.ts:17 — `style` 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.
D1 · Cyclomatic Complexity · updateYFragment.updateYFragment (cyclomatic 47) · ×1
  • updateYFragment.updateYFragment (cyclomatic 47) packages/y-tiptap/src/lib/utils/reconciliation/updateYFragment.ts:19 — updateYFragment.updateYFragment has cyclomatic complexity 47 (threshold 15). Of this number, 17 points are the body's own statements and 30 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · absolutePositionToRelativePosition.absolutePositionToRelativePosition (cyclomatic 40) · ×1
  • absolutePositionToRelativePosition.absolutePositionToRelativePosition (cyclomatic 40) packages/y-tiptap/src/lib/utils/positions/absolutePositionToRelativePosition.ts:11 — absolutePositionToRelativePosition.absolutePositionToRelativePosition has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MarkdownManager.renderNodesWithMarkBoundaries (cyclomatic 39) · ×1
  • MarkdownManager.renderNodesWithMarkBoundaries (cyclomatic 39) REDACTED:1310 — MarkdownManager.renderNodesWithMarkBoundaries has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 2 of the 39 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 1322, 1565, 1385, …). 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.
D1 · Cyclomatic Complexity · splitListItem.splitListItem.<returned closure> (cyclomatic 37) · ×1
  • splitListItem.splitListItem.<returned closure> (cyclomatic 37) packages/core/src/commands/splitListItem.ts:29 — splitListItem.splitListItem.<returned closure> has cyclomatic complexity 37 (threshold 15). Of this number, 34 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · toggleList.toggleList.<returned closure> (cyclomatic 37) · ×1
  • toggleList.toggleList.<returned closure> (cyclomatic 37) packages/core/src/commands/toggleList.ts:133 — toggleList.toggleList.<returned closure> has cyclomatic complexity 37 (threshold 15). Of this number, 28 points are the body's own statements and 9 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.
D1 · Cyclomatic Complexity · insertContentAt.insertContentAt.<returned closure> (cyclomatic 35) · ×1
  • insertContentAt.insertContentAt.<returned closure> (cyclomatic 35) packages/core/src/commands/insertContentAt.ts:66 — insertContentAt.insertContentAt.<returned closure> has cyclomatic complexity 35 (threshold 15). Of this number, 29 points are the body's own statements and 6 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.
D1 · Cyclomatic Complexity · MarkdownManager.parseInlineTokens (cyclomatic 35) · ×1
  • MarkdownManager.parseInlineTokens (cyclomatic 35) REDACTED:752 — MarkdownManager.parseInlineTokens has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NodeView.stopEvent (cyclomatic 33) · ×1
  • NodeView.stopEvent (cyclomatic 33) packages/core/src/NodeView.ts:166 — NodeView.stopEvent has cyclomatic complexity 33 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · drag-handle-plugin.DragHandlePlugin (cyclomatic 33) · ×1
  • drag-handle-plugin.DragHandlePlugin (cyclomatic 33) packages/extension-drag-handle/src/drag-handle-plugin.ts:88 — drag-handle-plugin.DragHandlePlugin has cyclomatic complexity 33 (threshold 15). Of this number, 19 points are the body's own statements and 14 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.
D1 · Cyclomatic Complexity · view.createSuggestionView.update (cyclomatic 31) · ×1
  • view.createSuggestionView.update (cyclomatic 31) packages/suggestion/src/plugin/view.ts:96 — view.createSuggestionView.update has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · yCursorPlugin.yCursorPlugin (cyclomatic 30) · ×1
  • yCursorPlugin.yCursorPlugin (cyclomatic 30) packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts:162 — yCursorPlugin.yCursorPlugin has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 10 of the 30 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 268, 255, 233, …). 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.
D1 · Cyclomatic Complexity · splitBlock.splitBlock.<returned closure> (cyclomatic 29) · ×1
  • splitBlock.splitBlock.<returned closure> (cyclomatic 29) packages/core/src/commands/splitBlock.ts:35 — splitBlock.splitBlock.<returned closure> has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · findAbsolutePositionAfterStructuralChange.findAbsolutePositionAfterStructuralChange (cyclomatic 29) · ×1
  • findAbsolutePositionAfterStructuralChange.findAbsolutePositionAfterStructuralChange (cyclomatic 29) packages/y-tiptap/src/lib/utils/positions/findAbsolutePositionAfterStructuralChange.ts:6 — findAbsolutePositionAfterStructuralChange.findAbsolutePositionAfterStructuralChange has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (findByPredicate, place, a function literal at line 95, …). 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.
D1 · Cyclomatic Complexity · ySyncPlugin.ySyncPlugin (cyclomatic 28) · ×1
  • ySyncPlugin.ySyncPlugin (cyclomatic 28) packages/y-tiptap/src/lib/plugins/ySyncPlugin.ts:14 — ySyncPlugin.ySyncPlugin has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 61, 137, 84, …). 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.
D1 · Cyclomatic Complexity · updateAttributes.updateAttributes.<returned closure> (cyclomatic 27) · ×1
  • updateAttributes.updateAttributes.<returned closure> (cyclomatic 27) packages/core/src/commands/updateAttributes.ts:35 — updateAttributes.updateAttributes.<returned closure> has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 78, 58, 68, …). 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.
D1 · Cyclomatic Complexity · markdown.renderTableToMarkdown (cyclomatic 26) · ×1
  • markdown.renderTableToMarkdown (cyclomatic 26) packages/extension-table/src/table/utilities/markdown.ts:101 — markdown.renderTableToMarkdown has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 117, 158, 180, …). 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.
D1 · Cyclomatic Complexity · utils.getEmbedUrlFromYoutubeUrl (cyclomatic 26) · ×1
  • utils.getEmbedUrlFromYoutubeUrl (cyclomatic 26) packages/extension-youtube/src/utils.ts:55 — utils.getEmbedUrlFromYoutubeUrl has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MarkdownManager.parseListToken (cyclomatic 24) · ×1
  • MarkdownManager.parseListToken (cyclomatic 24) REDACTED:541 — MarkdownManager.parseListToken has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · state.createSuggestionState.apply (cyclomatic 23) · ×1
  • state.createSuggestionState.apply (cyclomatic 23) packages/suggestion/src/plugin/state.ts:65 — state.createSuggestionState.apply has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · findBestDragTarget.findBestDragTarget (cyclomatic 22) · ×1
  • findBestDragTarget.findBestDragTarget (cyclomatic 22) packages/extension-drag-handle/src/helpers/findBestDragTarget.ts:56 — findBestDragTarget.findBestDragTarget has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 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.
D1 · Cyclomatic Complexity · focus.focus.<returned closure> (cyclomatic 21) · ×1
  • focus.focus.<returned closure> (cyclomatic 21) packages/core/src/commands/focus.ts:38 — focus.focus.<returned closure> has cyclomatic complexity 21 (threshold 15). Of this number, 13 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.
D1 · Cyclomatic Complexity · createNodeFromYElement.createNodeFromYElement (cyclomatic 20) · ×1
  • createNodeFromYElement.createNodeFromYElement (cyclomatic 20) packages/y-tiptap/src/lib/utils/conversion/createNodeFromYElement.ts:45 — createNodeFromYElement.createNodeFromYElement has cyclomatic complexity 20 (threshold 15). Of this number, 13 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · ProsemirrorBinding._renderSnapshot (cyclomatic 20) · ×1
  • ProsemirrorBinding._renderSnapshot (cyclomatic 20) packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts:264 — ProsemirrorBinding._renderSnapshot has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 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.
D1 · Cyclomatic Complexity · autolink.autolink (cyclomatic 19) · ×1
  • autolink.autolink (cyclomatic 19) packages/extension-link/src/helpers/autolink.ts:52 — autolink.autolink 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 5 function literals inside it that branch (lines 103, 55, 82, …). 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.
D1 · Cyclomatic Complexity · PasteRule.pasteRulesPlugin.plugins (cyclomatic 18) · ×1
  • PasteRule.pasteRulesPlugin.plugins (cyclomatic 18) packages/core/src/PasteRule.ts:263 — PasteRule.pasteRulesPlugin.plugins has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 336, handleDragstart, a function literal at line 296, …). 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.
D1 · Cyclomatic Complexity · rewriteUnknownContent.rewriteUnknownContentInner (cyclomatic 17) · ×1
  • rewriteUnknownContent.rewriteUnknownContentInner (cyclomatic 17) packages/core/src/helpers/rewriteUnknownContent.ts:27 — rewriteUnknownContent.rewriteUnknownContentInner has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 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.
D1 · Cyclomatic Complexity · wrappingInputRule.wrappingInputRule (cyclomatic 17) · ×1
  • wrappingInputRule.wrappingInputRule (cyclomatic 17) packages/core/src/inputRules/wrappingInputRule.ts:25 — wrappingInputRule.wrappingInputRule has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 41). 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.
D1 · Cyclomatic Complexity · parseIndentedBlocks.parseIndentedBlocks (cyclomatic 17) · ×1
  • parseIndentedBlocks.parseIndentedBlocks (cyclomatic 17) packages/core/src/utilities/markdown/parseIndentedBlocks.ts:130 — parseIndentedBlocks.parseIndentedBlocks has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · createNodeFromContent.createNodeFromContent (cyclomatic 16) · ×1
  • createNodeFromContent.createNodeFromContent (cyclomatic 16) packages/core/src/helpers/createNodeFromContent.ts:21 — createNodeFromContent.createNodeFromContent 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.
D1 · Cyclomatic Complexity · NodeView.ignoreMutation (cyclomatic 16) · ×1
  • NodeView.ignoreMutation (cyclomatic 16) packages/core/src/NodeView.ts:271 — NodeView.ignoreMutation has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · BubbleMenuView.middlewares (cyclomatic 16) · ×1
  • BubbleMenuView.middlewares (cyclomatic 16) packages/extension-bubble-menu/src/bubble-menu-plugin.ts:225 — BubbleMenuView.middlewares has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FloatingMenuView.middlewares (cyclomatic 16) · ×1
  • FloatingMenuView.middlewares (cyclomatic 16) packages/extension-floating-menu/src/floating-menu-plugin.ts:208 — FloatingMenuView.middlewares has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TableView.updateColumns (cyclomatic 16) · ×1
  • TableView.updateColumns (cyclomatic 16) packages/extension-table/src/table/TableView.ts:6 — TableView.updateColumns has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · react.domOutputSpecToReactElement (cyclomatic 16) · ×1
  • react.domOutputSpecToReactElement (cyclomatic 16) packages/static-renderer/src/pm/react/react.ts:64 — react.domOutputSpecToReactElement has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · findSuggestionMatch.findSuggestionMatch (cyclomatic 16) · ×1
  • findSuggestionMatch.findSuggestionMatch (cyclomatic 16) REDACTED:20 — findSuggestionMatch.findSuggestionMatch has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ProsemirrorBinding._isDomSelectionInView (cyclomatic 16) · ×1
  • ProsemirrorBinding._isDomSelectionInView (cyclomatic 16) packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts:127 — ProsemirrorBinding._isDomSelectionInView has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · absolutePositionToRelativePosition.absolutePositionToRelativePosition (cognitive 103) · ×1
  • absolutePositionToRelativePosition.absolutePositionToRelativePosition (cognitive 103) packages/y-tiptap/src/lib/utils/positions/absolutePositionToRelativePosition.ts:11 — absolutePositionToRelativePosition.absolutePositionToRelativePosition has cognitive complexity 103 (threshold 15). Drivers by points: if/else 20 (58 pts), ternaries 5 (25 pts), boolean chains 10, loops 3 (10 pts) (nesting depth added 65). 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.
D2 · Cognitive Complexity · MarkdownManager.parseInlineTokens (cognitive 73) · ×1
  • MarkdownManager.parseInlineTokens (cognitive 73) REDACTED:752 — MarkdownManager.parseInlineTokens has cognitive complexity 73 (threshold 15). Drivers by points: if/else 21 (57 pts), boolean chains 10, loops 3 (6 pts) (nesting depth added 39). 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.
D2 · Cognitive Complexity · MarkdownManager.renderNodesWithMarkBoundaries (cognitive 72) · ×1
  • MarkdownManager.renderNodesWithMarkBoundaries (cognitive 72) REDACTED:1310 — MarkdownManager.renderNodesWithMarkBoundaries has cognitive complexity 72 (threshold 15). Drivers by points: if/else 26 (56 pts), boolean chains 11, ternaries 3 (5 pts) (nesting depth added 32). Most of this is not in the body itself: 1 of the 72 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 1322, 1565, 1385, …). 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.
D2 · Cognitive Complexity · toggleList.toggleList.<returned closure> (cognitive 63) · ×1
  • toggleList.toggleList.<returned closure> (cognitive 63) packages/core/src/commands/toggleList.ts:133 — toggleList.toggleList.<returned closure> has cognitive complexity 63 (threshold 15). Drivers by points: if/else 15 (39 pts), boolean chains 14, ternaries 3 (6 pts), error handling 1 (4 pts) (nesting depth added 30). Of this number, 37 points are the body's own statements and 26 belong to 4 function literals 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.
D2 · Cognitive Complexity · updateYFragment.updateYFragment (cognitive 60) · ×1
  • updateYFragment.updateYFragment (cognitive 60) packages/y-tiptap/src/lib/utils/reconciliation/updateYFragment.ts:19 — updateYFragment.updateYFragment has cognitive complexity 60 (threshold 15). Drivers by points: if/else 22 (40 pts), boolean chains 12, loops 6 (8 pts) (nesting depth added 20). Of this number, 28 points are the body's own statements and 32 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · splitListItem.splitListItem.<returned closure> (cognitive 56) · ×1
  • splitListItem.splitListItem.<returned closure> (cognitive 56) packages/core/src/commands/splitListItem.ts:29 — splitListItem.splitListItem.<returned closure> has cognitive complexity 56 (threshold 15). Drivers by points: if/else 12 (22 pts), ternaries 10 (20 pts), boolean chains 11, loops 1 (3 pts) (nesting depth added 22). Of this number, 49 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MarkdownManager.parseListToken (cognitive 52) · ×1
  • MarkdownManager.parseListToken (cognitive 52) REDACTED:541 — MarkdownManager.parseListToken has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (41 pts), ternaries 3 (6 pts), boolean chains 3, loops 2 (nesting depth added 29). Of this number, 46 points are the body's own statements and 6 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.
D2 · Cognitive Complexity · updateAttributes.updateAttributes.<returned closure> (cognitive 47) · ×1
  • updateAttributes.updateAttributes.<returned closure> (cognitive 47) packages/core/src/commands/updateAttributes.ts:35 — updateAttributes.updateAttributes.<returned closure> has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (38 pts), boolean chains 8, ternaries 1 (nesting depth added 21). Most of this is not in the body itself: 4 of the 47 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 78, 58, 100, …). 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.
D2 · Cognitive Complexity · insertContentAt.insertContentAt.<returned closure> (cognitive 46) · ×1
  • insertContentAt.insertContentAt.<returned closure> (cognitive 46) packages/core/src/commands/insertContentAt.ts:66 — insertContentAt.insertContentAt.<returned closure> has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 9, error handling 2 (5 pts), ternaries 2 (4 pts) (nesting depth added 18). Of this number, 42 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · parseIndentedBlocks.parseIndentedBlocks (cognitive 40) · ×1
  • parseIndentedBlocks.parseIndentedBlocks (cognitive 40) packages/core/src/utilities/markdown/parseIndentedBlocks.ts:130 — parseIndentedBlocks.parseIndentedBlocks has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (34 pts), boolean chains 3, loops 2 (3 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.
D2 · Cognitive Complexity · react.domOutputSpecToReactElement (cognitive 37) · ×1
  • react.domOutputSpecToReactElement (cognitive 37) packages/static-renderer/src/pm/react/react.ts:64 — react.domOutputSpecToReactElement has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (36 pts), boolean chains 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.
D2 · Cognitive Complexity · splitBlock.splitBlock.<returned closure> (cognitive 36) · ×1
  • splitBlock.splitBlock.<returned closure> (cognitive 36) packages/core/src/commands/splitBlock.ts:35 — splitBlock.splitBlock.<returned closure> has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 6, ternaries 5 (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.
D2 · Cognitive Complexity · TableView.updateColumns (cognitive 35) · ×1
  • TableView.updateColumns (cognitive 35) packages/extension-table/src/table/TableView.ts:6 — TableView.updateColumns has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 2 (8 pts), loops 3 (6 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · html-string.domOutputSpecToHTMLString (cognitive 35) · ×1
  • html-string.domOutputSpecToHTMLString (cognitive 35) packages/static-renderer/src/pm/html-string/html-string.ts:43 — html-string.domOutputSpecToHTMLString has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (34 pts), boolean chains 1 (nesting depth added 21). 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.
D2 · Cognitive Complexity · view.createSuggestionView.update (cognitive 34) · ×1
  • view.createSuggestionView.update (cognitive 34) packages/suggestion/src/plugin/view.ts:96 — view.createSuggestionView.update has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 13, 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.
D2 · Cognitive Complexity · findAbsolutePositionAfterStructuralChange.findAbsolutePositionAfterStructuralChange (cognitive 33) · ×1
  • findAbsolutePositionAfterStructuralChange.findAbsolutePositionAfterStructuralChange (cognitive 33) packages/y-tiptap/src/lib/utils/positions/findAbsolutePositionAfterStructuralChange.ts:6 — findAbsolutePositionAfterStructuralChange.findAbsolutePositionAfterStructuralChange has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 9, loops 3, ternaries 1 (2 pts) (nesting depth added 7). Most of this is not in the body itself: 10 of the 33 points are its own statements and the rest belongs to 6 function items inside it that branch (findByPredicate, place, a function literal at line 95, …). 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.
D2 · Cognitive Complexity · drag-handle-plugin.DragHandlePlugin (cognitive 32) · ×1
  • drag-handle-plugin.DragHandlePlugin (cognitive 32) packages/extension-drag-handle/src/drag-handle-plugin.ts:88 — drag-handle-plugin.DragHandlePlugin has cognitive complexity 32 (threshold 15). Drivers by points: if/else 21 (26 pts), boolean chains 5, ternaries 1 (nesting depth added 5). Of this number, 23 points are the body's own statements and 9 belong to 2 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.
D2 · Cognitive Complexity · yCursorPlugin.yCursorPlugin (cognitive 31) · ×1
  • yCursorPlugin.yCursorPlugin (cognitive 31) packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts:162 — yCursorPlugin.yCursorPlugin has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 9, ternaries 2 (3 pts) (nesting depth added 3). Most of this is not in the body itself: 8 of the 31 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 268, 255, 233, …). 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.
D2 · Cognitive Complexity · state.createSuggestionState.apply (cognitive 30) · ×1
  • state.createSuggestionState.apply (cognitive 30) packages/suggestion/src/plugin/state.ts:65 — state.createSuggestionState.apply has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 10 (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.
D2 · Cognitive Complexity · ySyncPlugin.ySyncPlugin (cognitive 30) · ×1
  • ySyncPlugin.ySyncPlugin (cognitive 30) packages/y-tiptap/src/lib/plugins/ySyncPlugin.ts:14 — ySyncPlugin.ySyncPlugin has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 10 (nesting depth added 7). None of this is in the body itself: all 30 points belong to 7 function literals inside it that branch (lines 137, 61, 84, …). 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.
D2 · Cognitive Complexity · findBestDragTarget.findBestDragTarget (cognitive 28) · ×1
  • findBestDragTarget.findBestDragTarget (cognitive 28) packages/extension-drag-handle/src/helpers/findBestDragTarget.ts:56 — findBestDragTarget.findBestDragTarget has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 3, ternaries 3 (nesting depth added 8). Of this number, 19 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · createNodeFromContent.createNodeFromContent (cognitive 26) · ×1
  • createNodeFromContent.createNodeFromContent (cognitive 26) packages/core/src/helpers/createNodeFromContent.ts:21 — createNodeFromContent.createNodeFromContent has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 3, error handling 1 (2 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.
D2 · Cognitive Complexity · autolink.autolink (cognitive 26) · ×1
  • autolink.autolink (cognitive 26) packages/extension-link/src/helpers/autolink.ts:52 — autolink.autolink has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 4 (nesting depth added 8). None of this is in the body itself: all 26 points belong to 5 function literals inside it that branch (lines 103, 55, 82, …). 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.
D2 · Cognitive Complexity · isStructuralTransaction.isStructuralTransaction (cognitive 26) · ×1
  • isStructuralTransaction.isStructuralTransaction (cognitive 26) packages/y-tiptap/src/lib/utils/positions/isStructuralTransaction.ts:6 — isStructuralTransaction.isStructuralTransaction has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 2, loops 1 (nesting depth added 14). Of this number, 22 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · restoreRelativeSelection.restoreRelativeSelection (cognitive 26) · ×1
  • restoreRelativeSelection.restoreRelativeSelection (cognitive 26) packages/y-tiptap/src/lib/utils/positions/restoreRelativeSelection.ts:29 — restoreRelativeSelection.restoreRelativeSelection has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (24 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.
D2 · Cognitive Complexity · ProsemirrorBinding._renderSnapshot (cognitive 26) · ×1
  • ProsemirrorBinding._renderSnapshot (cognitive 26) packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts:264 — ProsemirrorBinding._renderSnapshot has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 4 (7 pts), boolean chains 5 (nesting depth added 7). Of this number, 13 points are the body's own statements and 13 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · utils.getEmbedUrlFromYoutubeUrl (cognitive 25) · ×1
  • utils.getEmbedUrlFromYoutubeUrl (cognitive 25) packages/extension-youtube/src/utils.ts:55 — utils.getEmbedUrlFromYoutubeUrl has cognitive complexity 25 (threshold 15). Drivers by points: if/else 23 (24 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · markdown.renderTableToMarkdown (cognitive 24) · ×1
  • markdown.renderTableToMarkdown (cognitive 24) packages/extension-table/src/table/utilities/markdown.ts:101 — markdown.renderTableToMarkdown has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 8, loops 2, ternaries 2 (nesting depth added 4). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 158, 180, 117, …). 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.
D2 · Cognitive Complexity · createNodeFromYElement.createNodeFromYElement (cognitive 24) · ×1
  • createNodeFromYElement.createNodeFromYElement (cognitive 24) packages/y-tiptap/src/lib/utils/conversion/createNodeFromYElement.ts:45 — createNodeFromYElement.createNodeFromYElement has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 4, ternaries 2, error handling 1 (nesting depth added 3). Of this number, 14 points are the body's own statements and 10 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · vue-sfc-imports.replacePackageSpecifiers (cognitive 23) · ×1
  • vue-sfc-imports.replacePackageSpecifiers (cognitive 23) codemods/tiptap-v4-migration/scripts/vue-sfc-imports.mjs:142 — vue-sfc-imports.replacePackageSpecifiers has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 3 (9 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · markdown.escapeTableCellPipes (cognitive 23) · ×1
  • markdown.escapeTableCellPipes (cognitive 23) packages/extension-table/src/table/utilities/markdown.ts:18 — markdown.escapeTableCellPipes 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.
D2 · Cognitive Complexity · utils.getEmbedUrlFromTwitchUrl (cognitive 23) · ×1
  • utils.getEmbedUrlFromTwitchUrl (cognitive 23) packages/extension-twitch/src/utils.ts:147 — utils.getEmbedUrlFromTwitchUrl has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (22 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.
D2 · Cognitive Complexity · mergeAttributes.splitStyleDeclarations (cognitive 22) · ×1
  • mergeAttributes.splitStyleDeclarations (cognitive 22) packages/core/src/utilities/mergeAttributes.ts:2 — mergeAttributes.splitStyleDeclarations has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 5, 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.
D2 · Cognitive Complexity · BubbleMenuView.middlewares (cognitive 22) · ×1
  • BubbleMenuView.middlewares (cognitive 22) packages/extension-bubble-menu/src/bubble-menu-plugin.ts:225 — BubbleMenuView.middlewares has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 8 (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.
D2 · Cognitive Complexity · FloatingMenuView.middlewares (cognitive 22) · ×1
  • FloatingMenuView.middlewares (cognitive 22) packages/extension-floating-menu/src/floating-menu-plugin.ts:208 — FloatingMenuView.middlewares has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 8 (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.
D2 · Cognitive Complexity · utils.collectOrderedListItems (cognitive 22) · ×1
  • utils.collectOrderedListItems (cognitive 22) packages/extension-list/src/ordered-list/utils.ts:144 — utils.collectOrderedListItems has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 2 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · focus.focus.<returned closure> (cognitive 21) · ×1
  • focus.focus.<returned closure> (cognitive 21) packages/core/src/commands/focus.ts:38 — focus.focus.<returned closure> has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 8, error handling 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · NodeView.stopEvent (cognitive 21) · ×1
  • NodeView.stopEvent (cognitive 21) packages/core/src/NodeView.ts:166 — NodeView.stopEvent has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 11, if/else 9 (10 pts) (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.
D2 · Cognitive Complexity · PasteRule.pasteRulesPlugin.plugins (cognitive 21) · ×1
  • PasteRule.pasteRulesPlugin.plugins (cognitive 21) packages/core/src/PasteRule.ts:263 — PasteRule.pasteRulesPlugin.plugins has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 4 (nesting depth added 6). None of this is in the body itself: all 21 points belong to 5 function items inside it that branch (a function literal at line 336, a function literal at line 296, a function literal at line 305, …). 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.
D2 · Cognitive Complexity · findNextElementFromCursor.findElementNextToCoords (cognitive 21) · ×1
  • findNextElementFromCursor.findElementNextToCoords (cognitive 21) packages/extension-drag-handle/src/helpers/findNextElementFromCursor.ts:149 — findNextElementFromCursor.findElementNextToCoords has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 2 (7 pts), error handling 1 (nesting depth added 9). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · clearNodes.clearNodes.<returned closure> (cognitive 19) · ×1
  • clearNodes.clearNodes.<returned closure> (cognitive 19) packages/core/src/commands/clearNodes.ts:19 — clearNodes.clearNodes.<returned closure> has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 2, loops 1 (nesting depth added 8). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 59, 31). 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.
D2 · Cognitive Complexity · BubbleMenuView.virtualElement (cognitive 19) · ×1
  • BubbleMenuView.virtualElement (cognitive 19) packages/extension-bubble-menu/src/bubble-menu-plugin.ts:305 — BubbleMenuView.virtualElement has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 4 (8 pts), boolean chains 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.
D2 · Cognitive Complexity · keyboardShortcut.normalizeKeyName (cognitive 18) · ×1
  • keyboardShortcut.normalizeKeyName (cognitive 18) packages/core/src/commands/keyboardShortcut.ts:5 — keyboardShortcut.normalizeKeyName has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 1, loops 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.
D2 · Cognitive Complexity · ExtensionManager.plugins (cognitive 18) · ×1
  • ExtensionManager.plugins (cognitive 18) packages/core/src/ExtensionManager.ts:104 — ExtensionManager.plugins has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, ternaries 1 (3 pts) (nesting depth added 4). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to one function literal inside it that branches (line 114). 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.
D2 · Cognitive Complexity · renderNestedMarkdownContent.renderNestedMarkdownContent (cognitive 17) · ×1
  • renderNestedMarkdownContent.renderNestedMarkdownContent (cognitive 17) packages/core/src/utilities/markdown/renderNestedMarkdownContent.ts:76 — renderNestedMarkdownContent.renderNestedMarkdownContent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 4 (7 pts), boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 114, 107, 118, …). 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.
D2 · Cognitive Complexity · NodePos.closest (cognitive 17) · ×1
  • NodePos.closest (cognitive 17) packages/core/src/NodePos.ts:185 — NodePos.closest has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · utils.buildNestedStructure (cognitive 17) · ×1
  • utils.buildNestedStructure (cognitive 17) packages/extension-list/src/ordered-list/utils.ts:283 — utils.buildNestedStructure has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 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.
D2 · Cognitive Complexity · markdown.renderToMarkdown (cognitive 17) · ×1
  • markdown.renderToMarkdown (cognitive 17) packages/static-renderer/src/pm/markdown/markdown.ts:18 — markdown.renderToMarkdown has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, loops 1 (nesting depth added 2). Of this number, 14 points are the body's own statements and 3 belong to 2 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.
D2 · Cognitive Complexity · yCursorPlugin.createDecorations (cognitive 17) · ×1
  • yCursorPlugin.createDecorations (cognitive 17) packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts:64 — yCursorPlugin.createDecorations has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4 (nesting depth added 4). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 84). 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.
D2 · Cognitive Complexity · undoInputRule.undoInputRule.<returned closure> (cognitive 16) · ×1
  • undoInputRule.undoInputRule.<returned closure> (cognitive 16) packages/core/src/commands/undoInputRule.ts:17 — undoInputRule.undoInputRule.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (5 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.
D2 · Cognitive Complexity · wrappingInputRule.wrappingInputRule (cognitive 16) · ×1
  • wrappingInputRule.wrappingInputRule (cognitive 16) packages/core/src/inputRules/wrappingInputRule.ts:25 — wrappingInputRule.wrappingInputRule has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (6 pts), ternaries 1 (2 pts) (nesting depth added 2). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 41). 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.
D2 · Cognitive Complexity · relativePositionToAbsolutePosition.relativePositionToAbsolutePosition (cognitive 16) · ×1
  • relativePositionToAbsolutePosition.relativePositionToAbsolutePosition (cognitive 16) packages/y-tiptap/src/lib/utils/positions/relativePositionToAbsolutePosition.ts:9 — relativePositionToAbsolutePosition.relativePositionToAbsolutePosition has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · setMeta.updateMetas (cognitive 16) · ×1
  • setMeta.updateMetas (cognitive 16) packages/y-tiptap/src/lib/plugins/setMeta.ts:19 — setMeta.updateMetas has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 2, error handling 1 (2 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.
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: MarkdownManager REDACTED:39 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: Editor packages/core/src/Editor.ts:60 — ClassTooLong — 457 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 57 over it, 1.14× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: table-cell.ts → table-header.ts, table-row.ts, table.ts packages/extension-table/src/cell/table-cell.ts — `packages/extension-table/src/cell/table-cell.ts` changes together with 3 other files — `packages/extension-table/src/header/table-header.ts`, `packages/extension-table/src/row/table-row.ts`, `packages/extension-table/src/table/table.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.
D35 · Change Coupling · Change coupling clique · ×1
  • Change coupling clique: Extension.ts, Mark.ts, Node.ts packages/core/src/Extension.ts — 3 files — `packages/core/src/Extension.ts`, `packages/core/src/Mark.ts`, `packages/core/src/Node.ts` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Guard cannot change the result · ×1
  • Guard cannot change the result — returns what the code already falls through to packages/react/src/menus/useMenuElementProps.ts:106 — The guard above `return key;` also returns `key`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
R10 · Code Duplication · Duplication concentrated across 37 sibling directories (47 clone groups) · ×1
  • Duplication concentrated across 37 sibling directories (47 clone groups) packages/react/src/ReactNodeViewRenderer.tsx:142 — 47 duplicated blocks under packages/ have copies in at least two of the sibling directories core, extension-audio, extension-blockquote, extension-bold, extension-bubble-menu, extension-code (+31 more sibling(s) not listed) — 35 of them are reported below, and 12 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 47 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 47 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 47 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.
R10 · Code Duplication · Duplicated block with local edits (163 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (163 matched lines × 2 locations) packages/extension-mathematics/src/extensions/BlockMath.ts:8 — packages/extension-mathematics/src/extensions/BlockMath.ts:8 · packages/extension-mathematics/src/extensions/InlineMath.ts:9 — the two spans are one implementation copied and then locally edited — 805 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 (126 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (126 matched lines × 2 locations) packages/core/src/Mark.ts:8 — packages/core/src/Mark.ts:8 · packages/core/src/Node.ts:8 — the two spans are one implementation copied and then locally edited — 650 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 (103 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (103 matched lines × 2 locations) packages/react/src/ReactNodeViewRenderer.tsx:142 — packages/react/src/ReactNodeViewRenderer.tsx:142 · packages/vue/src/VueNodeViewRenderer.ts:118 — the two spans are one implementation copied and then locally edited — 543 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 (87 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (87 matched lines × 2 locations) packages/extension-bold/src/bold.tsx:4 — packages/extension-bold/src/bold.tsx:4 · packages/extension-italic/src/italic.ts:3 — the two spans are one implementation copied and then locally edited — 355 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 (86 lines × 2 locations) · ×1
  • Duplicated block (86 lines × 2 locations) packages/react/src/menus/BubbleMenu.tsx:27 — packages/react/src/menus/BubbleMenu.tsx:27 · packages/react/src/menus/FloatingMenu.tsx:29 — 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 (80 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (80 matched lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu-plugin.ts:555 — packages/extension-bubble-menu/src/bubble-menu-plugin.ts:555 · packages/extension-floating-menu/src/floating-menu-plugin.ts:333 — the two spans are one implementation copied and then locally edited — 463 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 (63 lines × 2 locations) · ×1
  • Duplicated block (63 lines × 2 locations) packages/extension-subscript/src/subscript.ts:4 — packages/extension-subscript/src/subscript.ts:4 · packages/extension-superscript/src/superscript.ts:4 — 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.
R10 · Code Duplication · Duplicated block (62 lines × 2 locations) · ×1
  • Duplicated block (62 lines × 2 locations) packages/extension-text-style/src/background-color/background-color.ts:5 — packages/extension-text-style/src/background-color/background-color.ts:5 · packages/extension-text-style/src/color/color.ts:5 — 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.
R10 · Code Duplication · Duplicated block with local edits (44 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (44 matched lines × 2 locations) packages/core/src/helpers/getSchemaSpecByResolvedExtensions.ts:68 — packages/core/src/helpers/getSchemaSpecByResolvedExtensions.ts:68 · packages/core/src/helpers/getSchemaSpecByResolvedExtensions.ts:166 — the two spans are one implementation copied and then locally edited — 293 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 (36 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (36 matched lines × 2 locations) REDACTED:67 — REDACTED:67 · REDACTED:70 — the two spans are one implementation copied and then locally edited — 197 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 (36 lines × 3 locations) · ×1
  • Duplicated block (36 lines × 3 locations) packages/extension-text-style/src/font-family/font-family.ts:52 — packages/extension-text-style/src/font-family/font-family.ts:52 · packages/extension-text-style/src/font-size/font-size.ts:52 · packages/extension-text-style/src/line-height/line-height.ts:52 — the 3 copies are spread across 3 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.
R10 · Code Duplication · Duplicated block (31 lines × 2 locations) · ×1
  • Duplicated block (31 lines × 2 locations) packages/extension-highlight/src/highlight.ts:158 — packages/extension-highlight/src/highlight.ts:158 · packages/extension-strike/src/strike.ts:101 — 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 (28 lines × 2 locations) · ×1
  • Duplicated block (28 lines × 2 locations) packages/extension-table/src/table/table.ts:440 — packages/extension-table/src/table/table.ts:440 · packages/extension-table/src/table/table.ts:470 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×1
  • Duplicated block (26 lines × 2 locations) packages/core/src/MarkView.ts:100 — packages/core/src/MarkView.ts:100 · packages/core/src/NodeView.ts:290 — 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 (26 lines × 3 locations) · ×1
  • Duplicated block (26 lines × 3 locations) packages/extension-code/src/code.ts:167 — packages/extension-code/src/code.ts:167 · packages/extension-highlight/src/highlight.ts:158 · packages/extension-strike/src/strike.ts:101 — the 3 copies are spread across 3 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 (23 lines × 2 locations) · ×1
  • Duplicated block (23 lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu-plugin.ts:248 — packages/extension-bubble-menu/src/bubble-menu-plugin.ts:248 · packages/extension-floating-menu/src/floating-menu-plugin.ts:231 — 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 (20 lines × 3 locations) · ×1
  • Duplicated block (20 lines × 3 locations) packages/extension-audio/src/audio.ts:200 — packages/extension-audio/src/audio.ts:200 · packages/extension-twitch/src/twitch.ts:234 · packages/extension-youtube/src/youtube.ts:310 — 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 (19 lines × 7 locations) · ×1
  • Duplicated block (19 lines × 7 locations) packages/extension-blockquote/src/blockquote.tsx:108 — packages/extension-blockquote/src/blockquote.tsx:108 · packages/extension-bold/src/bold.tsx:111 · packages/extension-code/src/code.ts:157 · packages/extension-strike/src/strike.ts:91 · +3 more site(s) not listed — the 7 copies are spread across 7 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.
R10 · Code Duplication · Duplicated block (19 lines × 3 locations) · ×1
  • Duplicated block (19 lines × 3 locations) packages/extension-italic/src/italic.ts:90 — packages/extension-italic/src/italic.ts:90 · packages/extension-subscript/src/subscript.ts:72 · packages/extension-superscript/src/superscript.ts:72 — the 3 copies are spread across 3 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.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×1
  • Duplicated block (18 lines × 2 locations) packages/extension-bubble-menu/src/bubble-menu.ts:32 — packages/extension-bubble-menu/src/bubble-menu.ts:32 · packages/extension-floating-menu/src/floating-menu.ts:59 — 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.
R11 · Import Boundaries · Boundary violation [package · ×1
  • Boundary violation [package:third-party-deep-import] packages/extension-code-block-lowlight/src/lowlight-plugin.ts:6 — packages/extension-code-block-lowlight/src/lowlight-plugin.ts:6 imports highlight.js/lib/core, 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.
R2 · Cyclomatic Complexity · Complex function absolutePositionToRelativePosition (cyclomatic 42, cognitive 128) · ×1
  • Complex function absolutePositionToRelativePosition (cyclomatic 42, cognitive 128) packages/y-tiptap/src/lib/utils/positions/absolutePositionToRelativePosition.ts:11 — absolutePositionToRelativePosition has cyclomatic complexity 42 and cognitive complexity 128; 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.
R2 · Cyclomatic Complexity · Complex function parseInlineTokens (cyclomatic 39, cognitive 74) · ×1
  • Complex function parseInlineTokens (cyclomatic 39, cognitive 74) REDACTED:752 — parseInlineTokens has cyclomatic complexity 39 and cognitive complexity 74; 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.
R2 · Cyclomatic Complexity · Complex function update (cyclomatic 36, cognitive 43) · ×1
  • Complex function update (cyclomatic 36, cognitive 43) packages/suggestion/src/plugin/view.ts:96 — update has cyclomatic complexity 36 and cognitive complexity 43; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 34, cognitive 47) · ×1
  • Complex function (anonymous) (cyclomatic 34, cognitive 47) packages/core/src/commands/splitListItem.ts:29 — (anonymous) has cyclomatic complexity 34 and cognitive complexity 47; 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.
R2 · Cyclomatic Complexity · Complex function stopEvent (cyclomatic 33, cognitive 21) · ×1
  • Complex function stopEvent (cyclomatic 33, cognitive 21) packages/core/src/NodeView.ts:166 — stopEvent has cyclomatic complexity 33 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 31, cognitive 36) · ×1
  • Complex function (anonymous) (cyclomatic 31, cognitive 36) packages/y-tiptap/src/lib/utils/reconciliation/updateYFragment.ts:109 — (anonymous) has cyclomatic complexity 31 and cognitive complexity 36; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 29, cognitive 42) · ×1
  • Complex function (anonymous) (cyclomatic 29, cognitive 42) packages/core/src/commands/insertContentAt.ts:66 — (anonymous) has cyclomatic complexity 29 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 29, cognitive 40) · ×1
  • Complex function (anonymous) (cyclomatic 29, cognitive 40) packages/core/src/commands/splitBlock.ts:35 — (anonymous) has cyclomatic complexity 29 and cognitive complexity 40; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 29, cognitive 38) · ×1
  • Complex function (anonymous) (cyclomatic 29, cognitive 38) packages/core/src/commands/toggleList.ts:133 — (anonymous) has cyclomatic complexity 29 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 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.
R2 · Cyclomatic Complexity · Complex function addInputRules (cyclomatic 27, cognitive 32) · ×1
  • Complex function addInputRules (cyclomatic 27, cognitive 32) packages/extension-typography/src/typography.ts:345 — addInputRules has cyclomatic complexity 27 and cognitive complexity 32; 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.
R2 · Cyclomatic Complexity · Complex function getEmbedUrlFromYoutubeUrl (cyclomatic 26, cognitive 27) · ×1
  • Complex function getEmbedUrlFromYoutubeUrl (cyclomatic 26, cognitive 27) packages/extension-youtube/src/utils.ts:55 — getEmbedUrlFromYoutubeUrl has cyclomatic complexity 26 and cognitive complexity 27; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 24, cognitive 41) · ×1
  • Complex function (anonymous) (cyclomatic 24, cognitive 41) REDACTED:1322 — (anonymous) has cyclomatic complexity 24 and cognitive complexity 41; 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.
R2 · Cyclomatic Complexity · Complex function menuBarStateSelector (cyclomatic 24, cognitive 23) · ×1
  • Complex function menuBarStateSelector (cyclomatic 24, cognitive 23) demos/src/Examples/Default/React/menuBarState.ts:8 — menuBarStateSelector has cyclomatic complexity 24 and cognitive complexity 23; 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.
R2 · Cyclomatic Complexity · Complex function apply (cyclomatic 23, cognitive 33) · ×1
  • Complex function apply (cyclomatic 23, cognitive 33) packages/suggestion/src/plugin/state.ts:65 — apply has cyclomatic complexity 23 and cognitive complexity 33; 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.
R2 · Cyclomatic Complexity · Complex function addExtensions (cyclomatic 23, cognitive 22) · ×1
  • Complex function addExtensions (cyclomatic 23, cognitive 22) packages/starter-kit/src/starter-kit.ts:180 — addExtensions has cyclomatic complexity 23 and cognitive complexity 22; 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.
R2 · Cyclomatic Complexity · Complex function selector (cyclomatic 18, cognitive 17) · ×1
  • Complex function selector (cyclomatic 18, cognitive 17) demos/src/Examples/Tables/React/index.jsx:57 — selector has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function parseIndentedBlocks (cyclomatic 17, cognitive 40) · ×1
  • Complex function parseIndentedBlocks (cyclomatic 17, cognitive 40) packages/core/src/utilities/markdown/parseIndentedBlocks.ts:130 — parseIndentedBlocks has cyclomatic complexity 17 and cognitive complexity 40; 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.
R2 · Cyclomatic Complexity · Complex function updateYFragment (cyclomatic 17, cognitive 28) · ×1
  • Complex function updateYFragment (cyclomatic 17, cognitive 28) packages/y-tiptap/src/lib/utils/reconciliation/updateYFragment.ts:19 — updateYFragment has cyclomatic complexity 17 and cognitive complexity 28; 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.
R2 · Cyclomatic Complexity · Complex function handleKeyDown (cyclomatic 17, cognitive 19) · ×1
  • Complex function handleKeyDown (cyclomatic 17, cognitive 19) packages/extension-emoji/src/emoji.ts:395 — handleKeyDown has cyclomatic complexity 17 and cognitive complexity 19; 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.
R2 · Cyclomatic Complexity · Complex function handler (cyclomatic 17, cognitive 17) · ×1
  • Complex function handler (cyclomatic 17, cognitive 17) packages/core/src/inputRules/wrappingInputRule.ts:41 — handler has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
R2 · Cyclomatic Complexity · Complex function domOutputSpecToReactElement (cyclomatic 16, cognitive 37) · ×1
  • Complex function domOutputSpecToReactElement (cyclomatic 16, cognitive 37) packages/static-renderer/src/pm/react/react.ts:64 — domOutputSpecToReactElement has cyclomatic complexity 16 and cognitive complexity 37; 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.
R2 · Cyclomatic Complexity · Complex function updateColumns (cyclomatic 16, cognitive 36) · ×1
  • Complex function updateColumns (cyclomatic 16, cognitive 36) packages/extension-table/src/table/TableView.ts:6 — updateColumns has cyclomatic complexity 16 and cognitive complexity 36; 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.
R2 · Cyclomatic Complexity · Complex function replacePackageSpecifiers (cyclomatic 16, cognitive 27) · ×1
  • Complex function replacePackageSpecifiers (cyclomatic 16, cognitive 27) codemods/tiptap-v4-migration/scripts/vue-sfc-imports.mjs:142 — replacePackageSpecifiers has cyclomatic complexity 16 and cognitive complexity 27; 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.
R2 · Cyclomatic Complexity · Complex function parseMarkdown (cyclomatic 16, cognitive 26) · ×1
  • Complex function parseMarkdown (cyclomatic 16, cognitive 26) packages/extension-list/src/item/list-item.ts:97 — parseMarkdown has cyclomatic complexity 16 and cognitive complexity 26; 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.
R2 · Cyclomatic Complexity · Complex function ignoreMutation (cyclomatic 16, cognitive 15) · ×1
  • Complex function ignoreMutation (cyclomatic 16, cognitive 15) packages/core/src/NodeView.ts:271 — ignoreMutation has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
R2 · Cyclomatic Complexity · Complex function findSuggestionMatch (cyclomatic 16, cognitive 14) · ×1
  • Complex function findSuggestionMatch (cyclomatic 16, cognitive 14) REDACTED:20 — findSuggestionMatch has cyclomatic complexity 16 and cognitive complexity 14; 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.
R2 · Cyclomatic Complexity · Complex function _isDomSelectionInView (cyclomatic 16, cognitive 13) · ×1
  • Complex function _isDomSelectionInView (cyclomatic 16, cognitive 13) packages/y-tiptap/src/lib/utils/binding/ProsemirrorBinding.ts:127 — _isDomSelectionInView has cyclomatic complexity 16 and cognitive complexity 13; 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.
R2 · Cyclomatic Complexity · Complex function handleMobileEnter (cyclomatic 16, cognitive 12) · ×1
  • Complex function handleMobileEnter (cyclomatic 16, cognitive 12) packages/react/src/handleMobileEnter.ts:9 — handleMobileEnter has cyclomatic complexity 16 and cognitive complexity 12; 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.
R2 · Cyclomatic Complexity · Complex function domOutputSpecToHTMLString (cyclomatic 15, cognitive 35) · ×1
  • Complex function domOutputSpecToHTMLString (cyclomatic 15, cognitive 35) packages/static-renderer/src/pm/html-string/html-string.ts:43 — domOutputSpecToHTMLString has cyclomatic complexity 15 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 1536 lines of code REDACTED:1 — REDACTED has 1536 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/core/src/types.ts · ×1
  • packages/core/src/types.ts: 1048 lines of code packages/core/src/types.ts:1 — packages/core/src/types.ts has 1048 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/core/src/lib/ResizableNodeView.ts · ×1
  • packages/core/src/lib/ResizableNodeView.ts: 923 lines of code packages/core/src/lib/ResizableNodeView.ts:1 — packages/core/src/lib/ResizableNodeView.ts has 923 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/core/src/Editor.ts · ×1
  • packages/core/src/Editor.ts: 804 lines of code packages/core/src/Editor.ts:1 — packages/core/src/Editor.ts has 804 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/core/src/Extendable.ts · ×1
  • packages/core/src/Extendable.ts: 622 lines of code packages/core/src/Extendable.ts:1 — packages/core/src/Extendable.ts has 622 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/extension-bubble-menu/src/bubble-menu-plugin.ts · ×1
  • packages/extension-bubble-menu/src/bubble-menu-plugin.ts: 602 lines of code packages/extension-bubble-menu/src/bubble-menu-plugin.ts:1 — packages/extension-bubble-menu/src/bubble-menu-plugin.ts has 602 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/extension-table/src/table/table.ts · ×1
  • packages/extension-table/src/table/table.ts: 562 lines of code packages/extension-table/src/table/table.ts:1 — packages/extension-table/src/table/table.ts has 562 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/extension-floating-menu/src/floating-menu-plugin.ts · ×1
  • packages/extension-floating-menu/src/floating-menu-plugin.ts: 499 lines of code packages/extension-floating-menu/src/floating-menu-plugin.ts:1 — packages/extension-floating-menu/src/floating-menu-plugin.ts has 499 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/extension-link/src/link.ts · ×1
  • packages/extension-link/src/link.ts: 497 lines of code packages/extension-link/src/link.ts:1 — packages/extension-link/src/link.ts has 497 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/core/src/ExtensionManager.ts · ×1
  • packages/core/src/ExtensionManager.ts: 489 lines of code packages/core/src/ExtensionManager.ts:1 — packages/core/src/ExtensionManager.ts has 489 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/extension-emoji/src/emoji.ts · ×1
  • packages/extension-emoji/src/emoji.ts: 466 lines of code packages/extension-emoji/src/emoji.ts:1 — packages/extension-emoji/src/emoji.ts has 466 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/extension-drag-handle/src/drag-handle-plugin.ts · ×1
  • packages/extension-drag-handle/src/drag-handle-plugin.ts: 448 lines of code packages/extension-drag-handle/src/drag-handle-plugin.ts:1 — packages/extension-drag-handle/src/drag-handle-plugin.ts has 448 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/static-renderer/src/pm/extensionRenderer.ts · ×1
  • packages/static-renderer/src/pm/extensionRenderer.ts: 440 lines of code packages/static-renderer/src/pm/extensionRenderer.ts:1 — packages/static-renderer/src/pm/extensionRenderer.ts has 440 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/extension-code-block/src/code-block.ts · ×1
  • packages/extension-code-block/src/code-block.ts: 425 lines of code packages/extension-code-block/src/code-block.ts:1 — packages/extension-code-block/src/code-block.ts has 425 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/extension-details/src/details.ts · ×1
  • packages/extension-details/src/details.ts: 420 lines of code packages/extension-details/src/details.ts:1 — packages/extension-details/src/details.ts has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~460 LoC) · ×1
  • Dead file (~460 LoC) demos/src/Experiments/CollaborationMappingPerformance/React/index.tsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~357 LoC) · ×1
  • Dead file (~357 LoC) demos/src/Examples/StaticRendering/React/index.tsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~351 LoC) · ×1
  • Dead file (~351 LoC) demos/src/Examples/NodePos/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~317 LoC) · ×1
  • Dead file (~317 LoC) demos/src/Examples/Accessibility/React/MenuBar.tsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 5 in-repo import(s) from 4 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~313 LoC) · ×1
  • Dead file (~313 LoC) demos/src/Examples/StaticRenderingAdvanced/React/index.tsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~285 LoC) · ×1
  • Dead file (~285 LoC) demos/src/Experiments/All/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~275 LoC) · ×1
  • Dead file (~275 LoC) demos/src/Examples/Tables/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~250 LoC) · ×1
  • Dead file (~250 LoC) demos/src/Examples/Tables/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~247 LoC) · ×1
  • Dead file (~247 LoC) demos/src/Markdown/Full/React/index.tsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~229 LoC) · ×1
  • Dead file (~229 LoC) demos/src/Experiments/GenericFigure/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~200 LoC) · ×1
  • Dead file (~200 LoC) demos/src/Markdown/CustomSyntax/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~195 LoC) · ×1
  • Dead file (~195 LoC) demos/src/Examples/Default/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~192 LoC) · ×1
  • Dead file (~192 LoC) demos/src/Extensions/DragHandle/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~191 LoC) · ×1
  • Dead file (~191 LoC) demos/src/Nodes/Audio/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~179 LoC) · ×1
  • Dead file (~179 LoC) demos/src/Examples/CSSModules/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~178 LoC) · ×1
  • Dead file (~178 LoC) demos/src/Commands/InsertContentApplyingRules/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~173 LoC) · ×1
  • Dead file (~173 LoC) demos/src/Extensions/DragHandle/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~172 LoC) · ×1
  • Dead file (~172 LoC) demos/src/Experiments/GlobalDragHandle/Vue/DragHandle.js — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 5 in-repo import(s) from 4 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~157 LoC) · ×1
  • Dead file (~157 LoC) demos/src/Examples/Book/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~145 LoC) · ×1
  • Dead file (~145 LoC) demos/src/Marks/Link/React/index.jsx — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~142 LoC) · ×1
  • Dead file (~142 LoC) demos/src/Extensions/BubbleMenu/Vue/index.vue — no import path from any entry point (131 application, 73 tooling, 375 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (demos/setup/react.ts, demos/setup/svelte.ts, demos/setup/vue.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R8 · Dependency Hygiene · Unused dependency '@changesets/changelog-github' · ×1
  • Unused dependency '@changesets/changelog-github' — 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.
R8 · Dependency Hygiene · Unused dependency 'cz-conventional-changelog' · ×1
  • Unused dependency 'cz-conventional-changelog' — 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.
R8 · Dependency Hygiene · Unused dependency 'minimist' · ×1
  • Unused dependency 'minimist' — 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.
R8 · Dependency Hygiene · Unused dependency 'pkg-pr-new' · ×1
  • Unused dependency 'pkg-pr-new' — 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.
R8 · Dependency Hygiene · Unused dependency 'tinyglobby' · ×1
  • Unused dependency 'tinyglobby' — 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.
R8 · Dependency Hygiene · Unused dependency 'tsconfig-paths' · ×1
  • Unused dependency 'tsconfig-paths' — 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.
R8 · Dependency Hygiene · Unused dependency '@lifeomic/attempt' · ×1
  • Unused dependency '@lifeomic/attempt' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency '@shikijs/core' · ×1
  • Unused dependency '@shikijs/core' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'linkifyjs' · ×1
  • Unused dependency 'linkifyjs' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-changeset' · ×1
  • Unused dependency 'prosemirror-changeset' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-collab' · ×1
  • Unused dependency 'prosemirror-collab' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-commands' · ×1
  • Unused dependency 'prosemirror-commands' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-dropcursor' · ×1
  • Unused dependency 'prosemirror-dropcursor' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-gapcursor' · ×1
  • Unused dependency 'prosemirror-gapcursor' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-history' · ×1
  • Unused dependency 'prosemirror-history' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-inputrules' · ×1
  • Unused dependency 'prosemirror-inputrules' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-keymap' · ×1
  • Unused dependency 'prosemirror-keymap' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-markdown' · ×1
  • Unused dependency 'prosemirror-markdown' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-menu' · ×1
  • Unused dependency 'prosemirror-menu' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-schema-basic' · ×1
  • Unused dependency 'prosemirror-schema-basic' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-schema-list' · ×1
  • Unused dependency 'prosemirror-schema-list' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-tables' · ×1
  • Unused dependency 'prosemirror-tables' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-trailing-node' · ×1
  • Unused dependency 'prosemirror-trailing-node' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'prosemirror-transform' · ×1
  • Unused dependency 'prosemirror-transform' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency 'sass-embedded' · ×1
  • Unused dependency 'sass-embedded' — Declared in demos/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.
R8 · Dependency Hygiene · Unused dependency '@tiptap/extension-bullet-list' · ×1
  • Unused dependency '@tiptap/extension-bullet-list' — Declared in packages/starter-kit/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.
R8 · Dependency Hygiene · Unused dependency '@tiptap/extension-ordered-list' · ×1
  • Unused dependency '@tiptap/extension-ordered-list' — Declared in packages/starter-kit/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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) packages/core/src/helpers/warnOnDuplicatedProseMirrorModel.ts:35 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Minor — 179 finding(s)
D19 · Documentation Quality · Documentation · ×56
  • Documentation: no build, run or usage example packages/ai-toolkit/README.md:1 — `ai-toolkit` is a published package (`package.json` without `"private": true`) and neither `packages/ai-toolkit/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/core/README.md:1 — `core` is a published package (`package.json` without `"private": true`) and neither `packages/core/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-blockquote/README.md:1 — `extension-blockquote` is a published package (`package.json` without `"private": true`) and neither `packages/extension-blockquote/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-bold/README.md:1 — `extension-bold` is a published package (`package.json` without `"private": true`) and neither `packages/extension-bold/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-bubble-menu/README.md:1 — `extension-bubble-menu` is a published package (`package.json` without `"private": true`) and neither `packages/extension-bubble-menu/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-bullet-list/README.md:1 — `extension-bullet-list` is a published package (`package.json` without `"private": true`) and neither `packages/extension-bullet-list/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-code/README.md:1 — `extension-code` is a published package (`package.json` without `"private": true`) and neither `packages/extension-code/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-code-block/README.md:1 — `extension-code-block` is a published package (`package.json` without `"private": true`) and neither `packages/extension-code-block/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-code-block-lowlight/README.md:1 — `extension-code-block-lowlight` is a published package (`package.json` without `"private": true`) and neither `packages/extension-code-block-lowlight/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-collaboration/README.md:1 — `extension-collaboration` is a published package (`package.json` without `"private": true`) and neither `packages/extension-collaboration/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-collaboration-caret/README.md:1 — `extension-collaboration-caret` is a published package (`package.json` without `"private": true`) and neither `packages/extension-collaboration-caret/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-color/README.md:1 — `extension-color` is a published package (`package.json` without `"private": true`) and neither `packages/extension-color/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-details/README.md:1 — `extension-details` is a published package (`package.json` without `"private": true`) and neither `packages/extension-details/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-document/README.md:1 — `extension-document` is a published package (`package.json` without `"private": true`) and neither `packages/extension-document/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-drag-handle/README.md:1 — `extension-drag-handle` is a published package (`package.json` without `"private": true`) and neither `packages/extension-drag-handle/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-drag-handle-react/README.md:1 — `extension-drag-handle-react` is a published package (`package.json` without `"private": true`) and neither `packages/extension-drag-handle-react/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-drag-handle-vue/README.md:1 — `extension-drag-handle-vue` is a published package (`package.json` without `"private": true`) and neither `packages/extension-drag-handle-vue/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-file-handler/README.md:1 — `extension-file-handler` is a published package (`package.json` without `"private": true`) and neither `packages/extension-file-handler/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-find-and-replace/README.md:1 — `extension-find-and-replace` is a published package (`package.json` without `"private": true`) and neither `packages/extension-find-and-replace/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-floating-menu/README.md:1 — `extension-floating-menu` is a published package (`package.json` without `"private": true`) and neither `packages/extension-floating-menu/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-font-family/README.md:1 — `extension-font-family` is a published package (`package.json` without `"private": true`) and neither `packages/extension-font-family/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-hard-break/README.md:1 — `extension-hard-break` is a published package (`package.json` without `"private": true`) and neither `packages/extension-hard-break/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-heading/README.md:1 — `extension-heading` is a published package (`package.json` without `"private": true`) and neither `packages/extension-heading/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-highlight/README.md:1 — `extension-highlight` is a published package (`package.json` without `"private": true`) and neither `packages/extension-highlight/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/extension-horizontal-rule/README.md:1 — `extension-horizontal-rule` is a published package (`package.json` without `"private": true`) and neither `packages/extension-horizontal-rule/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • + 31 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×42
  • Orphaned file demos/src/Experiments/All/Vue/index.vue: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 demos/src/Experiments/GenericFigure/Vue/index.vue: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 demos/preview/Demo.vue: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/extension-link/src/helpers/markdownLink.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 demos/src/Extensions/BubbleMenu/Vue/index.vue: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 demos/src/Experiments/GlobalDragHandle/Vue/DragHandle.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 demos/src/Experiments/MultipleEditors/Vue/index.vue: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 demos/src/Nodes/Table/Vue/index.vue: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 demos/src/Commands/InsertContentApplyingRules/React/index.jsx: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 demos/src/Experiments/Figure/Vue/index.vue: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 demos/src/Demos/SingleRoomCollab/React/index.jsx: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/core/src/helpers/getAttributesFromExtensions.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 demos/src/Extensions/Color/React/index.tsx: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 demos/src/GuideContent/ExportJSON/Vue/index.vue: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 demos/src/Extensions/TextAlign/React/index.jsx: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 demos/src/Extensions/FloatingMenu/Vue/index.vue: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 demos/src/Nodes/CodeBlockLowlight/Vue/index.vue: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 demos/src/GuideContent/ExportHTML/Vue/index.vue: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 demos/src/Marks/Highlight/React/index.jsx: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 demos/src/Extensions/CollaborationWithMenus/Vue/index.vue: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/core/src/inputRules/wrappingInputRule.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 demos/src/Marks/TextStyle/Vue/index.vue: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 demos/src/Extensions/TextAlign/Vue/index.vue: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/extensions/src/focus/focus.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 demos/src/Nodes/ListItem/React/index.jsx: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.
  • + 17 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×24
  • redundant comment packages/core/src/helpers/createNodeFromContent.ts:68 — "Check for invalid content" repeats the code it sits on: 3 of its 3 words (check, invalid, content) are already in `if (options.errorOnInvalidContent)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core/src/helpers/findChildrenInRange.ts:22 — "if (nodeAt) { nodesWithPos.push({ node: nodeAt, pos: range.from, }) } }" repeats the code it sits on: 4 of its 5 words (node, nodes, pos, range) are already in `node.nodesBetween(range.from, range.to, (child, pos) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core/src/utilities/markdown/createInlineMarkdownSpec.ts:227 — "Parse attributes from the attribute string" repeats the code it sits on: 4 of its 4 words (parse, attributes, attribute, string) are already in `const attributes = parseAttributes(attrString.trim())`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/extension-drag-handle/src/drag-handle-plugin.ts:320 — "Set the new position for our current node." repeats the code it sits on: 4 of its 5 words (set, new, current, node) are already in `currentNodePos = newPos`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/extension-drag-handle/src/drag-handle-plugin.ts:333 — "Set the new position for our current node." repeats the code it sits on: 4 of its 5 words (set, new, current, node) are already in `currentNodePos = newPos`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/extension-list/src/item/list-item.ts:140 — "Parse the inline content from the text token" repeats the code it sits on: 4 of its 5 words (parse, inline, content, token) are already in `const inlineContent = helpers.parseInline(firstToken.tokens)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/extension-list/src/task-item/task-item.test.ts:255 — "Extend TaskItem with a custom attribute" repeats the code it sits on: 5 of its 5 words (extend, task, item, custom, attribute) are already in `const CustomTaskItem = TaskItem.extend({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/extension-list/src/task-item/task-item.test.ts:436 — "Configure TaskItem with static HTMLAttributes" repeats the code it sits on: 6 of its 6 words (configure, task, item, static, html, attributes) are already in `const ConfiguredTaskItem = TaskItem.configure({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/extension-list/src/task-item/task-item.test.ts:470 — "Update the task item" repeats the code it sits on: 3 of its 3 words (update, task, item) are already in `editor.chain().setTextSelection(4).updateAttributes('taskItem', { checked: true }).run()`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/extension-list/src/task-item/task-item.ts:163 — "If we have tokens, create a paragraph with the inline content" repeats the code it sits on: 5 of its 5 words (tokens, create, paragraph, inline, content) are already in `content.push(h.createNode('paragraph', {}, h.parseInline(token.tokens)))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/extension-list/src/task-item/task-item.ts:166 — "If we have raw text, create a paragraph with text node" repeats the code it sits on: 4 of its 5 words (text, create, paragraph, node) are already in `content.push(h.createNode('paragraph', {}, [h.createNode('text', { text: token.text })]))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/extension-paragraph/src/paragraph.ts:74 — "Parse the inline tokens" repeats the code it sits on: 3 of its 3 words (parse, inline, tokens) are already in `const content = helpers.parseInline(tokens)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/extension-table/src/table/utilities/markdown.ts:110 — "Build rows: each cell is { text, isHeader, align }" repeats the code it sits on: 5 of its 6 words (rows, cell, text, header, align) are already in `const rows: { text: string; isHeader: boolean; align: TableCellAlignType | null }[][] = []`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:827 — "Fallback: single html token parse" repeats the code it sits on: 4 of its 5 words (single, html, token, parse) are already in `const parsedSingle = this.parseHTMLToken(token)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/markdown/src/utils.ts:50 — "split content lines" repeats the code it sits on: 3 of its 3 words (split, content, lines) are already in `const lines = content.split('\n')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/markdown/src/utils.ts:132 — "Check if nextNode has a mark of the same type with matching attrs" repeats the code it sits on: 6 of its 7 words (check, next, node, mark, type, attrs) are already in `const nextMark = nextNode.marks.find(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/markdown/src/utils.ts:141 — "Close all active marks" repeats the code it sits on: 3 of its 3 words (close, active, marks) are already in `marksToCloseAtEnd.push(...Array.from(activeMarks.keys()).reverse())`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/markdown/tests/integration/server-side-parsing.test.ts:65 — "Find text nodes with code marks" repeats the code it sits on: 4 of its 5 words (text, nodes, code, marks) are already in `const codeTextNodes = paragraph.content!.filter(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/react/src/ReactNodeViewRenderer.tsx:194 — "remove the nodeViewWrapper attribute from the element" repeats the code it sits on: 5 of its 6 words (node, view, wrapper, attribute, element) are already in `if (element.hasAttribute('data-node-view-wrapper'))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/react/src/ReactRenderer.tsx:63 — "Check if it's a class component" repeats the code it sits on: 3 of its 3 words (check, class, component) are already in `if (isClassComponent(Component))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/react/src/ReactRenderer.tsx:68 — "Check if it's a forwardRef component" repeats the code it sits on: 4 of its 4 words (check, forward, ref, component) are already in `if (isForwardRefComponent(Component))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/vue/src/VueMarkViewRenderer.test.ts:43 — "Create editor element" repeats the code it sits on: 3 of its 3 words (create, editor, element) are already in `editorElement = document.createElement('div')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/vue/src/VueMarkViewRenderer.test.ts:61 — "Create editor with custom mark" repeats the code it sits on: 4 of its 4 words (create, editor, custom, mark) are already in `editor = new Editor({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/vue/src/VueMarkViewRenderer.test.ts:92 — "Create editor with custom mark" repeats the code it sits on: 4 of its 4 words (create, editor, custom, mark) are already in `editor = new Editor({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
X10 · Duplicated predicate · Duplicated predicate · ×21
  • Duplicated predicate packages/extension-table-of-contents/src/generate-toc-ids.ts:68 — `!anchorTypes.includes(node.type.name) || node.textContent.length === 0` appears character-identically in 2 files — packages/extension-table-of-contents/src/generate-toc-ids.ts, packages/extension-table-of-contents/src/plugin.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/react/src/menus/BubbleMenu.tsx:130 — `!pluginInitialized || !pluginEditor || pluginEditor.isDestroyed` appears character-identically in 2 files — packages/react/src/menus/BubbleMenu.tsx, packages/react/src/menus/FloatingMenu.tsx. 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/core/src/inputRules/markInputRule.ts:29 — `attributes === false || attributes === null` appears character-identically in 3 files — packages/core/src/inputRules/markInputRule.ts, packages/core/src/pasteRules/markPasteRule.ts, packages/core/src/pasteRules/nodePasteRule.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/extension-details/src/details.ts:210 — `editor.isEditable && typeof getPos === 'function'` appears character-identically in 2 files — packages/extension-details/src/details.ts, packages/extension-list/src/task-item/task-item.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/extension-bubble-menu/src/bubble-menu-plugin.ts:476 — `event?.relatedTarget && this.element.parentNode?.contains(event.relatedTarget as Node)` appears character-identically in 2 files — packages/extension-bubble-menu/src/bubble-menu-plugin.ts, packages/extension-floating-menu/src/floating-menu-plugin.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/extension-bubble-menu/src/bubble-menu-plugin.ts:651 — `meta && typeof meta === 'object' && meta.type === 'updateOptions'` appears character-identically in 2 files — packages/extension-bubble-menu/src/bubble-menu-plugin.ts, packages/extension-floating-menu/src/floating-menu-plugin.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/extension-bubble-menu/src/bubble-menu-plugin.ts:508 — `middlewareData.hide?.referenceHidden || middlewareData.hide?.escaped` appears character-identically in 2 files — packages/extension-bubble-menu/src/bubble-menu-plugin.ts, packages/extension-floating-menu/src/floating-menu-plugin.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/extension-table-of-contents/src/plugin.ts:40 — `nodeId === null || nodeId === undefined || existingIds.includes(nodeId)` appears character-identically in 2 files — packages/extension-table-of-contents/src/plugin.ts, packages/extension-table-of-contents/src/tableOfContents.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/extensions/src/placeholder/plugins/PlaceholderPlugin.ts:33 — `options.showOnlyCurrent && !options.includeChildren` appears character-identically in 2 files — packages/extensions/src/placeholder/plugins/PlaceholderPlugin.ts, packages/extensions/src/placeholder/utils/buildPlaceholderDecorations.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/core/src/commands/setTextDirection.ts:29 — `position && 'from' in position && 'to' in position` appears character-identically in 2 files — packages/core/src/commands/setTextDirection.ts, packages/core/src/commands/unsetTextDirection.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/extension-collaboration/src/helpers/yRelativePosition.ts:18 — `relativePositionToAbsolutePosition( ystate.doc, ystate.type, relativePos, ystate.binding.mapping, ) || 0` appears character-identically in 2 files — packages/extension-collaboration/src/helpers/yRelativePosition.ts, packages/extension-drag-handle/src/drag-handle-plugin.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/core/src/helpers/isProseMirrorCellSelection.ts:13 — `selection === null || typeof selection !== 'object'` appears character-identically in 2 files — packages/core/src/helpers/isProseMirrorCellSelection.ts, packages/core/src/helpers/isProseMirrorNodeSelection.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/core/src/commands/splitListItem.ts:163 — `storedMarks || (selection.$to.parentOffset && selection.$from.marks())` appears character-identically in 4 files — packages/core/src/commands/splitListItem.ts, packages/core/src/commands/toggleList.ts, packages/core/src/inputRules/wrappingInputRule.ts, packages/extension-hard-break/src/hard-break.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/core/src/MarkView.ts:122 — `this.contentDOM === mutation.target && mutation.type === 'attributes'` appears character-identically in 2 files — packages/core/src/MarkView.ts, packages/core/src/NodeView.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/core/src/MarkView.ts:107 — `this.contentDOM.contains(mutation.target) && mutation.type === 'childList' && (isiOS() || isAndroid()) && this.editor.isFocused` appears character-identically in 2 files — packages/core/src/MarkView.ts, packages/core/src/NodeView.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/extension-bubble-menu/src/bubble-menu-plugin.ts:519 — `this.isVisible && this.floatingUIOptions.onUpdate` appears character-identically in 2 files — packages/extension-bubble-menu/src/bubble-menu-plugin.ts, packages/extension-floating-menu/src/floating-menu-plugin.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/extension-list/src/bullet-list/bullet-list.ts:137 — `this.options.keepMarks || this.options.keepAttributes` appears character-identically in 2 files — packages/extension-list/src/bullet-list/bullet-list.ts, packages/extension-list/src/ordered-list/ordered-list.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/static-renderer/src/pm/html-string/html-string.ts:49 — `typeof content === 'object' && 'length' in content` appears character-identically in 2 files — packages/static-renderer/src/pm/html-string/html-string.ts, packages/static-renderer/src/pm/react/react.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/react/src/ReactNodeViewRenderer.tsx:91 — `typeof newPos !== 'number' || newPos === this.currentPos` appears character-identically in 2 files — packages/react/src/ReactNodeViewRenderer.tsx, packages/vue/src/VueNodeViewRenderer.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/html/src/server/generateHTML.ts:22 — `typeof process !== 'undefined' && process.versions != null && process.versions.node != null` appears character-identically in 2 files — packages/html/src/server/generateHTML.ts, packages/html/src/server/generateJSON.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/core/src/helpers/isProseMirrorAddMarkStep.ts:13 — `value === null || typeof value !== 'object'` appears character-identically in 12 files — packages/core/src/helpers/isProseMirrorAddMarkStep.ts, packages/core/src/helpers/isProseMirrorAddNodeMarkStep.ts, packages/core/src/helpers/isProseMirrorAttrStep.ts, packages/core/src/helpers/isProseMirrorDocAttrStep.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.
D10 · Test Quality · Mock-dominated test · ×16
  • Mock-dominated test: should respect shouldShow returning false packages/suggestion/tests/integration/suggestion.test.ts:9 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 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: should respect shouldShow returning true packages/suggestion/tests/integration/suggestion.test.ts:49 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 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: should not call items when query is shorter than minQueryLength packages/suggestion/tests/integration/suggestion.test.ts:415 — This test sets up 4 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 4 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: should pass initialItems to onBeforeStart/onBeforeUpdate and resolved items to onStart/onUpdate packages/suggestion/tests/integration/suggestion.test.ts:468 — This test sets up 6 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 7 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: should set loading to true in before callbacks and false after when items() is called packages/suggestion/tests/integration/suggestion.test.ts:545 — This test sets up 6 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 5 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: should recover when items() rejects packages/suggestion/tests/integration/suggestion.test.ts:597 — This test sets up 4 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 3 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: should set loading to false in all callbacks when minQueryLength blocks items() packages/suggestion/tests/integration/suggestion.test.ts:633 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 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: should not emit stale callbacks after a request is superseded packages/suggestion/tests/integration/suggestion.test.ts:734 — This test sets up 3 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 2 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: should delay the items() call by the configured debounce time packages/suggestion/tests/integration/suggestion.test.ts:827 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 4 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: should cancel pending debounce work on destroy packages/suggestion/tests/integration/suggestion.test.ts:874 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 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: does not clear or restore the DOM selection when the editor is not editable packages/extensions/src/selection/selection.test.ts:60 — This test sets up 3 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 2 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: hides the menu once the composition ends packages/extension-floating-menu/src/floating-menu-plugin.test.ts:253 — This test sets up 3 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 4 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: hides the menu once the composition ends packages/extension-bubble-menu/src/bubble-menu-plugin.test.ts:292 — This test sets up 3 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 4 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: forced updateDecorations(name) runs full create for that extension only, never createInRange packages/core/tests/integration/changedRangeDecorations.test.ts:147 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 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 only the latest option callback and keeps event listeners packages/core/tests/integration/runtimeOptions.test.ts:13 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 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: updates callbacks before mounting and on destruction packages/core/tests/integration/runtimeOptions.test.ts:56 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×3
  • Silent fallback default in catch packages/core/src/commands/toggleList.ts:243 — `toggleList.<returned closure>` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch REDACTED:320 — `getHandlersForToken` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch REDACTED:342 — `getHandlersForNodeType` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
D12 · Dependency Hygiene · Deprecated · ×2
  • Deprecated: git-raw-commits REDACTED:4349 — git-raw-commits 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Deprecated and no longer maintained. Use @conventional-changelog/git-client instead.". 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:5910 — whatwg-encoding 2.0.0 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.
D12 · Dependency Hygiene · Outdated (npm) · ×2
  • Outdated (npm): @shikijs/core demos/package.json:18 — @shikijs/core is pinned at 1.10.3; registry.npmjs.org publishes 4.6.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): shiki demos/package.json:46 — shiki is pinned at 1.29.2; registry.npmjs.org publishes 4.6.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.
D16 · Bus Factor · Off-boarding risk · ×2
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 18 significant file(s) lose their only recent owner: packages/extension-drag-handle/src/types/options.ts, packages/extension-twitch/src/utils.ts, demos/src/Extensions/DragHandle/Vue/index.vue, packages/markdown/src/Extension.ts, demos/src/Markdown/Full/React/index.tsx, demos/src/Extensions/DragHandle/React/index.jsx, demos/src/Experiments/CollaborationAnnotation/Vue/index.vue, demos/src/Nodes/Audio/React/index.jsx (+10 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 7 significant file(s) lose their only recent owner: demos/src/Experiments/CollaborationMappingPerformance/React/index.tsx, packages/y-tiptap/src/lib/plugins/yCursorPlugin.ts, demos/src/Demos/CollaborationSplitPane/React/Editor.jsx, packages/y-tiptap/src/lib/utils/conversion/createNodeFromYElement.ts, demos/src/Extensions/CollaborationMapPositions/React/index.tsx, packages/y-tiptap/src/index.ts, packages/extension-unique-id/src/generate-unique-ids.ts. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (29 single-owned of 275 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; 275 of the 1174 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/static-renderer/src/pm/extensionRenderer.ts, packages/ai-toolkit/src/streaming-reveal.ts, packages/extension-mathematics/src/extensions/BlockMath.ts, packages/core/src/commands/clearNodes.ts.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found package.json:9 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `package.json` makes this repository a deployable product (line 9).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 63 project(s) overshoot their size bounds, lowering Project Cohesion to 9.7/10. The most over is `packages/core` (15970 LoC, 366 module-visible types across 13 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.
D30 · Dependency Vulnerabilities · Low CVE · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 42 of 275 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (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; 275 of the 1174 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: demos/src/Experiments/All/Vue/index.vue, demos/src/Experiments/GenericFigure/Vue/index.vue, demos/preview/Demo.vue, packages/extension-link/src/helpers/markdownLink.ts, demos/src/Extensions/BubbleMenu/Vue/index.vue, demos/src/Experiments/GlobalDragHandle/Vue/DragHandle.js, demos/src/Experiments/MultipleEditors/Vue/index.vue, demos/src/Nodes/Table/Vue/index.vue (and 34 more). 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:17 — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · Dependabot does not watch npm · ×1
  • Dependabot does not watch npm REDACTED:5 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
X5 · Nullable reference types · Null assertions (`!`) override strict null checking · ×1
  • Null assertions (`!`) override strict null checking — ~0.3 `!` null assertions per 1k TypeScript source lines — 25 assertion(s) across the 83949 source line(s) of the 777 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/core/src/Editor.ts (6), packages/extension-node-range/src/helpers/NodeRangeBookmark.ts (3), packages/vue/src/VueNodeViewRenderer.ts (3). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Minor — 47 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×27
  • Outdated (npm): @hocuspocus/provider — @hocuspocus/provider is pinned at 2.15.3; registry.npmjs.org publishes 4.8.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): @hocuspocus/transformer — @hocuspocus/transformer is pinned at 2.15.3; registry.npmjs.org publishes 4.8.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): @lexical/react — @lexical/react is pinned at 0.36.2; registry.npmjs.org publishes 0.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): @types/use-sync-external-store — @types/use-sync-external-store is pinned at 0.0.6; registry.npmjs.org publishes 1.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): d3 — d3 is pinned at 7.9.0; registry.npmjs.org publishes 7.9.2 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): emoji-regex — emoji-regex is pinned at 10.6.0; registry.npmjs.org publishes 11.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): emojibase-data — emojibase-data is pinned at 17.0.0; registry.npmjs.org publishes 18.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): es-toolkit — es-toolkit is pinned at 1.50.0; registry.npmjs.org publishes 1.53.2 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): fast-equals — fast-equals is pinned at 5.4.1; registry.npmjs.org publishes 6.2.2 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.4; 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): lexical — lexical is pinned at 0.36.2; registry.npmjs.org publishes 0.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): lib0 — lib0 is pinned at 0.2.117; registry.npmjs.org publishes 0.2.120 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): linkifyjs — linkifyjs is pinned at 4.3.3; 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): marked — marked is pinned at 17.0.6; registry.npmjs.org publishes 18.2.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): prosemirror-changeset — prosemirror-changeset is pinned at 2.4.4; registry.npmjs.org publishes 2.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): prosemirror-inputrules — prosemirror-inputrules is pinned at 1.5.1; registry.npmjs.org publishes 1.6.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): prosemirror-markdown — prosemirror-markdown is pinned at 1.13.8; registry.npmjs.org publishes 1.13.9 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): prosemirror-model — prosemirror-model is pinned at 1.25.12; registry.npmjs.org publishes 1.25.13 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): prosemirror-schema-list — prosemirror-schema-list is pinned at 1.5.1; registry.npmjs.org publishes 1.6.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): prosemirror-transform — prosemirror-transform is pinned at 1.12.2; registry.npmjs.org publishes 1.12.5 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): prosemirror-view — prosemirror-view is pinned at 1.42.6; registry.npmjs.org publishes 1.42.9 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): re2js — re2js is pinned at 2.8.7; registry.npmjs.org publishes 2.10.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): remixicon — remixicon is pinned at 2.5.0; registry.npmjs.org publishes 4.9.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): use-sync-external-store — use-sync-external-store is pinned at 1.6.0; registry.npmjs.org publishes 1.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): uuid — uuid is pinned at 14.0.1; 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.
  • + 2 more in this group — see findings.md.
D24 · Comment Value · doc comments repeat the names · ×18
  • doc comments repeat the names packages/ai-toolkit/src/schema-awareness/get-editor-context.ts:12 — 0 of 16 documented parameters and 1 of 63 summaries in `@tiptap/ai-toolkit` only repeat the member or parameter name (e.g. "Options for ." for `GetEditorContextOptions`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/core/src/Editor.ts:453 — 10 of 281 documented parameters and 39 of 672 summaries in `@tiptap/core` only repeat the member or parameter name (e.g. "The plugins name" for `nameOrPluginKeyToRemove`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-bubble-menu/src/bubble-menu-plugin.ts:35 — 0 of 0 documented parameters and 2 of 14 summaries in `@tiptap/extension-bubble-menu` only repeat the member or parameter name (e.g. "The plugin key." for `pluginKey`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-code-block/src/code-block.ts:28 — 0 of 2 documented parameters and 3 of 13 summaries in `@tiptap/extension-code-block` only repeat the member or parameter name (e.g. "The default language." for `defaultLanguage`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-code-block-lowlight/src/code-block-lowlight.ts:8 — 0 of 0 documented parameters and 1 of 2 summaries in `@tiptap/extension-code-block-lowlight` only repeat the member or parameter name (e.g. "The lowlight instance." for `lowlight`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-file-handler/src/types.ts:12 — 2 of 5 documented parameters and 1 of 6 summaries in `@tiptap/extension-file-handler` only repeat the member or parameter name (e.g. "The editor instance." for `editor`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-find-and-replace/src/types.ts:73 — 0 of 26 documented parameters and 2 of 37 summaries in `@tiptap/extension-find-and-replace` only repeat the member or parameter name (e.g. "The current search term." for `searchTerm`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-floating-menu/src/floating-menu-plugin.ts:28 — 0 of 0 documented parameters and 2 of 17 summaries in `@tiptap/extension-floating-menu` only repeat the member or parameter name (e.g. "The editor instance." for `editor`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-invisible-characters/src/invisible-characters.ts:15 — 0 of 0 documented parameters and 3 of 5 summaries in `@tiptap/extension-invisible-characters` only repeat the member or parameter name (e.g. "Show invisible characters" for `showInvisibleCharacters`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-list/src/bullet-list/bullet-list.ts:40 — 0 of 29 documented parameters and 3 of 66 summaries in `@tiptap/extension-list` only repeat the member or parameter name (e.g. "Toggle a bullet list" for `toggleBulletList`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-ruby-text/src/ruby-text-decoration-plugin.ts:33 — 0 of 5 documented parameters and 1 of 17 summaries in `@tiptap/extension-ruby-text` only repeat the member or parameter name (e.g. "The editor instance." for `editor`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-table/src/table/table.ts:108 — 0 of 13 documented parameters and 13 of 52 summaries in `@tiptap/extension-table` only repeat the member or parameter name (e.g. "Allow table node selection." for `allowTableNodeSelection`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-text-align/src/text-align.ts:19 — 2 of 2 documented parameters and 1 of 7 summaries in `@tiptap/extension-text-align` only repeat the member or parameter name (e.g. "The default alignment." for `defaultAlignment`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extension-text-style/src/font-family/font-family.ts:18 — 3 of 6 documented parameters and 7 of 34 summaries in `@tiptap/extension-text-style` only repeat the member or parameter name (e.g. "Set the font family" for `setFontFamily`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/extensions/src/placeholder/plugins/PlaceholderPlugin.ts:19 — 5 of 26 documented parameters and 0 of 58 summaries in `@tiptap/extensions` only repeat the member or parameter name (e.g. "The editor instance." for `editor`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/react/src/ReactNodeViewRenderer.tsx:68 — 0 of 13 documented parameters and 6 of 101 summaries in `@tiptap/react` only repeat the member or parameter name (e.g. "The renderer instance." for `renderer`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/suggestion/src/types.ts:93 — 9 of 16 documented parameters and 2 of 72 summaries in `@tiptap/suggestion` only repeat the member or parameter name (e.g. "The props object." for `props`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/vue/src/VueWidgetRenderer.ts:23 — 0 of 4 documented parameters and 1 of 24 summaries in `@tiptap/vue` only repeat the member or parameter name (e.g. "The editor instance." for `editor`). Delete the restating tags, or add what the name does not say.
D10 · Test Quality · Skipped (documented) · ×2
  • Skipped (documented): (unnamed test) packages/y-tiptap/tests/integration/cache.test.ts:58 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/y-tiptap/tests/integration/incremental-sync.test.ts:79 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cc2b290d1b1646568724cd2ae0be32ea/history.json --exit-code 0 --source .1artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cc2b290d1b1646568724cd2ae0be32ea/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude .codex .47artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .2artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: 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 10 file(s) — `packages/core/jsx-dev-runtime/index.d.ts`, `packages/core/jsx-runtime/index.d.ts`, `packages/core/src/decorations/DecorationManager.ts`, `packages/core/src/helpers/getSchemaSpecByResolvedExtensions.ts`, `packages/core/src/index.ts`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1d9f1-e664-72cb-83bc-df656171b06b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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