Public report of Automattic/harper, published 27 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 27 October 2026, 01:43 UTC · Survey ID cd_077c7dcad6c0401a820304e9edfda0ff
Automattic/harper
Measured 27 October 2026, 01:36 UTC, at code version dd536c3
Regression: 2 dimensions fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskNo change 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: 127,089 lines of product code in 31 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Accessibility, 53
Findings by how serious they are
151 critical621 serious51 minor
15 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
27 October 2026, 01:36 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
81of 81 dimensions measured by tools.
796of 823 findings point to an exact file and line, so you can open each one in the code. The other 27 concern the repository as a whole, such as missing documentation.
81dimensions across 7 lenses, read from 127,089 lines of product code in 31 projects.
Automattic/harper is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because it has form fields without a label. It scores 57 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 53, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 2 points. Making the controls keyboard-usable would lift Accessibility itself, also worth about 2. Raising Accessibility to 70 would lift the score to about 60.
Eighty-one known security holes in the packages the code depends on can be used by attackers. Twenty-two form fields can't be read by a screen reader, and twenty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages, labelling the form fields and pinning each tool to an exact version would close these risks. Setting a waiting period for automatic updates would fix the four automatic dependency updates that take new releases at once, and the three unsafe settings in infrastructure or container files need changing to safe values. The ten labels or groups of fields with no name need connecting to their fields or naming.
The product code is 127,089 lines, about €140,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Accessibility rose from 53 to 70, the lowest score rated Strong, the score would rise from 57 to about 60.
Code composition: what the lines of code are
Product code 92%Tests 8%
New since the last survey: 132 findings
These 132 critical or serious findings weren't in the previous survey, on 13 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 358 findings
These 358 critical or serious findings were in the previous survey, on 13 October 2026, and are gone from this one. The first 100 are listed here.
Large Files · packages/chrome-plugin/src/background/index.ts: 796 lines of code packages/chrome-plugin/src/background/index.ts
Large Files · packages/chrome-plugin/src/options/Options.svelte: 511 lines of code packages/chrome-plugin/src/options/Options.svelte
Test Coverage · No test reaches this file packages/components/src/lib/Button.svelte
Test Coverage · No test reaches this file packages/wordpress-plugin/src/harper/SidebarControl.tsx
Test Coverage · No test reaches this file harper-desktop/src/lib/settings/components/AppPickerModal.svelte
Test Coverage · No test reaches this file packages/wordpress-plugin/src/harper/DataBlock.ts
Test Coverage · No test reaches this file packages/components/src/lib/SlideDeck.svelte
Test Coverage · No test reaches this file packages/wordpress-plugin/src/harper/RichText.ts
Test Coverage · No test reaches this file harper-desktop/src/lib/settings/components/AppIcon.svelte
Test Coverage · No test reaches this file harper-desktop/src/lib/settings/pages/WeirpacksPage.svelte
Test Coverage · No test reaches this file packages/chrome-plugin/src/popup/Popup.svelte
Test Coverage · No test reaches this file packages/web/src/routes/get/+page.svelte
Test Coverage · No test reaches this file packages/vscode-plugin/esbuild.cjs
Test Coverage · No test reaches this file packages/harper-editor/src/lib/LintCard.svelte
Test Coverage · No test reaches this file packages/web/src/routes/titlecase/+page.svelte
Test Coverage · No test reaches this file packages/wordpress-plugin/src/harper/useLintConfig.ts
Test Coverage · No test reaches this file harper-desktop/src/lib/settings/SettingsApp.svelte
Test Coverage · No test reaches this file packages/web/src/routes/languagedetection/+page.svelte
Test Coverage · No test reaches this file packages/wordpress-plugin/src/harper/LintSettingRow.tsx
Test Coverage · No test reaches this file packages/web/src/lib/components/WeirStudioFileExplorer.svelte
Test Coverage · No test reaches this file packages/wordpress-plugin/src/harper/LintList.tsx
Test Coverage · No test reaches this file packages/web/src/lib/db/models/UpdateCheckCounts.ts
Test Coverage · No test reaches this file packages/components/src/lib/DelayedRender.svelte
Test Coverage · No test reaches this file packages/web/src/lib/db/models/ProblematicLints.ts
Test Coverage · No test reaches this file packages/web/src/routes/install-browser-extension/+page.svelte
Test Coverage · No test reaches this file packages/wordpress-plugin/src/harper/DialectSelectRow.tsx
Test Coverage · No test reaches this file packages/chrome-plugin/src/background/detectDialect.ts
Test Coverage · No test reaches this file packages/components/src/lib/Select.svelte
Test Coverage · No test reaches this file packages/web/src/lib/db/models/UninstallFeedback.ts
Test Coverage · No test reaches this file packages/components/src/lib/Input.svelte
Test Coverage · No test reaches this file packages/harper.js/renderPage.js
Rebuild cost: about €140,000 · Estimate
Cost to rebuild
€48,000 to €240,000, for 792 to 2,512 hours of work, about 1.0 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 127,089 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
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 €140,000 to build again, about 1.0 person-years of work. Its weakest lens is Accessibility, at 53 (Adequate). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Documentation finding(s) in Documentation Quality. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 1 Documentation Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
701 modules, with 1673 dependencies between them. 3 loops run through 14 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 661 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.
1 pair of types, where a type in harper_core.expr.all uses a type in harper_core.span.
The types involved
harper_core.expr.all.All → harper_core.span.Span
Direction
harper_core.expr.all uses harper_core.span, so a change to harper_core.span can break harper_core.expr.all, while a change to harper_core.expr.all can't break harper_core.span.
Position
Below the diagonal: harper_core.expr.all uses a module listed above it, which is the healthy direction.
8→23 harper_core.expr.all uses harper_core.exprpart of a loop✕
Connections
1 pair of types, where a type in harper_core.expr.all uses a type in harper_core.expr.
The types involved
harper_core.expr.all.All → harper_core.expr.Expr
Direction
harper_core.expr.all uses harper_core.expr, so a change to harper_core.expr can break harper_core.expr.all, while a change to harper_core.expr.all can't break harper_core.expr.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
harper_core.expr.first_match_of uses harper_core.span, so a change to harper_core.span can break harper_core.expr.first_match_of, while a change to harper_core.expr.first_match_of can't break harper_core.span.
Position
Below the diagonal: harper_core.expr.first_match_of uses a module listed above it, which is the healthy direction.
9→23 harper_core.expr.first_match_of uses harper_core.exprpart of a loop✕
Connections
1 pair of types, where a type in harper_core.expr.first_match_of uses a type in harper_core.expr.
harper_core.expr.first_match_of uses harper_core.expr, so a change to harper_core.expr can break harper_core.expr.first_match_of, while a change to harper_core.expr.first_match_of can't break harper_core.expr.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
harper_core.expr.longest_match_of uses harper_core.span, so a change to harper_core.span can break harper_core.expr.longest_match_of, while a change to harper_core.expr.longest_match_of can't break harper_core.span.
Position
Below the diagonal: harper_core.expr.longest_match_of uses a module listed above it, which is the healthy direction.
10→23 harper_core.expr.longest_match_of uses harper_core.exprpart of a loop✕
Connections
1 pair of types, where a type in harper_core.expr.longest_match_of uses a type in harper_core.expr.
harper_core.expr.longest_match_of uses harper_core.expr, so a change to harper_core.expr can break harper_core.expr.longest_match_of, while a change to harper_core.expr.longest_match_of can't break harper_core.expr.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
harper_core.linting.suggestion uses harper_core.span, so a change to harper_core.span can break harper_core.linting.suggestion, while a change to harper_core.linting.suggestion can't break harper_core.span.
Position
Below the diagonal: harper_core.linting.suggestion uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in harper_core.mask uses a type in harper_core.span.
The types involved
harper_core.mask.Mask → harper_core.span.Span
Direction
harper_core.mask uses harper_core.span, so a change to harper_core.span can break harper_core.mask, while a change to harper_core.mask can't break harper_core.span.
Position
Below the diagonal: harper_core.mask uses a module listed above it, which is the healthy direction.
harper_core.token_kind uses harper_pos_utils.upos, so a change to harper_pos_utils.upos can break harper_core.token_kind, while a change to harper_core.token_kind can't break harper_pos_utils.upos.
Position
Below the diagonal: harper_core.token_kind uses a module listed above it, which is the healthy direction.
13→22 harper_core.token_kind uses harper_core.dict_word_metadatapart of a loop✕
Connections
1 pair of types, where a type in harper_core.token_kind uses a type in harper_core.dict_word_metadata.
harper_core.token_kind uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_core.token_kind, while a change to harper_core.token_kind can't break harper_core.dict_word_metadata.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.harper_js.src.Linter uses packages.harper_js.src.main, so a change to packages.harper_js.src.main can break packages.harper_js.src.Linter, while a change to packages.harper_js.src.Linter can't break packages.harper_js.src.main.
Position
Below the diagonal: packages.harper_js.src.Linter uses a module listed above it, which is the healthy direction.
packages.harper_js.src.Linter uses packages.obsidian-plugin.src.lint, so a change to packages.obsidian-plugin.src.lint can break packages.harper_js.src.Linter, while a change to packages.harper_js.src.Linter can't break packages.obsidian-plugin.src.lint.
Position
Below the diagonal: packages.harper_js.src.Linter uses a module listed above it, which is the healthy direction.
harper_core.linting.lint uses harper_core.linting.lint_kind, so a change to harper_core.linting.lint_kind can break harper_core.linting.lint, while a change to harper_core.linting.lint can't break harper_core.linting.lint_kind.
Position
Below the diagonal: harper_core.linting.lint uses a module listed above it, which is the healthy direction.
harper_core.linting.lint uses harper_core.span, so a change to harper_core.span can break harper_core.linting.lint, while a change to harper_core.linting.lint can't break harper_core.span.
Position
Below the diagonal: harper_core.linting.lint uses a module listed above it, which is the healthy direction.
harper_core.linting.lint uses harper_core.linting.suggestion, so a change to harper_core.linting.suggestion can break harper_core.linting.lint, while a change to harper_core.linting.lint can't break harper_core.linting.suggestion.
Position
Below the diagonal: harper_core.linting.lint uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in harper_core.token uses a type in harper_core.span.
The types involved
harper_core.token.Token → harper_core.span.Span
Direction
harper_core.token uses harper_core.span, so a change to harper_core.span can break harper_core.token, while a change to harper_core.token can't break harper_core.span.
Position
Below the diagonal: harper_core.token uses a module listed above it, which is the healthy direction.
harper_core.token uses harper_core.token_kind, so a change to harper_core.token_kind can break harper_core.token, while a change to harper_core.token can't break harper_core.token_kind.
Position
Below the diagonal: harper_core.token uses a module listed above it, which is the healthy direction.
harper_core.parsers uses harper_core.token, so a change to harper_core.token can break harper_core.parsers, while a change to harper_core.parsers can't break harper_core.token.
Position
Below the diagonal: harper_core.parsers uses a module listed above it, which is the healthy direction.
harper_desktop.rect uses harper_core.linting.suggestion, so a change to harper_core.linting.suggestion can break harper_desktop.rect, while a change to harper_desktop.rect can't break harper_core.linting.suggestion.
Position
Below the diagonal: harper_desktop.rect uses a module listed above it, which is the healthy direction.
harper_desktop.rect uses harper_core.linting.lint, so a change to harper_core.linting.lint can break harper_desktop.rect, while a change to harper_desktop.rect can't break harper_core.linting.lint.
Position
Below the diagonal: harper_desktop.rect uses a module listed above it, which is the healthy direction.
harper_core.parsers.markdown uses harper_core.token, so a change to harper_core.token can break harper_core.parsers.markdown, while a change to harper_core.parsers.markdown can't break harper_core.token.
Position
Below the diagonal: harper_core.parsers.markdown uses a module listed above it, which is the healthy direction.
harper_core.parsers.markdown uses harper_core.parsers, so a change to harper_core.parsers can break harper_core.parsers.markdown, while a change to harper_core.parsers.markdown can't break harper_core.parsers.
Position
Below the diagonal: harper_core.parsers.markdown uses a module listed above it, which is the healthy direction.
harper_desktop.highlighter.render_state.render_lint_card uses harper_core.linting.lint_kind, so a change to harper_core.linting.lint_kind can break harper_desktop.highlighter.render_state.render_lint_card, while a change to harper_desktop.highlighter.render_state.render_lint_card can't break harper_core.linting.lint_kind.
Position
Below the diagonal: harper_desktop.highlighter.render_state.render_lint_card uses a module listed above it, which is the healthy direction.
harper_desktop.highlighter.render_state.render_lint_card uses harper_core.linting.suggestion, so a change to harper_core.linting.suggestion can break harper_desktop.highlighter.render_state.render_lint_card, while a change to harper_desktop.highlighter.render_state.render_lint_card can't break harper_core.linting.suggestion.
Position
Below the diagonal: harper_desktop.highlighter.render_state.render_lint_card uses a module listed above it, which is the healthy direction.
harper_desktop.highlighter.render_state.render_lint_card uses harper_core.linting.lint, so a change to harper_core.linting.lint can break harper_desktop.highlighter.render_state.render_lint_card, while a change to harper_desktop.highlighter.render_state.render_lint_card can't break harper_core.linting.lint.
Position
Below the diagonal: harper_desktop.highlighter.render_state.render_lint_card uses a module listed above it, which is the healthy direction.
harper_desktop.highlighter.render_state.render_lint_card uses harper_desktop.rect, so a change to harper_desktop.rect can break harper_desktop.highlighter.render_state.render_lint_card, while a change to harper_desktop.highlighter.render_state.render_lint_card can't break harper_desktop.rect.
Position
Below the diagonal: harper_desktop.highlighter.render_state.render_lint_card uses a module listed above it, which is the healthy direction.
harper_core.document uses harper_core.span, so a change to harper_core.span can break harper_core.document, while a change to harper_core.document can't break harper_core.span.
Position
Below the diagonal: harper_core.document uses a module listed above it, which is the healthy direction.
harper_core.document uses harper_core.token, so a change to harper_core.token can break harper_core.document, while a change to harper_core.document can't break harper_core.token.
Position
Below the diagonal: harper_core.document uses a module listed above it, which is the healthy direction.
harper_core.document uses harper_core.parsers.markdown, so a change to harper_core.parsers.markdown can break harper_core.document, while a change to harper_core.document can't break harper_core.parsers.markdown.
Position
Below the diagonal: harper_core.document uses a module listed above it, which is the healthy direction.
harper_core.dict_word_metadata uses harper_pos_utils.upos, so a change to harper_pos_utils.upos can break harper_core.dict_word_metadata, while a change to harper_core.dict_word_metadata can't break harper_pos_utils.upos.
Position
Below the diagonal: harper_core.dict_word_metadata uses a module listed above it, which is the healthy direction.
harper_core.dict_word_metadata uses harper_core.document, so a change to harper_core.document can break harper_core.dict_word_metadata, while a change to harper_core.dict_word_metadata can't break harper_core.document.
Position
Below the diagonal: harper_core.dict_word_metadata uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in harper_core.expr uses a type in harper_core.span.
The types involved
harper_core.expr.Expr → harper_core.span.Span
Direction
harper_core.expr uses harper_core.span, so a change to harper_core.span can break harper_core.expr, while a change to harper_core.expr can't break harper_core.span.
Position
Below the diagonal: harper_core.expr uses a module listed above it, which is the healthy direction.
harper_core.expr uses harper_core.expr.all, so a change to harper_core.expr.all can break harper_core.expr, while a change to harper_core.expr can't break harper_core.expr.all.
Position
Below the diagonal: harper_core.expr uses a module listed above it, which is the healthy direction.
harper_core.expr uses harper_core.expr.first_match_of, so a change to harper_core.expr.first_match_of can break harper_core.expr, while a change to harper_core.expr can't break harper_core.expr.first_match_of.
Position
Below the diagonal: harper_core.expr uses a module listed above it, which is the healthy direction.
harper_core.expr uses harper_core.expr.longest_match_of, so a change to harper_core.expr.longest_match_of can break harper_core.expr, while a change to harper_core.expr can't break harper_core.expr.longest_match_of.
Position
Below the diagonal: harper_core.expr uses a module listed above it, which is the healthy direction.
harper_core.expr uses harper_core.document, so a change to harper_core.document can break harper_core.expr, while a change to harper_core.expr can't break harper_core.document.
Position
Below the diagonal: harper_core.expr uses a module listed above it, which is the healthy direction.
harper_core.ignored_lints uses harper_core.linting.lint, so a change to harper_core.linting.lint can break harper_core.ignored_lints, while a change to harper_core.ignored_lints can't break harper_core.linting.lint.
Position
Below the diagonal: harper_core.ignored_lints uses a module listed above it, which is the healthy direction.
harper_core.ignored_lints uses harper_core.document, so a change to harper_core.document can break harper_core.ignored_lints, while a change to harper_core.ignored_lints can't break harper_core.document.
Position
Below the diagonal: harper_core.ignored_lints uses a module listed above it, which is the healthy direction.
harper_core.linting uses harper_core.linting.lint, so a change to harper_core.linting.lint can break harper_core.linting, while a change to harper_core.linting can't break harper_core.linting.lint.
Position
Below the diagonal: harper_core.linting uses a module listed above it, which is the healthy direction.
harper_core.linting uses harper_core.document, so a change to harper_core.document can break harper_core.linting, while a change to harper_core.linting can't break harper_core.document.
Position
Below the diagonal: harper_core.linting uses a module listed above it, which is the healthy direction.
harper_core.linting.expr_linter uses harper_core.linting.lint, so a change to harper_core.linting.lint can break harper_core.linting.expr_linter, while a change to harper_core.linting.expr_linter can't break harper_core.linting.lint.
Position
Below the diagonal: harper_core.linting.expr_linter uses a module listed above it, which is the healthy direction.
harper_core.linting.expr_linter uses harper_core.token, so a change to harper_core.token can break harper_core.linting.expr_linter, while a change to harper_core.linting.expr_linter can't break harper_core.token.
Position
Below the diagonal: harper_core.linting.expr_linter uses a module listed above it, which is the healthy direction.
harper_core.linting.expr_linter uses harper_core.document, so a change to harper_core.document can break harper_core.linting.expr_linter, while a change to harper_core.linting.expr_linter can't break harper_core.document.
Position
Below the diagonal: harper_core.linting.expr_linter uses a module listed above it, which is the healthy direction.
harper_core.patterns uses harper_core.span, so a change to harper_core.span can break harper_core.patterns, while a change to harper_core.patterns can't break harper_core.span.
Position
Below the diagonal: harper_core.patterns uses a module listed above it, which is the healthy direction.
harper_core.patterns uses harper_core.token, so a change to harper_core.token can break harper_core.patterns, while a change to harper_core.patterns can't break harper_core.token.
Position
Below the diagonal: harper_core.patterns uses a module listed above it, which is the healthy direction.
harper_core.patterns uses harper_core.document, so a change to harper_core.document can break harper_core.patterns, while a change to harper_core.patterns can't break harper_core.document.
Position
Below the diagonal: harper_core.patterns uses a module listed above it, which is the healthy direction.
harper_cli.lint uses harper_core.linting.lint_kind, so a change to harper_core.linting.lint_kind can break harper_cli.lint, while a change to harper_cli.lint can't break harper_core.linting.lint_kind.
Position
Below the diagonal: harper_cli.lint uses a module listed above it, which is the healthy direction.
harper_cli.lint uses harper_core.parsers.markdown, so a change to harper_core.parsers.markdown can break harper_cli.lint, while a change to harper_cli.lint can't break harper_core.parsers.markdown.
Position
Below the diagonal: harper_cli.lint uses a module listed above it, which is the healthy direction.
harper_cli.lint uses harper_core.document, so a change to harper_core.document can break harper_cli.lint, while a change to harper_cli.lint can't break harper_core.document.
Position
Below the diagonal: harper_cli.lint uses a module listed above it, which is the healthy direction.
harper_cli.lint uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_cli.lint, while a change to harper_cli.lint can't break harper_core.dict_word_metadata.
Position
Below the diagonal: harper_cli.lint uses a module listed above it, which is the healthy direction.
harper_core.expr.expr_map uses harper_core.span, so a change to harper_core.span can break harper_core.expr.expr_map, while a change to harper_core.expr.expr_map can't break harper_core.span.
Position
Below the diagonal: harper_core.expr.expr_map uses a module listed above it, which is the healthy direction.
harper_core.expr.expr_map uses harper_core.expr, so a change to harper_core.expr can break harper_core.expr.expr_map, while a change to harper_core.expr.expr_map can't break harper_core.expr.
Position
Below the diagonal: harper_core.expr.expr_map uses a module listed above it, which is the healthy direction.
harper_core.expr.sequence_expr uses harper_core.span, so a change to harper_core.span can break harper_core.expr.sequence_expr, while a change to harper_core.expr.sequence_expr can't break harper_core.span.
Position
Below the diagonal: harper_core.expr.sequence_expr uses a module listed above it, which is the healthy direction.
harper_core.expr.sequence_expr uses harper_core.token_kind, so a change to harper_core.token_kind can break harper_core.expr.sequence_expr, while a change to harper_core.expr.sequence_expr can't break harper_core.token_kind.
Position
Below the diagonal: harper_core.expr.sequence_expr uses a module listed above it, which is the healthy direction.
harper_core.expr.sequence_expr uses harper_core.expr, so a change to harper_core.expr can break harper_core.expr.sequence_expr, while a change to harper_core.expr.sequence_expr can't break harper_core.expr.
Position
Below the diagonal: harper_core.expr.sequence_expr uses a module listed above it, which is the healthy direction.
harper_core.linting.lint_group uses harper_core.linting.lint_group.flat_config, so a change to harper_core.linting.lint_group.flat_config can break harper_core.linting.lint_group, while a change to harper_core.linting.lint_group can't break harper_core.linting.lint_group.flat_config.
Position
Below the diagonal: harper_core.linting.lint_group uses a module listed above it, which is the healthy direction.
harper_core.linting.lint_group uses harper_core.linting.lint, so a change to harper_core.linting.lint can break harper_core.linting.lint_group, while a change to harper_core.linting.lint_group can't break harper_core.linting.lint.
Position
Below the diagonal: harper_core.linting.lint_group uses a module listed above it, which is the healthy direction.
harper_core.linting.lint_group uses harper_core.document, so a change to harper_core.document can break harper_core.linting.lint_group, while a change to harper_core.linting.lint_group can't break harper_core.document.
Position
Below the diagonal: harper_core.linting.lint_group uses a module listed above it, which is the healthy direction.
harper_core.linting.lint_group uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_core.linting.lint_group, while a change to harper_core.linting.lint_group can't break harper_core.dict_word_metadata.
Position
Below the diagonal: harper_core.linting.lint_group uses a module listed above it, which is the healthy direction.
harper_core.linting.lint_group uses harper_core.linting, so a change to harper_core.linting can break harper_core.linting.lint_group, while a change to harper_core.linting.lint_group can't break harper_core.linting.
Position
Below the diagonal: harper_core.linting.lint_group uses a module listed above it, which is the healthy direction.
harper_core.patterns.word_set uses harper_core.token, so a change to harper_core.token can break harper_core.patterns.word_set, while a change to harper_core.patterns.word_set can't break harper_core.token.
Position
Below the diagonal: harper_core.patterns.word_set uses a module listed above it, which is the healthy direction.
harper_core.patterns.word_set uses harper_core.patterns, so a change to harper_core.patterns can break harper_core.patterns.word_set, while a change to harper_core.patterns.word_set can't break harper_core.patterns.
Position
Below the diagonal: harper_core.patterns.word_set uses a module listed above it, which is the healthy direction.
harper_core.spell.dictionary uses harper_core.spell.word_id.canonical_word_id, so a change to harper_core.spell.word_id.canonical_word_id can break harper_core.spell.dictionary, while a change to harper_core.spell.dictionary can't break harper_core.spell.word_id.canonical_word_id.
Position
Below the diagonal: harper_core.spell.dictionary uses a module listed above it, which is the healthy direction.
harper_core.spell.dictionary uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_core.spell.dictionary, while a change to harper_core.spell.dictionary can't break harper_core.dict_word_metadata.
Position
Below the diagonal: harper_core.spell.dictionary uses a module listed above it, which is the healthy direction.
harper_core.linting.gonna_gotta_wanna uses harper_core.linting.lint, so a change to harper_core.linting.lint can break harper_core.linting.gonna_gotta_wanna, while a change to harper_core.linting.gonna_gotta_wanna can't break harper_core.linting.lint.
Position
Below the diagonal: harper_core.linting.gonna_gotta_wanna uses a module listed above it, which is the healthy direction.
harper_core.linting.gonna_gotta_wanna uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_core.linting.gonna_gotta_wanna, while a change to harper_core.linting.gonna_gotta_wanna can't break harper_core.dict_word_metadata.
Position
Below the diagonal: harper_core.linting.gonna_gotta_wanna uses a module listed above it, which is the healthy direction.
harper_core.linting.gonna_gotta_wanna uses harper_core.linting.expr_linter, so a change to harper_core.linting.expr_linter can break harper_core.linting.gonna_gotta_wanna, while a change to harper_core.linting.gonna_gotta_wanna can't break harper_core.linting.expr_linter.
Position
Below the diagonal: harper_core.linting.gonna_gotta_wanna uses a module listed above it, which is the healthy direction.
harper_core.linting.gonna_gotta_wanna uses harper_core.expr.sequence_expr, so a change to harper_core.expr.sequence_expr can break harper_core.linting.gonna_gotta_wanna, while a change to harper_core.linting.gonna_gotta_wanna can't break harper_core.expr.sequence_expr.
Position
Below the diagonal: harper_core.linting.gonna_gotta_wanna uses a module listed above it, which is the healthy direction.
harper_core.linting.gonna_gotta_wanna uses harper_core.linting.lint_group, so a change to harper_core.linting.lint_group can break harper_core.linting.gonna_gotta_wanna, while a change to harper_core.linting.gonna_gotta_wanna can't break harper_core.linting.lint_group.
Position
Below the diagonal: harper_core.linting.gonna_gotta_wanna uses a module listed above it, which is the healthy direction.
harper_core.spell.merged_dictionary uses harper_core.spell.word_id.canonical_word_id, so a change to harper_core.spell.word_id.canonical_word_id can break harper_core.spell.merged_dictionary, while a change to harper_core.spell.merged_dictionary can't break harper_core.spell.word_id.canonical_word_id.
Position
Below the diagonal: harper_core.spell.merged_dictionary uses a module listed above it, which is the healthy direction.
harper_core.spell.merged_dictionary uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_core.spell.merged_dictionary, while a change to harper_core.spell.merged_dictionary can't break harper_core.dict_word_metadata.
Position
Below the diagonal: harper_core.spell.merged_dictionary uses a module listed above it, which is the healthy direction.
harper_core.spell.merged_dictionary uses harper_core.spell.dictionary, so a change to harper_core.spell.dictionary can break harper_core.spell.merged_dictionary, while a change to harper_core.spell.merged_dictionary can't break harper_core.spell.dictionary.
Position
Below the diagonal: harper_core.spell.merged_dictionary uses a module listed above it, which is the healthy direction.
harper_core.spell.mutable_dictionary uses harper_core.spell.word_id.canonical_word_id, so a change to harper_core.spell.word_id.canonical_word_id can break harper_core.spell.mutable_dictionary, while a change to harper_core.spell.mutable_dictionary can't break harper_core.spell.word_id.canonical_word_id.
Position
Below the diagonal: harper_core.spell.mutable_dictionary uses a module listed above it, which is the healthy direction.
harper_core.spell.mutable_dictionary uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_core.spell.mutable_dictionary, while a change to harper_core.spell.mutable_dictionary can't break harper_core.dict_word_metadata.
Position
Below the diagonal: harper_core.spell.mutable_dictionary uses a module listed above it, which is the healthy direction.
harper_core.spell.mutable_dictionary uses harper_core.spell.dictionary, so a change to harper_core.spell.dictionary can break harper_core.spell.mutable_dictionary, while a change to harper_core.spell.mutable_dictionary can't break harper_core.spell.dictionary.
Position
Below the diagonal: harper_core.spell.mutable_dictionary uses a module listed above it, which is the healthy direction.
harper_core.spell.fst_dictionary uses harper_core.spell.word_id.canonical_word_id, so a change to harper_core.spell.word_id.canonical_word_id can break harper_core.spell.fst_dictionary, while a change to harper_core.spell.fst_dictionary can't break harper_core.spell.word_id.canonical_word_id.
Position
Below the diagonal: harper_core.spell.fst_dictionary uses a module listed above it, which is the healthy direction.
harper_core.spell.fst_dictionary uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_core.spell.fst_dictionary, while a change to harper_core.spell.fst_dictionary can't break harper_core.dict_word_metadata.
Position
Below the diagonal: harper_core.spell.fst_dictionary uses a module listed above it, which is the healthy direction.
harper_core.spell.fst_dictionary uses harper_core.spell.dictionary, so a change to harper_core.spell.dictionary can break harper_core.spell.fst_dictionary, while a change to harper_core.spell.fst_dictionary can't break harper_core.spell.dictionary.
Position
Below the diagonal: harper_core.spell.fst_dictionary uses a module listed above it, which is the healthy direction.
harper_core.spell.fst_dictionary uses harper_core.spell.mutable_dictionary, so a change to harper_core.spell.mutable_dictionary can break harper_core.spell.fst_dictionary, while a change to harper_core.spell.fst_dictionary can't break harper_core.spell.mutable_dictionary.
Position
Below the diagonal: harper_core.spell.fst_dictionary uses a module listed above it, which is the healthy direction.
harper_desktop.config uses harper_core.linting.lint_group.flat_config, so a change to harper_core.linting.lint_group.flat_config can break harper_desktop.config, while a change to harper_desktop.config can't break harper_core.linting.lint_group.flat_config.
Position
Below the diagonal: harper_desktop.config uses a module listed above it, which is the healthy direction.
harper_desktop.config uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_desktop.config, while a change to harper_desktop.config can't break harper_core.dict_word_metadata.
Position
Below the diagonal: harper_desktop.config uses a module listed above it, which is the healthy direction.
harper_desktop.config uses harper_core.ignored_lints, so a change to harper_core.ignored_lints can break harper_desktop.config, while a change to harper_desktop.config can't break harper_core.ignored_lints.
Position
Below the diagonal: harper_desktop.config uses a module listed above it, which is the healthy direction.
harper_desktop.config uses harper_core.linting.lint_group, so a change to harper_core.linting.lint_group can break harper_desktop.config, while a change to harper_desktop.config can't break harper_core.linting.lint_group.
Position
Below the diagonal: harper_desktop.config uses a module listed above it, which is the healthy direction.
harper_desktop.config uses harper_core.spell.merged_dictionary, so a change to harper_core.spell.merged_dictionary can break harper_desktop.config, while a change to harper_desktop.config can't break harper_core.spell.merged_dictionary.
Position
Below the diagonal: harper_desktop.config uses a module listed above it, which is the healthy direction.
harper_desktop.config uses harper_core.spell.mutable_dictionary, so a change to harper_core.spell.mutable_dictionary can break harper_desktop.config, while a change to harper_desktop.config can't break harper_core.spell.mutable_dictionary.
Position
Below the diagonal: harper_desktop.config uses a module listed above it, which is the healthy direction.
harper_wasm uses harper_core.linting.suggestion, so a change to harper_core.linting.suggestion can break harper_wasm, while a change to harper_wasm can't break harper_core.linting.suggestion.
Position
Below the diagonal: harper_wasm uses a module listed above it, which is the healthy direction.
harper_wasm uses harper_core.linting.lint, so a change to harper_core.linting.lint can break harper_wasm, while a change to harper_wasm can't break harper_core.linting.lint.
Position
Below the diagonal: harper_wasm uses a module listed above it, which is the healthy direction.
harper_wasm uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_wasm, while a change to harper_wasm can't break harper_core.dict_word_metadata.
Position
Below the diagonal: harper_wasm uses a module listed above it, which is the healthy direction.
harper_wasm uses harper_core.ignored_lints, so a change to harper_core.ignored_lints can break harper_wasm, while a change to harper_wasm can't break harper_core.ignored_lints.
Position
Below the diagonal: harper_wasm uses a module listed above it, which is the healthy direction.
harper_wasm uses harper_core.linting.lint_group, so a change to harper_core.linting.lint_group can break harper_wasm, while a change to harper_wasm can't break harper_core.linting.lint_group.
Position
Below the diagonal: harper_wasm uses a module listed above it, which is the healthy direction.
harper_wasm uses harper_core.spell.merged_dictionary, so a change to harper_core.spell.merged_dictionary can break harper_wasm, while a change to harper_wasm can't break harper_core.spell.merged_dictionary.
Position
Below the diagonal: harper_wasm uses a module listed above it, which is the healthy direction.
harper_wasm uses harper_core.spell.mutable_dictionary, so a change to harper_core.spell.mutable_dictionary can break harper_wasm, while a change to harper_wasm can't break harper_core.spell.mutable_dictionary.
Position
Below the diagonal: harper_wasm uses a module listed above it, which is the healthy direction.
harper_desktop uses harper_core.dict_word_metadata, so a change to harper_core.dict_word_metadata can break harper_desktop, while a change to harper_desktop can't break harper_core.dict_word_metadata.
Position
Below the diagonal: harper_desktop uses a module listed above it, which is the healthy direction.
harper_desktop uses harper_core.ignored_lints, so a change to harper_core.ignored_lints can break harper_desktop, while a change to harper_desktop can't break harper_core.ignored_lints.
Position
Below the diagonal: harper_desktop uses a module listed above it, which is the healthy direction.
harper_desktop uses harper_core.linting.lint_group, so a change to harper_core.linting.lint_group can break harper_desktop, while a change to harper_desktop can't break harper_core.linting.lint_group.
Position
Below the diagonal: harper_desktop uses a module listed above it, which is the healthy direction.
harper_desktop uses harper_core.spell.mutable_dictionary, so a change to harper_core.spell.mutable_dictionary can break harper_desktop, while a change to harper_desktop can't break harper_core.spell.mutable_dictionary.
Position
Below the diagonal: harper_desktop uses a module listed above it, which is the healthy direction.
harper_desktop uses harper_desktop.config, so a change to harper_desktop.config can break harper_desktop, while a change to harper_desktop can't break harper_desktop.config.
Position
Below the diagonal: harper_desktop uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 56% · Adequate · gated by R7, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
172
High / Critical
A05:2025 — Injection
30
High / Critical
A02:2025 — Security Misconfiguration
10
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
First, ensure all interactive elements are fully keyboard-accessible and properly linked, while providing programmatic labels for every form control and button. Next, add descriptive text alternatives to all images, media, and canvas elements to support screen readers. Then, enable nullable reference types across all projects and resolve warnings directly instead of suppressing them. Finally, improve documentation quality by addressing findings in the README.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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 — 151
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 — 621
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 — 51
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 15
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 81 of 81 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 81 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 796 of 823 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the vitest suite in packages/components/ ran and not one test passed (Errors 1 error), so the coverage would describe the failed run, not the code — but the repository pins Node 24.15.0 in .nvmrc and the analyzer image ran it on Node 22, so the failure describes our runtime, not the suite. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 156 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 29 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the JavaScript/TypeScript suite (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/components/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/harper.js/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/obsidian-plugin/ (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Cargo manifest, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Cargo dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/lint-framework/src/lint/lintKindColor.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — db Pulling db Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: db Pulling db Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 133 further occurrence(s) are not listed individually; the score already reflects all 173.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 151 further occurrence(s) are not listed individually; the score already reflects all 191.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's C# was parsed (it ships no .sln or .csproj, so it was read as syntax-only projects), but this check proves its findings from resolved symbols and a reference-free parse resolves none. It abstained rather than report a clean bill it could not earn. That is a gap in this analyzer's reach into build-less repositories — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
45 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was harper_cli::main at 91. A further 11 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being AvoidContractions::expansion at 49 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: harper-core/src/linting/avoid_contractions.rs (AvoidContractions::expansion at 49), harper-core/src/punctuation.rs (Punctuation::from_char at 42), harper-comments/src/comment_parser.rs (CommentParser::new_from_language_id at 37), harper-core/src/linting/spelled_numbers.rs (harper_core::linting::spelled_numbers::spell_out_number at 35), harper-core/src/linting/lint_kind.rs (LintKind::from_string_key at 21), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 32 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with harper_cli::main (cyclomatic 91). — Refactoring it lifts Cyclomatic Complexity from 6.1 to about 6.5/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 48 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with harper_cli::main (cognitive 181). — Refactoring it lifts Cognitive Complexity from 5.4 to about 5.8/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.1 / 10Stronggated by 37 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 MethodTooLong finding(s) in God Classes — start with backend.rs (2), mod.rs, typst_translator.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 TooManyMethods finding(s) in God Classes — start with sequence_expr.rs, document.rs, dict_word_metadata.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 FileTooLong finding(s) in God Classes — start with mod.rs (2), main.rs, dict_word_metadata.rs. — One of this dimension's main actionable groups (8 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
81 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 39 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with dict_word_metadata.rs (2), mod.rs, one_of_the_singular.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), there_is_agreement.rs (2), merge_words.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 6 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with expand_memory_shorthands.rs, mod.rs, did_past.rs. — One of this dimension's main actionable groups (6 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.5 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
31 production modules (Cargo+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 6 module(s) off the main sequence, with abstractness counted on 27 of the 31 (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: harper-pos-utils · ×6
What to do
Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
7076 test methods: 7040 unit, 36 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 156 `it`/`test` case(s) across 30 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 6920 `#[test]` function(s) across 472 file(s) declaring at least one; its unit/integration split is Cargo's own — 16 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality7.1 / 10Strong✓ 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.
6 skipped, 22 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 156 tests. Measured on the JavaScript/TypeScript suite only — at least 29 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: ${linterName} can run setup without issues · ×22packages/harper.js/src/Linter.test.ts:208
Resolve the 22 No assertions finding(s) in Test Quality — start with google_docs.spec.ts (14), google_docs_live.spec.ts (3), Linter.test.ts. — One of this dimension's main actionable groups (22 warning-level).
Resolve the 6 Skipped test finding(s) in Test Quality — start with iframe_domain_inheritance.spec.ts, lexical_webcomponent.spec.ts, options_delay.spec.ts. — One of this dimension's main actionable groups (6 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
1 outdated direct gem(s), 0 pinning defect(s). 2 declaration(s) graded against rubygems.org, 1 of them against a version resolved in a committed Gemfile.lock. 1 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Outdated: fastlane
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 126 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 126 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Cargo manifest and REDACTED, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: harper-cli/src/main.rs (4×91=364); harper-core/src/linting/missing_to.rs (4×41=164); packages/chrome-plugin/src/contentScript/index.ts (3×30=90) Repeated repair below the complexity floor: packages/chrome-plugin/tests/testUtils.ts (4 of 6 changes were fixes); packages/web/src/lib/components/Loader.svelte (4 of 4 changes were fixes); packages/web/src/routes/+page.svelte (3 of 5 changes were fixes)
Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs (2), missing_to.rs, index.ts. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 Repeated repair finding(s) in Churn × Complexity Hotspots — start with testUtils.ts, Loader.svelte, +page.svelte. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor6.1 / 10Adequate✓ 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.
209 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is harper-core/src/linting/regionalisms.rs. Counted over 532 of the 760 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
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
76 deducted task-comment markers across 127089 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 76 TodoComment finding(s) in Explicit Debt — start with mod.rs (10), there_is_agreement.rs (10), update_place_names.rs (9). — One of this dimension's main actionable groups (76 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
0 of 1 documentation facets pass in full; short on: F2 example. 54 document(s) read across 1 unit(s).
Documentation: no build, run or usage exampleREADME.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
30 finding(s): 0 critical, 29 high, 1 medium, 0 low. 21 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 3 file(s) — `harper-brill/finished_chunker/vocab.json`, `harper-brill/trained_tagger_model.json`, `packages/lint-framework/src/lint/lintKindColor.ts` (line 29) — 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 2 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
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 21 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (21 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 74 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (73), REDACTED. — One of this dimension's main actionable groups (74 issue-level).
Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
6 of 532 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is harper-core/src/parsers/org_mode.rs. Counted over 532 of the 760 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 4 Change coupling finding(s) in Change Coupling — start with ProtocolClient.ts, LocalLinter.ts, backend.rs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with unclosed_quotes.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives5.1 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — packages/web/src/lib/components/BarChart.svelte:120, packages/web/src/lib/components/Loader.svelte:205
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels5.1 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×13) — harper-desktop/src/lib/settings/components/AppPickerModal.svelte:108, harper-desktop/src/lib/settings/pages/DictionaryPage.svelte:166, packages/chrome-plugin/src/popup/DomainReview.svelte:63, …
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×9) — harper-desktop/src/lib/settings/pages/RulesPage.svelte:382, harper-desktop/src/lib/settings/pages/RulesPage.svelte:407, harper-desktop/src/lib/settings/pages/WeirpacksPage.svelte:118, …
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×10) — packages/chrome-plugin/src/popup/DomainReview.svelte:62, packages/chrome-plugin/src/popup/DomainReview.svelte:72, packages/chrome-plugin/src/popup/DomainReview.svelte:109, …
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — packages/components/src/lib/Toggle.svelte:35
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×2) — packages/components/src/app.html:2, packages/harper-editor/src/app.html:2
An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. (×2) — packages/components/src/lib/Section.svelte:19, packages/components/src/lib/Section.svelte:43
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — packages/web/src/routes/presentation/+page.svelte:23, packages/web/src/routes/presentation/+page.svelte:43
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — harper-desktop/src/lib/settings/components/AppPickerModal.svelte:90, packages/harper-editor/src/lib/LintSidebar.svelte:354
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`:global(.DocSearch-Input:focus)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/web/src/lib/marketing/MarketingDocSearch.svelte:107
`.harper-editor-surface` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/harper-editor/src/lib/styles.css:58
`.harper-editor-surface:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/harper-editor/src/lib/styles.css:70
`.search-strip input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — harper-desktop/src/lib/settings/settings.css:462
`.animate-bigbounce` moves (`animation: bigbounce 1s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/web/src/app.css:186
`.animate-after-bigbounce::after` moves (`animation: bigbounce 1s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/web/src/app.css:190
`.progress-fill` moves (`transition: width 160ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — harper-desktop/src/lib/settings/settings.css:177
`.chevron` moves (`transition: transform 140ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — harper-desktop/src/lib/settings/settings.css:651
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 164 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`Linter` declares 37 required operations: `setup`, `lint`, `organizedLints`, `applySuggestion`, `isLikelyEnglish`, `isolateEnglish`, `getLintConfig`, `getDefaultLintConfigAsJSON`, `getDefaultLintConfig`, `getStructuredLintConfig`, `getStructuredLintConfigJSON`, `setLintConfig`, `getLintConfigAsJSON`, `setLintConfigWithJSON`, `getLintDescriptionsAsJSON`, `getLintDescriptions`, `getLintDescriptionsHTMLAsJSON`, `getLintDescriptionsHTML`, `toTitleCase`, `dispose`, `ignoreLint`, `ignoreLints`, `ignoreLintHash`, `exportIgnoredLints`, `importIgnoredLints`, `contextHash`, `clearIgnoredLints`, `clearWords`, `importWords`, `exportWords`, `getDialect`, `setDialect`, `summarizeStats`, `generateStatsFile`, `importStatsFile`, `loadWeirpackFromBlob`, `loadWeirpackFromBytes`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/harper.js/src/Linter.ts:14
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in 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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
713 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 17 of 33 project(s) that lack one — worth up to 1 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability5.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 3/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `harper-cli`, `harper-core`, `harper-desktop`, `packages/components`, `packages/harper-editor` and 1 more.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Dependabot is configured but does not watch `bundler` — 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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
P6 · Release Hygiene8.0 / 10Strong✓ 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.
The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
What to do
Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety10.0 / 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.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
8 duplicated blocks under packages/ have copies in at least two of the sibling directories chrome-plugin, lint-framework, obsidian-plugin, wordpress-plugin — 7 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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/chrome-plugin/public/google-docs-bridge.js:449
packages/chrome-plugin/public/google-docs-bridge.js:449 · packages/lint-framework/src/lint/computeLintBoxes/googleDocsUtilities.ts:84 — the two spans are one implementation copied and then locally edited — 693 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/chrome-plugin/public/google-docs-bridge.js:449
packages/lint-framework/src/lint/domUtils.ts:69 · packages/wordpress-plugin/src/harper/domUtils.ts:33 — the two spans are one implementation copied and then locally edited — 249 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/lint-framework/src/lint/domUtils.ts:69
harper-desktop/src/lib/settings/pages/DictionaryPage.svelte:31 · harper-desktop/src/lib/settings/pages/IntegrationsPage.svelte:42 — 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. — harper-desktop/src/lib/settings/pages/DictionaryPage.svelte:31
packages/harper.js/src/LocalLinter.ts:160 · packages/harper.js/src/WorkerLinter/index.ts:157 — the two spans are one implementation copied and then locally edited — 255 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/harper.js/src/LocalLinter.ts:160
harper-desktop/src/lib/settings/pages/GeneralPage.svelte:112 · harper-desktop/src/lib/settings/pages/IntegrationsPage.svelte:51 — 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. — harper-desktop/src/lib/settings/pages/GeneralPage.svelte:112
packages/lint-framework/src/lint/lintKindColor.ts:7 · packages/obsidian-plugin/src/lintKindColor.ts:3 — the two spans are one implementation copied and then locally edited — 103 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/lint-framework/src/lint/lintKindColor.ts:7
packages/web/src/routes/admin/ext-site-problems/[slug]/+page.server.ts:5 · packages/web/src/routes/admin/ext-uninstall-reasons/[slug]/+page.server.ts:5 · packages/web/src/routes/admin/problematic-lints/[slug]/+page.server.ts:5 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — packages/web/src/routes/admin/ext-site-problems/[slug]/+page.server.ts:5
packages/lint-framework/src/lint/computeLintBoxes/index.ts:218 · packages/lint-framework/src/lint/computeLintBoxes/index.ts:248 — 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/lint-framework/src/lint/computeLintBoxes/index.ts:218
packages/chrome-plugin/src/options/Options.svelte:166 · packages/chrome-plugin/src/options/StructuredRuleSettings.svelte:130 — 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/chrome-plugin/src/options/Options.svelte:166
packages/lint-framework/src/lint/Box.ts:2 · packages/wordpress-plugin/src/harper/Box.ts:1 — the two spans are one implementation copied and then locally edited — 100 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/lint-framework/src/lint/Box.ts:2
packages/harper.js/src/Linter.ts:86 · packages/harper.js/src/WorkerLinter/index.ts:145 — the two spans are one implementation copied and then locally edited — 190 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/harper.js/src/Linter.ts:86
packages/lint-framework/src/lint/domUtils.ts:12 · packages/wordpress-plugin/src/harper/domUtils.ts:11 — 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/lint-framework/src/lint/domUtils.ts:12
packages/components/src/lib/Input.svelte:44 · packages/components/src/lib/Select.svelte:25 — 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/components/src/lib/Input.svelte:44
packages/lint-framework/src/lint/computeLintBoxes/index.ts:105 · packages/lint-framework/src/lint/googleDocsAdapter.ts:141 — 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/lint-framework/src/lint/computeLintBoxes/index.ts:105
packages/wordpress-plugin/src/harper/LintListItem.tsx:12 · packages/wordpress-plugin/src/harper/SuggestionControl.tsx:69 — the two spans are one implementation copied and then locally edited — 140 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/wordpress-plugin/src/harper/LintListItem.tsx:12
packages/wordpress-plugin/src/harper/Logo.jsx:42 · packages/wordpress-plugin/src/harper/Logo.jsx:77 — 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/wordpress-plugin/src/harper/Logo.jsx:42
packages/chrome-plugin/src/options/StructuredRuleSettings.svelte:155 · packages/obsidian-plugin/src/HarperSettingTab.ts:500 — 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/chrome-plugin/src/options/StructuredRuleSettings.svelte:155
packages/lint-framework/src/lint/computeLintBoxes/index.ts:72 · packages/lint-framework/src/lint/googleDocsAdapter.ts:47 — 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/lint-framework/src/lint/computeLintBoxes/index.ts:72
packages/lint-framework/src/lint/editorUtils.ts:21 · packages/lint-framework/src/lint/editorUtils.ts:62 · packages/lint-framework/src/lint/editorUtils.ts:90 — all 3 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/lint-framework/src/lint/editorUtils.ts:21
packages/chrome-plugin/src/contentScript/index.ts:124 · packages/chrome-plugin/src/contentScript/index.ts:215 — 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/chrome-plugin/src/contentScript/index.ts:124
packages/obsidian-plugin/src/lint.ts:980 · packages/obsidian-plugin/src/lint.ts:998 — 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/obsidian-plugin/src/lint.ts:980
packages/web/src/lib/db/models/DomainReviews.ts:13 · packages/web/src/lib/db/models/UninstallFeedback.ts:13 — 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/web/src/lib/db/models/DomainReviews.ts:13
harper-desktop/src/lib/settings/pages/RulesPage.svelte:105 · harper-desktop/src/lib/settings/pages/RulesPage.svelte:131 — 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. — harper-desktop/src/lib/settings/pages/RulesPage.svelte:105
packages/chrome-plugin/src/options/Options.svelte:124 · packages/obsidian-plugin/src/textUtils.ts:2 — 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/chrome-plugin/src/options/Options.svelte:124
packages/chrome-plugin/src/popup/DomainReview.svelte:15 · packages/chrome-plugin/src/popup/ReportProblematicLint.svelte:10 — 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/chrome-plugin/src/popup/DomainReview.svelte:15
packages/components/src/lib/Checkbox.svelte:6 · packages/components/src/lib/Toggle.svelte: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/components/src/lib/Checkbox.svelte:6
harper-desktop/src/lib/settings/pages/DictionaryPage.svelte:130 · packages/web/src/routes/weir/studio/+page.svelte:352 — the two spans are one implementation copied and then locally edited — 53 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. — harper-desktop/src/lib/settings/pages/DictionaryPage.svelte:130
packages/chrome-plugin/public/google-docs-bridge.js:95 · packages/chrome-plugin/public/google-docs-bridge.js:105 — 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/chrome-plugin/public/google-docs-bridge.js:95
packages/wordpress-plugin/src/harper/useDialect.ts:9 · packages/wordpress-plugin/src/harper/useLintConfig.ts:12 — 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/wordpress-plugin/src/harper/useDialect.ts:9
harper-desktop/src/lib/EditorView.svelte:13 · packages/web/src/lib/createEditorLinter.ts:3 — 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. — harper-desktop/src/lib/EditorView.svelte:13
packages/chrome-plugin/public/google-docs-bridge.js:384 · packages/chrome-plugin/public/google-docs-bridge.js:393 — the two spans are one implementation copied and then locally edited — 73 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/chrome-plugin/public/google-docs-bridge.js:384
packages/components/src/lib/Checkbox.svelte:8 · packages/components/src/lib/IconButton.svelte:7 · packages/components/src/lib/Toggle.svelte:7 — 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/components/src/lib/Checkbox.svelte:8
packages/components/src/lib/Panel.svelte:2 · packages/components/src/lib/SettingRow.svelte:3 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/components/src/lib/Panel.svelte:2
packages/wordpress-plugin/src/harper/useDialect.ts:8 · packages/wordpress-plugin/src/harper/useIgnoredLintState.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/wordpress-plugin/src/harper/useDialect.ts:8
packages/wordpress-plugin/src/harper/useDialect.ts:8 · packages/wordpress-plugin/src/harper/useIgnoredLintState.ts:9 · packages/wordpress-plugin/src/harper/usePersonalDictionary.ts:11 — 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/wordpress-plugin/src/harper/useDialect.ts:8
packages/web/src/lib/marketing/SveltePressGlobalLayout.svelte:5 · packages/web/src/lib/marketing/SveltePressPageLayout.svelte:5 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — packages/web/src/lib/marketing/SveltePressGlobalLayout.svelte:5
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
packages/web/src/routes/+page.svelte:24 reaches into another package with a relative path (../../../../demo.md?raw) — import the package by name instead. — packages/web/src/routes/+page.svelte:24
packages/web/src/routes/languagedetection/+page.svelte:5 reaches into another package with a relative path (../../../../../demo.md?raw) — import the package by name instead. — packages/web/src/routes/languagedetection/+page.svelte:5
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.
renderLintBoxes has cyclomatic complexity 26 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/lint-framework/src/lint/Highlights.ts:62
buildRenderNodes has cyclomatic complexity 19 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. — packages/chrome-plugin/src/options/StructuredRuleSettings.svelte:201
(anonymous) has cyclomatic complexity 17 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/chrome-plugin/src/contentScript/index.ts:162
isVisible has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/lint-framework/src/lint/domUtils.ts:151
serializeArg 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/harper.js/src/Serializer.ts:51
localeToDialect has cyclomatic complexity 15 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/chrome-plugin/src/background/detectDialect.ts:17
getGoogleDocsHighlightRects has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/lint-framework/src/lint/computeLintBoxes/googleDocsUtilities.ts:235
buildRectSnapshot has cyclomatic complexity 13 and cognitive complexity 18; 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/chrome-plugin/src/contentScript/googleDocs.ts:434
initializeFromSettings has cyclomatic complexity 13 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/obsidian-plugin/src/State.ts:58
handleKeydown has cyclomatic complexity 13 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/chrome-plugin/src/options/Options.svelte:298
supportsCustomHighlights has cyclomatic complexity 13 and cognitive complexity 11; 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/lint-framework/src/lint/Highlights.ts:386
renderStructuredSettings has cyclomatic complexity 12 and cognitive complexity 20; 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/obsidian-plugin/src/HarperSettingTab.ts:320
computeLintBoxes has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/lint-framework/src/lint/computeLintBoxes/index.ts:28
buildLogicalSnapshot has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/chrome-plugin/src/contentScript/googleDocs.ts:365
positionMirror has cyclomatic complexity 12 and cognitive complexity 11; 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/lint-framework/src/lint/TextFieldRange.ts:125
isUpToDate has cyclomatic complexity 12 and cognitive complexity 9; 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/web/src/lib/marketing/versions.ts:15
requestLintUpdate has cyclomatic complexity 11 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 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/lint-framework/src/lint/LintFramework.ts:127
getCaretPosition has cyclomatic complexity 11 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 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/lint-framework/src/lint/editorUtils.ts:121
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files9.0 / 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.
packages/obsidian-plugin/src/lint.ts has 936 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/obsidian-plugin/src/lint.ts:1
packages/chrome-plugin/src/background/index.ts has 798 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/chrome-plugin/src/background/index.ts:1
packages/chrome-plugin/public/google-docs-bridge.js has 663 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/chrome-plugin/public/google-docs-bridge.js:1
packages/chrome-plugin/src/options/Options.svelte has 651 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/chrome-plugin/src/options/Options.svelte:1
packages/lint-framework/src/lint/SuggestionBox.ts has 569 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/lint-framework/src/lint/SuggestionBox.ts:1
packages/obsidian-plugin/src/HarperSettingTab.ts has 555 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/obsidian-plugin/src/HarperSettingTab.ts:1
packages/chrome-plugin/src/contentScript/googleDocs.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/chrome-plugin/src/contentScript/googleDocs.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage3.4 / 10Weak✓ 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. (×40) — packages/chrome-plugin/src/background/index.ts:1, packages/chrome-plugin/public/google-docs-bridge.js:1, packages/obsidian-plugin/src/HarperSettingTab.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED 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: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code2.5 / 10Critical✓ 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.
24 file(s) (~1241 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/wordpress-plugin
Unreachable from the 97 application, 26 tooling and 57 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 (97 application, 26 tooling, 57 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (harper-desktop/src/lib/settings/SettingsApp.svelte, harper-desktop/src/lib/settings/SettingsSidebar.svelte, harper-desktop/src/lib/settings/pages/GeneralPage.svelte 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 — harper-desktop/src/lib/settings/settings-data.ts
no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (harper-desktop/src/lib/settings/SettingsApp.svelte) — 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) — harper-desktop/src/lib/settings/pages/RulesPage.svelte, harper-desktop/src/lib/settings/pages/GeneralPage.svelte, harper-desktop/src/lib/settings/pages/GettingStartedPage.svelte, …
no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×22) — harper-desktop/src/lib/client.ts, packages/web/src/lib/components/Loader.svelte, packages/web/src/lib/components/LineChart.svelte, …
no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/web/src/lib/marketing/IntegrationTile.svelte, packages/web/src/lib/marketing/MarketingDocSearch.svelte, packages/web/src/lib/marketing/MarketingFooter.svelte 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 — packages/web/src/lib/marketing/data.ts
no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/web/src/lib/components/AnalyticsPage.svelte, packages/web/src/lib/components/LintKindChart.svelte) — 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 — packages/web/src/lib/components/BarChart.svelte
no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (harper-desktop/src/lib/settings/pages/IntegrationsPage.svelte) — 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 — harper-desktop/src/lib/settings/components/AppPickerModal.svelte
no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (harper-desktop/src/lib/settings/components/AppPickerModal.svelte, harper-desktop/src/lib/settings/pages/GettingStartedPage.svelte, harper-desktop/src/lib/settings/pages/IntegrationsPage.svelte) — 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 — harper-desktop/src/lib/settings/components/AppIcon.svelte
no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/components/src/lib/index.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 (×4) — packages/components/src/lib/DelayedRender.svelte, packages/components/src/lib/Checkbox.svelte, packages/components/src/lib/IconButton.svelte, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in packages/chrome-plugin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
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.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped3.5 / 10Weak✓ 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.
`this.shadowHost.outerHTML` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/lint-framework/src/lint/RenderBox.ts:77
`descriptionHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/obsidian-plugin/src/HarperSettingTab.ts:564
`lint.message_html()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/obsidian-plugin/src/State.ts:225
`state.hasEditorLinter()?logoSvg:logoSvgDisabled` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/obsidian-plugin/src/index.ts:134
`this.state.hasEditorLinter()?logoSvg:logoSvgDisabled` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/obsidian-plugin/src/index.ts:321
`this.getDialectStatus(dialect)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/obsidian-plugin/src/index.ts:325
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/1 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 8 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.
X9 Subsumed condition operand — 1 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 — 46 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.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — db Pulling db Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: db Pulling db Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D11 Test Reliability — No tests discovered
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 — Naming consistency is measured on C# only; Java, JavaScript, PHP, Python, Rust, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .php, .rs, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 9 value object(s); a Domain/Aggregates/ValueObjects layer
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable (this repository commits no MSBuild project, so its C# was read as syntax-only projects — a handler marked ONLY by an interface from a package is not visible without a build)
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — Drizzle is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
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 — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — 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
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
X27 Collection changed while being enumerated — This check needs a compiled C# program and this repository commits no project file to compile, so only its syntax could be read. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — 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
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
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.
AC2 · Forms & labels· <input> without a programmatic label · ×13
<input> without a programmatic label harper-desktop/src/lib/settings/components/AppPickerModal.svelte:108— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label harper-desktop/src/lib/settings/pages/DictionaryPage.svelte:166— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label harper-desktop/src/lib/settings/pages/WeirpacksPage.svelte:118— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label packages/chrome-plugin/src/popup/DomainReview.svelte:63— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/components/src/lib/Input.svelte:62— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/components/src/lib/SearchField.svelte:25— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/web/src/lib/components/WeirStudioFileExplorer.svelte:103— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label packages/web/src/routes/domain-review/+page.svelte:17— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/web/src/routes/domain-review/+page.svelte:28— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/web/src/routes/report-problematic-lint/+page.svelte:15— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/web/src/routes/report-problematic-lint/+page.svelte:22— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/web/src/routes/report-problematic-lint/+page.svelte:28— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/web/src/routes/uninstall-browser-extension/+page.svelte:47— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC2 · Forms & labels· <label> that labels no control · ×10
<label> that labels no control packages/chrome-plugin/src/popup/DomainReview.svelte:62— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/chrome-plugin/src/popup/DomainReview.svelte:72— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/chrome-plugin/src/popup/DomainReview.svelte:109— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web/src/routes/domain-review/+page.svelte:15— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web/src/routes/domain-review/+page.svelte:19— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web/src/routes/domain-review/+page.svelte:26— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web/src/routes/report-problematic-lint/+page.svelte:13— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web/src/routes/report-problematic-lint/+page.svelte:20— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web/src/routes/report-problematic-lint/+page.svelte:26— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web/src/routes/uninstall-browser-extension/+page.svelte:37— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC2 · Forms & labels· <select> without a programmatic label · ×5
<select> without a programmatic label harper-desktop/src/lib/settings/pages/RulesPage.svelte:382— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label harper-desktop/src/lib/settings/pages/RulesPage.svelte:407— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label packages/components/src/lib/Select.svelte:43— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label packages/web/src/routes/domain-review/+page.svelte:21— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label packages/web/src/routes/languagedetection/+page.svelte:62— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <textarea> without a programmatic label · ×4
<textarea> without a programmatic label packages/chrome-plugin/src/popup/DomainReview.svelte:110— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label packages/components/src/lib/Textarea.svelte:20— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label packages/web/src/routes/languagedetection/+page.svelte:64— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label packages/web/src/routes/titlecase/+page.svelte:74— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure· Document without a <title> · ×2
Document without a <title> packages/components/src/app.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> packages/harper-editor/src/app.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC2 · Forms & labels· <button> with no accessible text · ×1
<button> with no accessible text packages/components/src/lib/Toggle.svelte:35— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
TodoComment packages/wordpress-plugin/src/harper/useLintBoxes.ts:91— // TODO: revisit this to do more lazily. — 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 harper-wasm/src/lib.rs:68— // TODO: Have a way to configure the Markdown parser — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment harper-tree-sitter/src/lib.rs:26— // TODO: Use incremental parsing — 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 harper-core/src/case.rs:75— // TODO: maybe move this functionality to CharStringExt if and when CharStringExt can be — 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 harper-core/src/char_string.rs:7— // TODO: remove this when `SmallVec` allows retrieving this value in a const context. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment harper-core/src/dict_word_metadata.rs:950— // TODO other noun properties may be worth adding: abstract — 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 harper-core/src/dict_word_metadata.rs:983— // TODO for now focused on personal pronouns? — 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 harper-core/src/dict_word_metadata.rs:1996— // TODO: positive degree not implemented — 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 harper-core/src/document.rs:470— // TODO: Allow spaces between `a` and `b` — 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 harper-core/src/token_kind.rs:366— /// TODO: Separate this into two functions and add OR functionality to — 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 harper-core/src/linting/addicting.rs:18— // Semicolon is not handled like comma is for `Chunk` - TODO: remove when #3405 is fixed
TodoComment harper-core/src/linting/adjective_double_degree.rs:196— // TODO: special-case after "the" since that implies a superlative — 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 harper-core/src/linting/analog_acoustic_bike.rs:28— // TODO: address the optional indefinite article — 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 harper-core/src/linting/cease_to.rs:173— // TODO: maybe try looking for "have" in the before context? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment harper-core/src/linting/damages.rs:134— // TODO: this fails when "damages" is misuses in a diclaimer: — 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 harper-core/src/linting/damages.rs:210— // TODO: would the word "calculate" before "damages" be a good heuristic? — 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 harper-core/src/linting/despite_it_is.rs:242— // TODO: Freshwater Research Station is selectable as starting location despite having been removed by Dark Days of the Dead mod — 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 harper-core/src/linting/despite_it_is.rs:244— // TODO: Freshwater Research Station is selectable as starting location despite it having been removed by Dark Days of the Dead mod — 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 harper-core/src/linting/despite_it_is.rs:246— // TODO: Freshwater Research Station is selectable as starting location despite its having been removed by Dark Days of the Dead mod — 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 harper-core/src/linting/flesh_out_vs_full_fledged.rs:155— // TODO: only with "fully" and not "full"? — 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 harper-core/src/linting/looking_forward_to.rs:20— // TODO: update the use the verb with progressive tense function later — 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 harper-core/src/linting/looking_forward_to.rs:41— // TODO: create a util function to handle the appending of -ing — 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 harper-core/src/linting/mod.rs:893— // TODO verify sole suggestion is not the one we wanted fails — 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 harper-core/src/linting/mod.rs:905— // TODO verify many suggestions including the one we want succeeds — 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 harper-core/src/linting/mod.rs:906— // TODO verify many suggestions but not the one we want fails — 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.
+ 51 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file packages/chrome-plugin/src/background/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/chrome-plugin/public/google-docs-bridge.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/obsidian-plugin/src/HarperSettingTab.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/chrome-plugin/src/contentScript/googleDocs.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/web/src/routes/weir/studio/+page.svelte: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/chrome-plugin/src/options/Options.svelte: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/harper-editor/src/lib/editorDisplay.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/chrome-plugin/src/protocol.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/obsidian-plugin/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 harper-desktop/src/lib/settings/settings-data.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 harper-desktop/src/lib/settings/pages/RulesPage.svelte: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/harper-editor/src/lib/Editor.svelte: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/chrome-plugin/src/options/StructuredRuleSettings.svelte: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 harper-desktop/src/lib/client.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/web/src/lib/marketing/data.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 harper-desktop/src/lib/settings/pages/GeneralPage.svelte: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/obsidian-plugin/src/SidebarView.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/chrome-plugin/src/contentScript/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/chrome-plugin/src/contentScript/GoogleDocsBridgeClient.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/chrome-plugin/src/ProtocolClient.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/web/src/lib/components/Loader.svelte: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 harper-desktop/src/lib/settings/pages/GettingStartedPage.svelte: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 harper-desktop/src/lib/settings/pages/IntegrationsPage.svelte: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/harper-editor/src/lib/LintSidebar.svelte: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/web/src/routes/download-harper-desktop/[target]/[arch]/[current_version]/+server.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.
+ 15 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×32
No assertions: ${linterName} can run setup without issues packages/harper.js/src/Linter.test.ts:208— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: scales highlight offsets and widths with Google Docs zoom packages/chrome-plugin/tests/google_docs.spec.ts:485— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: lints the logical text across positioned formatting spans packages/chrome-plugin/tests/google_docs.spec.ts:521— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs restores spaces around formatted inline words packages/chrome-plugin/tests/google_docs.spec.ts:550— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs formatted rects stay in the same sentence packages/chrome-plugin/tests/google_docs.spec.ts:559— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs does not invent spaces around standalone punctuation rects packages/chrome-plugin/tests/google_docs.spec.ts:568— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs superscript-like rects do not create a fake line break packages/chrome-plugin/tests/google_docs.spec.ts:579— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs keeps soft wraps out of the logical bridge text packages/chrome-plugin/tests/google_docs.spec.ts:588— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs preserves paragraph breaks from annotated text packages/chrome-plugin/tests/google_docs.spec.ts:600— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs keeps numbered list markers with closing parentheses on single list lines packages/chrome-plugin/tests/google_docs.spec.ts:612— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs keeps NBSP-separated formatted inline words in the same sentence packages/chrome-plugin/tests/google_docs.spec.ts:628— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs does not invent spaces around em dash rects in fallback mode packages/chrome-plugin/tests/google_docs.spec.ts:638— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs keeps wide same-row fallback gaps in a single logical line packages/chrome-plugin/tests/google_docs.spec.ts:646— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs keeps column-major table rects in logical row order packages/chrome-plugin/tests/google_docs.spec.ts:654— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Google Docs repairs collapsed wrapped words from malformed logical text packages/chrome-plugin/tests/google_docs.spec.ts:663— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: keeps inline formatting in the same sentence (#2882) packages/chrome-plugin/tests/google_docs_live.spec.ts:225— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not misread bullet lists as headings (#2923) packages/chrome-plugin/tests/google_docs_live.spec.ts:266— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: preserves paragraph boundaries in the bridge text (#2959) packages/chrome-plugin/tests/google_docs_live.spec.ts:283— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: display lint kind colors packages/chrome-plugin/tests/lint-kinds.spec.ts:5— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: persists the delay setting in storage packages/chrome-plugin/tests/options_delay.spec.ts:12— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: category dropdown bulk updates constituent flat rules packages/chrome-plugin/tests/options_structured_rules.spec.ts:69— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Hides stale textarea highlights during lint delay when editing inside a lint packages/chrome-plugin/tests/simple_textarea.spec.ts:141— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
harper_core::linting::plural_decades::two_digits::match_to_lint_two_digits (cognitive 38) harper-core/src/linting/plural_decades/two_digits.rs:22— harper_core::linting::plural_decades::two_digits::match_to_lint_two_digits has cognitive complexity 38 (threshold 15). Drivers by points: if/else 22 (30 pts), boolean chains 8 (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.
harper_core::title_case::try_make_title_case (cognitive 37) harper-core/src/title_case.rs:71— harper_core::title_case::try_make_title_case has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 3 (9 pts), boolean chains 5 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harper_core::spell::is_ei_ie_misspelling (cognitive 30) harper-core/src/spell/mod.rs:247— harper_core::spell::is_ei_ie_misspelling has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (25 pts), boolean chains 4, loops 1 (nesting depth added 16). 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.
harper_core::indefinite_article::starts_with_vowel (cognitive 28) harper-core/src/indefinite_article.rs:21— harper_core::indefinite_article::starts_with_vowel has cognitive complexity 28 (threshold 15). Drivers by points: if/else 23 (24 pts), boolean chains 3, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
harper_core::lexing::email_address::validate_local_part (cognitive 28) harper-core/src/lexing/email_address.rs:49— harper_core::lexing::email_address::validate_local_part has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harper_core::linting::vice_versa::replacement_for (cognitive 26) harper-core/src/linting/vice_versa.rs:10— harper_core::linting::vice_versa::replacement_for has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harper_core::spell::score_suggestion (cognitive 26) harper-core/src/spell/mod.rs:295— harper_core::spell::score_suggestion has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 10, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
harper_core::linting::regular_irregulars::handle_plural_nouns (cognitive 25) harper-core/src/linting/regular_irregulars.rs:128— harper_core::linting::regular_irregulars::handle_plural_nouns has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (25 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harper_core::weir::parsing::stmt::parse_stmt (cognitive 22) harper-core/src/weir/parsing/stmt.rs:75— harper_core::weir::parsing::stmt::parse_stmt has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (19 pts), match/switch 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harper_core::spell::is_cksz_misspelling (cognitive 21) harper-core/src/spell/mod.rs:85— harper_core::spell::is_cksz_misspelling has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 7, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harper_core::spell::is_ou_misspelling (cognitive 19) harper-core/src/spell/mod.rs:41— harper_core::spell::is_ou_misspelling has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (harper_core::spell::is_ll_misspelling) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
harper_core::spell::is_ll_misspelling (cognitive 19) harper-core/src/spell/mod.rs:154— harper_core::spell::is_ll_misspelling has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (harper_core::spell::is_ou_misspelling) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
harper_core::spell::is_ay_ey_misspelling (cognitive 18) harper-core/src/spell/mod.rs:204— harper_core::spell::is_ay_ey_misspelling has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 4, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harper_core::lexing::lex_regexish (cognitive 16) harper-core/src/lexing/mod.rs:151— harper_core::lexing::lex_regexish has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harper_core::linting::criteria_phenomena::plural_criterion_phenomenon::modifier_number (cognitive 16) harper-core/src/linting/criteria_phenomena/plural_criterion_phenomenon.rs:105— harper_core::linting::criteria_phenomena::plural_criterion_phenomenon::modifier_number has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), match/switch 2 (4 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×13
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×12
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×11
MethodTooLong: LintGroup.new_curated harper-core/src/linting/lint_group/mod.rs:588— MethodTooLong — new_curated runs 380 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 280 over it, 3.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TypstTranslator.parse_expr harper-typst/src/typst_translator.rs:195— MethodTooLong — parse_expr runs 185 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AvoidCurses.match_to_lint harper-core/src/linting/avoid_curses.rs:27— MethodTooLong — match_to_lint runs 150 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DictWordMetadata.enforce_pos_exclusivity harper-core/src/dict_word_metadata.rs:199— MethodTooLong — enforce_pos_exclusivity runs 144 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HarperSettingTab.display packages/obsidian-plugin/src/HarperSettingTab.ts:71— MethodTooLong — display runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Backend.update_document harper-ls/src/backend.rs:243— MethodTooLong — update_document runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PhrasalVerbAsCompoundNoun.analyse harper-core/src/linting/phrasal_verb_as_compound_noun.rs:63— MethodTooLong — analyse runs 125 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MissingTo.match_to_lint_with_context harper-core/src/linting/missing_to.rs:374— MethodTooLong — match_to_lint_with_context runs 115 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Backend.execute_command harper-ls/src/backend.rs:708— MethodTooLong — execute_command runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
TooManyMethods: SequenceExpr harper-core/src/expr/sequence_expr.rs:11— TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Document harper-core/src/document.rs:18— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DictWordMetadata harper-core/src/dict_word_metadata.rs:22— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TokenKind harper-core/src/token_kind.rs:36— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WorkerLinter packages/harper.js/src/WorkerLinter/index.ts:21— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. Most of these members implement Linter.Linter (37 of 41 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: LocalLinter packages/harper.js/src/LocalLinter.ts:39— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. Most of these members implement Linter.Linter (37 of 39 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: Client harper-desktop/src/lib/client.ts:61— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Linter harper-wasm/src/lib.rs:111— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: phrase_set_corrections/mod.rs harper-core/src/linting/phrase_set_corrections/mod.rs— FileTooLong — 1002 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 502 over it, 2.00× 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: lint_group/mod.rs harper-core/src/linting/lint_group/mod.rs— FileTooLong — 950 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 62% of them inside a single declaration: LintGroup (4 blocks, 378-1152). The bar is 500 significant lines; this is 450 over it, 1.90× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/main.rs harper-cli/src/main.rs— FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 206 over it, 1.41× 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/dict_word_metadata.rs harper-core/src/dict_word_metadata.rs— FileTooLong — 703 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: DictWordMetadata (2 blocks, 22-869). The bar is 500 significant lines; this is 203 over it, 1.41× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lint.ts packages/obsidian-plugin/src/lint.ts— FileTooLong — 681 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 181 over it, 1.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/backend.rs harper-ls/src/backend.rs— FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 92% of them inside a single declaration: Backend (3 blocks, 55-920). The bar is 500 significant lines; this is 115 over it, 1.23× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/document.rs harper-core/src/document.rs— FileTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 98% of them inside a single declaration: Document (5 blocks, 18-949). The bar is 500 significant lines; this is 52 over it, 1.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: render_state/render_lint_card.rs harper-desktop/src-tauri/src/highlighter/render_state/render_lint_card.rs— FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 9 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (10 lines × 2) harper-core/src/dict_word_metadata.rs:220— harper-core/src/dict_word_metadata.rs:220-229 | harper-core/src/dict_word_metadata.rs:260-269 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) harper-core/src/dict_word_metadata.rs:261— harper-core/src/dict_word_metadata.rs:261-270 | harper-core/src/dict_word_metadata.rs:283-292 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) harper-core/src/linting/lint_group/mod.rs:1081— harper-core/src/linting/lint_group/mod.rs:1081-1090 | harper-core/src/linting/lint_group/mod.rs:1114-1123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) harper-core/src/linting/one_of_the_singular.rs:112— harper-core/src/linting/one_of_the_singular.rs:112-121 | harper-core/src/linting/one_of_the_singular.rs:125-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) harper-core/src/linting/plural_decades/four_digits.rs:27— harper-core/src/linting/plural_decades/four_digits.rs:27-36 | harper-core/src/linting/plural_decades/four_digits.rs:40-49 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) harper-core/src/linting/there_is_agreement.rs:281— harper-core/src/linting/there_is_agreement.rs:281-292 | harper-core/src/linting/there_is_agreement.rs:352-361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) harper-desktop/src-tauri/src/mac_broker/accessibility_activation.rs:142— harper-desktop/src-tauri/src/mac_broker/accessibility_activation.rs:142-151 | harper-desktop/src-tauri/src/mac_broker/core_foundation_utilities.rs:43-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) harper-desktop/src-tauri/src/mac_broker/app_catalog.rs:102— harper-desktop/src-tauri/src/mac_broker/app_catalog.rs:102-111 | harper-desktop/src-tauri/src/mac_broker/app_icons.rs:69-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) harper-core/src/linting/lint_group/mod.rs:1066— harper-core/src/linting/lint_group/mod.rs:1066-1073 | harper-core/src/linting/lint_group/mod.rs:1099-1106 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) harper-core/src/linting/merge_words.rs:54— harper-core/src/linting/merge_words.rs:54-61 | harper-core/src/linting/merge_words.rs:71-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) harper-core/src/linting/orthographic_consistency.rs:109— harper-core/src/linting/orthographic_consistency.rs:109-116 | harper-core/src/linting/orthographic_consistency.rs:126-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) harper-core/src/linting/there_is_agreement.rs:269— harper-core/src/linting/there_is_agreement.rs:269-276 | harper-core/src/linting/there_is_agreement.rs:432-439 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) harper-core/src/spell/mod.rs:264— harper-core/src/spell/mod.rs:264-271 | harper-core/src/spell/mod.rs:279-286 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) harper-core/src/weir/parsing/stmt.rs:178— harper-core/src/weir/parsing/stmt.rs:178-185 | harper-core/src/weir/parsing/stmt.rs:196-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) harper-core/src/linting/there_is_agreement.rs:381— harper-core/src/linting/there_is_agreement.rs:381-388 | harper-core/src/linting/there_is_agreement.rs:478-485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) harper-core/src/irregular_nouns.rs:29— harper-core/src/irregular_nouns.rs:29-36 | harper-core/src/irregular_verbs.rs:28-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Hotspot: harper-cli/src/main.rs harper-cli/src/main.rs:248— harper-cli/src/main.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 91 in harper_cli::main at line 248. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- harper-cli/src/main.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: harper-core/src/linting/missing_to.rs harper-core/src/linting/missing_to.rs:374— harper-core/src/linting/missing_to.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in MissingTo::match_to_lint_with_context at line 374. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- harper-core/src/linting/missing_to.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/chrome-plugin/src/contentScript/index.ts packages/chrome-plugin/src/contentScript/index.ts:95— packages/chrome-plugin/src/contentScript/index.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in index.scan at line 95. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- packages/chrome-plugin/src/contentScript/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: harper-comments/src/comment_parser.rs harper-comments/src/comment_parser.rs:21— harper-comments/src/comment_parser.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in CommentParser::new_from_language_id at line 21. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- harper-comments/src/comment_parser.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: harper-desktop/src-tauri/src/main.rs harper-desktop/src-tauri/src/main.rs:244— harper-desktop/src-tauri/src/main.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in harper_desktop::run_highlighter at line 244. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- harper-desktop/src-tauri/src/main.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: harper-desktop/src-tauri/src/communication/server.rs harper-desktop/src-tauri/src/communication/server.rs:44— harper-desktop/src-tauri/src/communication/server.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in Server::handle_request at line 44. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- harper-desktop/src-tauri/src/communication/server.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: harper-core/src/linting/orthographic_consistency.rs harper-core/src/linting/orthographic_consistency.rs:41— harper-core/src/linting/orthographic_consistency.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in OrthographicConsistency::match_to_lint_with_context at line 41. 1 of those changes was a fix/bug commit, 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- harper-core/src/linting/orthographic_consistency.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FunctionTooLong: harper_core::linting::phrase_set_corrections::lint_group harper-core/src/linting/phrase_set_corrections/mod.rs:11— FunctionTooLong — harper_core::linting::phrase_set_corrections::lint_group runs 1000 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 900 over it, 10.00× 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: harper_cli::main harper-cli/src/main.rs:248— FunctionTooLong — harper_cli::main runs 533 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 433 over it, 5.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: harper_desktop::run_highlighter harper-desktop/src-tauri/src/main.rs:244— FunctionTooLong — harper_desktop::run_highlighter runs 162 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: harper_cli::lint::lint harper-cli/src/lint.rs:173— FunctionTooLong — harper_cli::lint::lint runs 125 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Logo.Logo packages/wordpress-plugin/src/harper/Logo.jsx:1— FunctionTooLong — Logo runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: harper_cli::lint_engine::lint_one_input harper-cli/src/lint_engine.rs:24— FunctionTooLong — harper_cli::lint_engine::lint_one_input runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (9 lines × 2) harper-core/src/linting/expand_memory_shorthands.rs:20— harper-core/src/linting/expand_memory_shorthands.rs:20-28 | harper-core/src/linting/expand_time_shorthands.rs:19-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) harper-desktop/src-tauri/src/highlighter/render_state/mod.rs:236— harper-desktop/src-tauri/src/highlighter/render_state/mod.rs:236-244 | harper-desktop/src-tauri/src/highlighter/render_state/mod.rs:251-259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) harper-core/src/linting/did_past.rs:34— harper-core/src/linting/did_past.rs:34-42 | harper-core/src/linting/helped_past.rs:33-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) harper-core/src/linting/first_aid_kit.rs:33— harper-core/src/linting/first_aid_kit.rs:33-41 | harper-core/src/linting/pronoun_knew.rs:63-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) harper-core/src/linting/free_predicate.rs:48— harper-core/src/linting/free_predicate.rs:48-56 | harper-core/src/linting/respond.rs:65-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) harper-core/src/linting/quite_quiet.rs:76— harper-core/src/linting/quite_quiet.rs:76-84 | harper-core/src/linting/quite_quiet.rs:102-110 — 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.
Off the main sequence: harper-pos-utils — harper-pos-utils: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: harper-tree-sitter — harper-tree-sitter: abstractness 0.00, instability 0.11, distance 0.89 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: harper-core — harper-core: abstractness 0.06, instability 0.11, distance 0.83 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
Off the main sequence: harper.js — harper.js: abstractness 0.21, instability 0.00, distance 0.79 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: harper-stats — harper-stats: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: harper-typst — harper-typst: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×6
Untrusted text written into markup unescaped packages/lint-framework/src/lint/RenderBox.ts:77— `this.shadowHost.outerHTML` is text this program did not author, and it is written into the text of an element through `outerHTML` 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/obsidian-plugin/src/HarperSettingTab.ts:564— `descriptionHTML` 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/obsidian-plugin/src/State.ts:225— `lint.message_html()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/obsidian-plugin/src/index.ts:134— `state.hasEditorLinter()?logoSvg:logoSvgDisabled` 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/obsidian-plugin/src/index.ts:321— `this.state.hasEditorLinter()?logoSvg:logoSvgDisabled` 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/obsidian-plugin/src/index.ts:325— `this.getDialectStatus(dialect)` 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.
harper_core::linting::plural_decades::two_digits::match_to_lint_two_digits (cyclomatic 30) harper-core/src/linting/plural_decades/two_digits.rs:22— harper_core::linting::plural_decades::two_digits::match_to_lint_two_digits has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
harper_core::indefinite_article::starts_with_vowel (cyclomatic 27) harper-core/src/indefinite_article.rs:21— harper_core::indefinite_article::starts_with_vowel has cyclomatic complexity 27 (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.
harper_core::spell::score_suggestion (cyclomatic 25) harper-core/src/spell/mod.rs:295— harper_core::spell::score_suggestion has cyclomatic complexity 25 (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.
harper_core::title_case::try_make_title_case (cyclomatic 19) harper-core/src/title_case.rs:71— harper_core::title_case::try_make_title_case has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
harper_core::lexing::email_address::validate_local_part (cyclomatic 18) harper-core/src/lexing/email_address.rs:49— harper_core::lexing::email_address::validate_local_part has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Repeated repair: packages/chrome-plugin/tests/testUtils.ts packages/chrome-plugin/tests/testUtils.ts:73— packages/chrome-plugin/tests/testUtils.ts changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is replaceEditorContent at line 73), 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(chrome-ext): don't close popup when the context_hash changes (#4658)”; “fix(chrome-ext): Lexical tests now wait for linting to complete (#4624)”; “fix(chrome-ext): fix test setup to avoid race conditions (#4485)”; “fix(chrome-ext): remove bad assertion”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- packages/chrome-plugin/tests/testUtils.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/web/src/lib/components/Loader.svelte packages/web/src/lib/components/Loader.svelte:99— packages/web/src/lib/components/Loader.svelte changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is updateParticles at line 99), 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(web): preload logo for aesthetics (#4602)”; “fix(web): make the `<Loader />` less irksome (#4401)”; “fix(web): color of the logo used in loading animation (#4349)”; “fix(web): biome issue”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- packages/web/src/lib/components/Loader.svelte`: 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/web/src/routes/+page.svelte packages/web/src/routes/+page.svelte:151— packages/web/src/routes/+page.svelte 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 1 (its worst body is (anonymous) at line 151), 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(chrome-ext): bypass spellcheck suppression on Gmail (#4653)”; “fix(web): give the home page FAQ section the #faqs anchor (#4620)”; “fix(web): `s/writers/students`”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- packages/web/src/routes/+page.svelte`: 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: harper-core/src/linting/wrong_negative.rs harper-core/src/linting/wrong_negative.rs:37— harper-core/src/linting/wrong_negative.rs 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 WrongNegative::match_to_lint at line 37), 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: don't flag "deus" to change to "imus" (#4671)”; “fix: give `MassPlurals` higher priority than `SplitWords` (#4347)”; “fix: don't flag "defo" (#4390)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- harper-core/src/linting/wrong_negative.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/obsidian-plugin/src/HarperSettingTab.ts packages/obsidian-plugin/src/HarperSettingTab.ts:320— packages/obsidian-plugin/src/HarperSettingTab.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 HarperSettingTab.renderStructuredSettings at line 320), 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: add missing static analysis tools (#4551)”; “fix(obsidian): rules are hidden (#4546)”; “fix(obsidian): plugin failing to load due to race condition (#4020)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:54:47 -06:00' --until='2026-10-26 16:54:47 -06:00' --full-history --no-merges -- packages/obsidian-plugin/src/HarperSettingTab.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.
ClassTooLong: LintGroup harper-core/src/linting/lint_group/mod.rs:378— ClassTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods, 4 blocks, lines 378-1152. The bar is 400 significant lines; this is 187 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Backend harper-ls/src/backend.rs:55— ClassTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 3 blocks, lines 55-920. The bar is 400 significant lines; this is 168 over it, 1.42× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Document harper-core/src/document.rs:18— ClassTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 48 methods, 5 blocks, lines 18-949. The bar is 400 significant lines; this is 139 over it, 1.35× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DictWordMetadata harper-core/src/dict_word_metadata.rs:22— ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 47 methods, 2 blocks, lines 22-869. The bar is 400 significant lines; this is 23 over it, 1.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HarperSettingTab packages/obsidian-plugin/src/HarperSettingTab.ts:14— ClassTooLong — 422 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 22 over it, 1.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×4
Focus outline removed in CSS without a :focus replacement packages/web/src/lib/marketing/MarketingDocSearch.svelte:107— `:global(.DocSearch-Input:focus)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/harper-editor/src/lib/styles.css:58— `.harper-editor-surface` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/harper-editor/src/lib/styles.css:70— `.harper-editor-surface:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement harper-desktop/src/lib/settings/settings.css:462— `.search-strip input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×4
Animation without a prefers-reduced-motion guard packages/web/src/app.css:186— `.animate-bigbounce` moves (`animation: bigbounce 1s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/web/src/app.css:190— `.animate-after-bigbounce::after` moves (`animation: bigbounce 1s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard harper-desktop/src/lib/settings/settings.css:177— `.progress-fill` moves (`transition: width 160ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard harper-desktop/src/lib/settings/settings.css:651— `.chevron` moves (`transition: transform 140ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
harper_cli::main (cognitive 181) harper-cli/src/main.rs:248— harper_cli::main has cognitive complexity 181 (threshold 15). Drivers by points: if/else 47 (120 pts), loops 19 (42 pts), boolean chains 11, match/switch 3 (8 pts) (nesting depth added 101). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harper_cli::lint::lint (cognitive 35) harper-cli/src/lint.rs:173— harper_cli::lint::lint has cognitive complexity 35 (threshold 15). Drivers by points: loops 9 (16 pts), if/else 11 (15 pts), match/switch 3, boolean chains 1 (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
harper_cli::lint_engine::lint_one_input (cognitive 29) harper-cli/src/lint_engine.rs:24— harper_cli::lint_engine::lint_one_input has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (12 pts), match/switch 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harper_cli::lint_reporter::single_input_report (cognitive 27) harper-cli/src/lint_reporter.rs:16— harper_cli::lint_reporter::single_input_report has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 4 (12 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Change coupling: ProtocolClient.ts ↔ index.ts packages/chrome-plugin/src/ProtocolClient.ts:1— `packages/chrome-plugin/src/ProtocolClient.ts` and `packages/chrome-plugin/src/background/index.ts` change together 88% of the time (14 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `865bccac` fix: avoid memory leak in JS products (#3917); `3f3daf3d` feat: expose English isolation option (#3669); `b21e2c17` feat(chrome-ext): add delay option (#3166) — run `git show` on any of them.
Change coupling: LocalLinter.ts ↔ index.ts packages/harper.js/src/LocalLinter.ts:1— `packages/harper.js/src/LocalLinter.ts` and `packages/harper.js/src/WorkerLinter/index.ts` change together 83% of the time (29 of the 35 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 29 shared commits counted here, the most recent 3 are `6a2257b4` feat(harper.js): make it easier to ignore all lints (#3315); `b76e8dd3` feat: render configuration structurally (#3123); `eab8bba0` fix(harper.js): create disposal function and use it (#2445) — run `git show` on any of them.
Change coupling: backend.rs ↔ diagnostics.rs harper-ls/src/backend.rs:1— `harper-ls/src/backend.rs` and `harper-ls/src/diagnostics.rs` change together 64% of the time (18 of the 28 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 18 shared commits counted here, the most recent 3 are `bdefce17` Fix 1734 (#1761); `4ba92b4e` (feat) Add concept of workspace dictionary to harper-ls (#1669); `29f03d86` feat(stats): now includes lint context + misspelled words — run `git show` on any of them.
Change coupling: repeated_words.rs ↔ spaces.rs harper-core/src/linting/repeated_words.rs:1— `harper-core/src/linting/repeated_words.rs` and `harper-core/src/linting/spaces.rs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f7b48c4c` refactor(core): move `TokenStringExt` into its own module; `d8227828` feat: added descriptions to each individual lint rule; `06785038` feat: wrote docs and reorganized `harper_core::linter` imports — run `git show` on any of them.
Duplicated block (17 lines × 2) harper-core/src/dict_word_metadata.rs:211— harper-core/src/dict_word_metadata.rs:211-227 | harper-core/src/dict_word_metadata.rs:237-253 — 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 (17 lines × 2) harper-core/src/document.rs:627— harper-core/src/document.rs:627-643 | harper-core/src/document.rs:689-705 — 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 (17 lines × 2) harper-core/src/linting/double_click.rs:62— harper-core/src/linting/double_click.rs:62-78 | harper-core/src/linting/right_click.rs:38-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) harper-pos-utils/src/chunker/brill_chunker/mod.rs:131— harper-pos-utils/src/chunker/brill_chunker/mod.rs:131-147 | harper-pos-utils/src/tagger/brill_tagger/mod.rs:150-166 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) harper-core/src/linting/after_later.rs:51— harper-core/src/linting/after_later.rs:51-57 | harper-core/src/linting/in_time_from_now.rs:54-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) harper-core/src/linting/noun_verb_confusion/effect_affect/affect_to_effect.rs:29— harper-core/src/linting/noun_verb_confusion/effect_affect/affect_to_effect.rs:29-35 | harper-core/src/linting/noun_verb_confusion/effect_affect/affect_to_effect.rs:54-60 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) harper-pos-utils/src/chunker/burn_chunker.rs:212— harper-pos-utils/src/chunker/burn_chunker.rs:212-218 | harper-pos-utils/src/chunker/burn_chunker.rs:273-279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) harper-core/src/expr/mod.rs:114— harper-core/src/expr/mod.rs:114-120 | harper-pos-utils/src/patch_criteria.rs:120-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Dead file (~32 LoC) packages/web/src/lib/components/DefaultNeovimConfig.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~32 LoC) packages/web/src/lib/components/Graph.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~32 LoC) packages/web/src/lib/db/models/DomainReviews.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~32 LoC) packages/web/src/lib/marketing/IntegrationTile.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
harper_cli::main (cyclomatic 91) harper-cli/src/main.rs:248— harper_cli::main has cyclomatic complexity 91 (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.
harper_cli::lint::lint (cyclomatic 26) harper-cli/src/lint.rs:173— harper_cli::lint::lint has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
harper_cli::lint_reporter::single_input_report (cyclomatic 16) harper-cli/src/lint_reporter.rs:16— harper_cli::lint_reporter::single_input_report 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.
Duplicated block (16 lines × 2) harper-comments/src/comment_parsers/lua.rs:68— harper-comments/src/comment_parsers/lua.rs:68-83 | harper-comments/src/comment_parsers/unit.rs:67-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) harper-core/src/linting/there_is_agreement.rs:299— harper-core/src/linting/there_is_agreement.rs:299-314 | harper-core/src/linting/there_is_agreement.rs:367-382 — 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 (16 lines × 2) harper-core/src/linting/to_two_too/to_too_adjective_end.rs:93— harper-core/src/linting/to_two_too/to_too_adjective_end.rs:93-108 | harper-core/src/linting/to_two_too/to_too_adjective_punct.rs:70-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) harper-core/src/document.rs:766— harper-core/src/document.rs:766-779 | harper-core/src/document.rs:824-837 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) harper-core/src/linting/pleaded_pled.rs:46— harper-core/src/linting/pleaded_pled.rs:46-59 | harper-core/src/linting/sneaked_snuck.rs:46-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) harper-pos-utils/src/tagger/brill_tagger/mod.rs:85— harper-pos-utils/src/tagger/brill_tagger/mod.rs:85-98 | harper-pos-utils/src/tagger/brill_tagger/mod.rs:112-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) harper-core/src/dict_word_metadata.rs:277— harper-core/src/dict_word_metadata.rs:277-289 | harper-core/src/dict_word_metadata.rs:299-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) harper-core/src/linting/its_possessive.rs:46— harper-core/src/linting/its_possessive.rs:46-58 | harper-core/src/linting/its_possessive.rs:103-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) harper-core/src/linting/code_in_write_in.rs:82— harper-core/src/linting/code_in_write_in.rs:82-94 | harper-core/src/linting/in_ones_defense.rs:69-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) harper-comments/src/comment_parsers/go.rs:28— harper-comments/src/comment_parsers/go.rs:28-39 | harper-comments/src/comment_parsers/solidity.rs:61-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) harper-core/src/spell/mutable_dictionary.rs:246— harper-core/src/spell/mutable_dictionary.rs:246-257 | harper-core/src/spell/mutable_dictionary.rs:260-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) harper-core/src/linting/pronoun_verb_agreement.rs:224— harper-core/src/linting/pronoun_verb_agreement.rs:224-236 | harper-core/src/linting/went_ahead_and_agreement.rs:92-103 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) harper-core/src/linting/adjective_of_a.rs:102— harper-core/src/linting/adjective_of_a.rs:102-112 | harper-core/src/linting/adjective_of_a.rs:114-124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) harper-core/src/linting/to_two_too/to_too_adverb.rs:27— harper-core/src/linting/to_two_too/to_too_adverb.rs:27-37 | harper-core/src/linting/to_two_too/to_too_degree_words.rs:24-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) harper-core/src/linting/amounts_for.rs:46— harper-core/src/linting/amounts_for.rs:46-56 | harper-core/src/linting/amounts_for.rs:67-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) harper-cli/src/lint.rs:393— harper-cli/src/lint.rs:393-398 | harper-cli/src/lint.rs:414-418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) harper-core/src/linting/very_less.rs:66— harper-core/src/linting/very_less.rs:66-70 | harper-core/src/linting/very_less.rs:73-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) harper-tex/src/masker.rs:257— harper-tex/src/masker.rs:257-261 | harper-tex/src/masker.rs:270-274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2 locations) packages/chrome-plugin/src/contentScript/index.ts:124— packages/chrome-plugin/src/contentScript/index.ts:124 · packages/chrome-plugin/src/contentScript/index.ts:215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2 locations) packages/obsidian-plugin/src/lint.ts:980— packages/obsidian-plugin/src/lint.ts:980 · packages/obsidian-plugin/src/lint.ts:998 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2 locations) packages/web/src/lib/db/models/DomainReviews.ts:13— packages/web/src/lib/db/models/DomainReviews.ts:13 · packages/web/src/lib/db/models/UninstallFeedback.ts:13 — 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 (9 lines × 2 locations) packages/chrome-plugin/src/options/Options.svelte:124— packages/chrome-plugin/src/options/Options.svelte:124 · packages/obsidian-plugin/src/textUtils.ts:2 — 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 (9 lines × 2 locations) packages/chrome-plugin/src/popup/DomainReview.svelte:15— packages/chrome-plugin/src/popup/DomainReview.svelte:15 · packages/chrome-plugin/src/popup/ReportProblematicLint.svelte:10 — 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 (9 lines × 2 locations) packages/components/src/lib/Checkbox.svelte:6— packages/components/src/lib/Checkbox.svelte:6 · packages/components/src/lib/Toggle.svelte: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.
Duplicated block (7 lines × 2 locations) harper-desktop/src/lib/EditorView.svelte:13— harper-desktop/src/lib/EditorView.svelte:13 · packages/web/src/lib/createEditorLinter.ts:3 — 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 (7 lines × 2 locations) packages/components/src/lib/Panel.svelte:2— packages/components/src/lib/Panel.svelte:2 · packages/components/src/lib/SettingRow.svelte:3 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (7 lines × 2 locations) packages/wordpress-plugin/src/harper/useDialect.ts:8— packages/wordpress-plugin/src/harper/useDialect.ts:8 · packages/wordpress-plugin/src/harper/useIgnoredLintState.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.
Dead file (~25 LoC) harper-desktop/src/lib/settings/SettingsSidebar.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (harper-desktop/src/lib/settings/SettingsApp.svelte) — 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 (~25 LoC) packages/web/src/lib/marketing/AppLogoTile.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~25 LoC) packages/web/src/lib/marketing/PillButton.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC1 · Text alternatives· <canvas> without a text alternative · ×2
<canvas> without a text alternative packages/web/src/lib/components/BarChart.svelte:120— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative packages/web/src/lib/components/Loader.svelte:205— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
Empty <h3> heading packages/components/src/lib/Section.svelte:19— An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative.
Empty <h3> heading packages/components/src/lib/Section.svelte:43— An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×2
Heading level jumps from h1 to h3 packages/web/src/routes/presentation/+page.svelte:23— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 packages/web/src/routes/presentation/+page.svelte:43— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×2
Modal dialog does not manage focus harper-desktop/src/lib/settings/components/AppPickerModal.svelte:90— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus packages/harper-editor/src/lib/LintSidebar.svelte:354— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
MissingTo::match_to_lint_with_context (cyclomatic 41) harper-core/src/linting/missing_to.rs:374— MissingTo::match_to_lint_with_context has cyclomatic complexity 41 (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.
MissingTo::preposition_or_determiner_within_four (cyclomatic 19) harper-core/src/linting/missing_to.rs:229— MissingTo::preposition_or_determiner_within_four has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Backend::update_document (cyclomatic 25) harper-ls/src/backend.rs:243— Backend::update_document has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Backend::execute_command (cyclomatic 19) harper-ls/src/backend.rs:708— Backend::execute_command has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AttributeList::expand_annotated_word (cognitive 62) harper-core/src/spell/rune/attribute_list.rs:56— AttributeList::expand_annotated_word has cognitive complexity 62 (threshold 15). Drivers by points: if/else 15 (40 pts), loops 9 (21 pts), boolean chains 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeList::apply_replacement (cognitive 17) harper-core/src/spell/rune/attribute_list.rs:218— AttributeList::apply_replacement has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MissingTo::match_to_lint_with_context (cognitive 40) harper-core/src/linting/missing_to.rs:374— MissingTo::match_to_lint_with_context has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 22, if/else 18. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MissingTo::preposition_or_determiner_within_four (cognitive 30) harper-core/src/linting/missing_to.rs:229— MissingTo::preposition_or_determiner_within_four has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Markdown::remove_hidden_wikilink_tokens (cognitive 27) harper-core/src/parsers/markdown.rs:45— Markdown::remove_hidden_wikilink_tokens has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Markdown::parse (cognitive 26) harper-core/src/parsers/markdown.rs:140— Markdown::parse has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (19 pts), boolean chains 4, match/switch 1 (2 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Backend::execute_command (cognitive 24) harper-ls/src/backend.rs:708— Backend::execute_command has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 3 (5 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.
Backend::update_document (cognitive 18) harper-ls/src/backend.rs:243— Backend::update_document has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), match/switch 2, boolean chains 1 (nesting depth added 4). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DictWordMetadata::enforce_pos_exclusivity (cognitive 21) harper-core/src/dict_word_metadata.rs:199— DictWordMetadata::enforce_pos_exclusivity has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (20 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DictWordMetadata::infer_pos_tag (cognitive 17) harper-core/src/dict_word_metadata.rs:131— DictWordMetadata::infer_pos_tag has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (17 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
Document::condense_spaces (cognitive 19) harper-core/src/document.rs:486— Document::condense_spaces has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Document::condense_filename_extensions (cognitive 19) harper-core/src/document.rs:654— Document::condense_filename_extensions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (15 lines × 2) harper-core/src/document.rs:512— harper-core/src/document.rs:512-526 | harper-core/src/document.rs:589-603 — 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 (15 lines × 2) harper-core/src/linting/noun_verb_confusion/effect_affect/affect_to_effect.rs:104— harper-core/src/linting/noun_verb_confusion/effect_affect/affect_to_effect.rs:104-118 | harper-core/src/linting/noun_verb_confusion/effect_affect/effect_to_affect.rs:127-142 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9–10 lines × 2) harper-core/src/expr/pronoun_be.rs:11— harper-core/src/expr/pronoun_be.rs:11-19 | harper-core/src/linting/be_adjective_confusions.rs:27-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9–10 lines × 2) harper-core/src/linting/compound_nouns/compound_noun_after_det_adj.rs:36— harper-core/src/linting/compound_nouns/compound_noun_after_det_adj.rs:36-44 | harper-core/src/linting/compound_nouns/compound_noun_after_possessive.rs:33-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 3) harper-core/src/dict_word_metadata.rs:221— harper-core/src/dict_word_metadata.rs:221-229 | harper-core/src/dict_word_metadata.rs:261-269 | harper-core/src/dict_word_metadata.rs:283-291 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) harper-ls/src/backend.rs:744— harper-ls/src/backend.rs:744-752 | harper-ls/src/backend.rs:765-773 | harper-ls/src/backend.rs:796-804 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) harper-core/src/linting/lint_group/mod.rs:426— harper-core/src/linting/lint_group/mod.rs:426-431 | harper-core/src/linting/lint_group/mod.rs:450-455 | harper-core/src/linting/lint_group/mod.rs:471-476 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) harper-core/src/linting/lint_group/mod.rs:489— harper-core/src/linting/lint_group/mod.rs:489-494 | harper-core/src/linting/lint_group/mod.rs:502-507 | harper-core/src/linting/lint_group/mod.rs:515-520 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Low cohesion: MacBroker (LCOM4 8) harper-desktop/src-tauri/src/mac_broker/mod.rs:62— MacBroker's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WindowsBroker (LCOM4 7) harper-desktop/src-tauri/src/windows_broker/mod.rs:32— WindowsBroker's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplicated block (14 lines × 2 locations) packages/lint-framework/src/lint/computeLintBoxes/index.ts:105— packages/lint-framework/src/lint/computeLintBoxes/index.ts:105 · packages/lint-framework/src/lint/googleDocsAdapter.ts:141 — 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 (14 lines × 2 locations) packages/wordpress-plugin/src/harper/Logo.jsx:42— packages/wordpress-plugin/src/harper/Logo.jsx:42 · packages/wordpress-plugin/src/harper/Logo.jsx:77 — 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 (12 lines × 2 locations) packages/chrome-plugin/src/options/StructuredRuleSettings.svelte:155— packages/chrome-plugin/src/options/StructuredRuleSettings.svelte:155 · packages/obsidian-plugin/src/HarperSettingTab.ts:500 — 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 (12 lines × 2 locations) packages/lint-framework/src/lint/computeLintBoxes/index.ts:72— packages/lint-framework/src/lint/computeLintBoxes/index.ts:72 · packages/lint-framework/src/lint/googleDocsAdapter.ts:47 — 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 (8 lines × 2 locations) packages/chrome-plugin/public/google-docs-bridge.js:95— packages/chrome-plugin/public/google-docs-bridge.js:95 · packages/chrome-plugin/public/google-docs-bridge.js:105 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) packages/wordpress-plugin/src/harper/useDialect.ts:9— packages/wordpress-plugin/src/harper/useDialect.ts:9 · packages/wordpress-plugin/src/harper/useLintConfig.ts:12 — 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 (7 lines × 3 locations) packages/components/src/lib/Checkbox.svelte:8— packages/components/src/lib/Checkbox.svelte:8 · packages/components/src/lib/IconButton.svelte:7 · packages/components/src/lib/Toggle.svelte:7 — 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.
Duplicated block (7 lines × 3 locations) packages/wordpress-plugin/src/harper/useDialect.ts:8— packages/wordpress-plugin/src/harper/useDialect.ts:8 · packages/wordpress-plugin/src/harper/useIgnoredLintState.ts:9 · packages/wordpress-plugin/src/harper/usePersonalDictionary.ts:11 — 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.
Boundary violation [package:relative-cross-package] packages/web/src/routes/+page.svelte:24— packages/web/src/routes/+page.svelte:24 reaches into another package with a relative path (../../../../demo.md?raw) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/web/src/routes/languagedetection/+page.svelte:5— packages/web/src/routes/languagedetection/+page.svelte:5 reaches into another package with a relative path (../../../../../demo.md?raw) — import the package by name instead.
Dead file (~130 LoC) packages/web/src/lib/components/LineChart.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~130 LoC) packages/web/src/lib/marketing/versions.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~30 LoC) packages/components/src/lib/Checkbox.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/components/src/lib/index.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 (~30 LoC) packages/web/src/lib/adminUtils.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~27 LoC) packages/components/src/lib/Link.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/components/src/lib/index.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 (~27 LoC) packages/web/src/lib/components/AnalyticsPage.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
TypstTranslator::parse_expr (cyclomatic 44) harper-typst/src/typst_translator.rs:195— TypstTranslator::parse_expr has cyclomatic complexity 44 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ExpandMemoryShorthands::get_replacement (cyclomatic 43) harper-core/src/linting/expand_memory_shorthands.rs:30— ExpandMemoryShorthands::get_replacement has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NounCountability::match_to_lint_with_context (cyclomatic 35) harper-core/src/linting/mass_nouns/noun_countability.rs:54— NounCountability::match_to_lint_with_context has cyclomatic complexity 35 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PhrasalVerbAsCompoundNoun::analyse (cyclomatic 31) harper-core/src/linting/phrasal_verb_as_compound_noun.rs:63— PhrasalVerbAsCompoundNoun::analyse 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.
Config::from_lsp_config (cyclomatic 31) harper-ls/src/config.rs:88— Config::from_lsp_config has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
uploadRelease (cyclomatic 27) .buildkite/commands/upload-release.cjs:35— uploadRelease has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 9 of the 27 points are its own statements and the rest belongs to 11 function items inside it that branch (json, retry, list, …). 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.
Highlights.renderLintBoxes (cyclomatic 25) packages/lint-framework/src/lint/Highlights.ts:62— Highlights.renderLintBoxes has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SplitWords::match_to_lint_with_context (cyclomatic 23) harper-core/src/linting/split_words.rs:47— SplitWords::match_to_lint_with_context 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.
AttributeList::expand_annotated_word (cyclomatic 23) harper-core/src/spell/rune/attribute_list.rs:56— AttributeList::expand_annotated_word 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.
OrthFlags::from_letters (cyclomatic 23) harper-core/src/dict_word_metadata_orthography.rs:70— OrthFlags::from_letters 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.
Server::handle_request (cyclomatic 23) harper-desktop/src-tauri/src/communication/server.rs:44— Server::handle_request has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AnA::lint (cyclomatic 22) harper-core/src/linting/an_a.rs:21— AnA::lint has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InflectedVerbAfterTo::lint (cyclomatic 22) harper-core/src/linting/inflected_verb_after_to.rs:20— InflectedVerbAfterTo::lint has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EffectToAffect::match_to_lint (cyclomatic 21) harper-core/src/linting/noun_verb_confusion/effect_affect/effect_to_affect.rs:40— EffectToAffect::match_to_lint has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Markdown::parse (cyclomatic 21) harper-core/src/parsers/markdown.rs:140— Markdown::parse has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AdjectiveOfA::lint (cyclomatic 20) harper-core/src/linting/adjective_of_a.rs:57— AdjectiveOfA::lint has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MoreAdjective::match_to_lint (cyclomatic 20) harper-core/src/linting/more_adjective.rs:56— MoreAdjective::match_to_lint has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
DictWordMetadata::enforce_pos_exclusivity (cyclomatic 19) harper-core/src/dict_word_metadata.rs:199— DictWordMetadata::enforce_pos_exclusivity has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Damages::match_to_lint_with_context (cyclomatic 19) harper-core/src/linting/damages.rs:41— Damages::match_to_lint_with_context has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
General::match_to_lint (cyclomatic 19) harper-core/src/linting/its_contraction/general.rs:75— General::match_to_lint has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Touristic::match_to_lint (cyclomatic 18) harper-core/src/linting/touristic.rs:93— Touristic::match_to_lint has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FleshOutVsFullFledged::match_to_lint_with_context (cyclomatic 17) harper-core/src/linting/flesh_out_vs_full_fledged.rs:32— FleshOutVsFullFledged::match_to_lint_with_context has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GonnaGottaWanna::match_to_lint_with_context (cyclomatic 17) harper-core/src/linting/gonna_gotta_wanna.rs:50— GonnaGottaWanna::match_to_lint_with_context has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Patch::generate_candidate_patches (cyclomatic 17) harper-pos-utils/src/chunker/brill_chunker/patch.rs:15— Patch::generate_candidate_patches has cyclomatic complexity 17 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
PopupHandler.updateLintBoxes (cyclomatic 17) packages/lint-framework/src/lint/PopupHandler.ts:206— PopupHandler.updateLintBoxes has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 2 function literals inside it that branch. 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.
LintFramework.requestLintUpdate (cyclomatic 17) packages/lint-framework/src/lint/LintFramework.ts:127— LintFramework.requestLintUpdate has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Everyday::match_to_lint (cyclomatic 16) harper-core/src/linting/everyday.rs:130— Everyday::match_to_lint has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
MergeWords::lint (cyclomatic 16) harper-core/src/linting/merge_words.rs:28— MergeWords::lint 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.
ThisTypeOfThing::match_to_lint (cyclomatic 16) harper-core/src/linting/this_type_of_thing.rs:47— ThisTypeOfThing::match_to_lint has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
RenderState::render (cyclomatic 16) harper-desktop/src-tauri/src/highlighter/render_state/mod.rs:177— RenderState::render 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.
LiterateHaskellMasker::create_mask (cyclomatic 16) harper-literate-haskell/src/masker.rs:28— LiterateHaskellMasker::create_mask 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.
Serializer.serializeArg (cyclomatic 16) packages/harper.js/src/Serializer.ts:51— Serializer.serializeArg 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.
domUtils.isVisible (cyclomatic 16) packages/lint-framework/src/lint/domUtils.ts:151— domUtils.isVisible 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.
ExpandMemoryShorthands::get_replacement (cognitive 64) harper-core/src/linting/expand_memory_shorthands.rs:30— ExpandMemoryShorthands::get_replacement has cognitive complexity 64 (threshold 15). Drivers by points: if/else 42 (63 pts), match/switch 1 (nesting depth added 21). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Config::from_lsp_config (cognitive 47) harper-ls/src/config.rs:88— Config::from_lsp_config has cognitive complexity 47 (threshold 15). Drivers by points: if/else 31 (43 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InflectedVerbAfterTo::lint (cognitive 45) harper-core/src/linting/inflected_verb_after_to.rs:20— InflectedVerbAfterTo::lint has cognitive complexity 45 (threshold 15). Drivers by points: if/else 17 (40 pts), boolean chains 4, loops 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Highlights.renderLintBoxes (cognitive 44) packages/lint-framework/src/lint/Highlights.ts:62— Highlights.renderLintBoxes has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (34 pts), loops 4 (5 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnA::lint (cognitive 41) harper-core/src/linting/an_a.rs:21— AnA::lint has cognitive complexity 41 (threshold 15). Drivers by points: if/else 6 (20 pts), match/switch 4 (13 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SentenceCapitalization::lint (cognitive 41) harper-core/src/linting/sentence_capitalization.rs:23— SentenceCapitalization::lint has cognitive complexity 41 (threshold 15). Drivers by points: if/else 8 (31 pts), loops 3 (8 pts), boolean chains 2 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OrthFlags::from_letters (cognitive 41) harper-core/src/dict_word_metadata_orthography.rs:70— OrthFlags::from_letters has cognitive complexity 41 (threshold 15). Drivers by points: if/else 20 (36 pts), boolean chains 4, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SplitWords::match_to_lint_with_context (cognitive 37) harper-core/src/linting/split_words.rs:47— SplitWords::match_to_lint_with_context has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (31 pts), boolean chains 3, loops 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThrowRubbish::lint (cognitive 37) harper-core/src/linting/throw_rubbish.rs:33— ThrowRubbish::lint has cognitive complexity 37 (threshold 15). Drivers by points: if/else 7 (29 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
uploadRelease (cognitive 35) .buildkite/commands/upload-release.cjs:35— uploadRelease has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (15 pts), error handling 4 (6 pts), loops 5 (6 pts), boolean chains 4, ternaries 3 (4 pts) (nesting depth added 9). Most of this is not in the body itself: 9 of the 35 points are its own statements and the rest belongs to 11 function items inside it that branch (json, retry, list, …). 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.
Patch::generate_candidate_patches (cognitive 34) harper-pos-utils/src/chunker/brill_chunker/patch.rs:15— Patch::generate_candidate_patches has cognitive complexity 34 (threshold 15). Drivers by points: loops 15 (31 pts), if/else 1 (3 pts) (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
WeirLinter::run_tests (cognitive 31) harper-core/src/weir/mod.rs:214— WeirLinter::run_tests has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 4 (6 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 15). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 2 function items inside it that branch (transform_to_expected, transform_nth_str). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
LintGroup::organized_lints (cognitive 30) harper-core/src/linting/lint_group/mod.rs:1040— LintGroup::organized_lints has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 6 (10 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhrasalVerbAsCompoundNoun::analyse (cognitive 30) harper-core/src/linting/phrasal_verb_as_compound_noun.rs:63— PhrasalVerbAsCompoundNoun::analyse has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 13, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Touristic::match_to_lint (cognitive 28) harper-core/src/linting/touristic.rs:93— Touristic::match_to_lint has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 2, match/switch 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AdjectiveOfA::lint (cognitive 27) harper-core/src/linting/adjective_of_a.rs:57— AdjectiveOfA::lint has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 6, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BurnChunker::extract_sents_from_files (cognitive 27) harper-pos-utils/src/chunker/burn_chunker.rs:287— BurnChunker::extract_sents_from_files has cognitive complexity 27 (threshold 15). Drivers by points: loops 6 (16 pts), if/else 3 (9 pts), boolean chains 2 (nesting depth added 16). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
LintFramework.requestLintUpdate (cognitive 27) packages/lint-framework/src/lint/LintFramework.ts:127— LintFramework.requestLintUpdate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 2 (7 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 12). Most of this is not in the body itself: 11 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 167, 205). 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.
MassPlurals::match_to_lint (cognitive 24) harper-core/src/linting/mass_nouns/mass_plurals.rs:58— MassPlurals::match_to_lint has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (24 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
WillNonLemma::match_to_lint_with_context (cognitive 24) harper-core/src/linting/will_non_lemma.rs:52— WillNonLemma::match_to_lint_with_context has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3, match/switch 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.
OrgMode::parse (cognitive 24) harper-core/src/parsers/org_mode.rs:132— OrgMode::parse has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LiterateHaskellMasker::create_mask (cognitive 24) harper-literate-haskell/src/masker.rs:28— LiterateHaskellMasker::create_mask has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 9, 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.
JavaDoc::parse (cognitive 21) harper-comments/src/comment_parsers/javadoc.rs:15— JavaDoc::parse has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (6 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.
domUtils.isVisible (cognitive 21) packages/lint-framework/src/lint/domUtils.ts:151— domUtils.isVisible has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, error handling 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.
Damages::match_to_lint_with_context (cognitive 20) harper-core/src/linting/damages.rs:41— Damages::match_to_lint_with_context has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 8, match/switch 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MergeWords::lint (cognitive 20) harper-core/src/linting/merge_words.rs:28— MergeWords::lint has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 9, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EffectToAffect::match_to_lint (cognitive 20) harper-core/src/linting/noun_verb_confusion/effect_affect/effect_to_affect.rs:40— EffectToAffect::match_to_lint has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 9, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RepeatedWords::lint (cognitive 20) harper-core/src/linting/repeated_words.rs:36— RepeatedWords::lint has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (13 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WithOpenArms::match_to_lint (cognitive 20) harper-core/src/linting/with_open_arms.rs:43— WithOpenArms::match_to_lint has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (20 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Masker::create_mask (cognitive 20) harper-tex/src/masker.rs:9— Masker::create_mask has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypstTranslator::parse_expr (cognitive 20) harper-typst/src/typst_translator.rs:195— TypstTranslator::parse_expr has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 5 (6 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HarperSettingTab.renderStructuredSettings (cognitive 20) packages/obsidian-plugin/src/HarperSettingTab.ts:320— HarperSettingTab.renderStructuredSettings has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 4, 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.
General::match_to_lint (cognitive 19) harper-core/src/linting/its_contraction/general.rs:75— General::match_to_lint has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 9. 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.
MoreAdjective::match_to_lint (cognitive 18) harper-core/src/linting/more_adjective.rs:56— MoreAdjective::match_to_lint has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, match/switch 5, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RenderState::render (cognitive 18) harper-desktop/src-tauri/src/highlighter/render_state/mod.rs:177— RenderState::render has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MacBroker::ensure_accessibility_activation (cognitive 18) harper-desktop/src-tauri/src/mac_broker/mod.rs:139— MacBroker::ensure_accessibility_activation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 2, 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.
BrillChunker::epoch (cognitive 18) harper-pos-utils/src/chunker/brill_chunker/mod.rs:110— BrillChunker::epoch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 5 (7 pts), match/switch 1 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.computeLintBoxes (cognitive 18) packages/lint-framework/src/lint/computeLintBoxes/index.ts:28— index.computeLintBoxes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 4 (7 pts), error handling 1, loops 1 (nesting depth added 4). Of this number, 16 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.
FleshOutVsFullFledged::match_to_lint_with_context (cognitive 16) harper-core/src/linting/flesh_out_vs_full_fledged.rs:32— FleshOutVsFullFledged::match_to_lint_with_context has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), match/switch 3, boolean chains 1, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OrthographicConsistency::match_to_lint_with_context (cognitive 16) harper-core/src/linting/orthographic_consistency.rs:41— OrthographicConsistency::match_to_lint_with_context has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PronounVerbAgreement::match_to_lint_with_context (cognitive 16) harper-core/src/linting/pronoun_verb_agreement.rs:173— PronounVerbAgreement::match_to_lint_with_context has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SpellCheck::lint (cognitive 16) harper-core/src/linting/spell_check.rs:92— SpellCheck::lint has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Server::handle_request (cognitive 16) harper-desktop/src-tauri/src/communication/server.rs:44— Server::handle_request has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
googleDocsUtilities.getGoogleDocsHighlightRects (cognitive 16) packages/lint-framework/src/lint/computeLintBoxes/googleDocsUtilities.ts:235— googleDocsUtilities.getGoogleDocsHighlightRects has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, loops 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
State.constructEditorLinter (cognitive 16) packages/obsidian-plugin/src/State.ts:121— State.constructEditorLinter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 1 (3 pts), ternaries 2 (nesting depth added 6). None of this is in the body itself: all 16 points belong to 4 function literals inside it that branch (lines 123, 155, 144, …). 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.
TooManyFunctions: harper_desktop::commands harper-desktop/src-tauri/src/commands.rs:20— TooManyFunctions — 31 free functions. The bar is 30 free functions; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change-coupling hub: unclosed_quotes.rs → repeated_words.rs, sentence_capitalization.rs, spell_check.rs, token.rs harper-core/src/linting/unclosed_quotes.rs— `harper-core/src/linting/unclosed_quotes.rs` changes together with 4 other files — `harper-core/src/linting/repeated_words.rs`, `harper-core/src/linting/sentence_capitalization.rs`, `harper-core/src/linting/spell_check.rs`, `harper-core/src/token.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Near-duplicate member pair (40 shared lines) harper-core/src/linting/there_is_agreement.rs:223— harper-core/src/linting/there_is_agreement.rs:223-320 | harper-core/src/linting/there_is_agreement.rs:395-485 — These two members are variants of one another: 40 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) harper-core/src/linting/did_past.rs:56— harper-core/src/linting/did_past.rs:56-109 | harper-core/src/linting/helped_past.rs:47-100 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) harper-core/src/linting/to_two_too/to_too_adjverb_ed_punct.rs:42— harper-core/src/linting/to_two_too/to_too_adjverb_ed_punct.rs:42-57 | harper-core/src/linting/to_two_too/to_too_adverb.rs:47-62 | harper-core/src/linting/to_two_too/to_too_chunk_start_comma.rs:34-49 | harper-core/src/linting/to_two_too/to_too_degree_words.rs:44-59 | harper-core/src/linting/to_two_too/to_too_pronoun_end.rs:55-70 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) harper-comments/src/comment_parsers/jsdoc.rs:24— harper-comments/src/comment_parsers/jsdoc.rs:24-48 | harper-comments/src/comment_parsers/lua.rs:24-57 | harper-comments/src/comment_parsers/solidity.rs:25-49 | harper-comments/src/comment_parsers/unit.rs:29-63 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (16–54 lines × 2) harper-core/expr_linter_skeleton.rs:28— harper-core/expr_linter_skeleton.rs:28-43 | harper-core/expr_linter_skeleton_commented.rs:53-106 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (46 lines × 2) harper-core/src/linting/did_past.rs:57— harper-core/src/linting/did_past.rs:57-102 | harper-core/src/linting/helped_past.rs:48-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (40 lines × 2) harper-pos-utils/src/chunker/brill_chunker/mod.rs:193— harper-pos-utils/src/chunker/brill_chunker/mod.rs:193-232 | harper-pos-utils/src/tagger/brill_tagger/mod.rs:194-233 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (37 lines × 2) harper-core/src/spell/mod.rs:42— harper-core/src/spell/mod.rs:42-78 | harper-core/src/spell/mod.rs:155-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (29 lines × 2) harper-core/src/linting/expand_memory_shorthands.rs:95— harper-core/src/linting/expand_memory_shorthands.rs:95-123 | harper-core/src/linting/expand_time_shorthands.rs:59-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19–22 lines × 2) harper-core/src/linting/there_is_agreement.rs:240— harper-core/src/linting/there_is_agreement.rs:240-258 | harper-core/src/linting/there_is_agreement.rs:402-423 — 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 (20 lines × 2) harper-core/src/linting/its_contraction/general.rs:228— harper-core/src/linting/its_contraction/general.rs:228-247 | harper-core/src/linting/of_course.rs:85-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (19 lines × 4) harper-comments/src/comment_parsers/jsdoc.rs:30— harper-comments/src/comment_parsers/jsdoc.rs:30-48 | harper-comments/src/comment_parsers/lua.rs:39-57 | harper-comments/src/comment_parsers/solidity.rs:31-49 | harper-comments/src/comment_parsers/unit.rs:45-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (19 lines × 2) harper-core/src/linting/its_contraction/general.rs:250— harper-core/src/linting/its_contraction/general.rs:250-268 | harper-core/src/linting/nobody.rs:71-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (18 lines × 2) harper-core/src/linting/ajar.rs:36— harper-core/src/linting/ajar.rs:36-53 | harper-core/src/linting/akimbo.rs:39-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 5) harper-core/src/linting/to_two_too/to_too_adjverb_ed_punct.rs:43— harper-core/src/linting/to_two_too/to_too_adjverb_ed_punct.rs:43-57 | harper-core/src/linting/to_two_too/to_too_adverb.rs:48-62 | harper-core/src/linting/to_two_too/to_too_chunk_start_comma.rs:35-49 | harper-core/src/linting/to_two_too/to_too_degree_words.rs:45-59 | harper-core/src/linting/to_two_too/to_too_pronoun_end.rs:56-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
Duplicated block (11–13 lines × 2) harper-core/src/linting/there_is_agreement.rs:279— harper-core/src/linting/there_is_agreement.rs:279-291 | harper-core/src/linting/there_is_agreement.rs:442-452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–12 lines × 2) harper-core/src/linting/hedging.rs:17— harper-core/src/linting/hedging.rs:17-25 | harper-core/src/linting/oxymorons.rs:35-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11–12 lines × 2) harper-core/src/spell/mod.rs:205— harper-core/src/spell/mod.rs:205-216 | harper-core/src/spell/mod.rs:248-258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–11 lines × 2) harper-core/src/document.rs:789— harper-core/src/document.rs:789-799 | harper-core/src/document.rs:856-863 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–11 lines × 2) harper-core/src/linting/quite_quiet.rs:91— harper-core/src/linting/quite_quiet.rs:91-100 | harper-core/src/linting/quite_quiet.rs:104-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–11 lines × 2) harper-desktop/src-tauri/src/commands.rs:139— harper-desktop/src-tauri/src/commands.rs:139-149 | harper-desktop/src-tauri/src/commands.rs:286-294 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–10 lines × 2) harper-wasm/src/lib.rs:365— harper-wasm/src/lib.rs:365-374 | harper-wasm/src/lib.rs:409-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–9 lines × 2) harper-core/src/linting/its_possessive.rs:35— harper-core/src/linting/its_possessive.rs:35-43 | harper-core/src/linting/its_possessive.rs:58-64 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–9 lines × 2) harper-core/src/linting/to_two_too/to_too_adjective_end.rs:47— harper-core/src/linting/to_two_too/to_too_adjective_end.rs:47-55 | harper-core/src/linting/to_two_too/to_too_adjective_punct.rs:44-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7–8 lines × 2) harper-core/src/document.rs:667— harper-core/src/document.rs:667-673 | harper-core/src/document.rs:735-742 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 3) harper-ls/src/backend.rs:733— harper-ls/src/backend.rs:733-739 | harper-ls/src/backend.rs:754-760 | harper-ls/src/backend.rs:775-781 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 4) harper-asciidoc/src/lib.rs:31— harper-asciidoc/src/lib.rs:31-41 | harper-git-commit/src/lib.rs:32-42 | harper-html/src/lib.rs:29-39 | harper-ink/src/lib.rs:28-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (22 lines × 2) harper-core/src/linting/after_later.rs:13— harper-core/src/linting/after_later.rs:13-34 | harper-core/src/linting/in_time_from_now.rs:14-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) harper-cli/src/lint_reporter.rs:127— harper-cli/src/lint_reporter.rs:127-132 | harper-cli/src/lint_reporter.rs:146-151 — 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.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 713 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
Duplication concentrated across 4 sibling directories (8 clone groups) packages/chrome-plugin/public/google-docs-bridge.js:449— 8 duplicated blocks under packages/ have copies in at least two of the sibling directories chrome-plugin, lint-framework, obsidian-plugin, wordpress-plugin — 7 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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 (85 matched lines × 2 locations) · ×1
Duplicated block with local edits (85 matched lines × 2 locations) packages/chrome-plugin/public/google-docs-bridge.js:449— packages/chrome-plugin/public/google-docs-bridge.js:449 · packages/lint-framework/src/lint/computeLintBoxes/googleDocsUtilities.ts:84 — the two spans are one implementation copied and then locally edited — 693 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 (36 matched lines × 2 locations) · ×1
Duplicated block with local edits (36 matched lines × 2 locations) packages/lint-framework/src/lint/domUtils.ts:69— packages/lint-framework/src/lint/domUtils.ts:69 · packages/wordpress-plugin/src/harper/domUtils.ts:33 — the two spans are one implementation copied and then locally edited — 249 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 (27 lines × 2 locations) harper-desktop/src/lib/settings/pages/DictionaryPage.svelte:31— harper-desktop/src/lib/settings/pages/DictionaryPage.svelte:31 · harper-desktop/src/lib/settings/pages/IntegrationsPage.svelte:42 — 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 (27 matched lines × 2 locations) · ×1
Duplicated block with local edits (27 matched lines × 2 locations) packages/harper.js/src/LocalLinter.ts:160— packages/harper.js/src/LocalLinter.ts:160 · packages/harper.js/src/WorkerLinter/index.ts:157 — the two spans are one implementation copied and then locally edited — 255 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 (24 lines × 2 locations) harper-desktop/src/lib/settings/pages/GeneralPage.svelte:112— harper-desktop/src/lib/settings/pages/GeneralPage.svelte:112 · harper-desktop/src/lib/settings/pages/IntegrationsPage.svelte:51 — 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 (24 matched lines × 2 locations) · ×1
Duplicated block with local edits (24 matched lines × 2 locations) packages/lint-framework/src/lint/lintKindColor.ts:7— packages/lint-framework/src/lint/lintKindColor.ts:7 · packages/obsidian-plugin/src/lintKindColor.ts:3 — the two spans are one implementation copied and then locally edited — 103 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 (23 lines × 3 locations) packages/web/src/routes/admin/ext-site-problems/[slug]/+page.server.ts:5— packages/web/src/routes/admin/ext-site-problems/[slug]/+page.server.ts:5 · packages/web/src/routes/admin/ext-uninstall-reasons/[slug]/+page.server.ts:5 · packages/web/src/routes/admin/problematic-lints/[slug]/+page.server.ts:5 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (21 lines × 2 locations) packages/lint-framework/src/lint/computeLintBoxes/index.ts:218— packages/lint-framework/src/lint/computeLintBoxes/index.ts:218 · packages/lint-framework/src/lint/computeLintBoxes/index.ts:248 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) packages/chrome-plugin/src/options/Options.svelte:166— packages/chrome-plugin/src/options/Options.svelte:166 · packages/chrome-plugin/src/options/StructuredRuleSettings.svelte:130 — 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.
R10 · Code Duplication· Duplicated block with local edits (18 matched lines × 2 locations) · ×1
Duplicated block with local edits (18 matched lines × 2 locations) packages/lint-framework/src/lint/Box.ts:2— packages/lint-framework/src/lint/Box.ts:2 · packages/wordpress-plugin/src/harper/Box.ts:1 — the two spans are one implementation copied and then locally edited — 100 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 (17 matched lines × 2 locations) · ×1
Duplicated block with local edits (17 matched lines × 2 locations) packages/harper.js/src/Linter.ts:86— packages/harper.js/src/Linter.ts:86 · packages/harper.js/src/WorkerLinter/index.ts:145 — the two spans are one implementation copied and then locally edited — 190 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 (16 lines × 2 locations) packages/lint-framework/src/lint/domUtils.ts:12— packages/lint-framework/src/lint/domUtils.ts:12 · packages/wordpress-plugin/src/harper/domUtils.ts:11 — 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 (15 lines × 2 locations) packages/components/src/lib/Input.svelte:44— packages/components/src/lib/Input.svelte:44 · packages/components/src/lib/Select.svelte:25 — 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 (14 matched lines × 2 locations) · ×1
Duplicated block with local edits (14 matched lines × 2 locations) packages/wordpress-plugin/src/harper/LintListItem.tsx:12— packages/wordpress-plugin/src/harper/LintListItem.tsx:12 · packages/wordpress-plugin/src/harper/SuggestionControl.tsx:69 — the two spans are one implementation copied and then locally edited — 140 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 (12 lines × 3 locations) packages/lint-framework/src/lint/editorUtils.ts:21— packages/lint-framework/src/lint/editorUtils.ts:21 · packages/lint-framework/src/lint/editorUtils.ts:62 · packages/lint-framework/src/lint/editorUtils.ts:90 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 2 locations) harper-desktop/src/lib/settings/pages/RulesPage.svelte:105— harper-desktop/src/lib/settings/pages/RulesPage.svelte:105 · harper-desktop/src/lib/settings/pages/RulesPage.svelte:131 — 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 with local edits (8 matched lines × 2 locations) · ×1
Duplicated block with local edits (8 matched lines × 2 locations) harper-desktop/src/lib/settings/pages/DictionaryPage.svelte:130— harper-desktop/src/lib/settings/pages/DictionaryPage.svelte:130 · packages/web/src/routes/weir/studio/+page.svelte:352 — the two spans are one implementation copied and then locally edited — 53 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 (7 matched lines × 2 locations) · ×1
Duplicated block with local edits (7 matched lines × 2 locations) packages/chrome-plugin/public/google-docs-bridge.js:384— packages/chrome-plugin/public/google-docs-bridge.js:384 · packages/chrome-plugin/public/google-docs-bridge.js:393 — the two spans are one implementation copied and then locally edited — 73 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (5 lines × 2 locations) packages/web/src/lib/marketing/SveltePressGlobalLayout.svelte:5— packages/web/src/lib/marketing/SveltePressGlobalLayout.svelte:5 · packages/web/src/lib/marketing/SveltePressPageLayout.svelte:5 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
Complex function renderLintBoxes (cyclomatic 26, cognitive 47) packages/lint-framework/src/lint/Highlights.ts:62— renderLintBoxes has cyclomatic complexity 26 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.
Complex function buildRenderNodes (cyclomatic 19, cognitive 22) packages/chrome-plugin/src/options/StructuredRuleSettings.svelte:201— buildRenderNodes has cyclomatic complexity 19 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 (anonymous) (cyclomatic 17, cognitive 15) packages/chrome-plugin/src/contentScript/index.ts:162— (anonymous) has cyclomatic complexity 17 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 isVisible (cyclomatic 16, cognitive 21) packages/lint-framework/src/lint/domUtils.ts:151— isVisible has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function serializeArg (cyclomatic 16, cognitive 13) packages/harper.js/src/Serializer.ts:51— serializeArg 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.
Complex function localeToDialect (cyclomatic 15, cognitive 17) packages/chrome-plugin/src/background/detectDialect.ts:17— localeToDialect has cyclomatic complexity 15 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.
Complex function getGoogleDocsHighlightRects (cyclomatic 14, cognitive 16) packages/lint-framework/src/lint/computeLintBoxes/googleDocsUtilities.ts:235— getGoogleDocsHighlightRects has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildRectSnapshot (cyclomatic 13, cognitive 18) packages/chrome-plugin/src/contentScript/googleDocs.ts:434— buildRectSnapshot has cyclomatic complexity 13 and cognitive complexity 18; 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 initializeFromSettings (cyclomatic 13, cognitive 17) packages/obsidian-plugin/src/State.ts:58— initializeFromSettings has cyclomatic complexity 13 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.
Complex function handleKeydown (cyclomatic 13, cognitive 12) packages/chrome-plugin/src/options/Options.svelte:298— handleKeydown has cyclomatic complexity 13 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.
Complex function supportsCustomHighlights (cyclomatic 13, cognitive 11) packages/lint-framework/src/lint/Highlights.ts:386— supportsCustomHighlights has cyclomatic complexity 13 and cognitive complexity 11; 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 renderStructuredSettings (cyclomatic 12, cognitive 20) packages/obsidian-plugin/src/HarperSettingTab.ts:320— renderStructuredSettings has cyclomatic complexity 12 and cognitive complexity 20; 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 computeLintBoxes (cyclomatic 12, cognitive 16) packages/lint-framework/src/lint/computeLintBoxes/index.ts:28— computeLintBoxes has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildLogicalSnapshot (cyclomatic 12, cognitive 15) packages/chrome-plugin/src/contentScript/googleDocs.ts:365— buildLogicalSnapshot has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function positionMirror (cyclomatic 12, cognitive 11) packages/lint-framework/src/lint/TextFieldRange.ts:125— positionMirror has cyclomatic complexity 12 and cognitive complexity 11; 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 isUpToDate (cyclomatic 12, cognitive 9) packages/web/src/lib/marketing/versions.ts:15— isUpToDate has cyclomatic complexity 12 and cognitive complexity 9; 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 requestLintUpdate (cyclomatic 11, cognitive 12) packages/lint-framework/src/lint/LintFramework.ts:127— requestLintUpdate has cyclomatic complexity 11 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 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 getCaretPosition (cyclomatic 11, cognitive 12) packages/lint-framework/src/lint/editorUtils.ts:121— getCaretPosition has cyclomatic complexity 11 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/obsidian-plugin/src/lint.ts · ×1
packages/obsidian-plugin/src/lint.ts: 936 lines of code packages/obsidian-plugin/src/lint.ts:1— packages/obsidian-plugin/src/lint.ts has 936 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/chrome-plugin/src/background/index.ts · ×1
packages/chrome-plugin/src/background/index.ts: 798 lines of code packages/chrome-plugin/src/background/index.ts:1— packages/chrome-plugin/src/background/index.ts has 798 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/chrome-plugin/public/google-docs-bridge.js · ×1
packages/chrome-plugin/public/google-docs-bridge.js: 663 lines of code packages/chrome-plugin/public/google-docs-bridge.js:1— packages/chrome-plugin/public/google-docs-bridge.js has 663 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/chrome-plugin/src/options/Options.svelte · ×1
packages/chrome-plugin/src/options/Options.svelte: 651 lines of code packages/chrome-plugin/src/options/Options.svelte:1— packages/chrome-plugin/src/options/Options.svelte has 651 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/lint-framework/src/lint/SuggestionBox.ts · ×1
packages/lint-framework/src/lint/SuggestionBox.ts: 569 lines of code packages/lint-framework/src/lint/SuggestionBox.ts:1— packages/lint-framework/src/lint/SuggestionBox.ts has 569 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/obsidian-plugin/src/HarperSettingTab.ts · ×1
packages/obsidian-plugin/src/HarperSettingTab.ts: 555 lines of code packages/obsidian-plugin/src/HarperSettingTab.ts:1— packages/obsidian-plugin/src/HarperSettingTab.ts has 555 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/chrome-plugin/src/contentScript/googleDocs.ts · ×1
packages/chrome-plugin/src/contentScript/googleDocs.ts: 489 lines of code packages/chrome-plugin/src/contentScript/googleDocs.ts:1— packages/chrome-plugin/src/contentScript/googleDocs.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.
Dead file (~326 LoC) harper-desktop/src/lib/settings/settings-data.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (harper-desktop/src/lib/settings/SettingsApp.svelte, harper-desktop/src/lib/settings/SettingsSidebar.svelte, harper-desktop/src/lib/settings/pages/GeneralPage.svelte 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 (~319 LoC) harper-desktop/src/lib/settings/pages/RulesPage.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (harper-desktop/src/lib/settings/SettingsApp.svelte) — 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 (~275 LoC) harper-desktop/src/lib/client.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~270 LoC) packages/web/src/lib/marketing/data.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/web/src/lib/marketing/IntegrationTile.svelte, packages/web/src/lib/marketing/MarketingDocSearch.svelte, packages/web/src/lib/marketing/MarketingFooter.svelte 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 (~269 LoC) harper-desktop/src/lib/settings/pages/GeneralPage.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (harper-desktop/src/lib/settings/SettingsApp.svelte) — 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 (~197 LoC) packages/web/src/lib/components/Loader.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~178 LoC) harper-desktop/src/lib/settings/pages/GettingStartedPage.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (harper-desktop/src/lib/settings/SettingsApp.svelte) — 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 (~174 LoC) harper-desktop/src/lib/settings/pages/IntegrationsPage.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (harper-desktop/src/lib/settings/SettingsApp.svelte) — 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 (~147 LoC) harper-desktop/src/lib/settings/pages/DictionaryPage.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (harper-desktop/src/lib/settings/SettingsApp.svelte) — 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 (~120 LoC) packages/web/src/lib/GitHubClient.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~96 LoC) packages/web/src/lib/components/BarChart.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/web/src/lib/components/AnalyticsPage.svelte, packages/web/src/lib/components/LintKindChart.svelte) — 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 (~80 LoC) packages/components/src/lib/index.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~75 LoC) harper-desktop/src/lib/settings/components/AppPickerModal.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (harper-desktop/src/lib/settings/pages/IntegrationsPage.svelte) — 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 (~66 LoC) harper-desktop/src/lib/settings/components/AppIcon.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (harper-desktop/src/lib/settings/components/AppPickerModal.svelte, harper-desktop/src/lib/settings/pages/GettingStartedPage.svelte, harper-desktop/src/lib/settings/pages/IntegrationsPage.svelte) — 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 (~62 LoC) harper-desktop/src/lib/settings/pages/WeirpacksPage.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (harper-desktop/src/lib/settings/SettingsApp.svelte) — 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 (~51 LoC) harper-desktop/src/lib/settings/SettingsApp.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~48 LoC) packages/web/src/lib/components/WeirStudioFileExplorer.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~46 LoC) packages/web/src/lib/db/models/UpdateCheckCounts.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~45 LoC) packages/components/src/lib/DelayedRender.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/components/src/lib/index.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 (~41 LoC) packages/web/src/lib/db/models/ProblematicLints.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~40 LoC) packages/web/src/lib/db/models/UninstallFeedback.ts— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~31 LoC) packages/web/src/lib/marketing/MarketingHeader.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~29 LoC) packages/components/src/lib/IconButton.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/components/src/lib/index.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 (~26 LoC) packages/web/src/lib/components/WeirStudioWorkspace.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~22 LoC) harper-desktop/src/lib/EditorView.svelte— no import path from any entry point (97 application, 26 tooling, 57 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency 'flowbite' — Declared in packages/chrome-plugin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'http-server' — Declared in packages/chrome-plugin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'tslib' — Declared in packages/chrome-plugin/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.
Duplicated predicate packages/lint-framework/src/lint/domUtils.ts:124— `startFound && traversed + childText.length >= span.end` appears character-identically in 2 files — packages/lint-framework/src/lint/domUtils.ts, packages/wordpress-plugin/src/harper/domUtils.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/lint-framework/src/lint/domUtils.ts:119— `traversed + childText.length > span.start && !startFound` appears character-identically in 2 files — packages/lint-framework/src/lint/domUtils.ts, packages/wordpress-plugin/src/harper/domUtils.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/chrome-plugin/public/google-docs-bridge-request-handler.js:139— `value != null && typeof value === 'object'` appears character-identically in 2 files — packages/chrome-plugin/public/google-docs-bridge-request-handler.js, packages/chrome-plugin/src/contentScript/GoogleDocsBridgeClient.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 harper-core/src/linting/did_past.rs:28— `(k.is_verb_simple_past_form() || k.is_verb_past_form()) && !k.is_verb_lemma()` appears character-identically in 2 files — harper-core/src/linting/did_past.rs, harper-core/src/linting/helped_past.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate harper-desktop/src-tauri/src/communication/message.rs:167— `bundle_id == "com.example.Editor" && !enabled` appears character-identically in 2 files — harper-desktop/src-tauri/src/communication/message.rs, harper-desktop/src-tauri/src/communication/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate harper-core/src/linting/to_two_too/to_too_adjective_end.rs:53— `idx < tokens.len() && tokens[idx].kind.is_whitespace()` appears character-identically in 2 files — harper-core/src/linting/to_two_too/to_too_adjective_end.rs, harper-core/src/linting/to_two_too/to_too_adjective_punct.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate harper-cli/src/main.rs:703— `line.is_empty() || line.starts_with('#')` appears character-identically in 2 files — harper-cli/src/main.rs, harper-core/src/spell/rune/word_list.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate harper-core/src/linting/to_two_too/to_too_adjective_end.rs:68— `prev_non_ws && prepositional_preceder().matches_token(prev_token, source)` appears character-identically in 2 files — harper-core/src/linting/to_two_too/to_too_adjective_end.rs, harper-core/src/linting/to_two_too/to_too_adjective_punct.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Orphaned file harper-core/src/parsers/org_mode.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file harper-core/src/parsers/collapse_identifiers.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file harper-literate-haskell/src/masker.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file harper-core/src/linting/looking_forward_to.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file harper-python/src/lib.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file harper-comments/src/masker.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Silent fallback default in catch packages/chrome-plugin/tests/googleDocsTestUtils.ts:52— `openLiveGoogleDoc` 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 packages/lint-framework/src/lint/googleDocsAdapter.ts:70— `maybeComputeGoogleDocsLintBoxes` 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 packages/lint-framework/src/lint/computeLintBoxes/index.ts:98— `computeLintBoxes` 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 177 significant file(s) lose their only recent owner: harper-core/src/linting/regionalisms.rs, harper-core/src/linting/adjective_of_a.rs, harper-core/src/linting/redundant_acronyms.rs, harper-core/src/linting/full_to_the_brim.rs, harper-core/src/linting/few_units_of_time_ago.rs, harper-core/src/linting/throw_baby_with_bathwater.rs, harper-core/src/linting/all_intents_and_purposes.rs, harper-core/src/linting/code_in_write_in.rs (+169 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 30 significant file(s) lose their only recent owner: harper-desktop/src-tauri/src/main.rs, packages/chrome-plugin/src/contentScript/googleDocs.ts, harper-desktop/src-tauri/src/communication/mod.rs, harper-desktop/src-tauri/src/mac_broker/accessibility_text.rs, harper-core/src/linting/criteria_phenomena/plural_criterion_phenomenon.rs, harper-desktop/src-tauri/src/highlighter/window_manager.rs, harper-desktop/src-tauri/src/communication/message.rs, harper-core/src/weirpack/mod.rs (+22 more). Pair on, review, or document these before any departure.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 164 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
Fat interface: Linter (37 required operations) packages/harper.js/src/Linter.ts:14— `Linter` declares 37 required operations: `setup`, `lint`, `organizedLints`, `applySuggestion`, `isLikelyEnglish`, `isolateEnglish`, `getLintConfig`, `getDefaultLintConfigAsJSON`, `getDefaultLintConfig`, `getStructuredLintConfig`, `getStructuredLintConfigJSON`, `setLintConfig`, `getLintConfigAsJSON`, `setLintConfigWithJSON`, `getLintDescriptionsAsJSON`, `getLintDescriptions`, `getLintDescriptionsHTMLAsJSON`, `getLintDescriptionsHTML`, `toTitleCase`, `dispose`, `ignoreLint`, `ignoreLints`, `ignoreLintHash`, `exportIgnoredLints`, `importIgnoredLints`, `contextHash`, `clearIgnoredLints`, `clearWords`, `importWords`, `exportWords`, `getDialect`, `setDialect`, `summarizeStats`, `generateStatsFile`, `importStatsFile`, `loadWeirpackFromBlob`, `loadWeirpackFromBytes`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 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 (209 single-owned of 532 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; 532 of the 760 production source files in this repository met that bar). They are anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: harper-cli/src/annotate.rs, harper-core/src/spell/rune/matcher.rs.
Documentation: no build, run or usage example README.md:1— the repository holds project manifests and neither `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.
No ADRs found — 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/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 31 project(s) overshoot their size bounds, lowering Project Cohesion to 9.4/10. The most over is `harper-core` (98158 LoC, 631 module-visible types across 36 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 6 of 532 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; 532 of the 760 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: harper-core/src/parsers/org_mode.rs, harper-core/src/parsers/collapse_identifiers.rs, harper-literate-haskell/src/masker.rs, harper-core/src/linting/looking_forward_to.rs, harper-python/src/lib.rs, harper-comments/src/masker.rs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 3/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `harper-cli`, `harper-core`, `harper-desktop`, `packages/components`, `packages/harper-editor` and 1 more.
Changelog looks stale/thin — The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
Nullable reference types not enabled everywhere — 0/1 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Subsumed condition operand harper-cli/tests/output_format.rs:165— `stdout.contains("No lints found")` can never decide this `||` — every value satisfying `stdout.contains("No lints found")` also satisfies `stdout.contains("lints")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Outdated: fastlane — `fastlane` is resolved to 2.240.1 in the committed Gemfile.lock but 2.241.2 is the current release on rubygems.org, and it already satisfies the `"~> 2.238"` requirement declared in Gemfile — so the lockfile is behind this repository's own declared range. This build is therefore missing every fix published since, including any security fix. Run `bundle update fastlane` and commit the updated Gemfile.lock.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `packages/lint-framework/src/lint/lintKindColor.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a17b00-04e6-78ba-8385-76423eb89d4a · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 151 · Warnings: 621 · Recommendations: 50 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 27-10-2026 @ 01:36 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.