Public report of danielmiessler/Fabric, published 13 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 13 November 2026, 11:39 UTC · Survey ID cd_7ab2441b91564ee9881aab3cad465efe
danielmiessler/Fabric
Measured 13 November 2026, 11:38 UTC, at code version 793f78f
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).
CAI scoreAt riskUp 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 26,395 lines of product code in 3 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 45
Findings by how serious they are
54 critical350 serious55 minor
20 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 11:38 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
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. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
75of 75 dimensions measured by tools.
426of 459 findings point to an exact file and line, so you can open each one in the code. The other 33 concern the repository as a whole, such as missing documentation.
75dimensions across 8 lenses, read from 26,395 lines of product code in 3 projects.
danielmiessler/Fabric is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 52 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 45, is the weakest lens and counts most in the score. The best first step for the work it takes is pinning the dependencies to tagged releases, worth about 2 points. Adding tests for the code no test reaches would lift Production Readiness itself, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 57.
Fourteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three pipeline steps run downloads nobody checks, and twenty-two form fields can't be read by a screen reader. Pinning each tool to an exact version, checking each download against a checksum and labelling the form fields would close these risks. Updating the vulnerable packages would fix the two packages with a known security hole, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The two buttons or links with no name need a name, even when they only show an icon.
The product code is 26,395 lines, about €50,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.
Cancellation propagation · Async function without AbortSignal: RequestHandler web/src/routes/obsidian/+server.ts
Cancellation propagation · Async function without AbortSignal: RequestHandler web/src/routes/notes/+server.ts
Cancellation propagation · Async function without AbortSignal: RequestHandler web/src/routes/chat/+server.ts
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 83 findings
These 83 critical or serious findings were in the previous survey, on 23 October 2026, and are gone from this one.
Dependency Vulnerabilities · Medium CVE: GO-2026-4599 REDACTED
Test Coverage · No test reaches this file web/src/lib/store/chat-config.ts
Test Coverage · No test reaches this file web/src/lib/components/ui/toc/Toc.svelte
Test Coverage · No test reaches this file web/src/lib/components/settings/LanguageSelector.svelte
Test Coverage · No test reaches this file web/src/lib/services/toast-service.ts
Test Coverage · No test reaches this file web/src/lib/components/ui/toast/Toast.svelte
Test Coverage · No test reaches this file web/src/lib/config/features.ts
Test Coverage · No test reaches this file web/src/lib/actions/clickOutside.ts
Test Coverage · No test reaches this file web/src/lib/components/ui/button/button.svelte
Test Coverage · No test reaches this file web/src/lib/components/posts/PostCard.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/help/HelpModal.svelte
Test Coverage · No test reaches this file web/src/lib/store/language-store.ts
Test Coverage · No test reaches this file web/src/routes/+layout.svelte
Test Coverage · No test reaches this file web/src/routes/+page.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/connections/canvas.ts
Test Coverage · No test reaches this file web/src/lib/components/ui/cards/card.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/input/Input.svelte
Test Coverage · No test reaches this file web/src/lib/api/contexts.ts
Test Coverage · No test reaches this file web/src/lib/components/ui/modal/Modal.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/select/select-value.svelte
Test Coverage · No test reaches this file web/src/lib/components/posts/PostLayout.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/checkbox/Checkbox.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/select/select-content.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/select/select-trigger.svelte
Test Coverage · No test reaches this file web/src/lib/components/posts/PostContent.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/select/select-item.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/select/select.svelte
Test Coverage · No test reaches this file web/src/routes/chat/+layout.svelte
Test Coverage · No test reaches this file web/src/routes/posts/[slug]/+page.svelte
Test Coverage · No test reaches this file web/src/routes/tags/+page.svelte
Test Coverage · No test reaches this file web/src/routes/tags/[tag]/+page.svelte
Test Coverage · No test reaches this file web/src/lib/components/posts/PostMeta.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/label/index.js
Test Coverage · No test reaches this file web/src/lib/components/ui/select/index.js
Test Coverage · No test reaches this file web/src/lib/components/ui/spinner/spinner.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/textarea/textarea.svelte
Test Coverage · No test reaches this file web/src/lib/utils/utils.ts
Test Coverage · No test reaches this file web/src/lib/components/ui/select/select-label.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/select/select-separator.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/slider/index.js
Test Coverage · No test reaches this file web/src/lib/components/ui/textarea/index.js
Test Coverage · No test reaches this file web/src/routes/about/+page.ts
Test Coverage · No test reaches this file web/src/routes/chat/+page.ts
Test Coverage · No test reaches this file web/src/routes/contact/+page.ts
Test Coverage · No test reaches this file web/src/lib/components/ui/checkbox/index.ts
Test Coverage · No test reaches this file web/src/lib/components/ui/connections/colors.ts
Test Coverage · No test reaches this file web/src/lib/components/ui/input/index.ts
Test Coverage · No test reaches this file web/src/lib/components/home/Footer.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/buymeacoffee/BuyMeCoffee.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/label/label.svelte
Test Coverage · No test reaches this file web/src/lib/components/ui/toast/ToastContainer.svelte
Test Coverage · No test reaches this file web/src/routes/+layout.ts
Test Coverage · No test reaches this file web/src/routes/about/+page.svelte
Test Coverage · No test reaches this file web/src/lib/components/contact/Contact.svelte
Test Coverage · No test reaches this file web/src/lib/interfaces/LanguageDisplay.svelte
Test Coverage · No test reaches this file web/src/routes/about/+error.svelte
Test Coverage · No test reaches this file web/src/routes/chat/+page.svelte
Test Coverage · No test reaches this file web/src/routes/contact/+error.svelte
Test Coverage · No test reaches this file web/src/routes/contact/+page.svelte
Test Coverage · No test reaches this file web/src/routes/posts/+error.svelte
Test Coverage · No test reaches this file web/src/routes/posts/[slug]/+error.svelte
Test Coverage · No test reaches this file web/src/routes/+page.ts
Visual & motion safety · Focus outline removed in CSS without a :focus replacement web/src/lib/components/chat/Chat.svelte
Visual & motion safety · Focus outline removed in CSS without a :focus replacement web/src/lib/components/chat/Chat.svelte
Rebuild cost: about €50,000 · Estimate
Cost to rebuild
€17,000 to €84,000, for 277 to 880 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 26,395 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
Add tests that import the unreached modules (directly or through their public entry).
Raises the score by about 3 points · Medium effort · Test Coverage
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €50,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 45 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. 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 Dependency Hygiene findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.9 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 6% on every change. The history of the code shows how much it changes: about 30,814 lines over the last 90 days, which is about 124,968 lines a year. At that pace, the extra work comes to an estimated 8.9 to 53.5 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: 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.
103 modules, with 118 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 63 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.
2 pairs of types, where a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache uses a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/git.
github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache uses github.com/danielmiessler/fabric/cmd/generate_changelog/internal/git, so a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/git can break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache, while a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache can't break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/git.
Position
Below the diagonal: github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache uses a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/github.
github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache uses github.com/danielmiessler/fabric/cmd/generate_changelog/internal/github, so a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/github can break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache, while a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache can't break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/github.
Position
Below the diagonal: github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/domain uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/domain, while a change to github.com/danielmiessler/fabric/internal/domain can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/domain uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/db/fsdb uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/db/fsdb uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/db/fsdb, while a change to github.com/danielmiessler/fabric/internal/plugins/db/fsdb can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/db/fsdb uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/strategy uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/strategy uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/strategy, while a change to github.com/danielmiessler/fabric/internal/plugins/strategy can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/strategy uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/tools/custom_patterns uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/tools/custom_patterns uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/tools/custom_patterns, while a change to github.com/danielmiessler/fabric/internal/tools/custom_patterns can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/tools/custom_patterns uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/tools/firecrawl uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/tools/firecrawl uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/tools/firecrawl, while a change to github.com/danielmiessler/fabric/internal/tools/firecrawl can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/tools/firecrawl uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/tools/jina uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/tools/jina uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/tools/jina, while a change to github.com/danielmiessler/fabric/internal/tools/jina can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/tools/jina uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/tools/lang uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/tools/lang uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/tools/lang, while a change to github.com/danielmiessler/fabric/internal/tools/lang can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/tools/lang uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/tools/youtube uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/tools/youtube uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/tools/youtube, while a change to github.com/danielmiessler/fabric/internal/tools/youtube can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/tools/youtube uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal uses a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/config.
github.com/danielmiessler/fabric/cmd/generate_changelog/internal uses github.com/danielmiessler/fabric/cmd/generate_changelog/internal/config, so a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/config can break github.com/danielmiessler/fabric/cmd/generate_changelog/internal, while a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal can't break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/config.
Position
Below the diagonal: github.com/danielmiessler/fabric/cmd/generate_changelog/internal uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal uses a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache.
github.com/danielmiessler/fabric/cmd/generate_changelog/internal uses github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache, so a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache can break github.com/danielmiessler/fabric/cmd/generate_changelog/internal, while a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal can't break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache.
Position
Below the diagonal: github.com/danielmiessler/fabric/cmd/generate_changelog/internal uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/config.
github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses github.com/danielmiessler/fabric/cmd/generate_changelog/internal/config, so a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/config can break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog, while a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog can't break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/config.
Position
Below the diagonal: github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/git.
github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses github.com/danielmiessler/fabric/cmd/generate_changelog/internal/git, so a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/git can break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog, while a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog can't break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/git.
Position
Below the diagonal: github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/github.
github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses github.com/danielmiessler/fabric/cmd/generate_changelog/internal/github, so a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/github can break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog, while a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog can't break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/github.
Position
Below the diagonal: github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses a type in github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache.
github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache, so a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache can break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog, while a change to github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog can't break github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache.
Position
Below the diagonal: github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/plugins/ai uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/tools uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/tools, while a change to github.com/danielmiessler/fabric/internal/tools can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/tools uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/tools uses a type in github.com/danielmiessler/fabric/internal/plugins/db/fsdb.
github.com/danielmiessler/fabric/internal/tools uses github.com/danielmiessler/fabric/internal/plugins/db/fsdb, so a change to github.com/danielmiessler/fabric/internal/plugins/db/fsdb can break github.com/danielmiessler/fabric/internal/tools, while a change to github.com/danielmiessler/fabric/internal/tools can't break github.com/danielmiessler/fabric/internal/plugins/db/fsdb.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/tools uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in github.com/danielmiessler/fabric/internal/core uses a type in github.com/danielmiessler/fabric/internal/plugins/db/fsdb.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/plugins/db/fsdb, so a change to github.com/danielmiessler/fabric/internal/plugins/db/fsdb can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/plugins/db/fsdb.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/core uses a type in github.com/danielmiessler/fabric/internal/plugins/strategy.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/plugins/strategy, so a change to github.com/danielmiessler/fabric/internal/plugins/strategy can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/plugins/strategy.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/core uses a type in github.com/danielmiessler/fabric/internal/tools/custom_patterns.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/tools/custom_patterns, so a change to github.com/danielmiessler/fabric/internal/tools/custom_patterns can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/tools/custom_patterns.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/core uses a type in github.com/danielmiessler/fabric/internal/tools/firecrawl.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/tools/firecrawl, so a change to github.com/danielmiessler/fabric/internal/tools/firecrawl can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/tools/firecrawl.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/tools/jina, so a change to github.com/danielmiessler/fabric/internal/tools/jina can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/tools/jina.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/tools/lang, so a change to github.com/danielmiessler/fabric/internal/tools/lang can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/tools/lang.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/core uses a type in github.com/danielmiessler/fabric/internal/tools/youtube.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/tools/youtube, so a change to github.com/danielmiessler/fabric/internal/tools/youtube can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/tools/youtube.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/core uses github.com/danielmiessler/fabric/internal/tools, so a change to github.com/danielmiessler/fabric/internal/tools can break github.com/danielmiessler/fabric/internal/core, while a change to github.com/danielmiessler/fabric/internal/core can't break github.com/danielmiessler/fabric/internal/tools.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/core uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/anthropic, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/anthropic can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/anthropic, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/anthropic can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/anthropic, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/anthropic can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/anthropic, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/anthropic can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/anthropic uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/azure uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/azure uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/azure, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/azure can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/azure uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/azure uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/azure uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/azure, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/azure can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/azure uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/azure_entra uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/azure_entra uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/azure_entra, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/azure_entra can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/azure_entra uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/azure_entra uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/azure_entra uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/azure_entra, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/azure_entra can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/azure_entra uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/azureaigateway uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/bedrock, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/bedrock can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/bedrock, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/bedrock can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/bedrock, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/bedrock can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/bedrock, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/bedrock can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/bedrock uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/claudecode, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/claudecode can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/claudecode, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/claudecode can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/claudecode, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/claudecode can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/claudecode, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/claudecode can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/claudecode uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/codex uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/codex uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/codex, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/codex can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/codex uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/codex uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/codex uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/codex, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/codex can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/codex uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/codex uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/codex uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/codex, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/codex can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/codex uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/codex uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/codex uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/codex, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/codex can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/codex uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/copilot, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/copilot can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/copilot, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/copilot can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/copilot, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/copilot can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/copilot, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/copilot can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/copilot uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/digitalocean uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/digitalocean uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/digitalocean, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/digitalocean can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/digitalocean uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/digitalocean uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/digitalocean uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/digitalocean, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/digitalocean can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/digitalocean uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/dryrun, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/dryrun can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/dryrun, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/dryrun can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/dryrun, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/dryrun can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/dryrun, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/dryrun can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/dryrun uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/exolab uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/exolab uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/exolab, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/exolab can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/exolab uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/exolab uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/exolab uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/exolab, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/exolab can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/exolab uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/gemini, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/gemini can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/gemini, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/gemini can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/gemini, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/gemini can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/gemini, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/gemini can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/gemini uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/lmstudio uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/ollama, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/ollama can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/ollama, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/ollama can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/ollama, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/ollama can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/ollama, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/ollama can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/ollama uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/openai uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/openai uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/openai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/openai can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/openai uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/openai uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/openai uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/openai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/openai can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/openai uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/openai uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/openai uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/openai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/openai can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/openai uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/openai uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/openai uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/openai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/openai can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/openai uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/openai_compatible uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/openai_compatible uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/openai_compatible, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/openai_compatible can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/openai_compatible uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/openai_compatible uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/openai_compatible uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/openai_compatible, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/openai_compatible can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/openai_compatible uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/perplexity uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/perplexity uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/perplexity, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/perplexity can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/perplexity uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/perplexity uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/perplexity uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/perplexity, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/perplexity can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/perplexity uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses a type in github.com/danielmiessler/fabric/internal/chat.
github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses github.com/danielmiessler/fabric/internal/chat, so a change to github.com/danielmiessler/fabric/internal/chat can break github.com/danielmiessler/fabric/internal/plugins/ai/vertexai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/vertexai can't break github.com/danielmiessler/fabric/internal/chat.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses a type in github.com/danielmiessler/fabric/internal/plugins.
github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses github.com/danielmiessler/fabric/internal/plugins, so a change to github.com/danielmiessler/fabric/internal/plugins can break github.com/danielmiessler/fabric/internal/plugins/ai/vertexai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/vertexai can't break github.com/danielmiessler/fabric/internal/plugins.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses a type in github.com/danielmiessler/fabric/internal/domain.
github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/plugins/ai/vertexai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/vertexai can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/plugins/ai/vertexai, while a change to github.com/danielmiessler/fabric/internal/plugins/ai/vertexai can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/plugins/ai/vertexai uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/cli uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/cli, while a change to github.com/danielmiessler/fabric/internal/cli can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/cli uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in github.com/danielmiessler/fabric/internal/cli uses a type in github.com/danielmiessler/fabric/internal/plugins/db/fsdb.
github.com/danielmiessler/fabric/internal/cli uses github.com/danielmiessler/fabric/internal/plugins/db/fsdb, so a change to github.com/danielmiessler/fabric/internal/plugins/db/fsdb can break github.com/danielmiessler/fabric/internal/cli, while a change to github.com/danielmiessler/fabric/internal/cli can't break github.com/danielmiessler/fabric/internal/plugins/db/fsdb.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/cli uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/cli uses github.com/danielmiessler/fabric/internal/core, so a change to github.com/danielmiessler/fabric/internal/core can break github.com/danielmiessler/fabric/internal/cli, while a change to github.com/danielmiessler/fabric/internal/cli can't break github.com/danielmiessler/fabric/internal/core.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/cli uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/server uses github.com/danielmiessler/fabric/internal/domain, so a change to github.com/danielmiessler/fabric/internal/domain can break github.com/danielmiessler/fabric/internal/server, while a change to github.com/danielmiessler/fabric/internal/server can't break github.com/danielmiessler/fabric/internal/domain.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/server uses a module listed above it, which is the healthy direction.
9 pairs of types, where a type in github.com/danielmiessler/fabric/internal/server uses a type in github.com/danielmiessler/fabric/internal/plugins/db/fsdb.
github.com/danielmiessler/fabric/internal/server uses github.com/danielmiessler/fabric/internal/plugins/db/fsdb, so a change to github.com/danielmiessler/fabric/internal/plugins/db/fsdb can break github.com/danielmiessler/fabric/internal/server, while a change to github.com/danielmiessler/fabric/internal/server can't break github.com/danielmiessler/fabric/internal/plugins/db/fsdb.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/server uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/danielmiessler/fabric/internal/server uses a type in github.com/danielmiessler/fabric/internal/tools/youtube.
github.com/danielmiessler/fabric/internal/server uses github.com/danielmiessler/fabric/internal/tools/youtube, so a change to github.com/danielmiessler/fabric/internal/tools/youtube can break github.com/danielmiessler/fabric/internal/server, while a change to github.com/danielmiessler/fabric/internal/server can't break github.com/danielmiessler/fabric/internal/tools/youtube.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/server uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in github.com/danielmiessler/fabric/internal/server uses a type in github.com/danielmiessler/fabric/internal/plugins/ai.
github.com/danielmiessler/fabric/internal/server uses github.com/danielmiessler/fabric/internal/plugins/ai, so a change to github.com/danielmiessler/fabric/internal/plugins/ai can break github.com/danielmiessler/fabric/internal/server, while a change to github.com/danielmiessler/fabric/internal/server can't break github.com/danielmiessler/fabric/internal/plugins/ai.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/server uses a module listed above it, which is the healthy direction.
github.com/danielmiessler/fabric/internal/server uses github.com/danielmiessler/fabric/internal/core, so a change to github.com/danielmiessler/fabric/internal/core can break github.com/danielmiessler/fabric/internal/server, while a change to github.com/danielmiessler/fabric/internal/server can't break github.com/danielmiessler/fabric/internal/core.
Position
Below the diagonal: github.com/danielmiessler/fabric/internal/server uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 80% · Adequate · gated by D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
33
High / Critical
A03:2025 — Software Supply Chain Failures
20
High / Critical
A02:2025 — Security Misconfiguration
5
Medium
Roadmap
Top priorities: Add tests that import the unreached modules (directly or through their public entry); Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
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 — 54
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 — 350
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 — 55
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 20
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 75 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 75 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, 426 of 459 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 50 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 116 test source file(s) (.go) 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.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its Python distribution dependencies. Nothing was read about its Go 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Python distribution 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `internal/server/contexts.go`, `internal/server/patterns.go`, `internal/server/sessions.go`, `internal/util/groups_items.go`, `web/src/lib/services/PdfConversionService.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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — #10 CANCELED ------ > [builder 4/7] COPY REDACTED go.sum ./: ------ REDACTED:32 -------------------- 30 | && rm -f /tmp/go.tgz 31 | 32 | >>> COPY REDACTED go.sum ./ 33 | RUN go mod download 34 | -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref eacf0ab3-d9f6-4186-b6c0-2814f61ae348::zvrlds2jqx7a3fz3lhfavlm2f: "/go.sum": not found; runtime evidence skipped.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Go, Svelte components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Go, Svelte components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 61 further occurrence(s) are not listed individually; the score already reflects all 101.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X26 Unsynchronised callback handoff — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
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 (REDACTED, 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.
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.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 33 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 38 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Chatter.Send (cyclomatic 51), TranslatedHelpWriter.writeAllFlags (cyclomatic 43), APIConvert.ollamaChat (cyclomatic 39). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 38 together lifts Cyclomatic Complexity from 5.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 66 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with Generator.collectData (cognitive 162), Chatter.Send (cognitive 87), cli.handleToolProcessing (cognitive 78). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 2.0 to about 3.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.3 / 10Stronggated by 5 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.
Resolve the 2 MethodTooLong finding(s) in God Classes — start with ollama.go, chatter.go. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 TooManyFields finding(s) in God Classes — start with flags.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 FileTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
29 duplicated block group(s) detected. A further 28 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 2 of the 57 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 32 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with anthropic.go, backend_bedrock.go, walker.go. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Edited copy of a member (39 corresponding lines) finding(s) in Code Duplication — start with extension_manager.go, auth_transport.go, copilot.go. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with copilot.go (2), gemini.go. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ 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.
2 production modules (npm+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
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.
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 50 tests. Measured on the JavaScript/TypeScript suite only — at least 116 test source file(s) (.go) went unread, so its test quality is unmeasured and is not in these counts.
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
9 outdated, 1 author-deprecated direct Go module(s), 1 pinning or checksum defect(s). 35 of 35 direct requirement(s) were graded against proxy.golang.org (0 not served there, 1 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
Resolve the 1 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
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 44 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 7 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (37 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 8 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum) and package.json, 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: internal/core/chatter.go (12×51=612); internal/core/plugin_registry.go (11×33=363); internal/server/ollama.go (8×39=312) Repeated repair below the complexity floor: internal/plugins/ai/codex/codex.go (7 of 7 changes were fixes); internal/server/auth.go (6 of 7 changes were fixes); internal/server/serve.go (4 of 7 changes were fixes)
Resolve the 14 Hotspot finding(s) in Churn × Complexity Hotspots — start with chat.go (2), chatter.go, plugin_registry.go. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 13 Repeated repair finding(s) in Churn × Complexity Hotspots — start with REDACTED (2), codex.go, auth.go. — One of this dimension's main actionable groups (13 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.9 / 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.
32 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is cmd/generate_changelog/internal/changelog/generator.go. Counted over 102 of the 205 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
What to do
Resolve the 1 Off-boarding risk 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.
3 deducted task-comment markers across 26395 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
TodoComment · ×3web/src/routes/posts/+page.ts:4
What to do
Resolve the 3 TodoComment finding(s) in Explicit Debt — start with +page.ts, contexts.ts, geminicommon.go. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 62 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment Value8.1 / 10Strong✓ Tool-verified
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
Resolve the 1 redundant comment finding(s) in Comment Value — start with sanitize-html.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion3.3 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
1 of 3 build units (Go, Python, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.3 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
63 % of calls cross a namespace and 3 % go through an interface, but 49 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Pass-through layer finding(s) in Navigability — start with toast-service.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
33 finding(s): 0 critical, 22 high, 11 medium, 0 low. 14 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 7 file(s) — `internal/server/contexts.go` (lines 9–10, line 11, line 12), `internal/server/patterns.go` (lines 15–16, line 17, line 18), `internal/server/sessions.go` (lines 9–10, line 11, line 12), `internal/util/groups_items.go` (line 176), `web/.github/dependabot.yml`, … (+2 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 9 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 14 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 (14 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 7 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
7 of 102 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is scripts/python_ui/streamlit.py. Counted over 102 of the 205 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with streamlit.py. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, pattern-store.ts, attachment.go. — One of this dimension's main actionable groups (6 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 7 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.4 / 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. — web/src/lib/components/ui/connections/Connections.svelte:122
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 & labels4.6 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has 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. (×11) — web/src/lib/components/chat/Chat.svelte:164, web/src/lib/components/chat/ChatInput.svelte:343, web/src/lib/components/chat/Transcripts.svelte:66, …
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). (×2) — web/src/lib/components/chat/ChatMessages.svelte:175, web/src/lib/components/contact/Contact.svelte:24
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×11) — web/src/lib/components/chat/DropdownGroup.svelte:55, web/src/lib/components/chat/DropdownGroup.svelte:65, web/src/lib/components/chat/Models.svelte:12, …
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. (×2) — web/src/lib/components/chat/ModelConfig.svelte:69, web/src/lib/components/settings/LanguageSelector.svelte:21
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>. — web/src/app.html:2
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×3) — web/src/lib/components/ui/cards/card.svelte:35, web/src/lib/components/ui/help/HelpModal.svelte:26, web/src/routes/posts/+page.svelte:63
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 <canvas> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. — web/src/lib/components/ui/connections/Connections.svelte:122
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. — web/src/lib/components/ui/modal/Modal.svelte:14
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.
<span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×3) — web/src/lib/components/chat/ChatMessages.svelte:144, web/src/lib/components/chat/ChatMessages.svelte:145, web/src/lib/components/chat/ChatMessages.svelte:146
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — web/src/lib/components/terminal/Terminal.svelte:119
<button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — web/src/lib/components/ui/modal/PatternTilesModal.svelte:190
`.tag-panel` moves (`transition: left 0.3s 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. — web/src/lib/components/patterns/TagFilterPanel.svelte:70
`.resize-handle::after` moves (`transition: background-color 0.2s, width 0.2s`) 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. — web/src/lib/components/chat/Chat.svelte:244
`.vertical-resize-handle::after` moves (`transition: background-color 0.2s, height 0.2s`) 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. — web/src/lib/components/chat/Chat.svelte:281
`.spinner-border` moves (`animation: spin 0.75s linear 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. — web/src/lib/components/chat/Transcripts.svelte:116
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 · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`YouTube` is shared by every request (`initService` is called per request from the Gin handler `YouTubeHandler.Transcript`, on the one `YouTube` value that handler's shared receiver holds) but writes its fields outside any lock (normalizeRegex, service; e.g. `normalizeRegex` in `initService` at line 101). Unsynchronised concurrent writes are a data race in Go: an update is lost or a value tears, and a concurrent map write aborts the process. — REDACTED:84
What to do
Go: guard the state handlers share with a sync.Mutex held for the whole update (`mu.Lock(); defer mu.Unlock()`), make counters sync/atomic types (atomic.Int64) and caches a sync.Map, or keep per-request data in locals and the request context. `go test -race` over a handler test confirms the race and then its fix.
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 · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.
Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
`Attachment.ID` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — internal/domain/attachment.go:24
What to do
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Do you agree with this assessment?
DM4 · Rich vs anemic model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
The domain package `github.com/danielmiessler/fabric/internal/domain` imports `net/http` — an infrastructure concern (persistence/HTTP/broker/auth). The dependency direction points from the domain layer to infrastructure; invert it behind a domain-owned port. — internal/domain/attachment.go:11
What to do
Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.
Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.
Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `web`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /healthz handler) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add gosec / govulncheck (or golangci-lint) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9
`web/.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `gomod`, `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — web/.github/dependabot.yml:7
What to do
Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `github-actions`, `gomod`, `pip` — add those `package-ecosystem` entries to .github/dependabot.yml 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.
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.
`http.DefaultClient` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — cmd/generate_changelog/internal/github/client.go:38
`http.Head(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — internal/domain/attachment.go:67, internal/domain/attachment.go:151
`http.Get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — internal/domain/attachment.go:95, REDACTED:119
`http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — internal/server/ollama.go:199, internal/tools/jina/jina.go:56
What to do
Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type 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.
web/src/lib/components/patterns/PatternList.svelte:5 · web/src/lib/components/ui/modal/PatternTilesModal.svelte:4 — 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. — web/src/lib/components/patterns/PatternList.svelte:5
web/src/lib/components/ui/tagSearch/TagSearch.svelte:12 · web/src/routes/posts/+page.svelte:15 — 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. — web/src/lib/components/ui/tagSearch/TagSearch.svelte:12
web/src/lib/components/chat/Chat.svelte:42 · web/src/lib/components/chat/Chat.svelte:77 — 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. — web/src/lib/components/chat/Chat.svelte:42
web/src/routes/tags/+page.ts:7 · web/src/routes/tags/[tag]/+page.ts:7 — 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. — web/src/routes/tags/+page.ts:7
web/src/lib/components/ui/connections/ParticleSystem.ts:19 · web/src/lib/components/ui/connections/ParticleSystem.ts:48 — 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. — web/src/lib/components/ui/connections/ParticleSystem.ts:19
web/src/lib/store/pattern-store.ts:56 · web/src/lib/store/pattern-store.ts:70 — the two spans are one implementation copied and then locally edited — 72 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. — web/src/lib/store/pattern-store.ts:56
web/vite.config.ts:50 · web/vite.config.ts: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. Check what actually differs between the copies before collapsing them: every one of them is an argument to a `defineConfig(…)` call, so where these calls are a MATRIX of cases — one per input, differing precisely in the case each one pins — the repetition is the enumeration and extracting the shared part would delete cases rather than de-duplicate anything. — web/vite.config.ts:50
web/src/routes/chat/+server.ts:130 · web/src/routes/obsidian/+server.ts:61 — 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. — web/src/routes/chat/+server.ts:130
web/src/lib/api/base.ts:62 · web/src/lib/api/base.ts:79 — 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. — web/src/lib/api/base.ts:62
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
POST has cyclomatic complexity 13 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. — web/src/routes/obsidian/+server.ts:15
Do you agree with this assessment?
R3 · Large Files10.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.
Do you agree with this assessment?
R4 · Test Coverage1.5 / 10Critical✓ 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) — web/src/lib/services/ChatService.ts:1, web/src/lib/store/chat-store.ts:1, web/src/routes/chat/+server.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
145 file(s) (~5296 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: web/src/routes/api/youtube/transcript/+server.ts imports './$types', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — web
Nothing imports this binding — it is safe to review for removal. — web/src/lib/api/base.ts:60
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×3) — web/src/lib/components/chat/ChatInput.svelte:135, web/src/lib/components/ui/help/HelpModal.svelte:11, web/src/routes/posts/Search.svelte:9
This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments. — web/src/lib/services/ChatService.ts:40
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 web/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. (×9)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — 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.
Other · Code Health — Whether functions that make a cancellable request accept or pass on a context.Context or an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 20/40 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`RequestHandler` holds an AbortSignal but calls `writeFile(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `writeFile(…, { signal })`. (×2) — web/src/routes/obsidian/+server.ts:15, web/src/routes/notes/+server.ts:9
`RequestHandler` holds an AbortSignal but calls `fetch(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `fetch(…, { signal })`. — web/src/routes/chat/+server.ts:7
`saveToFile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — web/src/lib/store/note-store.ts:47
`loadPatterns` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — web/src/lib/store/pattern-store.ts:39
`loadSessions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — web/src/lib/store/session-store.ts:13
`loadSessionMessages` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — web/src/lib/store/session-store.ts:93
`fetchStrategies` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — web/src/lib/store/strategy-store.ts:19
`getTranscript` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — web/src/lib/services/transcriptService.ts:15
`stream` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — web/src/lib/api/base.ts:34
`refreshAccessToken` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — internal/tools/spotify/spotify.go:87
`doRequest` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — internal/tools/spotify/spotify.go:135
`Search` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. (×2) — internal/tools/serply/serply.go:58, internal/tools/firecrawl/firecrawl.go:66
`request` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — internal/tools/jina/jina.go:45
`fetch` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — internal/plugins/template/fetch.go:98
`downloadLocale` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:111
`ResolveType` calls `http.Head(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — internal/domain/attachment.go:52
`ContentBytes` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — internal/domain/attachment.go:82
`detectMimeTypeFromURL` calls `http.Head(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — internal/domain/attachment.go:150
What to do
Thread a context.Context or an AbortSignal through functions that make requests, so the work stops when its caller gives up.
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.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — web/src/lib/components/chat/DropdownGroup.svelte:36
`if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×13) — internal/util/utils.go:53, internal/util/utils.go:59, internal/util/utils.go:64, …
`if err := json.Unmarshal(data, &s); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/server/strategies.go:48
`if err := json.Unmarshal(data, &entry); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/plugins/ai/openai/models_cache.go:58
`if err := json.Unmarshal(body, &payload); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/plugins/ai/codex/errors.go:155
`if answerErr := setupQuestion.Ask(i18n.T(" ")); answerErr != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/core/plugin_registry.go:343
`if err = o.SaveEnvFile(); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/core/plugin_registry.go:363
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
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 — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 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.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no exported interface declares behaviour
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — #10 CANCELED ------ > [builder 4/7] COPY REDACTED go.sum ./: ------ REDACTED:32 -------------------- 30 | && rm -f /tmp/go.tgz 31 | 32 | >>> COPY REDACTED go.sum ./ 33 | RUN go mod download 34 | -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref eacf0ab3-d9f6-4186-b6c0-2814f61ae348::zvrlds2jqx7a3fz3lhfavlm2f: "/go.sum": not found; 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
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# and TypeScript only; Go, Python not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (domain), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 5 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — web/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — X1 reached only 28% of this repository's production lines — go (22,209 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 28% of this repository's production lines — go (22,209 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 21% of this repository's production lines — go (22,209 lines), python (2,058 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — X21 reached only 28% of this repository's production lines — go (22,209 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — X24 reached only 28% of this repository's production lines — go (22,209 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — 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
X29 Per-element action decided by a fixed element — X29 reached only 21% of this repository's production lines — go (22,209 lines), python (2,058 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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 · ×9
<input> without a programmatic label web/src/lib/components/chat/Transcripts.svelte:66— 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 web/src/lib/components/contact/Contact.svelte:9— 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 web/src/lib/components/contact/Contact.svelte:14— 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 web/src/lib/components/contact/Contact.svelte:18— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label web/src/lib/components/patterns/PatternList.svelte:85— 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 web/src/lib/components/terminal/Terminal.svelte:119— 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 web/src/lib/components/ui/checkbox/Checkbox.svelte:12— 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 web/src/lib/components/ui/input/Input.svelte:13— 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 web/src/lib/components/ui/modal/PatternTilesModal.svelte:85— 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· <select> without a programmatic label · ×8
<select> without a programmatic label web/src/lib/components/chat/DropdownGroup.svelte:55— 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 web/src/lib/components/chat/DropdownGroup.svelte:65— 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 web/src/lib/components/chat/Models.svelte:12— 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 web/src/lib/components/chat/Models.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 web/src/lib/components/chat/Patterns.svelte:37— 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 web/src/lib/components/chat/SessionSelector.svelte:69— 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 web/src/lib/components/settings/LanguageSelector.svelte:22— 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 web/src/lib/components/ui/select/select.svelte:11— 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 · ×5
<textarea> without a programmatic label web/src/lib/components/chat/Chat.svelte:164— 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 web/src/lib/components/chat/ChatInput.svelte:343— 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 web/src/lib/components/chat/Transcripts.svelte:101— 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 web/src/lib/components/ui/noteDrawer/NoteDrawer.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.
<textarea> without a programmatic label web/src/lib/components/ui/textarea/textarea.svelte:9— 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· <button> with no accessible text · ×2
<button> with no accessible text web/src/lib/components/chat/ChatMessages.svelte:175— 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).
<button> with no accessible text web/src/lib/components/contact/Contact.svelte:24— 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).
AC2 · Forms & labels· <label> that labels no control · ×2
<label> that labels no control web/src/lib/components/chat/ModelConfig.svelte:69— 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 web/src/lib/components/settings/LanguageSelector.svelte:21— 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.
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> web/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>.
AC4 · Keyboard semantics· Hover-only interaction on <canvas> · ×1
Hover-only interaction on <canvas> web/src/lib/components/ui/connections/Connections.svelte:122— This <canvas> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
Orphaned knowledge scripts/python_ui/streamlit.py:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file web/src/lib/services/ChatService.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/lib/store/chat-store.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/routes/chat/+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.
No test reaches this file web/src/lib/components/ui/connections/Connections.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 web/src/lib/store/pattern-store.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/lib/store/note-store.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/lib/store/session-store.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/lib/components/ui/connections/ParticleSystem.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/lib/components/terminal/Terminal.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 web/src/lib/services/transcriptService.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/routes/obsidian/+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.
No test reaches this file web/src/lib/components/ui/modal/PatternTilesModal.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 web/src/lib/components/patterns/PatternList.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 web/src/lib/components/ui/noteDrawer/NoteDrawer.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 web/src/lib/components/ui/slider/slider.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 web/src/lib/components/chat/Transcripts.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 web/src/lib/store/obsidian-store.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/lib/store/theme-store.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/lib/store/model-store.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/lib/components/ui/tooltip/Tooltip.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 web/src/lib/utils/file-utils.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/src/routes/notes/+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.
No test reaches this file web/src/routes/posts/+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 web/src/routes/api/youtube/transcript/+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.
No test reaches this file web/src/lib/components/ui/tagSearch/TagSearch.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.
Swallowed exception (caught, then discarded) internal/util/utils.go:53— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/util/utils.go:59— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/util/utils.go:64— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:483— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/server/strategies.go:48— `if err := json.Unmarshal(data, &s); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/plugins/db/fsdb/storage.go:118— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/plugins/ai/openai/models_cache.go:50— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/plugins/ai/openai/models_cache.go:54— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/plugins/ai/openai/models_cache.go:58— `if err := json.Unmarshal(data, &entry); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/plugins/ai/codex/errors.go:112— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/plugins/ai/codex/errors.go:155— `if err := json.Unmarshal(body, &payload); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/plugins/ai/codex/token.go:33— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/plugins/ai/anthropic/anthropic.go:682— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:103— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/core/plugin_registry.go:343— `if answerErr := setupQuestion.Ask(i18n.T(" ")); answerErr != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) internal/core/plugin_registry.go:363— `if err = o.SaveEnvFile(); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cmd/generate_changelog/internal/changelog/processing.go:476— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:441— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Hotspot: internal/core/chatter.go internal/core/chatter.go:73— internal/core/chatter.go changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in Chatter.Send at line 73. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/core/chatter.go`: 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: internal/core/plugin_registry.go internal/core/plugin_registry.go:534— internal/core/plugin_registry.go changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in PluginRegistry.GetChatter at line 534. 5 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/core/plugin_registry.go`: 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: internal/server/ollama.go internal/server/ollama.go:282— internal/server/ollama.go changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in APIConvert.ollamaChat at line 282. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/server/ollama.go`: 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: internal/cli/flags.go internal/cli/flags.go:130— internal/cli/flags.go changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in cli.Init at line 130. 4 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/cli/flags.go`: 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: internal/cli/help.go internal/cli/help.go:223— internal/cli/help.go changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in TranslatedHelpWriter.writeAllFlags at line 223. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/cli/help.go`: 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: internal/plugins/ai/openai/openai.go internal/plugins/ai/openai/openai.go:320— internal/plugins/ai/openai/openai.go changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Client.buildResponseParams at line 320. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/plugins/ai/openai/openai.go`: 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: internal/cli/chat.go internal/cli/chat.go:20— internal/cli/chat.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in cli.handleChatProcessing at line 20. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/cli/chat.go`: 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: internal/server/chat.go internal/server/chat.go:72— internal/server/chat.go changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in ChatHandler.HandleChat at line 72. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/server/chat.go`: 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: internal/cli/tools.go internal/cli/tools.go:14— internal/cli/tools.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in cli.handleToolProcessing at line 14. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/cli/tools.go`: 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: internal/domain/file_manager.go internal/domain/file_manager.go:31— internal/domain/file_manager.go changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in domain.ParseFileChanges at line 31. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/domain/file_manager.go`: 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: internal/plugins/ai/claudecode/claudecode.go internal/plugins/ai/claudecode/claudecode.go:108— internal/plugins/ai/claudecode/claudecode.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in claudecode.command at line 108. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/plugins/ai/claudecode/claudecode.go`: 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: internal/cli/cli.go internal/cli/cli.go:17— internal/cli/cli.go changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in cli.Cli at line 17. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/cli/cli.go`: 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: internal/util/httpclient.go internal/util/httpclient.go:165— internal/util/httpclient.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in util.HostAllowedForInsecureHTTP at line 165. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/util/httpclient.go`: 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: internal/plugins/ai/lmstudio/lmstudio.go internal/plugins/ai/lmstudio/lmstudio.go:92— internal/plugins/ai/lmstudio/lmstudio.go changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Client.SendStream at line 92. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/plugins/ai/lmstudio/lmstudio.go`: 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: internal/plugins/ai/codex/codex.go internal/plugins/ai/codex/codex.go:303— internal/plugins/ai/codex/codex.go changed 7 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is Client.SendStream at line 303), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: return Codex response failures immediately during streaming”; “fix: close endpoint validation gaps and expose vendor configuration failures”; “fix: tighten server bind authentication and localize endpoint validation errors”; “fix(codex): return the error of a failed Responses stream and report its usage”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/plugins/ai/codex/codex.go`: 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: internal/server/auth.go internal/server/auth.go:104— internal/server/auth.go changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is restapi.requireAPIKeyForBind at line 104), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: protect provider error details and bound response memory usage”; “fix: prune unlocked authentication clients while preserving active lockouts”; “fix: tighten server bind authentication and localize endpoint validation errors”; “fix(server): lock out a client after repeated wrong API keys”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/server/auth.go`: 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: internal/server/serve.go internal/server/serve.go:88— internal/server/serve.go changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is restapi.newServeEngine at line 88), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(server): set nosniff and no-store on every API response”; “fix(server): redact the API key in the recovery request dumps”; “fix: harden servers, templates, plugins, storage, and user interfaces”; “fix: secure storage paths and authenticate REST and Ollama servers”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/server/serve.go`: 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: internal/plugins/ai/gemini/gemini.go internal/plugins/ai/gemini/gemini.go:322— internal/plugins/ai/gemini/gemini.go changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is Client.performTTSGeneration at line 322), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: honor caller context cancellation across AI providers”; “fix(gemini): return an error when a non-streaming response is blocked”; “fix(gemini): return an error when a stream is blocked or stopped by a safety filter”; “fix(gemini): keep thought summaries out of the output and count thinking tokens”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/plugins/ai/gemini/gemini.go`: 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: internal/server/patterns.go internal/server/patterns.go:98— internal/server/patterns.go changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is PatternsHandler.ApplyPattern at line 98), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: protect provider error details and bound response memory usage”; “fix: harden servers, templates, plugins, storage, and user interfaces”; “fix(core): route input through user messages in BuildSession”; “fix: secure storage paths and authenticate REST and Ollama servers”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/server/patterns.go`: 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: internal/cli/setup_server.go internal/cli/setup_server.go:18— internal/cli/setup_server.go 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 10 (its worst body is cli.handleSetupAndServerCommands at line 18), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: harden servers, templates, plugins, storage, and user interfaces”; “fix: honor configured yt-dlp arguments for REST API transcripts”; “fix: secure storage paths and authenticate REST and Ollama servers”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/cli/setup_server.go`: 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: internal/cli/prompt_export.go internal/cli/prompt_export.go:53— internal/cli/prompt_export.go 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 8 (its worst body is cli.renderPromptExport at line 53), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: reject --print-prompt with an audio output file”; “fix: apply vendor raw mode in --print-prompt for a named model”; “refactor: simplify --print-prompt export and revert unrelated playlist change”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/cli/prompt_export.go`: 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: internal/plugins/ai/ollama/ollama.go internal/plugins/ai/ollama/ollama.go:309— internal/plugins/ai/ollama/ollama.go 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 10 (its worst body is Client.convertMessage at line 309), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: protect provider error details and bound response memory usage”; “fix: harden servers, templates, plugins, storage, and user interfaces”; “fix(ollama): honor caller context in SendStream and ListModels”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/plugins/ai/ollama/ollama.go`: 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: internal/plugins/db/fsdb/db.go internal/plugins/db/fsdb/db.go:50— internal/plugins/db/fsdb/db.go 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 11 (its worst body is Db.Configure at line 50), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(fsdb): make existing session and context folders and files private”; “fix: harden servers, templates, plugins, storage, and user interfaces”; “fix: persist refreshed Codex tokens and reactivate configured vendors”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/plugins/db/fsdb/db.go`: 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: internal/plugins/db/fsdb/storage.go internal/plugins/db/fsdb/storage.go:70— internal/plugins/db/fsdb/storage.go changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is StorageEntity.GetNames at line 70), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(fsdb): make existing session and context folders and files private”; “fix: harden servers, templates, plugins, storage, and user interfaces”; “fix: secure storage paths and authenticate REST and Ollama servers”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/plugins/db/fsdb/storage.go`: 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: internal/plugins/ai/vendors.go internal/plugins/ai/vendors.go:88— internal/plugins/ai/vendors.go 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 5 (its worst body is VendorsManager.readModels at line 88), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ai): simplify model catalog invalidation on vendor registration”; “fix: harden servers, templates, plugins, storage, and user interfaces”; “fix(ai): refresh model catalogs after vendor membership changes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/plugins/ai/vendors.go`: 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: REDACTED REDACTED:125— REDACTED 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 9 (its worst body is PatternsEntity.getFromDB at line 125), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: harden servers, templates, plugins, storage, and user interfaces”; “fix(core): route input through user messages in BuildSession”; “fix: secure storage paths and authenticate REST and Ollama servers”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: internal/plugins/ai/codex/errors.go internal/plugins/ai/codex/errors.go:119— internal/plugins/ai/codex/errors.go 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 codex.extractErrorMessage at line 119), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: correct SSE streaming behavior and restore native Azure routing”; “fix: preserve Codex provider details in authentication errors”; “fix: persist refreshed Codex tokens and reactivate configured vendors”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 02:26:43 +00:00' --until='2026-11-13 02:26:43 +00:00' --full-history --no-merges -- internal/plugins/ai/codex/errors.go`: 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×10
Async function without AbortSignal: RequestHandler web/src/routes/obsidian/+server.ts:15— `RequestHandler` holds an AbortSignal but calls `writeFile(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `writeFile(…, { signal })`.
Async function without AbortSignal: RequestHandler web/src/routes/notes/+server.ts:9— `RequestHandler` holds an AbortSignal but calls `writeFile(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `writeFile(…, { signal })`.
Async function without AbortSignal: RequestHandler web/src/routes/chat/+server.ts:7— `RequestHandler` holds an AbortSignal but calls `fetch(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `fetch(…, { signal })`.
Async function without AbortSignal: saveToFile web/src/lib/store/note-store.ts:47— `saveToFile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: loadPatterns web/src/lib/store/pattern-store.ts:39— `loadPatterns` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: loadSessions web/src/lib/store/session-store.ts:13— `loadSessions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: loadSessionMessages web/src/lib/store/session-store.ts:93— `loadSessionMessages` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchStrategies web/src/lib/store/strategy-store.ts:19— `fetchStrategies` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getTranscript web/src/lib/services/transcriptService.ts:15— `getTranscript` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: stream web/src/lib/api/base.ts:34— `stream` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
X2 · Cancellation propagation· Function without context.Context · ×10
Function without context.Context: refreshAccessToken internal/tools/spotify/spotify.go:87— `refreshAccessToken` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: doRequest internal/tools/spotify/spotify.go:135— `doRequest` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: Search internal/tools/serply/serply.go:58— `Search` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: request internal/tools/jina/jina.go:45— `request` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: Search internal/tools/firecrawl/firecrawl.go:66— `Search` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: fetch internal/plugins/template/fetch.go:98— `fetch` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: downloadLocale REDACTED:111— `downloadLocale` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: ResolveType internal/domain/attachment.go:52— `ResolveType` calls `http.Head(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: ContentBytes internal/domain/attachment.go:82— `ContentBytes` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: detectMimeTypeFromURL internal/domain/attachment.go:150— `detectMimeTypeFromURL` calls `http.Head(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×7
Animation without a prefers-reduced-motion guard web/src/lib/components/chat/ChatMessages.svelte:144— <span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard web/src/lib/components/chat/ChatMessages.svelte:145— <span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard web/src/lib/components/chat/ChatMessages.svelte:146— <span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard web/src/lib/components/patterns/TagFilterPanel.svelte:70— `.tag-panel` moves (`transition: left 0.3s 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 web/src/lib/components/chat/Chat.svelte:244— `.resize-handle::after` moves (`transition: background-color 0.2s, width 0.2s`) 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 web/src/lib/components/chat/Chat.svelte:281— `.vertical-resize-handle::after` moves (`transition: background-color 0.2s, height 0.2s`) 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 web/src/lib/components/chat/Transcripts.svelte:116— `.spinner-border` moves (`animation: spin 0.75s linear 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.
Outbound HTTP without resilience cmd/generate_changelog/internal/github/client.go:38— `http.DefaultClient` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience internal/domain/attachment.go:67— `http.Head(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience internal/domain/attachment.go:95— `http.Get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience internal/domain/attachment.go:151— `http.Head(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:119— `http.Get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience internal/server/ollama.go:199— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience internal/tools/jina/jina.go:56— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Duplicated block (7 lines × 2) internal/plugins/ai/anthropic/anthropic.go:515— internal/plugins/ai/anthropic/anthropic.go:515-523 | internal/plugins/ai/vertexai/vertexai.go:406-412 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `internal/plugins/ai/anthropic/anthropic.go:515` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) internal/plugins/ai/azureaigateway/backend_bedrock.go:125— internal/plugins/ai/azureaigateway/backend_bedrock.go:125-131 | internal/plugins/ai/vertexai/vertexai.go:166-173 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `internal/plugins/ai/azureaigateway/backend_bedrock.go:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) cmd/generate_changelog/internal/git/walker.go:88— cmd/generate_changelog/internal/git/walker.go:88-94 | cmd/generate_changelog/internal/git/walker.go:289-295 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/generate_changelog/internal/git/walker.go:88` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) cmd/generate_changelog/internal/changelog/generator.go:244— cmd/generate_changelog/internal/changelog/generator.go:244-250 | cmd/generate_changelog/internal/changelog/processing.go:198-204 — 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) internal/plugins/ai/copilot/copilot.go:231— internal/plugins/ai/copilot/copilot.go:231-237 | internal/plugins/ai/copilot/copilot.go:277-283 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `internal/plugins/ai/copilot/copilot.go:231` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
TodoComment web/src/routes/posts/+page.ts:4— // TODO: the same glob is in posts/[slug]/+page.ts, tags/+page.ts, and tags/[tag]/+page.ts. — 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 web/src/lib/api/contexts.ts:11— // TODO: add a context element to the UI. It could be the file upload — 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 internal/plugins/ai/geminicommon/geminicommon.go:47— // TODO: image parts are dropped. Gemini needs an inline data part built from the URL. — 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.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×3
Edited copy of a member (39 corresponding lines) internal/plugins/template/extension_manager.go:32— internal/plugins/template/extension_manager.go:32-70 | internal/plugins/template/extension_manager.go:73-120 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (39 corresponding lines) internal/plugins/ai/codex/auth_transport.go:112— internal/plugins/ai/codex/auth_transport.go:112-158 | REDACTED:201-239 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (39 corresponding lines) internal/plugins/ai/copilot/copilot.go:244— internal/plugins/ai/copilot/copilot.go:244-286 | internal/plugins/ai/copilot/copilot.go:289-327 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) internal/plugins/ai/copilot/copilot.go:216— internal/plugins/ai/copilot/copilot.go:216-227 | internal/plugins/ai/copilot/copilot.go:262-273 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (12 lines × 2) internal/plugins/ai/gemini/gemini.go:95— internal/plugins/ai/gemini/gemini.go:95-106 | internal/plugins/ai/gemini/gemini.go:126-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `internal/plugins/ai/gemini/gemini.go:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) internal/plugins/ai/copilot/copilot.go:245— internal/plugins/ai/copilot/copilot.go:245-256 | internal/plugins/ai/copilot/copilot.go:290-301 — 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) internal/plugins/ai/azureaigateway/backend_bedrock.go:63— internal/plugins/ai/azureaigateway/backend_bedrock.go:63-73 | internal/plugins/ai/azureaigateway/backend_vertex_ai.go:56-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `internal/plugins/ai/azureaigateway/backend_bedrock.go:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) internal/server/ollama.go:110— internal/server/ollama.go:110-120 | internal/server/ollama.go:124-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 (11 lines × 2) internal/tools/firecrawl/firecrawl.go:91— internal/tools/firecrawl/firecrawl.go:91-101 | internal/tools/serply/serply.go:73-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `internal/tools/firecrawl/firecrawl.go:91` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (10 lines × 2) internal/plugins/ai/azure/azure.go:46— internal/plugins/ai/azure/azure.go:46-55 | internal/plugins/ai/azure_entra/azure_entra.go:46-55 — 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 (10 lines × 2) internal/tools/spotify/spotify.go:307— internal/tools/spotify/spotify.go:307-316 | internal/tools/spotify/spotify.go:426-435 — 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) cmd/generate_changelog/internal/git/walker.go:243— cmd/generate_changelog/internal/git/walker.go:243-252 | cmd/generate_changelog/internal/git/walker.go:255-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/generate_changelog/internal/git/walker.go:243` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) internal/plugins/template/extension_manager.go:80— internal/plugins/template/extension_manager.go:80-88 | internal/plugins/template/extension_registry.go:99-107 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) internal/server/ollama.go:501— internal/server/ollama.go:501-509 | internal/server/ollama.go:517-525 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `internal/server/ollama.go:528` calls `New`, `T` and `internal/server/ollama.go:510` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) internal/plugins/ai/codex/auth_transport.go:133— internal/plugins/ai/codex/auth_transport.go:133-141 | REDACTED:218-226 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `internal/plugins/ai/codex/auth_transport.go:133` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Focus outline removed inline web/src/lib/components/terminal/Terminal.svelte:119— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline web/src/lib/components/ui/modal/PatternTilesModal.svelte:190— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
MethodTooLong: APIConvert.ollamaChat internal/server/ollama.go:282— MethodTooLong — ollamaChat runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: Chatter.Send internal/core/chatter.go:73— MethodTooLong — Send runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (55 corresponding lines) · ×2
Edited copy of a member (55 corresponding lines) internal/plugins/ai/anthropic/anthropic.go:471— internal/plugins/ai/anthropic/anthropic.go:471-540 | internal/plugins/ai/vertexai/vertexai.go:374-428 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (55 corresponding lines) internal/plugins/ai/gemini/gemini.go:123— internal/plugins/ai/gemini/gemini.go:123-177 | internal/plugins/ai/vertexai/vertexai.go:317-372 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) internal/plugins/ai/gemini/gemini.go:179— internal/plugins/ai/gemini/gemini.go:179-196 | internal/plugins/ai/vertexai/vertexai.go:297-315 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) REDACTED:260— REDACTED:260-277 | internal/plugins/db/fsdb/storage.go:173-190 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) cmd/generate_changelog/internal/github/client.go:104— cmd/generate_changelog/internal/github/client.go:104-118 | cmd/generate_changelog/internal/github/client.go:133-152 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) internal/plugins/ai/copilot/copilot.go:156— internal/plugins/ai/copilot/copilot.go:156-170 | internal/plugins/ai/copilot/copilot.go:173-188 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) internal/plugins/plugin.go:71— internal/plugins/plugin.go:71-79 | internal/plugins/plugin.go:95-104 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) internal/server/patterns.go:65— internal/server/patterns.go:65-77 | internal/server/storage.go:69-77 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) internal/plugins/ai/azure/azure.go:16— internal/plugins/ai/azure/azure.go:16-25 | internal/plugins/ai/azure_entra/azure_entra.go:18-30 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) internal/plugins/strategy/strategy.go:110— internal/plugins/strategy/strategy.go:110-120 | internal/tools/patterns_loader.go:75-84 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) internal/plugins/ai/anthropic/anthropic.go:526— internal/plugins/ai/anthropic/anthropic.go:526-540 | internal/plugins/ai/vertexai/vertexai.go:414-428 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `internal/plugins/ai/anthropic/anthropic.go:526` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) REDACTED:325— REDACTED:325-340 | REDACTED:408-422 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:325` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (13 lines × 2 locations) web/src/lib/components/chat/Chat.svelte:42— web/src/lib/components/chat/Chat.svelte:42 · web/src/lib/components/chat/Chat.svelte:77 — 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 (13 lines × 2 locations) web/src/routes/tags/+page.ts:7— web/src/routes/tags/+page.ts:7 · web/src/routes/tags/[tag]/+page.ts:7 — 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.
AC1 · Text alternatives· <canvas> without a text alternative · ×1
<canvas> without a text alternative web/src/lib/components/ui/connections/Connections.svelte:122— 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.
AC3 · Page structure· Heading level jumps from h3 to h6 · ×1
Heading level jumps from h3 to h6 web/src/lib/components/ui/cards/card.svelte:35— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×1
Heading level jumps from h1 to h3 web/src/lib/components/ui/help/HelpModal.svelte:26— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure· Heading level jumps from h1 to h4 · ×1
Heading level jumps from h1 to h4 web/src/routes/posts/+page.svelte:63— 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 · ×1
Modal dialog does not manage focus web/src/lib/components/ui/modal/Modal.svelte:14— 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.
Stateful handler dependency: YouTube REDACTED:84— `YouTube` is shared by every request (`initService` is called per request from the Gin handler `YouTubeHandler.Transcript`, on the one `YouTube` value that handler's shared receiver holds) but writes its fields outside any lock (normalizeRegex, service; e.g. `normalizeRegex` in `initService` at line 101). Unsynchronised concurrent writes are a data race in Go: an update is lost or a value tears, and a concurrent map write aborts the process.
Chatter.Send (cyclomatic 51) internal/core/chatter.go:73— Chatter.Send has cyclomatic complexity 51 (threshold 15). Of this number, 50 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TranslatedHelpWriter.writeAllFlags (cyclomatic 43) internal/cli/help.go:223— TranslatedHelpWriter.writeAllFlags has cyclomatic complexity 43 (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.
APIConvert.ollamaChat (cyclomatic 39) internal/server/ollama.go:282— APIConvert.ollamaChat has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Generator.collectData (cyclomatic 38) cmd/generate_changelog/internal/changelog/generator.go:75— Generator.collectData has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cli.handleChatProcessing (cyclomatic 37) internal/cli/chat.go:20— cli.handleChatProcessing has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cli.handleToolProcessing (cyclomatic 35) internal/cli/tools.go:14— cli.handleToolProcessing has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Generator.CreateNewChangelogEntry (cyclomatic 34) cmd/generate_changelog/internal/changelog/processing.go:119— Generator.CreateNewChangelogEntry has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cli.Cli (cyclomatic 34) internal/cli/cli.go:17— cli.Cli has cyclomatic complexity 34 (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.
PluginRegistry.GetChatter (cyclomatic 33) internal/core/plugin_registry.go:534— PluginRegistry.GetChatter has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BedrockClient.Setup (cyclomatic 33) internal/plugins/ai/bedrock/bedrock.go:212— BedrockClient.Setup has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Chatter.BuildSession (cyclomatic 28) internal/core/chatter.go:266— Chatter.BuildSession has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cli.Init (cyclomatic 27) internal/cli/flags.go:130— cli.Init has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
restapi.parseOllamaNumCtx (cyclomatic 27) internal/server/ollama.go:89— restapi.parseOllamaNumCtx has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
template.resolveToken (cyclomatic 26) internal/plugins/template/template.go:174— template.resolveToken has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
YouTube.GrabVisual (cyclomatic 23) REDACTED:861— YouTube.GrabVisual has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Generator.fetchPRs (cyclomatic 22) cmd/generate_changelog/internal/changelog/generator.go:189— Generator.fetchPRs 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.
cli.validateImageParameters (cyclomatic 21) internal/cli/flags.go:347— cli.validateImageParameters 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.
claudecode.command (cyclomatic 21) internal/plugins/ai/claudecode/claudecode.go:108— claudecode.command 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.
cli.processYoutubeVideo (cyclomatic 20) internal/cli/cli.go:123— cli.processYoutubeVideo 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.
gemini.ListGeminiVoices (cyclomatic 20) REDACTED:95— gemini.ListGeminiVoices 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.
Client.SendStream (cyclomatic 20) internal/plugins/ai/lmstudio/lmstudio.go:92— Client.SendStream 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.
Client.buildResponseParams (cyclomatic 20) internal/plugins/ai/openai/openai.go:320— Client.buildResponseParams 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.
FilePlugin.Apply (cyclomatic 20) internal/plugins/template/file.go:85— FilePlugin.Apply 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.
ChatHandler.HandleChat (cyclomatic 20) internal/server/chat.go:72— ChatHandler.HandleChat has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
YouTube.readAndFormatVTTWithTimestamps (cyclomatic 20) REDACTED:330— YouTube.readAndFormatVTTWithTimestamps 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.
cli.handleListingCommands (cyclomatic 19) internal/cli/listing.go:19— cli.handleListingCommands 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.
Client.toMessages (cyclomatic 19) internal/plugins/ai/anthropic/anthropic.go:471— Client.toMessages 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.
openai.FetchModelsDirectly (cyclomatic 19) internal/plugins/ai/openai/direct_models.go:33— openai.FetchModelsDirectly 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.
Generator.generateRawVersionContent (cyclomatic 17) cmd/generate_changelog/internal/changelog/generator.go:408— Generator.generateRawVersionContent has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
main.main (cyclomatic 17) REDACTED:43— main.main has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
domain.ParseFileChanges (cyclomatic 17) internal/domain/file_manager.go:31— domain.ParseFileChanges has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Client.fetchModelsFromControlPlane (cyclomatic 17) internal/plugins/ai/digitalocean/digitalocean.go:69— Client.fetchModelsFromControlPlane 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.
Generator.formatVersion (cyclomatic 16) cmd/generate_changelog/internal/changelog/generator.go:312— Generator.formatVersion 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.
Client.FetchAllMergedPRsGraphQL (cyclomatic 16) cmd/generate_changelog/internal/github/client.go:318— Client.FetchAllMergedPRsGraphQL 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.
main.run (cyclomatic 16) cmd/generate_changelog/main.go:51— main.run 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.
Client.ensureAccessTokenLocked (cyclomatic 16) internal/plugins/ai/codex/auth_transport.go:63— Client.ensureAccessTokenLocked 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.
Client.toMessages (cyclomatic 16) internal/plugins/ai/vertexai/vertexai.go:374— Client.toMessages 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.
util.HostAllowedForInsecureHTTP (cyclomatic 16) internal/util/httpclient.go:165— util.HostAllowedForInsecureHTTP has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Deprecated module: github.com/go-shiori/go-readability — `github.com/go-shiori/go-readability` is required at v0.0.0-20251205110129-5db1dc9836f0 in REDACTED, and its author has DEPRECATED the module: "use codeberg.org/readeck/go-readability/v2 instead." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
D12 · Dependency Hygiene· Dependency pinned to a stale untagged commit · ×1
Dependency pinned to a stale untagged commit: github.com/kballard/go-shellquote — Direct dependency `github.com/kballard/go-shellquote` is required at `v0.0.0-20180428030007-95032a82bc51` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2018-04-28, 8.5 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/kballard/go-shellquote` and has not moved this requirement in 8.5 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/kballard/go-shellquote` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Generator.collectData (cognitive 162) cmd/generate_changelog/internal/changelog/generator.go:75— Generator.collectData has cognitive complexity 162 (threshold 15). Drivers by points: if/else 27 (120 pts), loops 7 (37 pts), boolean chains 5 (nesting depth added 123). 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.
Chatter.Send (cognitive 87) internal/core/chatter.go:73— Chatter.Send has cognitive complexity 87 (threshold 15). Drivers by points: if/else 34 (68 pts), match/switch 3 (9 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 42). Of this number, 85 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.
cli.handleToolProcessing (cognitive 78) internal/cli/tools.go:14— cli.handleToolProcessing has cognitive complexity 78 (threshold 15). Drivers by points: if/else 32 (71 pts), loops 1 (4 pts), boolean chains 3 (nesting depth added 42). 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.
Generator.CreateNewChangelogEntry (cognitive 73) cmd/generate_changelog/internal/changelog/processing.go:119— Generator.CreateNewChangelogEntry has cognitive complexity 73 (threshold 15). Drivers by points: if/else 28 (58 pts), loops 6 (15 pts) (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PluginRegistry.GetChatter (cognitive 70) internal/core/plugin_registry.go:534— PluginRegistry.GetChatter has cognitive complexity 70 (threshold 15). Drivers by points: if/else 30 (66 pts), boolean chains 4 (nesting depth added 36). 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.
APIConvert.ollamaChat (cognitive 68) internal/server/ollama.go:282— APIConvert.ollamaChat has cognitive complexity 68 (threshold 15). Drivers by points: if/else 33 (55 pts), loops 3 (8 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cli.Init (cognitive 59) internal/cli/flags.go:130— cli.Init has cognitive complexity 59 (threshold 15). Drivers by points: if/else 20 (50 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 32). 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.
cli.handleChatProcessing (cognitive 50) internal/cli/chat.go:20— cli.handleChatProcessing has cognitive complexity 50 (threshold 15). Drivers by points: if/else 28 (40 pts), boolean chains 10 (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.
ChatHandler.HandleChat (cognitive 48) internal/server/chat.go:72— ChatHandler.HandleChat has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (32 pts), match/switch 3 (11 pts), loops 3 (5 pts) (nesting depth added 31). Of this number, 42 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BedrockClient.Setup (cognitive 42) internal/plugins/ai/bedrock/bedrock.go:212— BedrockClient.Setup has cognitive complexity 42 (threshold 15). Drivers by points: if/else 24 (35 pts), boolean chains 4, loops 2, match/switch 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.
Chatter.BuildSession (cognitive 41) internal/core/chatter.go:266— Chatter.BuildSession has cognitive complexity 41 (threshold 15). Drivers by points: if/else 24 (36 pts), boolean chains 5 (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.
gemini.ListGeminiVoices (cognitive 41) REDACTED:95— gemini.ListGeminiVoices has cognitive complexity 41 (threshold 15). Drivers by points: if/else 9 (29 pts), loops 5 (9 pts), match/switch 1 (3 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cli.Cli (cognitive 40) internal/cli/cli.go:17— cli.Cli has cognitive complexity 40 (threshold 15). Drivers by points: if/else 26 (32 pts), boolean chains 8 (nesting depth added 6). 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.
Client.SendStream (cognitive 36) internal/plugins/ai/lmstudio/lmstudio.go:92— Client.SendStream has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (34 pts), boolean chains 1, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
restapi.parseOllamaNumCtx (cognitive 35) internal/server/ollama.go:89— restapi.parseOllamaNumCtx has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (32 pts), boolean chains 2, match/switch 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.
claudecode.command (cognitive 34) internal/plugins/ai/claudecode/claudecode.go:108— claudecode.command has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 4 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
template.resolveToken (cognitive 34) internal/plugins/template/template.go:174— template.resolveToken has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 4, match/switch 2 (4 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Client.FetchAllMergedPRsGraphQL (cognitive 33) cmd/generate_changelog/internal/github/client.go:318— Client.FetchAllMergedPRsGraphQL has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 3 (6 pts), match/switch 1 (4 pts), boolean chains 2 (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.
YouTube.readAndFormatVTTWithTimestamps (cognitive 33) REDACTED:330— YouTube.readAndFormatVTTWithTimestamps has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (29 pts), boolean chains 3, loops 1 (nesting depth added 18). 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.
Client.buildResponseParams (cognitive 32) internal/plugins/ai/openai/openai.go:320— Client.buildResponseParams has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (30 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Generator.formatVersion (cognitive 31) cmd/generate_changelog/internal/changelog/generator.go:312— Generator.formatVersion has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 2 (nesting depth added 17). 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.
cli.processYoutubeVideo (cognitive 31) internal/cli/cli.go:123— cli.processYoutubeVideo has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (28 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.
Client.Send (cognitive 31) internal/plugins/ai/anthropic/anthropic.go:409— Client.Send has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 18). 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.
Client.toMessages (cognitive 31) internal/plugins/ai/anthropic/anthropic.go:471— Client.toMessages has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 5, 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.
Generator.fetchPRs (cognitive 29) cmd/generate_changelog/internal/changelog/generator.go:189— Generator.fetchPRs has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Client.extractText (cognitive 29) internal/plugins/ai/openai/openai.go:443— Client.extractText has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (20 pts), loops 3 (9 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FilePlugin.Apply (cognitive 29) internal/plugins/template/file.go:85— FilePlugin.Apply has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (28 pts), match/switch 1 (nesting depth added 14). 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.
YouTube.GrabVisual (cognitive 28) REDACTED:861— YouTube.GrabVisual has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19 (24 pts), loops 3, boolean chains 1 (nesting depth added 5). Of this number, 23 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
util.HostAllowedForInsecureHTTP (cognitive 28) internal/util/httpclient.go:165— util.HostAllowedForInsecureHTTP has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 4, loops 1 (nesting depth added 13). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Generator.syncGitHistory (cognitive 27) cmd/generate_changelog/internal/changelog/generator.go:682— Generator.syncGitHistory has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Client.convertGitHubPR (cognitive 27) cmd/generate_changelog/internal/github/client.go:163— Client.convertGitHubPR has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Generator.generateRawVersionContent (cognitive 26) cmd/generate_changelog/internal/changelog/generator.go:408— Generator.generateRawVersionContent has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 5 (8 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cli.handleListingCommands (cognitive 26) internal/cli/listing.go:19— cli.handleListingCommands has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (25 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openai.FetchModelsDirectly (cognitive 25) internal/plugins/ai/openai/direct_models.go:33— openai.FetchModelsDirectly has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (25 pts) (nesting depth added 6). 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.
Client.extractAndSaveImages (cognitive 25) internal/plugins/ai/openai/openai_image.go:92— Client.extractAndSaveImages has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (23 pts), boolean chains 1, 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.
cli.validateImageParameters (cognitive 24) internal/cli/flags.go:347— cli.validateImageParameters has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
domain.ParseFileChanges (cognitive 24) internal/domain/file_manager.go:31— domain.ParseFileChanges has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 2, loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Client.toMessages (cognitive 24) internal/plugins/ai/vertexai/vertexai.go:374— Client.toMessages has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.main (cognitive 23) cmd/code2context/main.go:11— main.main has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Walker.GetRepoInfo (cognitive 23) cmd/generate_changelog/internal/git/walker.go:235— Walker.GetRepoInfo has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (19 pts), boolean chains 2, loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Flags.BuildChatRequest (cognitive 23) internal/cli/flags.go:447— Flags.BuildChatRequest has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Client.SendStream (cognitive 23) internal/plugins/ai/codex/codex.go:303— Client.SendStream has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cache.GetVersions (cognitive 22) REDACTED:183— Cache.GetVersions has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 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.
Walker.PushToRemote (cognitive 22) cmd/generate_changelog/internal/git/walker.go:501— Walker.PushToRemote has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 13). 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.
main.main (cognitive 21) REDACTED:43— main.main has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (20 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PluginRegistry.runInteractiveSetup (cognitive 21) internal/core/plugin_registry.go:318— PluginRegistry.runInteractiveSetup has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 1 (nesting depth added 10). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
geminicommon.ExtractCitations (cognitive 21) internal/plugins/ai/geminicommon/geminicommon.go:134— geminicommon.ExtractCitations has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openai.splitAudioFile (cognitive 21) internal/plugins/ai/openai/openai_audio.go:140— openai.splitAudioFile has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (5 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.
Client.TranscribeFile (cognitive 21) internal/plugins/ai/openai/openai_audio.go:50— Client.TranscribeFile has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 pts), loops 3 (nesting depth added 6). Of this number, 17 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StorageEntity.GetNames (cognitive 21) internal/plugins/db/fsdb/storage.go:70— StorageEntity.GetNames has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.ScanDirectory (cognitive 20) cmd/code2context/code.go:35— main.ScanDirectory has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (19 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to one function literal inside it that branches (line 46). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Client.performTTSGeneration (cognitive 20) internal/plugins/ai/gemini/gemini.go:322— Client.performTTSGeneration has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3 (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.
PatternsLoader.createUniquePatternsFile (cognitive 20) internal/tools/patterns_loader.go:297— PatternsLoader.createUniquePatternsFile has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 3 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Generator.getDirectCommitsSinceLastRelease (cognitive 19) cmd/generate_changelog/internal/changelog/processing.go:285— Generator.getDirectCommitsSinceLastRelease has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cli.runWorkflow (cognitive 19) internal/cli/workflow.go:104— cli.runWorkflow has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3, 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.
domain.fixInvalidEscapes (cognitive 19) internal/domain/file_manager.go:102— domain.fixInvalidEscapes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3, 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.
Client.parseSSEStream (cognitive 19) internal/plugins/ai/copilot/copilot.go:330— Client.parseSSEStream has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (17 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.
YouTube.Grab (cognitive 19) REDACTED:571— YouTube.Grab has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (19 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.
Client.FetchAllMergedPRs (cognitive 18) cmd/generate_changelog/internal/github/client.go:244— Client.FetchAllMergedPRs has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (7 pts) (nesting depth added 9). Of this number, 15 points are the body's own statements and 3 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.
PluginRegistry.runFirstTimeSetup (cognitive 18) internal/core/plugin_registry.go:214— PluginRegistry.runFirstTimeSetup has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (18 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
i18n.Init (cognitive 18) REDACTED:40— i18n.Init has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, 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.
Client.ensureAccessTokenLocked (cognitive 18) internal/plugins/ai/codex/auth_transport.go:63— Client.ensureAccessTokenLocked has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Client.fetchModelsFromControlPlane (cognitive 18) internal/plugins/ai/digitalocean/digitalocean.go:69— Client.fetchModelsFromControlPlane has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PatternsLoader.tryPathMigration (cognitive 18) internal/tools/patterns_loader.go:239— PatternsLoader.tryPathMigration has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (17 pts), boolean chains 1 (nesting depth added 11). 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.
ChatService.createMessageStream (cognitive 18) web/src/lib/services/ChatService.ts:107— ChatService.createMessageStream has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), error handling 3 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.run (cognitive 17) cmd/generate_changelog/main.go:51— main.run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Session.String (cognitive 17) internal/plugins/db/fsdb/sessions.go:164— Session.String has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (4 pts), match/switch 1 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Generator.extractChanges (cognitive 16) cmd/generate_changelog/internal/changelog/generator.go:531— Generator.extractChanges has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
changelog.fixMarkdown (cognitive 16) cmd/generate_changelog/internal/changelog/generator.go:474— changelog.fixMarkdown has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Client.buildChatCompletionParams (cognitive 16) internal/plugins/ai/openai/chat_completions.go:71— Client.buildChatCompletionParams has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 1, 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.
PatternsLoader.PersistPatterns (cognitive 16) internal/tools/patterns_loader.go:125— PatternsLoader.PersistPatterns has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyFields: Flags internal/cli/flags.go:28— TooManyFields — 94 stored fields beside 5 methods. The bar is 30 stored fields; this is 64 over it, 3.13× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
FileTooLong: REDACTED REDACTED— FileTooLong — 601 significant lines (blank, comment-only and punctuation-only lines excluded), about 70% of them inside a single declaration: YouTube (27 blocks, 84-990). The bar is 500 significant lines; this is 101 over it, 1.20× 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.
ClassTooLong: YouTube REDACTED:84— ClassTooLong — 421 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods, 27 blocks, lines 84-990. The bar is 400 significant lines; this is 21 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) internal/plugins/ai/anthropic/anthropic.go:306— internal/plugins/ai/anthropic/anthropic.go:306-359 | internal/plugins/ai/vertexai/vertexai.go:187-241 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) internal/plugins/ai/lmstudio/lmstudio.go:92— internal/plugins/ai/lmstudio/lmstudio.go:92-200 | internal/plugins/ai/lmstudio/lmstudio.go:202-262 | internal/plugins/ai/lmstudio/lmstudio.go:264-318 | internal/plugins/ai/lmstudio/lmstudio.go:320-373 — 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.
D4 · Code Duplication· Edited copy of a member (57 corresponding lines) · ×1
Edited copy of a member (57 corresponding lines) internal/tools/spotify/spotify.go:329— internal/tools/spotify/spotify.go:329-386 | internal/tools/spotify/spotify.go:389-445 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) internal/tools/spotify/spotify.go:222— internal/tools/spotify/spotify.go:222-268 | internal/tools/spotify/spotify.go:271-326 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) internal/plugins/ai/azure/azure.go:35— internal/plugins/ai/azure/azure.go:35-65 | internal/plugins/ai/azure_entra/azure_entra.go:40-70 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) REDACTED:323— REDACTED:323-352 | REDACTED:406-432 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) internal/domain/attachment.go:52— internal/domain/attachment.go:52-80 | internal/domain/attachment.go:82-106 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) internal/plugins/ai/exolab/exolab.go:34— internal/plugins/ai/exolab/exolab.go:34-47 | internal/plugins/ai/openai/openai.go:144-161 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) cmd/generate_changelog/internal/git/walker.go:408— cmd/generate_changelog/internal/git/walker.go:408-425 | cmd/generate_changelog/internal/git/walker.go:429-446 | cmd/generate_changelog/internal/git/walker.go:450-467 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) internal/tools/spotify/spotify.go:169— internal/tools/spotify/spotify.go:169-184 | REDACTED:108-123 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 15+ corresponding lines) · ×1
Edited copies of one member (6 members, 15+ corresponding lines) internal/tools/custom_patterns/custom_patterns.go:13— internal/tools/custom_patterns/custom_patterns.go:13-28 | internal/tools/firecrawl/firecrawl.go:29-44 | internal/tools/jina/jina.go:19-34 | internal/tools/lang/language.go:9-25 | internal/tools/serply/serply.go:27-42 | REDACTED:68-82 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) internal/util/groups_items.go:138— internal/util/groups_items.go:138-151 | internal/util/groups_items.go:153-165 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) internal/server/patterns.go:24— internal/server/patterns.go:24-34 | internal/server/storage.go:44-54 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) internal/tools/firecrawl/firecrawl.go:18— internal/tools/firecrawl/firecrawl.go:18-27 | internal/tools/serply/serply.go:18-25 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (30–31 lines × 2) internal/plugins/ai/anthropic/anthropic.go:323— internal/plugins/ai/anthropic/anthropic.go:323-352 | internal/plugins/ai/vertexai/vertexai.go:208-238 — 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 (26 lines × 4) internal/plugins/ai/lmstudio/lmstudio.go:106— internal/plugins/ai/lmstudio/lmstudio.go:106-131 | internal/plugins/ai/lmstudio/lmstudio.go:210-235 | internal/plugins/ai/lmstudio/lmstudio.go:272-297 | internal/plugins/ai/lmstudio/lmstudio.go:328-353 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (26 lines × 2) cmd/generate_changelog/internal/git/walker.go:186— cmd/generate_changelog/internal/git/walker.go:186-211 | cmd/generate_changelog/internal/git/walker.go:322-347 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/generate_changelog/internal/git/walker.go:186` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22–24 lines × 2) internal/plugins/ai/gemini/gemini.go:153— internal/plugins/ai/gemini/gemini.go:153-176 | internal/plugins/ai/vertexai/vertexai.go:348-369 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `internal/plugins/ai/gemini/gemini.go:153` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 2) internal/plugins/template/extension_manager.go:48— internal/plugins/template/extension_manager.go:48-65 | internal/plugins/template/extension_manager.go:100-117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: `internal/plugins/template/extension_manager.go:100` is reached only past a guard at line 94 that tests `ext.Timeout` and leaves the function early, and `internal/plugins/template/extension_manager.go:48` reads `ext.Timeout` with no such check. What separates these copies is not which lines they run but which PRECONDITION they enforce, so one of them is operating on state the other one refuses. Decide which is intended BEFORE unifying them — extract the shared part and whichever copy is missing the check keeps running unchecked, and if the guard is the correct behaviour then that hole is already live.
Duplicated block (13 lines × 2) cmd/generate_changelog/internal/github/client.go:66— cmd/generate_changelog/internal/github/client.go:66-78 | cmd/generate_changelog/internal/github/client.go:277-289 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/generate_changelog/internal/github/client.go:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (12–13 lines × 2) internal/tools/spotify/spotify.go:253— internal/tools/spotify/spotify.go:253-265 | internal/tools/spotify/spotify.go:370-381 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `internal/tools/spotify/spotify.go:253` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 3) cmd/generate_changelog/internal/git/walker.go:98— cmd/generate_changelog/internal/git/walker.go:98-107 | cmd/generate_changelog/internal/git/walker.go:163-172 | cmd/generate_changelog/internal/git/walker.go:299-308 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/generate_changelog/internal/git/walker.go:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cmd/generate_changelog/internal/git/walker.go:311` calls `Close` and `cmd/generate_changelog/internal/git/walker.go:176` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) internal/plugins/plugin.go:73— internal/plugins/plugin.go:73-78 | internal/plugins/plugin.go:98-103 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) scripts/python_ui/streamlit.py:1039— scripts/python_ui/streamlit.py:1039-1075 | scripts/python_ui/streamlit.py:1079-1122 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9–10 lines × 2) scripts/python_ui/streamlit.py:969— scripts/python_ui/streamlit.py:969-977 | scripts/python_ui/streamlit.py:980-989 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `scripts/python_ui/streamlit.py:978` calls `error` and `scripts/python_ui/streamlit.py:990` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — web/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
Duplicated block (52 lines × 2 locations) web/src/lib/components/patterns/PatternList.svelte:5— web/src/lib/components/patterns/PatternList.svelte:5 · web/src/lib/components/ui/modal/PatternTilesModal.svelte:4 — 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 (26 lines × 2 locations) web/src/lib/components/ui/tagSearch/TagSearch.svelte:12— web/src/lib/components/ui/tagSearch/TagSearch.svelte:12 · web/src/routes/posts/+page.svelte:15 — 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 (10 lines × 2 locations) web/src/lib/components/ui/connections/ParticleSystem.ts:19— web/src/lib/components/ui/connections/ParticleSystem.ts:19 · web/src/lib/components/ui/connections/ParticleSystem.ts:48 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (10 matched lines × 2 locations) · ×1
Duplicated block with local edits (10 matched lines × 2 locations) web/src/lib/store/pattern-store.ts:56— web/src/lib/store/pattern-store.ts:56 · web/src/lib/store/pattern-store.ts:70 — the two spans are one implementation copied and then locally edited — 72 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 (9 lines × 2 locations) web/vite.config.ts:50— web/vite.config.ts:50 · web/vite.config.ts: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. Check what actually differs between the copies before collapsing them: every one of them is an argument to a `defineConfig(…)` call, so where these calls are a MATRIX of cases — one per input, differing precisely in the case each one pins — the repetition is the enumeration and extracting the shared part would delete cases rather than de-duplicate anything.
Duplicated block (8 lines × 2 locations) web/src/routes/chat/+server.ts:130— web/src/routes/chat/+server.ts:130 · web/src/routes/obsidian/+server.ts:61 — 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 (6 lines × 2 locations) web/src/lib/api/base.ts:62— web/src/lib/api/base.ts:62 · web/src/lib/api/base.ts:79 — 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.
R2 · Cyclomatic Complexity· Complex function POST (cyclomatic 13, cognitive 15) · ×1
Complex function POST (cyclomatic 13, cognitive 15) web/src/routes/obsidian/+server.ts:15— POST has cyclomatic complexity 13 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.
Unused dependency '@floating-ui/dom' — Declared in web/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 'highlight.js' — Declared in web/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 'nanoid' — Declared in web/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 'patch-package' — Declared in web/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 'rehype' — Declared in web/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 'svelte-inview' — Declared in web/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 'svelte-reveal' — Declared in web/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 'svelte-youtube-embed' — Declared in web/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 'vfile-message' — Declared in web/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.
Swallowed exception (empty catch) web/src/lib/components/chat/DropdownGroup.svelte:36— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Duplicated predicate internal/plugins/ai/anthropic/anthropic.go:523— `!lastRoleWasUser && len(anthropicMessages) > 0` appears character-identically in 2 files — internal/plugins/ai/anthropic/anthropic.go, internal/plugins/ai/vertexai/vertexai.go. 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 internal/plugins/ai/anthropic/anthropic.go:438— `block.Type == "text" && block.Text != ""` appears character-identically in 3 files — internal/plugins/ai/anthropic/anthropic.go, internal/plugins/ai/azureaigateway/backend_bedrock.go, internal/plugins/ai/vertexai/vertexai.go. 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 internal/cli/chat.go:46— `currentFlags.Output != "" && IsAudioFormat(currentFlags.Output)` appears character-identically in 2 files — internal/cli/chat.go, internal/cli/prompt_export.go. 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 internal/plugins/ai/anthropic/anthropic.go:333— `event.Message.Usage.InputTokens != 0 || event.Message.Usage.OutputTokens != 0` appears character-identically in 2 files — internal/plugins/ai/anthropic/anthropic.go, internal/plugins/ai/vertexai/vertexai.go. 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 internal/plugins/ai/anthropic/anthropic.go:342— `event.Usage.InputTokens != 0 || event.Usage.OutputTokens != 0` appears character-identically in 2 files — internal/plugins/ai/anthropic/anthropic.go, internal/plugins/ai/vertexai/vertexai.go. 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 internal/plugins/ai/anthropic/anthropic.go:505— `isFirstUserMessage && systemContent != ""` appears character-identically in 2 files — internal/plugins/ai/anthropic/anthropic.go, internal/plugins/ai/vertexai/vertexai.go. 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 internal/plugins/ai/anthropic/anthropic.go:535— `len(anthropicMessages) == 0 && systemContent != ""` appears character-identically in 2 files — internal/plugins/ai/anthropic/anthropic.go, internal/plugins/ai/vertexai/vertexai.go. 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 cmd/generate_changelog/internal/changelog/generator.go:463— `message != "" && !g.isDuplicateMessage(message, directCommits)` appears character-identically in 2 files — cmd/generate_changelog/internal/changelog/generator.go, cmd/generate_changelog/internal/changelog/processing.go. 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 internal/plugins/ai/openai/chat_completions.go:78— `strings.Contains(opts.Model, "deepseek") && len(inputMsgs) == 1 && msg.Role == chat.ChatMessageRoleSystem` appears character-identically in 2 files — internal/plugins/ai/openai/chat_completions.go, internal/plugins/ai/openai/openai.go. 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 REDACTED: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 web/src/lib/store/pattern-store.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file internal/domain/attachment.go: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 web/src/lib/store/session-store.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file web/src/lib/components/ui/connections/ParticleSystem.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file web/src/lib/store/note-store.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 32 significant file(s) lose their only recent owner: cmd/generate_changelog/internal/changelog/generator.go, internal/server/ollama.go, internal/tools/spotify/spotify.go, cmd/generate_changelog/internal/changelog/processing.go, cmd/generate_changelog/internal/git/walker.go, REDACTED, cmd/generate_changelog/internal/github/client.go, internal/tools/patterns_loader.go (+24 more). Pair on, review, or document these before any departure.
No ADRs found REDACTED:10— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `REDACTED` makes this repository a deployable product (line 10).
redundant comment web/src/lib/utils/sanitize-html.ts:20— "escapeHtml gives text with HTML escapes." repeats the code it sits on: 4 of its 5 words (escape, html, text, escapes) are already in `function escapeHtml(text: string): string`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 3 project(s) overshoot their size bounds, lowering Project Cohesion to 3.3/10. The most over is `(repository root)` (22560 LoC, 206 module-visible types across 61 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.
Scattered collaborators — 63 % of calls cross a namespace and only 49 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
Pass-through layer web/src/lib/services/toast-service.ts:5— toastService: all 3 public methods forward their arguments unchanged to toastStoreInstance and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call toastStoreInstance directly, or give the layer a job.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 6 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: internal/domain/attachment.go, REDACTED, web/src/lib/store/pattern-store.ts, web/src/lib/store/session-store.ts, web/src/lib/components/ui/connections/ParticleSystem.ts, web/src/lib/store/note-store.ts (7 orphaned of 102 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; 102 of the 205 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
DM2 · Strongly-typed ids· Primitive id on a domain type · ×1
Primitive id on a domain type: Attachment.ID internal/domain/attachment.go:24— `Attachment.ID` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Domain depends on infrastructure: domain internal/domain/attachment.go:11— The domain package `github.com/danielmiessler/fabric/internal/domain` imports `net/http` — an infrastructure concern (persistence/HTTP/broker/auth). The dependency direction points from the domain layer to infrastructure; invert it behind a domain-owned port.
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 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `web`.
No SAST REDACTED:9— No static application security testing detected. For this repository's stack, add gosec / govulncheck (or golangci-lint) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling· Dependabot does not watch github-actions/gomod/pip · ×1
Dependabot does not watch github-actions/gomod/pip web/.github/dependabot.yml:7— `web/.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `gomod`, `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
R7 · Dead Code· Unused export 'createStorageAPI' · ×1
Unused export 'createStorageAPI' web/src/lib/api/base.ts:60— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused module-local declaration 'saveToObsidian' · ×1
Unused module-local declaration 'saveToObsidian' web/src/lib/components/chat/ChatInput.svelte:135— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'handleMouseLeave' · ×1
Unused module-local declaration 'handleMouseLeave' web/src/lib/components/ui/help/HelpModal.svelte:11— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Write-only private field 'validator' · ×1
Write-only private field 'validator' web/src/lib/services/ChatService.ts:40— This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
R7 · Dead Code· Unused module-local declaration 'cards' · ×1
Unused module-local declaration 'cards' web/src/routes/posts/Search.svelte:9— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
X2 · Cancellation propagation· Not all functions that make a request accept a context.Context or an AbortSignal · ×1
Not all functions that make a request accept a context.Context or an AbortSignal — Only 20/40 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X7 · Silent fallback defaults· Pending state with no failure state · ×1
Pending state with no failure state web/src/lib/components/ui/noteDrawer/NoteDrawer.svelte:136— The view draws `Saving...` under `saving`, but `saving` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Silent fallback default on error internal/plugins/ai/codex/errors.go:155— `extractErrorCode` turns a non-nil `err` into `return ""` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. 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 `if` or in the doc comment, and the row stops firing.
Subsumed condition operand internal/cli/chat.go:210— `strings.Contains(lowerModel, "preview-tts")` can never decide this `||` — every value satisfying `strings.Contains(lowerModel, "preview-tts")` also satisfies `strings.Contains(lowerModel, "tts")`, 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: github.com/anthropics/anthropic-sdk-go/v2 — `github.com/anthropics/anthropic-sdk-go/v2` is required at v2.8.0 in REDACTED, but v2.9.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/anthropics/anthropic-sdk-go/v2@v2.9.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2 — `github.com/aws/aws-sdk-go-v2` is required at v1.47.8 in REDACTED, but v1.48.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2@v1.48.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream — `github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream` is required at v1.7.26 in REDACTED, but v1.7.27 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream@v1.7.27 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/config — `github.com/aws/aws-sdk-go-v2/config` is required at v1.33.17 in REDACTED, but v1.33.18 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/config@v1.33.18 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/credentials — `github.com/aws/aws-sdk-go-v2/credentials` is required at v1.20.17 in REDACTED, but v1.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/credentials@v1.21.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/bedrock — `github.com/aws/aws-sdk-go-v2/service/bedrock` is required at v1.74.6 in REDACTED, but v1.74.7 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/bedrock@v1.74.7 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/bedrockruntime — `github.com/aws/aws-sdk-go-v2/service/bedrockruntime` is required at v1.63.12 in REDACTED, but v1.63.13 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/bedrockruntime@v1.63.13 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/openai/openai-go/v3 — `github.com/openai/openai-go/v3` is required at v3.98.0 in REDACTED, but v3.99.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/openai/openai-go/v3@v3.99.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: google.golang.org/api — `google.golang.org/api` is required at v0.311.0 in REDACTED, but v0.314.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get google.golang.org/api@v0.314.0 && go mod tidy` and commit the updated REDACTED and go.sum.
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 5 file(s) — `internal/server/contexts.go`, `internal/server/patterns.go`, `internal/server/sessions.go`, `internal/util/groups_items.go`, `web/src/lib/services/PdfConversionService.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a1d4b3-cc5a-7182-a40b-734fbeb52662 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 54 · Warnings: 350 · Recommendations: 46 · Info: 9 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 13-11-2026 @ 11:38 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.